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

LinkoraApp/Linkora

Measured 16 November 2026, 18:14 UTC, at code version 1e3890b

First survey, so nothing to compare with yet
CAI score 48.4out of 100 Adequate
CriticalWeakAdequateStrongExemplary

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

A medium codebase: 46,333 lines of product code in 7 projects, tests not counted · Estimated rebuild effort: about 0.4 person-years · Weakest lens: Production Readiness, 34.4

Findings by how serious they are

42 critical 325 serious 46 minor

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

This survey was produced by

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

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

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

53of 53 dimensions measured by tools.
401of 413 findings point to an exact file and line, so you can open each one in the code. The other 12 concern the repository as a whole, such as missing documentation.
53dimensions across 7 lenses, read from 46,333 lines of product code in 7 projects.
Chapters

Executive summary

LinkoraApp/Linkora falls short of our standard for a preview release because we found no logging, tracing or health checks in the code and no automated security scanning of the code, its secrets or its dependencies. It scores 48.4 out of 100 and is rated Adequate, and 38 of its 42 critical findings are security problems in the build pipeline and in the packages it uses.

Production Readiness, at 34.4, is the weakest lens and counts most in the score. The best first steps are adding a diagnostic log and adding automated security scanning, each worth about 7.2 points. Raising Production Readiness to 62 would lift the score to about 57.8.

Thirty-four pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. One known security hole in a package the code depends on can be used by attackers, and four sets of files in separate parts keep changing together, which points to hidden dependencies. Pinning each tool to an exact version, updating the vulnerable packages and making the hidden dependencies explicit would close these risks. Passing outside input through environment variables would fix the pipeline step that puts outside input straight into a shell command, and the pipeline step that runs a download without checking it needs each download checked against a known checksum first.

The product code is 46,333 lines, about €54,000 to rebuild. The check for the health of its packages couldn't finish, so that result is missing, not a clean pass.

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

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

If Production Readiness rose from 34.4 to 62, the lowest score rated Strong, the score would rise from 48.4 to about 57.8.

Code composition: what the lines of code are
Product code 90%Tests 10%
Rebuild cost: about €54,000 · Estimate
Cost to rebuild€18,000 to €91,000, for 301 to 956 hours of work, about 0.4 person-years for one engineer
Difficulty of the problemStandard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor×0.7 at a score of 48. 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.
SizeMedium: 46,333 lines of product code
What it is notNot a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one.

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

Top priorities

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

1
Write a diagnostic trail the user can hand back with a bug report: a log file under the platform's per-user data directory, switchable with a `--verbose`/`--debug` flag.
Start with the error paths that emit nothing — a discarded error is the failure the user cannot describe and you cannot reproduce.
Raises the score by about 7.2 points · Medium effort · Observability
2
Add a SAST step to CI running what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
Raises the score by about 7.2 points · Medium effort · Security & performance tooling
3
Keep a changelog (e.g.
Keep-a-Changelog) recording what shipped in each release.
Raises the score by about 3.3 points · Medium effort · Release Hygiene

Diagnosis: what the measurements show together

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

Where the investment is most exposed · Value at risk
This code would cost about €54,000 to build again, about 0.4 person-years of work. Its weakest lens is Production Readiness, at 34.4 (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.
One cause behind 34 Domain Modelling findings · Common cause
34 findings in the Domain Modelling lens come from the same cause. The code models the business as objects, such as an order or a customer, and each object should guard its own rules: an order, for example, should refuse to be shipped before it has been paid. Here the objects don't do that. Other code can change an object's data directly, so it can put an order into a state the rules forbid. Some objects only hold data, while the rules that should keep that data valid sit elsewhere in the code. Identifiers, such as order numbers and customer numbers, are passed around as plain numbers or text, so nothing stops the code from using one kind where another belongs. Because all of these findings have the same cause, fixing it once, in the business objects themselves, deals with them together.
Based on: Encapsulated state (2 findings) · Rich vs anemic model (13 findings) · Strongly-typed ids (19 findings)
What to do: Give each business object the methods that enforce its rules, such as a method for shipping an order that first checks it has been paid, and let only those methods change its data. Give each kind of identifier a type of its own, so an order number can't be used where a customer number belongs.
If you do one thing first · First action
Write a diagnostic trail the user can hand back with a bug report: a log file under the platform's per-user data directory, switchable with a `--verbose`/`--debug` flag. Of all the actions in this report, it raises the score most for the work it takes: about 7.2 points for medium effort. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
What hard-to-read code costs each year · Cost
Four dimensions measure how easy the code is to work in: two measure how tangled its logic is, one how much of it is copied, and one how well each part sticks to a single job. In this codebase they average 6.2 out of 10. Code at that level is slower to change than clean code, and we estimate the extra work at 4% to 10% on every change. The history of the code shows how much it changes: about 47,846 lines over the last 90 days, which is about 194,042 lines a year. At that pace, the extra work comes to an estimated 21.2 to 127.3 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 — module dependency graph

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

arch :androidApp :androidApp :shared :shared :androidApp->:shared :web-capture :web-capture :androidApp->:web-capture :desktopApp :desktopApp :desktopApp->:shared :desktopApp->:web-capture :shared->:web-capture :webApp :webApp :webApp->:shared :webApp->:web-capture Linkora Linkora sqlite-wasm-worker sqlite-wasm-worker

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.

145 modules, with 338 dependencies between them. 2 loops run through 28 of the modules, marked above the diagonal.

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

Which modules use which. The module on each row uses the module in each column, and the number counts the pairs of types that connect them. A cell above the diagonal is part of a loop.
uses →1 com.sakethh.linkora.domain.model.panel2 com.sakethh.linkora.domain.model.tag3 com.sakethh.linkora.ui.navigation.Navigation4 com.sakethh.linkora.domain.dto.server.folder5 com.sakethh.linkora.domain.dto.server.link6 com.sakethh.linkora.domain.model.link7 com.sakethh.linkora.ui.domain8 com.sakethh.linkora.ui.domain.model9 com.sakethh.linkora.domain.model10 com.sakethh.linkora.domain.dto.server11 com.sakethh.linkora.domain.repository.local12 com.sakethh.linkora.domain.repository.remote13 com.sakethh.linkora.domain14 com.sakethh.linkora.data.local.dao15 com.sakethh.linkora.data.remote.repository16 com.sakethh.linkora.domain.repository17 com.sakethh.linkora.domain.repository.LocalizationRepo18 com.sakethh.linkora.ui.components19 com.sakethh.linkora.ui.components.link20 com.sakethh.linkora.ui.domain.AddANewLinkDialogBoxAction21 com.sakethh.linkora.data22 com.sakethh.linkora.data.local23 com.sakethh.linkora.ui.screens.home.panels24 com.sakethh.linkora.platform.NativeUtils25 com.sakethh.linkora.ui.screens.settings26 com.sakethh.linkora.ui.screens.settings.section.data27 com.sakethh.linkora.platform28 com.sakethh.linkora.utils29 com.sakethh.linkora.data.local.repository30 com.sakethh.linkora.data.remote.repository.sync31 com.sakethh.linkora.ui32 com.sakethh.linkora.ui.components.sorting33 com.sakethh.linkora.ui.screens.settings.section34 com.sakethh.linkora.ui.screens.settings.section.data.sync35 com.sakethh.linkora36 com.sakethh.linkora.di37 com.sakethh.linkora.ui.screens.collections38 com.sakethh.linkora.ui.screens.home39 com.sakethh.linkora.ui.screens.search40 (global)
1 com.sakethh.linkora.domain.model.panel
2 com.sakethh.linkora.domain.model.tag
3 com.sakethh.linkora.ui.navigation.Navigation
4 com.sakethh.linkora.domain.dto.server.folder6
5 com.sakethh.linkora.domain.dto.server.link154
6 com.sakethh.linkora.domain.model.link12
7 com.sakethh.linkora.ui.domain1
8 com.sakethh.linkora.ui.domain.model4235
9 com.sakethh.linkora.domain.model23126
10 com.sakethh.linkora.domain.dto.server2311112
11 com.sakethh.linkora.domain.repository.local442210131
12 com.sakethh.linkora.domain.repository.remote651207
13 com.sakethh.linkora.domain12212211
14 com.sakethh.linkora.data.local.dao23172
15 com.sakethh.linkora.data.remote.repository651866
16 com.sakethh.linkora.domain.repository122
17 com.sakethh.linkora.domain.repository.LocalizationRepo2
18 com.sakethh.linkora.ui.components12134
19 com.sakethh.linkora.ui.components.link33333
20 com.sakethh.linkora.ui.domain.AddANewLinkDialogBoxAction311111
21 com.sakethh.linkora.data13913122
22 com.sakethh.linkora.data.local12101
23 com.sakethh.linkora.ui.screens.home.panels43311
24 com.sakethh.linkora.platform.NativeUtils22111
25 com.sakethh.linkora.ui.screens.settings2121112
26 com.sakethh.linkora.ui.screens.settings.section.data1413211113
27 com.sakethh.linkora.platform13611
28 com.sakethh.linkora.utils1341
29 com.sakethh.linkora.data.local.repository4422101305131311122
30 com.sakethh.linkora.data.remote.repository.sync12219142612
31 com.sakethh.linkora.ui12613113
32 com.sakethh.linkora.ui.components.sorting21111112
33 com.sakethh.linkora.ui.screens.settings.section11221
34 com.sakethh.linkora.ui.screens.settings.section.data.sync1113113
35 com.sakethh.linkora95222
36 com.sakethh.linkora.di1263215112
37 com.sakethh.linkora.ui.screens.collections215669822
38 com.sakethh.linkora.ui.screens.home211114111
39 com.sakethh.linkora.ui.screens.search11114511
40 (global)13111
Uses a module listed above itPart of a loopThe module itself
1 com.sakethh.linkora.domain.model.panel2 com.sakethh.linkora.domain.model.tag3 com.sakethh.linkora.ui.navigation.Navigation4 com.sakethh.linkora.domain.dto.server.folder5 com.sakethh.linkora.domain.dto.server.link6 com.sakethh.linkora.domain.model.link7 com.sakethh.linkora.ui.domain8 com.sakethh.linkora.ui.domain.model9 com.sakethh.linkora.domain.model10 com.sakethh.linkora.domain.dto.server11 com.sakethh.linkora.domain.repository.local12 com.sakethh.linkora.domain.repository.remote13 com.sakethh.linkora.domain14 com.sakethh.linkora.data.local.dao15 com.sakethh.linkora.data.remote.repository16 com.sakethh.linkora.domain.repository17 com.sakethh.linkora.domain.repository.LocalizationRepo18 com.sakethh.linkora.ui.components19 com.sakethh.linkora.ui.components.link20 com.sakethh.linkora.ui.domain.AddANewLinkDialogBoxAction21 com.sakethh.linkora.data22 com.sakethh.linkora.data.local23 com.sakethh.linkora.ui.screens.home.panels24 com.sakethh.linkora.platform.NativeUtils25 com.sakethh.linkora.ui.screens.settings26 com.sakethh.linkora.ui.screens.settings.section.data27 com.sakethh.linkora.platform28 com.sakethh.linkora.utils29 com.sakethh.linkora.data.local.repository30 com.sakethh.linkora.data.remote.repository.sync31 com.sakethh.linkora.ui32 com.sakethh.linkora.ui.components.sorting33 com.sakethh.linkora.ui.screens.settings.section34 com.sakethh.linkora.ui.screens.settings.section.data.sync35 com.sakethh.linkora36 com.sakethh.linkora.di37 com.sakethh.linkora.ui.screens.collections38 com.sakethh.linkora.ui.screens.home39 com.sakethh.linkora.ui.screens.search40 (global)com.sakethh.linkora.domain.model.panel1com.sakethh.linkora.domain.model.tag2com.sakethh.linkora.ui.navigation.Navigation3com.sakethh.linkora.domain.dto.server.folder4com.sakethh.linkora.domain.dto.server.link5com.sakethh.linkora.domain.model.link6com.sakethh.linkora.ui.domain7com.sakethh.linkora.ui.domain.model8com.sakethh.linkora.domain.model9com.sakethh.linkora.domain.dto.server10com.sakethh.linkora.domain.repository.local11com.sakethh.linkora.domain.repository.remote12com.sakethh.linkora.domain13com.sakethh.linkora.data.local.dao14com.sakethh.linkora.data.remote.repository15com.sakethh.linkora.domain.repository16com.sakethh.linkora.domain.repository.LocalizationRepo17com.sakethh.linkora.ui.components18com.sakethh.linkora.ui.components.link19com.sakethh.linkora.ui.domain.AddANewLinkDialogBoxAction20com.sakethh.linkora.data21com.sakethh.linkora.data.local22com.sakethh.linkora.ui.screens.home.panels23com.sakethh.linkora.platform.NativeUtils24com.sakethh.linkora.ui.screens.settings25com.sakethh.linkora.ui.screens.settings.section.data26com.sakethh.linkora.platform27com.sakethh.linkora.utils28com.sakethh.linkora.data.local.repository29com.sakethh.linkora.data.remote.repository.sync30com.sakethh.linkora.ui31com.sakethh.linkora.ui.components.sorting32com.sakethh.linkora.ui.screens.settings.section33com.sakethh.linkora.ui.screens.settings.section.data.sync34com.sakethh.linkora35com.sakethh.linkora.di36com.sakethh.linkora.ui.screens.collections37com.sakethh.linkora.ui.screens.home38com.sakethh.linkora.ui.screens.search39(global)4061541214235231262311112442210131651207122122112317265186612221213433333311111139131221210143311221112121112141321111313611134144221013051313111221221914261212613113211111121122111131139522212632151122156698222111141111111451113111+105 more modules (most-connected shown)

At a glance — Code Health · 74.1 · Strong ·

At a glance — Architecture · 83.4 · Strong ·

At a glance — Maturity · 68.5 · Adequate · gated by M2 ·

At a glance — Readiness · 34.4 · Weak · gated by P2, P3 ·

At a glance — Security · 69.0 · Adequate · gated by D36 ·

At a glance — Domain Modelling · 46.5 · Adequate · gated by DM2, DM4 ·

At a glance — Performance · 100.0 · Exemplary ·

Security & Compliance — OWASP Top-10 mapping

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

OWASP categoryFindingsSeverity
A05:2025 — Injection40High / Critical
A03:2025 — Software Supply Chain Failures8High / Critical

Roadmap

Top priorities: Write a diagnostic trail the user can hand back with a bug report: a log file under the platform's per-user data directory, switchable with a `--verbose`/`--debug` flag. Start with the error paths that emit nothing — a discarded error is the failure the user cannot describe and you cannot reproduce; Add a SAST step to CI running what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing; Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.

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

Do thisHelpsEffortDimension
Write a diagnostic trail the user can hand back with a bug report: a log file under the platform's per-user data directory, switchable with a `--verbose`/`--debug` flag. Start with the error paths that emit nothing — a discarded error is the failure the user cannot describe and you cannot reproduce.+7.2 ptsMediumObservability
Add a SAST step to CI running what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.+7.2 ptsMediumSecurity & performance tooling
Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.+3.3 ptsMediumRelease Hygiene
Adopt strongly-typed ids across the domain — finish the migration or document the boundary; primitive ids invite transposed-argument bugs.+2.7 ptsMediumStrongly-typed ids
Move business rules onto the aggregates/entities they govern so invariants are enforced at the source, not in anemic services.+2.7 ptsMediumRich vs anemic model
Resolve the 1 No ADRs found finding(s) in ADR Quality — start with build.gradle.kts.+1.2 ptsLowADR Quality
Give each aggregate one way in that can refuse — a guarded constructor, value-object parameters that validate themselves, or a private constructor behind a factory that returns a failure.+2.0 ptsMediumConstructible invalid state
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).+1.5 ptsMediumEncapsulated state

File quality

Per-file score 0–10 — a quality signature. Of 90 files carrying findings, judged against the Preview bar: 2% slop · 15% mixed · 83% near-clean.

FileScoreBandWorst signal
REDACTED2.3SlopStatic Analysis (SAST): High: REDACTED
REDACTED2.3SlopStatic Analysis (SAST): High: REDACTED
shared/src/commonMain/kotlin/com/sakethh/linkora/data/local/repository/LocalLinksRepoImpl.kt4.8MixedCyclomatic Complexity: LocalLinksRepoImpl.addANewLink (cyclomatic 29)
androidApp/src/main/kotlin/com/sakethh/linkora/LinkoraApp.kt5.5MixedChange Coupling: Boundary-crossing change coupling: LinkoraApp.kt ↔ ViewModelModule.kt
shared/src/commonMain/kotlin/com/sakethh/linkora/data/local/repository/LocalFoldersRepoImpl.kt5.9MixedGod Classes: TooManyMethods: LocalFoldersRepoImpl
shared/src/desktopMain/kotlin/com/sakethh/linkora/platform/FileManager.kt5.9MixedCode Duplication: Edited copy of a member (21 corresponding lines)
shared/src/commonMain/kotlin/com/sakethh/linkora/data/remote/repository/sync/PendingQueueService.kt6.0MixedExplicit Debt: TodoComment
shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/link/AddANewLinkDialog.kt6.0MixedExplicit Debt: TodoComment
shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/settings/section/LanguageSettingsScreenVM.kt6.0MixedExplicit Debt: TodoComment
shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/search/SearchScreenVM.kt6.0MixedExplicit Debt: TodoComment
shared/src/commonMain/kotlin/com/sakethh/linkora/ui/AppVM.kt6.3MixedCode Duplication: Edited copy of a member (28 corresponding lines)
REDACTED6.3MixedStatic Analysis (SAST): Medium: REDACTED
androidApp/src/main/kotlin/com/sakethh/linkora/MainActivity.kt6.5MixedChange Coupling: Boundary-crossing change coupling: MainActivity.kt ↔ ThemeSettingsScreen.kt
androidApp/src/main/kotlin/com/sakethh/linkora/ShareToSaveActivity.kt6.5MixedChange Coupling: Boundary-crossing change coupling: ShareToSaveActivity.kt ↔ ViewModelModule.kt
shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/settings/section/GeneralSettingsScreen.kt6.7MixedExplicit Debt: TodoComment
shared/src/commonMain/kotlin/com/sakethh/linkora/data/remote/repository/sync/LocalDataUpdateService.kt7.0Near-cleanCyclomatic Complexity: LocalDataUpdateService.updateLocalDBAccordingToEvent (cyclomatic 109)
shared/src/commonMain/kotlin/com/sakethh/linkora/domain/Mappers.kt7.0Near-cleanCode Duplication: Edited copy of a member (15 corresponding lines)
shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/CollectionLayoutManager.kt7.0Near-cleanCyclomatic Complexity: CollectionLayoutManagerKt.CollectionLayoutManager (cyclomatic 60)
shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/collections/CollectionDetailPane.kt7.0Near-cleanCyclomatic Complexity: CollectionDetailPaneKt.CollectionDetailPane (cyclomatic 32)
shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/folder/RenameFolderDialog.kt7.0Near-cleanCognitive Complexity: RenameFolderDialogKt.RenameFolderDialog (cognitive 21)

How the grades work

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

Critical — 42

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

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

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

Could not be resolved — 13

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 53 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 — 53 dimensions across the health lenses
D1D2D3D4D5D6D13D14D15D17D19D20D26D27D28D29D30D34D35D36D43D44AX10AX3AX4AX6DM11DM12DM2DM4DM5DM6DM9M1M2M3M4P1P2P3P4P6PF3X1X12X16X18X2X21X25X27X3X5

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

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

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

Tools & methods

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

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

Every finding is locatable in findings.md. Run 01a1e591-20ff-7998-a082-c783051bae48.

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

Run transparency — what happened this run

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

  • D8 Code Coverage — 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. Coverage NOT MEASURED: test source is present (.kt) but the built-in coverage collector has no runner for this repository's ecosystem — so this suite was never executed by it. Not scored — this is a gap in the analyzer's language coverage, not a defect in the repo.
  • D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.kt) and this repository declares a JVM test suite (repository root, Gradle), but it was not re-run: no test result was produced. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
  • D12 Dependency Hygiene — 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 repository's dependency manifests WERE read and their pinning discipline assessed; what went unanswered is the currency half, because api.foojay.io — the registry that answers it — was asked and did not reply (the build stopped because api.foojay.io, a repository this project declares, refused it with HTTP 403 — what this scan's egress allowlist returns for a host that is not on it, so the dependency graph was not resolved). This is OUR side and it is an ENVIRONMENT fault, not a missing collector: the collector exists and ran. An HTTP 403 here is what this scan's egress allowlist returns for a host that is not on it, so the remedy is to add api.foojay.io to the allowlist and re-run — not to build anything.
  • D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (9 contributor(s) across 1382 commit(s) sampled, automation and bot accounts excluded). One of them holds 99% of the history; the other 8 hold 0.1% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
  • D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
  • 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 naming rules read C# through Roslyn and every other language through its sidecar model; these languages are left out (PHP's reading is its own change, a Roslyn-loaded VB or F# project has no population builder yet). Their declarations carry no naming verdict this run — this says nothing about whether their names are consistent.
  • D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
  • D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
  • D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is an ADMISSION gap, not an environment fault: no published-package marker D22 reads admitted any project here. D22 DOES collect the public API of every language in this tree, and admits a project only when its manifest makes that ecosystem's publication act in a form the marker recognises — so what is missing is not a collector but an admission rule for the publication act this repository makes, if it makes one. The remedy is a better discriminator for that marker — not a collector, and no change to the scan image can close it. The marker's rules are measured to refuse applications, so one refused repository is the rule working as calibrated; several are the evidence that it is too strict. For npm the surface is what a published package.json's entry points (exports, main, module, types) export, followed through the source; an entry that names build output the tree does not commit (dist/, build/) is not followed back to source, because only a tsconfig outDir/rootDir pair states that mapping and a bundler's input lives in executable configuration this engine does not evaluate.
  • D24 Comment Value — 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. 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. `shared/build.gradle.kts`, `shared/src/androidDesktopMain/kotlin/Utils.kt`, `shared/src/androidMain/kotlin/com/sakethh/linkora/platform/FileManager.kt`, `shared/src/androidMain/kotlin/com/sakethh/linkora/utils/ExtensionFunctions.kt`, `shared/src/commonMain/kotlin/com/sakethh/linkora/data/local/dao/LocalDatabaseUtilsDao.kt`, … (+17 more) produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
  • AX1 Captive dependencies — 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 Microsoft.Extensions.DependencyInjection registrations in C# and Spring beans in Java/Kotlin only, and this repository defines its own container in shared/src/commonMain/kotlin/com/sakethh/linkora/di/DependencyContainer.kt, whose lifetimes are not modelled 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.
  • AXB1 Runtime evidence locked — no reproducible boot — 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. Subject: 1 markup document(s) — HTML, Razor, JSX, Vue, Svelte or server templates. The Runtime Evidence tier boots an app only via docker-compose, an Aspire AppHost, a Dockerfile, an npm dev script, a web service's own toolchain entry point (cargo, go, dotnet, Python, Spring Boot), or an Android app's own Gradle wrapper (run on an emulator); an Apple or Flutter app needs a host it lacks. None applied, so no live runtime a11y/egress/header evidence was collected. You can widen what we reach: add a docker-compose.yml (or an Aspire AppHost) that brings the app up with its dependencies. We then boot it in an isolated sandbox and gathers real runtime evidence — you change nothing in your pipeline (no CI step, no SDK).
  • 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.
  • 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, Scala, Rust and Java source only, and this repository's Kotlin 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, Scala and Rust source only, and this repository's Kotlin 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.
  • 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.

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.
  • D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
  • D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
  • D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
  • D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
  • D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
  • D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
  • 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.
  • D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
  • D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
  • D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
  • D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
  • AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
  • 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.

Dimensions

D1 · Cyclomatic Complexity5.5 / 10Adequate✓ Tool-verified

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

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

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

24 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was LocalDataUpdateService.updateLocalDBAccordingToEvent at 109.

LocalDataUpdateService.updateLocalDBAccordingToEvent (cyclomatic 109)shared/src/commonMain/kotlin/com/sakethh/linkora/data/remote/repository/sync/LocalDataUpdateService.kt:76
PendingQueueService.pushPendingSyncQueueToServer (cyclomatic 71)shared/src/commonMain/kotlin/com/sakethh/linkora/data/remote/repository/sync/PendingQueueService.kt:80
CollectionLayoutManagerKt.CollectionLayoutManager (cyclomatic 60)shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/CollectionLayoutManager.kt:73
AddANewLinkDialogKt.BottomPartOfAddANewLinkDialogBox (cyclomatic 43)shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/link/AddANewLinkDialog.kt:661
CollectionsScreenKt.CollectionsScreen (cyclomatic 39)shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/collections/CollectionsScreen.kt:132

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

What to do

  1. Bring the 2 bodies over 60 down to 60 or less in Cyclomatic Complexity — start with LocalDataUpdateService.updateLocalDBAccordingToEvent (cyclomatic 109), PendingQueueService.pushPendingSyncQueueToServer (cyclomatic 71). — 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 2 together lifts Cyclomatic Complexity from 5.5 to about 6.3/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.

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

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

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

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

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

31 method(s) exceeded the cognitive complexity threshold of 15; the worst was LocalDataUpdateService.updateLocalDBAccordingToEvent at 127.

LocalDataUpdateService.updateLocalDBAccordingToEvent (cognitive 127)shared/src/commonMain/kotlin/com/sakethh/linkora/data/remote/repository/sync/LocalDataUpdateService.kt:76
CollectionLayoutManagerKt.CollectionLayoutManager (cognitive 102)shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/CollectionLayoutManager.kt:73
AddANewLinkDialogKt.BottomPartOfAddANewLinkDialogBox (cognitive 79)shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/link/AddANewLinkDialog.kt:661
DataSettingsScreenKt.DataSettingsScreen (cognitive 72)shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/settings/section/data/DataSettingsScreen.kt:125
BottomNavOnSelectionKt.BottomNavOnSelection (cognitive 71)shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/nav/BottomNavOnSelection.kt:72

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

What to do

  1. Bring the 5 bodies over 60 down to 60 or less in Cognitive Complexity — start with LocalDataUpdateService.updateLocalDBAccordingToEvent (cognitive 127), CollectionLayoutManagerKt.CollectionLayoutManager (cognitive 102), AddANewLinkDialogKt.BottomPartOfAddANewLinkDialogBox (cognitive 79). — 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 5 together lifts Cognitive Complexity from 4.5 to about 5.7/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.

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

D3 · God Classes5.6 / 10Adequate✓ Tool-verified

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

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

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

65 god class(es) detected.

MethodTooLong: DataSettingsScreenKt.DataSettingsScreen · ×44shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/settings/section/data/DataSettingsScreen.kt:125
FileTooLong: link/AddANewLinkDialog.kt · ×13shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/link/AddANewLinkDialog.kt
ClassTooLong: LocalLinksRepoImpl · ×6shared/src/commonMain/kotlin/com/sakethh/linkora/data/local/repository/LocalLinksRepoImpl.kt:63
TooManyMethods: LocalLinksRepoImpl · ×2shared/src/commonMain/kotlin/com/sakethh/linkora/data/local/repository/LocalLinksRepoImpl.kt:63

What to do

  1. Resolve the 44 MethodTooLong finding(s) in God Classes — start with AddANewLinkDialog.kt (3), OnboardingSlidesScreen.kt (2), ImportDataRepoImpl.kt (2). — One of this dimension's main actionable groups (44 warning-level).
  2. Resolve the 13 FileTooLong finding(s) in God Classes — start with AddANewLinkDialog.kt, DataSettingsScreen.kt, LocalLinksRepoImpl.kt. — One of this dimension's main actionable groups (13 warning-level).
  3. Resolve the 6 ClassTooLong finding(s) in God Classes — start with LocalLinksRepoImpl.kt, LocalDataUpdateService.kt, PendingQueueService.kt. — One of this dimension's main actionable groups (6 warning-level).

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

D4 · Code Duplication5.8 / 10Adequate✓ Tool-verified

What it measures: How much of the production code is copy-pasted: the share of production lines inside a reported copy (every copy of a duplicated block or of an edited member, each line once), 10 at none and 0 at a quarter of the lines.

Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), scored on the share of production lines inside a reported copy (each line once; 10 at none, 0 at a quarter). Deterministic.

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

78 duplicated block group(s) detected. 10.4 % of the production lines (4,834 of 46,333) are in a reported copy. A further 31 rows report members as variants of one another; the share counts each copied line once, however many rows cite it.

Duplicated block (15 lines × 2) · ×8shared/src/commonMain/kotlin/com/sakethh/linkora/data/remote/repository/sync/LocalDataUpdateService.kt:664
Duplicated block (20 lines × 2) · ×4shared/src/androidMain/kotlin/com/sakethh/linkora/platform/FileManager.kt:185
Duplicated block (19 lines × 2) · ×4shared/src/commonMain/kotlin/com/sakethh/linkora/data/local/repository/LocalLinksRepoImpl.kt:298
Duplicated block (17 lines × 2) · ×4shared/src/androidMain/kotlin/com/sakethh/linkora/worker/AllLinksWebCaptureWorker.kt:112
Edited copy of a member (27 corresponding lines) · ×3shared/src/androidMain/kotlin/com/sakethh/linkora/utils/ExtensionFunctions.kt:78

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

What to do

  1. Resolve the 8 Duplicated block (15 lines × 2) finding(s) in Code Duplication — start with SettingsScreenViewModel.kt (3), LocalDataUpdateService.kt, SyncSessionServiceImpl.kt. — One of this dimension's main actionable groups (8 warning-level).
  2. Resolve the 4 Duplicated block (20 lines × 2) finding(s) in Code Duplication — start with FileManager.kt, RenameFolderDialog.kt, WebPageCaptureScreen.kt. — One of this dimension's main actionable groups (4 warning-level).
  3. Resolve the 4 Duplicated block (19 lines × 2) finding(s) in Code Duplication — start with LocalLinksRepoImpl.kt, RenameFolderDialog.kt, AddANewLinkDialog.kt. — One of this dimension's main actionable groups (4 warning-level).

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

D5 · Coupling8.9 / 10Strong✓ Tool-verified

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

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

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

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

7 production modules (Gradle+npm), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; edges a convention plugin adds from buildSrc or build-logic are not visible there; 1 module(s) off the main sequence, with abstractness counted on 5 of the 7 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).

Off the main sequence: :web-capture

What to do

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

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

D6 · Cohesion (LCOM4)9.2 / 10Stronggated by 3 serious findings✓ Tool-verified

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

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

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

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

3 of 43 classes have LCOM4 above 3.

Low cohesion: SearchScreenVM (LCOM4 6) · ×3shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/search/SearchScreenVM.kt:48

What to do

  1. Resolve the 3 Low cohesion finding(s) in Cohesion (LCOM4) — start with SearchScreenVM.kt, AppVM.kt, FileManager.kt. — One of this dimension's main actionable groups (3 warning-level).

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

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

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

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

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

Secret scan ran and found no leaked secrets.

✓ On the Gold path — maintain.

Detailed fixes: d13_recommendation.md.

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

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

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

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

0 of 40 declared JVM dependency artifact(s) use a banned license. Licences were resolved from the POMs Maven Central publishes, over the coordinates this repository's 7 Maven/Gradle manifest(s) declare with a version resolvable from the manifest itself — the same declaration-site closure this analysis reads for dependency currency. The JVM has no lockfile a checkout is guaranteed to carry, so this is deliberately NOT the transitive closure. A further 11 coordinate(s) are not published to Maven Central — another repository (Google's Maven hosts androidx), a SNAPSHOT, or a private artifact — so their licences are not readable from here and they are outside this verdict.

✓ On the Gold path — maintain.

Detailed fixes: d14_recommendation.md.

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

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

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

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

Top hotspots: shared/src/commonMain/kotlin/com/sakethh/linkora/data/remote/repository/sync/LocalDataUpdateService.kt (4×109=436); shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/settings/section/data/DataSettingsScreen.kt (10×34=340); shared/src/commonMain/kotlin/com/sakethh/linkora/ui/App.kt (10×30=300)

Hotspot: shared/src/commonMain/kotlin/com/sakethh/linkora/data/remote/repository/sync/LocalDataUpdateService.kt · ×22shared/src/commonMain/kotlin/com/sakethh/linkora/data/remote/repository/sync/LocalDataUpdateService.kt:76

What to do

  1. Resolve the 22 Hotspot finding(s) in Churn × Complexity Hotspots — start with LocalDataUpdateService.kt, DataSettingsScreen.kt, App.kt. — One of this dimension's main actionable groups (22 warning-level).

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

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

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

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

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

9 deducted task-comment markers across 46333 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 · ×9shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/settings/section/GeneralSettingsScreen.kt:100

What to do

  1. Resolve the 9 TodoComment finding(s) in Explicit Debt — start with LanguageSettingsScreenVM.kt (2), HomeScreenVM.kt (2), GeneralSettingsScreen.kt. — One of this dimension's main actionable groups (9 warning-level).

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

D19 · Documentation Quality10.0 / 10Exemplary○ Nothing flagged

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

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

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

1 of 1 documentation facets pass in full. 4 document(s) read across 2 unit(s).

✓ On the Gold path — maintain.

Detailed fixes: d19_recommendation.md.

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

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

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

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

No architecture decision records were found.

No ADRs founddesktopApp/build.gradle.kts:41

What to do

  1. Resolve the 1 No ADRs found finding(s) in ADR Quality — start with build.gradle.kts. — 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.

D26 · Project Cohesion6.7 / 10Adequate✓ Tool-verified

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

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

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

1 of 6 build units (Gradle, npm) flagged as possibly oversized/incoherent.

Projects may be oversized for their cohesionshared/build.gradle.kts:1

What to do

  1. Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion — start with build.gradle.kts. — 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.

D27 · Navigability7.0 / 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.

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

84 % of calls cross a namespace and 59 % go through an interface, but 99 % of collaborators are co-located — so following a call takes several hops. Baseline: small — navigation cost is tolerated.

High interface indirection

What to do

  1. Resolve the 1 High interface indirection finding(s) in Navigability. — 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.

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

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

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

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

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

✓ On the Gold path — maintain.

Detailed fixes: d28_recommendation.md.

D29 · Static Analysis (SAST)5.1 / 10Adequate✓ Tool-verified

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

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

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

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

40 finding(s): 0 critical, 37 high, 3 medium, 0 low. 34 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 3 file(s) — `gradlew` (line 74, line 181), `shared/src/androidMain/kotlin/com/sakethh/linkora/platform/FileManager.kt` (line 282, line 409), `shared/src/commonMain/kotlin/com/sakethh/linkora/di/ViewModelModule.kt` (line 122) — 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

What to do

  1. Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
  2. Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
  3. No action in Static Analysis (SAST) — all 34 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 (34 issue-level, 0 of them charged here).

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

D30 · Dependency Vulnerabilities9.4 / 10Adequategated by 1 critical finding✓ Tool-verified

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

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

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

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

REDACTED

What to do

  1. Resolve the 1 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).

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

D34 · Knowledge Freshness10.0 / 10Exemplary✓ Tool-verified

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

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

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

Every significant source file has living knowledge — recently and meaningfully worked. Counted over 148 of the 339 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.

✓ On the Gold path — maintain.

Detailed fixes: d34_recommendation.md.

D35 · Change Coupling9.3 / 10Adequategated by 4 critical findings✓ Tool-verified

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

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

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

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

Strongest change-coupling: Utils.kt↔Expected.wasmJs.kt 87%; LocalFoldersRepoImpl.kt↔RemoteFoldersRepoImpl.kt 80%; LocalLinksRepoImpl.kt↔RemoteLinksRepoImpl.kt 80%

Boundary-crossing change coupling: LinkoraApp.kt ↔ ViewModelModule.kt · ×4androidApp/src/main/kotlin/com/sakethh/linkora/LinkoraApp.kt:1
Change coupling: Utils.kt ↔ Expected.wasmJs.kt · ×10shared/src/androidDesktopMain/kotlin/Utils.kt:1
Change-coupling hub: LocalFoldersRepoImpl.kt → PanelsDao.kt, LocalPanelsRepoImpl.kt, RemoteFoldersRepoImpl.kt · ×3shared/src/commonMain/kotlin/com/sakethh/linkora/data/local/repository/LocalFoldersRepoImpl.kt

What to do

  1. Resolve the 4 Boundary-crossing change coupling finding(s) in Change Coupling — start with LinkoraApp.kt (2), MainActivity.kt, ShareToSaveActivity.kt. — One of this dimension's main actionable groups (4 issue-level).
  2. Resolve the 10 Change coupling finding(s) in Change Coupling — start with LocalLinksRepoImpl.kt (2), Utils.kt, PanelsDao.kt. — One of this dimension's main actionable groups (10 warning-level).
  3. Resolve the 3 Change-coupling hub finding(s) in Change Coupling — start with LocalFoldersRepoImpl.kt, FoldersDao.kt, PreferencesImpl.kt. — One of this dimension's main actionable groups (3 warning-level).

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

D36 · Supply-chain Provenance & Signing2.5 / 10Weak✓ Tool-verified

What it measures: Whether the build pipeline provides supply-chain integrity — generated provenance/attestation, signed artifacts (cosign/sigstore), an SBOM, and pinned build actions. Presence of the configuration, not a runtime guarantee.

Method: Supply-chain provenance/signing read deterministically from CI/build config (.github/workflows, .gitlab-ci.yml, azure-pipelines, Jenkinsfile, .circleci) + the release surface: four signals — generated provenance/attestation (SLSA/in-toto/actions-attest), artifact signing (cosign/sigstore/gitsign), an SBOM (syft/sbom-action/*.spdx.json/*.cdx.json), and SHA-pinned build actions — scored 10·present/denom. NotApplicable without a build pipeline. Detects configuration presence, not runtime enforcement.

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

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

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

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

What to do

  1. Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
  2. Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
  3. Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).

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

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

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

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

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

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

✓ On the Gold path — maintain.

Detailed fixes: d43_recommendation.md.

D44 · Platform End-of-Life10.0 / 10Exemplary✓ Tool-verified

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.

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

0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 4 platform declaration(s) and 54 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.

Frontend & cross-cutting dimensions

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

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

Other · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified. How each file's role is decided, because the split is only as good as that: a generated name or a build-output tree makes it Generated, a test project makes it Test, and otherwise the file's NAMESPACE and PATH words are matched against fixed vocabularies in a fixed ORDER — domain, then infrastructure, then application — so a file whose words hit two layers is counted under the earlier one. A production file matching none of them counts as application, so that share reads 'application or unclassified' rather than a measured application layer. Roles come from naming convention, never from what the code does. On this repository the split was taken from the source tree on disk rather than from a loaded .NET workspace, so a file's role is decided by its PATH segments alone — no declared namespace was available to add to the evidence — and generated output is excluded from the census entirely rather than counted as a generated share.

Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.

Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.

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

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

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

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

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

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

AX6 · Interface segregation9.1 / 10Exemplary✓ Tool-verified

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

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

  • `FoldersDao` declares 38 abstract methods: `insertANewFolder`, `duplicateAFolder`, `insertMultipleNewFolders`, `getAllArchiveFoldersAsFlow`, `getAllArchiveFoldersAsList`, `getAllRootFoldersAsFlow`, `getAllRootFoldersAsList`, `getAllFoldersAsList`, `doesFolderTableHaveData`, `getAllFoldersAsFlow`, `getLatestFoldersTableID`, `getThisFolderData`, `doesFolderExists`, `doesThisRootFolderExists`, `getChildFoldersAsFlow`, `getChildFoldersAsList`, `renameAFolderName`, `markFolderAsArchive`, `markMultipleFoldersAsArchive`, `markMultipleFoldersAsRegular`, `markFolderAsRegularFolder`, `renameAFolderNote`, `updateFolder`, `updateFolderTimestamp`, `updateFoldersTimestamp`, `deleteAFolderNote`, `deleteAFolder`, `getChildFolders`, `getRootFoldersSortedById`, `getRootFoldersSortedByName`, `search`, `getRemoteFolderId`, `getRemoteIds`, `getLocalIdOfAFolder`, `getUnSyncedFolders`, `moveFolders`, `markFoldersAsRoot`, `updateARemoteLinkId`. Counted over its public functions with no body, once per name; default-bodied functions and properties are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — shared/src/commonMain/kotlin/com/sakethh/linkora/data/local/dao/FoldersDao.kt:12
  • `LinksDao` declares 40 abstract methods: `addANewLink`, `addMultipleLinks`, `deleteLinksOfFolder`, `deleteALinkNote`, `archiveALink`, `archiveMultipleLinks`, `deleteALink`, `deleteMultipleLinks`, `updateLinkNote`, `updateLinkTitle`, `isInArchive`, `search`, `getSortedLinks`, `getLinksSortedById`, `getLinksSortedByTitle`, `getAllLinks`, `getAllLinksAsFlow`, `getLinksOfThisFolderAsList`, `updateALink`, `getRemoteId`, `getLocalIdOfALink`, `getLocalIds`, `getLatestId`, `getLink`, `getUnSyncedLinks`, `updateLinkTimestamp`, `updateLinksTimestamp`, `doesLinkExist`, `changeIdOfALink`, `deleteLinksFromHistory`, `deleteLinks`, `moveLinks`, `getIdsOfCopiedLinks`, `updateRemoteLinkId`, `unarchiveLinks`, `getRemoteIds`, `getAllLinksSortedById`, `getAllLinksSortedByTitle`, `doesLinkTableHaveData`, `forceSetDefaultFolderToInternalIds`. Counted over its public functions with no body, once per name; default-bodied functions and properties are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — shared/src/commonMain/kotlin/com/sakethh/linkora/data/local/dao/LinksDao.kt:15
  • `PanelsDao` declares 28 abstract methods: `getLatestPanelID`, `getLatestPanelFolderID`, `addANewPanel`, `updateAPanel`, `updateAPanelFolder`, `getRemoteIdOfPanel`, `updateAFolderName`, `addMultiplePanels`, `addMultiplePanelFolders`, `deleteAPanel`, `updateAPanelName`, `updatePanelTimestamp`, `deleteConnectedFoldersOfPanel`, `addANewFolderInAPanel`, `deleteAFolderFromAPanel`, `deleteAFolderFromAllPanels`, `getAllThePanels`, `getAllThePanelsAsAList`, `doesPanelsTableHaveData`, `getAllThePanelFoldersAsAList`, `getAllThePanelFoldersAsAFlow`, `getAllTheFoldersFromAPanel`, `getPanel`, `getLocalPanelId`, `getLocalPanelFolderId`, `getPanelFolder`, `getUnSyncedPanels`, `getUnSyncedPanelFolders`. Counted over its public functions with no body, once per name; default-bodied functions and properties are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — shared/src/commonMain/kotlin/com/sakethh/linkora/data/local/dao/PanelsDao.kt:12
  • `TagsDao` declares 26 abstract methods: `createATag`, `updateATag`, `updateRemoteId`, `getATag`, `createLinkTags`, `deleteLinkTagsBasedOnTags`, `deleteATag`, `renameATag`, `getLastInsertedIdFromTags`, `getAllTags`, `getTagsSortedById`, `getTagsSortedByName`, `getAllTagsAsList`, `getAllTagLinksAsList`, `getAllLinkTags`, `getTagsBasedOnTheLinkId`, `getTags`, `search`, `getTagsWithLinkIds`, `getTagsWithLinkIdsAsList`, `getLocalTagIds`, `getLocalTags`, `getLocalTagId`, `getRemoteTagIds`, `getRemoteTagId`, `getUnsyncedTags`. Counted over its public functions with no body, once per name; default-bodied functions and properties are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — shared/src/commonMain/kotlin/com/sakethh/linkora/data/local/dao/TagsDao.kt:15
  • `LocalFoldersRepo` declares 29 abstract methods: `insertANewFolder`, `insertANewFolderLocally`, `getAllRootFoldersAsList`, `getAllFoldersAsResultList`, `getAllFoldersAsList`, `isFoldersTableEmpty`, `getAllFoldersAsFlow`, `getChildFoldersOfThisParentIDAsList`, `getLatestFoldersTableID`, `getThisFolderData`, `doesThisChildFolderExists`, `doesThisRootFolderExists`, `getRootFolders`, `getChildFolders`, `getChildFoldersAsList`, `sortFoldersAsNonResultFlow`, `getChildFoldersOfThisParentIDAsFlow`, `markFolderAsArchive`, `markFolderAsRegularFolder`, `markFoldersAsRoot`, `updateLocalFolderData`, `updateFolder`, `deleteAFolderNote`, `deleteAFolder`, `deleteMultipleFolders`, `search`, `getRemoteIdOfAFolder`, `getLocalIdOfAFolder`, `getUnSyncedFolders`. Counted over its public functions with no body, once per name; default-bodied functions and properties are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — shared/src/commonMain/kotlin/com/sakethh/linkora/domain/repository/local/LocalFoldersRepo.kt:7
  • `LocalLinksRepo` declares 31 abstract methods: `addANewLink`, `addANewLinkLocally`, `addMultipleLinks`, `getLinks`, `getLinksAsNonResultFlow`, `getAllLinks`, `deleteLinksOfFolder`, `deleteALinkNote`, `deleteALink`, `deleteMultipleLinks`, `archiveALink`, `updateLinkNote`, `updateLinkTitle`, `isInArchive`, `search`, `getLinksOfThisFolderAsList`, `getAllLinksAsFlow`, `updateALink`, `refreshLinkMetadata`, `getLocalLinkId`, `getRemoteLinkId`, `getALink`, `getLatestId`, `getUnSyncedLinks`, `changeIdOfALink`, `doesLinkExist`, `deleteDuplicateLinks`, `deleteLinksLocally`, `isLinksTableEmpty`, `forceSetDefaultFolderToInternalIds`, `scrapeLinkData`. Counted over its public functions with no body, once per name; default-bodied functions and properties are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — shared/src/commonMain/kotlin/com/sakethh/linkora/domain/repository/local/LocalLinksRepo.kt:12
  • `LocalPanelsRepo` declares 26 abstract methods: `addANewPanel`, `addANewPanelLocally`, `deleteAPanel`, `updateAPanelName`, `updatePanel`, `addANewFolderInAPanel`, `deleteAFolderFromAllPanels`, `deleteAFolderFromAPanel`, `getAllThePanels`, `getAllThePanelsAsAList`, `isPanelsTableEmpty`, `getAllThePanelFoldersAsAList`, `getAllThePanelFoldersAsAFlow`, `getAllTheFoldersFromAPanel`, `getPanel`, `getPanelFolder`, `getLocalPanelId`, `getRemotePanelId`, `getLocalPanelFolderId`, `updateAFolderName`, `addMultiplePanels`, `addMultiplePanelFolders`, `getLatestPanelID`, `getUnSyncedPanels`, `getUnSyncedPanelFolders`, `updateAPanelFolder`. Counted over its public functions with no body, once per name; default-bodied functions and properties are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — shared/src/commonMain/kotlin/com/sakethh/linkora/domain/repository/local/LocalPanelsRepo.kt:8
  • `LocalTagsRepo` declares 19 abstract methods: `createATag`, `createATagLocally`, `createLinkTags`, `deleteLinkTagsBasedOnTags`, `deleteATag`, `renameATag`, `getLastInsertedIdFromTags`, `getAllTags`, `getTags`, `getAllTagsAsList`, `getAllLinkTagsAsList`, `getAllLinkTags`, `getTagsBasedOnTheLinkId`, `getTagsForLinks`, `getTagsForLinksAsMap`, `search`, `getLocalTagIds`, `getLocalTags`, `getLocalTagId`. Counted over its public functions with no body, once per name; default-bodied functions and properties are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — shared/src/commonMain/kotlin/com/sakethh/linkora/domain/repository/local/LocalTagsRepo.kt:8

What to do

  • Split fat interfaces into focused role-interfaces so clients depend only on what they use.
DM11 · Constructible invalid state4.1 / 10Weak✓ Tool-verified

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.

  • `CaptureTrack`'s public constructor takes `capturedLinkId`, `captureWorkerId` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `CaptureTrack` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — shared/src/commonMain/kotlin/com/sakethh/linkora/domain/model/CaptureTrack.kt:7
  • `Folder`'s public constructor takes `name`, `note` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `Folder` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — shared/src/commonMain/kotlin/com/sakethh/linkora/domain/model/Folder.kt:21
  • `PendingSyncQueue`'s public constructor takes `operation`, `payload` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `PendingSyncQueue` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — shared/src/commonMain/kotlin/com/sakethh/linkora/domain/model/PendingSyncQueue.kt:7
  • `Snapshot`'s public constructor takes `content` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `Snapshot` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — shared/src/commonMain/kotlin/com/sakethh/linkora/domain/model/Snapshot.kt:7
  • `Link`'s public constructor takes `title`, `url`, `host`, `imgURL`, … as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `Link` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — shared/src/commonMain/kotlin/com/sakethh/linkora/domain/model/link/Link.kt:25
  • `LocalizedLanguage`'s public constructor takes `languageCode`, `languageName`, `contributionLink` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `LocalizedLanguage` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — shared/src/commonMain/kotlin/com/sakethh/linkora/domain/model/localization/LocalizedLanguage.kt:9
  • `LocalizedString`'s public constructor takes `languageCode`, `stringName`, `stringValue` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `LocalizedString` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — shared/src/commonMain/kotlin/com/sakethh/linkora/domain/model/localization/LocalizedString.kt:7
  • `Panel`'s public constructor takes `panelName` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `Panel` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — shared/src/commonMain/kotlin/com/sakethh/linkora/domain/model/panel/Panel.kt:10
  • `PanelFolder`'s public constructor takes `folderName` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `PanelFolder` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — shared/src/commonMain/kotlin/com/sakethh/linkora/domain/model/panel/PanelFolder.kt:10
  • `Tag`'s public constructor takes `name` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `Tag` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — shared/src/commonMain/kotlin/com/sakethh/linkora/domain/model/tag/Tag.kt:19
  • `WebCaptureMetadata`'s public constructor takes `link`, `uuid` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `WebCaptureMetadata` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — web-capture/src/commonMain/kotlin/com/sakethh/linkora/WebCaptureDatabase.kt:13

What to do

  • Give each aggregate one way in that can refuse — a guarded constructor, value-object parameters that validate themselves, or a private constructor behind a factory that returns a failure.
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.

DM2 · Strongly-typed ids3.0 / 10Weak✓ Tool-verified

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.

  • `CaptureTrack.capturedLinkId` 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. — shared/src/commonMain/kotlin/com/sakethh/linkora/domain/model/CaptureTrack.kt:8
  • `CaptureTrack.captureWorkerId` 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. — shared/src/commonMain/kotlin/com/sakethh/linkora/domain/model/CaptureTrack.kt:9
  • `Folder.parentFolderId` is a raw `Long` — give it a strongly-typed id: a dedicated single-field type wrapping the `Long`, in whatever form your language spells that. — shared/src/commonMain/kotlin/com/sakethh/linkora/domain/model/Folder.kt:24
  • `Folder.localId` is a raw `Long` — give it a strongly-typed id: a dedicated single-field type wrapping the `Long`, in whatever form your language spells that. — shared/src/commonMain/kotlin/com/sakethh/linkora/domain/model/Folder.kt:25
  • `Folder.remoteId` is a raw `Long` — give it a strongly-typed id: a dedicated single-field type wrapping the `Long`, in whatever form your language spells that. — shared/src/commonMain/kotlin/com/sakethh/linkora/domain/model/Folder.kt:26
  • `RefreshLink.refreshedLinkId` is a raw `Long` — give it a strongly-typed id: a dedicated single-field type wrapping the `Long`, in whatever form your language spells that. — shared/src/commonMain/kotlin/com/sakethh/linkora/domain/model/RefreshLink.kt:8
  • `Link.localId` is a raw `Long` — give it a strongly-typed id: a dedicated single-field type wrapping the `Long`, in whatever form your language spells that. — shared/src/commonMain/kotlin/com/sakethh/linkora/domain/model/link/Link.kt:27
  • `Link.remoteId` is a raw `Long` — give it a strongly-typed id: a dedicated single-field type wrapping the `Long`, in whatever form your language spells that. — shared/src/commonMain/kotlin/com/sakethh/linkora/domain/model/link/Link.kt:28
  • `Panel.localId` is a raw `Long` — give it a strongly-typed id: a dedicated single-field type wrapping the `Long`, in whatever form your language spells that. — shared/src/commonMain/kotlin/com/sakethh/linkora/domain/model/panel/Panel.kt:11
  • `Panel.remoteId` is a raw `Long` — give it a strongly-typed id: a dedicated single-field type wrapping the `Long`, in whatever form your language spells that. — shared/src/commonMain/kotlin/com/sakethh/linkora/domain/model/panel/Panel.kt:13
  • `PanelFolder.localId` is a raw `Long` — give it a strongly-typed id: a dedicated single-field type wrapping the `Long`, in whatever form your language spells that. — shared/src/commonMain/kotlin/com/sakethh/linkora/domain/model/panel/PanelFolder.kt:11
  • `PanelFolder.remoteId` is a raw `Long` — give it a strongly-typed id: a dedicated single-field type wrapping the `Long`, in whatever form your language spells that. — shared/src/commonMain/kotlin/com/sakethh/linkora/domain/model/panel/PanelFolder.kt:12
  • `PanelFolder.folderId` is a raw `Long` — give it a strongly-typed id: a dedicated single-field type wrapping the `Long`, in whatever form your language spells that. — shared/src/commonMain/kotlin/com/sakethh/linkora/domain/model/panel/PanelFolder.kt:13
  • `PanelFolder.connectedPanelId` is a raw `Long` — give it a strongly-typed id: a dedicated single-field type wrapping the `Long`, in whatever form your language spells that. — shared/src/commonMain/kotlin/com/sakethh/linkora/domain/model/panel/PanelFolder.kt:16
  • `Tag.localId` is a raw `Long` — give it a strongly-typed id: a dedicated single-field type wrapping the `Long`, in whatever form your language spells that. — shared/src/commonMain/kotlin/com/sakethh/linkora/domain/model/tag/Tag.kt:20
  • `Tag.remoteId` is a raw `Long` — give it a strongly-typed id: a dedicated single-field type wrapping the `Long`, in whatever form your language spells that. — shared/src/commonMain/kotlin/com/sakethh/linkora/domain/model/tag/Tag.kt:21
  • `LinkTag.remoteId` is a raw `Long` — give it a strongly-typed id: a dedicated single-field type wrapping the `Long`, in whatever form your language spells that. — shared/src/commonMain/kotlin/com/sakethh/linkora/domain/model/tag/Tag.kt:47
  • `LinkTag.linkId` is a raw `Long` — give it a strongly-typed id: a dedicated single-field type wrapping the `Long`, in whatever form your language spells that. — shared/src/commonMain/kotlin/com/sakethh/linkora/domain/model/tag/Tag.kt:48
  • `LinkTag.tagId` is a raw `Long` — give it a strongly-typed id: a dedicated single-field type wrapping the `Long`, in whatever form your language spells that. — shared/src/commonMain/kotlin/com/sakethh/linkora/domain/model/tag/Tag.kt:49

What to do

  • Adopt strongly-typed ids across the domain — finish the migration or document the boundary; primitive ids invite transposed-argument bugs.
DM4 · Rich vs anemic model3.0 / 10Weak✓ 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.

  • `CaptureTrack` is an aggregate/entity with 2 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — shared/src/commonMain/kotlin/com/sakethh/linkora/domain/model/CaptureTrack.kt:7
  • `Folder` is an aggregate/entity with 8 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — shared/src/commonMain/kotlin/com/sakethh/linkora/domain/model/Folder.kt:21
  • `PendingSyncQueue` is an aggregate/entity with 3 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — shared/src/commonMain/kotlin/com/sakethh/linkora/domain/model/PendingSyncQueue.kt:7
  • `RefreshLink` is an aggregate/entity with 1 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — shared/src/commonMain/kotlin/com/sakethh/linkora/domain/model/RefreshLink.kt:7
  • `Snapshot` is an aggregate/entity with 2 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — shared/src/commonMain/kotlin/com/sakethh/linkora/domain/model/Snapshot.kt:7
  • `Link` is an aggregate/entity with 14 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — shared/src/commonMain/kotlin/com/sakethh/linkora/domain/model/link/Link.kt:25
  • `LocalizedLanguage` is an aggregate/entity with 4 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — shared/src/commonMain/kotlin/com/sakethh/linkora/domain/model/localization/LocalizedLanguage.kt:9
  • `LocalizedString` is an aggregate/entity with 4 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — shared/src/commonMain/kotlin/com/sakethh/linkora/domain/model/localization/LocalizedString.kt:7
  • `Panel` is an aggregate/entity with 4 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — shared/src/commonMain/kotlin/com/sakethh/linkora/domain/model/panel/Panel.kt:10
  • `PanelFolder` is an aggregate/entity with 7 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — shared/src/commonMain/kotlin/com/sakethh/linkora/domain/model/panel/PanelFolder.kt:10
  • `Tag` is an aggregate/entity with 4 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — shared/src/commonMain/kotlin/com/sakethh/linkora/domain/model/tag/Tag.kt:19
  • `LinkTag` is an aggregate/entity with 4 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — shared/src/commonMain/kotlin/com/sakethh/linkora/domain/model/tag/Tag.kt:46
  • `WebCaptureMetadata` is an aggregate/entity with 2 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — web-capture/src/commonMain/kotlin/com/sakethh/linkora/WebCaptureDatabase.kt:13

What to do

  • Move business rules onto the aggregates/entities they govern so invariants are enforced at the source, not in anemic services.
DM5 · Encapsulated state5.2 / 10Adequate✓ Tool-verified

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.

  • `Folder` exposes publicly writable state (path). — shared/src/commonMain/kotlin/com/sakethh/linkora/domain/model/Folder.kt:21
  • `Link` exposes publicly writable state (path). — shared/src/commonMain/kotlin/com/sakethh/linkora/domain/model/link/Link.kt:25

What to do

  • 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).
DM6 · Domain ↔ infrastructure boundary10.0 / 10Exemplary✓ Tool-verified

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.

DM9 · Scattered domain decisions10.0 / 10Exemplary✓ Tool-verified

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.

M1 · Documentation (README)8.0 / 10Strong✓ Tool-verified

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

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

M2 · Architecture documentation2.0 / 10Weak✓ Tool-verified

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

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

  • No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.

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.
M3 · Folder & project structure10.0 / 10Exemplary✓ Tool-verified

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

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

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

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

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

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

Readiness · Readiness — Whether an automated pipeline builds and tests every change.

Method: Filesystem scan: CI workflow files (.github/workflows, .gitlab-ci.yml, etc.) for build and test stages. Exhaustive, deterministic.

P2 · Observability0.0 / 10Critical✓ Tool-verified

Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.

Method: Filesystem/Roslyn scan: structured-logging frameworks (Serilog, NLog), OpenTelemetry, and health-check endpoint patterns. Exhaustive, deterministic.

  • No logging or diagnostics emission found. This repository ships a binary its users launch rather than a service you operate, so there is no operator to page — but when a run fails on a user's machine, neither they nor you have anything to read.

What to do

  • Write a diagnostic trail the user can hand back with a bug report: a log file under the platform's per-user data directory, switchable with a `--verbose`/`--debug` flag. Start with the error paths that emit nothing — a discarded error is the failure the user cannot describe and you cannot reproduce.
P3 · Security & performance tooling0.0 / 10Critical✓ Tool-verified

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

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

  • No static application security testing detected. For this repository's stack, add spotbugs with find-sec-bugs (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 2 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.
  • `webApp/worker/package.json` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — webApp/worker/package.json:5

What to do

  • Add a SAST step to CI running what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
  • Enable Dependabot/Renovate or a dependency-review gate.
  • Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback7.0 / 10Strong✓ Tool-verified

Readiness · Readiness — Whether releases are automated and safely reversible (probes, rolling updates, approval gates) — from manifests/pipeline files, not the live environment.

Method: Filesystem scan: deployment manifests/IaC (K8s YAML, Helm, Terraform) for rolling updates, probes, approval gates, migration hooks. Exhaustive, deterministic.

P6 · Release Hygiene5.0 / 10Adequate✓ Tool-verified

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

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

  • No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)

What to do

  • Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
PF3 · Async & latency hygiene10.0 / 10Exemplary✓ Tool-verified

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

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

X1 · Async correctness10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether the code avoids sync-over-async (deadlock-prone blocking on tasks) and async void.

Method: Roslyn syntax scan: async methods scanned for .Wait()/.GetAwaiter().GetResult() and async-void outside event handlers. Deterministic, hard fact per invocation.

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

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

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

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

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

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

X18 · Disposal-pattern correctness10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a type's disposal matches what it OWNS — releasing what it created, leaving alone what it was handed, and not declaring a finalizer for state that has nothing unmanaged to finalize.

Method: Roslyn syntax + semantics: every assignment to a disposable field is read to decide whether the type CREATED the value or was handed it, and the type's disposal is checked against that answer — an injected interface it disposes, a value it constructed and never releases, a finalizer on a type holding nothing unmanaged, and a disposable local whose every reference is a plain member read. A value handed to a container that disposes its contents (a parent control's `Controls` collection, a component `IContainer`) is released by that container and is not reported; generated code is out of population. On a repository with no .NET source the same ownership questions are read in JavaScript/TypeScript off the engine’s own token stream (test, vendored, generated and minified paths not): a class declaring `dispose()`, `[Symbol.dispose]()` or `[Symbol.asyncDispose]()` that disposes a field it was handed through a constructor parameter typed as a repository interface or resolved by a dependency-injection container; that assigns a field only ever from `new X(…)` of a disposable class and neither releases it anywhere in the class nor names it in its disposal member or a method that member calls, nor hands it to anything else; and a `const`/`let` local built from literals only whose every reference opens a statement operating on a non-release member of it. A class is disposable when every repository declaration of its name declares or inherits a disposal member, or when it is a documented library disposable (`vscode` EventEmitter, CancellationTokenSource and Disposable; three.js geometries, materials, textures, render targets, renderers, controls and composers). The finalizer arm has no JavaScript counterpart: a class cannot declare one. Dart is read for the owned-and-never-released arm: a Flutter `State` (or a class declaring `dispose()`/`close()`) whose library-private field is written only with direct creations of a framework controller, `FocusNode`, `StreamController` or periodic `Timer` (or a `.listen(…)` into a field declared `StreamSubscription`), which nothing in the class or its library releases (`dispose`/`close`/`cancel`) and which is never handed on except as a named argument. Ruby is read for the owned-and-never-released arm and the abandoned-local arm: a class declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose instance variable is written only with a blockless core descriptor creation (`File.open`/`new`, `Tempfile`, `Dir.open`, `IO.popen`, the `socket` and `openssl` socket classes) that no method of the class closes and that is never handed on (passed, returned, stored, exposed by `attr_reader`, delegated) — a class whose superclass or mixin lies outside the repository is not judged — and a blockless creation read through and dropped (`File.open(path).read`) or held in a local that is never closed, returned, passed or stored (a `&:read` block-pass, an `autoclose: false` borrow and a `fileno` hand-over are not abandonment). PHP is read for the same two arms: a class (not a trait, and not one using a trait) declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose `private` property (or a `final` class's `protected` one) is written only with a direct core `fopen`, `tmpfile`, `popen`, `proc_open`, `fsockopen`, `stream_socket_client`/`server` or `opendir` that nothing in the class closes (`fclose`, `pclose`, `closedir`, `unset`, a reset to `null`) and that is never handed on, and a handle held in a function's local, or read through as the argument of a reader, that is never closed, returned, passed, captured or stored; a `php://` stream, `curl_init`, `SplFileObject`, `PDO` and a function the repository declares under the core name are not read. Deterministic, provable per finding. Advisory.

X2 · Cancellation propagation10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether suspend functions that make a cancellable request accept or pass on the coroutine's cancellation (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.

X21 · Side-effecting pattern guard10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a `when` guard is free of side effects — a guard that increments a counter or assigns while deciding whether its arm matches applies that change during PATTERN MATCHING, on an arm that may not be selected, and skips it entirely when a short-circuit to its left answers first.

Method: Roslyn syntax: `when` guards on case labels and switch-expression arms, read for a mutation (`++`/`--`/assignment) sitting in a position the guard's own `&&`/`||`/`??`/`?:`/`?.` can skip. Deterministic, provable per finding. Advisory.

X25 · Inert configuration knob10.0 / 10Exemplary○ Nothing flagged

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

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

X27 · Collection changed while being enumerated10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a `for (x in c)` or `c.forEach { … }` leaves the collection it is walking alone — a `mutableListOf`/`ArrayList`, `mutableMapOf`/`HashMap` or `mutableSetOf`/`HashSet` is a `java.util` collection on the JVM and is walked by its own fail-fast iterator, so a body that adds to or removes from the very collection the loop is walking makes the next step throw `ConcurrentModificationException` and the remaining elements are never seen.

Method: Roslyn syntax + semantics: `foreach` statements whose body calls a structural mutator (`Add`/`Remove`/`Clear`/`Insert`/…) on the very expression the loop is enumerating. Two arms. ARM A — the source is a concrete fragile BCL collection, or a live `Keys`/`Values` view over one, and the mutator resolves to that same collection's own member; concurrent and immutable collections and arrays are outside the population by construction, since their enumerators survive a structural change. ARM B — the source is an argument-less accessor CALL on a receiver whose body is in source: the accessor must return a stored field VERBATIM and a sibling member must structurally change that same field, both read off the implementations rather than from the members' names. A mutation the loop provably exits immediately after (`break`/`return`/`throw`/`goto`), or one written inside a nested loop or a lambda, is counted and never reported. Deterministic, provable per finding. Advisory.

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

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

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

  • `catch (_: Exception)` 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. (×9) — shared/src/desktopMain/kotlin/com/sakethh/linkora/AllLinksWebCaptureService.kt:65, shared/src/desktopMain/kotlin/com/sakethh/linkora/AllLinksWebCaptureService.kt:100, shared/src/commonMain/kotlin/com/sakethh/linkora/ui/Paginator.kt:147, …
  • `catch (_: Error)` 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. (×3) — shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/settings/section/data/DataSettingsScreen.kt:1010, shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/settings/section/data/snapshots/SnapshotsScreen.kt:297, shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/settings/section/data/capture/WebPageCaptureScreen.kt:544
  • 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. — shared/src/commonMain/kotlin/com/sakethh/linkora/data/remote/repository/sync/RemoteSyncRepoImpl.kt:229

What to do

  • Swallowed exception (caught, then discarded)
X5 · Nullable reference types9.8 / 10Exemplary✓ Tool-verified

Other · Code Health — Whether Kotlin's null safety is not undermined by not-null assertions — `String` cannot hold null and `String?` must be checked before use in every Kotlin module, and each `!!` is a run-time `NullPointerException` the author has told the compiler cannot happen.

Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.

Reference — by lens

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

LensScoreRatingImpact
Code Health74.1StrongSolid.
Architecture83.4StrongSolid.
Maturity68.5Adequate — gated by M2Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Readiness34.4Weak — gated by P2, P3Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security69.0Adequate — gated by D36Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Domain Modelling46.5Adequate — gated by DM2, DM4Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Performance100.0ExemplaryStrongest area.
Unscored — 2 check(s) recorded observations but carry no score

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

  • P12 CI test-gate honesty — 1 observation(s) recorded · Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
  • X10 Duplicated predicate — 9 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 1 control(s) we could not find positive evidence for

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

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

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

  • AC1 Text alternatives — Frontend below the scale floor (18 DOM element(s) < 25) — too little surface to assess accessibility.
  • AC2 Forms & labels — Frontend below the scale floor (18 DOM element(s) < 25) — too little surface to assess accessibility.
  • AC3 Page structure — Frontend below the scale floor (18 DOM element(s) < 25) — too little surface to assess accessibility.
  • AC4 Keyboard semantics — Frontend below the scale floor (18 DOM element(s) < 25) — too little surface to assess accessibility.
  • AC5 ARIA correctness — Frontend below the scale floor (18 DOM element(s) < 25) — too little surface to assess accessibility.
  • AC6 Visual & motion safety — Frontend below the scale floor (18 DOM element(s) < 25) — too little surface to assess accessibility.
  • AX1 Captive dependencies — 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
  • AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No class in this Kotlin code is a Spring, JSR-330 or CDI singleton bean. TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
  • AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • AX7 Slice cohesion — not applicable — not a vertical-slice architecture
  • AX8 Test isolation — no test/production split to check
  • AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
  • AXB1 Runtime evidence locked — no reproducible boot — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Room, JPA or MongoDB entity, an Exposed or Ktorm table, or in a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (Room, Exposed, SQLDelight, Realm, JPA, JDBC, MongoDB, Firebase, …) imported either, so this repository keeps no data at rest for these controls to protect.
  • 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.
  • C3 Audit Trail — No personal data detected in a persisted data model — no PII-named column (email, first_name, date_of_birth, phone_number, …) or stored credential on a Room, JPA or MongoDB entity, an Exposed or Ktorm table, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (Room, Exposed, SQLDelight, Realm, JPA, JDBC, MongoDB, Firebase, …) imported either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a store configured outside this repository, for instance), the trail belongs to wherever that data is stored.
  • C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Room, JPA or MongoDB entity, an Exposed or Ktorm table, or in a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (Room, Exposed, SQLDelight, Realm, JPA, JDBC, MongoDB, Firebase, …) imported either, so this repository keeps no personal data whose lifetime a retention limit would bound.
  • C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Room, JPA or MongoDB entity, an Exposed or Ktorm table, or in a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (Room, Exposed, SQLDelight, Realm, JPA, JDBC, MongoDB, Firebase, …) imported either, so this repository keeps no personal data for a data subject to erase, export or consent over.
  • D10 Test Quality — ~5218 lines of test source are present (.kt) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
  • D11 Test Reliability — Test reliability not included — the .kt suite was found but not re-run
  • D12 Dependency Hygiene — Dependency currency not established — api.foojay.io did not answer
  • D16 Bus Factor — single-maintainer repository — bus factor is not applicable
  • D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
  • D21 Naming Consistency — Naming consistency does not read html yet; 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. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
  • D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only; comments in this repository's .kt source were not judged.
  • D25 ADR Conformance — no ADRs to check
  • D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
  • D32 Data Compliance (PII/GDPR) — 22 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
  • D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
  • 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 included — suite not readable by the collector
  • DM1 Aggregate boundaries — no aggregates detected — aggregate-boundary check not applicable
  • 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
  • DM7 Repository granularity — no repository abstraction detected (e.g. uses a document session)
  • 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, Scala, Rust and Java, 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
  • P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JVM, JavaScript/TypeScript source, so there is no service whose uptime a failing dependency could take down
  • P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
  • P9 Domain vs controller coverage — coverage 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 `@Benchmark` in a Java, Kotlin or Scala file importing JMH or kotlinx-benchmark, Jetpack Benchmark's `measureRepeated` in a file importing androidx.benchmark, or JMH/kotlinx-benchmark/androidx.benchmark in a pom.xml, Gradle or sbt build, 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.
  • 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.
  • X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • 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
  • X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X20 Mistyped argument guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • 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 — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X29 Per-element action decided by a fixed element — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • 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 — This check asks whether log calls keep a message's values apart from its text, which needs a logger that can carry them as fields. This repository's Kotlin was read, and it logs through none that an assembled message defeats: Android's `Log` and Timber, java.util.logging and log4j-api-kotlin take one finished message (as log4net does in C#), or it makes no call through a named logger at all. Calls made through SLF4J, log4j 2 or kotlin-logging (`LoggerFactory.getLogger`, `KotlinLogging.logger {}`) would be judged.
  • X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.

Appendix A — Findings (grouped)

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

Critical — 42 finding(s)
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • + 9 more in this group — see findings.md.
D35 · Change Coupling · Boundary-crossing change coupling · ×4
  • Boundary-crossing change coupling: LinkoraApp.kt ↔ ViewModelModule.kt androidApp/src/main/kotlin/com/sakethh/linkora/LinkoraApp.kt:1 — `androidApp/src/main/kotlin/com/sakethh/linkora/LinkoraApp.kt` (context androidApp) and `shared/src/commonMain/kotlin/com/sakethh/linkora/di/ViewModelModule.kt` (context shared) sit in DIFFERENT parts of the tree yet change together 75% of the time (9 of the 12 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 9 shared commits counted here, the most recent 3 are `c052a73e` feat: add AndroidTV as a platform (at that commit the files were still `composeApp/src/androidMain/kotlin/com/sakethh/linkora/LinkoraApp.kt` and `composeApp/src/commonMain/kotlin/com/sakethh/linkora/di/ViewModelModule.kt`); `a49fb20d` fix(android-web-capture): gain ownership of the external database aft… (at that commit the files were still `composeApp/src/androidMain/kotlin/com/sakethh/linkora/LinkoraApp.kt` and `composeApp/src/commonMain/kotlin/com/sakethh/linkora/di/ViewModelModule.kt`); `1f174d25` feat(web-capture): implement bulk web-capture support for all the loc… (at that commit the files were still `composeApp/src/androidMain/kotlin/com/sakethh/linkora/LinkoraApp.kt` and `composeApp/src/commonMain/kotlin/com/sakethh/linkora/di/ViewModelModule.kt`) — run `git show` on any of them.
  • Boundary-crossing change coupling: LinkoraApp.kt ↔ SnapshotWorker.kt androidApp/src/main/kotlin/com/sakethh/linkora/LinkoraApp.kt:1 — `androidApp/src/main/kotlin/com/sakethh/linkora/LinkoraApp.kt` (context androidApp) and `shared/src/androidMain/kotlin/com/sakethh/linkora/worker/SnapshotWorker.kt` (context shared) sit in DIFFERENT parts of the tree yet change together 64% of the time (7 of the 11 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `1d875fb4` chore: replace hardcoded strings for localization (at that commit the files were still `composeApp/src/androidMain/kotlin/com/sakethh/linkora/LinkoraApp.kt` and `composeApp/src/androidMain/kotlin/com/sakethh/linkora/worker/SnapshotWorker.kt`); `7d76cd8f` feat(android-tv): support exports, snapshots, and web-captures operat… (at that commit the files were still `composeApp/src/androidMain/kotlin/com/sakethh/linkora/LinkoraApp.kt` and `composeApp/src/androidMain/kotlin/com/sakethh/linkora/worker/SnapshotWorker.kt`); `3f75d064` refactor: use companion object for LinkoraSDK provider (at that commit the files were still `composeApp/src/androidMain/kotlin/com/sakethh/linkora/LinkoraApp.kt` and `composeApp/src/androidMain/kotlin/com/sakethh/linkora/worker/SnapshotWorker.kt`) — run `git show` on any of them.
  • Boundary-crossing change coupling: MainActivity.kt ↔ ThemeSettingsScreen.kt androidApp/src/main/kotlin/com/sakethh/linkora/MainActivity.kt:1 — `androidApp/src/main/kotlin/com/sakethh/linkora/MainActivity.kt` (context androidApp) and `shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/settings/section/ThemeSettingsScreen.kt` (context shared) sit in DIFFERENT parts of the tree yet change together 58% of the time (7 of the 12 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `c052a73e` feat: add AndroidTV as a platform (at that commit the files were still `composeApp/src/androidMain/kotlin/com/sakethh/linkora/MainActivity.kt` and `composeApp/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/settings/section/ThemeSettingsScreen.kt`); `b340eca2` chore: rename a few preferences names (at that commit the files were still `composeApp/src/androidMain/kotlin/com/sakethh/linkora/MainActivity.kt` and `composeApp/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/settings/section/ThemeSettingsScreen.kt`); `ddf99a88` refactor codebase to use manual DI (at that commit the files were still `composeApp/src/androidMain/kotlin/com/sakethh/linkora/MainActivity.kt` and `composeApp/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/settings/section/ThemeSettingsScreen.kt`) — run `git show` on any of them.
  • Boundary-crossing change coupling: ShareToSaveActivity.kt ↔ ViewModelModule.kt androidApp/src/main/kotlin/com/sakethh/linkora/ShareToSaveActivity.kt:1 — `androidApp/src/main/kotlin/com/sakethh/linkora/ShareToSaveActivity.kt` (context androidApp) and `shared/src/commonMain/kotlin/com/sakethh/linkora/di/ViewModelModule.kt` (context shared) sit in DIFFERENT parts of the tree yet change together 50% of the time (6 of the 12 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `c052a73e` feat: add AndroidTV as a platform (at that commit the files were still `composeApp/src/androidMain/kotlin/com/sakethh/linkora/ShareToSaveActivity.kt` and `composeApp/src/commonMain/kotlin/com/sakethh/linkora/di/ViewModelModule.kt`); `ca943768` feat(android): add auto-save support for links shared from other apps… (at that commit the files were still `composeApp/src/androidMain/kotlin/com/sakethh/linkora/ShareToSaveActivity.kt` and `composeApp/src/commonMain/kotlin/com/sakethh/linkora/di/ViewModelModule.kt`); `3f75d064` refactor: use companion object for LinkoraSDK provider (at that commit the files were still `composeApp/src/androidMain/kotlin/com/sakethh/linkora/IntentActivity.kt` and `composeApp/src/commonMain/kotlin/com/sakethh/linkora/di/ViewModelModule.kt`) — run `git show` on any of them.
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D30 · Dependency Vulnerabilities · High CVE · ×1
  • REDACTED
Serious — 325 finding(s)
D3 · God Classes · MethodTooLong · ×44
  • MethodTooLong: DataSettingsScreenKt.DataSettingsScreen shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/settings/section/data/DataSettingsScreen.kt:125 — MethodTooLong — DataSettingsScreen runs 782 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 682 over it, 7.82× 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: AddANewLinkDialogKt.BottomPartOfAddANewLinkDialogBox shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/link/AddANewLinkDialog.kt:661 — MethodTooLong — BottomPartOfAddANewLinkDialogBox runs 716 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 616 over it, 7.16× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: AppKt.App shared/src/commonMain/kotlin/com/sakethh/linkora/ui/App.kt:134 — MethodTooLong — App runs 644 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 544 over it, 6.44× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: LocalDataUpdateService.updateLocalDBAccordingToEvent shared/src/commonMain/kotlin/com/sakethh/linkora/data/remote/repository/sync/LocalDataUpdateService.kt:76 — MethodTooLong — updateLocalDBAccordingToEvent runs 625 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 525 over it, 6.25× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: PendingQueueService.pushPendingSyncQueueToServer shared/src/commonMain/kotlin/com/sakethh/linkora/data/remote/repository/sync/PendingQueueService.kt:80 — MethodTooLong — pushPendingSyncQueueToServer runs 549 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 449 over it, 5.49× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: CollectionsScreenKt.CollectionsScreen shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/collections/CollectionsScreen.kt:132 — MethodTooLong — CollectionsScreen runs 518 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 418 over it, 5.18× 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: CollectionLayoutManagerKt.CollectionLayoutManager shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/CollectionLayoutManager.kt:73 — MethodTooLong — CollectionLayoutManager runs 456 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 356 over it, 4.56× 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: WebPageCaptureScreenKt.WebPageCaptureScreen shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/settings/section/data/capture/WebPageCaptureScreen.kt:72 — MethodTooLong — WebPageCaptureScreen runs 417 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 317 over it, 4.17× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: CollectionDetailPaneKt.CollectionDetailPane shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/collections/CollectionDetailPane.kt:113 — MethodTooLong — CollectionDetailPane runs 377 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 277 over it, 3.77× 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: ServerSetupScreenKt.ServerSetupScreen shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/settings/section/data/sync/ServerSetupScreen.kt:77 — MethodTooLong — ServerSetupScreen runs 288 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 188 over it, 2.88× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: AboutScreenKt.AboutScreen shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/settings/section/about/AboutScreen.kt:60 — MethodTooLong — AboutScreen runs 287 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 187 over it, 2.87× 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: GeneralSettingsScreenKt.GeneralSettingsScreen shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/settings/section/GeneralSettingsScreen.kt:86 — MethodTooLong — GeneralSettingsScreen runs 272 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 172 over it, 2.72× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: GridViewLinkComponentKt.GridViewLinkComponent shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/link/GridViewLinkComponent.kt:67 — MethodTooLong — GridViewLinkComponent runs 268 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 168 over it, 2.68× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: BottomNavOnSelectionKt.BottomNavOnSelection shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/nav/BottomNavOnSelection.kt:72 — MethodTooLong — BottomNavOnSelection runs 267 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 167 over it, 2.67× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: HomeScreenKt.HomeScreen shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/home/HomeScreen.kt:83 — MethodTooLong — HomeScreen runs 247 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 147 over it, 2.47× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: LinkMenuBtmSheetKt.LinkMenuBtmSheet shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/link/menu/LinkMenuBtmSheet.kt:79 — MethodTooLong — LinkMenuBtmSheet runs 243 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 143 over it, 2.43× 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: SnapshotsScreenKt.SnapshotsScreen shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/settings/section/data/snapshots/SnapshotsScreen.kt:70 — MethodTooLong — SnapshotsScreen runs 242 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 142 over it, 2.42× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: LanguageSettingsScreenKt.LanguageSettingsScreen shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/settings/section/LanguageSettingsScreen.kt:69 — MethodTooLong — LanguageSettingsScreen runs 229 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 129 over it, 2.29× 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: ListViewLinkComponentKt.ListViewLinkComponent shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/link/ListViewLinkComponent.kt:79 — MethodTooLong — ListViewLinkComponent runs 226 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 126 over it, 2.26× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: LayoutSettingsScreenKt.LayoutSettingsScreen shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/settings/section/LayoutSettingsScreen.kt:58 — MethodTooLong — LayoutSettingsScreen runs 214 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 114 over it, 2.14× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: SearchScreenKt.SearchScreen shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/search/SearchScreen.kt:72 — MethodTooLong — SearchScreen runs 208 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 108 over it, 2.08× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: AddANewLinkDialogKt.TopPartOfAddANewLinkDialogBox shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/link/AddANewLinkDialog.kt:387 — MethodTooLong — TopPartOfAddANewLinkDialogBox runs 196 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 96 over it, 1.96× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: OnboardingSlidesScreenKt.Slide3 shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/onboarding/OnboardingSlidesScreen.kt:441 — MethodTooLong — Slide3 runs 190 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 90 over it, 1.90× 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: SpecificPanelManagerScreenKt.SpecificPanelManagerScreen shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/home/panels/SpecificPanelManagerScreen.kt:62 — MethodTooLong — SpecificPanelManagerScreen runs 172 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 72 over it, 1.72× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: AddANewLinkDialogKt.AddANewLinkDialogBox shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/link/AddANewLinkDialog.kt:171 — MethodTooLong — AddANewLinkDialogBox runs 162 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 62 over it, 1.62× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • + 19 more in this group — see findings.md.
D15 · Churn × Complexity Hotspots · Hotspot · ×22
  • Hotspot: shared/src/commonMain/kotlin/com/sakethh/linkora/data/remote/repository/sync/LocalDataUpdateService.kt shared/src/commonMain/kotlin/com/sakethh/linkora/data/remote/repository/sync/LocalDataUpdateService.kt:76 — shared/src/commonMain/kotlin/com/sakethh/linkora/data/remote/repository/sync/LocalDataUpdateService.kt changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 109 in LocalDataUpdateService.updateLocalDBAccordingToEvent at line 76. 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-07..2026-11-05, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-07 11:44:56 +05:30' --until='2026-11-05 11:44:56 +05:30' --full-history --no-merges -- shared/src/commonMain/kotlin/com/sakethh/linkora/data/remote/repository/sync/LocalDataUpdateService.kt`: 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: shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/settings/section/data/DataSettingsScreen.kt shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/settings/section/data/DataSettingsScreen.kt:125 — shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/settings/section/data/DataSettingsScreen.kt changed 10 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 34 in DataSettingsScreenKt.DataSettingsScreen at line 125. 1 of those changes was a fix/bug commit, and the other 9 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-07..2026-11-05, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-07 11:44:56 +05:30' --until='2026-11-05 11:44:56 +05:30' --full-history --no-merges -- shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/settings/section/data/DataSettingsScreen.kt`: 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: shared/src/commonMain/kotlin/com/sakethh/linkora/ui/App.kt shared/src/commonMain/kotlin/com/sakethh/linkora/ui/App.kt:134 — shared/src/commonMain/kotlin/com/sakethh/linkora/ui/App.kt changed 10 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 30 in AppKt.App at line 134. 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-07..2026-11-05, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-07 11:44:56 +05:30' --until='2026-11-05 11:44:56 +05:30' --full-history --no-merges -- shared/src/commonMain/kotlin/com/sakethh/linkora/ui/App.kt`: 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: shared/src/commonMain/kotlin/com/sakethh/linkora/data/local/repository/LocalLinksRepoImpl.kt shared/src/commonMain/kotlin/com/sakethh/linkora/data/local/repository/LocalLinksRepoImpl.kt:84 — shared/src/commonMain/kotlin/com/sakethh/linkora/data/local/repository/LocalLinksRepoImpl.kt changed 10 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 29 in LocalLinksRepoImpl.addANewLink at line 84. 1 of those changes was a fix/bug commit, and the other 9 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-07..2026-11-05, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-07 11:44:56 +05:30' --until='2026-11-05 11:44:56 +05:30' --full-history --no-merges -- shared/src/commonMain/kotlin/com/sakethh/linkora/data/local/repository/LocalLinksRepoImpl.kt`: 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: shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/nav/BottomNavOnSelection.kt shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/nav/BottomNavOnSelection.kt:72 — shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/nav/BottomNavOnSelection.kt changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 34 in BottomNavOnSelectionKt.BottomNavOnSelection at line 72. 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-07..2026-11-05, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-07 11:44:56 +05:30' --until='2026-11-05 11:44:56 +05:30' --full-history --no-merges -- shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/nav/BottomNavOnSelection.kt`: 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: shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/collections/CollectionsScreen.kt shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/collections/CollectionsScreen.kt:132 — shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/collections/CollectionsScreen.kt changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 39 in CollectionsScreenKt.CollectionsScreen at line 132. 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-07..2026-11-05, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-07 11:44:56 +05:30' --until='2026-11-05 11:44:56 +05:30' --full-history --no-merges -- shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/collections/CollectionsScreen.kt`: 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: shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/link/menu/LinkMenuBtmSheet.kt shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/link/menu/LinkMenuBtmSheet.kt:79 — shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/link/menu/LinkMenuBtmSheet.kt changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 27 in LinkMenuBtmSheetKt.LinkMenuBtmSheet at line 79. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-07..2026-11-05, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-07 11:44:56 +05:30' --until='2026-11-05 11:44:56 +05:30' --full-history --no-merges -- shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/link/menu/LinkMenuBtmSheet.kt`: 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: shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/settings/section/data/capture/WebPageCaptureScreen.kt shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/settings/section/data/capture/WebPageCaptureScreen.kt:72 — shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/settings/section/data/capture/WebPageCaptureScreen.kt changed 8 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 22 in WebPageCaptureScreenKt.WebPageCaptureScreen at line 72. 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-07..2026-11-05, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-07 11:44:56 +05:30' --until='2026-11-05 11:44:56 +05:30' --full-history --no-merges -- shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/settings/section/data/capture/WebPageCaptureScreen.kt`: 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: shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/link/AddANewLinkDialog.kt shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/link/AddANewLinkDialog.kt:661 — shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/link/AddANewLinkDialog.kt changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 43 in AddANewLinkDialogKt.BottomPartOfAddANewLinkDialogBox at line 661. 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-07..2026-11-05, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-07 11:44:56 +05:30' --until='2026-11-05 11:44:56 +05:30' --full-history --no-merges -- shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/link/AddANewLinkDialog.kt`: 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: shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/settings/section/data/snapshots/SnapshotsScreen.kt shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/settings/section/data/snapshots/SnapshotsScreen.kt:70 — shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/settings/section/data/snapshots/SnapshotsScreen.kt changed 8 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 18 in SnapshotsScreenKt.SnapshotsScreen at line 70. 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-07..2026-11-05, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-07 11:44:56 +05:30' --until='2026-11-05 11:44:56 +05:30' --full-history --no-merges -- shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/settings/section/data/snapshots/SnapshotsScreen.kt`: 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: shared/src/commonMain/kotlin/com/sakethh/linkora/data/remote/repository/sync/PendingQueueService.kt shared/src/commonMain/kotlin/com/sakethh/linkora/data/remote/repository/sync/PendingQueueService.kt:80 — shared/src/commonMain/kotlin/com/sakethh/linkora/data/remote/repository/sync/PendingQueueService.kt changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 71 in PendingQueueService.pushPendingSyncQueueToServer at line 80. 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-07..2026-11-05, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-07 11:44:56 +05:30' --until='2026-11-05 11:44:56 +05:30' --full-history --no-merges -- shared/src/commonMain/kotlin/com/sakethh/linkora/data/remote/repository/sync/PendingQueueService.kt`: 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: shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/collections/CollectionDetailPane.kt shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/collections/CollectionDetailPane.kt:113 — shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/collections/CollectionDetailPane.kt changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 32 in CollectionDetailPaneKt.CollectionDetailPane at line 113. 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-07..2026-11-05, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-07 11:44:56 +05:30' --until='2026-11-05 11:44:56 +05:30' --full-history --no-merges -- shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/collections/CollectionDetailPane.kt`: 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: shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/nav/DesktopNavigationRail.kt shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/nav/DesktopNavigationRail.kt:48 — shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/nav/DesktopNavigationRail.kt changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 25 in DesktopNavigationRailKt.DesktopNavigationRail at line 48. 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-07..2026-11-05, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-07 11:44:56 +05:30' --until='2026-11-05 11:44:56 +05:30' --full-history --no-merges -- shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/nav/DesktopNavigationRail.kt`: 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: shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/CollectionLayoutManager.kt shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/CollectionLayoutManager.kt:73 — shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/CollectionLayoutManager.kt changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 60 in CollectionLayoutManagerKt.CollectionLayoutManager at line 73. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-07..2026-11-05, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-07 11:44:56 +05:30' --until='2026-11-05 11:44:56 +05:30' --full-history --no-merges -- shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/CollectionLayoutManager.kt`: 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: shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/link/ListViewLinkComponent.kt shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/link/ListViewLinkComponent.kt:79 — shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/link/ListViewLinkComponent.kt changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 28 in ListViewLinkComponentKt.ListViewLinkComponent at line 79. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-07..2026-11-05, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-07 11:44:56 +05:30' --until='2026-11-05 11:44:56 +05:30' --full-history --no-merges -- shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/link/ListViewLinkComponent.kt`: 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: shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/link/GridViewLinkComponent.kt shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/link/GridViewLinkComponent.kt:67 — shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/link/GridViewLinkComponent.kt changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 36 in GridViewLinkComponentKt.GridViewLinkComponent at line 67. 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-07..2026-11-05, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-07 11:44:56 +05:30' --until='2026-11-05 11:44:56 +05:30' --full-history --no-merges -- shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/link/GridViewLinkComponent.kt`: 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: shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/nav/MobileBottomNavBar.kt shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/nav/MobileBottomNavBar.kt:44 — shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/nav/MobileBottomNavBar.kt changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 18 in MobileBottomNavBarKt.MobileBottomNavBar at line 44. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-07..2026-11-05, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-07 11:44:56 +05:30' --until='2026-11-05 11:44:56 +05:30' --full-history --no-merges -- shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/nav/MobileBottomNavBar.kt`: 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: shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/folder/FolderComponent.kt shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/folder/FolderComponent.kt:52 — shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/folder/FolderComponent.kt changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in FolderComponentKt.FolderComponent at line 52. 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-07..2026-11-05, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-07 11:44:56 +05:30' --until='2026-11-05 11:44:56 +05:30' --full-history --no-merges -- shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/folder/FolderComponent.kt`: 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: shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/settings/section/data/sync/ServerSetupScreen.kt shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/settings/section/data/sync/ServerSetupScreen.kt:77 — shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/settings/section/data/sync/ServerSetupScreen.kt changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 20 in ServerSetupScreenKt.ServerSetupScreen at line 77. 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-07..2026-11-05, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-07 11:44:56 +05:30' --until='2026-11-05 11:44:56 +05:30' --full-history --no-merges -- shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/settings/section/data/sync/ServerSetupScreen.kt`: 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: shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/settings/common/composables/SettingComponent.kt shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/settings/common/composables/SettingComponent.kt:41 — shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/settings/common/composables/SettingComponent.kt changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in SettingComponentKt.SettingComponent at line 41. 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-07..2026-11-05, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-07 11:44:56 +05:30' --until='2026-11-05 11:44:56 +05:30' --full-history --no-merges -- shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/settings/common/composables/SettingComponent.kt`: 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: shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/folder/menu/FolderMenuBtmSheet.kt shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/folder/menu/FolderMenuBtmSheet.kt:49 — shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/folder/menu/FolderMenuBtmSheet.kt changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 23 in FolderMenuBtmSheetKt.FolderMenuBtmSheet at line 49. 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-07..2026-11-05, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-07 11:44:56 +05:30' --until='2026-11-05 11:44:56 +05:30' --full-history --no-merges -- shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/folder/menu/FolderMenuBtmSheet.kt`: 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: shared/src/commonMain/kotlin/com/sakethh/linkora/data/ImportDataRepoImpl.kt shared/src/commonMain/kotlin/com/sakethh/linkora/data/ImportDataRepoImpl.kt:259 — shared/src/commonMain/kotlin/com/sakethh/linkora/data/ImportDataRepoImpl.kt changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 17 in ImportDataRepoImpl.importDataFromHTML at line 259. 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-07..2026-11-05, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-07 11:44:56 +05:30' --until='2026-11-05 11:44:56 +05:30' --full-history --no-merges -- shared/src/commonMain/kotlin/com/sakethh/linkora/data/ImportDataRepoImpl.kt`: 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.
D3 · God Classes · FileTooLong · ×13
  • FileTooLong: link/AddANewLinkDialog.kt shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/link/AddANewLinkDialog.kt — FileTooLong — 1382 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 882 over it, 2.76× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: data/DataSettingsScreen.kt shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/settings/section/data/DataSettingsScreen.kt — FileTooLong — 904 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 404 over it, 1.81× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: repository/LocalLinksRepoImpl.kt shared/src/commonMain/kotlin/com/sakethh/linkora/data/local/repository/LocalLinksRepoImpl.kt — FileTooLong — 873 significant lines (blank, comment-only and punctuation-only lines excluded), about 93% of them inside a single declaration: LocalLinksRepoImpl (63-1211). The bar is 500 significant lines; this is 373 over it, 1.75× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
  • FileTooLong: ui/App.kt shared/src/commonMain/kotlin/com/sakethh/linkora/ui/App.kt — FileTooLong — 774 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 274 over it, 1.55× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: sync/LocalDataUpdateService.kt shared/src/commonMain/kotlin/com/sakethh/linkora/data/remote/repository/sync/LocalDataUpdateService.kt — FileTooLong — 692 significant lines (blank, comment-only and punctuation-only lines excluded), about 92% of them inside a single declaration: LocalDataUpdateService (56-1015). The bar is 500 significant lines; this is 192 over it, 1.38× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
  • FileTooLong: collections/CollectionsScreen.kt shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/collections/CollectionsScreen.kt — FileTooLong — 692 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 192 over it, 1.38× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: sync/PendingQueueService.kt shared/src/commonMain/kotlin/com/sakethh/linkora/data/remote/repository/sync/PendingQueueService.kt — FileTooLong — 620 significant lines (blank, comment-only and punctuation-only lines excluded), about 92% of them inside a single declaration: PendingQueueService (54-889). The bar is 500 significant lines; this is 120 over it, 1.24× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
  • FileTooLong: settings/SettingsScreenViewModel.kt shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/settings/SettingsScreenViewModel.kt — FileTooLong — 585 significant lines (blank, comment-only and punctuation-only lines excluded), about 93% of them inside a single declaration: SettingsScreenViewModel (45-751). The bar is 500 significant lines; this is 85 over it, 1.17× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
  • FileTooLong: onboarding/OnboardingSlidesScreen.kt shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/onboarding/OnboardingSlidesScreen.kt — FileTooLong — 574 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 74 over it, 1.15× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: collections/CollectionsScreenVM.kt shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/collections/CollectionsScreenVM.kt — FileTooLong — 556 significant lines (blank, comment-only and punctuation-only lines excluded), about 91% of them inside a single declaration: CollectionsScreenVM (54-820). The bar is 500 significant lines; this is 56 over it, 1.11× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
  • FileTooLong: domain/AppPreferences.kt shared/src/commonMain/kotlin/com/sakethh/linkora/domain/AppPreferences.kt — FileTooLong — 549 significant lines (blank, comment-only and punctuation-only lines excluded), about 97% of them inside a single declaration: AppPreferences (18-801). The bar is 500 significant lines; this is 49 over it, 1.10× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
  • FileTooLong: components/CollectionLayoutManager.kt shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/CollectionLayoutManager.kt — FileTooLong — 526 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 26 over it, 1.05× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: capture/WebPageCaptureScreen.kt shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/settings/section/data/capture/WebPageCaptureScreen.kt — FileTooLong — 525 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 25 over it, 1.05× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
DM4 · Rich vs anemic model · Anemic entity · ×13
  • Anemic entity: CaptureTrack shared/src/commonMain/kotlin/com/sakethh/linkora/domain/model/CaptureTrack.kt:7 — `CaptureTrack` is an aggregate/entity with 2 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
  • Anemic entity: Folder shared/src/commonMain/kotlin/com/sakethh/linkora/domain/model/Folder.kt:21 — `Folder` is an aggregate/entity with 8 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
  • Anemic entity: PendingSyncQueue shared/src/commonMain/kotlin/com/sakethh/linkora/domain/model/PendingSyncQueue.kt:7 — `PendingSyncQueue` is an aggregate/entity with 3 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
  • Anemic entity: RefreshLink shared/src/commonMain/kotlin/com/sakethh/linkora/domain/model/RefreshLink.kt:7 — `RefreshLink` is an aggregate/entity with 1 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
  • Anemic entity: Snapshot shared/src/commonMain/kotlin/com/sakethh/linkora/domain/model/Snapshot.kt:7 — `Snapshot` is an aggregate/entity with 2 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
  • Anemic entity: Link shared/src/commonMain/kotlin/com/sakethh/linkora/domain/model/link/Link.kt:25 — `Link` is an aggregate/entity with 14 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
  • Anemic entity: LocalizedLanguage shared/src/commonMain/kotlin/com/sakethh/linkora/domain/model/localization/LocalizedLanguage.kt:9 — `LocalizedLanguage` is an aggregate/entity with 4 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
  • Anemic entity: LocalizedString shared/src/commonMain/kotlin/com/sakethh/linkora/domain/model/localization/LocalizedString.kt:7 — `LocalizedString` is an aggregate/entity with 4 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
  • Anemic entity: Panel shared/src/commonMain/kotlin/com/sakethh/linkora/domain/model/panel/Panel.kt:10 — `Panel` is an aggregate/entity with 4 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
  • Anemic entity: PanelFolder shared/src/commonMain/kotlin/com/sakethh/linkora/domain/model/panel/PanelFolder.kt:10 — `PanelFolder` is an aggregate/entity with 7 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
  • Anemic entity: Tag shared/src/commonMain/kotlin/com/sakethh/linkora/domain/model/tag/Tag.kt:19 — `Tag` is an aggregate/entity with 4 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
  • Anemic entity: LinkTag shared/src/commonMain/kotlin/com/sakethh/linkora/domain/model/tag/Tag.kt:46 — `LinkTag` is an aggregate/entity with 4 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
  • Anemic entity: WebCaptureMetadata web-capture/src/commonMain/kotlin/com/sakethh/linkora/WebCaptureDatabase.kt:13 — `WebCaptureMetadata` is an aggregate/entity with 2 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
X3 · Exception handling · Swallowed exception (caught, then discarded) · ×12
  • Swallowed exception (caught, then discarded) shared/src/desktopMain/kotlin/com/sakethh/linkora/AllLinksWebCaptureService.kt:65 — `catch (_: Exception)` 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) shared/src/desktopMain/kotlin/com/sakethh/linkora/AllLinksWebCaptureService.kt:100 — `catch (_: Exception)` 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) shared/src/commonMain/kotlin/com/sakethh/linkora/ui/Paginator.kt:147 — `catch (_: Exception)` 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) shared/src/commonMain/kotlin/com/sakethh/linkora/ui/Paginator.kt:157 — `catch (_: Exception)` 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) shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/settings/section/data/DataSettingsScreen.kt:1008 — `catch (_: Exception)` 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) shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/settings/section/data/DataSettingsScreen.kt:1010 — `catch (_: Error)` 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) shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/settings/section/data/snapshots/SnapshotsScreen.kt:295 — `catch (_: Exception)` 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) shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/settings/section/data/snapshots/SnapshotsScreen.kt:297 — `catch (_: Error)` 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) shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/settings/section/data/capture/WebPageCaptureScreen.kt:542 — `catch (_: Exception)` 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) shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/settings/section/data/capture/WebPageCaptureScreen.kt:544 — `catch (_: Error)` 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) shared/src/commonMain/kotlin/com/sakethh/linkora/data/remote/repository/sync/RemoteSyncRepoImpl.kt:206 — `catch (_: Exception)` 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) shared/src/androidMain/kotlin/com/sakethh/linkora/utils/ExtensionFunctions.kt:24 — `catch (_: Exception)` 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.
DM11 · Constructible invalid state · Constructible in an invalid state · ×11
  • Constructible in an invalid state: CaptureTrack shared/src/commonMain/kotlin/com/sakethh/linkora/domain/model/CaptureTrack.kt:7 — `CaptureTrack`'s public constructor takes `capturedLinkId`, `captureWorkerId` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `CaptureTrack` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse.
  • Constructible in an invalid state: Folder shared/src/commonMain/kotlin/com/sakethh/linkora/domain/model/Folder.kt:21 — `Folder`'s public constructor takes `name`, `note` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `Folder` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse.
  • Constructible in an invalid state: PendingSyncQueue shared/src/commonMain/kotlin/com/sakethh/linkora/domain/model/PendingSyncQueue.kt:7 — `PendingSyncQueue`'s public constructor takes `operation`, `payload` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `PendingSyncQueue` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse.
  • Constructible in an invalid state: Snapshot shared/src/commonMain/kotlin/com/sakethh/linkora/domain/model/Snapshot.kt:7 — `Snapshot`'s public constructor takes `content` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `Snapshot` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse.
  • Constructible in an invalid state: Link shared/src/commonMain/kotlin/com/sakethh/linkora/domain/model/link/Link.kt:25 — `Link`'s public constructor takes `title`, `url`, `host`, `imgURL`, … as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `Link` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse.
  • Constructible in an invalid state: LocalizedLanguage shared/src/commonMain/kotlin/com/sakethh/linkora/domain/model/localization/LocalizedLanguage.kt:9 — `LocalizedLanguage`'s public constructor takes `languageCode`, `languageName`, `contributionLink` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `LocalizedLanguage` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse.
  • Constructible in an invalid state: LocalizedString shared/src/commonMain/kotlin/com/sakethh/linkora/domain/model/localization/LocalizedString.kt:7 — `LocalizedString`'s public constructor takes `languageCode`, `stringName`, `stringValue` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `LocalizedString` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse.
  • Constructible in an invalid state: Panel shared/src/commonMain/kotlin/com/sakethh/linkora/domain/model/panel/Panel.kt:10 — `Panel`'s public constructor takes `panelName` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `Panel` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse.
  • Constructible in an invalid state: PanelFolder shared/src/commonMain/kotlin/com/sakethh/linkora/domain/model/panel/PanelFolder.kt:10 — `PanelFolder`'s public constructor takes `folderName` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `PanelFolder` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse.
  • Constructible in an invalid state: Tag shared/src/commonMain/kotlin/com/sakethh/linkora/domain/model/tag/Tag.kt:19 — `Tag`'s public constructor takes `name` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `Tag` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse.
  • Constructible in an invalid state: WebCaptureMetadata web-capture/src/commonMain/kotlin/com/sakethh/linkora/WebCaptureDatabase.kt:13 — `WebCaptureMetadata`'s public constructor takes `link`, `uuid` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `WebCaptureMetadata` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse.
D35 · Change Coupling · Change coupling · ×10
  • Change coupling: Utils.kt ↔ Expected.wasmJs.kt shared/src/androidDesktopMain/kotlin/Utils.kt:1 — `shared/src/androidDesktopMain/kotlin/Utils.kt` and `shared/src/wasmJsMain/kotlin/platform/Expected.wasmJs.kt` change together 87% of the time (13 of the 15 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 13 shared commits counted here, the most recent 3 are `0de15bf9` feat(android): suggest last saved folder when saving a link; `d0e94d55` fix: use numerals for the initial route ID instead of localized strings (at that commit the files were still `composeApp/src/androidDesktopMain/kotlin/Utils.kt` and `composeApp/src/wasmJsMain/kotlin/com/sakethh/linkora/platform/Expected.web.kt`); `c052a73e` feat: add AndroidTV as a platform (at that commit the files were still `composeApp/src/androidDesktopMain/kotlin/Utils.kt` and `composeApp/src/wasmJsMain/kotlin/com/sakethh/linkora/platform/Expected.web.kt`) — run `git show` on any of them.
  • Change coupling: LocalLinksRepoImpl.kt ↔ RemoteLinksRepoImpl.kt shared/src/commonMain/kotlin/com/sakethh/linkora/data/local/repository/LocalLinksRepoImpl.kt:1 — `shared/src/commonMain/kotlin/com/sakethh/linkora/data/local/repository/LocalLinksRepoImpl.kt` and `shared/src/commonMain/kotlin/com/sakethh/linkora/data/remote/repository/RemoteLinksRepoImpl.kt` change together 80% of the time (8 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 8 shared commits counted here, the most recent 3 are `a418ff5f` feat: add option to enforce strict folder IDs for default folders (at that commit the files were still `composeApp/src/commonMain/kotlin/com/sakethh/linkora/data/local/repository/LocalLinksRepoImpl.kt` and `composeApp/src/commonMain/kotlin/com/sakethh/linkora/data/remote/repository/RemoteLinksRepoImpl.kt`); `1919721e` refactor: migrate folder and link moving logic to `MOVE_EXISTING_ITEMS` (at that commit the files were still `composeApp/src/commonMain/kotlin/com/sakethh/linkora/data/local/repository/LocalLinksRepoImpl.kt` and `composeApp/src/commonMain/kotlin/com/sakethh/linkora/data/remote/repository/RemoteLinksRepoImpl.kt`); `7327965e` feat: integrate `ARCHIVE_MULTIPLE_ITEMS` remote operation with local … (at that commit the files were still `composeApp/src/commonMain/kotlin/com/sakethh/linkora/data/local/repository/LocalLinksRepoImpl.kt` and `composeApp/src/commonMain/kotlin/com/sakethh/linkora/data/remote/repository/RemoteLinksRepoImpl.kt`) — run `git show` on any of them.
  • Change coupling: PanelsDao.kt ↔ LocalPanelsRepo.kt shared/src/commonMain/kotlin/com/sakethh/linkora/data/local/dao/PanelsDao.kt:1 — `shared/src/commonMain/kotlin/com/sakethh/linkora/data/local/dao/PanelsDao.kt` and `shared/src/commonMain/kotlin/com/sakethh/linkora/domain/repository/local/LocalPanelsRepo.kt` change together 69% of the time (9 of the 13 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 9 shared commits counted here, the most recent 3 are `4ff46762` feat: add initial logic for snapshots (#36) (at that commit the files were still `composeApp/src/commonMain/kotlin/com/sakethh/linkora/data/local/dao/PanelsDao.kt` and `composeApp/src/commonMain/kotlin/com/sakethh/linkora/domain/repository/local/LocalPanelsRepo.kt`); `d1a9b2c2` feat: push imported data to server after successful import (at that commit the files were still `composeApp/src/commonMain/kotlin/com/sakethh/linkora/data/local/dao/PanelsDao.kt` and `composeApp/src/commonMain/kotlin/com/sakethh/linkora/domain/repository/local/LocalPanelsRepo.kt`); `57b9c057` feat: read websocket events and update `panel` and `panel_folder` tab… (at that commit the files were still `composeApp/src/commonMain/kotlin/com/sakethh/linkora/data/local/dao/PanelsDao.kt` and `composeApp/src/commonMain/kotlin/com/sakethh/linkora/domain/repository/local/LocalPanelsRepo.kt`) — run `git show` on any of them.
  • Change coupling: LinksDao.kt ↔ LocalLinksRepo.kt shared/src/commonMain/kotlin/com/sakethh/linkora/data/local/dao/LinksDao.kt:1 — `shared/src/commonMain/kotlin/com/sakethh/linkora/data/local/dao/LinksDao.kt` and `shared/src/commonMain/kotlin/com/sakethh/linkora/domain/repository/local/LocalLinksRepo.kt` change together 67% of the time (24 of the 36 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 24 shared commits counted here, the most recent 3 are `f79ed656` fix: use `:linkType` or its parent id when determining the link type (at that commit the files were still `composeApp/src/commonMain/kotlin/com/sakethh/linkora/data/local/dao/LinksDao.kt` and `composeApp/src/commonMain/kotlin/com/sakethh/linkora/domain/repository/local/LocalLinksRepo.kt`); `a418ff5f` feat: add option to enforce strict folder IDs for default folders (at that commit the files were still `composeApp/src/commonMain/kotlin/com/sakethh/linkora/data/local/dao/LinksDao.kt` and `composeApp/src/commonMain/kotlin/com/sakethh/linkora/domain/repository/local/LocalLinksRepo.kt`); `8d7c6435` feat: implement a custom paginator to load the data batch wise (at that commit the files were still `composeApp/src/commonMain/kotlin/com/sakethh/linkora/data/local/dao/LinksDao.kt` and `composeApp/src/commonMain/kotlin/com/sakethh/linkora/domain/repository/local/LocalLinksRepo.kt`) — run `git show` on any of them.
  • Change coupling: AddANewFolderDialogBox.kt ↔ CollectionsScreen.kt shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/folder/AddANewFolderDialogBox.kt:1 — `shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/folder/AddANewFolderDialogBox.kt` and `shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/collections/CollectionsScreen.kt` change together 64% of the time (7 of the 11 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `59645d8b` fix: use proper FAB context from screens to switch Main FAB visibilit… (at that commit the files were still `composeApp/src/commonMain/kotlin/com/sakethh/linkora/ui/components/AddANewFolderDialogBox.kt` and `composeApp/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/collections/CollectionsScreen.kt`); `e3461fa5` feat: add nested folders support and folder hierarchy deletion (at that commit the files were still `composeApp/src/commonMain/kotlin/com/sakethh/linkora/ui/components/AddANewFolderDialogBox.kt` and `composeApp/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/collections/CollectionsScreen.kt`); `ddf99a88` refactor codebase to use manual DI (at that commit the files were still `composeApp/src/commonMain/kotlin/com/sakethh/linkora/ui/components/AddANewFolderDialogBox.kt` and `composeApp/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/collections/CollectionsScreen.kt`) — run `git show` on any of them.
  • Change coupling: SnapshotWorker.kt ↔ DataSettingsScreen.kt shared/src/androidMain/kotlin/com/sakethh/linkora/worker/SnapshotWorker.kt:1 — `shared/src/androidMain/kotlin/com/sakethh/linkora/worker/SnapshotWorker.kt` and `shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/settings/section/data/DataSettingsScreen.kt` change together 55% of the time (6 of the 11 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `1d875fb4` chore: replace hardcoded strings for localization (at that commit the files were still `composeApp/src/androidMain/kotlin/com/sakethh/linkora/worker/SnapshotWorker.kt` and `composeApp/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/settings/section/data/DataSettingsScreen.kt`); `7d76cd8f` feat(android-tv): support exports, snapshots, and web-captures operat… (at that commit the files were still `composeApp/src/androidMain/kotlin/com/sakethh/linkora/worker/SnapshotWorker.kt` and `composeApp/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/settings/section/data/DataSettingsScreen.kt`); `3ff34831` feat: set up auto-deletion for snapshots (at that commit the files were still `composeApp/src/androidMain/kotlin/com/sakethh/linkora/worker/SnapshotWorker.kt` and `composeApp/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/settings/section/data/DataSettingsScreen.kt`) — run `git show` on any of them.
  • Change coupling: RemoteFoldersRepoImpl.kt ↔ LocalFoldersRepo.kt shared/src/commonMain/kotlin/com/sakethh/linkora/data/remote/repository/RemoteFoldersRepoImpl.kt:1 — `shared/src/commonMain/kotlin/com/sakethh/linkora/data/remote/repository/RemoteFoldersRepoImpl.kt` and `shared/src/commonMain/kotlin/com/sakethh/linkora/domain/repository/local/LocalFoldersRepo.kt` change together 53% of the time (8 of the 15 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 8 shared commits counted here, the most recent 3 are `5a19d19a` feat(sync): unify folder updates into a single POST request (at that commit the files were still `composeApp/src/commonMain/kotlin/com/sakethh/linkora/data/remote/repository/RemoteFoldersRepoImpl.kt` and `composeApp/src/commonMain/kotlin/com/sakethh/linkora/domain/repository/local/LocalFoldersRepo.kt`); `1919721e` refactor: migrate folder and link moving logic to `MOVE_EXISTING_ITEMS` (at that commit the files were still `composeApp/src/commonMain/kotlin/com/sakethh/linkora/data/remote/repository/RemoteFoldersRepoImpl.kt` and `composeApp/src/commonMain/kotlin/com/sakethh/linkora/domain/repository/local/LocalFoldersRepo.kt`); `cd6ed64c` feat(remote): integrate `MOVE_FOLDERS` remote operation with local op… (at that commit the files were still `composeApp/src/commonMain/kotlin/com/sakethh/linkora/data/remote/repository/RemoteFoldersRepoImpl.kt` and `composeApp/src/commonMain/kotlin/com/sakethh/linkora/domain/repository/local/LocalFoldersRepo.kt`) — run `git show` on any of them.
  • Change coupling: Mappers.kt ↔ CollectionsScreenVM.kt shared/src/commonMain/kotlin/com/sakethh/linkora/domain/Mappers.kt:1 — `shared/src/commonMain/kotlin/com/sakethh/linkora/domain/Mappers.kt` and `shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/collections/CollectionsScreenVM.kt` change together 53% of the time (9 of the 17 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 9 shared commits counted here, the most recent 3 are `fe56f139` rename `baseURL` variable to `host` in `Link` (at that commit the files were still `composeApp/src/commonMain/kotlin/com/sakethh/linkora/domain/Mappers.kt` and `composeApp/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/collections/CollectionsScreenVM.kt`); `5a19d19a` feat(sync): unify folder updates into a single POST request (at that commit the files were still `composeApp/src/commonMain/kotlin/com/sakethh/linkora/domain/Mappers.kt` and `composeApp/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/collections/CollectionsScreenVM.kt`); `0147904e` feat(links): revamp important link handling (at that commit the files were still `composeApp/src/commonMain/kotlin/com/sakethh/linkora/domain/Mappers.kt` and `composeApp/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/collections/CollectionsScreenVM.kt`) — run `git show` on any of them.
  • Change coupling: LocalLinksRepoImpl.kt ↔ Mappers.kt shared/src/commonMain/kotlin/com/sakethh/linkora/data/local/repository/LocalLinksRepoImpl.kt:1 — `shared/src/commonMain/kotlin/com/sakethh/linkora/data/local/repository/LocalLinksRepoImpl.kt` and `shared/src/commonMain/kotlin/com/sakethh/linkora/domain/Mappers.kt` change together 53% of the time (9 of the 17 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 9 shared commits counted here, the most recent 3 are `a418ff5f` feat: add option to enforce strict folder IDs for default folders (at that commit the files were still `composeApp/src/commonMain/kotlin/com/sakethh/linkora/data/local/repository/LocalLinksRepoImpl.kt` and `composeApp/src/commonMain/kotlin/com/sakethh/linkora/domain/Mappers.kt`); `fe56f139` rename `baseURL` variable to `host` in `Link` (at that commit the files were still `composeApp/src/commonMain/kotlin/com/sakethh/linkora/data/local/repository/LocalLinksRepoImpl.kt` and `composeApp/src/commonMain/kotlin/com/sakethh/linkora/domain/Mappers.kt`); `0147904e` feat(links): revamp important link handling (at that commit the files were still `composeApp/src/commonMain/kotlin/com/sakethh/linkora/data/local/repository/LocalLinksRepoImpl.kt` and `composeApp/src/commonMain/kotlin/com/sakethh/linkora/domain/Mappers.kt`) — run `git show` on any of them.
  • Change coupling: RemoteLinksRepoImpl.kt ↔ LocalLinksRepo.kt shared/src/commonMain/kotlin/com/sakethh/linkora/data/remote/repository/RemoteLinksRepoImpl.kt:1 — `shared/src/commonMain/kotlin/com/sakethh/linkora/data/remote/repository/RemoteLinksRepoImpl.kt` and `shared/src/commonMain/kotlin/com/sakethh/linkora/domain/repository/local/LocalLinksRepo.kt` change together 50% of the time (5 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 5 shared commits counted here, the most recent 3 are `a418ff5f` feat: add option to enforce strict folder IDs for default folders (at that commit the files were still `composeApp/src/commonMain/kotlin/com/sakethh/linkora/data/remote/repository/RemoteLinksRepoImpl.kt` and `composeApp/src/commonMain/kotlin/com/sakethh/linkora/domain/repository/local/LocalLinksRepo.kt`); `1919721e` refactor: migrate folder and link moving logic to `MOVE_EXISTING_ITEMS` (at that commit the files were still `composeApp/src/commonMain/kotlin/com/sakethh/linkora/data/remote/repository/RemoteLinksRepoImpl.kt` and `composeApp/src/commonMain/kotlin/com/sakethh/linkora/domain/repository/local/LocalLinksRepo.kt`); `7327965e` feat: integrate `ARCHIVE_MULTIPLE_ITEMS` remote operation with local … (at that commit the files were still `composeApp/src/commonMain/kotlin/com/sakethh/linkora/data/remote/repository/RemoteLinksRepoImpl.kt` and `composeApp/src/commonMain/kotlin/com/sakethh/linkora/domain/repository/local/LocalLinksRepo.kt`) — run `git show` on any of them.
D17 · Explicit Debt · TodoComment · ×9
  • TodoComment shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/settings/section/GeneralSettingsScreen.kt:100 — // TODO: GET RID OF THIS — 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 shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/settings/section/LanguageSettingsScreenVM.kt:72 — // TODO: NESTED collection — 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 shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/settings/section/LanguageSettingsScreenVM.kt:160 — // TODO: NESTED collectLatest — 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 shared/src/commonMain/kotlin/com/sakethh/linkora/data/remote/repository/sync/PendingQueueService.kt:235 — // TODO: NESTED collectLatest — 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 shared/src/commonMain/kotlin/com/sakethh/linkora/data/local/repository/SnapshotRepoImpl.kt:78 — // TODO: NESTED collectLatest — 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 shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/search/SearchScreenVM.kt:105 — // TODO: refactor this into a data class — 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 shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/home/HomeScreenVM.kt:64 — // TODO: migrate to the pagination — 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 shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/home/HomeScreenVM.kt:68 — // TODO: migrate to the pagination — 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 shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/link/AddANewLinkDialog.kt:1756 — // TODO: get rid of this — 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 · Duplicated block (15 lines × 2) · ×8
  • Duplicated block (15 lines × 2) shared/src/commonMain/kotlin/com/sakethh/linkora/data/remote/repository/sync/LocalDataUpdateService.kt:664 — shared/src/commonMain/kotlin/com/sakethh/linkora/data/remote/repository/sync/LocalDataUpdateService.kt:664-678 | shared/src/commonMain/kotlin/com/sakethh/linkora/data/remote/repository/sync/LocalDataUpdateService.kt:741-755 — 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 `shared/src/commonMain/kotlin/com/sakethh/linkora/data/remote/repository/sync/LocalDataUpdateService.kt:664` 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 (15 lines × 2) shared/src/commonMain/kotlin/com/sakethh/linkora/data/remote/repository/sync/SyncSessionServiceImpl.kt:162 — shared/src/commonMain/kotlin/com/sakethh/linkora/data/remote/repository/sync/SyncSessionServiceImpl.kt:162-176 | shared/src/commonMain/kotlin/com/sakethh/linkora/data/remote/repository/sync/SyncSessionServiceImpl.kt:182-196 — 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 `shared/src/commonMain/kotlin/com/sakethh/linkora/data/remote/repository/sync/SyncSessionServiceImpl.kt:162` 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 (15 lines × 2) shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/settings/SettingsScreenViewModel.kt:500 — shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/settings/SettingsScreenViewModel.kt:500-514 | shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/settings/SettingsScreenViewModel.kt:565-579 — 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 `shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/settings/SettingsScreenViewModel.kt:500` 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 (15 lines × 2) shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/settings/section/AdvancedSettingsScreen.kt:153 — shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/settings/section/AdvancedSettingsScreen.kt:153-167 | shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/settings/section/AdvancedSettingsScreen.kt:187-201 — 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 `shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/settings/section/AdvancedSettingsScreen.kt: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.
  • Duplicated block (15 lines × 2) shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/settings/section/data/capture/WebPageCaptureScreen.kt:100 — shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/settings/section/data/capture/WebPageCaptureScreen.kt:100-114 | shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/settings/section/data/snapshots/SnapshotsScreen.kt:93-107 — 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 `shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/settings/section/data/capture/WebPageCaptureScreen.kt:100` 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 (15 lines × 2) shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/settings/SettingsScreenViewModel.kt:265 — shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/settings/SettingsScreenViewModel.kt:265-279 | shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/settings/SettingsScreenViewModel.kt:298-312 — 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 `shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/settings/SettingsScreenViewModel.kt:265` 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 (15 lines × 2) shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/settings/SettingsScreen.kt:201 — shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/settings/SettingsScreen.kt:201-215 | shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/settings/SettingsScreen.kt:224-238 — 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 `shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/settings/SettingsScreen.kt:201` 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 (15 lines × 2) shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/settings/SettingsScreenViewModel.kt:409 — shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/settings/SettingsScreenViewModel.kt:409-423 | shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/settings/SettingsScreenViewModel.kt:473-487 — 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 `shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/settings/SettingsScreenViewModel.kt:409` 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.
D3 · God Classes · ClassTooLong · ×6
  • ClassTooLong: LocalLinksRepoImpl shared/src/commonMain/kotlin/com/sakethh/linkora/data/local/repository/LocalLinksRepoImpl.kt:63 — ClassTooLong — 813 significant lines (blank, comment-only and punctuation-only lines excluded), 39 methods. The bar is 400 significant lines; this is 413 over it, 2.03× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: LocalDataUpdateService shared/src/commonMain/kotlin/com/sakethh/linkora/data/remote/repository/sync/LocalDataUpdateService.kt:56 — ClassTooLong — 639 significant lines (blank, comment-only and punctuation-only lines excluded), 4 methods. The bar is 400 significant lines; this is 239 over it, 1.60× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: PendingQueueService shared/src/commonMain/kotlin/com/sakethh/linkora/data/remote/repository/sync/PendingQueueService.kt:54 — ClassTooLong — 569 significant lines (blank, comment-only and punctuation-only lines excluded), 3 methods. The bar is 400 significant lines; this is 169 over it, 1.42× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: SettingsScreenViewModel shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/settings/SettingsScreenViewModel.kt:45 — ClassTooLong — 543 significant lines (blank, comment-only and punctuation-only lines excluded), 8 methods. The bar is 400 significant lines; this is 143 over it, 1.36× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: AppPreferences shared/src/commonMain/kotlin/com/sakethh/linkora/domain/AppPreferences.kt:18 — ClassTooLong — 534 significant lines (blank, comment-only and punctuation-only lines excluded), 1 methods. The bar is 400 significant lines; this is 134 over it, 1.34× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: CollectionsScreenVM shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/collections/CollectionsScreenVM.kt:54 — ClassTooLong — 505 significant lines (blank, comment-only and punctuation-only lines excluded), 25 methods. The bar is 400 significant lines; this is 105 over it, 1.26× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
D4 · Code Duplication · Duplicated block (20 lines × 2) · ×4
  • Duplicated block (20 lines × 2) shared/src/androidMain/kotlin/com/sakethh/linkora/platform/FileManager.kt:185 — shared/src/androidMain/kotlin/com/sakethh/linkora/platform/FileManager.kt:185-204 | shared/src/androidMain/kotlin/com/sakethh/linkora/platform/FileManager.kt:217-236 — 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 `shared/src/androidMain/kotlin/com/sakethh/linkora/platform/FileManager.kt:185` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (20 lines × 2) shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/folder/RenameFolderDialog.kt:110 — shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/folder/RenameFolderDialog.kt:110-129 | shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/link/RenameLinkDialogParam.kt:138-157 — before extracting anything, compare `shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/folder/RenameFolderDialog.kt` and `shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/link/RenameLinkDialogParam.kt` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 158 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/folder/RenameFolderDialog.kt:110` 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 (20 lines × 2) shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/settings/section/data/capture/WebPageCaptureScreen.kt:331 — shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/settings/section/data/capture/WebPageCaptureScreen.kt:331-350 | shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/settings/section/data/capture/WebPageCaptureScreen.kt:378-397 — 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 `shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/settings/section/data/capture/WebPageCaptureScreen.kt:331` 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 (20 lines × 2) shared/src/commonMain/kotlin/com/sakethh/linkora/utils/Extensions.kt:411 — shared/src/commonMain/kotlin/com/sakethh/linkora/utils/Extensions.kt:411-430 | shared/src/commonMain/kotlin/com/sakethh/linkora/utils/Extensions.kt:441-460 — 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.
D4 · Code Duplication · Duplicated block (19 lines × 2) · ×4
  • Duplicated block (19 lines × 2) shared/src/commonMain/kotlin/com/sakethh/linkora/data/local/repository/LocalLinksRepoImpl.kt:298 — shared/src/commonMain/kotlin/com/sakethh/linkora/data/local/repository/LocalLinksRepoImpl.kt:298-316 | shared/src/commonMain/kotlin/com/sakethh/linkora/data/local/repository/LocalLinksRepoImpl.kt:352-370 — 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 `shared/src/commonMain/kotlin/com/sakethh/linkora/data/local/repository/LocalLinksRepoImpl.kt:298` 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 (19 lines × 2) shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/folder/RenameFolderDialog.kt:136 — shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/folder/RenameFolderDialog.kt:136-154 | shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/link/RenameLinkDialogParam.kt:164-182 — before extracting anything, compare `shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/folder/RenameFolderDialog.kt` and `shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/link/RenameLinkDialogParam.kt` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 158 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/folder/RenameFolderDialog.kt:136` 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 (19 lines × 2) shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/link/AddANewLinkDialog.kt:1524 — shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/link/AddANewLinkDialog.kt:1524-1542 | shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/link/AddANewLinkDialog.kt:1578-1596 — 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 `shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/link/AddANewLinkDialog.kt:1524` 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 (19 lines × 2) shared/src/desktopMain/kotlin/com/sakethh/linkora/platform/FileManager.kt:156 — shared/src/desktopMain/kotlin/com/sakethh/linkora/platform/FileManager.kt:156-174 | shared/src/desktopMain/kotlin/com/sakethh/linkora/platform/FileManager.kt:182-200 — 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 `shared/src/desktopMain/kotlin/com/sakethh/linkora/platform/FileManager.kt:156` 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.
D4 · Code Duplication · Duplicated block (17 lines × 2) · ×4
  • Duplicated block (17 lines × 2) shared/src/androidMain/kotlin/com/sakethh/linkora/worker/AllLinksWebCaptureWorker.kt:112 — shared/src/androidMain/kotlin/com/sakethh/linkora/worker/AllLinksWebCaptureWorker.kt:112-128 | shared/src/desktopMain/kotlin/com/sakethh/linkora/AllLinksWebCaptureService.kt:72-88 — before extracting anything, compare `shared/src/androidMain/kotlin/com/sakethh/linkora/worker/AllLinksWebCaptureWorker.kt` and `shared/src/desktopMain/kotlin/com/sakethh/linkora/AllLinksWebCaptureService.kt` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 46 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (17 lines × 2) shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/home/panels/PanelsManagerScreen.kt:119 — shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/home/panels/PanelsManagerScreen.kt:119-135 | shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/home/panels/SpecificPanelManagerScreen.kt:79-95 — 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 `shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/home/panels/PanelsManagerScreen.kt:119` 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 (17 lines × 2) shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/settings/SettingsScreenViewModel.kt:350 — shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/settings/SettingsScreenViewModel.kt:350-366 | shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/settings/SettingsScreenViewModel.kt:383-399 — 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 `shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/settings/SettingsScreenViewModel.kt:350` 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 (17 lines × 2) shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/settings/SettingsScreen.kt:146 — shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/settings/SettingsScreen.kt:146-162 | shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/settings/SettingsScreen.kt:166-182 — 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 `shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/settings/SettingsScreen.kt:146` 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.
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D35 · Change Coupling · Change-coupling hub · ×3
  • Change-coupling hub: LocalFoldersRepoImpl.kt → PanelsDao.kt, LocalPanelsRepoImpl.kt, RemoteFoldersRepoImpl.kt shared/src/commonMain/kotlin/com/sakethh/linkora/data/local/repository/LocalFoldersRepoImpl.kt — `shared/src/commonMain/kotlin/com/sakethh/linkora/data/local/repository/LocalFoldersRepoImpl.kt` changes together with 3 other files — `shared/src/commonMain/kotlin/com/sakethh/linkora/data/local/dao/PanelsDao.kt`, `shared/src/commonMain/kotlin/com/sakethh/linkora/data/local/repository/LocalPanelsRepoImpl.kt`, `shared/src/commonMain/kotlin/com/sakethh/linkora/data/remote/repository/RemoteFoldersRepoImpl.kt` — none of which declares a dependency on it: one file is the hub of 3 separate couplings, not 3 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 3.
  • Change-coupling hub: FoldersDao.kt → LinksDao.kt, LocalFoldersRepo.kt, App.kt shared/src/commonMain/kotlin/com/sakethh/linkora/data/local/dao/FoldersDao.kt — `shared/src/commonMain/kotlin/com/sakethh/linkora/data/local/dao/FoldersDao.kt` changes together with 3 other files — `shared/src/commonMain/kotlin/com/sakethh/linkora/data/local/dao/LinksDao.kt`, `shared/src/commonMain/kotlin/com/sakethh/linkora/domain/repository/local/LocalFoldersRepo.kt`, `shared/src/commonMain/kotlin/com/sakethh/linkora/ui/App.kt` — none of which declares a dependency on it: one file is the hub of 3 separate couplings, not 3 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 3.
  • Change-coupling hub: PreferencesImpl.kt → Utils.kt, App.kt, Expected.wasmJs.kt shared/src/commonMain/kotlin/com/sakethh/linkora/data/local/repository/PreferencesImpl.kt — `shared/src/commonMain/kotlin/com/sakethh/linkora/data/local/repository/PreferencesImpl.kt` changes together with 3 other files — `shared/src/androidDesktopMain/kotlin/Utils.kt`, `shared/src/commonMain/kotlin/com/sakethh/linkora/ui/App.kt`, `shared/src/wasmJsMain/kotlin/platform/Expected.wasmJs.kt` — none of which declares a dependency on it: one file is the hub of 3 separate couplings, not 3 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 3.
D4 · Code Duplication · Edited copy of a member (27 corresponding lines) · ×3
  • Edited copy of a member (27 corresponding lines) shared/src/androidMain/kotlin/com/sakethh/linkora/utils/ExtensionFunctions.kt:78 — shared/src/androidMain/kotlin/com/sakethh/linkora/utils/ExtensionFunctions.kt:78-104 | shared/src/desktopMain/kotlin/com/sakethh/linkora/Utils.kt:21-47 — 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.
  • Edited copy of a member (27 corresponding lines) shared/src/androidMain/kotlin/com/sakethh/linkora/service/RefreshAllLinksNotificationService.kt:37 — shared/src/androidMain/kotlin/com/sakethh/linkora/service/RefreshAllLinksNotificationService.kt:37-63 | shared/src/androidMain/kotlin/com/sakethh/linkora/service/WebCaptureNotificationService.kt:36-63 — 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.
  • Edited copy of a member (27 corresponding lines) shared/src/androidMain/kotlin/com/sakethh/linkora/platform/FileManager.kt:178 — shared/src/androidMain/kotlin/com/sakethh/linkora/platform/FileManager.kt:178-204 | shared/src/androidMain/kotlin/com/sakethh/linkora/platform/FileManager.kt:210-236 — 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 · Duplicated block (23 lines × 2) · ×3
  • Duplicated block (23 lines × 2) shared/src/androidMain/kotlin/com/sakethh/linkora/utils/RegularFunctions.kt:158 — shared/src/androidMain/kotlin/com/sakethh/linkora/utils/RegularFunctions.kt:158-180 | shared/src/androidMain/kotlin/com/sakethh/linkora/utils/RegularFunctions.kt:188-210 — 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 `shared/src/androidMain/kotlin/com/sakethh/linkora/utils/RegularFunctions.kt:158` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note 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 (23 lines × 2) shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/folder/menu/FolderMenuBtmSheet.kt:168 — shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/folder/menu/FolderMenuBtmSheet.kt:168-190 | shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/link/menu/LinkMenuBtmSheet.kt:338-360 — before extracting anything, compare `shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/folder/menu/FolderMenuBtmSheet.kt` and `shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/link/menu/LinkMenuBtmSheet.kt` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 95 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/folder/menu/FolderMenuBtmSheet.kt:168` 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 (23 lines × 2) shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/home/HomeScreen.kt:270 — shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/home/HomeScreen.kt:270-292 | shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/search/SearchScreen.kt:209-231 — 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 `shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/home/HomeScreen.kt:270` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (18 lines × 2) · ×3
  • Duplicated block (18 lines × 2) shared/src/commonMain/kotlin/com/sakethh/linkora/data/remote/repository/sync/LocalDataUpdateService.kt:474 — shared/src/commonMain/kotlin/com/sakethh/linkora/data/remote/repository/sync/LocalDataUpdateService.kt:474-491 | shared/src/commonMain/kotlin/com/sakethh/linkora/data/remote/repository/sync/LocalDataUpdateService.kt:507-524 — 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 `shared/src/commonMain/kotlin/com/sakethh/linkora/data/remote/repository/sync/LocalDataUpdateService.kt:474` 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 (18 lines × 2) shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/CollectionLayoutManager.kt:431 — shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/CollectionLayoutManager.kt:431-448 | shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/CollectionLayoutManager.kt:610-627 — 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 `shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/CollectionLayoutManager.kt:431` 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 (18 lines × 2) shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/CollectionLayoutManager.kt:498 — shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/CollectionLayoutManager.kt:498-515 | shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/CollectionLayoutManager.kt:680-697 — 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 `shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/CollectionLayoutManager.kt:498` 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.
D4 · Code Duplication · Duplicated block (15 lines × 3) · ×3
  • Duplicated block (15 lines × 3) shared/src/commonMain/kotlin/com/sakethh/linkora/data/remote/repository/sync/LocalDataUpdateService.kt:620 — shared/src/commonMain/kotlin/com/sakethh/linkora/data/remote/repository/sync/LocalDataUpdateService.kt:620-634 | shared/src/commonMain/kotlin/com/sakethh/linkora/data/remote/repository/sync/LocalDataUpdateService.kt:641-655 | shared/src/commonMain/kotlin/com/sakethh/linkora/data/remote/repository/sync/LocalDataUpdateService.kt:715-729 — 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 `shared/src/commonMain/kotlin/com/sakethh/linkora/data/remote/repository/sync/LocalDataUpdateService.kt:620` 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 (15 lines × 3) shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/AddItemFAB.kt:97 — shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/AddItemFAB.kt:97-111 | shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/AddItemFAB.kt:141-155 | shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/AddItemFAB.kt:186-200 — 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 `shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/AddItemFAB.kt:97` 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 (15 lines × 3) shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/onboarding/OnboardingSlidesScreen.kt:344 — shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/onboarding/OnboardingSlidesScreen.kt:344-365 | shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/onboarding/OnboardingSlidesScreen.kt:566-580 | shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/onboarding/OnboardingSlidesScreen.kt:640-657 — 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 `shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/onboarding/OnboardingSlidesScreen.kt:344` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note 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.
D6 · Cohesion (LCOM4) · Low cohesion · ×3
  • Low cohesion: SearchScreenVM (LCOM4 6) shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/search/SearchScreenVM.kt:48 — SearchScreenVM's methods fall into 6 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 6 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: AppVM (LCOM4 5) shared/src/commonMain/kotlin/com/sakethh/linkora/ui/AppVM.kt:66 — AppVM's methods fall into 5 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 5 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: FileManager (LCOM4 5) shared/src/desktopMain/kotlin/com/sakethh/linkora/platform/FileManager.kt:42 — FileManager's methods fall into 5 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 5 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
D3 · God Classes · TooManyMethods · ×2
  • TooManyMethods: LocalLinksRepoImpl shared/src/commonMain/kotlin/com/sakethh/linkora/data/local/repository/LocalLinksRepoImpl.kt:63 — TooManyMethods — 39 methods. The bar is 30 methods; this is 9 over it, 1.30× the bar. Most of these members implement local.LocalLinksRepo (31 of 35 members), so moving them onto a smaller type would remove them from that contract rather than reduce it. To reduce it, split the contract instead: give each cohesive group of operations its own smaller interface and its own implementing type. Where the contract has to stay whole, move the work behind these members into collaborator types, so what is left here is a forward per member rather than a responsibility per member.
  • TooManyMethods: LocalFoldersRepoImpl shared/src/commonMain/kotlin/com/sakethh/linkora/data/local/repository/LocalFoldersRepoImpl.kt:32 — TooManyMethods — 31 methods. The bar is 30 methods; this is 1 over it, 1.03× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
D4 · Code Duplication · Edited copy of a member (23 corresponding lines) · ×2
  • Edited copy of a member (23 corresponding lines) shared/src/androidMain/kotlin/com/sakethh/linkora/platform/NativeUtils.kt:69 — shared/src/androidMain/kotlin/com/sakethh/linkora/platform/NativeUtils.kt:69-93 | shared/src/androidMain/kotlin/com/sakethh/linkora/platform/NativeUtils.kt:226-248 — These two members are one piece of code written twice and then edited apart: 23 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 (23 corresponding lines) shared/src/commonMain/kotlin/com/sakethh/linkora/ui/AppVM.kt:274 — shared/src/commonMain/kotlin/com/sakethh/linkora/ui/AppVM.kt:274-301 | shared/src/commonMain/kotlin/com/sakethh/linkora/ui/AppVM.kt:307-329 — These two members are one piece of code written twice and then edited apart: 23 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 · Duplicated block (21 lines × 2) · ×2
  • Duplicated block (21 lines × 2) desktopApp/src/main/kotlin/com/sakethh/linkora/main.kt:116 — desktopApp/src/main/kotlin/com/sakethh/linkora/main.kt:116-136 | webApp/src/webMain/kotlin/com/sakethh/linkora/Main.kt:116-136 — 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 `desktopApp/src/main/kotlin/com/sakethh/linkora/main.kt:116` 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 (21 lines × 2) shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/folder/RenameFolderDialog.kt:157 — shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/folder/RenameFolderDialog.kt:157-177 | shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/link/RenameLinkDialogParam.kt:246-266 — before extracting anything, compare `shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/folder/RenameFolderDialog.kt` and `shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/link/RenameLinkDialogParam.kt` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 158 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/folder/RenameFolderDialog.kt:157` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (20–21 lines × 2) · ×2
  • Duplicated block (20–21 lines × 2) shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/CollectionLayoutManager.kt:453 — shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/CollectionLayoutManager.kt:453-473 | shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/CollectionLayoutManager.kt:632-651 — 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 `shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/CollectionLayoutManager.kt:453` 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 (20–21 lines × 2) shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/search/SearchScreen.kt:245 — shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/search/SearchScreen.kt:245-265 | shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/search/SearchScreen.kt:333-352 — 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 `shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/search/SearchScreen.kt:245` 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.
D4 · Code Duplication · Duplicated block (15–18 lines × 2) · ×2
  • Duplicated block (15–18 lines × 2) shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/collections/CollectionDetailPane.kt:325 — shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/collections/CollectionDetailPane.kt:325-342 | shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/collections/CollectionDetailPane.kt:619-633 — 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 `shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/collections/CollectionDetailPane.kt: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. 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 (15–18 lines × 2) shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/onboarding/OnboardingSlidesScreen.kt:572 — shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/onboarding/OnboardingSlidesScreen.kt:572-586 | shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/onboarding/OnboardingSlidesScreen.kt:646-663 — 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 `shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/onboarding/OnboardingSlidesScreen.kt:572` 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.
D4 · Code Duplication · Duplicated block (16 lines × 2) · ×2
  • Duplicated block (16 lines × 2) shared/src/commonMain/kotlin/com/sakethh/linkora/data/remote/repository/sync/LocalDataUpdateService.kt:662 — shared/src/commonMain/kotlin/com/sakethh/linkora/data/remote/repository/sync/LocalDataUpdateService.kt:662-677 | shared/src/commonMain/kotlin/com/sakethh/linkora/data/remote/repository/sync/LocalDataUpdateService.kt:688-703 — 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 `shared/src/commonMain/kotlin/com/sakethh/linkora/data/remote/repository/sync/LocalDataUpdateService.kt:662` 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 (16 lines × 2) shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/CollectionLayoutManager.kt:529 — shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/CollectionLayoutManager.kt:529-546 | shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/CollectionLayoutManager.kt:706-721 — 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 `shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/CollectionLayoutManager.kt:529` 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. 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.
D4 · Code Duplication · Duplicated block (13 lines × 4) · ×2
  • Duplicated block (13 lines × 4) shared/src/androidMain/kotlin/com/sakethh/linkora/worker/AllLinksWebCaptureWorker.kt:88 — shared/src/androidMain/kotlin/com/sakethh/linkora/worker/AllLinksWebCaptureWorker.kt:88-100 | shared/src/androidMain/kotlin/com/sakethh/linkora/worker/WebCaptureWorker.kt:80-92 | shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/settings/SettingsScreenViewModel.kt:724-736 | shared/src/desktopMain/kotlin/com/sakethh/linkora/AllLinksWebCaptureService.kt:52-64 — before extracting anything, compare `shared/src/androidMain/kotlin/com/sakethh/linkora/worker/AllLinksWebCaptureWorker.kt` and `shared/src/desktopMain/kotlin/com/sakethh/linkora/AllLinksWebCaptureService.kt` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 46 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `shared/src/androidMain/kotlin/com/sakethh/linkora/worker/AllLinksWebCaptureWorker.kt:88` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `shared/src/androidMain/kotlin/com/sakethh/linkora/worker/WebCaptureWorker.kt:94` calls `printStackTrace` and `shared/src/androidMain/kotlin/com/sakethh/linkora/worker/AllLinksWebCaptureWorker.kt:102` 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 (13 lines × 4) shared/src/commonMain/kotlin/com/sakethh/linkora/data/remote/repository/sync/LocalDataUpdateService.kt:406 — shared/src/commonMain/kotlin/com/sakethh/linkora/data/remote/repository/sync/LocalDataUpdateService.kt:406-419 | shared/src/commonMain/kotlin/com/sakethh/linkora/data/remote/repository/sync/LocalDataUpdateService.kt:426-439 | shared/src/commonMain/kotlin/com/sakethh/linkora/data/remote/repository/sync/LocalDataUpdateService.kt:449-462 | shared/src/commonMain/kotlin/com/sakethh/linkora/data/remote/repository/sync/LocalDataUpdateService.kt:538-550 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `shared/src/commonMain/kotlin/com/sakethh/linkora/data/remote/repository/sync/LocalDataUpdateService.kt:406` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (12 lines × 2) · ×2
  • Duplicated block (12 lines × 2) shared/src/commonMain/kotlin/com/sakethh/linkora/data/ImportDataRepoImpl.kt:246 — shared/src/commonMain/kotlin/com/sakethh/linkora/data/ImportDataRepoImpl.kt:246-257 | shared/src/commonMain/kotlin/com/sakethh/linkora/data/ImportDataRepoImpl.kt:426-437 — 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 `shared/src/commonMain/kotlin/com/sakethh/linkora/data/ImportDataRepoImpl.kt:246` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (12 lines × 2) shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/settings/section/data/capture/WebPageCaptureScreen.kt:167 — shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/settings/section/data/capture/WebPageCaptureScreen.kt:167-178 | shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/settings/section/data/snapshots/SnapshotsScreen.kt:156-167 — 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 `shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/settings/section/data/capture/WebPageCaptureScreen.kt:167` 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.
DM5 · Encapsulated state · Mutable entity · ×2
  • Mutable entity: Folder shared/src/commonMain/kotlin/com/sakethh/linkora/domain/model/Folder.kt:21 — `Folder` exposes publicly writable state (path).
  • Mutable entity: Link shared/src/commonMain/kotlin/com/sakethh/linkora/domain/model/link/Link.kt:25 — `Link` exposes publicly writable state (path).
D1 · Cyclomatic Complexity · LocalDataUpdateService.updateLocalDBAccordingToEvent (cyclomatic 109) · ×1
  • LocalDataUpdateService.updateLocalDBAccordingToEvent (cyclomatic 109) shared/src/commonMain/kotlin/com/sakethh/linkora/data/remote/repository/sync/LocalDataUpdateService.kt:76 — LocalDataUpdateService.updateLocalDBAccordingToEvent has cyclomatic complexity 109 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · PendingQueueService.pushPendingSyncQueueToServer (cyclomatic 71) · ×1
  • PendingQueueService.pushPendingSyncQueueToServer (cyclomatic 71) shared/src/commonMain/kotlin/com/sakethh/linkora/data/remote/repository/sync/PendingQueueService.kt:80 — PendingQueueService.pushPendingSyncQueueToServer has cyclomatic complexity 71 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · CollectionLayoutManagerKt.CollectionLayoutManager (cyclomatic 60) · ×1
  • CollectionLayoutManagerKt.CollectionLayoutManager (cyclomatic 60) shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/CollectionLayoutManager.kt:73 — CollectionLayoutManagerKt.CollectionLayoutManager has cyclomatic complexity 60 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · AddANewLinkDialogKt.BottomPartOfAddANewLinkDialogBox (cyclomatic 43) · ×1
  • AddANewLinkDialogKt.BottomPartOfAddANewLinkDialogBox (cyclomatic 43) shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/link/AddANewLinkDialog.kt:661 — AddANewLinkDialogKt.BottomPartOfAddANewLinkDialogBox has cyclomatic complexity 43 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · CollectionsScreenKt.CollectionsScreen (cyclomatic 39) · ×1
  • CollectionsScreenKt.CollectionsScreen (cyclomatic 39) shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/collections/CollectionsScreen.kt:132 — CollectionsScreenKt.CollectionsScreen has cyclomatic complexity 39 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · GridViewLinkComponentKt.GridViewLinkComponent (cyclomatic 36) · ×1
  • GridViewLinkComponentKt.GridViewLinkComponent (cyclomatic 36) shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/link/GridViewLinkComponent.kt:67 — GridViewLinkComponentKt.GridViewLinkComponent has cyclomatic complexity 36 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · BottomNavOnSelectionKt.BottomNavOnSelection (cyclomatic 34) · ×1
  • BottomNavOnSelectionKt.BottomNavOnSelection (cyclomatic 34) shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/nav/BottomNavOnSelection.kt:72 — BottomNavOnSelectionKt.BottomNavOnSelection 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.
D1 · Cyclomatic Complexity · DataSettingsScreenKt.DataSettingsScreen (cyclomatic 34) · ×1
  • DataSettingsScreenKt.DataSettingsScreen (cyclomatic 34) shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/settings/section/data/DataSettingsScreen.kt:125 — DataSettingsScreenKt.DataSettingsScreen 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.
D1 · Cyclomatic Complexity · CollectionDetailPaneKt.CollectionDetailPane (cyclomatic 32) · ×1
  • CollectionDetailPaneKt.CollectionDetailPane (cyclomatic 32) shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/collections/CollectionDetailPane.kt:113 — CollectionDetailPaneKt.CollectionDetailPane has cyclomatic complexity 32 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · AppKt.App (cyclomatic 30) · ×1
  • AppKt.App (cyclomatic 30) shared/src/commonMain/kotlin/com/sakethh/linkora/ui/App.kt:134 — AppKt.App has cyclomatic complexity 30 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · LocalLinksRepoImpl.addANewLink (cyclomatic 29) · ×1
  • LocalLinksRepoImpl.addANewLink (cyclomatic 29) shared/src/commonMain/kotlin/com/sakethh/linkora/data/local/repository/LocalLinksRepoImpl.kt:84 — LocalLinksRepoImpl.addANewLink has cyclomatic complexity 29 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · ListViewLinkComponentKt.ListViewLinkComponent (cyclomatic 28) · ×1
  • ListViewLinkComponentKt.ListViewLinkComponent (cyclomatic 28) shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/link/ListViewLinkComponent.kt:79 — ListViewLinkComponentKt.ListViewLinkComponent has cyclomatic complexity 28 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · LinkMenuBtmSheetKt.LinkMenuBtmSheet (cyclomatic 27) · ×1
  • LinkMenuBtmSheetKt.LinkMenuBtmSheet (cyclomatic 27) shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/link/menu/LinkMenuBtmSheet.kt:79 — LinkMenuBtmSheetKt.LinkMenuBtmSheet has cyclomatic complexity 27 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · DesktopNavigationRailKt.DesktopNavigationRail (cyclomatic 25) · ×1
  • DesktopNavigationRailKt.DesktopNavigationRail (cyclomatic 25) shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/nav/DesktopNavigationRail.kt:48 — DesktopNavigationRailKt.DesktopNavigationRail has cyclomatic complexity 25 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · FolderMenuBtmSheetKt.FolderMenuBtmSheet (cyclomatic 23) · ×1
  • FolderMenuBtmSheetKt.FolderMenuBtmSheet (cyclomatic 23) shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/folder/menu/FolderMenuBtmSheet.kt:49 — FolderMenuBtmSheetKt.FolderMenuBtmSheet has cyclomatic complexity 23 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · WebPageCaptureScreenKt.WebPageCaptureScreen (cyclomatic 22) · ×1
  • WebPageCaptureScreenKt.WebPageCaptureScreen (cyclomatic 22) shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/settings/section/data/capture/WebPageCaptureScreen.kt:72 — WebPageCaptureScreenKt.WebPageCaptureScreen 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.
D1 · Cyclomatic Complexity · AddANewLinkDialogKt.TopPartOfAddANewLinkDialogBox (cyclomatic 21) · ×1
  • AddANewLinkDialogKt.TopPartOfAddANewLinkDialogBox (cyclomatic 21) shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/link/AddANewLinkDialog.kt:387 — AddANewLinkDialogKt.TopPartOfAddANewLinkDialogBox has cyclomatic complexity 21 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · ServerSetupScreenKt.ServerSetupScreen (cyclomatic 20) · ×1
  • ServerSetupScreenKt.ServerSetupScreen (cyclomatic 20) shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/settings/section/data/sync/ServerSetupScreen.kt:77 — ServerSetupScreenKt.ServerSetupScreen has cyclomatic complexity 20 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · MobileBottomNavBarKt.MobileBottomNavBar (cyclomatic 18) · ×1
  • MobileBottomNavBarKt.MobileBottomNavBar (cyclomatic 18) shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/nav/MobileBottomNavBar.kt:44 — MobileBottomNavBarKt.MobileBottomNavBar has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
D1 · Cyclomatic Complexity · SnapshotsScreenKt.SnapshotsScreen (cyclomatic 18) · ×1
  • SnapshotsScreenKt.SnapshotsScreen (cyclomatic 18) shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/settings/section/data/snapshots/SnapshotsScreen.kt:70 — SnapshotsScreenKt.SnapshotsScreen has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · ImportDataRepoImpl.importDataFromHTML (cyclomatic 17) · ×1
  • ImportDataRepoImpl.importDataFromHTML (cyclomatic 17) shared/src/commonMain/kotlin/com/sakethh/linkora/data/ImportDataRepoImpl.kt:259 — ImportDataRepoImpl.importDataFromHTML has cyclomatic complexity 17 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
D1 · Cyclomatic Complexity · FolderComponentKt.FolderComponent (cyclomatic 16) · ×1
  • FolderComponentKt.FolderComponent (cyclomatic 16) shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/folder/FolderComponent.kt:52 — FolderComponentKt.FolderComponent has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · LinkMobileMenuKt.LinkMobileMenu (cyclomatic 16) · ×1
  • LinkMobileMenuKt.LinkMobileMenu (cyclomatic 16) shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/link/menu/LinkMobileMenu.kt:54 — LinkMobileMenuKt.LinkMobileMenu has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · SettingComponentKt.SettingComponent (cyclomatic 16) · ×1
  • SettingComponentKt.SettingComponent (cyclomatic 16) shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/settings/common/composables/SettingComponent.kt:41 — SettingComponentKt.SettingComponent 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.
D2 · Cognitive Complexity · LocalDataUpdateService.updateLocalDBAccordingToEvent (cognitive 127) · ×1
  • LocalDataUpdateService.updateLocalDBAccordingToEvent (cognitive 127) shared/src/commonMain/kotlin/com/sakethh/linkora/data/remote/repository/sync/LocalDataUpdateService.kt:76 — LocalDataUpdateService.updateLocalDBAccordingToEvent has cognitive complexity 127 (threshold 15). Drivers by points: if/else 61 (119 pts), match/switch 2 (4 pts), boolean chains 2, error handling 2 (nesting depth added 60). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · CollectionLayoutManagerKt.CollectionLayoutManager (cognitive 102) · ×1
  • CollectionLayoutManagerKt.CollectionLayoutManager (cognitive 102) shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/CollectionLayoutManager.kt:73 — CollectionLayoutManagerKt.CollectionLayoutManager has cognitive complexity 102 (threshold 15). Drivers by points: if/else 48 (79 pts), match/switch 7 (13 pts), boolean chains 10 (nesting depth added 37). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · AddANewLinkDialogKt.BottomPartOfAddANewLinkDialogBox (cognitive 79) · ×1
  • AddANewLinkDialogKt.BottomPartOfAddANewLinkDialogBox (cognitive 79) shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/link/AddANewLinkDialog.kt:661 — AddANewLinkDialogKt.BottomPartOfAddANewLinkDialogBox has cognitive complexity 79 (threshold 15). Drivers by points: if/else 46 (66 pts), error handling 3 (7 pts), boolean chains 5, match/switch 1 (nesting depth added 24). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · DataSettingsScreenKt.DataSettingsScreen (cognitive 72) · ×1
  • DataSettingsScreenKt.DataSettingsScreen (cognitive 72) shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/settings/section/data/DataSettingsScreen.kt:125 — DataSettingsScreenKt.DataSettingsScreen has cognitive complexity 72 (threshold 15). Drivers by points: if/else 37 (64 pts), error handling 2 (4 pts), loops 1 (2 pts), boolean chains 1, match/switch 1 (nesting depth added 30). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · BottomNavOnSelectionKt.BottomNavOnSelection (cognitive 71) · ×1
  • BottomNavOnSelectionKt.BottomNavOnSelection (cognitive 71) shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/nav/BottomNavOnSelection.kt:72 — BottomNavOnSelectionKt.BottomNavOnSelection has cognitive complexity 71 (threshold 15). Drivers by points: if/else 36 (61 pts), boolean chains 10 (nesting depth added 25). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · GridViewLinkComponentKt.GridViewLinkComponent (cognitive 56) · ×1
  • GridViewLinkComponentKt.GridViewLinkComponent (cognitive 56) shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/link/GridViewLinkComponent.kt:67 — GridViewLinkComponentKt.GridViewLinkComponent has cognitive complexity 56 (threshold 15). Drivers by points: if/else 35 (44 pts), boolean chains 12 (nesting depth added 9). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · PendingQueueService.pushPendingSyncQueueToServer (cognitive 54) · ×1
  • PendingQueueService.pushPendingSyncQueueToServer (cognitive 54) shared/src/commonMain/kotlin/com/sakethh/linkora/data/remote/repository/sync/PendingQueueService.kt:80 — PendingQueueService.pushPendingSyncQueueToServer has cognitive complexity 54 (threshold 15). Drivers by points: if/else 26 (49 pts), boolean chains 4, match/switch 1 (nesting depth added 23). 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.
D2 · Cognitive Complexity · CollectionsScreenKt.CollectionsScreen (cognitive 51) · ×1
  • CollectionsScreenKt.CollectionsScreen (cognitive 51) shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/collections/CollectionsScreen.kt:132 — CollectionsScreenKt.CollectionsScreen has cognitive complexity 51 (threshold 15). Drivers by points: if/else 32 (39 pts), boolean chains 11, match/switch 1 (nesting depth added 7). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · LocalLinksRepoImpl.addANewLink (cognitive 50) · ×1
  • LocalLinksRepoImpl.addANewLink (cognitive 50) shared/src/commonMain/kotlin/com/sakethh/linkora/data/local/repository/LocalLinksRepoImpl.kt:84 — LocalLinksRepoImpl.addANewLink has cognitive complexity 50 (threshold 15). Drivers by points: if/else 26 (36 pts), boolean chains 6, match/switch 2 (6 pts), error handling 1 (2 pts) (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · CollectionDetailPaneKt.CollectionDetailPane (cognitive 50) · ×1
  • CollectionDetailPaneKt.CollectionDetailPane (cognitive 50) shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/collections/CollectionDetailPane.kt:113 — CollectionDetailPaneKt.CollectionDetailPane has cognitive complexity 50 (threshold 15). Drivers by points: if/else 24 (37 pts), boolean chains 11, match/switch 1 (2 pts) (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · RegularFunctionsKt.getAppColorScheme (cognitive 49) · ×1
  • RegularFunctionsKt.getAppColorScheme (cognitive 49) shared/src/androidMain/kotlin/com/sakethh/linkora/utils/RegularFunctions.kt:141 — RegularFunctionsKt.getAppColorScheme has cognitive complexity 49 (threshold 15). Drivers by points: if/else 25 (47 pts), boolean chains 1, match/switch 1 (nesting depth added 22). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ListViewLinkComponentKt.ListViewLinkComponent (cognitive 42) · ×1
  • ListViewLinkComponentKt.ListViewLinkComponent (cognitive 42) shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/link/ListViewLinkComponent.kt:79 — ListViewLinkComponentKt.ListViewLinkComponent has cognitive complexity 42 (threshold 15). Drivers by points: if/else 28 (33 pts), boolean chains 9 (nesting depth added 5). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · SnapshotsScreenKt.SnapshotsScreen (cognitive 42) · ×1
  • SnapshotsScreenKt.SnapshotsScreen (cognitive 42) shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/settings/section/data/snapshots/SnapshotsScreen.kt:70 — SnapshotsScreenKt.SnapshotsScreen has cognitive complexity 42 (threshold 15). Drivers by points: if/else 18 (33 pts), error handling 2 (6 pts), match/switch 1 (2 pts), boolean chains 1 (nesting depth added 20). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · WebPageCaptureScreenKt.WebPageCaptureScreen (cognitive 38) · ×1
  • WebPageCaptureScreenKt.WebPageCaptureScreen (cognitive 38) shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/settings/section/data/capture/WebPageCaptureScreen.kt:72 — WebPageCaptureScreenKt.WebPageCaptureScreen has cognitive complexity 38 (threshold 15). Drivers by points: if/else 17 (29 pts), error handling 2 (4 pts), boolean chains 3, match/switch 1 (2 pts) (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · LinkMenuBtmSheetKt.LinkMenuBtmSheet (cognitive 37) · ×1
  • LinkMenuBtmSheetKt.LinkMenuBtmSheet (cognitive 37) shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/link/menu/LinkMenuBtmSheet.kt:79 — LinkMenuBtmSheetKt.LinkMenuBtmSheet has cognitive complexity 37 (threshold 15). Drivers by points: if/else 30 (33 pts), boolean chains 4 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · AppKt.App (cognitive 36) · ×1
  • AppKt.App (cognitive 36) shared/src/commonMain/kotlin/com/sakethh/linkora/ui/App.kt:134 — AppKt.App has cognitive complexity 36 (threshold 15). Drivers by points: if/else 22 (26 pts), boolean chains 9, match/switch 1 (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · AddANewLinkDialogKt.TopPartOfAddANewLinkDialogBox (cognitive 31) · ×1
  • AddANewLinkDialogKt.TopPartOfAddANewLinkDialogBox (cognitive 31) shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/link/AddANewLinkDialog.kt:387 — AddANewLinkDialogKt.TopPartOfAddANewLinkDialogBox has cognitive complexity 31 (threshold 15). Drivers by points: if/else 20 (26 pts), boolean chains 4, match/switch 1 (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.
D2 · Cognitive Complexity · ServerSetupScreenKt.ServerSetupScreen (cognitive 31) · ×1
  • ServerSetupScreenKt.ServerSetupScreen (cognitive 31) shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/settings/section/data/sync/ServerSetupScreen.kt:77 — ServerSetupScreenKt.ServerSetupScreen has cognitive complexity 31 (threshold 15). Drivers by points: if/else 23 (27 pts), boolean chains 4 (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · FolderMenuBtmSheetKt.FolderMenuBtmSheet (cognitive 30) · ×1
  • FolderMenuBtmSheetKt.FolderMenuBtmSheet (cognitive 30) shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/folder/menu/FolderMenuBtmSheet.kt:49 — FolderMenuBtmSheetKt.FolderMenuBtmSheet has cognitive complexity 30 (threshold 15). Drivers by points: if/else 22 (25 pts), boolean chains 5 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · DesktopNavigationRailKt.DesktopNavigationRail (cognitive 28) · ×1
  • DesktopNavigationRailKt.DesktopNavigationRail (cognitive 28) shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/nav/DesktopNavigationRail.kt:48 — DesktopNavigationRailKt.DesktopNavigationRail has cognitive complexity 28 (threshold 15). Drivers by points: if/else 15 (18 pts), boolean chains 6, match/switch 2 (4 pts) (nesting depth added 5). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · SettingComponentKt.SettingComponent (cognitive 28) · ×1
  • SettingComponentKt.SettingComponent (cognitive 28) shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/settings/common/composables/SettingComponent.kt:41 — SettingComponentKt.SettingComponent has cognitive complexity 28 (threshold 15). Drivers by points: if/else 20 (25 pts), boolean chains 3 (nesting depth added 5). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · RenameLinkDialogParamKt.RenameLinkDialog (cognitive 27) · ×1
  • RenameLinkDialogParamKt.RenameLinkDialog (cognitive 27) shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/link/RenameLinkDialogParam.kt:94 — RenameLinkDialogParamKt.RenameLinkDialog has cognitive complexity 27 (threshold 15). Drivers by points: if/else 14 (26 pts), boolean chains 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · LinkMobileMenuKt.LinkMobileMenu (cognitive 27) · ×1
  • LinkMobileMenuKt.LinkMobileMenu (cognitive 27) shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/link/menu/LinkMobileMenu.kt:54 — LinkMobileMenuKt.LinkMobileMenu has cognitive complexity 27 (threshold 15). Drivers by points: if/else 17 (23 pts), boolean chains 4 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · FolderComponentKt.FolderComponent (cognitive 25) · ×1
  • FolderComponentKt.FolderComponent (cognitive 25) shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/folder/FolderComponent.kt:52 — FolderComponentKt.FolderComponent has cognitive complexity 25 (threshold 15). Drivers by points: if/else 19 (22 pts), boolean chains 3 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · ImportDataRepoImpl.importDataFromHTML (cognitive 23) · ×1
  • ImportDataRepoImpl.importDataFromHTML (cognitive 23) shared/src/commonMain/kotlin/com/sakethh/linkora/data/ImportDataRepoImpl.kt:259 — ImportDataRepoImpl.importDataFromHTML has cognitive complexity 23 (threshold 15). Drivers by points: if/else 7 (9 pts), match/switch 3 (8 pts), error handling 1 (4 pts), boolean chains 1, loops 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · HomeScreenKt.HomeScreen (cognitive 23) · ×1
  • HomeScreenKt.HomeScreen (cognitive 23) shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/home/HomeScreen.kt:83 — HomeScreenKt.HomeScreen has cognitive complexity 23 (threshold 15). Drivers by points: if/else 17 (21 pts), boolean chains 2 (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · RenameFolderDialogKt.RenameFolderDialog (cognitive 21) · ×1
  • RenameFolderDialogKt.RenameFolderDialog (cognitive 21) shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/folder/RenameFolderDialog.kt:75 — RenameFolderDialogKt.RenameFolderDialog has cognitive complexity 21 (threshold 15). Drivers by points: if/else 11 (20 pts), boolean chains 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ExportDataRepoImpl.foldersSectionInHtml (cognitive 18) · ×1
  • ExportDataRepoImpl.foldersSectionInHtml (cognitive 18) shared/src/commonMain/kotlin/com/sakethh/linkora/data/ExportDataRepoImpl.kt:375 — ExportDataRepoImpl.foldersSectionInHtml has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (17 pts), loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · LocalMultiActionRepoImpl.copyFolders (cognitive 17) · ×1
  • LocalMultiActionRepoImpl.copyFolders (cognitive 17) shared/src/commonMain/kotlin/com/sakethh/linkora/data/local/repository/LocalMultiActionRepoImpl.kt:320 — LocalMultiActionRepoImpl.copyFolders has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (16 pts), loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · MobileBottomNavBarKt.MobileBottomNavBar (cognitive 17) · ×1
  • MobileBottomNavBarKt.MobileBottomNavBar (cognitive 17) shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/nav/MobileBottomNavBar.kt:44 — MobileBottomNavBarKt.MobileBottomNavBar has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9, boolean chains 4, match/switch 2 (4 pts) (nesting depth added 2). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · LocalLinksRepoImpl.scrapeLinkData (cognitive 16) · ×1
  • LocalLinksRepoImpl.scrapeLinkData (cognitive 16) shared/src/commonMain/kotlin/com/sakethh/linkora/data/local/repository/LocalLinksRepoImpl.kt:424 — LocalLinksRepoImpl.scrapeLinkData has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (11 pts), boolean chains 2, match/switch 2, error handling 1 (nesting depth added 3). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D4 · Code Duplication · Near-duplicate member family (4 members, 40 shared lines) · ×1
  • Near-duplicate member family (4 members, 40 shared lines) shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/DeleteAllDataDialogParam.kt:41 — shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/DeleteAllDataDialogParam.kt:41-135 | shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/DeleteSelectedItemsDialogParam.kt:29-95 | shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/folder/DeleteFolderDialog.kt:31-109 | shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/link/DeleteLinkDialogParam.kt:29-96 — These 4 members are variants of one another: a block of 40 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 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 · Near-duplicate member pair (138 shared lines) · ×1
  • Near-duplicate member pair (138 shared lines) shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/folder/RenameFolderDialog.kt:75 — shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/folder/RenameFolderDialog.kt:75-229 | shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/link/RenameLinkDialogParam.kt:94-321 — These two members are variants of one another: 138 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.
D4 · Code Duplication · Near-duplicate member pair (94 shared lines) · ×1
  • Near-duplicate member pair (94 shared lines) shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/folder/menu/FolderMenuBtmSheet.kt:52 — shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/folder/menu/FolderMenuBtmSheet.kt:52-248 | shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/link/menu/LinkMenuBtmSheet.kt:82-426 — These two members are variants of one another: 94 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.
D4 · Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) · ×1
  • Members sharing a duplicated core (4 members, 50+ identical tokens) shared/src/androidMain/kotlin/com/sakethh/linkora/worker/AllLinksWebCaptureWorker.kt:76 — shared/src/androidMain/kotlin/com/sakethh/linkora/worker/AllLinksWebCaptureWorker.kt:76-251 | shared/src/androidMain/kotlin/com/sakethh/linkora/worker/WebCaptureWorker.kt:70-215 | shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/settings/SettingsScreenViewModel.kt:709-743 | shared/src/desktopMain/kotlin/com/sakethh/linkora/AllLinksWebCaptureService.kt:46-166 — 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 (68 corresponding lines) · ×1
  • Edited copy of a member (68 corresponding lines) shared/src/androidMain/kotlin/com/sakethh/linkora/platform/Expected.android.kt:119 — shared/src/androidMain/kotlin/com/sakethh/linkora/platform/Expected.android.kt:119-186 | shared/src/desktopMain/kotlin/com/sakethh/linkora/platform/Expected.desktop.kt:219-286 — These two members are one piece of code written twice and then edited apart: 68 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 (82 corresponding lines) · ×1
  • Edited copy of a member (82 corresponding lines) shared/src/androidMain/kotlin/com/sakethh/linkora/platform/FileManager.kt:302 — shared/src/androidMain/kotlin/com/sakethh/linkora/platform/FileManager.kt:302-383 | shared/src/desktopMain/kotlin/com/sakethh/linkora/platform/FileManager.kt:218-302 — These two members are one piece of code written twice and then edited apart: 82 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 (59 corresponding lines) · ×1
  • Edited copy of a member (59 corresponding lines) shared/src/commonMain/kotlin/com/sakethh/linkora/data/local/repository/LocalPanelsRepoImpl.kt:37 — shared/src/commonMain/kotlin/com/sakethh/linkora/data/local/repository/LocalPanelsRepoImpl.kt:37-95 | shared/src/commonMain/kotlin/com/sakethh/linkora/data/local/repository/LocalPanelsRepoImpl.kt:208-280 — These two members are one piece of code written twice and then edited apart: 59 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 (36 corresponding lines) · ×1
  • Edited copy of a member (36 corresponding lines) shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/LoadingDialog.kt:34 — shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/LoadingDialog.kt:34-73 | shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/settings/section/about/LodingDialogBox.kt:36-71 — These two members are one piece of code written twice and then edited apart: 36 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (48 corresponding lines) · ×1
  • Edited copy of a member (48 corresponding lines) shared/src/commonMain/kotlin/com/sakethh/linkora/data/local/repository/LocalMultiActionRepoImpl.kt:50 — shared/src/commonMain/kotlin/com/sakethh/linkora/data/local/repository/LocalMultiActionRepoImpl.kt:50-97 | shared/src/commonMain/kotlin/com/sakethh/linkora/data/local/repository/LocalMultiActionRepoImpl.kt:158-213 — These two members are one piece of code written twice and then edited apart: 48 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (44 corresponding lines) · ×1
  • Edited copy of a member (44 corresponding lines) shared/src/commonMain/kotlin/com/sakethh/linkora/data/local/repository/LocalTagsRepoImpl.kt:110 — shared/src/commonMain/kotlin/com/sakethh/linkora/data/local/repository/LocalTagsRepoImpl.kt:110-153 | shared/src/commonMain/kotlin/com/sakethh/linkora/data/local/repository/LocalTagsRepoImpl.kt:185-231 — These two members are one piece of code written twice and then edited apart: 44 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 (42 corresponding lines) · ×1
  • Edited copy of a member (42 corresponding lines) shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/link/ListViewLinkComponent.kt:400 — shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/link/ListViewLinkComponent.kt:400-441 | shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/link/ListViewLinkComponent.kt:453-500 — These two members are one piece of code written twice and then edited apart: 42 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 (37 corresponding lines) · ×1
  • Edited copy of a member (37 corresponding lines) shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/HorizontalInfoCard.kt:30 — shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/HorizontalInfoCard.kt:30-71 | shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/VerticalInfoCard.kt:28-64 — 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.
D4 · Code Duplication · Edited copies of one member (4 members, 43+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 43+ corresponding lines) shared/src/commonMain/kotlin/com/sakethh/linkora/data/local/repository/LocalLinksRepoImpl.kt:562 — shared/src/commonMain/kotlin/com/sakethh/linkora/data/local/repository/LocalLinksRepoImpl.kt:562-604 | shared/src/commonMain/kotlin/com/sakethh/linkora/data/local/repository/LocalPanelsRepoImpl.kt:102-145 | shared/src/commonMain/kotlin/com/sakethh/linkora/data/local/repository/LocalPanelsRepoImpl.kt:151-195 | shared/src/commonMain/kotlin/com/sakethh/linkora/data/local/repository/LocalPanelsRepoImpl.kt:293-338 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 43 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (7 members, 42+ corresponding lines) · ×1
  • Edited copies of one member (7 members, 42+ corresponding lines) shared/src/commonMain/kotlin/com/sakethh/linkora/data/local/repository/LocalFoldersRepoImpl.kt:225 — shared/src/commonMain/kotlin/com/sakethh/linkora/data/local/repository/LocalFoldersRepoImpl.kt:225-267 | shared/src/commonMain/kotlin/com/sakethh/linkora/data/local/repository/LocalFoldersRepoImpl.kt:272-315 | shared/src/commonMain/kotlin/com/sakethh/linkora/data/local/repository/LocalFoldersRepoImpl.kt:381-422 | shared/src/commonMain/kotlin/com/sakethh/linkora/data/local/repository/LocalLinksRepoImpl.kt:513-557 | shared/src/commonMain/kotlin/com/sakethh/linkora/data/local/repository/LocalLinksRepoImpl.kt:616-658 | shared/src/commonMain/kotlin/com/sakethh/linkora/data/local/repository/LocalLinksRepoImpl.kt:664-708 | shared/src/commonMain/kotlin/com/sakethh/linkora/data/local/repository/LocalLinksRepoImpl.kt:714-758 — These 7 members are one piece of code written 7 times and then edited apart: every two of them correspond over at least 42 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 7 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (41 corresponding lines) · ×1
  • Edited copy of a member (41 corresponding lines) shared/src/commonMain/kotlin/com/sakethh/linkora/data/local/repository/LocalFoldersRepoImpl.kt:427 — shared/src/commonMain/kotlin/com/sakethh/linkora/data/local/repository/LocalFoldersRepoImpl.kt:427-475 | shared/src/commonMain/kotlin/com/sakethh/linkora/data/local/repository/LocalFoldersRepoImpl.kt:516-556 — These two members are one piece of code written twice and then edited apart: 41 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (33 corresponding lines) · ×1
  • Edited copy of a member (33 corresponding lines) shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/settings/section/LanguageSettingsScreenVM.kt:73 — shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/settings/section/LanguageSettingsScreenVM.kt:73-115 | shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/settings/section/LanguageSettingsScreenVM.kt:161-193 — These two members are one piece of code written twice and then edited apart: 33 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 (35 corresponding lines) · ×1
  • Edited copy of a member (35 corresponding lines) shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/search/SearchScreenVM.kt:276 — shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/search/SearchScreenVM.kt:276-311 | shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/settings/section/about/AboutSettingsScreenVM.kt:37-71 — These two members are one piece of code written twice and then edited apart: 35 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (21 corresponding lines) · ×1
  • Edited copy of a member (21 corresponding lines) shared/src/desktopMain/kotlin/com/sakethh/linkora/platform/FileManager.kt:147 — shared/src/desktopMain/kotlin/com/sakethh/linkora/platform/FileManager.kt:147-174 | shared/src/desktopMain/kotlin/com/sakethh/linkora/platform/FileManager.kt:180-200 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (28 corresponding lines) · ×1
  • Edited copy of a member (28 corresponding lines) shared/src/commonMain/kotlin/com/sakethh/linkora/ui/AppVM.kt:334 — shared/src/commonMain/kotlin/com/sakethh/linkora/ui/AppVM.kt:334-367 | shared/src/commonMain/kotlin/com/sakethh/linkora/ui/AppVM.kt:372-399 — These two members are one piece of code written twice and then edited apart: 28 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, 17+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 17+ corresponding lines) shared/src/commonMain/kotlin/com/sakethh/linkora/data/local/repository/LocalLinksRepoImpl.kt:325 — shared/src/commonMain/kotlin/com/sakethh/linkora/data/local/repository/LocalLinksRepoImpl.kt:325-343 | shared/src/commonMain/kotlin/com/sakethh/linkora/data/local/repository/LocalLinksRepoImpl.kt:1157-1177 | shared/src/commonMain/kotlin/com/sakethh/linkora/data/local/repository/LocalTagsRepoImpl.kt:163-179 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 17 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 (15 corresponding lines) · ×1
  • Edited copy of a member (15 corresponding lines) shared/src/commonMain/kotlin/com/sakethh/linkora/domain/Mappers.kt:97 — shared/src/commonMain/kotlin/com/sakethh/linkora/domain/Mappers.kt:97-111 | shared/src/commonMain/kotlin/com/sakethh/linkora/domain/Mappers.kt:118-133 — 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 (13 corresponding lines) · ×1
  • Edited copy of a member (13 corresponding lines) shared/src/commonMain/kotlin/com/sakethh/linkora/utils/RegularFunctions.kt:76 — shared/src/commonMain/kotlin/com/sakethh/linkora/utils/RegularFunctions.kt:76-89 | shared/src/commonMain/kotlin/com/sakethh/linkora/utils/RegularFunctions.kt:100-112 — 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 (14 corresponding lines) · ×1
  • Edited copy of a member (14 corresponding lines) shared/src/androidMain/kotlin/com/sakethh/linkora/platform/NativeUtils.kt:95 — shared/src/androidMain/kotlin/com/sakethh/linkora/platform/NativeUtils.kt:95-108 | shared/src/androidMain/kotlin/com/sakethh/linkora/platform/NativeUtils.kt:254-272 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (18 corresponding lines) · ×1
  • Edited copy of a member (18 corresponding lines) shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/home/panels/SpecificPanelManagerScreenVM.kt:204 — shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/home/panels/SpecificPanelManagerScreenVM.kt:204-222 | shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/home/panels/SpecificPanelManagerScreenVM.kt:321-338 — 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 (10 corresponding lines) · ×1
  • Edited copy of a member (10 corresponding lines) shared/src/desktopMain/kotlin/com/sakethh/linkora/platform/FileManager.kt:202 — shared/src/desktopMain/kotlin/com/sakethh/linkora/platform/FileManager.kt:202-212 | shared/src/desktopMain/kotlin/com/sakethh/linkora/platform/FileManager.kt:304-313 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 23+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 23+ corresponding lines) shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/collections/CollectionsScreenVM.kt:484 — shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/collections/CollectionsScreenVM.kt:484-506 | shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/collections/CollectionsScreenVM.kt:618-645 | shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/home/panels/SpecificPanelManagerScreenVM.kt:227-250 | shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/home/panels/SpecificPanelManagerScreenVM.kt:292-316 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 23 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Duplicated block (61 lines × 2) · ×1
  • Duplicated block (61 lines × 2) shared/src/androidMain/kotlin/com/sakethh/linkora/platform/Expected.android.kt:126 — shared/src/androidMain/kotlin/com/sakethh/linkora/platform/Expected.android.kt:126-186 | shared/src/desktopMain/kotlin/com/sakethh/linkora/platform/Expected.desktop.kt:226-286 — before extracting anything, compare `shared/src/androidMain/kotlin/com/sakethh/linkora/platform/Expected.android.kt` and `shared/src/desktopMain/kotlin/com/sakethh/linkora/platform/Expected.desktop.kt` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 79 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `shared/src/androidMain/kotlin/com/sakethh/linkora/platform/Expected.android.kt:126` 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.
D4 · Code Duplication · Duplicated block (54 lines × 2) · ×1
  • Duplicated block (54 lines × 2) shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/folder/RenameFolderDialog.kt:176 — shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/folder/RenameFolderDialog.kt:176-229 | shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/link/RenameLinkDialogParam.kt:268-321 — before extracting anything, compare `shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/folder/RenameFolderDialog.kt` and `shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/link/RenameLinkDialogParam.kt` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 158 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/folder/RenameFolderDialog.kt:176` 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.
D4 · Code Duplication · Duplicated block (47 lines × 2) · ×1
  • Duplicated block (47 lines × 2) shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/folder/menu/FolderMobileMenu.kt:71 — shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/folder/menu/FolderMobileMenu.kt:71-117 | shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/link/menu/LinkMobileMenu.kt:208-254 — 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 `shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/folder/menu/FolderMobileMenu.kt:71` 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.
D4 · Code Duplication · Duplicated block (40 lines × 2) · ×1
  • Duplicated block (40 lines × 2) shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/folder/menu/FolderMenuBtmSheet.kt:92 — shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/folder/menu/FolderMenuBtmSheet.kt:92-131 | shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/link/menu/LinkMenuBtmSheet.kt:187-226 — before extracting anything, compare `shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/folder/menu/FolderMenuBtmSheet.kt` and `shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/link/menu/LinkMenuBtmSheet.kt` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 95 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/folder/menu/FolderMenuBtmSheet.kt:92` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (35–36 lines × 2) · ×1
  • Duplicated block (35–36 lines × 2) shared/src/androidMain/kotlin/com/sakethh/linkora/platform/FileManager.kt:344 — shared/src/androidMain/kotlin/com/sakethh/linkora/platform/FileManager.kt:344-378 | shared/src/desktopMain/kotlin/com/sakethh/linkora/platform/FileManager.kt:265-300 — 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 `shared/src/androidMain/kotlin/com/sakethh/linkora/platform/FileManager.kt:344` 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.
D4 · Code Duplication · Duplicated block (35 lines × 2) · ×1
  • Duplicated block (35 lines × 2) shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/LoadingDialog.kt:39 — shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/LoadingDialog.kt:39-73 | shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/settings/section/about/LodingDialogBox.kt:37-71 — before extracting anything, compare `shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/LoadingDialog.kt` and `shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/settings/section/about/LodingDialogBox.kt` as WHOLE FILES: 88% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/LoadingDialog.kt:39` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (31–32 lines × 2) · ×1
  • Duplicated block (31–32 lines × 2) shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/folder/menu/FolderMenuBtmSheet.kt:211 — shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/folder/menu/FolderMenuBtmSheet.kt:211-242 | shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/link/menu/LinkMenuBtmSheet.kt:390-420 — before extracting anything, compare `shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/folder/menu/FolderMenuBtmSheet.kt` and `shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/link/menu/LinkMenuBtmSheet.kt` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 95 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/folder/menu/FolderMenuBtmSheet.kt:211` 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.
D4 · Code Duplication · Duplicated block (30–31 lines × 3) · ×1
  • Duplicated block (30–31 lines × 3) shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/onboarding/OnboardingSlidesScreen.kt:304 — shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/onboarding/OnboardingSlidesScreen.kt:304-333 | shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/onboarding/OnboardingSlidesScreen.kt:524-554 | shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/onboarding/OnboardingSlidesScreen.kt:599-629 — 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 `shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/onboarding/OnboardingSlidesScreen.kt:304` 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. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/onboarding/OnboardingSlidesScreen.kt:333` calls `Link` and `shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/onboarding/OnboardingSlidesScreen.kt:554` 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.
D4 · Code Duplication · Duplicated block (29 lines × 4) · ×1
  • Duplicated block (29 lines × 4) shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/DeleteAllDataDialogParam.kt:65 — shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/DeleteAllDataDialogParam.kt:65-93 | shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/DeleteSelectedItemsDialogParam.kt:49-77 | shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/folder/DeleteFolderDialog.kt:51-79 | shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/link/DeleteLinkDialogParam.kt:49-77 — before extracting anything, compare `shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/DeleteSelectedItemsDialogParam.kt` and `shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/link/DeleteLinkDialogParam.kt` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 56 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/DeleteAllDataDialogParam.kt:65` 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.
D4 · Code Duplication · Duplicated block (26–27 lines × 2) · ×1
  • Duplicated block (26–27 lines × 2) shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/collections/CollectionDetailPane.kt:468 — shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/collections/CollectionDetailPane.kt:468-494 | shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/collections/CollectionsScreen.kt:618-643 — 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 `shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/collections/CollectionDetailPane.kt:468` 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.
D4 · Code Duplication · Duplicated block (25–26 lines × 2) · ×1
  • Duplicated block (25–26 lines × 2) shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/link/AddANewLinkDialog.kt:239 — shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/link/AddANewLinkDialog.kt:239-263 | shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/link/AddANewLinkDialog.kt:295-320 — 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 `shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/link/AddANewLinkDialog.kt:239` 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.
D4 · Code Duplication · Duplicated block (26 lines × 2) · ×1
  • Duplicated block (26 lines × 2) shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/link/ListViewLinkComponent.kt:406 — shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/link/ListViewLinkComponent.kt:406-431 | shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/link/ListViewLinkComponent.kt:459-484 — 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 `shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/link/ListViewLinkComponent.kt:406` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (24–25 lines × 2) · ×1
  • Duplicated block (24–25 lines × 2) shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/collections/CollectionDetailPane.kt:412 — shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/collections/CollectionDetailPane.kt:412-435 | shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/collections/CollectionsScreen.kt:565-589 — 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 `shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/collections/CollectionDetailPane.kt:412` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note 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.
D4 · Code Duplication · Duplicated block (24 lines × 2) · ×1
  • Duplicated block (24 lines × 2) shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/link/AddANewLinkDialog.kt:570 — shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/link/AddANewLinkDialog.kt:570-593 | shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/link/AddANewLinkDialog.kt:611-634 — 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 `shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/link/AddANewLinkDialog.kt:570` 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.
D4 · Code Duplication · Duplicated block (22–23 lines × 4) · ×1
  • Duplicated block (22–23 lines × 4) shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/collections/CollectionsScreen.kt:717 — shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/collections/CollectionsScreen.kt:717-739 | shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/onboarding/OnboardingSlidesScreen.kt:307-328 | shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/onboarding/OnboardingSlidesScreen.kt:527-548 | shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/onboarding/OnboardingSlidesScreen.kt:602-623 — there are 4 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 4 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/collections/CollectionsScreen.kt:717` 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.
D4 · Code Duplication · Duplicated block (22–23 lines × 2) · ×1
  • Duplicated block (22–23 lines × 2) shared/src/commonMain/kotlin/com/sakethh/linkora/data/ExportDataRepoImpl.kt:239 — shared/src/commonMain/kotlin/com/sakethh/linkora/data/ExportDataRepoImpl.kt:239-261 | shared/src/commonMain/kotlin/com/sakethh/linkora/data/ExportDataRepoImpl.kt:347-368 — 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 `shared/src/commonMain/kotlin/com/sakethh/linkora/data/ExportDataRepoImpl.kt:239` 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.
D4 · Code Duplication · Duplicated block (19–20 lines × 2) · ×1
  • Duplicated block (19–20 lines × 2) shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/folder/RenameFolderDialog.kt:87 — shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/folder/RenameFolderDialog.kt:87-106 | shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/link/RenameLinkDialogParam.kt:118-136 — before extracting anything, compare `shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/folder/RenameFolderDialog.kt` and `shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/link/RenameLinkDialogParam.kt` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 158 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/folder/RenameFolderDialog.kt:87` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (18–20 lines × 2) · ×1
  • Duplicated block (18–20 lines × 2) shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/settings/section/about/AboutScreen.kt:145 — shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/settings/section/about/AboutScreen.kt:145-164 | shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/settings/section/data/DataSettingsScreen.kt:826-843 — 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 `shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/settings/section/about/AboutScreen.kt:145` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (15–19 lines × 2) · ×1
  • Duplicated block (15–19 lines × 2) shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/collections/CollectionDetailPane.kt:296 — shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/collections/CollectionDetailPane.kt:296-314 | shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/collections/CollectionDetailPane.kt:591-605 — 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 `shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/collections/CollectionDetailPane.kt:296` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note 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.
D4 · Code Duplication · Duplicated block (17–18 lines × 4) · ×1
  • Duplicated block (17–18 lines × 4) shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/collections/CollectionsScreen.kt:288 — shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/collections/CollectionsScreen.kt:288-304 | shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/collections/CollectionsScreen.kt:320-337 | shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/collections/CollectionsScreen.kt:352-369 | shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/collections/CollectionsScreen.kt:384-400 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/collections/CollectionsScreen.kt:288` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note 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.
D4 · Code Duplication · Duplicated block (6–18 lines × 2) · ×1
  • Duplicated block (6–18 lines × 2) androidApp/src/main/kotlin/com/sakethh/linkora/ShareToSaveActivity.kt:209 — androidApp/src/main/kotlin/com/sakethh/linkora/ShareToSaveActivity.kt:209-214 | shared/src/commonMain/kotlin/com/sakethh/linkora/data/ExportDataRepoImpl.kt:39-56 — 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. 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.
D4 · Code Duplication · Duplicated block (7–17 lines × 3) · ×1
  • Duplicated block (7–17 lines × 3) shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/AddItemFAB.kt:113 — shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/AddItemFAB.kt:113-128 | shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/AddItemFAB.kt:157-173 | shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/AddItemFAB.kt:201-207 — 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 `shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/AddItemFAB.kt:113` 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. 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.
D4 · Code Duplication · Duplicated block (16 lines × 3) · ×1
  • Duplicated block (16 lines × 3) shared/src/androidMain/kotlin/com/sakethh/linkora/worker/AllLinksWebCaptureWorker.kt:85 — shared/src/androidMain/kotlin/com/sakethh/linkora/worker/AllLinksWebCaptureWorker.kt:85-100 | shared/src/androidMain/kotlin/com/sakethh/linkora/worker/WebCaptureWorker.kt:77-92 | shared/src/desktopMain/kotlin/com/sakethh/linkora/AllLinksWebCaptureService.kt:49-64 — before extracting anything, compare `shared/src/androidMain/kotlin/com/sakethh/linkora/worker/AllLinksWebCaptureWorker.kt` and `shared/src/desktopMain/kotlin/com/sakethh/linkora/AllLinksWebCaptureService.kt` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 46 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `shared/src/androidMain/kotlin/com/sakethh/linkora/worker/AllLinksWebCaptureWorker.kt:85` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (15–16 lines × 2) · ×1
  • Duplicated block (15–16 lines × 2) shared/src/commonMain/kotlin/com/sakethh/linkora/data/remote/repository/sync/LocalDataUpdateService.kt:620 — shared/src/commonMain/kotlin/com/sakethh/linkora/data/remote/repository/sync/LocalDataUpdateService.kt:620-634 | shared/src/commonMain/kotlin/com/sakethh/linkora/data/remote/repository/sync/LocalDataUpdateService.kt:715-730 — 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 `shared/src/commonMain/kotlin/com/sakethh/linkora/data/remote/repository/sync/LocalDataUpdateService.kt:620` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (14–16 lines × 2) · ×1
  • Duplicated block (14–16 lines × 2) shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/DeleteSelectedItemsDialogParam.kt:80 — shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/DeleteSelectedItemsDialogParam.kt:80-95 | shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/link/DeleteLinkDialogParam.kt:83-96 — before extracting anything, compare `shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/DeleteSelectedItemsDialogParam.kt` and `shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/link/DeleteLinkDialogParam.kt` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 56 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/DeleteSelectedItemsDialogParam.kt:80` 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.
D4 · Code Duplication · Duplicated block (14 lines × 4) · ×1
  • Duplicated block (14 lines × 4) shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/folder/RenameFolderDialog.kt:131 — shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/folder/RenameFolderDialog.kt:131-144 | shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/link/RenameLinkDialogParam.kt:159-172 | shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/link/RenameLinkDialogParam.kt:174-187 | shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/link/RenameLinkDialogParam.kt:189-202 — before extracting anything, compare `shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/folder/RenameFolderDialog.kt` and `shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/link/RenameLinkDialogParam.kt` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 158 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/folder/RenameFolderDialog.kt:131` 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.
D4 · Code Duplication · Duplicated block (14 lines × 2) · ×1
  • Duplicated block (14 lines × 2) shared/src/commonMain/kotlin/com/sakethh/linkora/data/ExportDataRepoImpl.kt:398 — shared/src/commonMain/kotlin/com/sakethh/linkora/data/ExportDataRepoImpl.kt:398-411 | shared/src/commonMain/kotlin/com/sakethh/linkora/data/ExportDataRepoImpl.kt:524-537 — 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 `shared/src/commonMain/kotlin/com/sakethh/linkora/data/ExportDataRepoImpl.kt:398` 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.
D4 · Code Duplication · Duplicated block (11–12 lines × 2) · ×1
  • Duplicated block (11–12 lines × 2) shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/settings/section/LayoutSettingsScreen.kt:273 — shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/settings/section/LayoutSettingsScreen.kt:273-284 | shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/settings/section/LayoutSettingsScreen.kt:359-369 — 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 `shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/settings/section/LayoutSettingsScreen.kt:273` 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.
D4 · Code Duplication · Duplicated block (11 lines × 4) · ×1
  • Duplicated block (11 lines × 4) shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/DeleteAllDataDialogParam.kt:46 — shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/DeleteAllDataDialogParam.kt:46-56 | shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/DeleteSelectedItemsDialogParam.kt:33-43 | shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/folder/DeleteFolderDialog.kt:35-45 | shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/link/DeleteLinkDialogParam.kt:33-43 — before extracting anything, compare `shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/DeleteSelectedItemsDialogParam.kt` and `shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/link/DeleteLinkDialogParam.kt` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 56 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/DeleteAllDataDialogParam.kt:46` 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 before the matched lines, `shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/DeleteAllDataDialogParam.kt:44` calls `mutableStateOf` and `shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/DeleteSelectedItemsDialogParam.kt:31` 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.
D4 · Code Duplication · Duplicated block (11 lines × 2) · ×1
  • Duplicated block (11 lines × 2) shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/home/panels/SpecificPanelManagerScreen.kt:195 — shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/home/panels/SpecificPanelManagerScreen.kt:195-205 | shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/home/panels/SpecificPanelManagerScreen.kt:243-253 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/home/panels/SpecificPanelManagerScreen.kt:195` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/home/panels/SpecificPanelManagerScreen.kt:254` calls `highlightOnFocused` and `shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/home/panels/SpecificPanelManagerScreen.kt:206` 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.
D4 · Code Duplication · Duplicated block (10 lines × 6) · ×1
  • Duplicated block (10 lines × 6) shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/folder/RenameFolderDialog.kt:131 — shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/folder/RenameFolderDialog.kt:131-140 | shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/folder/RenameFolderDialog.kt:146-155 | shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/link/RenameLinkDialogParam.kt:159-168 | shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/link/RenameLinkDialogParam.kt:174-183 | shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/link/RenameLinkDialogParam.kt:189-198 | shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/link/RenameLinkDialogParam.kt:204-213 — before extracting anything, compare `shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/folder/RenameFolderDialog.kt` and `shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/link/RenameLinkDialogParam.kt` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 158 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/folder/RenameFolderDialog.kt:131` 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.
D4 · Code Duplication · Duplicated block (10 lines × 2) · ×1
  • Duplicated block (10 lines × 2) shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/nav/DesktopNavigationRail.kt:91 — shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/nav/DesktopNavigationRail.kt:91-100 | shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/nav/MobileBottomNavBar.kt:104-113 — 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 `shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/nav/DesktopNavigationRail.kt: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. Note first that the copies are not typed on the same thing: `Folder` names `androidx.compose.material.icons.filled.Folder` in one and `androidx.compose.material.icons.outlined.Folder` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
D4 · Code Duplication · Duplicated block (8 lines × 2) · ×1
  • Duplicated block (8 lines × 2) shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/nav/DesktopNavigationRail.kt:103 — shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/nav/DesktopNavigationRail.kt:103-111 | shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/nav/MobileBottomNavBar.kt:116-123 — 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 `shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/nav/DesktopNavigationRail.kt:103` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: `Folder` names `androidx.compose.material.icons.filled.Folder` in one and `androidx.compose.material.icons.outlined.Folder` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
D4 · Code Duplication · Duplicated block (11 lines × 3) · ×1
  • Duplicated block (11 lines × 3) shared/src/androidMain/kotlin/com/sakethh/linkora/platform/Expected.android.kt:80 — shared/src/androidMain/kotlin/com/sakethh/linkora/platform/Expected.android.kt:80-90 | shared/src/desktopMain/kotlin/com/sakethh/linkora/platform/Expected.desktop.kt:180-190 | shared/src/wasmJsMain/kotlin/platform/Expected.wasmJs.kt:190-200 — before extracting anything, compare `shared/src/androidMain/kotlin/com/sakethh/linkora/platform/Expected.android.kt` and `shared/src/desktopMain/kotlin/com/sakethh/linkora/platform/Expected.desktop.kt` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 79 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (7 lines × 2) · ×1
  • Duplicated block (7 lines × 2) shared/src/androidMain/kotlin/com/sakethh/linkora/platform/Expected.android.kt:204 — shared/src/androidMain/kotlin/com/sakethh/linkora/platform/Expected.android.kt:204-210 | shared/src/desktopMain/kotlin/com/sakethh/linkora/platform/Expected.desktop.kt:312-318 — before extracting anything, compare `shared/src/androidMain/kotlin/com/sakethh/linkora/platform/Expected.android.kt` and `shared/src/desktopMain/kotlin/com/sakethh/linkora/platform/Expected.desktop.kt` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 79 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (22 lines × 2) · ×1
  • Duplicated block (22 lines × 2) shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/collections/CollectionDetailPane.kt:383 — shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/collections/CollectionDetailPane.kt:383-405 | shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/collections/CollectionsScreen.kt:519-540 — 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 `shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/collections/CollectionDetailPane.kt:383` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (18 lines × 3) · ×1
  • Duplicated block (18 lines × 3) shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/settings/SettingsScreenViewModel.kt:447 — shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/settings/SettingsScreenViewModel.kt:447-464 | shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/settings/SettingsScreenViewModel.kt:510-528 | shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/settings/SettingsScreenViewModel.kt:543-560 — 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 `shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/settings/SettingsScreenViewModel.kt:447` 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. 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.
D5 · Coupling · Off the main sequence · ×1
  • Off the main sequence: :web-capture — :web-capture: abstractness 0.25, instability 0.00, distance 0.75 — zone of pain — concrete and depended on by 4 project(s), so it's rigid to change.
P12 · CI test-gate honesty · Test suite runs only after the merge · ×1
  • Test suite runs only after the merge — `REDACTED` run(s) the test suite, but no workflow that runs tests is triggered by a pull request (or a merge queue) — so the suite reports on code that is already on the default branch. A red build there blocks nothing and the only remedy is a revert. Add the pull-request trigger to the workflow that runs your suite so the gate applies before the merge, not after it.
P2 · Observability · No structured logging · ×1
  • No structured logging — No logging or diagnostics emission found. This repository ships a binary its users launch rather than a service you operate, so there is no operator to page — but when a run fails on a user's machine, neither they nor you have anything to read.
X3 · Exception handling · Swallowed exception (empty catch) · ×1
  • Swallowed exception (empty catch) shared/src/commonMain/kotlin/com/sakethh/linkora/data/remote/repository/sync/RemoteSyncRepoImpl.kt:229 — 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.
Minor — 46 finding(s)
DM2 · Strongly-typed ids · Primitive id on a domain type · ×19
  • Primitive id on a domain type: CaptureTrack.capturedLinkId shared/src/commonMain/kotlin/com/sakethh/linkora/domain/model/CaptureTrack.kt:8 — `CaptureTrack.capturedLinkId` 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.
  • Primitive id on a domain type: CaptureTrack.captureWorkerId shared/src/commonMain/kotlin/com/sakethh/linkora/domain/model/CaptureTrack.kt:9 — `CaptureTrack.captureWorkerId` 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.
  • Primitive id on a domain type: Folder.parentFolderId shared/src/commonMain/kotlin/com/sakethh/linkora/domain/model/Folder.kt:24 — `Folder.parentFolderId` is a raw `Long` — give it a strongly-typed id: a dedicated single-field type wrapping the `Long`, in whatever form your language spells that.
  • Primitive id on a domain type: Folder.localId shared/src/commonMain/kotlin/com/sakethh/linkora/domain/model/Folder.kt:25 — `Folder.localId` is a raw `Long` — give it a strongly-typed id: a dedicated single-field type wrapping the `Long`, in whatever form your language spells that.
  • Primitive id on a domain type: Folder.remoteId shared/src/commonMain/kotlin/com/sakethh/linkora/domain/model/Folder.kt:26 — `Folder.remoteId` is a raw `Long` — give it a strongly-typed id: a dedicated single-field type wrapping the `Long`, in whatever form your language spells that.
  • Primitive id on a domain type: RefreshLink.refreshedLinkId shared/src/commonMain/kotlin/com/sakethh/linkora/domain/model/RefreshLink.kt:8 — `RefreshLink.refreshedLinkId` is a raw `Long` — give it a strongly-typed id: a dedicated single-field type wrapping the `Long`, in whatever form your language spells that.
  • Primitive id on a domain type: Link.localId shared/src/commonMain/kotlin/com/sakethh/linkora/domain/model/link/Link.kt:27 — `Link.localId` is a raw `Long` — give it a strongly-typed id: a dedicated single-field type wrapping the `Long`, in whatever form your language spells that.
  • Primitive id on a domain type: Link.remoteId shared/src/commonMain/kotlin/com/sakethh/linkora/domain/model/link/Link.kt:28 — `Link.remoteId` is a raw `Long` — give it a strongly-typed id: a dedicated single-field type wrapping the `Long`, in whatever form your language spells that.
  • Primitive id on a domain type: Panel.localId shared/src/commonMain/kotlin/com/sakethh/linkora/domain/model/panel/Panel.kt:11 — `Panel.localId` is a raw `Long` — give it a strongly-typed id: a dedicated single-field type wrapping the `Long`, in whatever form your language spells that.
  • Primitive id on a domain type: Panel.remoteId shared/src/commonMain/kotlin/com/sakethh/linkora/domain/model/panel/Panel.kt:13 — `Panel.remoteId` is a raw `Long` — give it a strongly-typed id: a dedicated single-field type wrapping the `Long`, in whatever form your language spells that.
  • Primitive id on a domain type: PanelFolder.localId shared/src/commonMain/kotlin/com/sakethh/linkora/domain/model/panel/PanelFolder.kt:11 — `PanelFolder.localId` is a raw `Long` — give it a strongly-typed id: a dedicated single-field type wrapping the `Long`, in whatever form your language spells that.
  • Primitive id on a domain type: PanelFolder.remoteId shared/src/commonMain/kotlin/com/sakethh/linkora/domain/model/panel/PanelFolder.kt:12 — `PanelFolder.remoteId` is a raw `Long` — give it a strongly-typed id: a dedicated single-field type wrapping the `Long`, in whatever form your language spells that.
  • Primitive id on a domain type: PanelFolder.folderId shared/src/commonMain/kotlin/com/sakethh/linkora/domain/model/panel/PanelFolder.kt:13 — `PanelFolder.folderId` is a raw `Long` — give it a strongly-typed id: a dedicated single-field type wrapping the `Long`, in whatever form your language spells that.
  • Primitive id on a domain type: PanelFolder.connectedPanelId shared/src/commonMain/kotlin/com/sakethh/linkora/domain/model/panel/PanelFolder.kt:16 — `PanelFolder.connectedPanelId` is a raw `Long` — give it a strongly-typed id: a dedicated single-field type wrapping the `Long`, in whatever form your language spells that.
  • Primitive id on a domain type: Tag.localId shared/src/commonMain/kotlin/com/sakethh/linkora/domain/model/tag/Tag.kt:20 — `Tag.localId` is a raw `Long` — give it a strongly-typed id: a dedicated single-field type wrapping the `Long`, in whatever form your language spells that.
  • Primitive id on a domain type: Tag.remoteId shared/src/commonMain/kotlin/com/sakethh/linkora/domain/model/tag/Tag.kt:21 — `Tag.remoteId` is a raw `Long` — give it a strongly-typed id: a dedicated single-field type wrapping the `Long`, in whatever form your language spells that.
  • Primitive id on a domain type: LinkTag.remoteId shared/src/commonMain/kotlin/com/sakethh/linkora/domain/model/tag/Tag.kt:47 — `LinkTag.remoteId` is a raw `Long` — give it a strongly-typed id: a dedicated single-field type wrapping the `Long`, in whatever form your language spells that.
  • Primitive id on a domain type: LinkTag.linkId shared/src/commonMain/kotlin/com/sakethh/linkora/domain/model/tag/Tag.kt:48 — `LinkTag.linkId` is a raw `Long` — give it a strongly-typed id: a dedicated single-field type wrapping the `Long`, in whatever form your language spells that.
  • Primitive id on a domain type: LinkTag.tagId shared/src/commonMain/kotlin/com/sakethh/linkora/domain/model/tag/Tag.kt:49 — `LinkTag.tagId` is a raw `Long` — give it a strongly-typed id: a dedicated single-field type wrapping the `Long`, in whatever form your language spells that.
X10 · Duplicated predicate · Duplicated predicate · ×9
  • Duplicated predicate shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/folder/RenameFolderDialog.kt:117 — `!Platform.Android.onMobile() && !showProgressBar` appears character-identically in 2 files — shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/folder/RenameFolderDialog.kt, shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/link/RenameLinkDialogParam.kt. 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 shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/nav/DesktopNavigationRail.kt:70 — `!preferences.isHomeScreenEnabled && navRouteItem.toString() == Navigation.Root.HomeScreen.toString()` appears character-identically in 2 files — shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/nav/DesktopNavigationRail.kt, shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/nav/MobileBottomNavBar.kt. 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 shared/src/androidMain/kotlin/com/sakethh/linkora/platform/Expected.android.kt:132 — `!syncServerCert.exists() && !bypassCertCheck` appears character-identically in 2 files — shared/src/androidMain/kotlin/com/sakethh/linkora/platform/Expected.android.kt, shared/src/desktopMain/kotlin/com/sakethh/linkora/platform/Expected.desktop.kt. 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 shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/tag/TagSelectionComponent.kt:80 — `allTags.data.isEmpty() || allTags.data.values.first().isEmpty()` appears character-identically in 2 files — shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/tag/TagSelectionComponent.kt, shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/collections/CollectionsScreen.kt. 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 shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/folder/menu/FolderMenuBtmSheet.kt:221 — `menuBtmSheetParam.showProgressBarDuringRemoteSave.value && onAndroidMobile` appears character-identically in 2 files — shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/folder/menu/FolderMenuBtmSheet.kt, shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/link/menu/LinkMenuBtmSheet.kt. 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 shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/home/panels/SpecificPanelManagerScreen.kt:148 — `platform is Platform.Desktop || platform is Platform.Web` appears character-identically in 2 files — shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/home/panels/SpecificPanelManagerScreen.kt, shared/src/commonMain/kotlin/com/sakethh/linkora/ui/screens/onboarding/OnboardingSlidesScreen.kt. 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 shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/link/GridViewLinkComponent.kt:119 — `preferences.showDateInLinkView && linkComponentParam.link.date != null` appears character-identically in 2 files — shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/link/GridViewLinkComponent.kt, shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/link/ListViewLinkComponent.kt. 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 shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/link/GridViewLinkComponent.kt:124 — `preferences.showTagsInLinkView && linkComponentParam.tags != null` appears character-identically in 2 files — shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/link/GridViewLinkComponent.kt, shared/src/commonMain/kotlin/com/sakethh/linkora/ui/components/link/ListViewLinkComponent.kt. 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 shared/src/androidMain/kotlin/com/sakethh/linkora/platform/Expected.android.kt:126 — `syncServerCert.exists() && !bypassCertCheck` appears character-identically in 2 files — shared/src/androidMain/kotlin/com/sakethh/linkora/platform/Expected.android.kt, shared/src/desktopMain/kotlin/com/sakethh/linkora/platform/Expected.desktop.kt. 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.
AX6 · Interface segregation · Fat interface · ×8
  • Fat interface: FoldersDao (38 abstract methods) shared/src/commonMain/kotlin/com/sakethh/linkora/data/local/dao/FoldersDao.kt:12 — `FoldersDao` declares 38 abstract methods: `insertANewFolder`, `duplicateAFolder`, `insertMultipleNewFolders`, `getAllArchiveFoldersAsFlow`, `getAllArchiveFoldersAsList`, `getAllRootFoldersAsFlow`, `getAllRootFoldersAsList`, `getAllFoldersAsList`, `doesFolderTableHaveData`, `getAllFoldersAsFlow`, `getLatestFoldersTableID`, `getThisFolderData`, `doesFolderExists`, `doesThisRootFolderExists`, `getChildFoldersAsFlow`, `getChildFoldersAsList`, `renameAFolderName`, `markFolderAsArchive`, `markMultipleFoldersAsArchive`, `markMultipleFoldersAsRegular`, `markFolderAsRegularFolder`, `renameAFolderNote`, `updateFolder`, `updateFolderTimestamp`, `updateFoldersTimestamp`, `deleteAFolderNote`, `deleteAFolder`, `getChildFolders`, `getRootFoldersSortedById`, `getRootFoldersSortedByName`, `search`, `getRemoteFolderId`, `getRemoteIds`, `getLocalIdOfAFolder`, `getUnSyncedFolders`, `moveFolders`, `markFoldersAsRoot`, `updateARemoteLinkId`. Counted over its public functions with no body, once per name; default-bodied functions and properties are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: LinksDao (40 abstract methods) shared/src/commonMain/kotlin/com/sakethh/linkora/data/local/dao/LinksDao.kt:15 — `LinksDao` declares 40 abstract methods: `addANewLink`, `addMultipleLinks`, `deleteLinksOfFolder`, `deleteALinkNote`, `archiveALink`, `archiveMultipleLinks`, `deleteALink`, `deleteMultipleLinks`, `updateLinkNote`, `updateLinkTitle`, `isInArchive`, `search`, `getSortedLinks`, `getLinksSortedById`, `getLinksSortedByTitle`, `getAllLinks`, `getAllLinksAsFlow`, `getLinksOfThisFolderAsList`, `updateALink`, `getRemoteId`, `getLocalIdOfALink`, `getLocalIds`, `getLatestId`, `getLink`, `getUnSyncedLinks`, `updateLinkTimestamp`, `updateLinksTimestamp`, `doesLinkExist`, `changeIdOfALink`, `deleteLinksFromHistory`, `deleteLinks`, `moveLinks`, `getIdsOfCopiedLinks`, `updateRemoteLinkId`, `unarchiveLinks`, `getRemoteIds`, `getAllLinksSortedById`, `getAllLinksSortedByTitle`, `doesLinkTableHaveData`, `forceSetDefaultFolderToInternalIds`. Counted over its public functions with no body, once per name; default-bodied functions and properties are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: PanelsDao (28 abstract methods) shared/src/commonMain/kotlin/com/sakethh/linkora/data/local/dao/PanelsDao.kt:12 — `PanelsDao` declares 28 abstract methods: `getLatestPanelID`, `getLatestPanelFolderID`, `addANewPanel`, `updateAPanel`, `updateAPanelFolder`, `getRemoteIdOfPanel`, `updateAFolderName`, `addMultiplePanels`, `addMultiplePanelFolders`, `deleteAPanel`, `updateAPanelName`, `updatePanelTimestamp`, `deleteConnectedFoldersOfPanel`, `addANewFolderInAPanel`, `deleteAFolderFromAPanel`, `deleteAFolderFromAllPanels`, `getAllThePanels`, `getAllThePanelsAsAList`, `doesPanelsTableHaveData`, `getAllThePanelFoldersAsAList`, `getAllThePanelFoldersAsAFlow`, `getAllTheFoldersFromAPanel`, `getPanel`, `getLocalPanelId`, `getLocalPanelFolderId`, `getPanelFolder`, `getUnSyncedPanels`, `getUnSyncedPanelFolders`. Counted over its public functions with no body, once per name; default-bodied functions and properties are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: TagsDao (26 abstract methods) shared/src/commonMain/kotlin/com/sakethh/linkora/data/local/dao/TagsDao.kt:15 — `TagsDao` declares 26 abstract methods: `createATag`, `updateATag`, `updateRemoteId`, `getATag`, `createLinkTags`, `deleteLinkTagsBasedOnTags`, `deleteATag`, `renameATag`, `getLastInsertedIdFromTags`, `getAllTags`, `getTagsSortedById`, `getTagsSortedByName`, `getAllTagsAsList`, `getAllTagLinksAsList`, `getAllLinkTags`, `getTagsBasedOnTheLinkId`, `getTags`, `search`, `getTagsWithLinkIds`, `getTagsWithLinkIdsAsList`, `getLocalTagIds`, `getLocalTags`, `getLocalTagId`, `getRemoteTagIds`, `getRemoteTagId`, `getUnsyncedTags`. Counted over its public functions with no body, once per name; default-bodied functions and properties are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: LocalFoldersRepo (29 abstract methods) shared/src/commonMain/kotlin/com/sakethh/linkora/domain/repository/local/LocalFoldersRepo.kt:7 — `LocalFoldersRepo` declares 29 abstract methods: `insertANewFolder`, `insertANewFolderLocally`, `getAllRootFoldersAsList`, `getAllFoldersAsResultList`, `getAllFoldersAsList`, `isFoldersTableEmpty`, `getAllFoldersAsFlow`, `getChildFoldersOfThisParentIDAsList`, `getLatestFoldersTableID`, `getThisFolderData`, `doesThisChildFolderExists`, `doesThisRootFolderExists`, `getRootFolders`, `getChildFolders`, `getChildFoldersAsList`, `sortFoldersAsNonResultFlow`, `getChildFoldersOfThisParentIDAsFlow`, `markFolderAsArchive`, `markFolderAsRegularFolder`, `markFoldersAsRoot`, `updateLocalFolderData`, `updateFolder`, `deleteAFolderNote`, `deleteAFolder`, `deleteMultipleFolders`, `search`, `getRemoteIdOfAFolder`, `getLocalIdOfAFolder`, `getUnSyncedFolders`. Counted over its public functions with no body, once per name; default-bodied functions and properties are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: LocalLinksRepo (31 abstract methods) shared/src/commonMain/kotlin/com/sakethh/linkora/domain/repository/local/LocalLinksRepo.kt:12 — `LocalLinksRepo` declares 31 abstract methods: `addANewLink`, `addANewLinkLocally`, `addMultipleLinks`, `getLinks`, `getLinksAsNonResultFlow`, `getAllLinks`, `deleteLinksOfFolder`, `deleteALinkNote`, `deleteALink`, `deleteMultipleLinks`, `archiveALink`, `updateLinkNote`, `updateLinkTitle`, `isInArchive`, `search`, `getLinksOfThisFolderAsList`, `getAllLinksAsFlow`, `updateALink`, `refreshLinkMetadata`, `getLocalLinkId`, `getRemoteLinkId`, `getALink`, `getLatestId`, `getUnSyncedLinks`, `changeIdOfALink`, `doesLinkExist`, `deleteDuplicateLinks`, `deleteLinksLocally`, `isLinksTableEmpty`, `forceSetDefaultFolderToInternalIds`, `scrapeLinkData`. Counted over its public functions with no body, once per name; default-bodied functions and properties are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: LocalPanelsRepo (26 abstract methods) shared/src/commonMain/kotlin/com/sakethh/linkora/domain/repository/local/LocalPanelsRepo.kt:8 — `LocalPanelsRepo` declares 26 abstract methods: `addANewPanel`, `addANewPanelLocally`, `deleteAPanel`, `updateAPanelName`, `updatePanel`, `addANewFolderInAPanel`, `deleteAFolderFromAllPanels`, `deleteAFolderFromAPanel`, `getAllThePanels`, `getAllThePanelsAsAList`, `isPanelsTableEmpty`, `getAllThePanelFoldersAsAList`, `getAllThePanelFoldersAsAFlow`, `getAllTheFoldersFromAPanel`, `getPanel`, `getPanelFolder`, `getLocalPanelId`, `getRemotePanelId`, `getLocalPanelFolderId`, `updateAFolderName`, `addMultiplePanels`, `addMultiplePanelFolders`, `getLatestPanelID`, `getUnSyncedPanels`, `getUnSyncedPanelFolders`, `updateAPanelFolder`. Counted over its public functions with no body, once per name; default-bodied functions and properties are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: LocalTagsRepo (19 abstract methods) shared/src/commonMain/kotlin/com/sakethh/linkora/domain/repository/local/LocalTagsRepo.kt:8 — `LocalTagsRepo` declares 19 abstract methods: `createATag`, `createATagLocally`, `createLinkTags`, `deleteLinkTagsBasedOnTags`, `deleteATag`, `renameATag`, `getLastInsertedIdFromTags`, `getAllTags`, `getTags`, `getAllTagsAsList`, `getAllLinkTagsAsList`, `getAllLinkTags`, `getTagsBasedOnTheLinkId`, `getTagsForLinks`, `getTagsForLinksAsMap`, `search`, `getLocalTagIds`, `getLocalTags`, `getLocalTagId`. Counted over its public functions with no body, once per name; default-bodied functions and properties are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
D20 · ADR Quality · No ADRs found · ×1
  • No ADRs found desktopApp/build.gradle.kts:41 — 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 `desktopApp/build.gradle.kts` makes this repository a deployable product (line 41).
D26 · Project Cohesion · Projects may be oversized for their cohesion · ×1
  • Projects may be oversized for their cohesion shared/build.gradle.kts:1 — `shared` (44567 LoC, 643 module-visible types across 72 directories) overshoots its size bounds. 1 of 6 build unit(s) (Gradle, npm) overshoot their size bounds, lowering Project Cohesion to 6.7/10. Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
D27 · Navigability · High interface indirection · ×1
  • High interface indirection — 59 % of calls go through an interface — tracing a call means resolving the implementation each hop. Prefer concrete types where there's a single implementation.
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
M2 · Architecture documentation · No ADRs · ×1
  • No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
P3 · Security & performance tooling · No SAST · ×1
  • No SAST — No static application security testing detected. For this repository's stack, add spotbugs with find-sec-bugs (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 2 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 · No dependency-update automation · ×1
  • No dependency-update automation webApp/worker/package.json:5 — `webApp/worker/package.json` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`.
P6 · Release Hygiene · No changelog · ×1
  • No changelog — No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)

Appendix B — Reproduction & audit trail

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

DimensionToolVersionCommandFindingsRaw output
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=0 --max-count=200" --report-format json --report-path /tmp/watchdog-gitleaks-e06cfab875aa4e8a86f3871070b19207/history.json --exit-code 0 --source .0artifacts/raw/gitleaks-history.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=200 --max-count=800" --report-format json --report-path /tmp/watchdog-gitleaks-e06cfab875aa4e8a86f3871070b19207/history-1.json --exit-code 0 --source .0artifacts/raw/gitleaks-history-1.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=1000 --max-count=397" --report-format json --report-path /tmp/watchdog-gitleaks-e06cfab875aa4e8a86f3871070b19207/history-2.json --exit-code 0 --source .0artifacts/raw/gitleaks-history-2.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-e06cfab875aa4e8a86f3871070b19207/tree.json --exit-code 0 --source .0artifacts/raw/gitleaks-tree.json
D29 · Static Analysis (SAST)semgrep—semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt --exclude kotlin-js-store .40artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilitiestrivy—trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** .1artifacts/raw/trivy-fs.json
D31 · IaC & Container Securitytrivy—trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.0—
D32 · Data Compliance (PII/GDPR)semgrep—semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 22 file(s) — `shared/build.gradle.kts`, `shared/src/androidDesktopMain/kotlin/Utils.kt`, `shared/src/androidMain/kotlin/com/sakethh/linkora/platform/FileManager.kt`, `shared/src/androidMain/kotlin/com/sakethh/linkora/utils/ExtensionFunctions.kt`, `shared/src/commonMain/kotlin/com/sakethh/linkora/data/local/dao/LocalDatabaseUtilsDao.kt`, … (+17 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.0—
D37 · Vulnerability-disclosure Policydisclosure—disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.0—
D40 · Network Egress Confinementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.0—
D41 · Kernel & Syscall Confinementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.0—
D42 · Runtime Threat Enforcementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.0—
D43 · Malicious Dependenciestrivy—trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** .0artifacts/raw/trivy-fs.json

Run 01a1e591-20ff-7998-a082-c783051bae48 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.

Downloadable artifacts

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

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