Public report of xpipe-io/xpipe, published 24 October 2026. It has the same score, grades and number of
findings as the full report. The details of security findings (where they are in the code, which known
vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive reportMeasured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.10.5). Watchdog signed this survey and filed it in the standard's public register, where anyone can look it up by its survey ID. Check this survey →
Signed and filed in the standard's public register, 24 October 2026, 07:12 UTC · Survey ID cd_fc8b39c8f1b54bf1ad65380c4cb163ee
xpipe-io/xpipe
Measured 24 October 2026, 07:07 UTC, at code version adb8697
Regression: 1 dimension fell since the last survey
A regression is a drop of 0.5 points or more in the score, or of 2.5 or more out of 10 in a dimension, since the last survey.
CAI scoreWeak
CriticalWeakAdequateStrongExemplary
Down 7 since the last survey
The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.
A medium codebase: 93,315 lines of product code in 7 projects, tests not counted · Estimated rebuild effort: about 0.6 person-years · Weakest lens: Production Readiness, 30
Findings by how serious they are
9 critical546 serious43 minor
18 dimensions are left out of the score. For each one, Watchdog either couldn't measure it in this code, or found no evidence of the safeguard it looks for, such as a tested backup restore. They count neither for nor against the score, and Limitations lists each one with its reason.
This survey was produced by
Watchdog
Producer
Canine Development
Analyzer
Watchdog engine 1.0.0
Measured
24 October 2026, 07:07 UTC
A measurement, not a certificate. The Code Assurance Index records a number
together with the evidence it was worked out from, so anyone can recalculate it, but it doesn't certify or guarantee
the code. The standard was written by Canine Development, which also builds Watchdog. It is open to any tool that
implements it, and today Watchdog is the only one that does.
The score is deterministic, which means the same code always gets the same score. Watchdog works it out with tools that follow published rules, and an AI model never decides it, so anyone who applies the same rules to the same code gets the same number. How it is done is explained under Methodology ▸
53of 57 dimensions measured by tools. The other 4 are advisory notes from an AI model, which explain the code but don't count towards the score.
589of 598 findings point to an exact file and line, so you can open each one in the code. The other 9 concern the repository as a whole, such as missing documentation.
57dimensions across 6 lenses, read from 93,315 lines of product code in 7 projects.
xpipe-io/xpipe scores 51 out of 100, which would normally be rated Adequate, but it is rated Weak because its weakest group of dimensions, Security, is rated Critical. The standard never rates a score more than one step above its weakest group, so a high average can't hide a weak area.
The weakest lens counts most in the score, and here that is Production Readiness, which scores 30 and is rated Weak. Its Secret Scanning dimension scores 0 out of 10, and until that reaches 4, Production Readiness can't be rated higher than Adequate. The first actions are to resolve the 6 Leaked secret finding(s) in Secret Scanning and to add a CI workflow that builds and runs the test suite on every push/PR, and if Production Readiness rose to 70, the score would rise from 51 to about 67.
Nine findings are critical: six in Secret Scanning and three in Static Analysis (SAST).
Watchdog couldn't measure 16 dimensions in this code, among them Code Coverage, Test Reliability and Dependency Hygiene, so they are left out of the score. The product code is 93,315 lines, which would take an estimated 0.6 person-years, around €88,000, to rebuild.
A lens is capped at Adequate while one of its dimensions scores below 4 out of 10, however well the rest of the lens does. That way a serious problem in one place always shows in the lens's rating.
How the score is built: what each lens counts forThe lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.
Watchdog compares every finding with the previous survey's. A finding that has only moved to another line in the same file counts as the same finding, so only new findings appear here. Advisory notes from the AI model are left out, because the model words them afresh in every survey.
Fixed since the last survey: 9 findings
These 9 critical or serious findings were in the previous survey, on 10 October 2026, and are gone from this one.
Exception handling · Swallowed exception (caught, then discarded) app/src/main/java/io/xpipe/app/core/check/AppSystemFontCheck.java
Exception handling · Swallowed exception (caught, then discarded) app/src/main/java/io/xpipe/app/process/CommandControl.java
Rebuild cost: about €88,000 · Estimate
Cost to rebuild
€29,000 to €150,000, for 487 to 1,546 hours of work, about 0.6 person-years for 1 to 2 engineers
Difficulty of the problem
Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor
×0.7 at a score of 51. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
Size
Medium: 93,315 lines of product code
How the estimate is made: Watchdog prices the hours a team would need to write this code again, at €60 to €95 an hour. Declarations and boilerplate are priced at a fast rate and logic at a slower one, and the logic is then multiplied by the difficulty of the problem and by the quality factor. The estimate can be about 30% off either way, and it moves most with the hourly rate and the difficulty. For this code, every line is priced as straight logic, which keeps the estimate on the low side.
Top priorities
The three actions that raise the score most for the work they take. The full ranked list is in the Roadmap.
1
Resolve the 6 Leaked secret finding(s) in Secret Scanning — start with REDACTED (2), REDACTED (2), REDACTED.
Raises the score by about 19 points · Low effort · Secret Scanning
2
Add a CI workflow that builds and runs the test suite on every push/PR.
Raises the score by about 7 points · Medium effort · CI/CD gates
3
Resolve the 1 No assertions finding(s) in Test Quality — start with Test.java.
Raises the score by about 2 points · Low effort · Test Quality
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 €88,000 to build again, about 0.6 person-years of work. Its weakest lens is Production Readiness, at 30 (Weak). Production Readiness is about whether the product is ready to run in production and to change without breaking. Because the weakest lens counts most in the score, work on Production Readiness also moves the score most.
Based on: the rebuild estimate · the Production Readiness grade · how much each lens counts
What to do: Start with the Production Readiness actions in Top priorities.
If you do one thing first · First action
Resolve the 6 Leaked secret finding(s) in Secret Scanning. Of all the actions in this report, it raises the score most for the work it takes: about 19 points for low effort, because it clears the 6 Secret Scanning findings. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
Architecture: 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.
56 modules, with 351 dependencies between them. One loop runs through 29 of the modules, marked above the diagonal.
The table shows the 40 modules with the most connections; 16 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.
app.hub.section uses app.hub.entry, so a change to app.hub.entry can break app.hub.section, while a change to app.hub.section can't break app.hub.entry.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
3→7 app.hub.section uses app.hub.categorypart of a loop✕
Connections
2 pairs of types, where a type in app.hub.section uses a type in app.hub.category.
app.hub.section uses app.hub.category, so a change to app.hub.category can break app.hub.section, while a change to app.hub.section can't break app.hub.category.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
3→10 app.hub.section uses app.storagepart of a loop✕
Connections
1 pair of types, where a type in app.hub.section uses a type in app.storage.
app.hub.section uses app.comp.base, so a change to app.comp.base can break app.hub.section, while a change to app.hub.section can't break app.comp.base.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
app.hub.list uses app.hub.category, so a change to app.hub.category can break app.hub.list, while a change to app.hub.list can't break app.hub.category.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
app.hub.entry uses app.hub.section, so a change to app.hub.section can break app.hub.entry, while a change to app.hub.entry can't break app.hub.section.
Position
Below the diagonal: app.hub.entry uses a module listed above it, which is the healthy direction.
app.hub.entry uses app.hub.category, so a change to app.hub.category can break app.hub.entry, while a change to app.hub.entry can't break app.hub.category.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
app.hub.category uses app.hub.entry, so a change to app.hub.entry can break app.hub.category, while a change to app.hub.category can't break app.hub.entry.
Position
Below the diagonal: app.hub.category uses a module listed above it, which is the healthy direction.
7→10 app.hub.category uses app.storagepart of a loop✕
Connections
4 pairs of types, where a type in app.hub.category uses a type in app.storage.
app.hub.category uses app.platform, so a change to app.platform can break app.hub.category, while a change to app.hub.category can't break app.platform.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
app.hub.creation uses app.hub.section, so a change to app.hub.section can break app.hub.creation, while a change to app.hub.creation can't break app.hub.section.
Position
Below the diagonal: app.hub.creation uses a module listed above it, which is the healthy direction.
app.hub.creation uses app.hub.entry, so a change to app.hub.entry can break app.hub.creation, while a change to app.hub.creation can't break app.hub.entry.
Position
Below the diagonal: app.hub.creation uses a module listed above it, which is the healthy direction.
app.hub.creation uses app.hub.category, so a change to app.hub.category can break app.hub.creation, while a change to app.hub.creation can't break app.hub.category.
Position
Below the diagonal: app.hub.creation uses a module listed above it, which is the healthy direction.
8→9 app.hub.creation uses app.storepart of a loop✕
Connections
11 pairs of types, where a type in app.hub.creation uses a type in app.store.
app.hub.creation uses app.platform, so a change to app.platform can break app.hub.creation, while a change to app.hub.creation can't break app.platform.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
8→26 app.hub.creation uses app.corepart of a loop✕
Connections
1 pair of types, where a type in app.hub.creation uses a type in app.core.
app.hub.creation uses app.comp.base, so a change to app.comp.base can break app.hub.creation, while a change to app.hub.creation can't break app.comp.base.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
app.terminal uses app.util, so a change to app.util can break app.terminal, while a change to app.terminal can't break app.util.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
13→18 app.terminal uses app.processpart of a loop✕
Connections
32 pairs of types, where a type in app.terminal uses a type in app.process. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
app.browser.file uses app.hub.list, so a change to app.hub.list can break app.browser.file, while a change to app.browser.file can't break app.hub.list.
Position
Below the diagonal: app.browser.file uses a module listed above it, which is the healthy direction.
app.browser.file uses app.hub.entry, so a change to app.hub.entry can break app.browser.file, while a change to app.browser.file can't break app.hub.entry.
Position
Below the diagonal: app.browser.file uses a module listed above it, which is the healthy direction.
app.browser.file uses app.hub.category, so a change to app.hub.category can break app.browser.file, while a change to app.browser.file can't break app.hub.category.
Position
Below the diagonal: app.browser.file uses a module listed above it, which is the healthy direction.
34 pairs of types, where a type in app.process uses a type in app.util. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
31 pairs of types, where a type in app.prefs uses a type in app.comp. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
28 pairs of types, where a type in app.prefs uses a type in app.platform. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
ext.base.desktop uses app.hub.section, so a change to app.hub.section can break ext.base.desktop, while a change to ext.base.desktop can't break app.hub.section.
Position
Below the diagonal: ext.base.desktop uses a module listed above it, which is the healthy direction.
ext.base.desktop uses app.hub.entry, so a change to app.hub.entry can break ext.base.desktop, while a change to ext.base.desktop can't break app.hub.entry.
Position
Below the diagonal: ext.base.desktop uses a module listed above it, which is the healthy direction.
ext.base.desktop uses app.hub.creation, so a change to app.hub.creation can break ext.base.desktop, while a change to ext.base.desktop can't break app.hub.creation.
Position
Below the diagonal: ext.base.desktop uses a module listed above it, which is the healthy direction.
70 pairs of types, where a type in app.comp.base uses a type in app.comp. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
app.browser.action uses app.hub.action, so a change to app.hub.action can break app.browser.action, while a change to app.browser.action can't break app.hub.action.
Position
Below the diagonal: app.browser.action uses a module listed above it, which is the healthy direction.
app.browser.action uses app.browser.file, so a change to app.browser.file can break app.browser.action, while a change to app.browser.action can't break app.browser.file.
Position
Below the diagonal: app.browser.action uses a module listed above it, which is the healthy direction.
app.browser.action uses app.action, so a change to app.action can break app.browser.action, while a change to app.browser.action can't break app.action.
Position
Below the diagonal: app.browser.action uses a module listed above it, which is the healthy direction.
ext.base.identity uses app.hub.action, so a change to app.hub.action can break ext.base.identity, while a change to ext.base.identity can't break app.hub.action.
Position
Below the diagonal: ext.base.identity uses a module listed above it, which is the healthy direction.
ext.base.identity uses app.hub.section, so a change to app.hub.section can break ext.base.identity, while a change to ext.base.identity can't break app.hub.section.
Position
Below the diagonal: ext.base.identity uses a module listed above it, which is the healthy direction.
ext.base.identity uses app.hub.list, so a change to app.hub.list can break ext.base.identity, while a change to ext.base.identity can't break app.hub.list.
Position
Below the diagonal: ext.base.identity uses a module listed above it, which is the healthy direction.
ext.base.identity uses app.hub.entry, so a change to app.hub.entry can break ext.base.identity, while a change to ext.base.identity can't break app.hub.entry.
Position
Below the diagonal: ext.base.identity uses a module listed above it, which is the healthy direction.
ext.base.identity uses app.hub.creation, so a change to app.hub.creation can break ext.base.identity, while a change to ext.base.identity can't break app.hub.creation.
Position
Below the diagonal: ext.base.identity uses a module listed above it, which is the healthy direction.
ext.base.identity uses app.storage, so a change to app.storage can break ext.base.identity, while a change to ext.base.identity can't break app.storage.
Position
Below the diagonal: ext.base.identity uses a module listed above it, which is the healthy direction.
ext.base.identity uses app.process, so a change to app.process can break ext.base.identity, while a change to ext.base.identity can't break app.process.
Position
Below the diagonal: ext.base.identity uses a module listed above it, which is the healthy direction.
ext.base.identity uses app.identity, so a change to app.identity can break ext.base.identity, while a change to ext.base.identity can't break app.identity.
Position
Below the diagonal: ext.base.identity uses a module listed above it, which is the healthy direction.
ext.base.identity uses app.platform, so a change to app.platform can break ext.base.identity, while a change to ext.base.identity can't break app.platform.
Position
Below the diagonal: ext.base.identity uses a module listed above it, which is the healthy direction.
ext.base.script uses app.hub.action, so a change to app.hub.action can break ext.base.script, while a change to ext.base.script can't break app.hub.action.
Position
Below the diagonal: ext.base.script uses a module listed above it, which is the healthy direction.
ext.base.script uses app.hub.section, so a change to app.hub.section can break ext.base.script, while a change to ext.base.script can't break app.hub.section.
Position
Below the diagonal: ext.base.script uses a module listed above it, which is the healthy direction.
ext.base.script uses app.hub.entry, so a change to app.hub.entry can break ext.base.script, while a change to ext.base.script can't break app.hub.entry.
Position
Below the diagonal: ext.base.script uses a module listed above it, which is the healthy direction.
ext.base.script uses app.hub.category, so a change to app.hub.category can break ext.base.script, while a change to ext.base.script can't break app.hub.category.
Position
Below the diagonal: ext.base.script uses a module listed above it, which is the healthy direction.
ext.base.script uses app.hub.creation, so a change to app.hub.creation can break ext.base.script, while a change to ext.base.script can't break app.hub.creation.
Position
Below the diagonal: ext.base.script uses a module listed above it, which is the healthy direction.
28 pairs of types, where a type in ext.base.script uses a type in app.storage. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
ext.base.script uses app.browser.file, so a change to app.browser.file can break ext.base.script, while a change to ext.base.script can't break app.browser.file.
Position
Below the diagonal: ext.base.script uses a module listed above it, which is the healthy direction.
ext.base.store uses app.hub.action, so a change to app.hub.action can break ext.base.store, while a change to ext.base.store can't break app.hub.action.
Position
Below the diagonal: ext.base.store uses a module listed above it, which is the healthy direction.
ext.base.store uses app.hub.section, so a change to app.hub.section can break ext.base.store, while a change to ext.base.store can't break app.hub.section.
Position
Below the diagonal: ext.base.store uses a module listed above it, which is the healthy direction.
app.browser.menu uses app.browser.file, so a change to app.browser.file can break app.browser.menu, while a change to app.browser.menu can't break app.browser.file.
Position
Below the diagonal: app.browser.menu uses a module listed above it, which is the healthy direction.
app.browser.menu uses app.platform, so a change to app.platform can break app.browser.menu, while a change to app.browser.menu can't break app.platform.
Position
Below the diagonal: app.browser.menu uses a module listed above it, which is the healthy direction.
app.browser.menu uses app.browser.action, so a change to app.browser.action can break app.browser.menu, while a change to app.browser.menu can't break app.browser.action.
Position
Below the diagonal: app.browser.menu uses a module listed above it, which is the healthy direction.
ext.base.host uses app.hub.section, so a change to app.hub.section can break ext.base.host, while a change to ext.base.host can't break app.hub.section.
Position
Below the diagonal: ext.base.host uses a module listed above it, which is the healthy direction.
ext.base.host uses app.hub.creation, so a change to app.hub.creation can break ext.base.host, while a change to ext.base.host can't break app.hub.creation.
Position
Below the diagonal: ext.base.host uses a module listed above it, which is the healthy direction.
ext.base.host uses ext.base.identity, so a change to ext.base.identity can break ext.base.host, while a change to ext.base.host can't break ext.base.identity.
Position
Below the diagonal: ext.base.host uses a module listed above it, which is the healthy direction.
74 pairs of types, where a type in app.browser.menu.impl uses a type in app.browser.file. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
app.browser.menu.impl uses app.browser.file, so a change to app.browser.file can break app.browser.menu.impl, while a change to app.browser.menu.impl can't break app.browser.file.
Position
Below the diagonal: app.browser.menu.impl uses a module listed above it, which is the healthy direction.
app.browser.menu.impl uses app.process, so a change to app.process can break app.browser.menu.impl, while a change to app.browser.menu.impl can't break app.process.
Position
Below the diagonal: app.browser.menu.impl uses a module listed above it, which is the healthy direction.
30 pairs of types, where a type in app.browser.menu.impl uses a type in app.platform. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
app.browser.menu.impl uses app.platform, so a change to app.platform can break app.browser.menu.impl, while a change to app.browser.menu.impl can't break app.platform.
Position
Below the diagonal: app.browser.menu.impl uses a module listed above it, which is the healthy direction.
app.browser.menu.impl uses app.action, so a change to app.action can break app.browser.menu.impl, while a change to app.browser.menu.impl can't break app.action.
Position
Below the diagonal: app.browser.menu.impl uses a module listed above it, which is the healthy direction.
app.browser.menu.impl uses app.browser.action, so a change to app.browser.action can break app.browser.menu.impl, while a change to app.browser.menu.impl can't break app.browser.action.
Position
Below the diagonal: app.browser.menu.impl uses a module listed above it, which is the healthy direction.
68 pairs of types, where a type in app.browser.menu.impl uses a type in app.browser.menu. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
app.browser.menu.impl uses app.browser.menu, so a change to app.browser.menu can break app.browser.menu.impl, while a change to app.browser.menu.impl can't break app.browser.menu.
Position
Below the diagonal: app.browser.menu.impl uses a module listed above it, which is the healthy direction.
app.browser.menu.impl.compress uses app.browser.file, so a change to app.browser.file can break app.browser.menu.impl.compress, while a change to app.browser.menu.impl.compress can't break app.browser.file.
Position
Below the diagonal: app.browser.menu.impl.compress uses a module listed above it, which is the healthy direction.
app.browser.menu.impl.compress uses app.util, so a change to app.util can break app.browser.menu.impl.compress, while a change to app.browser.menu.impl.compress can't break app.util.
Position
Below the diagonal: app.browser.menu.impl.compress uses a module listed above it, which is the healthy direction.
app.browser.menu.impl.compress uses app.platform, so a change to app.platform can break app.browser.menu.impl.compress, while a change to app.browser.menu.impl.compress can't break app.platform.
Position
Below the diagonal: app.browser.menu.impl.compress uses a module listed above it, which is the healthy direction.
app.browser.menu.impl.compress uses app.action, so a change to app.action can break app.browser.menu.impl.compress, while a change to app.browser.menu.impl.compress can't break app.action.
Position
Below the diagonal: app.browser.menu.impl.compress uses a module listed above it, which is the healthy direction.
app.browser.menu.impl.compress uses app.browser.action, so a change to app.browser.action can break app.browser.menu.impl.compress, while a change to app.browser.menu.impl.compress can't break app.browser.action.
Position
Below the diagonal: app.browser.menu.impl.compress uses a module listed above it, which is the healthy direction.
app.browser.menu.impl.compress uses app.browser.menu, so a change to app.browser.menu can break app.browser.menu.impl.compress, while a change to app.browser.menu.impl.compress can't break app.browser.menu.
Position
Below the diagonal: app.browser.menu.impl.compress uses a module listed above it, which is the healthy direction.
ext.base.service uses app.hub.action, so a change to app.hub.action can break ext.base.service, while a change to ext.base.service can't break app.hub.action.
Position
Below the diagonal: ext.base.service uses a module listed above it, which is the healthy direction.
ext.base.service uses app.hub.section, so a change to app.hub.section can break ext.base.service, while a change to ext.base.service can't break app.hub.section.
Position
Below the diagonal: ext.base.service uses a module listed above it, which is the healthy direction.
ext.base.service uses app.hub.entry, so a change to app.hub.entry can break ext.base.service, while a change to ext.base.service can't break app.hub.entry.
Position
Below the diagonal: ext.base.service uses a module listed above it, which is the healthy direction.
ext.base.service uses app.hub.creation, so a change to app.hub.creation can break ext.base.service, while a change to ext.base.service can't break app.hub.creation.
Position
Below the diagonal: ext.base.service uses a module listed above it, which is the healthy direction.
ext.base.service uses app.platform, so a change to app.platform can break ext.base.service, while a change to ext.base.service can't break app.platform.
Position
Below the diagonal: ext.base.service uses a module listed above it, which is the healthy direction.
ext.base.service uses ext.base.host, so a change to ext.base.host can break ext.base.service, while a change to ext.base.service can't break ext.base.host.
Position
Below the diagonal: ext.base.service uses a module listed above it, which is the healthy direction.
ext.system.incus uses app.hub.action, so a change to app.hub.action can break ext.system.incus, while a change to ext.system.incus can't break app.hub.action.
Position
Below the diagonal: ext.system.incus uses a module listed above it, which is the healthy direction.
ext.system.incus uses app.hub.section, so a change to app.hub.section can break ext.system.incus, while a change to ext.system.incus can't break app.hub.section.
Position
Below the diagonal: ext.system.incus uses a module listed above it, which is the healthy direction.
ext.system.incus uses app.hub.creation, so a change to app.hub.creation can break ext.system.incus, while a change to ext.system.incus can't break app.hub.creation.
Position
Below the diagonal: ext.system.incus uses a module listed above it, which is the healthy direction.
ext.system.incus uses app.platform, so a change to app.platform can break ext.system.incus, while a change to ext.system.incus can't break app.platform.
Position
Below the diagonal: ext.system.incus uses a module listed above it, which is the healthy direction.
ext.system.incus uses ext.base.identity, so a change to ext.base.identity can break ext.system.incus, while a change to ext.system.incus can't break ext.base.identity.
Position
Below the diagonal: ext.system.incus uses a module listed above it, which is the healthy direction.
ext.system.incus uses ext.base.store, so a change to ext.base.store can break ext.system.incus, while a change to ext.system.incus can't break ext.base.store.
Position
Below the diagonal: ext.system.incus uses a module listed above it, which is the healthy direction.
ext.system.incus uses ext.base.host, so a change to ext.base.host can break ext.system.incus, while a change to ext.system.incus can't break ext.base.host.
Position
Below the diagonal: ext.system.incus uses a module listed above it, which is the healthy direction.
ext.system.lxd uses app.hub.action, so a change to app.hub.action can break ext.system.lxd, while a change to ext.system.lxd can't break app.hub.action.
Position
Below the diagonal: ext.system.lxd uses a module listed above it, which is the healthy direction.
ext.system.lxd uses app.hub.section, so a change to app.hub.section can break ext.system.lxd, while a change to ext.system.lxd can't break app.hub.section.
Position
Below the diagonal: ext.system.lxd uses a module listed above it, which is the healthy direction.
ext.system.lxd uses app.hub.creation, so a change to app.hub.creation can break ext.system.lxd, while a change to ext.system.lxd can't break app.hub.creation.
Position
Below the diagonal: ext.system.lxd uses a module listed above it, which is the healthy direction.
ext.system.lxd uses ext.base.identity, so a change to ext.base.identity can break ext.system.lxd, while a change to ext.system.lxd can't break ext.base.identity.
Position
Below the diagonal: ext.system.lxd uses a module listed above it, which is the healthy direction.
ext.system.lxd uses ext.base.store, so a change to ext.base.store can break ext.system.lxd, while a change to ext.system.lxd can't break ext.base.store.
Position
Below the diagonal: ext.system.lxd uses a module listed above it, which is the healthy direction.
ext.system.podman uses app.hub.action, so a change to app.hub.action can break ext.system.podman, while a change to ext.system.podman can't break app.hub.action.
Position
Below the diagonal: ext.system.podman uses a module listed above it, which is the healthy direction.
ext.system.podman uses app.hub.section, so a change to app.hub.section can break ext.system.podman, while a change to ext.system.podman can't break app.hub.section.
Position
Below the diagonal: ext.system.podman uses a module listed above it, which is the healthy direction.
ext.system.podman uses app.hub.creation, so a change to app.hub.creation can break ext.system.podman, while a change to ext.system.podman can't break app.hub.creation.
Position
Below the diagonal: ext.system.podman uses a module listed above it, which is the healthy direction.
ext.system.podman uses app.storage, so a change to app.storage can break ext.system.podman, while a change to ext.system.podman can't break app.storage.
Position
Below the diagonal: ext.system.podman uses a module listed above it, which is the healthy direction.
ext.system.podman uses app.process, so a change to app.process can break ext.system.podman, while a change to ext.system.podman can't break app.process.
Position
Below the diagonal: ext.system.podman uses a module listed above it, which is the healthy direction.
ext.system.podman uses app.platform, so a change to app.platform can break ext.system.podman, while a change to ext.system.podman can't break app.platform.
Position
Below the diagonal: ext.system.podman uses a module listed above it, which is the healthy direction.
ext.system.podman uses ext.base.store, so a change to ext.base.store can break ext.system.podman, while a change to ext.system.podman can't break ext.base.store.
Position
Below the diagonal: ext.system.podman uses a module listed above it, which is the healthy direction.
ext.system.podman uses ext.base.service, so a change to ext.base.service can break ext.system.podman, while a change to ext.system.podman can't break ext.base.service.
Position
Below the diagonal: ext.system.podman uses a module listed above it, which is the healthy direction.
At a glance — Code Health · 64% · Adequate · gated by X5 ·
Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).
OWASP category
Findings
Severity
A05:2025 — Injection
9
High / Critical
A07:2025 — Authentication Failures
6
High / Critical
Roadmap
Immediately resolve the six leaked secrets in the translation property files to eliminate critical security exposure. Establish a CI pipeline that builds and tests every change, integrating automated security scanning to prevent regressions from merging. Finally, fix the identified gaps in test quality by adding assertions and ensuring the test suite actually verifies code behavior.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Resolve the 6 Leaked secret finding(s) in Secret Scanning — start with REDACTED (2), REDACTED (2), REDACTED.
Run what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — locally for now, since there is no CI pipeline here yet, and as a step of the first workflow you add so a security regression fails the build instead of landing.
Declare the default where Java declares it: `@NullMarked` (org.jspecify.annotations) in each package's `package-info.java`, or once in `module-info.java`, and run NullAway (Error Prone) or the Checker Framework so the declaration is enforced. Then annotate the real exceptions `@Nullable` and resolve the suppressions rather than adding to them: a `@SuppressWarnings("NullAway")` or `castToNonNull(x)` on a value the checker could show to be null is a `NullPointerException` waiting for the path that makes it true — where the value genuinely cannot be null, say something the checker can see instead (a null check, `Objects.requireNonNull`, a non-null field initialised in the constructor).
Raise allocation-aware density on the hot paths — currently 12 use(s) across 110,510 production line(s) (~0.1/1k). More of the idioms below on the allocation-heavy paths climbs this toward 10.
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 — 9
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 — 546
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 — 43
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 18
Something this survey could not settle
from the outside, and which could be critical or serious. Either a control was required and no
positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves
nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean
result. These are excluded from the score rather than awarded a pass, so the number on the cover neither
rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each
one is named under Limitations.
Methodology & how to trust this report
Watchdog is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. 53 of 57 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); 4 documentation/naming judgement(s) are LLM-assisted and labelled advisory. Overall confidence is 0.9 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.
Every figure here is one of three kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact; ◐ Advisory — an LLM prose judgement. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10; ◐ Sampled · advisory marks an LLM verdict over a bounded sample — advisory, never a deterministic measurement.
What we checked — 57 dimensions across the health lenses
Each chip is a dimension scored from real signals across architecture, testing, dependencies, security & compliance, documentation, git-history and code quality — in one coherent pass. A surface report typically covers a handful.
How to trust any code-health report — three questions
Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 589 of 598 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
Is there a tool behind the number? Every score below names the method that produced it — Roslyn, git, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — not a narrative.
Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
This report answers yes to all three. That's the bar to hold any assessment to.
Tools & methods
The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.
Method
Backs
Version
Evaluator
Roslyn static analysis
Complexity, cohesion, coupling, dead code, API surface, layering
What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.
D8 Code Coverage — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: test source is present (.java) 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. To have real coverage read, produce a coverage report in a standard format (JaCoCo XML — the Gradle `jacocoTestReport` task) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures. You can widen what we reach: optional: produce a coverage report in a standard format (JaCoCo XML — the Gradle `jacocoTestReport` task) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures — then the real number is read on the next scan.
D11 Test Reliability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.java) but the built-in reliability runner does not support this repository's ecosystem, so flakiness couldn't be assessed. 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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Not scored — 8 Maven/Gradle manifest(s) were read, stating a version for 50 dependency(ies) and leaving 0 to a parent or an imported BOM, but no build resolved the dependency graph, so the outdated signal was not established. NOT a finding that these dependencies are current or healthy.
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 (23 contributor(s) across 3612 commit(s) sampled, automation and bot accounts excluded). One of them holds 99% of the history; the other 22 hold 0% 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.
D27 Navigability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
D32 Data Compliance (PII/GDPR) — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `app/src/main/java/io/xpipe/app/browser/action/impl/OpenFileNativeDetailsActionProvider.java`, `app/src/main/java/io/xpipe/app/browser/menu/impl/BrowseInNativeManagerMenuProvider.java`, `app/src/main/java/io/xpipe/app/browser/menu/impl/EditFileMenuProvider.java`, `app/src/main/java/io/xpipe/app/browser/menu/impl/GradleRunMenuProvider.java`, `app/src/main/java/io/xpipe/app/browser/menu/impl/OpenFileDefaultMenuProvider.java`, … (+24 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.
C1 Data Protection — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
C2 Access Controls — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
C3 Audit Trail — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These audit controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks audit controls.
C4 Data Retention — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These retention controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks retention controls.
C5 Data-Subject Rights — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These data-subject rights controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks data-subject rights controls.
GD1 Unfinished & placeholder code — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and no C#, F#, JavaScript/TypeScript, Dart, Ruby or Scala was found, and this repository's Java 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.
P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
S1 Web-Security Posture — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
X1 Async correctness — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala, Rust and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala, Rust or Kotlin was found in this repository, 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.
X12 Unreachable branch — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, 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.
X13 Undrained process stream — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, 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.
X17 Uncapped recursion over a caller-supplied document — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.
Limitations & what we did not check
Watchdog assesses the repository exactly as committed, and only the repository. By design it does not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.
D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
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").
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 is judged by an LLM over a bounded sample of docs — it reads what is written, not whether the docs match the running system, and it is advisory, not a measurement. Its critique rows are drawn from a closed category vocabulary and each row means the same thing in every run, so two scans can be compared row by row; the SET that fires is still a sample, and does not repeat exactly. Measured on one frozen input, six scans at one engine SHA: 2-5 critique rows per scan, 8 distinct rows across the six, 3 of those 8 seen in only one scan. So a D19 row is evidence about the documentation, but a COUNT of D19 rows is not a quantity — never read a change in it as an improvement or a regression.
D20 ADR Quality: ADR quality is an LLM read of the decision records present — it cannot know about decisions made and never recorded, and its verdict is sampled and advisory.
D21 Naming Consistency: Naming quality is an LLM judgement over a bounded sample — it assesses clarity/consistency of the names it sees, not domain-correctness, and is advisory.
D22 Internal API Consistency: API-surface coherence is an LLM judgement over a sample of the public surface — consistency of intent across the whole API is approximated, not exhaustively verified.
D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
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.
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.
M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
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.
The LLM boundary
LLM-set scores this run (4): D19, D21, D22, M4 (model: Local LLM). For these, a model reads a bounded sample and sets the numeric score; each names its own sample and method on its card. They are sampled and advisory by design: they vary at the margins between runs and are never a deterministic measurement. Every other score in this report is tool-computed at confidence 1.0.
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.
+ 52 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 57 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with StoreEntryWrapper.update (cyclomatic 38), StandardStorage.reloadContent (cyclomatic 37), AppDistributionType.determine (cyclomatic 35). — 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 57 together lifts Cyclomatic Complexity from 7.0 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
Stand up a CI pipeline, then gate Cyclomatic Complexity in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d1_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How hard the code is for a person to follow, beyond raw branching.
Method: Cognitive complexity per method (Sonar-style nesting-penalized score), computed exhaustively over production code, excluding test projects. Deterministic.
+ 106 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 1 body over 60 down to 60 or less in Cognitive Complexity — start with AppDistributionType.determine (cognitive 67). — Refactoring it lifts Cognitive Complexity from 6.4 to about 6.5/10.
Stand up a CI pipeline, then gate Cognitive Complexity in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes8.0 / 10Strong✓ Tool-verified
What it measures: Over-large classes that try to do too much ("god classes").
Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.
Resolve the 24 MethodTooLong finding(s) in God Classes — start with OptionsComp.java, StandardStorage.java, HttpStreamableServerTransportProvider.java. — One of this dimension's main actionable groups (24 warning-level).
Resolve the 13 TooManyMethods finding(s) in God Classes — start with AppPrefs.java, DataStorage.java, WrapperShellControl.java. — One of this dimension's main actionable groups (13 warning-level).
Resolve the 11 ClassTooLong finding(s) in God Classes — start with DataStorage.java, AppPrefs.java, DataStoreEntry.java. — One of this dimension's main actionable groups (11 warning-level).
Stand up a CI pipeline, then gate God Classes in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Copy-pasted code that should be shared instead.
Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), density-scored per KLoC of production code. Deterministic.
203 duplicated block group(s) detected. A further 5 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted.
+ 59 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 22 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with IncusCommandView.java (2), IncusContainerStore.java (2), McpTools.java. — One of this dimension's main actionable groups (22 warning-level).
Resolve the 18 Duplicated block (10 lines × 2) finding(s) in Code Duplication — start with StoreSectionBaseComp.java (2), LocalIdentityStoreProvider.java (2), BrowserFileInput.java. — One of this dimension's main actionable groups (18 warning-level).
Resolve the 18 Duplicated block (6 lines × 2) finding(s) in Code Duplication — start with BrowserFileInput.java (2), BrowserIconDirectoryType.java, ChgrpMenuProvider.java. — One of this dimension's main actionable groups (18 warning-level).
Stand up a CI pipeline, then gate Code Duplication in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling10.0 / 10Exemplary✓ Tool-verified
What it measures: Whether volatile projects sit underneath others that depend on them (so their churn ripples upward), and whether project dependencies form cycles. A widely-depended-on but stable shared/kernel project is healthy, not penalised.
Method: Dependency cycles via elementary-DFS over real .csproj references, plus Martin instability (afferent/efferent) per project. Exhaustive over the reference graph, deterministic.
Coverage: Exhaustive · type-level: afferent/efferent coupling + cycles computed over every production type — the population is all types, not a name convention.
7 production modules (Gradle), 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; 0 module(s) off the main sequence, with abstractness counted on 3 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).
What it measures: Whether a class's methods are focused on a single responsibility.
Method: LCOM4 cohesion per production class with at least two methods: connected components of methods sharing state or calls, computed syntactically. Deterministic, not a proxy.
Coverage: Exhaustive · type-level: LCOM4 cohesion computed over every production class — the population is all types, not a name convention.
Resolve the 9 Low cohesion finding(s) in Cohesion (LCOM4) — start with StoreCategoryWrapper.java, ContextMenuWrapper.java, Session.java. — One of this dimension's main actionable groups (9 warning-level).
Stand up a CI pipeline, then gate Cohesion (LCOM4) in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
Detailed fixes: d6_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D9 · Test Distribution10.0 / 10Exemplary✓ Tool-verified
What it measures: Whether the test suite has a healthy mix of unit / integration / end-to-end tests.
Method: Test projects classified (Unit/Integration/BDD/E2E) from compiled metadata; test methods counted exhaustively across projects with placement-agnostic disk fallback. Deterministic.
1 test methods: 1 unit, 0 integration, 0 BDD, 0 e2e.
✓ On the Gold path — maintain.
Detailed fixes: d9_recommendation.md.
Do you agree with this assessment?
D10 · Test Quality8.1 / 10Strong✓ Tool-verified
What it measures: Whether the tests truly assert behaviour rather than just running the code.
Method: Per-test assertions, skips, and mock references analyzed via Roslyn; structured skip-reason tags (BUG:/ENV:) separate documented deferrals from debt. Deterministic.
0 skipped, 1 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 1 tests.
No assertions: testapp/src/localTest/java/test/Test.java:9
Test project verifies nothing: appapp/src/localTest/java/test/Test.java:9
What to do
Resolve the 1 No assertions finding(s) in Test Quality — start with Test.java. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 Test project verifies nothing finding(s) in Test Quality — start with Test.java. — One of this dimension's main actionable groups (1 warning-level).
Stand up a CI pipeline, then gate Test Quality in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d10_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.
Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.
Resolve the 6 Leaked secret finding(s) in Secret Scanning — start with REDACTED (2), REDACTED (2), REDACTED. — One of this dimension's main actionable groups (6 issue-level).
Stand up a CI pipeline, then gate Secret Scanning in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d13_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Files that change often and are also complex — the riskiest hotspots.
Method: Per production file churn times cyclomatic complexity over a rolling window, computed from git and Roslyn/JS/Razor analysis. Exhaustive, deterministic per commit date.
Top hotspots: app/src/main/java/io/xpipe/app/storage/DataStorage.java (19×29=551); app/src/main/java/io/xpipe/app/hub/entry/StoreEntryWrapper.java (13×38=494); app/src/main/java/io/xpipe/app/browser/file/BrowserFileTransferOperation.java (7×34=238) Repeated repair below the complexity floor: app/src/main/java/io/xpipe/app/hub/category/StoreCategoryWrapper.java (10 of 12 changes were fixes); app/src/main/java/io/xpipe/app/process/ShellTemp.java (9 of 10 changes were fixes); app/src/main/java/io/xpipe/app/util/FilePath.java (7 of 10 changes were fixes)
Resolve the 34 Repeated repair finding(s) in Churn × Complexity Hotspots — start with StoreCategoryWrapper.java, ShellTemp.java, FilePath.java. — One of this dimension's main actionable groups (34 warning-level).
Resolve the 32 Hotspot finding(s) in Churn × Complexity Hotspots — start with DataStorage.java, StoreEntryWrapper.java, BrowserFileTransferOperation.java. — One of this dimension's main actionable groups (32 warning-level).
Detailed fixes: d15_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Acknowledged debt left in the code — TODOs, dead code, suppressed warnings.
Method: Roslyn syntactic debt markers (suppressions/TODO/FIXME/HACK/empty-catch/commented-code/Obsolete) plus SymbolFinder dead-code analysis; weighted-debt-per-KLoC density deducted 2.0x per unit. Deterministic, exhaustive.
5 deducted task-comment markers across 93315 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.
Resolve the 5 TodoComment finding(s) in Explicit Debt — start with AppDesktopIntegration.java, DataStateHandler.java, ZellijTerminalMultiplexer.java. — One of this dimension's main actionable groups (5 warning-level).
Stand up a CI pipeline, then gate Explicit Debt in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the project's documentation is clear, complete, and useful.
Method: Judged by language model at low temperature (0.0-0.1) on a deterministic doc sample (READMEs plus first 25 architecture docs), with two-pass stability filtering. Advisory, sampled.
The repository's root README gives a strong overview of XPipe as a connection-hub platform covering SSH, Docker, containers, virtual machines, Tailscale, AWS/Hetzner, Windows Subsystem for Linux, Kubernetes, and PowerShell remote sessions. It lists the supported connections with links to dedicated guides (SSH, Docker, Podman/LXD/Incus, Proxmox, Hyper-V/KVM/Vmware, Tailscale, Netbird, Teleport, AWS, RDP/VNC), plus a Windows/macOS/Linux distribution guide and download options for binaries, Docker containers, and tarballs. The lang/README is focused on translations with an explicit How-to section describing the DeepL workflow, correction syntax (custom annotation), and automatic-translation improvement; it is well-motivated but not as comprehensive as the root README. The gradle/gradle_scripts README documents a build-component directory without context about what the repository's main project does.
What to do
Improve Documentation Quality — currently 7.0/10. — The repository's root README gives a strong overview of XPipe as a connection-hub platform covering SSH, Docker, containers, virtual machines, Tailscale, AWS/Hetzner, Windows Subsystem for Linux, Kubernetes, and PowerShell remote sessions. It lists the supported connections with links to dedicated guides (SSH, Docker, Podman/LXD/Incus, Proxmox, Hyper-V/KVM/Vmware, Tailscale, Netbird, Teleport, AWS, RDP/VNC), plus a Windows/macOS/Linux distribution guide and download options for binaries, Docker containers, and tarballs. The lang/README is focused on translations with an explicit How-to section describing the DeepL workflow, correction syntax (custom annotation), and automatic-translation improvement; it is well-motivated but not as comprehensive as the root README. The gradle/gradle_scripts README documents a build-component directory without context about what the repository's main project does.
Detailed fixes: d19_recommendation.md.
Do you agree with this assessment?
D20 · ADR Quality0.0 / 10Critical✓ Tool-verified
What it measures: Whether architecture decisions are recorded well (context, decision, consequences).
Method: Per-ADR judgment by language model at low temperature with two-pass stability; confidence is share of ADRs evaluated; enforcement-field presence detected deterministically. Advisory.
What it measures: Whether names — types, methods, variables — are clear and consistent.
Method: Judged by language model at low temperature (0.0-0.1) on a deterministic random symbol sample (fixed size, not exhaustive), with disclosed confidence band. Advisory, sampled.
0 naming inconsistencies across 0 sampled symbols.
✓ On the Gold path — maintain.
Detailed fixes: d21_recommendation.md.
Do you agree with this assessment?
D22 · Internal API ConsistencyStronggated by 2 serious findings◐ Sampled · advisory
What it measures: Whether the internal API surface is consistent and coherent.
Method: Judged by language model at low temperature over a sample of the public API surface (IsPackable or .Contracts types). Sampled, advisory; confidence discounted by model uncertainty.
2 API inconsistencies across a 400-member sample of 1175 exposed types.
Inconsistent naming for validation/completeness checks across different domain types. While `checkComplete` is the dominant pattern, `ScriptTextSource`, `InPlace` (script), `Url`, and `SourceReference` also expose `checkAvailable(): void`. This suggests a distinction between 'available' (e.g., file exists, URL reachable) and 'complete' (all fields filled), but the API surface exposes both on some types (e.g., `ScriptTextSource` has both) while others only have `checkComplete`. More critically, `IdentityValue` and its subtypes (`InPlace`, `Ref`) have granular checks like `checkCompletePassword()`, `checkCompleteSshIdentity()`, etc., whereas other stores use a single `checkComplete()`. This forces consumers to handle different validation strategies depending on the type.
Inconsistent factory method naming and return types in `IdentityValue`. Most `of` methods return `InPlace`, but `ofBreakout` and `ofCategory` return `IdentityValue`. This breaks the expectation that `of` methods are simple constructors/factories returning the same type. `ofBreakout` implies a transformation or unwrapping, while `ofCategory` implies a lookup or creation, yet they share the `of` prefix with simple constructors.
What to do
Resolve the 1 Inconsistent naming for validation/completeness checks across different… finding(s) in Internal API Consistency. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 Inconsistent factory method naming and return types in `IdentityValue`.… finding(s) in Internal API Consistency. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d22_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D26 · Project Cohesion4.3 / 10Weak✓ Tool-verified
What it measures: Whether each project is a focused, coherent unit rather than an oversized grab-bag.
2 of 6 build units (Gradle) flagged as possibly oversized/incoherent.
Projects may be oversized for their cohesion
What to do
Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d26_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.
Method: Secret scan via TWO gitleaks detect passes in an isolated checkout — the full git history, then a second --no-git pass over the working tree as it stands — merged and de-duplicated by (rule, file, line); each match flagged High. Both invocations are recorded in the audit trail. Exhaustive; when the tool is absent, or when its output cannot be parsed into the expected shape, the dimension is WITHHELD as an explicit measurement gap on our side — unscored and excluded from the lens, never a hedged middling score.
What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.
Method: Polyglot static analysis via semgrep across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.
Coverage: semgrep pattern rules over all files — exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).
9 finding(s): 0 critical, 3 high, 4 medium, 2 low. semgrep hit a parse error in 30 file(s) — `app/src/main/java/io/xpipe/app/browser/action/impl/OpenFileNativeDetailsActionProvider.java` (line 47, line 71, line 90), `app/src/main/java/io/xpipe/app/browser/menu/impl/BrowseInNativeManagerMenuProvider.java` (line 32, line 33, line 34), `app/src/main/java/io/xpipe/app/browser/menu/impl/EditFileMenuProvider.java` (line 51, line 52, line 54), `app/src/main/java/io/xpipe/app/browser/menu/impl/GradleRunMenuProvider.java` (line 41), `app/src/main/java/io/xpipe/app/browser/menu/impl/OpenFileDefaultMenuProvider.java` (line 40, line 41, line 42), … (+25 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
+ 2 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether anyone still has living knowledge of each file, or it has been orphaned — last understood long ago by someone now gone quiet. The sibling of the bus factor: D16 asks who owns it, D34 asks whether anyone still knows it.
Method: File orphaning as total living-knowledge decay below one focused-commit's worth within a year, computed per-file from the D16 decay model. Exhaustive, deterministic over fixed history.
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 473 of the 1014 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.
Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.
Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling. A non-source file is never a coupling PARTICIPANT either: documentation, schemas, config and data files are dropped with the rest, so a code↔docs pair — a command and the reference page that restates it — is not reported however strongly the two co-change; nor is coupling that runs THROUGH a build step or config file.
Resolve the 2 Change coupling finding(s) in Change Coupling — start with BrowserContextMenu.java, AppDirectoryPermissionsCheck.java. — One of this dimension's main actionable groups (2 warning-level).
Detailed fixes: d35_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the repository publishes a coordinated-vulnerability-disclosure policy (SECURITY.md or security.txt) with a reporting contact, so finders know how to report a vulnerability. Presence of a policy file with a contact, not whether the policy is adequate or honoured.
Method: Vulnerability-disclosure policy read deterministically from the repo: a SECURITY.md (root/.github/docs) or .well-known/security.txt / security.txt, regex-checked for a reporting contact (email / URL / mailto). Present + contact → 10; present without a contact → 4; NotApplicable when no policy file exists (it may live off-repo). Detects the policy file's presence + contact, not its adequacy.
What it measures: Whether anyone still ships security patches for the platform this repository RUNS ON — the runtime it pins and the framework majors its own constraints hold it to. Separate from D12 because the question differs: a current Django on an end-of-life Python is perfectly up to date and completely unsupported, and the fix is a migration rather than a version bump. What the repository says it merely SUPPORTS is never charged.
Method: End-of-life PLATFORM read from the repository's own declarations and graded against a FROZEN, dated table of vendor support dates — no network, no feed, no API, so this dimension answers identically inside a closed scan fence. Two subjects: a RUNTIME the project pins (a single or all-end-of-life TargetFramework, a .nvmrc or .python-version, a requires-python CAP) and a FRAMEWORK major a dependency constraint cannot move off (a caret, tilde or exact version; `vue@^2.7.16` pins Vue 2). A FLOOR is deliberately never charged — `requires-python = ">=3.8"` states what a package SUPPORTS, not what it runs on — and a multi-target project is charged only when EVERY target is out of support. Runtime 4.0/product capped 8.0, framework 1.5 capped 4.5. The table is safe to freeze because a statement about support that ended in the past cannot become false: it loses recall as it ages, never precision, and a test asserts every entry predates the freeze date. Disjoint from D31 (a container image's OS layer) and D29 (the toolchain a CI workflow installs). Abstains when the repository declares no platform this pass reads — never scores it clean.
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 1 platform declaration(s) and 56 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.
Other · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified. How each file's role is decided, because the split is only as good as that: a generated name or a build-output tree makes it Generated, a test project makes it Test, and otherwise the file's NAMESPACE and PATH words are matched against fixed vocabularies in a fixed ORDER — domain, then infrastructure, then application — so a file whose words hit two layers is counted under the earlier one. A production file matching none of them counts as application, so that share reads 'application or unclassified' rather than a measured application layer. Roles come from naming convention, never from what the code does. On this repository the split was taken from the source tree on disk rather than from a loaded .NET workspace, so a file's role is decided by its PATH segments alone — no declared namespace was available to add to the evidence — and generated output is excluded from the census entirely rather than counted as a generated share.
Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.
Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.
What to do
The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
Other · Architecture — Whether the project-reference graph is acyclic (cycles block independent build/deploy and signal eroding boundaries).
Method: Project reference cycles via elementary-DFS over real .csproj references, using the engine shared with D5/D7; cyclic versus acyclic. Exhaustive, deterministic.
Other · Architecture — Whether dependencies point inward (Domain ← Application ← Infrastructure/Web) — the clean-architecture dependency rule, checked across the project graph.
Method: Layer violations by name-segment inference (Domain/Core to Application to Infrastructure/Web) over the project-reference graph. Exhaustive over all projects, deterministic.
Other · Architecture — Whether interfaces stay focused rather than fat — the Interface-Segregation principle (SOLID 'I').
Method: Roslyn scan: public interface declared-member counts (accessors fold into their property/event); fat-interface threshold (over 15 declared members) flagged per type. Each finding also reports the distinct-OPERATION count — members counted by name, so an overload group counts once — which decides whether it states the caller-side ISP harm or the implementer-side burden of an overload set. TypeScript: exported interfaces that declare behaviour, counted over their REQUIRED operations (method signatures and function-typed properties with no `?`, once per signature) — data-shape interfaces and ambient .d.ts declarations are outside the population; JavaScript declares no interfaces and is not applicable. Deterministic, type-level.
`DataStorageSyncHandler` declares 20 abstract methods: `addDataFile`, `afterStorageLoad`, `afterStorageSave`, `beforeStorageSave`, `getDataFile`, `getDirectory`, `getSavedDataFiles`, `handleCategory`, `handleDeletion`, `handleEntry`, `hasExternalStoredCredentials`, `init`, `prepareGpgIfNeeded`, `pullManually`, `pushManually`, `refreshRemoteData`, `reset`, `retrieveSyncedData`, `supportsSync`, `validateConnection`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants 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. — app/src/main/java/io/xpipe/app/storage/DataStorageSyncHandler.java:8
`ShellDialect` declares 69 abstract methods: `addToPathVariableCommand`, `assembleCommand`, `assignMissingExitCode`, `changeTitleCommand`, `clearDisplayCommand`, `createFileExistsCommand`, `createScriptTextFileWriteCommand`, `createStreamFileWriteCommand`, `createTextFileWriteCommand`, `deleteFileOrDirectory`, `determineCharset`, `directoryExists`, `doesEchoInputByDefault`, `environmentVariable`, `evaluateExpression`, `executeCommandWithShell`, `executeRobustBootstrapOutputCommand`, `fileArgument`, `formatError`, `getAskpass`, `getCatchAllVariable`, `getDiscardAllOperator`, `getDiscardStdoutOperator`, `getDisplayName`, `getDumbMode`, `getEchoCommand`, `getExecutableName`, `getFileCopyCommand`, `getFileDeleteCommand`, `getFileMoveCommand`, `getFileReadCommand`, `getFileTouchCommand`, `getId`, `getInitFileName`, `getLaunchCommand`, `getMkdirsCommand`, `getNewLine`, `getOpenScriptCommand`, `getPauseCommand`, `getPrintExitCodeCommand`, and 29 more. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants 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. — app/src/main/java/io/xpipe/app/process/ShellDialect.java:15
`ShellControl` declares 59 abstract methods: `buildElevatedCommand`, `checkLicenseOrThrow`, `closeStdout`, `command`, `elevated`, `exitAndWait`, `getActiveReplacementBackgroundSession`, `getEffectiveSecurityPolicy`, `getElevationHandler`, `getExitUuids`, `getLocalSystemAccess`, `getLock`, `getOriginalShellDialect`, `getOsName`, `getOsType`, `getParentControl`, `getParentSystemAccess`, `getSourceStore`, `getSourceStoreId`, `getStderr`, `getStdin`, `getStdout`, `getSubTemporaryDirectory`, `getSudoCache`, `getSystemTemporaryDirectory`, `getTtyState`, `isExiting`, `isInactive`, `isInitializing`, `isInteractive`, `isLocal`, `isSubShellActive`, `onExit`, `onInit`, `onKill`, `onStartupFail`, `prepareIntermediateTerminalOpen`, `requireLicensedFeature`, `restart`, `setDumbOpen`, and 19 more. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. Those 59 declarations carry 58 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 58 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. 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. — app/src/main/java/io/xpipe/app/process/ShellControl.java:23
`CommandControl` declares 24 abstract methods: `complex`, `discardOrThrow`, `elevated`, `getDisplayCommand`, `getExitCode`, `getParent`, `getTerminalCommand`, `noActivity`, `notComplex`, `readRawBytesOrThrow`, `readStdoutAndStderr`, `readStdoutIfPossible`, `readStdoutOrThrow`, `sensitive`, `setExitTimeout`, `setStartTimeout`, `start`, `startExternalStdin`, `startExternalStdout`, `waitFor`, `withCustomCharset`, `withErrorFormatter`, `withExceptionConverter`, `withWorkingDirectory`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants 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. — app/src/main/java/io/xpipe/app/process/CommandControl.java:13
`FileSystem` declares 47 abstract methods: `cd`, `chgrp`, `chmod`, `chown`, `copy`, `createTransferOptimizedFileSystem`, `delete`, `directoryAccessible`, `directoryExists`, `fileExists`, `getDirectorySize`, `getFileInfo`, `getFileSeparator`, `getFileSize`, `getIdentifier`, `getRawShellControl`, `getShell`, `getSuffix`, `getTerminalShellControl`, `hasAccurateProgress`, `isRunning`, `kill`, `listCommonDirectories`, `listFiles`, `listRoots`, `makeFileSystemCompatible`, `mkdirs`, `move`, `open`, `openInput`, `openOutput`, `pwd`, `readInstantIfPossible`, `reinitIfNeeded`, `requiresReinit`, `supportsChgrp`, `supportsChmod`, `supportsChown`, `supportsDirectorySizes`, `supportsLinkCreation`, and 7 more. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants 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. — app/src/main/java/io/xpipe/app/fs/FileSystem.java:19
What to do
Split fat interfaces into focused role-interfaces so clients depend only on what they use.
Other · Code Health — Unfinished work detected by code SHAPE, not keywords, in this repository's Java: methods that only throw a "not implemented" exception, methods that take inputs and return a constant or do nothing, dead `if (false)` branches, and skeleton classes most of whose methods are holes.
Method: Roslyn syntax scan: incompleteness by code shape (constant-returning methods, async-never-await, #if false branches, guards that return what the code already falls through to, tests an earlier guard already decided, comparisons against NaN, skeleton types), not keyword-gated. Deterministic, code-shape heuristic.
`@SuppressWarnings("all")` switches every compiler and analyser warning off for the whole declaration — hidden debt. Suppress the specific warning on the specific member, with a justification, instead. (×3) — app/src/main/java/io/xpipe/app/util/AppJacksonModule.java:412, app/src/main/java/io/xpipe/app/util/AppJacksonModule.java:432, app/src/main/java/io/xpipe/app/util/AppJacksonModule.java:494
What to do
Clear the softer debt: re-enable or delete @Disabled/@Ignore tests, decide whether each empty method or UnsupportedOperationException is deliberate (and say so in a comment), and replace @SuppressWarnings("all") with targeted, justified suppressions.
Maturity · Maturity — Whether the repo and its projects have a README, and whether it's substantive and current.
Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.
What to do
Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
Add a README to the 6 of 6 project(s) that lack one — worth up to 2 pts.
Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.
Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.
No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
Maturity · Maturity — Whether the README actually describes the code that exists (LLM-judged, advisory).
Method: Judged by language model at low temperature: README accuracy versus actual projects, within a disclosed tolerance. Advisory, not a measured number.
Do you agree with this assessment?
P1 · CI/CD gates0.0 / 10Critical✓ Tool-verified
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.
No CI workflow found (.github/workflows, azure-pipelines.yml, .gitlab-ci.yml, …) — changes aren't gated by an automated build/test.
What to do
Add a CI workflow that builds and runs the test suite on every push/PR.
Do you agree with this assessment?
P10 · Library API & versioning6.0 / 10Adequate✓ Tool-verified
Readiness · Readiness — For a library: a deliberate (small) public API surface and explicit semantic versioning so consumers can depend on it safely.
Method: Roslyn scan: public API surface area and semantic-versioning markers (SemVer attributes, changelog entries) for libraries; off .NET, a library is the ecosystem's publication act (an npm package that is not private and names an entry point, a PyPI distribution with a build system, a Rust library crate, a Maven/Gradle module that publishes, a Go module with no package main, a gemspec, a Composer library, a SwiftPM library product, a pub.dev or Hex package), its surface is the share of types the language model records as public (Rust, Swift, Java, Kotlin, Go, Dart; not measured where the model records no type visibility or, as in TypeScript, only module-level export), and its version is read from the manifest, a semver CHANGELOG, release tooling or semver git tags. Exhaustive, deterministic.
1172/1347 types (87%) declared in the published library are public. For a library, every public type is a stability contract — keep implementation types off the surface and expose only the intended API.
What to do
Keep implementation types off the public surface (Java: package-private (no modifier), or leave its package out of `module-info` exports) so internals can change without breaking consumers.
Do you agree with this assessment?
P2 · Observability7.0 / 10Strong✓ Tool-verified
Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.
Consider OpenTelemetry tracing/metrics (opentelemetry-java or Micrometer) and a health-check endpoint (Spring Boot Actuator's /actuator/health, or a /health route) for operability.
Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).
Method: Filesystem scan: SAST configuration, dependency-update automation, secret scanning, and a benchmark harness or benchmark step — in this repository's own ecosystem. Exhaustive, deterministic.
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) — this repository has no CI pipeline yet, so run it locally to clear the existing findings, then make it a step of the first workflow you add so a regression fails the build. What was searched, so you can tell an absence from a miss: the 0 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.
What to do
Run what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — locally for now, since there is no CI pipeline here yet, and as a step of the first workflow you add so a security regression fails the build instead of landing.
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
Readiness · Performance — Whether the code is written to minimise allocations so it doesn't pressure its host's memory manager — buffer/slice views over copies, object pooling, stack or value-type allocation, and buffer writers. Reward-only: credited where present, never penalised where a simpler style is fine.
Method: Production-source scan: density (per 1k LoC) of allocation-aware APIs — in .NET Span/Memory, ArrayPool/ObjectPool, stackalloc, ValueTask, value-type structs, IBufferWriter, string.Create, SkipLocalsInit; off .NET, with comments and strings blanked, Go's sync.Pool, preallocated slices/maps, Grow, strconv.Append* and buf[:0] reuse; the JVM's NIO buffer views, MemorySegment, primitive collections, pools and literal presizes (plus Kotlin primitive arrays and value classes, Scala AnyVal and @specialized); Swift's reserveCapacity, ContiguousArray, withUnsafe* access and ~Copyable. Activated off .NET on the same floor (400 lines, and benchmarks or 8 uses); Rust and garbage-collected scripting languages are not applicable. Reward-only. Deterministic, syntax/text detection.
What to do
Raise allocation-aware density on the hot paths — currently 12 use(s) across 110,510 production line(s) (~0.1/1k). More of the idioms below on the allocation-heavy paths climbs this toward 10.
Java: on hot paths, work through buffer views (ByteBuffer/LongBuffer slices, MemorySegment) instead of copies, avoid boxing with primitive collections (fastutil, Eclipse Collections, HPPC, Trove), presize collections and StringBuilders, and pool expensive buffers (Netty's pooled allocator, commons-pool).
Readiness · Performance — Whether asynchronous code stays responsive — it avoids sync-over-async blocking (a .NET .Wait()/.GetAwaiter().GetResult(), a time.sleep or blocking HTTP call inside a Python coroutine, a *Sync call inside an async JavaScript function, block_on inside a Rust async fn, runBlocking inside a Kotlin suspend function, block() inside a Reactor publisher) that stalls a thread or event loop and risks deadlock, and, where the code is a reusable library on .NET, awaits with ConfigureAwait(false) so it never captures and stalls its caller's context.
Method: Production-source scan: sync-over-async blocking counted everywhere — .Wait()/.GetAwaiter().GetResult() in .NET; off .NET, read from the language model, a blocking call inside an async function (Python, TS/JS, Rust, Kotlin, Swift, Dart) or inside a Java method returning a Reactor Mono/Flux or a Scala method returning a Future or effect — and, for a .NET library with ≥5 awaits, the share of awaits using ConfigureAwait(false). Deterministic, syntax/text detection.
`closeGracefully` is async and calls .block() — a blocking call inside async code stalls the event-loop thread the reactive pipeline runs on for as long as it runs. — app/src/main/java/io/xpipe/app/beacon/mcp/HttpStreamableServerTransportProvider.java:118
`notifyClients` is async and calls .block() — a blocking call inside async code stalls the event-loop thread the reactive pipeline runs on for as long as it runs. — app/src/main/java/io/xpipe/app/beacon/mcp/HttpStreamableServerTransportProvider.java:93
What to do
Java (Reactor): compose the publisher (flatMap/zipWith) instead of block(), and isolate unavoidable blocking calls with subscribeOn(Schedulers.boundedElastic()).
Other · Security — Whether a hand-rolled public/private IP check can be walked past — a method that unwraps IPv4-mapped IPv6 but returns the opposite verdict for the same host written as IPv4-compatible, 6to4 or NAT64.
Method: Roslyn syntax + semantics: methods that unwrap IPv4-mapped IPv6 and hand-roll IPv4 range carve-outs, checked for whether the IPv6 branch also accounts for the IPv4-compatible, 6to4 and NAT64 embeddings. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X15 · Unvalidated length from an untrusted reader10.0 / 10Exemplary○ Nothing flagged
Other · Security — Whether a length read out of the stream being parsed is bounded before it is allocated or read — an unchecked count taken from the input lets the input choose the allocation.
Method: Roslyn syntax + semantics: integer lengths read from a BinaryReader and spent on a bulk read or an array allocation, checked for any comparison or bounding call on the value anywhere in the method. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a loop that shortens a string until it fits a length budget has a floor — one with none grinds the value down to the empty string, or past it into a negative-length `Substring`.
Method: Roslyn syntax + semantics: while/do loops whose body's only effect on a string is to drop its last character, checked for whether anything — a direct comparison on the length, a body guard, a break — bounds that length below. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `while`/`do` loop whose body’s one assignment to a value is `x = x.slice(0, -1)` or `x = x.slice|substring|substr(0, x.length - 1)`, driven by a condition that reads `x.length` only as a term of a larger expression — never compared directly, never tested for truthiness, and with no other read of `x` — and whose body has no `break`, `return`, `throw` or `if` naming `x`. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a type's disposal matches what it OWNS — releasing what it created, leaving alone what it was handed, and not declaring a finalizer for state that has nothing unmanaged to finalize.
Method: Roslyn syntax + semantics: every assignment to a disposable field is read to decide whether the type CREATED the value or was handed it, and the type's disposal is checked against that answer — an injected interface it disposes, a value it constructed and never releases, a finalizer on a type holding nothing unmanaged, and a disposable local whose every reference is a plain member read. A value handed to a container that disposes its contents (a parent control's `Controls` collection, a component `IContainer`) is released by that container and is not reported; generated code is out of population. On a repository with no .NET source the same ownership questions are read in JavaScript/TypeScript off the engine’s own token stream (test, vendored, generated and minified paths not): a class declaring `dispose()`, `[Symbol.dispose]()` or `[Symbol.asyncDispose]()` that disposes a field it was handed through a constructor parameter typed as a repository interface or resolved by a dependency-injection container; that assigns a field only ever from `new X(…)` of a disposable class and neither releases it anywhere in the class nor names it in its disposal member or a method that member calls, nor hands it to anything else; and a `const`/`let` local built from literals only whose every reference opens a statement operating on a non-release member of it. A class is disposable when every repository declaration of its name declares or inherits a disposal member, or when it is a documented library disposable (`vscode` EventEmitter, CancellationTokenSource and Disposable; three.js geometries, materials, textures, render targets, renderers, controls and composers). The finalizer arm has no JavaScript counterpart: a class cannot declare one. Dart is read for the owned-and-never-released arm: a Flutter `State` (or a class declaring `dispose()`/`close()`) whose library-private field is written only with direct creations of a framework controller, `FocusNode`, `StreamController` or periodic `Timer` (or a `.listen(…)` into a field declared `StreamSubscription`), which nothing in the class or its library releases (`dispose`/`close`/`cancel`) and which is never handed on except as a named argument. Ruby is read for the owned-and-never-released arm and the abandoned-local arm: a class declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose instance variable is written only with a blockless core descriptor creation (`File.open`/`new`, `Tempfile`, `Dir.open`, `IO.popen`, the `socket` and `openssl` socket classes) that no method of the class closes and that is never handed on (passed, returned, stored, exposed by `attr_reader`, delegated) — a class whose superclass or mixin lies outside the repository is not judged — and a blockless creation read through and dropped (`File.open(path).read`) or held in a local that is never closed, returned, passed or stored (a `&:read` block-pass, an `autoclose: false` borrow and a `fileno` hand-over are not abandonment). PHP is read for the same two arms: a class (not a trait, and not one using a trait) declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose `private` property (or a `final` class's `protected` one) is written only with a direct core `fopen`, `tmpfile`, `popen`, `proc_open`, `fsockopen`, `stream_socket_client`/`server` or `opendir` that nothing in the class closes (`fclose`, `pclose`, `closedir`, `unset`, a reset to `null`) and that is never handed on, and a handle held in a function's local, or read through as the argument of a reader, that is never closed, returned, passed, captured or stored; a `php://` stream, `curl_init`, `SplFileObject`, `PDO` and a function the repository declares under the core name are not read. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a method that temporarily changes state belonging to the whole process — the working directory, an environment variable — puts it back on EVERY path: a restore reached only when nothing throws leaks the change to the rest of the process.
Method: Roslyn syntax + semantics: method bodies that write the process working directory or an environment variable and write it back in the same body, checked for whether that restore sits in a `finally`/`catch` or only on the straight-line path. On a repository with no .NET source the same rule reads production JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not): `process.chdir`, `process.env.NAME =`/`["NAME"] =` and `delete process.env.NAME`, and Deno’s `Deno.chdir`/`Deno.env.set`/`Deno.env.delete`, paired per function body (a nested function or arrow is its own body, and module top-level code is none), where the last write puts back a local the body captured from the same global or deletes a variable the first write set, with at least one statement between them; a write in a `catch`/`finally` of that body silences it. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether an argument guard throws the exception its own condition describes — a guard that rejects a value for being EMPTY and reports it as `NullPointerException` (Java, Kotlin, Scala), `ArgumentError.notNull` (Dart) or `ArgumentNullException` (F#'s `nullArg`) tells the caller a parameter was null when it provably was not.
Method: Roslyn syntax: `throw new ArgumentNullException(nameof(p))` statements controlled by an `if`, whose condition is read for a test that is true of a NON-null `p` — an emptiness test that dereferences it (`p.Count == 0`, `!p.Any()`) or a BCL predicate documented true of the empty value (`string.IsNullOrEmpty(p)`). Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a `when` guard is free of side effects — a guard that increments a counter or assigns while deciding whether its arm matches applies that change during PATTERN MATCHING, on an arm that may not be selected, and skips it entirely when a short-circuit to its left answers first.
Method: Roslyn syntax: `when` guards on case labels and switch-expression arms, read for a mutation (`++`/`--`/assignment) sitting in a position the guard's own `&&`/`||`/`??`/`?:`/`?.` can skip. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a method that TAKES a lock or semaphore and gives it back from a flag-guarded `finally` returns the value that flag implies — reporting success while the guard hands the primitive back admits a second caller the exclusion was there to keep out, and reporting failure while the guard keeps it leaves nothing to ever give it back.
Method: Roslyn syntax: `try` statements whose `finally` releases a synchronisation primitive under a bare local-bool guard, where the method also TOOK that same primitive before the `try`, checked for a `return` of a bool literal whose value disagrees with the flag state the method's own straight-line assignments put it in. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether the work a diagnostic log line costs is paid only when that line is wanted — C# evaluates a call's arguments BEFORE the call, so a trace/debug message joined or projected out of a collection is built in full on every pass, and then discarded by a sink the shipped configuration leaves switched off.
Method: Roslyn syntax: log calls at a diagnostic level (a `Log`-prefixed method naming Trace/Debug/Verbose, or a bare `Debug`/`Trace`/`Verbose` on a receiver named for a logger), whose argument list is read for a call whose cost scales with a sequence — a LINQ operator, a materialisation, `string.Join`, a serializer — with no enclosing level check or conditional-compilation region. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `debug`/`trace`/`verbose` call on a receiver named for a logger, or a `log`-prefixed method naming the level, whose argument calls an array operator (`map`/`filter`/`reduce`/`sort`/…), `Array.from`, `Object.keys/values/entries`, `JSON.stringify`/`util.inspect` over anything but a literal, or an array `join` — outside any arrow or function passed as an argument, which the logger calls only when the level is on — with no enclosing `if`, `&&` or `?:` whose condition names a level, a level string, or the `NODE_ENV`/`__DEV__`/`DEV` build switch. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X24 · Document value interpolated into markup unescaped10.0 / 10Exemplary○ Nothing flagged
Other · Security — Whether text read out of the document being converted is escaped before it is written into generated markup — a value the document's author chose, interpolated into an attribute the surrounding literal delimits, can close that attribute and open another.
Method: Roslyn semantic model over the whole compilation: a string-typed `Value`/`InnerText`/`InnerXml`/`Text` member declared inside `DocumentFormat.OpenXml` or `System.Xml` is a taint SOURCE, propagated through assignments, returns, arguments, tuple elements and string composition to its transitive closure, then read at interpolated-string holes that sit in a markup position the surrounding literal itself delimits. Escaper/encoder calls and enclosing validator conditions cut the flow. Flow- and container-insensitive by construction. A second arm needs no provenance at all and reports a type that CONTRADICTS ITSELF — the same expression escaped at one delimited markup hole and interpolated raw at another hole in the same markup position of the same type, which the type's own escaping proves is a defect without knowing where the value came from. On a repository with no .NET source it reads JavaScript/TypeScript off the token stream with the same rule: a DOM read of raw document text (`getAttribute`, `textContent`, `innerText`, `nodeValue`) is the source, propagated through local bindings and string composition, and judged at template-literal and concatenation holes in the same two delimited markup positions; escapers and validating conditions cut it, and documentation-site, test, vendored and minified scripts are not read. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a value the caller is invited to supply is the value the type actually uses — a constructor parameter stored in a private field that nothing ever reads while the default it was given is spelled out a second time at the site that should have read it, a keyed lookup that falls back to a different setting than the one its key names while the same type falls back to the matching one for that same key, or a culture-sensitive parse given no format provider by a type that feeds its own settable culture to the same kind of parse elsewhere, or a number an entry point writes to standard output under the host's culture while the same entry point formats with the invariant culture elsewhere. Either way, every caller who supplies a value silently gets something else.
Method: Roslyn syntax: private instance fields of a non-partial type assigned in a constructor from one of its own parameters with a `??` fallback, checked for whether anything in the type body reads the field and whether that same fallback expression is spelled out again outside the constructor; and `??` fallbacks onto a member access from a lookup call carrying exactly one string literal, grouped by that key across the type and checked for a fallback member whose folded name disagrees with the key while a sibling site for the same key agrees with it. On a repository with no .NET source the first two arms read JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `#x`, `private` or `private` parameter-property instance field filled in the constructor from a parameter (or one member of one) through `??`/`||` or a parameter default, never read anywhere in the file by name, whose constructed default is spelled again in the class body; and `lookup("key") ?? s.member` grouped by key per class, or per module outside every class. The culture arm has no JavaScript counterpart: its parses take no locale. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a value handed from a callback to the body that waits on it crosses on something built to be crossed — a `Queue<T>`/`List<T>`/`Dictionary<K,V>` written inside an event handler and read back outside it is mutated by two flows at once, and the semaphore or completion source beside it orders how MANY items exist while leaving the collection's own head, tail and backing array unprotected.
Method: Roslyn syntax: method, accessor, local-function and lambda bodies that declare BOTH a non-thread-safe generic collection (`Queue`/`Stack`/`List`/`Dictionary`/`HashSet`/`Sorted*`/`LinkedList`) and a synchronisation primitive (`SemaphoreSlim`/`TaskCompletionSource`/`ManualResetEvent(Slim)`/`AutoResetEvent`/`CountdownEvent`) as locals, then read for a `+=`-registered lambda that raises that primitive while the body outside every lambda waits on it — and, in that scope, a mutating call on the collection inside the lambda paired with a mention of it outside. Any `lock` in the scope abstains it. On a repository with no .NET source the same handoff is read in Java off the engine’s own token stream (test source sets, vendored and demonstration paths not): an `ArrayList`/`LinkedList`/`ArrayDeque`/`PriorityQueue`/`Hash*`/`LinkedHash*`/`Tree*` local and a `CountDownLatch`/`Semaphore`/`CompletableFuture` local, a lambda or anonymous class that raises the primitive and mutates the collection, and a wait outside it; any `synchronized` or `lock()` abstains the body. Because each of those primitives orders what the callback wrote before raising it, only a touch that provably overlaps the callback is convicted: one after the registration and before the next wait, or one in a loop registered-before, waiting on every pass and not declaring the collection. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X27 · Collection changed while being enumerated10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether an enhanced `for` leaves the collection it is walking alone — a body that adds to or removes from the very collection the loop is iterating invalidates the fail-fast iterator it is holding, so the next `next()` throws `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.
Do you agree with this assessment?
X28 · Index access outside its own emptiness guard10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a condition that tests a value for emptiness indexes that same value only where the test holds — an `||` written one parenthesis too far to the left leaves an index access outside the guard beside it, so the empty case the guard exists to anticipate reaches the index and throws.
Method: Roslyn syntax only, no semantic model: the OUTERMOST `&&`/`||` of every boolean condition, read for a symbol the condition tests for emptiness (`string.IsNullOrEmpty`/`IsNullOrWhiteSpace`, a `Length`/`Count` comparison against a literal, `Any()`, a `Length`/`Count` pattern, or a comparison against `""`) and ALSO indexes. Each `symbol[...]` access is placed by a boolean-reachability walk from the access up to the outermost connective: an access is COVERED when some enclosing step has it in the right operand and the left operand, under the truth value that step forces, proves the symbol non-empty — a recursion over `&&`/`||` whose true- and false-directions are asymmetric. A finding needs BOTH an uncovered access and a covered one on the same symbol in the same condition, which is the agreeing twin that separates a misplaced parenthesis from an unrelated length test. Bare index accesses with no emptiness test in the condition are neither counted nor reported; a non-identifier receiver and a lambda nested inside the condition are outside the population. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X29 · Per-element action decided by a fixed element10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a decision taken once per element is taken ABOUT that element — a test inside a counted loop that reads a fixed subscript of the very collection its guarded statement indexes by the loop variable applies element zero's answer to all of them, so the elements that differ from it are all handled wrongly, and in the same direction.
Method: Roslyn syntax only, no semantic model: every `for` statement declaring exactly ONE loop variable, and every `if` inside its body that is not under a nested loop or a lambda. A site enters the population when the `if`’s condition never mentions the loop variable while the statement it guards indexes some collection by that variable ALONE (`c[i]`; `c[i + 1]` and `c[i, j]` are outside it). A finding additionally needs the AGREEING TWIN at the same-collection grain: the condition must read THAT SAME collection at a subscript that does not move — written into the condition, or reached through a local declared BEFORE the loop, so an alias bound inside the body is not followed. Both collection expressions must be simple identifiers. On a repository with no .NET source the same rule reads JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `for (let|var|const x = …; …; …)` with one declarator and a braced body, an alias followed only when it is declared before the loop in a block that encloses it and never assigned inside the loop. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether exceptions are handled rather than silently swallowed or rethrown with lost stack traces.
Method: Roslyn syntax scan: every catch clause counted; empty catches and bare rethrows flagged. Population is all catch clauses, not estimated. Deterministic, hard fact.
`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. (×5) — app/src/main/java/io/xpipe/app/beacon/BeaconServer.java:31, app/src/main/java/io/xpipe/app/browser/file/BrowserClipboard.java:106, app/src/main/java/io/xpipe/app/core/AppSystemInfo.java:202, …
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. (×16) — app/src/main/java/io/xpipe/app/browser/file/BrowserFileTransferOperation.java:740, app/src/main/java/io/xpipe/app/browser/file/BrowserFileTransferOperation.java:747, app/src/main/java/io/xpipe/app/core/AppSystemInfo.java:114, …
`catch (Throwable)` 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. — app/src/main/java/io/xpipe/app/store/DataStore.java:18
What to do
Swallowed exception (caught, then discarded)
Do you agree with this assessment?
X30 · Support guard that admits what it rejects10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a guard written as a NEGATED `||` says what its author meant — `!(a || b || x != k)` is `!a && !b && x == k` by De Morgan, so a bail-out that mixes capabilities the code needs with a fault it refuses turns inside out: it fires only where the capabilities are ABSENT, and lets every value the fault term names walk straight into the body that cannot handle it.
Method: Roslyn syntax only, no semantic model: every logical-not whose operand is a parenthesised `||` chain of two or more disjuncts, flattened (a left-nested `a || b || c` read once would see `(a || b)` as one disjunct). A site enters the population on that shape alone. A finding additionally needs the disjuncts to DISAGREE in polarity: at least one bare boolean read — an identifier or member access, never an invocation, which is a predicate rather than a capability flag — and at least one `x != <constant>`, the only form that negates into an exact-value pin (`== null` negates into a looser requirement and is outside the fault set). Consistently-polarised disjunctions, all-fault or all-capability, are counted and never reported; a negated `&&` is outside the population entirely. No same-receiver gate: it was measured to cost a real defect and remove no false positive. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether log calls use message templates (queryable) rather than interpolated strings.
Method: Roslyn syntax scan: every log call-site counted; interpolated-string first-argument violations flagged. Population is all log calls, not estimated. 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 `trace`/`debug`/`info`/`warn`/`error`/`fatal`/`verbose`/`silly`/`http`/`log` call on a receiver named for a logger, in a package whose own or an enclosing `package.json` declares a logger that carries values as fields (pino, pino-http, nestjs-pino, Fastify, winston, bunyan, tslog, LogTape, roarr), whose first deciding argument is a template literal with substitutions; an object-literal fields argument is stepped over, a plain string message clears the call. Python is read the same way: a `debug`/`info`/`warning`/`error`/`exception`/`critical`/`log` call on a logger in a file that imports the standard library’s `logging` or structlog (loguru, which formats at the call, is not judged), whose message is a whole f-string with a non-constant field; a `%`-formatted, `.format()`-ed or concatenated message is not convicted, as in C#. PHP is read the same way: a PSR-3 level call (`emergency`…`debug`, `log`) on a logger (`$logger`, `$this->logger`, Laravel’s `Log::`, `logger()`, `\Drupal::logger()`) in a package whose `composer.json` requires a PSR-3 logger or a framework that hands one out (psr/log, Monolog, Laravel, Symfony, Drupal, CakePHP), or a file that imports one, whose message is a double-quoted string interpolating a variable; a single-quoted message clears the call, and `sprintf` or `.` concatenation is not convicted, as in C#. Dart is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on Sentry’s structured logger (`Sentry.logger`) whose message is a whole string literal interpolating a value (`$name`, `${…}`); the `Sentry.logger.fmt` template API clears the call. Dart that logs only through loggers with one message and no fields (package:logging, package:logger, talker, dart:developer) is not applicable rather than a reach gap. Ruby is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on the console gem’s `Console` (declared by a Gemfile, gemspec or Gemfile.lock, or required) or, where SemanticLogger, Ougai or dry-logger is declared or required, on a receiver named for a logger (`logger`, `@logger`, `Rails.logger`, `log`), whose first deciding argument is, as the whole argument, a double-quoted string interpolating a non-constant value (`#{…}`, `#@ivar`); a plain literal clears the call, keyword arguments are the fields, and a block, `%`-format or `+` concatenation is not convicted. Ruby that logs only through the standard Logger (Rails.logger) is not applicable rather than a reach gap. Deterministic.
Other · Code Health — Whether Java packages are null-marked and not undermined by heavy nullness suppression — a package under `@NullMarked` (or `@NonNullApi`, `@ParametersAreNonnullByDefault`, `@NonNullByDefault`, or a NullAway/Checker Framework configuration naming it) makes an unannotated reference exclude null, and `@SuppressWarnings("NullAway")`, `("nullness")`, `("null")` and `castToNonNull(…)` are what silence it.
Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.
0/55 of this repository's Java package directories are under a non-null default: a `package-info.java` declaring `@NullMarked` (JSpecify) or `@NonNullApi`, `@ParametersAreNonnullByDefault`, `@NonNullByDefault`, `@DefaultQualifier(NonNull.class)`; a `module-info.java` declaring `@NullMarked`; every type in it `@NullMarked`; or a build that runs NullAway with the package in `AnnotatedPackages`, or the Checker Framework's `NullnessChecker`. Elsewhere every reference admits null and no checker warns on the dereference that throws a `NullPointerException`.
What to do
Declare the default where Java declares it: `@NullMarked` (org.jspecify.annotations) in each package's `package-info.java`, or once in `module-info.java`, and run NullAway (Error Prone) or the Checker Framework so the declaration is enforced. Then annotate the real exceptions `@Nullable` and resolve the suppressions rather than adding to them: a `@SuppressWarnings("NullAway")` or `castToNonNull(x)` on a value the checker could show to be null is a `NullPointerException` waiting for the path that makes it true — where the value genuinely cannot be null, say something the checker can see instead (a null check, `Objects.requireNonNull`, a non-null field initialised in the constructor).
Do you agree with this assessment?
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.
Unscored — 2 check(s) recorded observations but carry no score
These checks ran and found something, but they do not carry a score — either by design (an advisory check reports evidence rather than grading it) or because they could not be scored here. They are excluded from the score for that reason, not because there was nothing to see.
X10 Duplicated predicate — 25 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X7 Silent fallback defaults — 2 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 5 control(s) we could not find positive evidence for
These checks grade a working control, and the repository shows no evidence of one. That is deliberately not scored as a zero: a repository cannot show an ops runbook, a database TTL or an infrastructure-side audit log, so absence of evidence here is not evidence the control is missing. It is also not a statement that the check is irrelevant to this codebase — the thing it grades applies; we just could not see it. Excluded from the score either way.
C3 Audit Trail — Not assessed: these audit controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks audit controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C4 Data Retention — Not assessed: these retention controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks retention controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C5 Data-Subject Rights — Not assessed: these data-subject rights controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks data-subject rights controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 56 check(s) not relevant to this codebase
These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.
AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
AX1 Captive dependencies — Not applicable: this repository's Java imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No class in this Java code is a Spring, JSR-330 or CDI singleton bean.
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 — This repository has nothing the runtime tiers could boot or serve — no markup, no UI framework or web-server dependency, no UI component source, no native UI project and no API definition — nothing here is a surface to boot — so runtime a11y/egress/header evidence has no subject here. Not applicable: this is neither a gap in the scan nor a finding about your code.
AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
D11 Test Reliability — Test reliability not included — no .java test runner
D12 Dependency Hygiene — Not scored — 8 Maven/Gradle manifest(s) were read, stating a version for 50 dependency(ies) and leaving 0 to a parent or an imported BOM, but no build resolved the dependency graph, so the outdated signal was not established. NOT a finding that these dependencies are current or healthy.
D14 License Compliance — Not scored — this repository's 50 declared JVM dependency coordinate(s) were read from its 8 Maven/Gradle manifest(s), but Maven Central could not be asked for the licence of 50 of them (HTTP 429 Too Many Requests from https://repo1.maven.org/maven2/org/hamcrest/hamcrest/3.0/hamcrest-3.0.pom), and a licence verdict over part of a dependency graph is not a licence verdict. Nothing is asserted about this repository's licensing in either direction.
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.
D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ projects each declaring an entity of their own. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
D24 Comment Value — No inline comments to assess — comment value is not applicable here.
D25 ADR Conformance — no ADRs to check
D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.java), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
D30 Dependency Vulnerabilities — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Gradle build (build.gradle/build.gradle.kts) — not scanned yet).
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) — 29 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
D36 Supply-chain Provenance & Signing — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for.
D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
D43 Malicious Dependencies — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Gradle build (build.gradle/build.gradle.kts) — not scanned yet).
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 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (169 value object(s))
ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
P12 CI test-gate honesty — no CI workflow found
P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JVM 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 — no coverage report found on disk — produce a coverage report in a standard format (JaCoCo XML — the Gradle `jacocoTestReport` task) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
PF1 Benchmark discipline — 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.
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.
X1 Async correctness — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X12 Unreachable branch — 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
X13 Undrained process stream — 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
X17 Uncapped recursion over a caller-supplied document — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X2 Cancellation propagation — no C# was loaded; this repository's Java was read, and no request in it can be cancelled by a caller — a Java request off Android takes no token: it is cancelled through the handle it returns (Future.cancel, Call.cancel, a Disposable), ambiently (io.grpc.Context) or by interrupting its thread, not through a parameter
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.
X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
The findings behind the scores, grouped by severity, then by dimension and kind. The high-severity issues are enumerated in full below; items per group are capped at 25 with any overflow stated explicitly per group, never silently truncated. The complete machine-readable list of every finding (all severities) is the companion findings.md in this report's bundle.
Repeated repair: app/src/main/java/io/xpipe/app/hub/category/StoreCategoryWrapper.java app/src/main/java/io/xpipe/app/hub/category/StoreCategoryWrapper.java:310— app/src/main/java/io/xpipe/app/hub/category/StoreCategoryWrapper.java changed 12 times in last 90 days and 10 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 14 (its worst body is StoreCategoryWrapper.canMoveToThis at line 310), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “Various small fixes”; “Fix various exceptions”; “Various performance fixes”; “Various fixes”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-26..2026-10-24, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-26 04:25:12 +00:00' --until='2026-10-24 04:25:12 +00:00' --full-history --no-merges -- app/src/main/java/io/xpipe/app/hub/category/StoreCategoryWrapper.java`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: app/src/main/java/io/xpipe/app/process/ShellTemp.java app/src/main/java/io/xpipe/app/process/ShellTemp.java:27— app/src/main/java/io/xpipe/app/process/ShellTemp.java changed 10 times in last 90 days and 9 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 12 (its worst body is ShellTemp.initUserSpecificTempDataDirectory at line 27), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “Various fixes [stage]”; “Various small fixes”; “Various fixes”; “Various fixes”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-26..2026-10-24, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-26 04:25:12 +00:00' --until='2026-10-24 04:25:12 +00:00' --full-history --no-merges -- app/src/main/java/io/xpipe/app/process/ShellTemp.java`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: app/src/main/java/io/xpipe/app/util/FilePath.java app/src/main/java/io/xpipe/app/util/FilePath.java:166— app/src/main/java/io/xpipe/app/util/FilePath.java changed 10 times in last 90 days and 7 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 7 (its worst body is FilePath.getParent at line 166), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “Fix browser error with links pointing at self”; “Fix file path root detection”; “Fix file path starts with check”; “Various fixes”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-26..2026-10-24, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-26 04:25:12 +00:00' --until='2026-10-24 04:25:12 +00:00' --full-history --no-merges -- app/src/main/java/io/xpipe/app/util/FilePath.java`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: app/src/main/java/io/xpipe/app/core/AppProperties.java app/src/main/java/io/xpipe/app/core/AppProperties.java:79— app/src/main/java/io/xpipe/app/core/AppProperties.java changed 8 times in last 90 days and 6 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 14 (its worst body is AppProperties.<init> at line 79), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “Implement various fixes from other kickstartfx projects”; “Fix beacon auth path”; “Various fixes”; “Various fixes [stage]”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-26..2026-10-24, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-26 04:25:12 +00:00' --until='2026-10-24 04:25:12 +00:00' --full-history --no-merges -- app/src/main/java/io/xpipe/app/core/AppProperties.java`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: app/src/main/java/io/xpipe/app/hub/list/StoreViewState.java app/src/main/java/io/xpipe/app/hub/list/StoreViewState.java:709— app/src/main/java/io/xpipe/app/hub/list/StoreViewState.java changed 9 times in last 90 days and 5 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 14 (its worst body is 3.compare at line 709), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “Section performance fixes”; “Various fixes”; “Small fixes”; “Various UI fixes”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-26..2026-10-24, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-26 04:25:12 +00:00' --until='2026-10-24 04:25:12 +00:00' --full-history --no-merges -- app/src/main/java/io/xpipe/app/hub/list/StoreViewState.java`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: app/src/main/java/io/xpipe/app/hub/entry/StoreEntryBadge.java app/src/main/java/io/xpipe/app/hub/entry/StoreEntryBadge.java:226— app/src/main/java/io/xpipe/app/hub/entry/StoreEntryBadge.java changed 7 times in last 90 days and 5 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 10 (its worst body is 1.run at line 226), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “Various small fixes”; “Fix address context menu”; “Fixes for incomplete badges”; “Various fixes”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-26..2026-10-24, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-26 04:25:12 +00:00' --until='2026-10-24 04:25:12 +00:00' --full-history --no-merges -- app/src/main/java/io/xpipe/app/hub/entry/StoreEntryBadge.java`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: app/src/main/java/io/xpipe/app/terminal/ZellijTerminalMultiplexer.java app/src/main/java/io/xpipe/app/terminal/ZellijTerminalMultiplexer.java:111— app/src/main/java/io/xpipe/app/terminal/ZellijTerminalMultiplexer.java changed 7 times in last 90 days and 5 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 8 (its worst body is ZellijTerminalMultiplexer.launchNewSession at line 111), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “Fix zellij config file using wrong dir”; “More quoting fixes”; “Fix zellij timing”; “Fix zellij timing”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-26..2026-10-24, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-26 04:25:12 +00:00' --until='2026-10-24 04:25:12 +00:00' --full-history --no-merges -- app/src/main/java/io/xpipe/app/terminal/ZellijTerminalMultiplexer.java`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: app/src/main/java/io/xpipe/app/browser/file/BrowserTerminalDockTabModel.java app/src/main/java/io/xpipe/app/browser/file/BrowserTerminalDockTabModel.java:72— app/src/main/java/io/xpipe/app/browser/file/BrowserTerminalDockTabModel.java changed 5 times in last 90 days and 5 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 8 (its worst body is BrowserTerminalDockTabModel.init at line 72), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “Fix browser dock threading”; “Fix browser split tab close check”; “Fix some leaks of listeners”; “Fix a few race conditions”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-26..2026-10-24, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-26 04:25:12 +00:00' --until='2026-10-24 04:25:12 +00:00' --full-history --no-merges -- app/src/main/java/io/xpipe/app/browser/file/BrowserTerminalDockTabModel.java`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: app/src/main/java/io/xpipe/app/prefs/AppPrefsStorageHandler.java app/src/main/java/io/xpipe/app/prefs/AppPrefsStorageHandler.java:97— app/src/main/java/io/xpipe/app/prefs/AppPrefsStorageHandler.java changed 7 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 13 (its worst body is AppPrefsStorageHandler.loadObject at line 97), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “Implement various fixes from other kickstartfx projects”; “Various performance fixes”; “Small fixes”; “Fix icon setting not persisting”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-26..2026-10-24, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-26 04:25:12 +00:00' --until='2026-10-24 04:25:12 +00:00' --full-history --no-merges -- app/src/main/java/io/xpipe/app/prefs/AppPrefsStorageHandler.java`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: app/src/main/java/io/xpipe/app/browser/file/BrowserFileListCompEntry.java app/src/main/java/io/xpipe/app/browser/file/BrowserFileListCompEntry.java:149— app/src/main/java/io/xpipe/app/browser/file/BrowserFileListCompEntry.java changed 7 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 14 (its worst body is BrowserFileListCompEntry.acceptsDrop at line 149), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “Various small fixes”; “Fix OOB”; “Various small fixes”; “Menu fixes [release]”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-26..2026-10-24, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-26 04:25:12 +00:00' --until='2026-10-24 04:25:12 +00:00' --full-history --no-merges -- app/src/main/java/io/xpipe/app/browser/file/BrowserFileListCompEntry.java`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: app/src/main/java/io/xpipe/app/browser/file/BrowserFileListNameCell.java app/src/main/java/io/xpipe/app/browser/file/BrowserFileListNameCell.java:139— app/src/main/java/io/xpipe/app/browser/file/BrowserFileListNameCell.java changed 6 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 10 (its worst body is BrowserFileListNameCell.setupRename at line 139), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “Fix browser error with links pointing at self”; “Various performance fixes”; “Various fixes”; “Various fixes”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-26..2026-10-24, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-26 04:25:12 +00:00' --until='2026-10-24 04:25:12 +00:00' --full-history --no-merges -- app/src/main/java/io/xpipe/app/browser/file/BrowserFileListNameCell.java`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: app/src/main/java/io/xpipe/app/beacon/AppBeaconServer.java app/src/main/java/io/xpipe/app/beacon/AppBeaconServer.java:192— app/src/main/java/io/xpipe/app/beacon/AppBeaconServer.java changed 6 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 8 (its worst body is AppBeaconServer.start at line 192), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “Fix mcp freeze on startup”; “Various small fixes”; “Various fixes”; “Fix beacon issues”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-26..2026-10-24, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-26 04:25:12 +00:00' --until='2026-10-24 04:25:12 +00:00' --full-history --no-merges -- app/src/main/java/io/xpipe/app/beacon/AppBeaconServer.java`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: app/src/main/java/io/xpipe/app/terminal/WezTerminalType.java app/src/main/java/io/xpipe/app/terminal/WezTerminalType.java:98— app/src/main/java/io/xpipe/app/terminal/WezTerminalType.java changed 6 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 10 (its worst body is WezTerminalType.getActiveSocket at line 98), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “Fix wezterm socket handling”; “Various fixes”; “Various fixes”; “Small fixes”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-26..2026-10-24, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-26 04:25:12 +00:00' --until='2026-10-24 04:25:12 +00:00' --full-history --no-merges -- app/src/main/java/io/xpipe/app/terminal/WezTerminalType.java`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: app/src/main/java/io/xpipe/app/terminal/TerminalLauncherManager.java app/src/main/java/io/xpipe/app/terminal/TerminalLauncherManager.java:171— app/src/main/java/io/xpipe/app/terminal/TerminalLauncherManager.java changed 6 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 8 (its worst body is TerminalLauncherManager.externalExchange at line 171), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “Various small fixes”; “Various fixes”; “Various fixes”; “Various fixes”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-26..2026-10-24, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-26 04:25:12 +00:00' --until='2026-10-24 04:25:12 +00:00' --full-history --no-merges -- app/src/main/java/io/xpipe/app/terminal/TerminalLauncherManager.java`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: app/src/main/java/io/xpipe/app/beacon/mcp/McpTools.java app/src/main/java/io/xpipe/app/beacon/mcp/McpTools.java:294— app/src/main/java/io/xpipe/app/beacon/mcp/McpTools.java changed 5 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 7 (its worst body is McpTools.getFileInfo at line 294), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “Various fixes”; “Fix mcp run script arg handling”; “Various fixes”; “Various fixes”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-26..2026-10-24, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-26 04:25:12 +00:00' --until='2026-10-24 04:25:12 +00:00' --full-history --no-merges -- app/src/main/java/io/xpipe/app/beacon/mcp/McpTools.java`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: app/src/main/java/io/xpipe/app/terminal/TerminalMultiplexerManager.java app/src/main/java/io/xpipe/app/terminal/TerminalMultiplexerManager.java:107— app/src/main/java/io/xpipe/app/terminal/TerminalMultiplexerManager.java changed 5 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 8 (its worst body is TerminalMultiplexerManager.waitForMultiplexerStartup at line 107), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “Various fixes”; “Fix small multiplexer issues”; “Fix some terminal concurrency issues”; “Fix terminal session tracking for multiple panes”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-26..2026-10-24, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-26 04:25:12 +00:00' --until='2026-10-24 04:25:12 +00:00' --full-history --no-merges -- app/src/main/java/io/xpipe/app/terminal/TerminalMultiplexerManager.java`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: app/src/main/java/io/xpipe/app/core/AppSystemInfo.java app/src/main/java/io/xpipe/app/core/AppSystemInfo.java:179— app/src/main/java/io/xpipe/app/core/AppSystemInfo.java changed 5 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 7 (its worst body is Windows.getUserHome at line 179), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “Implement various fixes from other kickstartfx projects”; “Various small fixes”; “Various fixes”; “Small fixes”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-26..2026-10-24, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-26 04:25:12 +00:00' --until='2026-10-24 04:25:12 +00:00' --full-history --no-merges -- app/src/main/java/io/xpipe/app/core/AppSystemInfo.java`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: app/src/main/java/io/xpipe/app/hub/entry/StoreEntryActionProviderSelectionState.java app/src/main/java/io/xpipe/app/hub/entry/StoreEntryActionProviderSelectionState.java:26— app/src/main/java/io/xpipe/app/hub/entry/StoreEntryActionProviderSelectionState.java changed 5 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 1 (its worst body is StoreEntryActionProviderSelectionState.externalChange at line 26), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “Fix provider update check”; “Fix provider state update check”; “Fix some providers not updating”; “Small fixes [release]”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-26..2026-10-24, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-26 04:25:12 +00:00' --until='2026-10-24 04:25:12 +00:00' --full-history --no-merges -- app/src/main/java/io/xpipe/app/hub/entry/StoreEntryActionProviderSelectionState.java`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: app/src/main/java/io/xpipe/app/comp/base/ListBoxViewComp.java app/src/main/java/io/xpipe/app/comp/base/ListBoxViewComp.java:243— app/src/main/java/io/xpipe/app/comp/base/ListBoxViewComp.java changed 5 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 14 (its worst body is ListBoxViewComp.isVisible at line 243), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “Fix list box listener leaks”; “Various small fixes”; “Various performance fixes”; “Various dialog fixes”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-26..2026-10-24, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-26 04:25:12 +00:00' --until='2026-10-24 04:25:12 +00:00' --full-history --no-merges -- app/src/main/java/io/xpipe/app/comp/base/ListBoxViewComp.java`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: app/src/main/java/io/xpipe/app/core/AppLocalTemp.java app/src/main/java/io/xpipe/app/core/AppLocalTemp.java:15— app/src/main/java/io/xpipe/app/core/AppLocalTemp.java changed 5 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 8 (its worst body is AppLocalTemp.getLocalTempDataDirectory at line 15), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “Various fixes”; “Various fixes”; “Various fixes”; “Various fixes”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-26..2026-10-24, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-26 04:25:12 +00:00' --until='2026-10-24 04:25:12 +00:00' --full-history --no-merges -- app/src/main/java/io/xpipe/app/core/AppLocalTemp.java`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: app/src/main/java/io/xpipe/app/prefs/ExternalApplicationHelper.java app/src/main/java/io/xpipe/app/prefs/ExternalApplicationHelper.java:74— app/src/main/java/io/xpipe/app/prefs/ExternalApplicationHelper.java changed 5 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 9 (its worst body is ExternalApplicationHelper.startAsync at line 74), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “Fix quoting of custom launch commands”; “Various fixes”; “Various tmp dir fixes”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-26..2026-10-24, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-26 04:25:12 +00:00' --until='2026-10-24 04:25:12 +00:00' --full-history --no-merges -- app/src/main/java/io/xpipe/app/prefs/ExternalApplicationHelper.java`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: ext/system/src/main/java/io/xpipe/ext/system/podman/PodmanCommandView.java ext/system/src/main/java/io/xpipe/ext/system/podman/PodmanCommandView.java:176— ext/system/src/main/java/io/xpipe/ext/system/podman/PodmanCommandView.java changed 5 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 5 (its worst body is Container.restart at line 176), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “Fix podman elevation”; “Fix podman quadlet root handling”; “Various fixes”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-26..2026-10-24, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-26 04:25:12 +00:00' --until='2026-10-24 04:25:12 +00:00' --full-history --no-merges -- ext/system/src/main/java/io/xpipe/ext/system/podman/PodmanCommandView.java`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: app/src/main/java/io/xpipe/app/browser/file/BrowserFileOutput.java app/src/main/java/io/xpipe/app/browser/file/BrowserFileOutput.java:45— app/src/main/java/io/xpipe/app/browser/file/BrowserFileOutput.java changed 5 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 12 (its worst body is BrowserFileOutput.requiresSudo at line 45), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “Various tmp dir fixes”; “Various fixes [stage]”; “Various fixes”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-26..2026-10-24, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-26 04:25:12 +00:00' --until='2026-10-24 04:25:12 +00:00' --full-history --no-merges -- app/src/main/java/io/xpipe/app/browser/file/BrowserFileOutput.java`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: app/src/main/java/io/xpipe/app/beacon/BeaconClient.java app/src/main/java/io/xpipe/app/beacon/BeaconClient.java:46— app/src/main/java/io/xpipe/app/beacon/BeaconClient.java changed 5 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 11 (its worst body is BeaconClient.performRequest at line 46), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “Fix beacon issues”; “Various fixes”; “Fix proxy handling for local cli socket”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-26..2026-10-24, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-26 04:25:12 +00:00' --until='2026-10-24 04:25:12 +00:00' --full-history --no-merges -- app/src/main/java/io/xpipe/app/beacon/BeaconClient.java`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: app/src/main/java/io/xpipe/app/core/window/AppDialog.java app/src/main/java/io/xpipe/app/core/window/AppDialog.java:79— app/src/main/java/io/xpipe/app/core/window/AppDialog.java changed 4 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 4 (its worst body is AppDialog.hide at line 79), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “Implement various fixes from other kickstartfx projects”; “Various small fixes”; “Various dialog fixes”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-26..2026-10-24, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-26 04:25:12 +00:00' --until='2026-10-24 04:25:12 +00:00' --full-history --no-merges -- app/src/main/java/io/xpipe/app/core/window/AppDialog.java`: 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: app/src/main/java/io/xpipe/app/storage/DataStorage.java app/src/main/java/io/xpipe/app/storage/DataStorage.java:739— app/src/main/java/io/xpipe/app/storage/DataStorage.java changed 19 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 29 in DataStorage.refreshChildren at line 739. 10 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-26..2026-10-24, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-26 04:25:12 +00:00' --until='2026-10-24 04:25:12 +00:00' --full-history --no-merges -- app/src/main/java/io/xpipe/app/storage/DataStorage.java`: 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: app/src/main/java/io/xpipe/app/hub/entry/StoreEntryWrapper.java app/src/main/java/io/xpipe/app/hub/entry/StoreEntryWrapper.java:153— app/src/main/java/io/xpipe/app/hub/entry/StoreEntryWrapper.java changed 13 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 38 in StoreEntryWrapper.update at line 153. 5 of those changes were fix/bug commits, and the other 8 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-26..2026-10-24, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-26 04:25:12 +00:00' --until='2026-10-24 04:25:12 +00:00' --full-history --no-merges -- app/src/main/java/io/xpipe/app/hub/entry/StoreEntryWrapper.java`: 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: app/src/main/java/io/xpipe/app/browser/file/BrowserFileTransferOperation.java app/src/main/java/io/xpipe/app/browser/file/BrowserFileTransferOperation.java:269— app/src/main/java/io/xpipe/app/browser/file/BrowserFileTransferOperation.java changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 34 in BrowserFileTransferOperation.handleSingleAcrossFileSystems at line 269. 6 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-26..2026-10-24, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-26 04:25:12 +00:00' --until='2026-10-24 04:25:12 +00:00' --full-history --no-merges -- app/src/main/java/io/xpipe/app/browser/file/BrowserFileTransferOperation.java`: 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: app/src/main/java/io/xpipe/app/hub/entry/StoreEntryComp.java app/src/main/java/io/xpipe/app/hub/entry/StoreEntryComp.java:467— app/src/main/java/io/xpipe/app/hub/entry/StoreEntryComp.java changed 8 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 27 in StoreEntryComp.createContextMenu at line 467. 5 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-26..2026-10-24, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-26 04:25:12 +00:00' --until='2026-10-24 04:25:12 +00:00' --full-history --no-merges -- app/src/main/java/io/xpipe/app/hub/entry/StoreEntryComp.java`: 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: app/src/main/java/io/xpipe/app/storage/DataStoreEntry.java app/src/main/java/io/xpipe/app/storage/DataStoreEntry.java:218— app/src/main/java/io/xpipe/app/storage/DataStoreEntry.java changed 10 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 20 in DataStoreEntry.fromDirectory at line 218. 3 of those changes were fix/bug commits, and the other 7 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-26..2026-10-24, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-26 04:25:12 +00:00' --until='2026-10-24 04:25:12 +00:00' --full-history --no-merges -- app/src/main/java/io/xpipe/app/storage/DataStoreEntry.java`: 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: app/src/main/java/io/xpipe/app/core/mode/AppOperationMode.java app/src/main/java/io/xpipe/app/core/mode/AppOperationMode.java:72— app/src/main/java/io/xpipe/app/core/mode/AppOperationMode.java changed 9 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 22 in AppOperationMode.setup at line 72. 5 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-26..2026-10-24, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-26 04:25:12 +00:00' --until='2026-10-24 04:25:12 +00:00' --full-history --no-merges -- app/src/main/java/io/xpipe/app/core/mode/AppOperationMode.java`: 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: app/src/main/java/io/xpipe/app/storage/StandardStorage.java app/src/main/java/io/xpipe/app/storage/StandardStorage.java:80— app/src/main/java/io/xpipe/app/storage/StandardStorage.java changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 37 in StandardStorage.reloadContent at line 80. 1 of those changes was a fix/bug commit, and the other 3 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-26..2026-10-24, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-26 04:25:12 +00:00' --until='2026-10-24 04:25:12 +00:00' --full-history --no-merges -- app/src/main/java/io/xpipe/app/storage/StandardStorage.java`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: REDACTED REDACTED:176— REDACTED changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 24 in SentryErrorHandler.fillScope at line 176. 5 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-26..2026-10-24, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-26 04:25:12 +00:00' --until='2026-10-24 04:25:12 +00:00' --full-history --no-merges -- REDACTED`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: app/src/main/java/io/xpipe/app/hub/creation/StoreChoicePopover.java app/src/main/java/io/xpipe/app/hub/creation/StoreChoicePopover.java:84— app/src/main/java/io/xpipe/app/hub/creation/StoreChoicePopover.java changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 23 in StoreChoicePopover.getPopover at line 84. 5 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-26..2026-10-24, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-26 04:25:12 +00:00' --until='2026-10-24 04:25:12 +00:00' --full-history --no-merges -- app/src/main/java/io/xpipe/app/hub/creation/StoreChoicePopover.java`: 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: app/src/main/java/io/xpipe/app/browser/file/BrowserFileListComp.java app/src/main/java/io/xpipe/app/browser/file/BrowserFileListComp.java:223— app/src/main/java/io/xpipe/app/browser/file/BrowserFileListComp.java changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 18 in BrowserFileListComp.formatOwner at line 223. 4 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-26..2026-10-24, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-26 04:25:12 +00:00' --until='2026-10-24 04:25:12 +00:00' --full-history --no-merges -- app/src/main/java/io/xpipe/app/browser/file/BrowserFileListComp.java`: 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: ext/base/src/main/java/io/xpipe/ext/base/identity/IdentitySelectComp.java ext/base/src/main/java/io/xpipe/ext/base/identity/IdentitySelectComp.java:193— ext/base/src/main/java/io/xpipe/ext/base/identity/IdentitySelectComp.java changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 24 in IdentitySelectComp.createComboBox at line 193. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-26..2026-10-24, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-26 04:25:12 +00:00' --until='2026-10-24 04:25:12 +00:00' --full-history --no-merges -- ext/base/src/main/java/io/xpipe/ext/base/identity/IdentitySelectComp.java`: 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: app/src/main/java/io/xpipe/app/comp/base/ModalOverlayComp.java app/src/main/java/io/xpipe/app/comp/base/ModalOverlayComp.java:54— app/src/main/java/io/xpipe/app/comp/base/ModalOverlayComp.java changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 26 in ModalOverlayComp.createSimple at line 54. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-26..2026-10-24, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-26 04:25:12 +00:00' --until='2026-10-24 04:25:12 +00:00' --full-history --no-merges -- app/src/main/java/io/xpipe/app/comp/base/ModalOverlayComp.java`: 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: app/src/main/java/io/xpipe/app/browser/BrowserSessionTabsComp.java app/src/main/java/io/xpipe/app/browser/BrowserSessionTabsComp.java:416— app/src/main/java/io/xpipe/app/browser/BrowserSessionTabsComp.java changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 25 in BrowserSessionTabsComp.createTab at line 416. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-26..2026-10-24, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-26 04:25:12 +00:00' --until='2026-10-24 04:25:12 +00:00' --full-history --no-merges -- app/src/main/java/io/xpipe/app/browser/BrowserSessionTabsComp.java`: 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: app/src/main/java/io/xpipe/app/hub/category/StoreCategoryComp.java app/src/main/java/io/xpipe/app/hub/category/StoreCategoryComp.java:51— app/src/main/java/io/xpipe/app/hub/category/StoreCategoryComp.java changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in StoreCategoryComp.createSimple at line 51. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-26..2026-10-24, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-26 04:25:12 +00:00' --until='2026-10-24 04:25:12 +00:00' --full-history --no-merges -- app/src/main/java/io/xpipe/app/hub/category/StoreCategoryComp.java`: 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: app/src/main/java/io/xpipe/app/hub/creation/StoreCreationDialog.java app/src/main/java/io/xpipe/app/hub/creation/StoreCreationDialog.java:204— app/src/main/java/io/xpipe/app/hub/creation/StoreCreationDialog.java changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 15 in StoreCreationDialog.createModalOverlay at line 204. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-26..2026-10-24, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-26 04:25:12 +00:00' --until='2026-10-24 04:25:12 +00:00' --full-history --no-merges -- app/src/main/java/io/xpipe/app/hub/creation/StoreCreationDialog.java`: 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: app/src/main/java/io/xpipe/app/prefs/AppPrefs.java app/src/main/java/io/xpipe/app/prefs/AppPrefs.java:853— app/src/main/java/io/xpipe/app/prefs/AppPrefs.java changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 18 in AppPrefs.fixLocalValues at line 853. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-26..2026-10-24, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-26 04:25:12 +00:00' --until='2026-10-24 04:25:12 +00:00' --full-history --no-merges -- app/src/main/java/io/xpipe/app/prefs/AppPrefs.java`: 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: app/src/main/java/io/xpipe/app/hub/creation/StoreCreationModel.java app/src/main/java/io/xpipe/app/hub/creation/StoreCreationModel.java:59— app/src/main/java/io/xpipe/app/hub/creation/StoreCreationModel.java changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 22 in StoreCreationModel.<init> at line 59. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-26..2026-10-24, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-26 04:25:12 +00:00' --until='2026-10-24 04:25:12 +00:00' --full-history --no-merges -- app/src/main/java/io/xpipe/app/hub/creation/StoreCreationModel.java`: 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: app/src/main/java/io/xpipe/app/beacon/BeaconRequestHandler.java app/src/main/java/io/xpipe/app/beacon/BeaconRequestHandler.java:71— app/src/main/java/io/xpipe/app/beacon/BeaconRequestHandler.java changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 28 in BeaconRequestHandler.handleAuthenticatedRequest at line 71. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-26..2026-10-24, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-26 04:25:12 +00:00' --until='2026-10-24 04:25:12 +00:00' --full-history --no-merges -- app/src/main/java/io/xpipe/app/beacon/BeaconRequestHandler.java`: 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: app/src/main/java/io/xpipe/app/issue/ErrorEventFactory.java app/src/main/java/io/xpipe/app/issue/ErrorEventFactory.java:63— app/src/main/java/io/xpipe/app/issue/ErrorEventFactory.java changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 21 in ErrorEventFactory.formatThrowableMessage at line 63. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-26..2026-10-24, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-26 04:25:12 +00:00' --until='2026-10-24 04:25:12 +00:00' --full-history --no-merges -- app/src/main/java/io/xpipe/app/issue/ErrorEventFactory.java`: 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: app/src/main/java/io/xpipe/app/rdp/FreeRdpClient.java app/src/main/java/io/xpipe/app/rdp/FreeRdpClient.java:131— app/src/main/java/io/xpipe/app/rdp/FreeRdpClient.java changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 20 in FreeRdpClient.launch at line 131. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-26..2026-10-24, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-26 04:25:12 +00:00' --until='2026-10-24 04:25:12 +00:00' --full-history --no-merges -- app/src/main/java/io/xpipe/app/rdp/FreeRdpClient.java`: 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: app/src/main/java/io/xpipe/app/comp/base/ContextualFileReferenceChoiceComp.java app/src/main/java/io/xpipe/app/comp/base/ContextualFileReferenceChoiceComp.java:73— app/src/main/java/io/xpipe/app/comp/base/ContextualFileReferenceChoiceComp.java changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 18 in ContextualFileReferenceChoiceComp.createSimple 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-07-26..2026-10-24, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-26 04:25:12 +00:00' --until='2026-10-24 04:25:12 +00:00' --full-history --no-merges -- app/src/main/java/io/xpipe/app/comp/base/ContextualFileReferenceChoiceComp.java`: 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: app/src/main/java/io/xpipe/app/core/AppLayoutModel.java app/src/main/java/io/xpipe/app/core/AppLayoutModel.java:89— app/src/main/java/io/xpipe/app/core/AppLayoutModel.java changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in AppLayoutModel.addListeners at line 89. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-26..2026-10-24, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-26 04:25:12 +00:00' --until='2026-10-24 04:25:12 +00:00' --full-history --no-merges -- app/src/main/java/io/xpipe/app/core/AppLayoutModel.java`: 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: app/src/main/java/io/xpipe/app/comp/base/AppMainWindowContentComp.java app/src/main/java/io/xpipe/app/comp/base/AppMainWindowContentComp.java:42— app/src/main/java/io/xpipe/app/comp/base/AppMainWindowContentComp.java changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in AppMainWindowContentComp.createSimple at line 42. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-26..2026-10-24, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-26 04:25:12 +00:00' --until='2026-10-24 04:25:12 +00:00' --full-history --no-merges -- app/src/main/java/io/xpipe/app/comp/base/AppMainWindowContentComp.java`: 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: app/src/main/java/io/xpipe/app/rdp/MicrosoftRdpClient.java app/src/main/java/io/xpipe/app/rdp/MicrosoftRdpClient.java:166— app/src/main/java/io/xpipe/app/rdp/MicrosoftRdpClient.java changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in MicrosoftRdpClient.launch at line 166. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-26..2026-10-24, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-26 04:25:12 +00:00' --until='2026-10-24 04:25:12 +00:00' --full-history --no-merges -- app/src/main/java/io/xpipe/app/rdp/MicrosoftRdpClient.java`: 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: app/src/main/java/io/xpipe/app/platform/PlatformState.java app/src/main/java/io/xpipe/app/platform/PlatformState.java:105— app/src/main/java/io/xpipe/app/platform/PlatformState.java changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 20 in PlatformState.initPlatform at line 105. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-26..2026-10-24, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-26 04:25:12 +00:00' --until='2026-10-24 04:25:12 +00:00' --full-history --no-merges -- app/src/main/java/io/xpipe/app/platform/PlatformState.java`: 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.
MethodTooLong: OptionsComp.createSimple app/src/main/java/io/xpipe/app/comp/base/OptionsComp.java:49— MethodTooLong — createSimple runs 181 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 81 over it, 1.81× 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: StandardStorage.reloadContent app/src/main/java/io/xpipe/app/storage/StandardStorage.java:80— MethodTooLong — reloadContent runs 166 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 66 over it, 1.66× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: HttpStreamableServerTransportProvider.doPost app/src/main/java/io/xpipe/app/beacon/mcp/HttpStreamableServerTransportProvider.java:218— MethodTooLong — doPost runs 157 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 57 over it, 1.57× 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: CopyPathMenuProvider.getBranchingActions app/src/main/java/io/xpipe/app/browser/menu/impl/CopyPathMenuProvider.java:58— MethodTooLong — getBranchingActions runs 156 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 56 over it, 1.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: StoreCategoryComp.createSimple app/src/main/java/io/xpipe/app/hub/category/StoreCategoryComp.java:51— MethodTooLong — createSimple runs 155 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 55 over it, 1.55× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: AppProperties.<init> app/src/main/java/io/xpipe/app/core/AppProperties.java:79— MethodTooLong — <init> runs 142 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 42 over it, 1.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: StoreEntryComp.createContextMenu app/src/main/java/io/xpipe/app/hub/entry/StoreEntryComp.java:467— MethodTooLong — createContextMenu runs 141 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 41 over it, 1.41× 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: PasswordManagerTestComp.createSimple app/src/main/java/io/xpipe/app/pwman/PasswordManagerTestComp.java:65— MethodTooLong — createSimple runs 139 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 39 over it, 1.39× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: BrowserFileSystemTabComp.createContent app/src/main/java/io/xpipe/app/browser/file/BrowserFileSystemTabComp.java:53— MethodTooLong — createContent runs 128 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 28 over it, 1.28× 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: DataStorage.refreshChildren app/src/main/java/io/xpipe/app/storage/DataStorage.java:739— MethodTooLong — refreshChildren runs 127 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 27 over it, 1.27× 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: IdentitySelectComp.createComboBox ext/base/src/main/java/io/xpipe/ext/base/identity/IdentitySelectComp.java:193— MethodTooLong — createComboBox runs 127 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 27 over it, 1.27× 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: BrowserTransferComp.createSimple app/src/main/java/io/xpipe/app/browser/file/BrowserTransferComp.java:38— MethodTooLong — createSimple runs 126 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 26 over it, 1.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: StoreChoicePopover.getPopover app/src/main/java/io/xpipe/app/hub/creation/StoreChoicePopover.java:84— MethodTooLong — getPopover runs 125 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 25 over it, 1.25× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: NewItemMenuProvider.getBranchingActions app/src/main/java/io/xpipe/app/browser/menu/impl/NewItemMenuProvider.java:49— MethodTooLong — getBranchingActions runs 124 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 24 over it, 1.24× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: TroubleshootCategory.create app/src/main/java/io/xpipe/app/prefs/TroubleshootCategory.java:52— MethodTooLong — create runs 122 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 22 over it, 1.22× 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: BrowserFileTransferOperation.handleSingleAcrossFileSystems app/src/main/java/io/xpipe/app/browser/file/BrowserFileTransferOperation.java:269— MethodTooLong — handleSingleAcrossFileSystems runs 120 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 20 over it, 1.20× 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: AppBaseMode.onSwitchTo app/src/main/java/io/xpipe/app/core/mode/AppBaseMode.java:63— MethodTooLong — onSwitchTo runs 119 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 19 over it, 1.19× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: AppMainWindowContentComp.createSimple app/src/main/java/io/xpipe/app/comp/base/AppMainWindowContentComp.java:42— MethodTooLong — createSimple runs 117 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 17 over it, 1.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: PlatformThread.sync app/src/main/java/io/xpipe/app/platform/PlatformThread.java:72— MethodTooLong — sync runs 116 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 16 over it, 1.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: StoreEntryWrapper.update app/src/main/java/io/xpipe/app/hub/entry/StoreEntryWrapper.java:153— MethodTooLong — update runs 110 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 10 over it, 1.10× 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: DataStoreEntry.fromDirectory app/src/main/java/io/xpipe/app/storage/DataStoreEntry.java:218— MethodTooLong — fromDirectory runs 110 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 10 over it, 1.10× 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: IconsCategory.createOverview app/src/main/java/io/xpipe/app/prefs/IconsCategory.java:63— MethodTooLong — createOverview runs 109 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 9 over it, 1.09× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: McpCategory.create app/src/main/java/io/xpipe/app/prefs/McpCategory.java:47— MethodTooLong — create runs 106 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 6 over it, 1.06× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: MultiIdentityStoreProvider.guiDialog ext/base/src/main/java/io/xpipe/ext/base/identity/MultiIdentityStoreProvider.java:69— MethodTooLong — guiDialog runs 104 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 4 over it, 1.04× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
Duplicated block (7 lines × 2) app/src/main/java/io/xpipe/app/beacon/mcp/McpTools.java:105— app/src/main/java/io/xpipe/app/beacon/mcp/McpTools.java:105-111 | app/src/main/java/io/xpipe/app/beacon/mcp/McpTools.java:125-131 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (7 lines × 2) app/src/main/java/io/xpipe/app/comp/base/FilterComp.java:54— app/src/main/java/io/xpipe/app/comp/base/FilterComp.java:54-60 | app/src/main/java/io/xpipe/app/hub/list/StoreFilterFieldComp.java:83-89 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/io/xpipe/app/comp/base/FilterComp.java:54` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) app/src/main/java/io/xpipe/app/hub/list/StoreListChoiceComp.java:90— app/src/main/java/io/xpipe/app/hub/list/StoreListChoiceComp.java:90-96 | app/src/main/java/io/xpipe/app/hub/list/StoreListChoiceComp.java:105-111 — 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 `app/src/main/java/io/xpipe/app/hub/list/StoreListChoiceComp.java:90` 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 (7 lines × 2) app/src/main/java/io/xpipe/app/prefs/RdpCategory.java:43— app/src/main/java/io/xpipe/app/prefs/RdpCategory.java:43-49 | app/src/main/java/io/xpipe/app/vnc/VncCategory.java:42-48 — 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 `app/src/main/java/io/xpipe/app/prefs/RdpCategory.java:43` 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, `app/src/main/java/io/xpipe/app/prefs/RdpCategory.java:50` calls `setMaxWidth` and `app/src/main/java/io/xpipe/app/vnc/VncCategory.java:49` does not — after which the two agree again for 4 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 (7 lines × 2) app/src/main/java/io/xpipe/app/prefs/TerminalCategory.java:326— app/src/main/java/io/xpipe/app/prefs/TerminalCategory.java:326-332 | app/src/main/java/io/xpipe/app/prefs/TerminalCategory.java:427-433 — 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 `app/src/main/java/io/xpipe/app/prefs/TerminalCategory.java:326` 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 (7 lines × 2) app/src/main/java/io/xpipe/app/process/ShellView.java:196— app/src/main/java/io/xpipe/app/process/ShellView.java:196-202 | app/src/main/java/io/xpipe/app/process/ShellView.java:205-211 — 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (7 lines × 2) app/src/main/java/io/xpipe/app/terminal/TermiusTerminalType.java:92— app/src/main/java/io/xpipe/app/terminal/TermiusTerminalType.java:92-98 | app/src/main/java/io/xpipe/app/terminal/XShellTerminalType.java:88-94 — 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 `app/src/main/java/io/xpipe/app/terminal/TermiusTerminalType.java:92` 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 (7 lines × 2) app/src/main/java/io/xpipe/app/update/AppRelease.java:19— app/src/main/java/io/xpipe/app/update/AppRelease.java:19-25 | app/src/main/java/io/xpipe/app/update/AppRelease.java:41-47 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) app/src/main/java/io/xpipe/app/update/GitHubUpdater.java:54— app/src/main/java/io/xpipe/app/update/GitHubUpdater.java:54-60 | app/src/main/java/io/xpipe/app/update/UpdateHandler.java:209-215 — 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 `app/src/main/java/io/xpipe/app/update/GitHubUpdater.java:54` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) app/src/main/java/io/xpipe/app/webtop/WebtopModeComp.java:26— app/src/main/java/io/xpipe/app/webtop/WebtopModeComp.java:26-32 | app/src/main/java/io/xpipe/app/webtop/WebtopModeComp.java:34-40 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) ext/base/src/main/java/io/xpipe/ext/base/script/ScriptStore.java:65— ext/base/src/main/java/io/xpipe/ext/base/script/ScriptStore.java:65-71 | ext/base/src/main/java/io/xpipe/ext/base/script/ScriptStore.java:101-107 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) ext/system/src/main/java/io/xpipe/ext/system/incus/IncusCommandView.java:217— ext/system/src/main/java/io/xpipe/ext/system/incus/IncusCommandView.java:217-223 | ext/system/src/main/java/io/xpipe/ext/system/lxd/LxdCommandView.java:228-234 — before extracting anything, compare `ext/system/src/main/java/io/xpipe/ext/system/incus/IncusCommandView.java` and `ext/system/src/main/java/io/xpipe/ext/system/lxd/LxdCommandView.java` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 110 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 (7 lines × 2) ext/system/src/main/java/io/xpipe/ext/system/incus/IncusContainerStoreProvider.java:26— ext/system/src/main/java/io/xpipe/ext/system/incus/IncusContainerStoreProvider.java:26-32 | ext/system/src/main/java/io/xpipe/ext/system/lxd/LxdContainerStoreProvider.java:26-32 — 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 `ext/system/src/main/java/io/xpipe/ext/system/incus/IncusContainerStoreProvider.java:26` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (7 lines × 2) ext/system/src/main/java/io/xpipe/ext/system/incus/IncusInstallStore.java:55— ext/system/src/main/java/io/xpipe/ext/system/incus/IncusInstallStore.java:55-61 | ext/system/src/main/java/io/xpipe/ext/system/lxd/LxdCmdStore.java:50-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. Read the line range as the matched WINDOW rather than a finished unit: at `ext/system/src/main/java/io/xpipe/ext/system/incus/IncusInstallStore.java:55` 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 (7 lines × 2) ext/system/src/main/java/io/xpipe/ext/system/incus/IncusInstallStoreProvider.java:26— ext/system/src/main/java/io/xpipe/ext/system/incus/IncusInstallStoreProvider.java:26-32 | ext/system/src/main/java/io/xpipe/ext/system/lxd/LxdCmdStoreProvider.java:26-32 — 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 `ext/system/src/main/java/io/xpipe/ext/system/incus/IncusInstallStoreProvider.java:26` 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 (7 lines × 2) app/src/main/java/io/xpipe/app/browser/action/impl/RunCommandInBackgroundActionProvider.java:69— app/src/main/java/io/xpipe/app/browser/action/impl/RunCommandInBackgroundActionProvider.java:69-75 | app/src/main/java/io/xpipe/app/browser/action/impl/RunCommandInTerminalActionProvider.java:57-63 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (7 lines × 2) app/src/main/java/io/xpipe/app/vnc/TigerVncClient.java:65— app/src/main/java/io/xpipe/app/vnc/TigerVncClient.java:65-71 | app/src/main/java/io/xpipe/app/vnc/TightVncClient.java:27-33 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (7 lines × 2) ext/system/src/main/java/io/xpipe/ext/system/incus/IncusCommandView.java:137— ext/system/src/main/java/io/xpipe/ext/system/incus/IncusCommandView.java:137-143 | ext/system/src/main/java/io/xpipe/ext/system/lxd/LxdCommandView.java:212-218 — before extracting anything, compare `ext/system/src/main/java/io/xpipe/ext/system/incus/IncusCommandView.java` and `ext/system/src/main/java/io/xpipe/ext/system/lxd/LxdCommandView.java` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 110 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (7 lines × 2) ext/system/src/main/java/io/xpipe/ext/system/incus/IncusContainerStore.java:85— ext/system/src/main/java/io/xpipe/ext/system/incus/IncusContainerStore.java:85-91 | ext/system/src/main/java/io/xpipe/ext/system/lxd/LxdContainerStore.java:88-94 — before extracting anything, compare `ext/system/src/main/java/io/xpipe/ext/system/incus/IncusContainerStore.java` and `ext/system/src/main/java/io/xpipe/ext/system/lxd/LxdContainerStore.java` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 70 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 (7 lines × 2) app/src/main/java/io/xpipe/app/browser/menu/impl/BackMenuProvider.java:21— app/src/main/java/io/xpipe/app/browser/menu/impl/BackMenuProvider.java:21-27 | app/src/main/java/io/xpipe/app/browser/menu/impl/ForwardMenuProvider.java:21-27 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (7 lines × 2) app/src/main/java/io/xpipe/app/ext/DataStorageExtensionProvider.java:21— app/src/main/java/io/xpipe/app/ext/DataStorageExtensionProvider.java:21-27 | app/src/main/java/io/xpipe/app/ext/ScanProvider.java:38-44 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (7 lines × 2) ext/system/src/main/java/io/xpipe/ext/system/incus/IncusContainerStore.java:94— ext/system/src/main/java/io/xpipe/ext/system/incus/IncusContainerStore.java:94-100 | ext/system/src/main/java/io/xpipe/ext/system/lxd/LxdContainerStore.java:97-103 — before extracting anything, compare `ext/system/src/main/java/io/xpipe/ext/system/incus/IncusContainerStore.java` and `ext/system/src/main/java/io/xpipe/ext/system/lxd/LxdContainerStore.java` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 70 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (10 lines × 2) app/src/main/java/io/xpipe/app/browser/file/BrowserFileInput.java:75— app/src/main/java/io/xpipe/app/browser/file/BrowserFileInput.java:75-84 | app/src/main/java/io/xpipe/app/browser/file/BrowserFileOutput.java:82-91 — before extracting anything, compare `app/src/main/java/io/xpipe/app/browser/file/BrowserFileInput.java` and `app/src/main/java/io/xpipe/app/browser/file/BrowserFileOutput.java` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 34 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (10 lines × 2) app/src/main/java/io/xpipe/app/browser/menu/impl/NewItemMenuProvider.java:93— app/src/main/java/io/xpipe/app/browser/menu/impl/NewItemMenuProvider.java:93-102 | app/src/main/java/io/xpipe/app/browser/menu/impl/NewItemMenuProvider.java:140-149 — 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 `app/src/main/java/io/xpipe/app/browser/menu/impl/NewItemMenuProvider.java:93` 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, `app/src/main/java/io/xpipe/app/browser/menu/impl/NewItemMenuProvider.java:150` calls `SimpleStringProperty` and `app/src/main/java/io/xpipe/app/browser/menu/impl/NewItemMenuProvider.java:103` 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 (10 lines × 2) app/src/main/java/io/xpipe/app/browser/menu/impl/compress/BaseUnzipUnixMenuProvider.java:45— app/src/main/java/io/xpipe/app/browser/menu/impl/compress/BaseUnzipUnixMenuProvider.java:45-54 | app/src/main/java/io/xpipe/app/browser/menu/impl/compress/BaseUnzipWindowsActionProvider.java:44-53 — before extracting anything, compare `app/src/main/java/io/xpipe/app/browser/menu/impl/compress/BaseUnzipUnixMenuProvider.java` and `app/src/main/java/io/xpipe/app/browser/menu/impl/compress/BaseUnzipWindowsActionProvider.java` as WHOLE FILES: 86% 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 2 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. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (10 lines × 2) app/src/main/java/io/xpipe/app/comp/base/TextAreaComp.java:29— app/src/main/java/io/xpipe/app/comp/base/TextAreaComp.java:29-38 | app/src/main/java/io/xpipe/app/comp/base/TextFieldComp.java:24-33 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (10 lines × 2) app/src/main/java/io/xpipe/app/core/AppI18nData.java:44— app/src/main/java/io/xpipe/app/core/AppI18nData.java:44-53 | app/src/main/java/io/xpipe/app/core/AppI18nData.java:81-90 — 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 `app/src/main/java/io/xpipe/app/core/AppI18nData.java:44` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `app/src/main/java/io/xpipe/app/core/AppI18nData.java:42` calls `AtomicInteger` and `app/src/main/java/io/xpipe/app/core/AppI18nData.java:79` 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.
Duplicated block (10 lines × 2) app/src/main/java/io/xpipe/app/hub/category/StoreCategoryComp.java:312— app/src/main/java/io/xpipe/app/hub/category/StoreCategoryComp.java:312-321 | app/src/main/java/io/xpipe/app/hub/category/StoreCategoryComp.java:332-341 — 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 `app/src/main/java/io/xpipe/app/hub/category/StoreCategoryComp.java:312` 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 (10 lines × 2) app/src/main/java/io/xpipe/app/hub/creation/StoreQuickConnect.java:80— app/src/main/java/io/xpipe/app/hub/creation/StoreQuickConnect.java:80-89 | app/src/main/java/io/xpipe/app/hub/creation/StoreQuickConnect.java:97-106 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2) app/src/main/java/io/xpipe/app/hub/entry/StoreIconChoiceDialog.java:56— app/src/main/java/io/xpipe/app/hub/entry/StoreIconChoiceDialog.java:56-65 | ext/base/src/main/java/io/xpipe/ext/base/script/ScriptCollectionSourceImportDialog.java:68-77 — 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 `app/src/main/java/io/xpipe/app/hub/entry/StoreIconChoiceDialog.java:56` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `ext/base/src/main/java/io/xpipe/ext/base/script/ScriptCollectionSourceImportDialog.java:67` calls `setHgrow` and `app/src/main/java/io/xpipe/app/hub/entry/StoreIconChoiceDialog.java:55` 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 (10 lines × 2) app/src/main/java/io/xpipe/app/hub/list/StoreEntryListComp.java:187— app/src/main/java/io/xpipe/app/hub/list/StoreEntryListComp.java:187-196 | app/src/main/java/io/xpipe/app/hub/list/StoreEntryListComp.java:203-212 — 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 `app/src/main/java/io/xpipe/app/hub/list/StoreEntryListComp.java:187` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (10 lines × 2) app/src/main/java/io/xpipe/app/hub/list/StoreViewState.java:673— app/src/main/java/io/xpipe/app/hub/list/StoreViewState.java:673-682 | app/src/main/java/io/xpipe/app/hub/list/StoreViewState.java:694-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 `app/src/main/java/io/xpipe/app/hub/list/StoreViewState.java:673` 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 (10 lines × 2) app/src/main/java/io/xpipe/app/hub/section/StoreSectionBaseComp.java:161— app/src/main/java/io/xpipe/app/hub/section/StoreSectionBaseComp.java:161-170 | app/src/main/java/io/xpipe/app/hub/section/StoreSectionBaseComp.java:184-193 — 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 `app/src/main/java/io/xpipe/app/hub/section/StoreSectionBaseComp.java:161` 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 (10 lines × 2) app/src/main/java/io/xpipe/app/hub/section/StoreSectionBaseComp.java:172— app/src/main/java/io/xpipe/app/hub/section/StoreSectionBaseComp.java:172-181 | app/src/main/java/io/xpipe/app/hub/section/StoreSectionBaseComp.java:195-204 — 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 `app/src/main/java/io/xpipe/app/hub/section/StoreSectionBaseComp.java:172` 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 (10 lines × 2) app/src/main/java/io/xpipe/app/terminal/KittyTerminalType.java:179— app/src/main/java/io/xpipe/app/terminal/KittyTerminalType.java:179-188 | app/src/main/java/io/xpipe/app/terminal/KittyTerminalType.java:237-246 — 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 `app/src/main/java/io/xpipe/app/terminal/KittyTerminalType.java:179` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `app/src/main/java/io/xpipe/app/terminal/KittyTerminalType.java:178` calls `isInPathOrThrow` and `app/src/main/java/io/xpipe/app/terminal/KittyTerminalType.java:236` does not — after which the two agree again for 4 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 (10 lines × 2) app/src/main/java/io/xpipe/app/util/HumanReadableFormat.java:21— app/src/main/java/io/xpipe/app/util/HumanReadableFormat.java:21-30 | app/src/main/java/io/xpipe/app/util/HumanReadableFormat.java:37-46 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2) ext/base/src/main/java/io/xpipe/ext/base/identity/LocalIdentityStoreProvider.java:43— ext/base/src/main/java/io/xpipe/ext/base/identity/LocalIdentityStoreProvider.java:43-52 | ext/base/src/main/java/io/xpipe/ext/base/identity/SyncedIdentityStoreProvider.java:82-91 — 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 `ext/base/src/main/java/io/xpipe/ext/base/identity/LocalIdentityStoreProvider.java:43` 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, `ext/base/src/main/java/io/xpipe/ext/base/identity/SyncedIdentityStoreProvider.java:93` calls `getInstance`, `isAccessRestricted`, `getType` and `ext/base/src/main/java/io/xpipe/ext/base/identity/LocalIdentityStoreProvider.java:54` 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.
Duplicated block (10 lines × 2) ext/base/src/main/java/io/xpipe/ext/base/identity/LocalIdentityStoreProvider.java:54— ext/base/src/main/java/io/xpipe/ext/base/identity/LocalIdentityStoreProvider.java:54-63 | ext/base/src/main/java/io/xpipe/ext/base/identity/SyncedIdentityStoreProvider.java:95-104 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `ext/base/src/main/java/io/xpipe/ext/base/identity/SyncedIdentityStoreProvider.java:93` calls `getInstance`, `isAccessRestricted`, `getType` and `ext/base/src/main/java/io/xpipe/ext/base/identity/LocalIdentityStoreProvider.java:52` 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.
Duplicated block (10 lines × 2) ext/base/src/main/java/io/xpipe/ext/base/service/ServiceProtocolTypeHelper.java:37— ext/base/src/main/java/io/xpipe/ext/base/service/ServiceProtocolTypeHelper.java:37-46 | ext/base/src/main/java/io/xpipe/ext/base/service/ServiceProtocolTypeHelper.java:53-62 — 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 `ext/base/src/main/java/io/xpipe/ext/base/service/ServiceProtocolTypeHelper.java:37` 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 first that the copies are not typed on the same thing: the declarations holding them bind `p` to `Property<ServiceProtocolType.Http>` in one and `Property<ServiceProtocolType.Https>` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (10 lines × 2) ext/system/src/main/java/io/xpipe/ext/system/incus/IncusContainerStore.java:215— ext/system/src/main/java/io/xpipe/ext/system/incus/IncusContainerStore.java:215-224 | ext/system/src/main/java/io/xpipe/ext/system/lxd/LxdContainerStore.java:218-227 — before extracting anything, compare `ext/system/src/main/java/io/xpipe/ext/system/incus/IncusContainerStore.java` and `ext/system/src/main/java/io/xpipe/ext/system/lxd/LxdContainerStore.java` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 70 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (6 lines × 2) app/src/main/java/io/xpipe/app/browser/file/BrowserFileInput.java:18— app/src/main/java/io/xpipe/app/browser/file/BrowserFileInput.java:18-23 | app/src/main/java/io/xpipe/app/browser/file/BrowserFileOutput.java:24-29 — before extracting anything, compare `app/src/main/java/io/xpipe/app/browser/file/BrowserFileInput.java` and `app/src/main/java/io/xpipe/app/browser/file/BrowserFileOutput.java` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 34 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (6 lines × 2) app/src/main/java/io/xpipe/app/browser/file/BrowserFileInput.java:52— app/src/main/java/io/xpipe/app/browser/file/BrowserFileInput.java:52-57 | app/src/main/java/io/xpipe/app/browser/file/BrowserFileOutput.java:59-64 — before extracting anything, compare `app/src/main/java/io/xpipe/app/browser/file/BrowserFileInput.java` and `app/src/main/java/io/xpipe/app/browser/file/BrowserFileOutput.java` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 34 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (6 lines × 2) app/src/main/java/io/xpipe/app/browser/icon/BrowserIconDirectoryType.java:36— app/src/main/java/io/xpipe/app/browser/icon/BrowserIconDirectoryType.java:36-41 | app/src/main/java/io/xpipe/app/browser/icon/BrowserIconFileType.java:28-33 — 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 `app/src/main/java/io/xpipe/app/browser/icon/BrowserIconDirectoryType.java:36` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `app/src/main/java/io/xpipe/app/browser/icon/BrowserIconFileType.java:34` calls `strip` and `app/src/main/java/io/xpipe/app/browser/icon/BrowserIconDirectoryType.java:42` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (6 lines × 2) app/src/main/java/io/xpipe/app/browser/menu/impl/ChgrpMenuProvider.java:39— app/src/main/java/io/xpipe/app/browser/menu/impl/ChgrpMenuProvider.java:39-44 | app/src/main/java/io/xpipe/app/browser/menu/impl/ChownMenuProvider.java:38-43 — before extracting anything, compare `app/src/main/java/io/xpipe/app/browser/menu/impl/ChgrpMenuProvider.java` and `app/src/main/java/io/xpipe/app/browser/menu/impl/ChownMenuProvider.java` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 32 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/io/xpipe/app/browser/menu/impl/ChgrpMenuProvider.java:39` 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 (6 lines × 2) app/src/main/java/io/xpipe/app/core/AppRestart.java:15— app/src/main/java/io/xpipe/app/core/AppRestart.java:15-20 | app/src/main/java/io/xpipe/app/core/AppRestart.java:39-44 — 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 `app/src/main/java/io/xpipe/app/core/AppRestart.java:15` 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 (6 lines × 2) app/src/main/java/io/xpipe/app/hub/category/StoreCategoryComp.java:513— app/src/main/java/io/xpipe/app/hub/category/StoreCategoryComp.java:513-518 | app/src/main/java/io/xpipe/app/hub/entry/StoreEntryComp.java:564-569 — 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 `app/src/main/java/io/xpipe/app/hub/category/StoreCategoryComp.java:513` 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 (6 lines × 2) app/src/main/java/io/xpipe/app/hub/list/StoreViewState.java:664— app/src/main/java/io/xpipe/app/hub/list/StoreViewState.java:664-669 | app/src/main/java/io/xpipe/app/hub/list/StoreViewState.java:685-690 — 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 `app/src/main/java/io/xpipe/app/hub/list/StoreViewState.java:664` 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, `app/src/main/java/io/xpipe/app/hub/list/StoreViewState.java:684` calls `getParentSectionForWrapper` and `app/src/main/java/io/xpipe/app/hub/list/StoreViewState.java:662` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (6 lines × 2) app/src/main/java/io/xpipe/app/terminal/ScreenTerminalMultiplexer.java:26— app/src/main/java/io/xpipe/app/terminal/ScreenTerminalMultiplexer.java:26-31 | app/src/main/java/io/xpipe/app/terminal/TmuxTerminalMultiplexer.java:31-36 — 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 `app/src/main/java/io/xpipe/app/terminal/ScreenTerminalMultiplexer.java:26` 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 (6 lines × 2) app/src/main/java/io/xpipe/app/util/GroupFile.java:25— app/src/main/java/io/xpipe/app/util/GroupFile.java:25-30 | app/src/main/java/io/xpipe/app/util/PasswdFile.java:25-30 — 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 `app/src/main/java/io/xpipe/app/util/GroupFile.java:25` 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 (6 lines × 2) app/src/main/java/io/xpipe/app/util/NativeMacOsWindowControl.java:25— app/src/main/java/io/xpipe/app/util/NativeMacOsWindowControl.java:25-30 | app/src/main/java/io/xpipe/app/util/NativeWinWindowControl.java:49-54 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `app/src/main/java/io/xpipe/app/util/NativeWinWindowControl.java:46` calls `empty` and `app/src/main/java/io/xpipe/app/util/NativeMacOsWindowControl.java:24` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (6 lines × 2) app/src/main/java/io/xpipe/app/util/StreamCharset.java:95— app/src/main/java/io/xpipe/app/util/StreamCharset.java:95-100 | app/src/main/java/io/xpipe/app/util/StreamCharset.java:105-110 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (6 lines × 2) app/src/main/java/io/xpipe/app/browser/menu/impl/compress/BaseUntarMenuProvider.java:89— app/src/main/java/io/xpipe/app/browser/menu/impl/compress/BaseUntarMenuProvider.java:89-94 | app/src/main/java/io/xpipe/app/browser/menu/impl/compress/UntarActionProvider.java:55-60 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (6 lines × 2) app/src/main/java/io/xpipe/app/browser/menu/impl/compress/BaseUnzipUnixMenuProvider.java:75— app/src/main/java/io/xpipe/app/browser/menu/impl/compress/BaseUnzipUnixMenuProvider.java:75-80 | app/src/main/java/io/xpipe/app/browser/menu/impl/compress/BaseUnzipWindowsActionProvider.java:68-73 — before extracting anything, compare `app/src/main/java/io/xpipe/app/browser/menu/impl/compress/BaseUnzipUnixMenuProvider.java` and `app/src/main/java/io/xpipe/app/browser/menu/impl/compress/BaseUnzipWindowsActionProvider.java` as WHOLE FILES: 86% 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 2 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. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (6 lines × 2) app/src/main/java/io/xpipe/app/browser/icon/BrowserIconFileType.java:20— app/src/main/java/io/xpipe/app/browser/icon/BrowserIconFileType.java:20-25 | app/src/main/java/io/xpipe/app/process/ShellDialects.java:48-53 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (6 lines × 2) app/src/main/java/io/xpipe/app/ext/AuthModuleProvider.java:19— app/src/main/java/io/xpipe/app/ext/AuthModuleProvider.java:19-24 | app/src/main/java/io/xpipe/app/ext/ProcModuleProvider.java:37-42 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (6 lines × 2) ext/system/src/main/java/io/xpipe/ext/system/incus/IncusInstallStoreProvider.java:46— ext/system/src/main/java/io/xpipe/ext/system/incus/IncusInstallStoreProvider.java:46-51 | ext/system/src/main/java/io/xpipe/ext/system/lxd/LxdCmdStoreProvider.java:46-51 — 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (6 lines × 2) app/src/main/java/io/xpipe/app/hub/list/StoreEntryListBatchBarComp.java:114— app/src/main/java/io/xpipe/app/hub/list/StoreEntryListBatchBarComp.java:114-119 | app/src/main/java/io/xpipe/app/hub/list/StoreEntryListBatchBarComp.java:127-132 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `app/src/main/java/io/xpipe/app/hub/list/StoreEntryListBatchBarComp.java:125` calls `hide`, `isEmpty`, `get` and `app/src/main/java/io/xpipe/app/hub/list/StoreEntryListBatchBarComp.java:113` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (6 lines × 2) app/src/main/java/io/xpipe/app/process/ShellView.java:74— app/src/main/java/io/xpipe/app/process/ShellView.java:74-79 | app/src/main/java/io/xpipe/app/process/ShellView.java:109-114 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (9 lines × 2) app/src/main/java/io/xpipe/app/browser/file/BrowserNavBarComp.java:223— app/src/main/java/io/xpipe/app/browser/file/BrowserNavBarComp.java:223-231 | app/src/main/java/io/xpipe/app/browser/file/BrowserNavBarComp.java:255-263 — 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 `app/src/main/java/io/xpipe/app/browser/file/BrowserNavBarComp.java:223` 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 (9 lines × 2) app/src/main/java/io/xpipe/app/browser/menu/impl/NewItemMenuProvider.java:81— app/src/main/java/io/xpipe/app/browser/menu/impl/NewItemMenuProvider.java:81-89 | app/src/main/java/io/xpipe/app/browser/menu/impl/NewItemMenuProvider.java:128-136 — 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 `app/src/main/java/io/xpipe/app/browser/menu/impl/NewItemMenuProvider.java:81` 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 (9 lines × 2) app/src/main/java/io/xpipe/app/comp/base/BusyButtonComp.java:42— app/src/main/java/io/xpipe/app/comp/base/BusyButtonComp.java:42-50 | app/src/main/java/io/xpipe/app/comp/base/TestButtonComp.java:64-72 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/io/xpipe/app/comp/base/BusyButtonComp.java:42` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) app/src/main/java/io/xpipe/app/core/AppLogs.java:174— app/src/main/java/io/xpipe/app/core/AppLogs.java:174-182 | app/src/main/java/io/xpipe/app/core/AppLogs.java:195-203 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/io/xpipe/app/core/AppLogs.java:174` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `app/src/main/java/io/xpipe/app/core/AppLogs.java:205` calls `handleStderrMessage` and `app/src/main/java/io/xpipe/app/core/AppLogs.java:184` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (9 lines × 2) app/src/main/java/io/xpipe/app/core/window/AppMainWindow.java:244— app/src/main/java/io/xpipe/app/core/window/AppMainWindow.java:244-252 | app/src/main/java/io/xpipe/app/core/window/AppMainWindow.java:257-265 — 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 `app/src/main/java/io/xpipe/app/core/window/AppMainWindow.java:257` 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 (9 lines × 2) app/src/main/java/io/xpipe/app/core/window/AppWindowBounds.java:19— app/src/main/java/io/xpipe/app/core/window/AppWindowBounds.java:19-27 | app/src/main/java/io/xpipe/app/core/window/AppWindowBounds.java:35-43 — 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 `app/src/main/java/io/xpipe/app/core/window/AppWindowBounds.java:19` 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 (9 lines × 2) app/src/main/java/io/xpipe/app/prefs/TerminalCategory.java:109— app/src/main/java/io/xpipe/app/prefs/TerminalCategory.java:109-117 | app/src/main/java/io/xpipe/app/prefs/TerminalCategory.java:342-350 — 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 `app/src/main/java/io/xpipe/app/prefs/TerminalCategory.java:109` 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 (9 lines × 2) app/src/main/java/io/xpipe/app/storage/DataStateHandler.java:18— app/src/main/java/io/xpipe/app/storage/DataStateHandler.java:18-26 | app/src/main/java/io/xpipe/app/storage/DataStateHandler.java:55-63 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) app/src/main/java/io/xpipe/app/storage/DataStateHandler.java:32— app/src/main/java/io/xpipe/app/storage/DataStateHandler.java:32-40 | app/src/main/java/io/xpipe/app/storage/DataStateHandler.java:69-77 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) ext/base/src/main/java/io/xpipe/ext/base/script/ScriptTextSource.java:74— ext/base/src/main/java/io/xpipe/ext/base/script/ScriptTextSource.java:74-82 | ext/base/src/main/java/io/xpipe/ext/base/script/ScriptTextSource.java:152-160 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (9 lines × 2) ext/system/src/main/java/io/xpipe/ext/system/incus/IncusCommandView.java:88— ext/system/src/main/java/io/xpipe/ext/system/incus/IncusCommandView.java:88-96 | ext/system/src/main/java/io/xpipe/ext/system/lxd/LxdCommandView.java:164-172 — before extracting anything, compare `ext/system/src/main/java/io/xpipe/ext/system/incus/IncusCommandView.java` and `ext/system/src/main/java/io/xpipe/ext/system/lxd/LxdCommandView.java` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 110 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (9 lines × 2) app/src/main/java/io/xpipe/app/terminal/ITerm2TerminalType.java:30— app/src/main/java/io/xpipe/app/terminal/ITerm2TerminalType.java:30-38 | app/src/main/java/io/xpipe/app/terminal/MacOsTerminalType.java:25-33 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (9 lines × 2) app/src/main/java/io/xpipe/app/terminal/OhMyPoshTerminalPrompt.java:202— app/src/main/java/io/xpipe/app/terminal/OhMyPoshTerminalPrompt.java:202-210 | app/src/main/java/io/xpipe/app/terminal/StarshipTerminalPrompt.java:167-175 — before extracting anything, compare `app/src/main/java/io/xpipe/app/terminal/OhMyPoshTerminalPrompt.java` and `app/src/main/java/io/xpipe/app/terminal/StarshipTerminalPrompt.java` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 62 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (9 lines × 2) ext/system/src/main/java/io/xpipe/ext/system/incus/IncusContainerConsoleActionProvider.java:53— ext/system/src/main/java/io/xpipe/ext/system/incus/IncusContainerConsoleActionProvider.java:53-61 | ext/system/src/main/java/io/xpipe/ext/system/lxd/LxdContainerConsoleActionProvider.java:53-61 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (9 lines × 2) ext/system/src/main/java/io/xpipe/ext/system/incus/IncusContainerEditConfigActionProvider.java:53— ext/system/src/main/java/io/xpipe/ext/system/incus/IncusContainerEditConfigActionProvider.java:53-61 | ext/system/src/main/java/io/xpipe/ext/system/lxd/LxdContainerEditConfigActionProvider.java:53-61 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (9 lines × 2) ext/system/src/main/java/io/xpipe/ext/system/incus/IncusCommandView.java:182— ext/system/src/main/java/io/xpipe/ext/system/incus/IncusCommandView.java:182-190 | ext/system/src/main/java/io/xpipe/ext/system/lxd/LxdCommandView.java:61-69 — before extracting anything, compare `ext/system/src/main/java/io/xpipe/ext/system/incus/IncusCommandView.java` and `ext/system/src/main/java/io/xpipe/ext/system/lxd/LxdCommandView.java` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 110 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. 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.
Swallowed exception (empty catch) app/src/main/java/io/xpipe/app/browser/file/BrowserFileTransferOperation.java:740— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) app/src/main/java/io/xpipe/app/browser/file/BrowserFileTransferOperation.java:747— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) app/src/main/java/io/xpipe/app/core/AppSystemInfo.java:114— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) app/src/main/java/io/xpipe/app/core/AppSystemInfo.java:151— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) app/src/main/java/io/xpipe/app/core/AppSystemInfo.java:170— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) app/src/main/java/io/xpipe/app/core/AppProperties.java:281— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) app/src/main/java/io/xpipe/app/hub/section/StoreSectionConfig.java:97— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) app/src/main/java/io/xpipe/app/platform/OptionsChoiceBuilder.java:84— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) app/src/main/java/io/xpipe/app/platform/OptionsChoiceBuilder.java:97— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) app/src/main/java/io/xpipe/app/platform/OptionsChoiceBuilder.java:110— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) app/src/main/java/io/xpipe/app/prefs/IconsCategory.java:118— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) app/src/main/java/io/xpipe/app/storage/DataStoreEntry.java:427— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) app/src/main/java/io/xpipe/app/util/TlsCertificateFormat.java:73— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) app/src/main/java/io/xpipe/app/util/TlsCertificateFormat.java:81— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) app/src/main/java/io/xpipe/app/util/PasswdFile.java:45— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) app/src/main/java/io/xpipe/app/util/GroupFile.java:45— 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.
TooManyMethods: AppPrefs app/src/main/java/io/xpipe/app/prefs/AppPrefs.java:49— TooManyMethods — 102 methods. The bar is 30 methods; this is 72 over it, 3.40× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: DataStorage app/src/main/java/io/xpipe/app/storage/DataStorage.java:25— TooManyMethods — 100 methods. The bar is 30 methods; this is 70 over it, 3.33× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: WrapperShellControl app/src/main/java/io/xpipe/app/process/WrapperShellControl.java:22— TooManyMethods — 72 methods. The bar is 30 methods; this is 42 over it, 2.40× the bar. Most of these members implement process.ShellControl (58 of 71 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: OptionsBuilder app/src/main/java/io/xpipe/app/platform/OptionsBuilder.java:36— TooManyMethods — 55 methods. The bar is 30 methods; this is 25 over it, 1.83× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: WrapperFileSystem app/src/main/java/io/xpipe/app/fs/WrapperFileSystem.java:16— TooManyMethods — 51 methods. The bar is 30 methods; this is 21 over it, 1.70× the bar. Most of these members implement fs.FileSystem (47 of 51 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: ShellFileSystem app/src/main/java/io/xpipe/app/fs/ShellFileSystem.java:28— TooManyMethods — 49 methods. The bar is 30 methods; this is 19 over it, 1.63× the bar. Most of these members implement fs.FileSystem (47 of 49 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: CommandBuilder app/src/main/java/io/xpipe/app/process/CommandBuilder.java:15— TooManyMethods — 42 methods. The bar is 30 methods; this is 12 over it, 1.40× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: DataStoreEntry app/src/main/java/io/xpipe/app/storage/DataStoreEntry.java:32— TooManyMethods — 42 methods. The bar is 30 methods; this is 12 over it, 1.40× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: ShellView app/src/main/java/io/xpipe/app/process/ShellView.java:17— TooManyMethods — 41 methods. The bar is 30 methods; this is 11 over it, 1.37× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: StoreViewState app/src/main/java/io/xpipe/app/hub/list/StoreViewState.java:46— TooManyMethods — 40 methods. The bar is 30 methods; this is 10 over it, 1.33× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: BrowserFileSystemTabModel app/src/main/java/io/xpipe/app/browser/file/BrowserFileSystemTabModel.java:50— TooManyMethods — 35 methods. The bar is 30 methods; this is 5 over it, 1.17× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: 2498 app/src/main/java/io/xpipe/app/platform/PlatformThread.java:74— TooManyMethods — 33 methods. The bar is 30 methods; this is 3 over it, 1.10× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: FilePath app/src/main/java/io/xpipe/app/util/FilePath.java:9— 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.
Duplicated block (8 lines × 2) app/src/main/java/io/xpipe/app/browser/menu/impl/CopyPathMenuProvider.java:67— app/src/main/java/io/xpipe/app/browser/menu/impl/CopyPathMenuProvider.java:67-74 | app/src/main/java/io/xpipe/app/browser/menu/impl/CopyPathMenuProvider.java:166-173 — 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 `app/src/main/java/io/xpipe/app/browser/menu/impl/CopyPathMenuProvider.java:67` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (8 lines × 2) app/src/main/java/io/xpipe/app/browser/menu/impl/CopyPathMenuProvider.java:147— app/src/main/java/io/xpipe/app/browser/menu/impl/CopyPathMenuProvider.java:147-154 | app/src/main/java/io/xpipe/app/browser/menu/impl/CopyPathMenuProvider.java:254-261 — 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 `app/src/main/java/io/xpipe/app/browser/menu/impl/CopyPathMenuProvider.java:147` 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 (8 lines × 2) app/src/main/java/io/xpipe/app/hub/category/StoreCategoryComp.java:149— app/src/main/java/io/xpipe/app/hub/category/StoreCategoryComp.java:149-156 | app/src/main/java/io/xpipe/app/hub/entry/StoreEntryComp.java:291-298 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (8 lines × 2) app/src/main/java/io/xpipe/app/hub/creation/StoreChoiceComp.java:191— app/src/main/java/io/xpipe/app/hub/creation/StoreChoiceComp.java:191-198 | ext/base/src/main/java/io/xpipe/ext/base/identity/IdentitySelectComp.java:366-373 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (8 lines × 2) app/src/main/java/io/xpipe/app/hub/entry/DenseStoreEntryComp.java:67— app/src/main/java/io/xpipe/app/hub/entry/DenseStoreEntryComp.java:67-74 | app/src/main/java/io/xpipe/app/hub/entry/StandardStoreEntryComp.java:65-72 — before extracting anything, compare `app/src/main/java/io/xpipe/app/hub/entry/DenseStoreEntryComp.java` and `app/src/main/java/io/xpipe/app/hub/entry/StandardStoreEntryComp.java` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 48 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (8 lines × 2) app/src/main/java/io/xpipe/app/hub/entry/DenseStoreEntryComp.java:114— app/src/main/java/io/xpipe/app/hub/entry/DenseStoreEntryComp.java:114-121 | app/src/main/java/io/xpipe/app/hub/entry/StandardStoreEntryComp.java:121-128 — before extracting anything, compare `app/src/main/java/io/xpipe/app/hub/entry/DenseStoreEntryComp.java` and `app/src/main/java/io/xpipe/app/hub/entry/StandardStoreEntryComp.java` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 48 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (8 lines × 2) app/src/main/java/io/xpipe/app/terminal/KittyTerminalType.java:191— app/src/main/java/io/xpipe/app/terminal/KittyTerminalType.java:191-198 | app/src/main/java/io/xpipe/app/terminal/KittyTerminalType.java:249-256 — 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 `app/src/main/java/io/xpipe/app/terminal/KittyTerminalType.java:191` 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 (8 lines × 2) app/src/main/java/io/xpipe/app/util/DataStoreFormatter.java:61— app/src/main/java/io/xpipe/app/util/DataStoreFormatter.java:61-68 | app/src/main/java/io/xpipe/app/util/DataStoreFormatter.java:71-78 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/io/xpipe/app/util/DataStoreFormatter.java:61` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (8 lines × 2) app/src/main/java/io/xpipe/app/webtop/WebtopAppListManager.java:113— app/src/main/java/io/xpipe/app/webtop/WebtopAppListManager.java:113-120 | app/src/main/java/io/xpipe/app/webtop/WebtopAppListManager.java:169-176 — 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 `app/src/main/java/io/xpipe/app/webtop/WebtopAppListManager.java:113` 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 (8 lines × 2) ext/base/src/main/java/io/xpipe/ext/base/identity/IdentityConvert.java:36— ext/base/src/main/java/io/xpipe/ext/base/identity/IdentityConvert.java:36-43 | ext/base/src/main/java/io/xpipe/ext/base/store/SyncConfigHubLeafProvider.java:73-80 — 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 `ext/base/src/main/java/io/xpipe/ext/base/identity/IdentityConvert.java:36` 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 (8 lines × 2) ext/base/src/main/java/io/xpipe/ext/base/identity/LocalIdentityStore.java:64— ext/base/src/main/java/io/xpipe/ext/base/identity/LocalIdentityStore.java:64-71 | ext/base/src/main/java/io/xpipe/ext/base/identity/SyncedIdentityStore.java:64-71 — 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (8 lines × 2) app/src/main/java/io/xpipe/app/browser/action/impl/OpenFileNativeDetailsActionProvider.java:27— app/src/main/java/io/xpipe/app/browser/action/impl/OpenFileNativeDetailsActionProvider.java:27-34 | app/src/main/java/io/xpipe/app/browser/action/impl/OpenFileNativeManagerActionProvider.java:23-30 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (8 lines × 2) app/src/main/java/io/xpipe/app/terminal/TerminalDockView.java:312— app/src/main/java/io/xpipe/app/terminal/TerminalDockView.java:312-319 | app/src/main/java/io/xpipe/app/util/RemoteDesktopDockView.java:174-181 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (11 lines × 2) app/src/main/java/io/xpipe/app/beacon/mcp/HttpStreamableServerTransportProvider.java:342— app/src/main/java/io/xpipe/app/beacon/mcp/HttpStreamableServerTransportProvider.java:342-352 | app/src/main/java/io/xpipe/app/beacon/mcp/HttpStreamableServerTransportProvider.java:354-364 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2) app/src/main/java/io/xpipe/app/browser/menu/impl/CopyPathMenuProvider.java:125— app/src/main/java/io/xpipe/app/browser/menu/impl/CopyPathMenuProvider.java:125-135 | app/src/main/java/io/xpipe/app/browser/menu/impl/CopyPathMenuProvider.java:231-241 — 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 `app/src/main/java/io/xpipe/app/browser/menu/impl/CopyPathMenuProvider.java:125` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (11 lines × 2) app/src/main/java/io/xpipe/app/core/AppGreetingsDialog.java:25— app/src/main/java/io/xpipe/app/core/AppGreetingsDialog.java:25-35 | app/src/main/java/io/xpipe/app/core/AppGreetingsDialog.java:40-50 — 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 `app/src/main/java/io/xpipe/app/core/AppGreetingsDialog.java:25` 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 (11 lines × 2) app/src/main/java/io/xpipe/app/hub/category/StoreCategoryWrapper.java:249— app/src/main/java/io/xpipe/app/hub/category/StoreCategoryWrapper.java:249-259 | app/src/main/java/io/xpipe/app/hub/category/StoreCategoryWrapper.java:267-277 — 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 `app/src/main/java/io/xpipe/app/hub/category/StoreCategoryWrapper.java:249` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (11 lines × 2) app/src/main/java/io/xpipe/app/hub/entry/DenseStoreEntryComp.java:102— app/src/main/java/io/xpipe/app/hub/entry/DenseStoreEntryComp.java:102-112 | app/src/main/java/io/xpipe/app/hub/entry/StandardStoreEntryComp.java:130-140 — before extracting anything, compare `app/src/main/java/io/xpipe/app/hub/entry/DenseStoreEntryComp.java` and `app/src/main/java/io/xpipe/app/hub/entry/StandardStoreEntryComp.java` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 48 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (11 lines × 2) app/src/main/java/io/xpipe/app/prefs/IconsCategory.java:141— app/src/main/java/io/xpipe/app/prefs/IconsCategory.java:141-151 | app/src/main/java/io/xpipe/app/prefs/IconsCategory.java:186-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 `app/src/main/java/io/xpipe/app/prefs/IconsCategory.java:141` 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 (11 lines × 2) app/src/main/java/io/xpipe/app/terminal/OhMyPoshTerminalPrompt.java:165— app/src/main/java/io/xpipe/app/terminal/OhMyPoshTerminalPrompt.java:165-175 | app/src/main/java/io/xpipe/app/terminal/StarshipTerminalPrompt.java:130-140 — before extracting anything, compare `app/src/main/java/io/xpipe/app/terminal/OhMyPoshTerminalPrompt.java` and `app/src/main/java/io/xpipe/app/terminal/StarshipTerminalPrompt.java` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 62 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (11 lines × 2) app/src/main/java/io/xpipe/app/terminal/TmuxTerminalMultiplexer.java:73— app/src/main/java/io/xpipe/app/terminal/TmuxTerminalMultiplexer.java:73-83 | app/src/main/java/io/xpipe/app/terminal/TmuxTerminalMultiplexer.java:102-112 — 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 `app/src/main/java/io/xpipe/app/terminal/TmuxTerminalMultiplexer.java:73` 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, `app/src/main/java/io/xpipe/app/terminal/TmuxTerminalMultiplexer.java:114` calls `add` and `app/src/main/java/io/xpipe/app/terminal/TmuxTerminalMultiplexer.java:85` 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 (11 lines × 2) app/src/main/java/io/xpipe/app/update/GitHubUpdater.java:70— app/src/main/java/io/xpipe/app/update/GitHubUpdater.java:70-80 | app/src/main/java/io/xpipe/app/update/GitHubUpdater.java:93-103 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/io/xpipe/app/update/GitHubUpdater.java:70` 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 (11 lines × 2) app/src/main/java/io/xpipe/app/util/ContextMenuWrapper.java:110— app/src/main/java/io/xpipe/app/util/ContextMenuWrapper.java:110-120 | app/src/main/java/io/xpipe/app/util/ContextMenuWrapper.java:132-142 — 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 `app/src/main/java/io/xpipe/app/util/ContextMenuWrapper.java:110` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (11 lines × 2) app/src/main/java/io/xpipe/app/util/FileBridge.java:161— app/src/main/java/io/xpipe/app/util/FileBridge.java:161-171 | app/src/main/java/io/xpipe/app/util/FileBridge.java:181-191 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/io/xpipe/app/util/FileBridge.java:161` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (11 lines × 2) app/src/main/java/io/xpipe/app/util/GroupFile.java:33— app/src/main/java/io/xpipe/app/util/GroupFile.java:33-43 | app/src/main/java/io/xpipe/app/util/PasswdFile.java:33-43 — 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 `app/src/main/java/io/xpipe/app/util/GroupFile.java:33` 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 (5 lines × 2) app/src/main/java/io/xpipe/app/beacon/api/FsReadExchange.java:34— app/src/main/java/io/xpipe/app/beacon/api/FsReadExchange.java:34-38 | app/src/main/java/io/xpipe/app/beacon/api/FsWriteExchange.java:30-34 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (5 lines × 2) app/src/main/java/io/xpipe/app/hub/category/StoreCategoryComp.java:498— app/src/main/java/io/xpipe/app/hub/category/StoreCategoryComp.java:498-502 | app/src/main/java/io/xpipe/app/hub/entry/StoreEntryComp.java:488-492 — 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 `app/src/main/java/io/xpipe/app/hub/category/StoreCategoryComp.java: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.
Duplicated block (5 lines × 2) app/src/main/java/io/xpipe/app/hub/creation/StoreCreationMenu.java:95— app/src/main/java/io/xpipe/app/hub/creation/StoreCreationMenu.java:95-99 | app/src/main/java/io/xpipe/app/hub/list/StoreEntryListComp.java:179-183 — 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 `app/src/main/java/io/xpipe/app/hub/creation/StoreCreationMenu.java:95` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 2) REDACTED:271— REDACTED:271-275 | REDACTED:288-292 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (5 lines × 2) app/src/main/java/io/xpipe/app/rdp/FreeRdpClient.java:83— app/src/main/java/io/xpipe/app/rdp/FreeRdpClient.java:83-87 | app/src/main/java/io/xpipe/app/rdp/FreeRdpClient.java:107-112 — 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 `app/src/main/java/io/xpipe/app/rdp/FreeRdpClient.java:83` 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 (5 lines × 2) app/src/main/java/io/xpipe/app/terminal/ScreenTerminalMultiplexer.java:61— app/src/main/java/io/xpipe/app/terminal/ScreenTerminalMultiplexer.java:61-66 | app/src/main/java/io/xpipe/app/terminal/ScreenTerminalMultiplexer.java:73-77 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/io/xpipe/app/terminal/ScreenTerminalMultiplexer.java:61` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (5 lines × 2) app/src/main/java/io/xpipe/app/update/CommandUpdater.java:55— app/src/main/java/io/xpipe/app/update/CommandUpdater.java:55-60 | app/src/main/java/io/xpipe/app/update/WingetUpdater.java:59-63 — before extracting anything, compare `app/src/main/java/io/xpipe/app/update/CommandUpdater.java` and `app/src/main/java/io/xpipe/app/update/WingetUpdater.java` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 38 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/io/xpipe/app/update/CommandUpdater.java:55` 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 (5 lines × 2) ext/base/src/main/java/io/xpipe/ext/base/identity/IdentitySelectComp.java:79— ext/base/src/main/java/io/xpipe/ext/base/identity/IdentitySelectComp.java:79-83 | ext/base/src/main/java/io/xpipe/ext/base/identity/IdentitySelectComp.java:96-100 — 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 `ext/base/src/main/java/io/xpipe/ext/base/identity/IdentitySelectComp.java:79` 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 (5 lines × 2) ext/system/src/main/java/io/xpipe/ext/system/incus/IncusContainerStoreProvider.java:61— ext/system/src/main/java/io/xpipe/ext/system/incus/IncusContainerStoreProvider.java:61-65 | ext/system/src/main/java/io/xpipe/ext/system/lxd/LxdContainerStoreProvider.java:61-65 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (5 lines × 2) app/src/main/java/io/xpipe/app/browser/action/impl/OpenFileWithActionProvider.java:24— app/src/main/java/io/xpipe/app/browser/action/impl/OpenFileWithActionProvider.java:24-28 | app/src/main/java/io/xpipe/app/browser/menu/impl/OpenFileWithMenuProvider.java:26-30 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (5 lines × 2) app/src/main/java/io/xpipe/app/secret/DataStorageAccessHandler.java:15— app/src/main/java/io/xpipe/app/secret/DataStorageAccessHandler.java:15-19 | app/src/main/java/io/xpipe/app/storage/DataStoreAccessScope.java:18-22 — 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 `app/src/main/java/io/xpipe/app/secret/DataStorageAccessHandler.java:15` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (5 lines × 2) app/src/main/java/io/xpipe/app/browser/file/BrowserFileSystemHelper.java:25— app/src/main/java/io/xpipe/app/browser/file/BrowserFileSystemHelper.java:25-29 | app/src/main/java/io/xpipe/app/prefs/ExternalApplicationHelper.java:78-82 — 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.
ClassTooLong: DataStorage app/src/main/java/io/xpipe/app/storage/DataStorage.java:25— ClassTooLong — 1029 significant lines (blank, comment-only and punctuation-only lines excluded), 100 methods. The bar is 400 significant lines; this is 629 over it, 2.57× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: AppPrefs app/src/main/java/io/xpipe/app/prefs/AppPrefs.java:49— ClassTooLong — 819 significant lines (blank, comment-only and punctuation-only lines excluded), 102 methods. The bar is 400 significant lines; this is 419 over it, 2.05× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: DataStoreEntry app/src/main/java/io/xpipe/app/storage/DataStoreEntry.java:32— ClassTooLong — 609 significant lines (blank, comment-only and punctuation-only lines excluded), 42 methods. The bar is 400 significant lines; this is 209 over it, 1.52× 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: ExternalEditorType app/src/main/java/io/xpipe/app/prefs/ExternalEditorType.java:25— ClassTooLong — 557 significant lines (blank, comment-only and punctuation-only lines excluded), 4 methods. The bar is 400 significant lines; this is 157 over it, 1.39× 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: BrowserFileListComp app/src/main/java/io/xpipe/app/browser/file/BrowserFileListComp.java:42— ClassTooLong — 492 significant lines (blank, comment-only and punctuation-only lines excluded), 14 methods. The bar is 400 significant lines; this is 92 over it, 1.23× 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: StoreViewState app/src/main/java/io/xpipe/app/hub/list/StoreViewState.java:46— ClassTooLong — 476 significant lines (blank, comment-only and punctuation-only lines excluded), 40 methods. The bar is 400 significant lines; this is 76 over it, 1.19× 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: BrowserFileTransferOperation app/src/main/java/io/xpipe/app/browser/file/BrowserFileTransferOperation.java:32— ClassTooLong — 468 significant lines (blank, comment-only and punctuation-only lines excluded), 16 methods. The bar is 400 significant lines; this is 68 over it, 1.17× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: StoreEntryComp app/src/main/java/io/xpipe/app/hub/entry/StoreEntryComp.java:53— ClassTooLong — 460 significant lines (blank, comment-only and punctuation-only lines excluded), 26 methods. The bar is 400 significant lines; this is 60 over it, 1.15× 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: AppTheme app/src/main/java/io/xpipe/app/core/AppTheme.java:38— ClassTooLong — 454 significant lines (blank, comment-only and punctuation-only lines excluded), 9 methods. The bar is 400 significant lines; this is 54 over it, 1.14× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: ExternalTerminalType app/src/main/java/io/xpipe/app/terminal/ExternalTerminalType.java:16— ClassTooLong — 446 significant lines (blank, comment-only and punctuation-only lines excluded), 14 methods. The bar is 400 significant lines; this is 46 over it, 1.12× 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: HttpStreamableServerTransportProvider app/src/main/java/io/xpipe/app/beacon/mcp/HttpStreamableServerTransportProvider.java:28— ClassTooLong — 407 significant lines (blank, comment-only and punctuation-only lines excluded), 12 methods. The bar is 400 significant lines; this is 7 over it, 1.02× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
Low cohesion: StoreCategoryWrapper (LCOM4 6) app/src/main/java/io/xpipe/app/hub/category/StoreCategoryWrapper.java:33— StoreCategoryWrapper'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: ContextMenuWrapper (LCOM4 4) app/src/main/java/io/xpipe/app/util/ContextMenuWrapper.java:24— ContextMenuWrapper's methods fall into 4 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 4 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: Session (LCOM4 4) app/src/main/java/io/xpipe/app/store/Session.java:9— Session's methods fall into 4 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 4 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: DataStorage (LCOM4 4) app/src/main/java/io/xpipe/app/storage/DataStorage.java:25— DataStorage's methods fall into 4 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 4 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: ErrorEvent (LCOM4 4) app/src/main/java/io/xpipe/app/issue/ErrorEvent.java:15— ErrorEvent's methods fall into 4 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 4 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: StoreViewState (LCOM4 4) app/src/main/java/io/xpipe/app/hub/list/StoreViewState.java:46— StoreViewState's methods fall into 4 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 4 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: AppProperties (LCOM4 4) app/src/main/java/io/xpipe/app/core/AppProperties.java:25— AppProperties's methods fall into 4 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 4 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: AppLogs (LCOM4 4) app/src/main/java/io/xpipe/app/core/AppLogs.java:33— AppLogs's methods fall into 4 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 4 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: AppLayoutModel (LCOM4 4) app/src/main/java/io/xpipe/app/core/AppLayoutModel.java:51— AppLayoutModel's methods fall into 4 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 4 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.
FileTooLong: storage/DataStorage.java app/src/main/java/io/xpipe/app/storage/DataStorage.java— FileTooLong — 1048 significant lines (blank, comment-only and punctuation-only lines excluded), about 98% of them inside a single declaration: DataStorage (25-1666). The bar is 500 significant lines; this is 548 over it, 2.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: prefs/AppPrefs.java app/src/main/java/io/xpipe/app/prefs/AppPrefs.java— FileTooLong — 862 significant lines (blank, comment-only and punctuation-only lines excluded), about 95% of them inside a single declaration: AppPrefs (49-1181). The bar is 500 significant lines; this is 362 over it, 1.72× 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: storage/DataStoreEntry.java app/src/main/java/io/xpipe/app/storage/DataStoreEntry.java— FileTooLong — 636 significant lines (blank, comment-only and punctuation-only lines excluded), about 96% of them inside a single declaration: DataStoreEntry (32-879). The bar is 500 significant lines; this is 136 over it, 1.27× 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: prefs/ExternalEditorType.java app/src/main/java/io/xpipe/app/prefs/ExternalEditorType.java— FileTooLong — 576 significant lines (blank, comment-only and punctuation-only lines excluded), about 97% of them inside a single declaration: ExternalEditorType (25-824). The bar is 500 significant lines; this is 76 over it, 1.15× 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: file/BrowserFileListComp.java app/src/main/java/io/xpipe/app/browser/file/BrowserFileListComp.java— FileTooLong — 527 significant lines (blank, comment-only and punctuation-only lines excluded), about 93% of them inside a single declaration: BrowserFileListComp (42-759). The bar is 500 significant lines; this is 27 over it, 1.05× 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: list/StoreViewState.java app/src/main/java/io/xpipe/app/hub/list/StoreViewState.java— FileTooLong — 516 significant lines (blank, comment-only and punctuation-only lines excluded), about 92% of them inside a single declaration: StoreViewState (46-810). The bar is 500 significant lines; this is 16 over it, 1.03× 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: entry/StoreEntryComp.java app/src/main/java/io/xpipe/app/hub/entry/StoreEntryComp.java— FileTooLong — 507 significant lines (blank, comment-only and punctuation-only lines excluded), about 91% of them inside a single declaration: StoreEntryComp (53-703). The bar is 500 significant lines; this is 7 over it, 1.01× 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.
Duplicated block (13 lines × 2) app/src/main/java/io/xpipe/app/browser/menu/MultiExecuteMenuProvider.java:75— app/src/main/java/io/xpipe/app/browser/menu/MultiExecuteMenuProvider.java:75-87 | app/src/main/java/io/xpipe/app/browser/menu/MultiExecuteMenuProvider.java:102-114 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/io/xpipe/app/browser/menu/MultiExecuteMenuProvider.java:75` 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. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (13 lines × 2) app/src/main/java/io/xpipe/app/browser/menu/impl/GradleRunMenuProvider.java:70— app/src/main/java/io/xpipe/app/browser/menu/impl/GradleRunMenuProvider.java:70-82 | app/src/main/java/io/xpipe/app/browser/menu/impl/compress/CompressMenuProvider.java:114-126 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/io/xpipe/app/browser/menu/impl/GradleRunMenuProvider.java:70` 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 (13 lines × 2) app/src/main/java/io/xpipe/app/hub/category/StoreCategoryDragComp.java:42— app/src/main/java/io/xpipe/app/hub/category/StoreCategoryDragComp.java:42-54 | app/src/main/java/io/xpipe/app/hub/list/StoreSectionDragComp.java:76-88 — 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (13 lines × 2) app/src/main/java/io/xpipe/app/platform/Listeners.java:118— app/src/main/java/io/xpipe/app/platform/Listeners.java:118-130 | app/src/main/java/io/xpipe/app/platform/Listeners.java:138-150 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (13 lines × 2) app/src/main/java/io/xpipe/app/storage/DataStoreCategory.java:275— app/src/main/java/io/xpipe/app/storage/DataStoreCategory.java:275-287 | app/src/main/java/io/xpipe/app/storage/DataStoreEntry.java:564-577 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (13 lines × 2) app/src/main/java/io/xpipe/app/terminal/OhMyPoshTerminalPrompt.java:221— app/src/main/java/io/xpipe/app/terminal/OhMyPoshTerminalPrompt.java:221-233 | app/src/main/java/io/xpipe/app/terminal/StarshipTerminalPrompt.java:86-98 — before extracting anything, compare `app/src/main/java/io/xpipe/app/terminal/OhMyPoshTerminalPrompt.java` and `app/src/main/java/io/xpipe/app/terminal/StarshipTerminalPrompt.java` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 62 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/io/xpipe/app/terminal/OhMyPoshTerminalPrompt.java:221` 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, `app/src/main/java/io/xpipe/app/terminal/StarshipTerminalPrompt.java:84` calls `add`, `getSetEnvironmentVariableCommand`, `toString` and `app/src/main/java/io/xpipe/app/terminal/OhMyPoshTerminalPrompt.java:220` 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 × 2) ext/system/src/main/java/io/xpipe/ext/system/incus/IncusContainerStore.java:104— ext/system/src/main/java/io/xpipe/ext/system/incus/IncusContainerStore.java:104-116 | ext/system/src/main/java/io/xpipe/ext/system/lxd/LxdContainerStore.java:107-119 — before extracting anything, compare `ext/system/src/main/java/io/xpipe/ext/system/incus/IncusContainerStore.java` and `ext/system/src/main/java/io/xpipe/ext/system/lxd/LxdContainerStore.java` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 70 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 `ext/system/src/main/java/io/xpipe/ext/system/incus/IncusContainerStore.java:104` 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.
Swallowed exception (caught, then discarded) app/src/main/java/io/xpipe/app/beacon/BeaconServer.java:31— `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) app/src/main/java/io/xpipe/app/browser/file/BrowserClipboard.java:106— `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) app/src/main/java/io/xpipe/app/core/AppSystemInfo.java:202— `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) app/src/main/java/io/xpipe/app/platform/OptionsChoiceBuilder.java:117— `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) app/src/main/java/io/xpipe/app/storage/DataStorage.java:316— `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) app/src/main/java/io/xpipe/app/store/DataStore.java:18— `catch (Throwable)` 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.
TodoComment app/src/main/java/io/xpipe/app/core/AppDesktopIntegration.java:101— // TODO: These don't show up any more — 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 app/src/main/java/io/xpipe/app/storage/DataStateHandler.java:83— // TODO: Do we need to set the cache? — 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 app/src/main/java/io/xpipe/app/terminal/ZellijTerminalMultiplexer.java:25— // TODO: It seems like zellij is still broken on Windows — 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 app/src/main/java/io/xpipe/app/terminal/TerminalMultiplexerManager.java:63— // TODO: It seems like zellij is still broken on Windows — 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 app/src/main/java/io/xpipe/app/webtop/WebtopPreconfiguredDialog.java:18— // TODO: This is disabled for now — 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.
Duplicated block (14 lines × 2) app/src/main/java/io/xpipe/app/action/ActionShortcutComp.java:61— app/src/main/java/io/xpipe/app/action/ActionShortcutComp.java:61-74 | app/src/main/java/io/xpipe/app/action/ActionShortcutComp.java:92-105 — 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 `app/src/main/java/io/xpipe/app/action/ActionShortcutComp.java:61` 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 (14 lines × 2) app/src/main/java/io/xpipe/app/hub/action/BatchHubProvider.java:59— app/src/main/java/io/xpipe/app/hub/action/BatchHubProvider.java:59-72 | app/src/main/java/io/xpipe/app/hub/action/HubLeafProvider.java:21-34 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (14 lines × 2) app/src/main/java/io/xpipe/app/hub/category/StoreCategoryIconComp.java:38— app/src/main/java/io/xpipe/app/hub/category/StoreCategoryIconComp.java:38-51 | app/src/main/java/io/xpipe/app/hub/entry/StoreEntryIconComp.java:46-59 — 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 `app/src/main/java/io/xpipe/app/hub/category/StoreCategoryIconComp.java:38` 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 (14 lines × 2) app/src/main/java/io/xpipe/app/storage/DataStorage.java:1246— app/src/main/java/io/xpipe/app/storage/DataStorage.java:1246-1259 | app/src/main/java/io/xpipe/app/storage/DataStorage.java:1270-1283 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (14 lines × 2) app/src/main/java/io/xpipe/app/util/ScanDialog.java:28— app/src/main/java/io/xpipe/app/util/ScanDialog.java:28-41 | app/src/main/java/io/xpipe/app/util/ScanDialog.java:56-69 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (12 lines × 2) app/src/main/java/io/xpipe/app/browser/file/BrowserFileInput.java:60— app/src/main/java/io/xpipe/app/browser/file/BrowserFileInput.java:60-71 | app/src/main/java/io/xpipe/app/browser/file/BrowserFileOutput.java:67-78 — before extracting anything, compare `app/src/main/java/io/xpipe/app/browser/file/BrowserFileInput.java` and `app/src/main/java/io/xpipe/app/browser/file/BrowserFileOutput.java` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 34 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/io/xpipe/app/browser/file/BrowserFileInput.java:60` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (12 lines × 2) app/src/main/java/io/xpipe/app/browser/file/BrowserFileOpener.java:29— app/src/main/java/io/xpipe/app/browser/file/BrowserFileOpener.java:29-40 | app/src/main/java/io/xpipe/app/browser/file/BrowserFileOpener.java:48-59 — 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 `app/src/main/java/io/xpipe/app/browser/file/BrowserFileOpener.java:29` 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 (12 lines × 2) app/src/main/java/io/xpipe/app/storage/DataStorage.java:1043— app/src/main/java/io/xpipe/app/storage/DataStorage.java:1043-1054 | app/src/main/java/io/xpipe/app/storage/DataStorage.java:1087-1098 — 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 `app/src/main/java/io/xpipe/app/storage/DataStorage.java:1043` 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 (12 lines × 2) app/src/main/java/io/xpipe/app/terminal/OhMyPoshTerminalPrompt.java:179— app/src/main/java/io/xpipe/app/terminal/OhMyPoshTerminalPrompt.java:179-190 | app/src/main/java/io/xpipe/app/terminal/StarshipTerminalPrompt.java:144-155 — before extracting anything, compare `app/src/main/java/io/xpipe/app/terminal/OhMyPoshTerminalPrompt.java` and `app/src/main/java/io/xpipe/app/terminal/StarshipTerminalPrompt.java` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 62 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/io/xpipe/app/terminal/OhMyPoshTerminalPrompt.java:179` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) app/src/main/java/io/xpipe/app/util/DesktopHelper.java:19— app/src/main/java/io/xpipe/app/util/DesktopHelper.java:19-30 | app/src/main/java/io/xpipe/app/util/DesktopHelper.java:59-70 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (22 lines × 2) app/src/main/java/io/xpipe/app/browser/file/BrowserFileListComp.java:438— app/src/main/java/io/xpipe/app/browser/file/BrowserFileListComp.java:438-459 | app/src/main/java/io/xpipe/app/browser/file/BrowserStatusBarComp.java:217-238 — 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 `app/src/main/java/io/xpipe/app/browser/file/BrowserFileListComp.java:438` 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 (22 lines × 2) app/src/main/java/io/xpipe/app/browser/menu/impl/CopyPathMenuProvider.java:67— app/src/main/java/io/xpipe/app/browser/menu/impl/CopyPathMenuProvider.java:67-88 | app/src/main/java/io/xpipe/app/browser/menu/impl/CopyPathMenuProvider.java:96-117 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (22 lines × 2) app/src/main/java/io/xpipe/app/browser/menu/impl/CopyPathMenuProvider.java:166— app/src/main/java/io/xpipe/app/browser/menu/impl/CopyPathMenuProvider.java:166-187 | app/src/main/java/io/xpipe/app/browser/menu/impl/CopyPathMenuProvider.java:195-216 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (22 lines × 2) app/src/main/java/io/xpipe/app/browser/menu/impl/NewItemMenuProvider.java:52— app/src/main/java/io/xpipe/app/browser/menu/impl/NewItemMenuProvider.java:52-73 | app/src/main/java/io/xpipe/app/browser/menu/impl/NewItemMenuProvider.java:99-120 — 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 `app/src/main/java/io/xpipe/app/browser/menu/impl/NewItemMenuProvider.java:52` 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) app/src/main/java/io/xpipe/app/beacon/mcp/HttpStreamableServerTransportProvider.java:146— app/src/main/java/io/xpipe/app/beacon/mcp/HttpStreamableServerTransportProvider.java:146-162 | app/src/main/java/io/xpipe/app/beacon/mcp/HttpStreamableServerTransportProvider.java:220-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.
Duplicated block (17 lines × 2) app/src/main/java/io/xpipe/app/terminal/OhMyPoshTerminalPrompt.java:138— app/src/main/java/io/xpipe/app/terminal/OhMyPoshTerminalPrompt.java:138-154 | app/src/main/java/io/xpipe/app/terminal/StarshipTerminalPrompt.java:31-47 — before extracting anything, compare `app/src/main/java/io/xpipe/app/terminal/OhMyPoshTerminalPrompt.java` and `app/src/main/java/io/xpipe/app/terminal/StarshipTerminalPrompt.java` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 62 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (17 lines × 2) app/src/main/java/io/xpipe/app/util/AskpassAlert.java:79— app/src/main/java/io/xpipe/app/util/AskpassAlert.java:79-95 | app/src/main/java/io/xpipe/app/util/AsktextAlert.java:32-48 — 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 `app/src/main/java/io/xpipe/app/util/AskpassAlert.java:79` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (17 lines × 2) ext/system/src/main/java/io/xpipe/ext/system/incus/IncusContainerStore.java:124— ext/system/src/main/java/io/xpipe/ext/system/incus/IncusContainerStore.java:124-140 | ext/system/src/main/java/io/xpipe/ext/system/lxd/LxdContainerStore.java:127-143 — before extracting anything, compare `ext/system/src/main/java/io/xpipe/ext/system/incus/IncusContainerStore.java` and `ext/system/src/main/java/io/xpipe/ext/system/lxd/LxdContainerStore.java` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 70 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 `ext/system/src/main/java/io/xpipe/ext/system/incus/IncusContainerStore.java:124` 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 (16 lines × 2) app/src/main/java/io/xpipe/app/comp/base/ChoiceComp.java:71— app/src/main/java/io/xpipe/app/comp/base/ChoiceComp.java:71-86 | app/src/main/java/io/xpipe/app/comp/base/ChoicePaneComp.java:65-80 — 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 `app/src/main/java/io/xpipe/app/comp/base/ChoiceComp.java:71` 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 (16 lines × 2) app/src/main/java/io/xpipe/app/core/AppImages.java:65— app/src/main/java/io/xpipe/app/core/AppImages.java:65-80 | app/src/main/java/io/xpipe/app/core/AppImages.java:83-98 — 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (16 lines × 2) app/src/main/java/io/xpipe/app/rdp/RemminaRdpClient.java:27— app/src/main/java/io/xpipe/app/rdp/RemminaRdpClient.java:27-42 | app/src/main/java/io/xpipe/app/vnc/RemminaVncClient.java:30-45 — 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 `app/src/main/java/io/xpipe/app/rdp/RemminaRdpClient.java:27` 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 first that the copies are not typed on the same thing: the declarations holding them bind `property` to `Property<RemminaRdpClient>` in one and `Property<RemminaVncClient>` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (16 lines × 2) ext/system/src/main/java/io/xpipe/ext/system/incus/IncusContainerStore.java:147— ext/system/src/main/java/io/xpipe/ext/system/incus/IncusContainerStore.java:147-162 | ext/system/src/main/java/io/xpipe/ext/system/lxd/LxdContainerStore.java:150-165 — before extracting anything, compare `ext/system/src/main/java/io/xpipe/ext/system/incus/IncusContainerStore.java` and `ext/system/src/main/java/io/xpipe/ext/system/lxd/LxdContainerStore.java` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 70 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (20 lines × 2) app/src/main/java/io/xpipe/app/beacon/mcp/HttpStreamableServerTransportProvider.java:164— app/src/main/java/io/xpipe/app/beacon/mcp/HttpStreamableServerTransportProvider.java:164-183 | app/src/main/java/io/xpipe/app/beacon/mcp/HttpStreamableServerTransportProvider.java:312-331 — 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 `app/src/main/java/io/xpipe/app/beacon/mcp/HttpStreamableServerTransportProvider.java:164` 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) app/src/main/java/io/xpipe/app/platform/PlatformThread.java:51— app/src/main/java/io/xpipe/app/platform/PlatformThread.java:51-70 | app/src/main/java/io/xpipe/app/platform/PlatformThread.java:243-262 — 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 `app/src/main/java/io/xpipe/app/platform/PlatformThread.java:51` 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) app/src/main/java/io/xpipe/app/util/SshLocalBridge.java:62— app/src/main/java/io/xpipe/app/util/SshLocalBridge.java:62-81 | app/src/main/java/io/xpipe/app/util/SshLocalBridge.java:84-103 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (15 lines × 2) app/src/main/java/io/xpipe/app/hub/section/StoreSection.java:73— app/src/main/java/io/xpipe/app/hub/section/StoreSection.java:73-87 | app/src/main/java/io/xpipe/app/hub/section/StoreSection.java:112-126 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (15 lines × 2) app/src/main/java/io/xpipe/app/spice/RemoteViewerSpiceClient.java:46— app/src/main/java/io/xpipe/app/spice/RemoteViewerSpiceClient.java:46-60 | app/src/main/java/io/xpipe/app/vnc/RemoteViewerVncClient.java:96-110 — 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (15 lines × 2) app/src/main/java/io/xpipe/app/terminal/KittyTerminalType.java:208— app/src/main/java/io/xpipe/app/terminal/KittyTerminalType.java:208-222 | app/src/main/java/io/xpipe/app/terminal/KittyTerminalType.java:259-273 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/io/xpipe/app/terminal/KittyTerminalType.java:208` 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 (8–9 lines × 2) app/src/main/java/io/xpipe/app/browser/menu/impl/CopyPathMenuProvider.java:115— app/src/main/java/io/xpipe/app/browser/menu/impl/CopyPathMenuProvider.java:115-122 | app/src/main/java/io/xpipe/app/browser/menu/impl/CopyPathMenuProvider.java:214-222 — 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 `app/src/main/java/io/xpipe/app/browser/menu/impl/CopyPathMenuProvider.java:115` 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 (8–9 lines × 2) app/src/main/java/io/xpipe/app/comp/base/ListBoxViewComp.java:95— app/src/main/java/io/xpipe/app/comp/base/ListBoxViewComp.java:95-102 | app/src/main/java/io/xpipe/app/comp/base/ScrollComp.java:31-39 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (8–9 lines × 2) ext/base/src/main/java/io/xpipe/ext/base/script/RunFileScriptMenuProvider.java:107— ext/base/src/main/java/io/xpipe/ext/base/script/RunFileScriptMenuProvider.java:107-115 | ext/base/src/main/java/io/xpipe/ext/base/script/RunScriptActionProviderMenu.java:377-384 — 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (8 lines × 3) app/src/main/java/io/xpipe/app/browser/file/BrowserFileOpener.java:32— app/src/main/java/io/xpipe/app/browser/file/BrowserFileOpener.java:32-39 | app/src/main/java/io/xpipe/app/browser/file/BrowserFileOpener.java:51-58 | app/src/main/java/io/xpipe/app/browser/file/BrowserFileOpener.java:85-92 — 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 `app/src/main/java/io/xpipe/app/browser/file/BrowserFileOpener.java:32` 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 (8 lines × 3) app/src/main/java/io/xpipe/app/core/AppImages.java:47— app/src/main/java/io/xpipe/app/core/AppImages.java:47-54 | app/src/main/java/io/xpipe/app/core/AppImages.java:66-73 | app/src/main/java/io/xpipe/app/core/AppImages.java:84-91 — 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 `app/src/main/java/io/xpipe/app/core/AppImages.java:47` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (8 lines × 3) app/src/main/java/io/xpipe/app/rdp/CustomRdpClient.java:28— app/src/main/java/io/xpipe/app/rdp/CustomRdpClient.java:28-35 | app/src/main/java/io/xpipe/app/spice/CustomSpiceClient.java:28-35 | app/src/main/java/io/xpipe/app/vnc/CustomVncClient.java:28-35 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 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 3 times. Note first that the copies are not typed on the same thing: the declarations holding them bind `property` to `Property<CustomRdpClient>` in one and `Property<CustomSpiceClient>` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (7 lines × 3) app/src/main/java/io/xpipe/app/beacon/mcp/McpTools.java:208— app/src/main/java/io/xpipe/app/beacon/mcp/McpTools.java:208-214 | app/src/main/java/io/xpipe/app/beacon/mcp/McpTools.java:234-240 | app/src/main/java/io/xpipe/app/beacon/mcp/McpTools.java:295-301 — 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 `app/src/main/java/io/xpipe/app/beacon/mcp/McpTools.java:208` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 3) app/src/main/java/io/xpipe/app/browser/menu/BrowserMenuLeafProvider.java:40— app/src/main/java/io/xpipe/app/browser/menu/BrowserMenuLeafProvider.java:40-46 | app/src/main/java/io/xpipe/app/hub/action/BatchHubProvider.java:60-66 | app/src/main/java/io/xpipe/app/hub/action/HubLeafProvider.java:22-28 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 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 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/io/xpipe/app/browser/menu/BrowserMenuLeafProvider.java:40` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 3) app/src/main/java/io/xpipe/app/browser/menu/impl/ChgrpMenuProvider.java:69— app/src/main/java/io/xpipe/app/browser/menu/impl/ChgrpMenuProvider.java:69-75 | app/src/main/java/io/xpipe/app/browser/menu/impl/ChmodMenuProvider.java:61-67 | app/src/main/java/io/xpipe/app/browser/menu/impl/ChownMenuProvider.java:68-74 — before extracting anything, compare `app/src/main/java/io/xpipe/app/browser/menu/impl/ChgrpMenuProvider.java` and `app/src/main/java/io/xpipe/app/browser/menu/impl/ChownMenuProvider.java` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 32 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (6 lines × 3) app/src/main/java/io/xpipe/app/beacon/mcp/McpTools.java:261— app/src/main/java/io/xpipe/app/beacon/mcp/McpTools.java:261-266 | app/src/main/java/io/xpipe/app/beacon/mcp/McpTools.java:369-374 | app/src/main/java/io/xpipe/app/beacon/mcp/McpTools.java:417-422 — 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 `app/src/main/java/io/xpipe/app/beacon/mcp/McpTools.java:261` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `app/src/main/java/io/xpipe/app/beacon/mcp/McpTools.java:268` calls `getOptionalBooleanArgument`, `orElse` and `app/src/main/java/io/xpipe/app/beacon/mcp/McpTools.java:376` 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.
Duplicated block (6 lines × 3) ext/base/src/main/java/io/xpipe/ext/base/service/CustomServiceStoreProvider.java:77— ext/base/src/main/java/io/xpipe/ext/base/service/CustomServiceStoreProvider.java:77-82 | ext/base/src/main/java/io/xpipe/ext/base/service/FixedServiceStoreProvider.java:50-55 | ext/base/src/main/java/io/xpipe/ext/base/service/MappedServiceStoreProvider.java:41-46 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `ext/base/src/main/java/io/xpipe/ext/base/service/CustomServiceStoreProvider.java:77` 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 (6 lines × 3) app/src/main/java/io/xpipe/app/hub/action/BatchStoreAction.java:81— app/src/main/java/io/xpipe/app/hub/action/BatchStoreAction.java:81-86 | app/src/main/java/io/xpipe/app/hub/action/MultiStoreAction.java:52-57 | app/src/main/java/io/xpipe/app/hub/action/StoreAction.java:49-54 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Change coupling: BrowserContextMenu.java ↔ BrowserFileListComp.java app/src/main/java/io/xpipe/app/browser/file/BrowserContextMenu.java:1— `app/src/main/java/io/xpipe/app/browser/file/BrowserContextMenu.java` and `app/src/main/java/io/xpipe/app/browser/file/BrowserFileListComp.java` 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). They sit in the same directory, and in this ecosystem sibling files there normally share one namespace/package — so a direct reference between them needs no import and this pass cannot see whether one exists. Read the pair before acting: if one file only DECLARES what the other consumes (a constants/types file beside its user), the co-change is definitional and the question is whether the split earns its keep; if they duplicate structure, extract the common part into a shared function or type they both call; 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 `ef7381f6` Rework context menus; `7ac78a2b` Fix: Context menu should be closed when renaming the file (#719) (#720); `fe5686c0` Various browser fixes — run `git show` on any of them.
Change coupling: AppDirectoryPermissionsCheck.java ↔ AppOperationMode.java app/src/main/java/io/xpipe/app/core/check/AppDirectoryPermissionsCheck.java:1— `app/src/main/java/io/xpipe/app/core/check/AppDirectoryPermissionsCheck.java` and `app/src/main/java/io/xpipe/app/core/mode/AppOperationMode.java` 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 `f4eac523` Small fixes [stage] [arm] (at that commit the file was still `app/src/main/java/io/xpipe/app/core/mode/OperationMode.java`); `a5878221` Improve directory permissions check (at that commit the file was still `app/src/main/java/io/xpipe/app/core/mode/OperationMode.java`); `3df5a1f6` Various resilience fixes (at that commit the files were still `app/src/main/java/io/xpipe/app/core/check/AppUserDirectoryCheck.java` and `app/src/main/java/io/xpipe/app/core/mode/OperationMode.java`) — run `git show` on any of them.
Duplicated block (28 lines × 2) ext/system/src/main/java/io/xpipe/ext/system/incus/IncusCommandView.java:108— ext/system/src/main/java/io/xpipe/ext/system/incus/IncusCommandView.java:108-135 | ext/system/src/main/java/io/xpipe/ext/system/lxd/LxdCommandView.java:183-210 — before extracting anything, compare `ext/system/src/main/java/io/xpipe/ext/system/incus/IncusCommandView.java` and `ext/system/src/main/java/io/xpipe/ext/system/lxd/LxdCommandView.java` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 110 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (28 lines × 2) app/src/main/java/io/xpipe/app/rdp/RdpLaunchConfig.java:1— app/src/main/java/io/xpipe/app/rdp/RdpLaunchConfig.java:1-39 | app/src/main/java/io/xpipe/app/rdp/RdpLaunchConfigGateway.java:1-28 — 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 `app/src/main/java/io/xpipe/app/rdp/RdpLaunchConfig.java:1` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (18 lines × 2) app/src/main/java/io/xpipe/app/browser/menu/impl/CopyPathMenuProvider.java:86— app/src/main/java/io/xpipe/app/browser/menu/impl/CopyPathMenuProvider.java:86-103 | app/src/main/java/io/xpipe/app/browser/menu/impl/CopyPathMenuProvider.java:185-202 — 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 `app/src/main/java/io/xpipe/app/browser/menu/impl/CopyPathMenuProvider.java:86` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (18 lines × 2) app/src/main/java/io/xpipe/app/comp/base/CheckBoxComp.java:31— app/src/main/java/io/xpipe/app/comp/base/CheckBoxComp.java:31-48 | app/src/main/java/io/xpipe/app/comp/base/ToggleSwitchComp.java:52-69 — 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 `app/src/main/java/io/xpipe/app/comp/base/CheckBoxComp.java:31` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 3) app/src/main/java/io/xpipe/app/browser/menu/MultiExecuteMenuProvider.java:27— app/src/main/java/io/xpipe/app/browser/menu/MultiExecuteMenuProvider.java:27-38 | app/src/main/java/io/xpipe/app/browser/menu/MultiExecuteMenuProvider.java:62-73 | app/src/main/java/io/xpipe/app/browser/menu/MultiExecuteMenuProvider.java:89-100 — 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 `app/src/main/java/io/xpipe/app/browser/menu/MultiExecuteMenuProvider.java:27` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 3) app/src/main/java/io/xpipe/app/action/XPipeUrlProvider.java:76— app/src/main/java/io/xpipe/app/action/XPipeUrlProvider.java:76-87 | app/src/main/java/io/xpipe/app/beacon/api/ActionExchange.java:38-49 | app/src/main/java/io/xpipe/app/beacon/api/TerminalExternalLaunchExchange.java:66-77 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 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 3 times. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (9 lines × 3) app/src/main/java/io/xpipe/app/browser/menu/MultiExecuteMenuProvider.java:40— app/src/main/java/io/xpipe/app/browser/menu/MultiExecuteMenuProvider.java:40-48 | app/src/main/java/io/xpipe/app/browser/menu/MultiExecuteMenuProvider.java:75-83 | app/src/main/java/io/xpipe/app/browser/menu/MultiExecuteMenuProvider.java:102-110 — 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 `app/src/main/java/io/xpipe/app/browser/menu/MultiExecuteMenuProvider.java:40` 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 (9 lines × 3) app/src/main/java/io/xpipe/app/comp/base/LazyTextFieldComp.java:73— app/src/main/java/io/xpipe/app/comp/base/LazyTextFieldComp.java:73-81 | app/src/main/java/io/xpipe/app/comp/base/TextAreaComp.java:53-62 | app/src/main/java/io/xpipe/app/comp/base/TextFieldComp.java:46-55 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/io/xpipe/app/comp/base/LazyTextFieldComp.java:73` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `app/src/main/java/io/xpipe/app/comp/base/TextAreaComp.java:52` calls `setValue` and `app/src/main/java/io/xpipe/app/comp/base/TextFieldComp.java:45` does not — after which the two agree again for 4 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 (5 lines × 3) app/src/main/java/io/xpipe/app/terminal/KittyTerminalType.java:57— app/src/main/java/io/xpipe/app/terminal/KittyTerminalType.java:57-61 | app/src/main/java/io/xpipe/app/terminal/KittyTerminalType.java:93-98 | app/src/main/java/io/xpipe/app/terminal/KittyTerminalType.java:114-118 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (5 lines × 3) app/src/main/java/io/xpipe/app/browser/menu/MultiExecuteMenuProvider.java:55— app/src/main/java/io/xpipe/app/browser/menu/MultiExecuteMenuProvider.java:55-60 | ext/base/src/main/java/io/xpipe/ext/base/script/RunScriptActionProviderMenu.java:195-199 | ext/base/src/main/java/io/xpipe/ext/base/script/RunScriptActionProviderMenu.java:212-216 — there are 3 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 3 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/io/xpipe/app/browser/menu/MultiExecuteMenuProvider.java:55` 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. 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.
Sync-over-async blocking app/src/main/java/io/xpipe/app/beacon/mcp/HttpStreamableServerTransportProvider.java:118— `closeGracefully` is async and calls .block() — a blocking call inside async code stalls the event-loop thread the reactive pipeline runs on for as long as it runs.
Sync-over-async blocking app/src/main/java/io/xpipe/app/beacon/mcp/HttpStreamableServerTransportProvider.java:93— `notifyClients` is async and calls .block() — a blocking call inside async code stalls the event-loop thread the reactive pipeline runs on for as long as it runs.
StoreEntryWrapper.update (cyclomatic 38) app/src/main/java/io/xpipe/app/hub/entry/StoreEntryWrapper.java:153— StoreEntryWrapper.update has cyclomatic complexity 38 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
StandardStorage.reloadContent (cyclomatic 37) app/src/main/java/io/xpipe/app/storage/StandardStorage.java:80— StandardStorage.reloadContent has cyclomatic complexity 37 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
AppDistributionType.determine (cyclomatic 35) app/src/main/java/io/xpipe/app/update/AppDistributionType.java:151— AppDistributionType.determine has cyclomatic complexity 35 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
BrowserFileTransferOperation.handleSingleAcrossFileSystems (cyclomatic 34) app/src/main/java/io/xpipe/app/browser/file/BrowserFileTransferOperation.java:269— BrowserFileTransferOperation.handleSingleAcrossFileSystems 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.
DataStorageQuery.toRegex (cyclomatic 33) app/src/main/java/io/xpipe/app/storage/DataStorageQuery.java:94— DataStorageQuery.toRegex has cyclomatic complexity 33 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
TlsCertificateFormat.parseDn (cyclomatic 29) app/src/main/java/io/xpipe/app/util/TlsCertificateFormat.java:103— TlsCertificateFormat.parseDn 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.
DataStorage.refreshChildren (cyclomatic 29) app/src/main/java/io/xpipe/app/storage/DataStorage.java:739— DataStorage.refreshChildren has cyclomatic complexity 29 (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.
BeaconRequestHandler.handleAuthenticatedRequest (cyclomatic 28) app/src/main/java/io/xpipe/app/beacon/BeaconRequestHandler.java:71— BeaconRequestHandler.handleAuthenticatedRequest has cyclomatic complexity 28 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
StoreEntryComp.createContextMenu (cyclomatic 27) app/src/main/java/io/xpipe/app/hub/entry/StoreEntryComp.java:467— StoreEntryComp.createContextMenu has cyclomatic complexity 27 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
TerminalLauncher.open (cyclomatic 26) app/src/main/java/io/xpipe/app/terminal/TerminalLauncher.java:135— TerminalLauncher.open has cyclomatic complexity 26 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
OptionsComp.createSimple (cyclomatic 26) app/src/main/java/io/xpipe/app/comp/base/OptionsComp.java:49— OptionsComp.createSimple has cyclomatic complexity 26 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ModalOverlayComp.createSimple (cyclomatic 26) app/src/main/java/io/xpipe/app/comp/base/ModalOverlayComp.java:54— ModalOverlayComp.createSimple has cyclomatic complexity 26 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
HttpStreamableServerTransportProvider.doPost (cyclomatic 26) app/src/main/java/io/xpipe/app/beacon/mcp/HttpStreamableServerTransportProvider.java:218— HttpStreamableServerTransportProvider.doPost has cyclomatic complexity 26 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
AbstractServiceStore.newSession (cyclomatic 25) ext/base/src/main/java/io/xpipe/ext/base/service/AbstractServiceStore.java:144— AbstractServiceStore.newSession has cyclomatic complexity 25 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
BrowserSessionTabsComp.createTab (cyclomatic 25) app/src/main/java/io/xpipe/app/browser/BrowserSessionTabsComp.java:416— BrowserSessionTabsComp.createTab 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.
IdentitySelectComp.createComboBox (cyclomatic 24) ext/base/src/main/java/io/xpipe/ext/base/identity/IdentitySelectComp.java:193— IdentitySelectComp.createComboBox has cyclomatic complexity 24 (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.
SentryErrorHandler.fillScope (cyclomatic 24) REDACTED:176— SentryErrorHandler.fillScope has cyclomatic complexity 24 (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.
SystemIconCache.rebuildCache (cyclomatic 24) REDACTED:47— SystemIconCache.rebuildCache has cyclomatic complexity 24 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
IntFieldComp.createSimple (cyclomatic 24) app/src/main/java/io/xpipe/app/comp/base/IntFieldComp.java:31— IntFieldComp.createSimple has cyclomatic complexity 24 (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.
SecretQueryProgress.process (cyclomatic 23) app/src/main/java/io/xpipe/app/secret/SecretQueryProgress.java:61— SecretQueryProgress.process has cyclomatic complexity 23 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
StoreChoicePopover.getPopover (cyclomatic 23) app/src/main/java/io/xpipe/app/hub/creation/StoreChoicePopover.java:84— StoreChoicePopover.getPopover has cyclomatic complexity 23 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
StoreCreationModel.<init> (cyclomatic 22) app/src/main/java/io/xpipe/app/hub/creation/StoreCreationModel.java:59— StoreCreationModel.<init> has cyclomatic complexity 22 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
AppOperationMode.setup (cyclomatic 22) app/src/main/java/io/xpipe/app/core/mode/AppOperationMode.java:72— AppOperationMode.setup has cyclomatic complexity 22 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
ErrorEventFactory.formatThrowableMessage (cyclomatic 21) app/src/main/java/io/xpipe/app/issue/ErrorEventFactory.java:63— ErrorEventFactory.formatThrowableMessage 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.
BrowserFileTransferOperation.transfer (cyclomatic 21) app/src/main/java/io/xpipe/app/browser/file/BrowserFileTransferOperation.java:484— BrowserFileTransferOperation.transfer has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
DataStoreEntry.fromDirectory (cyclomatic 20) app/src/main/java/io/xpipe/app/storage/DataStoreEntry.java:218— DataStoreEntry.fromDirectory 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.
FreeRdpClient.launch (cyclomatic 20) app/src/main/java/io/xpipe/app/rdp/FreeRdpClient.java:131— FreeRdpClient.launch has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
PlatformState.initPlatform (cyclomatic 20) app/src/main/java/io/xpipe/app/platform/PlatformState.java:105— PlatformState.initPlatform 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.
StoreSectionConfig.show (cyclomatic 20) app/src/main/java/io/xpipe/app/hub/section/StoreSectionConfig.java:70— StoreSectionConfig.show has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
BrowserFileListComp.prepareTableChanges (cyclomatic 20) app/src/main/java/io/xpipe/app/browser/file/BrowserFileListComp.java:544— BrowserFileListComp.prepareTableChanges has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
StandardStorage.save (cyclomatic 19) app/src/main/java/io/xpipe/app/storage/StandardStorage.java:438— StandardStorage.save has cyclomatic complexity 19 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
DataStoreEntry.writeDataToDisk (cyclomatic 19) app/src/main/java/io/xpipe/app/storage/DataStoreEntry.java:563— DataStoreEntry.writeDataToDisk has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
StoreFilterFieldComp.createSimple (cyclomatic 19) app/src/main/java/io/xpipe/app/hub/list/StoreFilterFieldComp.java:37— StoreFilterFieldComp.createSimple has cyclomatic complexity 19 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
DataStoreEntryNode.prepareForWrite (cyclomatic 18) app/src/main/java/io/xpipe/app/storage/DataStoreEntryNode.java:53— DataStoreEntryNode.prepareForWrite 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.
AppPrefs.fixLocalValues (cyclomatic 18) app/src/main/java/io/xpipe/app/prefs/AppPrefs.java:853— AppPrefs.fixLocalValues has cyclomatic complexity 18 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
OptionsChoiceBuilder.build (cyclomatic 18) app/src/main/java/io/xpipe/app/platform/OptionsChoiceBuilder.java:123— OptionsChoiceBuilder.build 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.
StoreCreationModel.finish (cyclomatic 18) app/src/main/java/io/xpipe/app/hub/creation/StoreCreationModel.java:285— StoreCreationModel.finish has cyclomatic complexity 18 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
ContextualFileReferenceChoiceComp.createSimple (cyclomatic 18) app/src/main/java/io/xpipe/app/comp/base/ContextualFileReferenceChoiceComp.java:73— ContextualFileReferenceChoiceComp.createSimple has cyclomatic complexity 18 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
BrowserFileSystemTabModel.cdSyncOrRetry (cyclomatic 18) app/src/main/java/io/xpipe/app/browser/file/BrowserFileSystemTabModel.java:366— BrowserFileSystemTabModel.cdSyncOrRetry has cyclomatic complexity 18 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
BrowserFileListComp.formatOwner (cyclomatic 18) app/src/main/java/io/xpipe/app/browser/file/BrowserFileListComp.java:223— BrowserFileListComp.formatOwner has cyclomatic complexity 18 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
1.handle (cyclomatic 18) app/src/main/java/io/xpipe/app/beacon/mcp/AppMcpServer.java:102— 1.handle 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.
OptionalEncryptedValue.with (cyclomatic 17) app/src/main/java/io/xpipe/app/secret/OptionalEncryptedValue.java:79— OptionalEncryptedValue.with has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
MultiPrincipalSecret.with (cyclomatic 17) app/src/main/java/io/xpipe/app/secret/MultiPrincipalSecret.java:179— MultiPrincipalSecret.with has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
AppModifiedStage.applyModes (cyclomatic 17) app/src/main/java/io/xpipe/app/core/window/AppModifiedStage.java:90— AppModifiedStage.applyModes has cyclomatic complexity 17 (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.
SecretFieldComp.createBase (cyclomatic 17) app/src/main/java/io/xpipe/app/comp/base/SecretFieldComp.java:67— SecretFieldComp.createBase has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
RegionDescriptor.apply (cyclomatic 17) app/src/main/java/io/xpipe/app/comp/RegionDescriptor.java:36— RegionDescriptor.apply has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
ScriptHierarchy.buildEnabledHierarchy (cyclomatic 16) ext/base/src/main/java/io/xpipe/ext/base/script/ScriptHierarchy.java:20— ScriptHierarchy.buildEnabledHierarchy 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.
HttpProxy.detectFromEnvironment (cyclomatic 16) app/src/main/java/io/xpipe/app/util/HttpProxy.java:32— HttpProxy.detectFromEnvironment 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.
MicrosoftRdpClient.launch (cyclomatic 16) app/src/main/java/io/xpipe/app/rdp/MicrosoftRdpClient.java:166— MicrosoftRdpClient.launch 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.
IconsCategory.createOverview (cyclomatic 16) app/src/main/java/io/xpipe/app/prefs/IconsCategory.java:63— IconsCategory.createOverview 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.
StoreCreationComp.createLayout (cyclomatic 16) app/src/main/java/io/xpipe/app/hub/creation/StoreCreationComp.java:44— StoreCreationComp.createLayout 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.
StoreCategoryComp.createSimple (cyclomatic 16) app/src/main/java/io/xpipe/app/hub/category/StoreCategoryComp.java:51— StoreCategoryComp.createSimple 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.
AppLayoutModel.addListeners (cyclomatic 16) app/src/main/java/io/xpipe/app/core/AppLayoutModel.java:89— AppLayoutModel.addListeners 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.
ModalOverlayComp.toBox (cyclomatic 16) app/src/main/java/io/xpipe/app/comp/base/ModalOverlayComp.java:204— ModalOverlayComp.toBox 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.
AppMainWindowContentComp.createSimple (cyclomatic 16) app/src/main/java/io/xpipe/app/comp/base/AppMainWindowContentComp.java:42— AppMainWindowContentComp.createSimple 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.
BrowserFileTransferOperation.execute (cyclomatic 16) app/src/main/java/io/xpipe/app/browser/file/BrowserFileTransferOperation.java:161— BrowserFileTransferOperation.execute 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.
ActionJacksonMapper.parse (cyclomatic 16) app/src/main/java/io/xpipe/app/action/ActionJacksonMapper.java:20— ActionJacksonMapper.parse 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.
No assertions: test app/src/localTest/java/test/Test.java:9— This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
D10 · Test Quality· Test project verifies nothing · ×1
Test project verifies nothing: app app/src/localTest/java/test/Test.java:9— No conventional assertion call was detected in 1 of 1 tests in `app` — the project as a whole, not one method. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a suite that genuinely checks nothing. If it is the latter, this project passes unconditionally and cannot fail.
AppDistributionType.determine (cognitive 67) app/src/main/java/io/xpipe/app/update/AppDistributionType.java:151— AppDistributionType.determine has cognitive complexity 67 (threshold 15). Drivers by points: if/else 23 (51 pts), boolean chains 10, error handling 2 (6 pts) (nesting depth added 32). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
BrowserFileTransferOperation.handleSingleAcrossFileSystems (cognitive 59) app/src/main/java/io/xpipe/app/browser/file/BrowserFileTransferOperation.java:269— BrowserFileTransferOperation.handleSingleAcrossFileSystems has cognitive complexity 59 (threshold 15). Drivers by points: if/else 27 (51 pts), boolean chains 7, loops 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.
SystemIconCache.rebuildCache (cognitive 56) REDACTED:47— SystemIconCache.rebuildCache has cognitive complexity 56 (threshold 15). Drivers by points: if/else 14 (41 pts), loops 5 (10 pts), boolean chains 3, error handling 1, ternaries 1 (nesting depth added 32). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
StoreEntryWrapper.update (cognitive 56) app/src/main/java/io/xpipe/app/hub/entry/StoreEntryWrapper.java:153— StoreEntryWrapper.update has cognitive complexity 56 (threshold 15). Drivers by points: if/else 22 (30 pts), boolean chains 12, error handling 3 (7 pts), ternaries 4 (7 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.
TlsCertificateFormat.parseDn (cognitive 55) app/src/main/java/io/xpipe/app/util/TlsCertificateFormat.java:103— TlsCertificateFormat.parseDn has cognitive complexity 55 (threshold 15). Drivers by points: if/else 11 (27 pts), loops 7 (15 pts), boolean chains 9, match/switch 1 (4 pts) (nesting depth added 27). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
StoreEntryComp.createContextMenu (cognitive 53) app/src/main/java/io/xpipe/app/hub/entry/StoreEntryComp.java:467— StoreEntryComp.createContextMenu has cognitive complexity 53 (threshold 15). Drivers by points: if/else 17 (42 pts), loops 3 (6 pts), boolean chains 3, ternaries 2 (nesting depth added 28). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
StandardStorage.reloadContent (cognitive 46) app/src/main/java/io/xpipe/app/storage/StandardStorage.java:80— StandardStorage.reloadContent has cognitive complexity 46 (threshold 15). Drivers by points: if/else 24 (32 pts), error handling 6 (8 pts), loops 4, boolean chains 2 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
BeaconRequestHandler.handleAuthenticatedRequest (cognitive 46) app/src/main/java/io/xpipe/app/beacon/BeaconRequestHandler.java:71— BeaconRequestHandler.handleAuthenticatedRequest has cognitive complexity 46 (threshold 15). Drivers by points: if/else 15 (23 pts), error handling 8 (10 pts), ternaries 3 (7 pts), boolean chains 6 (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.
ShellTemp.initUserSpecificTempDataDirectory (cognitive 44) app/src/main/java/io/xpipe/app/process/ShellTemp.java:27— ShellTemp.initUserSpecificTempDataDirectory has cognitive complexity 44 (threshold 15). Drivers by points: if/else 12 (43 pts), boolean chains 1 (nesting depth added 31). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
OptionsComp.createSimple (cognitive 43) app/src/main/java/io/xpipe/app/comp/base/OptionsComp.java:49— OptionsComp.createSimple has cognitive complexity 43 (threshold 15). Drivers by points: if/else 20 (32 pts), boolean chains 4, ternaries 3 (4 pts), loops 3 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AbstractServiceStore.newSession (cognitive 42) ext/base/src/main/java/io/xpipe/ext/base/service/AbstractServiceStore.java:144— AbstractServiceStore.newSession has cognitive complexity 42 (threshold 15). Drivers by points: if/else 17 (32 pts), boolean chains 6, ternaries 2 (4 pts) (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
IncusCommandView.listContainers (cognitive 38) ext/system/src/main/java/io/xpipe/ext/system/incus/IncusCommandView.java:239— IncusCommandView.listContainers has cognitive complexity 38 (threshold 15). Drivers by points: if/else 9 (27 pts), loops 3 (9 pts), boolean chains 1, error handling 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.
LxdCommandView.listContainers (cognitive 38) ext/system/src/main/java/io/xpipe/ext/system/lxd/LxdCommandView.java:250— LxdCommandView.listContainers has cognitive complexity 38 (threshold 15). Drivers by points: if/else 9 (27 pts), loops 3 (9 pts), boolean chains 1, error handling 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.
HttpProxy.detectFromEnvironment (cognitive 38) app/src/main/java/io/xpipe/app/util/HttpProxy.java:32— HttpProxy.detectFromEnvironment has cognitive complexity 38 (threshold 15). Drivers by points: ternaries 7 (23 pts), if/else 3 (8 pts), boolean chains 3, error handling 1 (3 pts), loops 1 (nesting depth added 23). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ModalOverlayComp.createSimple (cognitive 38) app/src/main/java/io/xpipe/app/comp/base/ModalOverlayComp.java:54— ModalOverlayComp.createSimple has cognitive complexity 38 (threshold 15). Drivers by points: if/else 20 (31 pts), boolean chains 4, ternaries 2, error handling 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TerminalLauncher.open (cognitive 36) app/src/main/java/io/xpipe/app/terminal/TerminalLauncher.java:135— TerminalLauncher.open has cognitive complexity 36 (threshold 15). Drivers by points: ternaries 11 (18 pts), if/else 6 (9 pts), boolean chains 6, loops 2 (3 pts) (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DataStorageQuery.toRegex (cognitive 36) app/src/main/java/io/xpipe/app/storage/DataStorageQuery.java:94— DataStorageQuery.toRegex has cognitive complexity 36 (threshold 15). Drivers by points: if/else 13 (27 pts), match/switch 2 (6 pts), boolean chains 2, loops 1 (nesting depth added 18). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
FreeRdpClient.launch (cognitive 34) app/src/main/java/io/xpipe/app/rdp/FreeRdpClient.java:131— FreeRdpClient.launch has cognitive complexity 34 (threshold 15). Drivers by points: if/else 15 (28 pts), ternaries 3 (4 pts), boolean chains 2 (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
BrowserFileTransferOperation.transfer (cognitive 34) app/src/main/java/io/xpipe/app/browser/file/BrowserFileTransferOperation.java:484— BrowserFileTransferOperation.transfer has cognitive complexity 34 (threshold 15). Drivers by points: if/else 16 (23 pts), error handling 5 (9 pts), boolean chains 2 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
1.handle (cognitive 34) app/src/main/java/io/xpipe/app/beacon/mcp/AppMcpServer.java:102— 1.handle has cognitive complexity 34 (threshold 15). Drivers by points: if/else 17 (33 pts), boolean chains 1 (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
HttpStreamableServerTransportProvider.doPost (cognitive 33) app/src/main/java/io/xpipe/app/beacon/mcp/HttpStreamableServerTransportProvider.java:218— HttpStreamableServerTransportProvider.doPost has cognitive complexity 33 (threshold 15). Drivers by points: if/else 17 (21 pts), error handling 5 (8 pts), boolean chains 4 (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.
StoreChoicePopover.getPopover (cognitive 32) app/src/main/java/io/xpipe/app/hub/creation/StoreChoicePopover.java:84— StoreChoicePopover.getPopover has cognitive complexity 32 (threshold 15). Drivers by points: ternaries 6 (14 pts), if/else 9 (11 pts), boolean chains 7 (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.
ScriptHierarchy.buildEnabledHierarchy (cognitive 31) ext/base/src/main/java/io/xpipe/ext/base/script/ScriptHierarchy.java:20— ScriptHierarchy.buildEnabledHierarchy has cognitive complexity 31 (threshold 15). Drivers by points: if/else 9 (24 pts), loops 4 (5 pts), boolean chains 2 (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DataStorage.refreshChildren (cognitive 31) app/src/main/java/io/xpipe/app/storage/DataStorage.java:739— DataStorage.refreshChildren has cognitive complexity 31 (threshold 15). Drivers by points: if/else 21 (22 pts), boolean chains 8, error handling 1 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
MultiPrincipalSecret.with (cognitive 31) app/src/main/java/io/xpipe/app/secret/MultiPrincipalSecret.java:179— MultiPrincipalSecret.with has cognitive complexity 31 (threshold 15). Drivers by points: if/else 8 (16 pts), ternaries 4 (10 pts), boolean chains 4, loops 1 (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SentryErrorHandler.fillScope (cognitive 30) REDACTED:176— SentryErrorHandler.fillScope has cognitive complexity 30 (threshold 15). Drivers by points: if/else 9 (12 pts), ternaries 9 (10 pts), boolean chains 5, error handling 2 (3 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.
BrowserFileListComp.prepareTableChanges (cognitive 30) app/src/main/java/io/xpipe/app/browser/file/BrowserFileListComp.java:544— BrowserFileListComp.prepareTableChanges has cognitive complexity 30 (threshold 15). Drivers by points: if/else 18 (25 pts), boolean chains 4, ternaries 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SecretQueryProgress.process (cognitive 29) app/src/main/java/io/xpipe/app/secret/SecretQueryProgress.java:61— SecretQueryProgress.process has cognitive complexity 29 (threshold 15). Drivers by points: if/else 16 (23 pts), boolean chains 4, loops 2 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AbstractServiceStoreProvider.supportsSession (cognitive 28) ext/base/src/main/java/io/xpipe/ext/base/service/AbstractServiceStoreProvider.java:31— AbstractServiceStoreProvider.supportsSession has cognitive complexity 28 (threshold 15). Drivers by points: if/else 11 (25 pts), boolean chains 3 (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
OptionsChoiceBuilder.build (cognitive 28) app/src/main/java/io/xpipe/app/platform/OptionsChoiceBuilder.java:123— OptionsChoiceBuilder.build has cognitive complexity 28 (threshold 15). Drivers by points: ternaries 8 (16 pts), if/else 7 (9 pts), loops 3 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
IdentitySelectComp.createComboBox (cognitive 27) ext/base/src/main/java/io/xpipe/ext/base/identity/IdentitySelectComp.java:193— IdentitySelectComp.createComboBox has cognitive complexity 27 (threshold 15). Drivers by points: if/else 18 (20 pts), boolean chains 5, loops 2 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
DataStoreEntry.writeDataToDisk (cognitive 27) app/src/main/java/io/xpipe/app/storage/DataStoreEntry.java:563— DataStoreEntry.writeDataToDisk has cognitive complexity 27 (threshold 15). Drivers by points: ternaries 7 (14 pts), if/else 8 (10 pts), boolean chains 2, loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ModalOverlayComp.toBox (cognitive 27) app/src/main/java/io/xpipe/app/comp/base/ModalOverlayComp.java:204— ModalOverlayComp.toBox has cognitive complexity 27 (threshold 15). Drivers by points: if/else 16 (20 pts), ternaries 2 (5 pts), loops 1 (2 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
StoreCreationModel.<init> (cognitive 26) app/src/main/java/io/xpipe/app/hub/creation/StoreCreationModel.java:59— StoreCreationModel.<init> has cognitive complexity 26 (threshold 15). Drivers by points: ternaries 9 (11 pts), if/else 8 (9 pts), boolean chains 6 (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.
IntFieldComp.createSimple (cognitive 26) app/src/main/java/io/xpipe/app/comp/base/IntFieldComp.java:31— IntFieldComp.createSimple has cognitive complexity 26 (threshold 15). Drivers by points: if/else 13 (14 pts), boolean chains 7, ternaries 2 (3 pts), error handling 2 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
AppPrefsStorageHandler.loadObject (cognitive 25) app/src/main/java/io/xpipe/app/prefs/AppPrefsStorageHandler.java:97— AppPrefsStorageHandler.loadObject has cognitive complexity 25 (threshold 15). Drivers by points: if/else 11 (24 pts), error handling 1 (nesting depth added 13). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
StoreSectionConfig.show (cognitive 25) app/src/main/java/io/xpipe/app/hub/section/StoreSectionConfig.java:70— StoreSectionConfig.show has cognitive complexity 25 (threshold 15). Drivers by points: if/else 11 (15 pts), boolean chains 8, error handling 1 (2 pts) (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Action.executeImpl (cognitive 25) app/src/main/java/io/xpipe/app/browser/menu/impl/compress/ZipActionProvider.java:34— Action.executeImpl has cognitive complexity 25 (threshold 15). Drivers by points: if/else 10 (18 pts), loops 2 (4 pts), boolean chains 2, error handling 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.
BrowserFileTransferOperation.execute (cognitive 25) app/src/main/java/io/xpipe/app/browser/file/BrowserFileTransferOperation.java:161— BrowserFileTransferOperation.execute has cognitive complexity 25 (threshold 15). Drivers by points: if/else 9 (17 pts), boolean chains 5, loops 2 (3 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
BrowserSessionTabsComp.createTab (cognitive 25) app/src/main/java/io/xpipe/app/browser/BrowserSessionTabsComp.java:416— BrowserSessionTabsComp.createTab has cognitive complexity 25 (threshold 15). Drivers by points: if/else 15, boolean chains 7, ternaries 3. 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.
SerializableAction.toDisplayMap (cognitive 25) app/src/main/java/io/xpipe/app/action/SerializableAction.java:46— SerializableAction.toDisplayMap has cognitive complexity 25 (threshold 15). Drivers by points: if/else 9 (18 pts), loops 2 (4 pts), ternaries 1 (3 pts) (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AppOperationMode.setup (cognitive 24) app/src/main/java/io/xpipe/app/core/mode/AppOperationMode.java:72— AppOperationMode.setup has cognitive complexity 24 (threshold 15). Drivers by points: if/else 14 (17 pts), boolean chains 6, error handling 1 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
TerminalPaneConfiguration.create (cognitive 23) app/src/main/java/io/xpipe/app/terminal/TerminalPaneConfiguration.java:66— TerminalPaneConfiguration.create has cognitive complexity 23 (threshold 15). Drivers by points: ternaries 6 (13 pts), if/else 5 (7 pts), boolean chains 3 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MultiPrincipalSecret.deserialize (cognitive 23) app/src/main/java/io/xpipe/app/secret/MultiPrincipalSecret.java:99— MultiPrincipalSecret.deserialize has cognitive complexity 23 (threshold 15). Drivers by points: if/else 10 (20 pts), boolean chains 2, 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.
PlatformState.initPlatform (cognitive 23) app/src/main/java/io/xpipe/app/platform/PlatformState.java:105— PlatformState.initPlatform has cognitive complexity 23 (threshold 15). Drivers by points: if/else 9 (11 pts), error handling 5, boolean chains 4, match/switch 1 (3 pts) (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
ErrorEventFactory.formatThrowableMessage (cognitive 23) app/src/main/java/io/xpipe/app/issue/ErrorEventFactory.java:63— ErrorEventFactory.formatThrowableMessage has cognitive complexity 23 (threshold 15). Drivers by points: if/else 15 (17 pts), boolean chains 6 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
1.scan (cognitive 22) app/src/main/java/io/xpipe/app/util/ScanDialogAction.java:17— 1.scan has cognitive complexity 22 (threshold 15). Drivers by points: if/else 5 (13 pts), boolean chains 6, error handling 1 (2 pts), loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DataStoreEntryNode.prepareForWrite (cognitive 22) app/src/main/java/io/xpipe/app/storage/DataStoreEntryNode.java:53— DataStoreEntryNode.prepareForWrite has cognitive complexity 22 (threshold 15). Drivers by points: boolean chains 10, if/else 6 (7 pts), ternaries 3 (5 pts) (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.
DataStorage.deleteStoreCategory (cognitive 22) app/src/main/java/io/xpipe/app/storage/DataStorage.java:1179— DataStorage.deleteStoreCategory has cognitive complexity 22 (threshold 15). Drivers by points: if/else 9 (15 pts), loops 3 (6 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.
PasswordManagerTestComp.testPasswordManager (cognitive 22) app/src/main/java/io/xpipe/app/pwman/PasswordManagerTestComp.java:254— PasswordManagerTestComp.testPasswordManager has cognitive complexity 22 (threshold 15). Drivers by points: if/else 10 (12 pts), ternaries 3 (8 pts), boolean chains 2 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AppExtensionManager.findAndParseExtension (cognitive 22) app/src/main/java/io/xpipe/app/core/AppExtensionManager.java:116— AppExtensionManager.findAndParseExtension has cognitive complexity 22 (threshold 15). Drivers by points: if/else 7 (16 pts), ternaries 1 (4 pts), error handling 1 (2 pts) (nesting depth added 13). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
BrowserFileTransferOperation.transferFile (cognitive 22) app/src/main/java/io/xpipe/app/browser/file/BrowserFileTransferOperation.java:617— BrowserFileTransferOperation.transferFile has cognitive complexity 22 (threshold 15). Drivers by points: if/else 11 (18 pts), loops 2, boolean chains 1, error handling 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
StoreFilterFieldComp.createSimple (cognitive 21) app/src/main/java/io/xpipe/app/hub/list/StoreFilterFieldComp.java:37— StoreFilterFieldComp.createSimple has cognitive complexity 21 (threshold 15). Drivers by points: if/else 13 (14 pts), boolean chains 4, ternaries 2 (3 pts) (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
AppLayoutModel.addListeners (cognitive 21) app/src/main/java/io/xpipe/app/core/AppLayoutModel.java:89— AppLayoutModel.addListeners has cognitive complexity 21 (threshold 15). Drivers by points: if/else 10 (15 pts), boolean chains 6 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
BrowserFileListComp.formatOwner (cognitive 21) app/src/main/java/io/xpipe/app/browser/file/BrowserFileListComp.java:223— BrowserFileListComp.formatOwner has cognitive complexity 21 (threshold 15). Drivers by points: ternaries 10 (14 pts), if/else 4, boolean chains 3 (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
ScanDialogBase.finish (cognitive 20) app/src/main/java/io/xpipe/app/util/ScanDialogBase.java:63— ScanDialogBase.finish has cognitive complexity 20 (threshold 15). Drivers by points: if/else 5 (13 pts), error handling 1 (3 pts), loops 2 (3 pts), boolean chains 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DataStoreEntry.fromDirectory (cognitive 20) app/src/main/java/io/xpipe/app/storage/DataStoreEntry.java:218— DataStoreEntry.fromDirectory has cognitive complexity 20 (threshold 15). Drivers by points: if/else 11 (12 pts), boolean chains 4, ternaries 3, loops 1 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
DataStorage.setupBuiltinCategories (cognitive 20) app/src/main/java/io/xpipe/app/storage/DataStorage.java:149— DataStorage.setupBuiltinCategories has cognitive complexity 20 (threshold 15). Drivers by points: if/else 17 (18 pts), boolean chains 2 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
StoreSection.insertSections (cognitive 20) app/src/main/java/io/xpipe/app/hub/section/StoreSection.java:159— StoreSection.insertSections has cognitive complexity 20 (threshold 15). Drivers by points: if/else 6 (11 pts), ternaries 3 (4 pts), boolean chains 3, loops 1 (2 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
StoreEntryBatchSelectComp.createSimple (cognitive 20) app/src/main/java/io/xpipe/app/hub/list/StoreEntryBatchSelectComp.java:26— StoreEntryBatchSelectComp.createSimple has cognitive complexity 20 (threshold 15). Drivers by points: if/else 10 (15 pts), loops 2 (4 pts), boolean chains 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
StoreCreationComp.createLayout (cognitive 20) app/src/main/java/io/xpipe/app/hub/creation/StoreCreationComp.java:44— StoreCreationComp.createLayout has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (12 pts), boolean chains 5, ternaries 2 (3 pts) (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
BrowserFileSystemTabModel.cdSyncOrRetry (cognitive 20) app/src/main/java/io/xpipe/app/browser/file/BrowserFileSystemTabModel.java:366— BrowserFileSystemTabModel.cdSyncOrRetry has cognitive complexity 20 (threshold 15). Drivers by points: if/else 12, error handling 4 (5 pts), boolean chains 2, ternaries 1 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
StoreEntryInformationComp.fill (cognitive 19) app/src/main/java/io/xpipe/app/hub/entry/StoreEntryInformationComp.java:84— StoreEntryInformationComp.fill has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (12 pts), boolean chains 4, loops 2 (3 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
StoreCreationModel.finish (cognitive 19) app/src/main/java/io/xpipe/app/hub/creation/StoreCreationModel.java:285— StoreCreationModel.finish has cognitive complexity 19 (threshold 15). Drivers by points: if/else 13 (15 pts), boolean chains 3, error handling 1 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
BrowserContextMenu.createMenu (cognitive 19) app/src/main/java/io/xpipe/app/browser/file/BrowserContextMenu.java:30— BrowserContextMenu.createMenu has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (10 pts), ternaries 3 (4 pts), loops 2 (3 pts), boolean chains 2 (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.
SecretEncryptExchange.handle (cognitive 19) app/src/main/java/io/xpipe/app/beacon/api/SecretEncryptExchange.java:30— SecretEncryptExchange.handle has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (17 pts), loops 1 (2 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
XPipeUrlProvider.createAction (cognitive 19) app/src/main/java/io/xpipe/app/action/XPipeUrlProvider.java:22— XPipeUrlProvider.createAction has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9 (16 pts), boolean chains 3 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
HostAddressChoiceComp.createComboBox (cognitive 18) ext/base/src/main/java/io/xpipe/ext/base/host/HostAddressChoiceComp.java:77— HostAddressChoiceComp.createComboBox has cognitive complexity 18 (threshold 15). Drivers by points: if/else 13 (17 pts), boolean chains 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.
AbstractServiceStore.requiresTunnel (cognitive 18) ext/base/src/main/java/io/xpipe/ext/base/service/AbstractServiceStore.java:98— AbstractServiceStore.requiresTunnel has cognitive complexity 18 (threshold 15). Drivers by points: if/else 11 (13 pts), boolean chains 5 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
WindowsTerminalType.toCommand (cognitive 18) app/src/main/java/io/xpipe/app/terminal/WindowsTerminalType.java:42— WindowsTerminalType.toCommand has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (9 pts), ternaries 5 (8 pts), loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
StandardStorage.save (cognitive 18) app/src/main/java/io/xpipe/app/storage/StandardStorage.java:438— StandardStorage.save has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9, error handling 5, boolean chains 4. 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.
OptionalEncryptedValue.with (cognitive 18) app/src/main/java/io/xpipe/app/secret/OptionalEncryptedValue.java:79— OptionalEncryptedValue.with has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (9 pts), boolean chains 6, ternaries 3 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
AppPrefs.fixLocalValues (cognitive 18) app/src/main/java/io/xpipe/app/prefs/AppPrefs.java:853— AppPrefs.fixLocalValues has cognitive complexity 18 (threshold 15). Drivers by points: if/else 12 (13 pts), boolean chains 4, ternaries 1 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
AppOpenArguments.parseActions (cognitive 18) app/src/main/java/io/xpipe/app/core/AppOpenArguments.java:70— AppOpenArguments.parseActions has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (7 pts), error handling 3 (5 pts), boolean chains 3, ternaries 1 (3 pts) (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AppLogs.init (cognitive 18) app/src/main/java/io/xpipe/app/core/AppLogs.java:79— AppLogs.init has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (9 pts), error handling 2 (4 pts), boolean chains 3, loops 1 (2 pts) (nesting depth added 5). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
SecretFieldComp.createBase (cognitive 18) app/src/main/java/io/xpipe/app/comp/base/SecretFieldComp.java:67— SecretFieldComp.createBase has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (8 pts), boolean chains 5, ternaries 4 (5 pts) (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
AppMainWindowContentComp.createSimple (cognitive 18) app/src/main/java/io/xpipe/app/comp/base/AppMainWindowContentComp.java:42— AppMainWindowContentComp.createSimple has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (10 pts), boolean chains 4, ternaries 3 (4 pts) (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
RegionDescriptor.apply (cognitive 18) app/src/main/java/io/xpipe/app/comp/RegionDescriptor.java:36— RegionDescriptor.apply has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (10 pts), ternaries 3 (5 pts), match/switch 1 (2 pts), boolean chains 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.
BrowserFileTransferOperation.killStreams (cognitive 18) app/src/main/java/io/xpipe/app/browser/file/BrowserFileTransferOperation.java:718— BrowserFileTransferOperation.killStreams has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (11 pts), error handling 2 (6 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.
ActionJacksonMapper.parse (cognitive 18) app/src/main/java/io/xpipe/app/action/ActionJacksonMapper.java:20— ActionJacksonMapper.parse has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (9 pts), boolean chains 5, loops 2 (4 pts) (nesting depth added 3). 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.
WezTerminalType.getActiveSocket (cognitive 17) app/src/main/java/io/xpipe/app/terminal/WezTerminalType.java:98— WezTerminalType.getActiveSocket has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (10 pts), error handling 3 (5 pts), boolean chains 1, loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DataStoreEntry.refreshStore (cognitive 17) app/src/main/java/io/xpipe/app/storage/DataStoreEntry.java:767— DataStoreEntry.refreshStore has cognitive complexity 17 (threshold 15). Drivers by points: if/else 10 (13 pts), boolean chains 2, error handling 2 (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.
DataStorage.updateEntry (cognitive 17) app/src/main/java/io/xpipe/app/storage/DataStorage.java:388— DataStorage.updateEntry has cognitive complexity 17 (threshold 15). Drivers by points: if/else 11 (14 pts), boolean chains 2, loops 1 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
MicrosoftRdpClient.launch (cognitive 17) app/src/main/java/io/xpipe/app/rdp/MicrosoftRdpClient.java:166— MicrosoftRdpClient.launch has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (8 pts), boolean chains 4, ternaries 2 (3 pts), loops 2 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
PasswordManagerTestComp.createSimple (cognitive 17) app/src/main/java/io/xpipe/app/pwman/PasswordManagerTestComp.java:65— PasswordManagerTestComp.createSimple has cognitive complexity 17 (threshold 15). Drivers by points: if/else 10, ternaries 2 (3 pts), boolean chains 2, error handling 2 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
LocalShell.reset (cognitive 17) app/src/main/java/io/xpipe/app/process/LocalShell.java:60— LocalShell.reset has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (11 pts), error handling 2 (6 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AppPrefs.save (cognitive 17) app/src/main/java/io/xpipe/app/prefs/AppPrefs.java:1033— AppPrefs.save has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (10 pts), loops 2 (4 pts), error handling 1 (3 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
StoreFilterState.apply (cognitive 17) app/src/main/java/io/xpipe/app/hub/list/StoreFilterState.java:178— StoreFilterState.apply has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (14 pts), error handling 1 (2 pts), boolean chains 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
LeftSplitPaneComp.createBase (cognitive 17) app/src/main/java/io/xpipe/app/comp/base/LeftSplitPaneComp.java:32— LeftSplitPaneComp.createBase has cognitive complexity 17 (threshold 15). Drivers by points: if/else 11 (14 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.
InputGroupComp.createSimple (cognitive 17) app/src/main/java/io/xpipe/app/comp/base/InputGroupComp.java:35— InputGroupComp.createSimple has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (12 pts), loops 2 (4 pts), boolean chains 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ContextualFileReferenceChoiceComp.createSimple (cognitive 17) app/src/main/java/io/xpipe/app/comp/base/ContextualFileReferenceChoiceComp.java:73— ContextualFileReferenceChoiceComp.createSimple has cognitive complexity 17 (threshold 15). Drivers by points: if/else 10, ternaries 4, boolean chains 2, error handling 1. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
BrowserFileTransferOperation.handleChoice (cognitive 17) app/src/main/java/io/xpipe/app/browser/file/BrowserFileTransferOperation.java:97— BrowserFileTransferOperation.handleChoice has cognitive complexity 17 (threshold 15). Drivers by points: if/else 10 (17 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
BrowserFileListNameCell.updateItem (cognitive 17) app/src/main/java/io/xpipe/app/browser/file/BrowserFileListNameCell.java:195— BrowserFileListNameCell.updateItem has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 2 (7 pts), if/else 5 (6 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.
ActionUrls.parse (cognitive 17) app/src/main/java/io/xpipe/app/action/ActionUrls.java:68— ActionUrls.parse has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (10 pts), loops 2 (3 pts), boolean chains 2, ternaries 1 (2 pts) (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ScriptStoreSetup.controlWithScripts (cognitive 16) ext/base/src/main/java/io/xpipe/ext/base/script/ScriptStoreSetup.java:21— ScriptStoreSetup.controlWithScripts has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (10 pts), boolean chains 4, error handling 2 (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.
HttpHelper.checkOrThrow (cognitive 16) REDACTED:94— HttpHelper.checkOrThrow has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 3 (9 pts), if/else 6 (7 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
UpdateChangelogDialog.showIfNeeded (cognitive 16) app/src/main/java/io/xpipe/app/update/UpdateChangelogDialog.java:23— UpdateChangelogDialog.showIfNeeded has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (13 pts), boolean chains 3 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
WorkspaceManager.load (cognitive 16) app/src/main/java/io/xpipe/app/prefs/WorkspaceManager.java:38— WorkspaceManager.load has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (6 pts), ternaries 2 (5 pts), error handling 1 (2 pts), loops 1 (2 pts), boolean chains 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
UpdateCheckComp.createSimple (cognitive 16) app/src/main/java/io/xpipe/app/prefs/UpdateCheckComp.java:31— UpdateCheckComp.createSimple has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (11 pts), ternaries 2 (4 pts), boolean chains 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
IconsCategory.createOverview (cognitive 16) app/src/main/java/io/xpipe/app/prefs/IconsCategory.java:63— IconsCategory.createOverview has cognitive complexity 16 (threshold 15). Drivers by points: if/else 10 (11 pts), boolean chains 4, error handling 1 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
TrackEvent.toString (cognitive 16) app/src/main/java/io/xpipe/app/issue/TrackEvent.java:88— TrackEvent.toString has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 4 (10 pts), loops 2 (4 pts), if/else 2 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
StoreCreationDialog.createModalOverlay (cognitive 16) app/src/main/java/io/xpipe/app/hub/creation/StoreCreationDialog.java:204— StoreCreationDialog.createModalOverlay has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (7 pts), ternaries 6 (7 pts), boolean chains 2 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
AppModifiedStage.applyModes (cognitive 16) app/src/main/java/io/xpipe/app/core/window/AppModifiedStage.java:90— AppModifiedStage.applyModes has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 7, if/else 6 (7 pts), error handling 1, match/switch 1 (nesting depth added 1). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PrettyImageComp.createSimple (cognitive 16) app/src/main/java/io/xpipe/app/comp/base/PrettyImageComp.java:34— PrettyImageComp.createSimple has cognitive complexity 16 (threshold 15). Drivers by points: if/else 12, ternaries 2 (3 pts), boolean chains 1 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
ListBoxViewComp.isVisible (cognitive 16) app/src/main/java/io/xpipe/app/comp/base/ListBoxViewComp.java:243— ListBoxViewComp.isVisible has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (11 pts), boolean chains 5 (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.
ChoicePaneComp.createSimple (cognitive 16) app/src/main/java/io/xpipe/app/comp/base/ChoicePaneComp.java:41— ChoicePaneComp.createSimple has cognitive complexity 16 (threshold 15). Drivers by points: if/else 10 (12 pts), boolean chains 3, ternaries 1 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
BrowserTransferComp.createSimple (cognitive 16) app/src/main/java/io/xpipe/app/browser/file/BrowserTransferComp.java:38— BrowserTransferComp.createSimple has cognitive complexity 16 (threshold 15). Drivers by points: if/else 10 (12 pts), boolean chains 2, error handling 1, ternaries 1 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
BrowserFileTransferOperation.handleSingleOnSameFileSystem (cognitive 16) app/src/main/java/io/xpipe/app/browser/file/BrowserFileTransferOperation.java:220— BrowserFileTransferOperation.handleSingleOnSameFileSystem has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (11 pts), boolean chains 5 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
BrowserFileListFilterComp.createBase (cognitive 16) app/src/main/java/io/xpipe/app/browser/file/BrowserFileListFilterComp.java:32— BrowserFileListFilterComp.createBase has cognitive complexity 16 (threshold 15). Drivers by points: if/else 12 (14 pts), boolean chains 2 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
BrowserSessionTabsComp.setupTabEntries (cognitive 16) app/src/main/java/io/xpipe/app/browser/BrowserSessionTabsComp.java:149— BrowserSessionTabsComp.setupTabEntries has cognitive complexity 16 (threshold 15). Drivers by points: loops 5 (8 pts), if/else 5 (7 pts), boolean chains 1 (nesting depth added 5). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
StoreAddExchange.handle (cognitive 16) app/src/main/java/io/xpipe/app/beacon/api/StoreAddExchange.java:35— StoreAddExchange.handle has cognitive complexity 16 (threshold 15). Drivers by points: if/else 11 (13 pts), boolean chains 2, error handling 1 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D22 · Internal API Consistency· Inconsistent naming for validation/completeness checks across different domain types. While `checkComplete` is the dominant pattern, `ScriptTextSource`, `InPlace` (script), `Url`, and `SourceReference` also expose `checkAvailable() · ×1
Inconsistent naming for validation/completeness checks across different domain types. While `checkComplete` is the dominant pattern, `ScriptTextSource`, `InPlace` (script), `Url`, and `SourceReference` also expose `checkAvailable(): void`. This suggests a distinction between 'available' (e.g., file exists, URL reachable) and 'complete' (all fields filled), but the API surface exposes both on some types (e.g., `ScriptTextSource` has both) while others only have `checkComplete`. More critically, `IdentityValue` and its subtypes (`InPlace`, `Ref`) have granular checks like `checkCompletePassword()`, `checkCompleteSshIdentity()`, etc., whereas other stores use a single `checkComplete()`. This forces consumers to handle different validation strategies depending on the type. — Standardize on a single validation method per type, or clearly separate 'availability' (resource existence) from 'completeness' (data integrity) with consistent naming. If `checkAvailable` is distinct, it should be present on all relevant types or removed if redundant. For `IdentityValue`, consider a unified `validate()` or `checkComplete()` that internally delegates, rather than exposing multiple granular methods that leak implementation details. (signatures: AbstractHostStore.checkComplete(): void | IdentityStore.checkComplete(): void | ScriptStore.checkComplete(): void | ScriptCollectionSourceStore.checkComplete(): void | ScriptTextSource.checkComplete(): void | InPlace.checkComplete(): void | Url.checkComplete(): void | SourceReference.checkComplete(): void | AbstractServiceGroupStore.checkComplete(): void | AbstractServiceStore.checkComplete(): void | IdentityValue.checkComplete(): void | InPlace.checkComplete(): void | Ref.checkComplete(): void | ScriptCollectionSource.checkComplete(): void | Directory.checkComplete(): void | GitRepository.checkComplete(): void | DesktopApplicationStore.checkComplete(): void)
D22 · Internal API Consistency· Inconsistent factory method naming and return types in `IdentityValue`. Most `of` methods return `InPlace`, but `ofBreakout` and `ofCategory` return `IdentityValue`. This breaks the expectation that `of` methods are simple constructors/factories returning the same type. `ofBreakout` implies a transformation or unwrapping, while `ofCategory` implies a lookup or creation, yet they share the `of` prefix with simple constructors. · ×1
Inconsistent factory method naming and return types in `IdentityValue`. Most `of` methods return `InPlace`, but `ofBreakout` and `ofCategory` return `IdentityValue`. This breaks the expectation that `of` methods are simple constructors/factories returning the same type. `ofBreakout` implies a transformation or unwrapping, while `ofCategory` implies a lookup or creation, yet they share the `of` prefix with simple constructors. — Rename `ofBreakout` to `fromEntry` or `unwrap` (if it does that) and `ofCategory` to `fromCategory` or `createForCategory` to distinguish simple construction from complex lookups/transformations. Ensure all simple factory methods return the same concrete type or a consistent interface. (signatures: IdentityValue.of(identityStore: LocalIdentityStore): InPlace | IdentityValue.of(user: String): InPlace | IdentityValue.of(user: String, password: SecretRetrievalStrategy): InPlace | IdentityValue.of(user: String, password: SecretRetrievalStrategy, sshIdentity: SshIdentityStrategy): InPlace | IdentityValue.ofBreakout(e: DataStoreEntry): IdentityValue | IdentityValue.ofCategory(category: DataStoreCategory): IdentityValue)
Near-duplicate member pair (48 shared lines) app/src/main/java/io/xpipe/app/hub/entry/DenseStoreEntryComp.java:41— app/src/main/java/io/xpipe/app/hub/entry/DenseStoreEntryComp.java:41-156 | app/src/main/java/io/xpipe/app/hub/entry/StandardStoreEntryComp.java:43-161 — These two members are variants of one another: 48 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.
Near-duplicate member pair (32 shared lines) app/src/main/java/io/xpipe/app/browser/menu/impl/NewItemMenuProvider.java:54— app/src/main/java/io/xpipe/app/browser/menu/impl/NewItemMenuProvider.java:54-86 | app/src/main/java/io/xpipe/app/browser/menu/impl/NewItemMenuProvider.java:101-133 — These two members are variants of one another: 32 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 (6 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (6 members, 50+ identical tokens) app/src/main/java/io/xpipe/app/hub/entry/StoreEntryBadge.java:344— app/src/main/java/io/xpipe/app/hub/entry/StoreEntryBadge.java:344-353 | app/src/main/java/io/xpipe/app/hub/entry/StoreEntryBadge.java:355-364 | app/src/main/java/io/xpipe/app/hub/entry/StoreEntryBadge.java:366-375 | app/src/main/java/io/xpipe/app/hub/entry/StoreEntryBadge.java:377-386 | app/src/main/java/io/xpipe/app/hub/entry/StoreEntryBadge.java:388-397 | app/src/main/java/io/xpipe/app/hub/entry/StoreEntryBadge.java:399-408 — These 6 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 6 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 6 times.
D4 · Code Duplication· Members sharing a duplicated core (5 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (5 members, 50+ identical tokens) app/src/main/java/io/xpipe/app/update/ChocoUpdater.java:31— app/src/main/java/io/xpipe/app/update/ChocoUpdater.java:31-53 | app/src/main/java/io/xpipe/app/update/CommandUpdater.java:29-51 | app/src/main/java/io/xpipe/app/update/GitHubUpdater.java:27-49 | app/src/main/java/io/xpipe/app/update/PortableUpdater.java:23-38 | app/src/main/java/io/xpipe/app/update/WingetUpdater.java:33-55 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
D4 · Code Duplication· Members sharing a duplicated core (4 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (4 members, 50+ identical tokens) app/src/main/java/io/xpipe/app/terminal/WindowsTerminalType.java:192— app/src/main/java/io/xpipe/app/terminal/WindowsTerminalType.java:192-211 | app/src/main/java/io/xpipe/app/terminal/WindowsTerminalType.java:245-268 | app/src/main/java/io/xpipe/app/terminal/WindowsTerminalType.java:303-326 | app/src/main/java/io/xpipe/app/terminal/WindowsTerminalType.java:366-389 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Duplicated block (50 lines × 2) ext/system/src/main/java/io/xpipe/ext/system/incus/IncusCommandView.java:241— ext/system/src/main/java/io/xpipe/ext/system/incus/IncusCommandView.java:241-290 | ext/system/src/main/java/io/xpipe/ext/system/lxd/LxdCommandView.java:252-301 — before extracting anything, compare `ext/system/src/main/java/io/xpipe/ext/system/incus/IncusCommandView.java` and `ext/system/src/main/java/io/xpipe/ext/system/lxd/LxdCommandView.java` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 110 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 `ext/system/src/main/java/io/xpipe/ext/system/incus/IncusCommandView.java:241` 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 (34 lines × 2) ext/base/src/main/java/io/xpipe/ext/base/service/FixedServiceStoreProvider.java:50— ext/base/src/main/java/io/xpipe/ext/base/service/FixedServiceStoreProvider.java:50-83 | ext/base/src/main/java/io/xpipe/ext/base/service/MappedServiceStoreProvider.java:41-74 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (32 lines × 2) app/src/main/java/io/xpipe/app/process/ParentSystemAccess.java:69— app/src/main/java/io/xpipe/app/process/ParentSystemAccess.java:69-100 | app/src/main/java/io/xpipe/app/process/ParentSystemAccess.java:157-188 — 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 `app/src/main/java/io/xpipe/app/process/ParentSystemAccess.java:69` 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 (24–26 lines × 2) app/src/main/java/io/xpipe/app/terminal/ZellijTerminalMultiplexer.java:80— app/src/main/java/io/xpipe/app/terminal/ZellijTerminalMultiplexer.java:80-105 | app/src/main/java/io/xpipe/app/terminal/ZellijTerminalMultiplexer.java:166-189 — 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 `app/src/main/java/io/xpipe/app/terminal/ZellijTerminalMultiplexer.java:80` 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–24 lines × 2) app/src/main/java/io/xpipe/app/util/AskpassAlert.java:102— app/src/main/java/io/xpipe/app/util/AskpassAlert.java:102-125 | app/src/main/java/io/xpipe/app/util/AsktextAlert.java:47-69 — 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 `app/src/main/java/io/xpipe/app/util/AskpassAlert.java:102` 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 (22 lines × 3) app/src/main/java/io/xpipe/app/update/AppInstaller.java:201— app/src/main/java/io/xpipe/app/update/AppInstaller.java:201-222 | app/src/main/java/io/xpipe/app/update/AppInstaller.java:235-256 | app/src/main/java/io/xpipe/app/update/AppInstaller.java:269-290 — 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 `app/src/main/java/io/xpipe/app/update/AppInstaller.java: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 (21 lines × 2) app/src/main/java/io/xpipe/app/hub/entry/DenseStoreEntryComp.java:81— app/src/main/java/io/xpipe/app/hub/entry/DenseStoreEntryComp.java:81-101 | app/src/main/java/io/xpipe/app/hub/entry/StandardStoreEntryComp.java:99-119 — before extracting anything, compare `app/src/main/java/io/xpipe/app/hub/entry/DenseStoreEntryComp.java` and `app/src/main/java/io/xpipe/app/hub/entry/StandardStoreEntryComp.java` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 48 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (20 lines × 4) app/src/main/java/io/xpipe/app/update/ChocoUpdater.java:34— app/src/main/java/io/xpipe/app/update/ChocoUpdater.java:34-53 | app/src/main/java/io/xpipe/app/update/CommandUpdater.java:32-51 | app/src/main/java/io/xpipe/app/update/GitHubUpdater.java:30-49 | app/src/main/java/io/xpipe/app/update/WingetUpdater.java:36-55 — before extracting anything, compare `app/src/main/java/io/xpipe/app/update/ChocoUpdater.java` and `app/src/main/java/io/xpipe/app/update/WingetUpdater.java` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 45 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/io/xpipe/app/update/ChocoUpdater.java:34` 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 (19 lines × 2) app/src/main/java/io/xpipe/app/util/NativeWinWindowControl.java:85— app/src/main/java/io/xpipe/app/util/NativeWinWindowControl.java:85-103 | app/src/main/java/io/xpipe/app/util/NativeWinWindowControl.java:115-133 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/io/xpipe/app/util/NativeWinWindowControl.java:85` 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 (16–17 lines × 2) app/src/main/java/io/xpipe/app/comp/base/ContextualFileReferenceSync.java:40— app/src/main/java/io/xpipe/app/comp/base/ContextualFileReferenceSync.java:40-56 | app/src/main/java/io/xpipe/app/comp/base/ContextualFileReferenceSync.java:57-72 — 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 `app/src/main/java/io/xpipe/app/comp/base/ContextualFileReferenceSync.java:40` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (15–16 lines × 2) app/src/main/java/io/xpipe/app/terminal/TerminalLauncher.java:325— app/src/main/java/io/xpipe/app/terminal/TerminalLauncher.java:325-339 | app/src/main/java/io/xpipe/app/terminal/TerminalLauncher.java:350-365 — 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 `app/src/main/java/io/xpipe/app/terminal/TerminalLauncher.java: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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `app/src/main/java/io/xpipe/app/terminal/TerminalLauncher.java:324` calls `get`, `start` and `app/src/main/java/io/xpipe/app/terminal/TerminalLauncher.java:349` does not — after which the two agree again for 4 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 (15 lines × 4) app/src/main/java/io/xpipe/app/terminal/WindowsTerminalType.java:197— app/src/main/java/io/xpipe/app/terminal/WindowsTerminalType.java:197-211 | app/src/main/java/io/xpipe/app/terminal/WindowsTerminalType.java:254-268 | app/src/main/java/io/xpipe/app/terminal/WindowsTerminalType.java:312-326 | app/src/main/java/io/xpipe/app/terminal/WindowsTerminalType.java:375-389 — 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 `app/src/main/java/io/xpipe/app/terminal/WindowsTerminalType.java:197` 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 (14–15 lines × 3) app/src/main/java/io/xpipe/app/browser/menu/impl/NewItemMenuProvider.java:66— app/src/main/java/io/xpipe/app/browser/menu/impl/NewItemMenuProvider.java:66-79 | app/src/main/java/io/xpipe/app/browser/menu/impl/NewItemMenuProvider.java:113-126 | app/src/main/java/io/xpipe/app/browser/menu/impl/NewItemMenuProvider.java:164-178 — 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 `app/src/main/java/io/xpipe/app/browser/menu/impl/NewItemMenuProvider.java:66` 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 (14 lines × 3) app/src/main/java/io/xpipe/app/rdp/FreeRdpClient.java:34— app/src/main/java/io/xpipe/app/rdp/FreeRdpClient.java:34-47 | app/src/main/java/io/xpipe/app/rdp/RemminaRdpClient.java:29-42 | app/src/main/java/io/xpipe/app/vnc/RemminaVncClient.java:32-45 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 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 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/io/xpipe/app/rdp/FreeRdpClient.java:34` 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 (13–14 lines × 2) app/src/main/java/io/xpipe/app/terminal/KittyTerminalType.java:94— app/src/main/java/io/xpipe/app/terminal/KittyTerminalType.java:94-107 | app/src/main/java/io/xpipe/app/terminal/KittyTerminalType.java:115-127 — 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 `app/src/main/java/io/xpipe/app/terminal/KittyTerminalType.java:94` 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 (13 lines × 3) app/src/main/java/io/xpipe/app/update/ChocoUpdater.java:102— app/src/main/java/io/xpipe/app/update/ChocoUpdater.java:102-114 | app/src/main/java/io/xpipe/app/update/PortableUpdater.java:43-55 | app/src/main/java/io/xpipe/app/update/WingetUpdater.java:96-108 — before extracting anything, compare `app/src/main/java/io/xpipe/app/update/ChocoUpdater.java` and `app/src/main/java/io/xpipe/app/update/WingetUpdater.java` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 45 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/io/xpipe/app/update/ChocoUpdater.java:102` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (4–13 lines × 3) app/src/main/java/io/xpipe/app/beacon/mcp/McpTools.java:337— app/src/main/java/io/xpipe/app/beacon/mcp/McpTools.java:337-349 | app/src/main/java/io/xpipe/app/beacon/mcp/McpTools.java:375-378 | app/src/main/java/io/xpipe/app/beacon/mcp/McpTools.java:393-405 — 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 `app/src/main/java/io/xpipe/app/beacon/mcp/McpTools.java:337` 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 (12–13 lines × 2) app/src/main/java/io/xpipe/app/hub/creation/StoreCreationMenu.java:98— app/src/main/java/io/xpipe/app/hub/creation/StoreCreationMenu.java:98-109 | app/src/main/java/io/xpipe/app/hub/list/StoreEntryListComp.java:198-210 — 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 `app/src/main/java/io/xpipe/app/hub/creation/StoreCreationMenu.java:98` 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. 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 (12 lines × 5) app/src/main/java/io/xpipe/app/update/ChocoUpdater.java:32— app/src/main/java/io/xpipe/app/update/ChocoUpdater.java:32-43 | app/src/main/java/io/xpipe/app/update/CommandUpdater.java:30-41 | app/src/main/java/io/xpipe/app/update/GitHubUpdater.java:28-39 | app/src/main/java/io/xpipe/app/update/PortableUpdater.java:24-35 | app/src/main/java/io/xpipe/app/update/WingetUpdater.java:34-45 — before extracting anything, compare `app/src/main/java/io/xpipe/app/update/ChocoUpdater.java` and `app/src/main/java/io/xpipe/app/update/WingetUpdater.java` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 45 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/io/xpipe/app/update/ChocoUpdater.java:32` 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 (4–12 lines × 3) app/src/main/java/io/xpipe/app/hub/action/impl/ScanHubBatchProvider.java:42— app/src/main/java/io/xpipe/app/hub/action/impl/ScanHubBatchProvider.java:42-53 | ext/base/src/main/java/io/xpipe/ext/base/identity/IdentityApplyHubLeafProvider.java:37-48 | ext/base/src/main/java/io/xpipe/ext/base/script/RunScriptActionProviderMenu.java:40-43 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 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 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/io/xpipe/app/hub/action/impl/ScanHubBatchProvider.java:42` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `o` to `DataStoreEntryRef<ShellStore>` in one and `DataStoreEntryRef<IdentityStore>` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (11–12 lines × 2) app/src/main/java/io/xpipe/app/rdp/RemoteDesktopAppRdpClient.java:25— app/src/main/java/io/xpipe/app/rdp/RemoteDesktopAppRdpClient.java:25-36 | app/src/main/java/io/xpipe/app/rdp/WindowsAppRdpClient.java:50-60 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/io/xpipe/app/rdp/RemoteDesktopAppRdpClient.java:25` 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 (10–11 lines × 3) app/src/main/java/io/xpipe/app/rdp/DevolutionsRdpClient.java:34— app/src/main/java/io/xpipe/app/rdp/DevolutionsRdpClient.java:34-43 | app/src/main/java/io/xpipe/app/terminal/MobaXTermTerminalType.java:70-79 | app/src/main/java/io/xpipe/app/terminal/XShellTerminalType.java:67-77 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 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 3 times. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (9–11 lines × 2) app/src/main/java/io/xpipe/app/storage/DataStorage.java:586— app/src/main/java/io/xpipe/app/storage/DataStorage.java:586-594 | app/src/main/java/io/xpipe/app/storage/DataStorage.java:640-650 — 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 `app/src/main/java/io/xpipe/app/storage/DataStorage.java:586` 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 (10 lines × 3) app/src/main/java/io/xpipe/app/browser/menu/impl/ChgrpMenuProvider.java:159— app/src/main/java/io/xpipe/app/browser/menu/impl/ChgrpMenuProvider.java:159-168 | app/src/main/java/io/xpipe/app/browser/menu/impl/ChmodMenuProvider.java:151-160 | app/src/main/java/io/xpipe/app/browser/menu/impl/ChownMenuProvider.java:158-167 — before extracting anything, compare `app/src/main/java/io/xpipe/app/browser/menu/impl/ChgrpMenuProvider.java` and `app/src/main/java/io/xpipe/app/browser/menu/impl/ChownMenuProvider.java` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 32 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/io/xpipe/app/browser/menu/impl/ChgrpMenuProvider.java:159` 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 (8–10 lines × 3) app/src/main/java/io/xpipe/app/browser/BrowserSessionTabsComp.java:375— app/src/main/java/io/xpipe/app/browser/BrowserSessionTabsComp.java:375-384 | app/src/main/java/io/xpipe/app/browser/BrowserSessionTabsComp.java:386-395 | app/src/main/java/io/xpipe/app/browser/BrowserSessionTabsComp.java:396-403 — 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 `app/src/main/java/io/xpipe/app/browser/BrowserSessionTabsComp.java:375` 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 (9–10 lines × 2) ext/base/src/main/java/io/xpipe/ext/base/service/ServiceHelper.java:12— ext/base/src/main/java/io/xpipe/ext/base/service/ServiceHelper.java:12-21 | ext/base/src/main/java/io/xpipe/ext/base/service/ServiceHelper.java:31-39 — 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 `ext/base/src/main/java/io/xpipe/ext/base/service/ServiceHelper.java:12` 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 (9 lines × 8) app/src/main/java/io/xpipe/app/browser/menu/impl/ChgrpMenuProvider.java:157— app/src/main/java/io/xpipe/app/browser/menu/impl/ChgrpMenuProvider.java:157-165 | app/src/main/java/io/xpipe/app/browser/menu/impl/ChmodMenuProvider.java:149-157 | app/src/main/java/io/xpipe/app/browser/menu/impl/ChownMenuProvider.java:156-164 | app/src/main/java/io/xpipe/app/browser/menu/impl/GradleRunMenuProvider.java:70-78 | app/src/main/java/io/xpipe/app/browser/menu/impl/NewItemMenuProvider.java:56-64 | app/src/main/java/io/xpipe/app/browser/menu/impl/NewItemMenuProvider.java:103-111 | app/src/main/java/io/xpipe/app/browser/menu/impl/compress/CompressMenuProvider.java:114-122 | app/src/main/java/io/xpipe/app/prefs/IconsCategory.java:88-96 — before extracting anything, compare `app/src/main/java/io/xpipe/app/browser/menu/impl/ChgrpMenuProvider.java` and `app/src/main/java/io/xpipe/app/browser/menu/impl/ChownMenuProvider.java` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 32 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/io/xpipe/app/browser/menu/impl/ChgrpMenuProvider.java: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.
Duplicated block (9 lines × 6) app/src/main/java/io/xpipe/app/hub/entry/StoreEntryBadge.java:345— app/src/main/java/io/xpipe/app/hub/entry/StoreEntryBadge.java:345-353 | app/src/main/java/io/xpipe/app/hub/entry/StoreEntryBadge.java:356-364 | app/src/main/java/io/xpipe/app/hub/entry/StoreEntryBadge.java:367-375 | app/src/main/java/io/xpipe/app/hub/entry/StoreEntryBadge.java:378-386 | app/src/main/java/io/xpipe/app/hub/entry/StoreEntryBadge.java:389-397 | app/src/main/java/io/xpipe/app/hub/entry/StoreEntryBadge.java:400-408 — all 6 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (7–9 lines × 3) app/src/main/java/io/xpipe/app/browser/file/BrowserFileSelectionListComp.java:45— app/src/main/java/io/xpipe/app/browser/file/BrowserFileSelectionListComp.java:45-51 | app/src/main/java/io/xpipe/app/hub/category/StoreCategoryDragComp.java:30-38 | app/src/main/java/io/xpipe/app/hub/list/StoreSectionDragComp.java:66-72 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 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 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/io/xpipe/app/browser/file/BrowserFileSelectionListComp.java:45` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (8 lines × 5) app/src/main/java/io/xpipe/app/prefs/McpCategory.java:110— app/src/main/java/io/xpipe/app/prefs/McpCategory.java:110-117 | app/src/main/java/io/xpipe/app/prefs/McpCategory.java:119-126 | app/src/main/java/io/xpipe/app/prefs/McpCategory.java:128-135 | app/src/main/java/io/xpipe/app/prefs/McpCategory.java:137-144 | app/src/main/java/io/xpipe/app/prefs/McpCategory.java:145-152 — all 5 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. 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 before the matched lines, `app/src/main/java/io/xpipe/app/prefs/McpCategory.java:110` calls `setPrefRowCount` and `app/src/main/java/io/xpipe/app/prefs/McpCategory.java:145` 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.
Duplicated block (7–8 lines × 2) app/src/main/java/io/xpipe/app/storage/DataStoreCategory.java:114— app/src/main/java/io/xpipe/app/storage/DataStoreCategory.java:114-121 | app/src/main/java/io/xpipe/app/storage/DataStoreEntry.java:295-301 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (6–7 lines × 3) app/src/main/java/io/xpipe/app/beacon/mcp/AppMcpServer.java:110— app/src/main/java/io/xpipe/app/beacon/mcp/AppMcpServer.java:110-116 | app/src/main/java/io/xpipe/app/beacon/mcp/AppMcpServer.java:147-153 | app/src/main/java/io/xpipe/app/beacon/mcp/AppMcpServer.java:168-173 — 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 `app/src/main/java/io/xpipe/app/beacon/mcp/AppMcpServer.java:110` 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 (6–7 lines × 2) app/src/main/java/io/xpipe/app/process/ShellTemp.java:37— app/src/main/java/io/xpipe/app/process/ShellTemp.java:37-42 | app/src/main/java/io/xpipe/app/process/ShellTemp.java:55-61 — 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 `app/src/main/java/io/xpipe/app/process/ShellTemp.java:55` 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 (25 lines × 4) app/src/main/java/io/xpipe/app/platform/GlobalBooleanProperty.java:9— app/src/main/java/io/xpipe/app/platform/GlobalBooleanProperty.java:9-33 | app/src/main/java/io/xpipe/app/platform/GlobalDoubleProperty.java:9-33 | app/src/main/java/io/xpipe/app/platform/GlobalObjectProperty.java:9-33 | app/src/main/java/io/xpipe/app/platform/GlobalStringProperty.java:9-33 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 4 call sites, so a change lands once.
Duplicated block (6 lines × 4) app/src/main/java/io/xpipe/app/process/ShellStoreState.java:27— app/src/main/java/io/xpipe/app/process/ShellStoreState.java:27-32 | app/src/main/java/io/xpipe/app/store/ContainerStoreState.java:65-70 | app/src/main/java/io/xpipe/app/store/NetworkContainerStoreState.java:21-26 | ext/system/src/main/java/io/xpipe/ext/system/podman/PodmanContainerStoreState.java:23-28 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated predicate app/src/main/java/io/xpipe/app/browser/menu/impl/JavapMenuProvider.java:36— `!BrowserApplicationPathMenuProvider.super.isApplicable(model, entries) || !BrowserMenuLeafProvider.super.isApplicable(model, entries)` appears character-identically in 4 files — app/src/main/java/io/xpipe/app/browser/menu/impl/JavapMenuProvider.java, app/src/main/java/io/xpipe/app/browser/menu/impl/compress/BaseUntarMenuProvider.java, app/src/main/java/io/xpipe/app/browser/menu/impl/compress/BaseUnzipUnixMenuProvider.java, app/src/main/java/io/xpipe/app/browser/menu/impl/compress/GunzipUnixMenuProvider.java. 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 ext/system/src/main/java/io/xpipe/ext/system/incus/IncusCommandView.java:90— `(containerEntry.getProject().equals(project) || project == null && containerEntry.getProject().equals("default")) && containerEntry.getName(…` appears character-identically in 2 files — ext/system/src/main/java/io/xpipe/ext/system/incus/IncusCommandView.java, ext/system/src/main/java/io/xpipe/ext/system/lxd/LxdCommandView.java. 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 app/src/main/java/io/xpipe/app/hub/action/impl/ScanHubBatchProvider.java:47— `(systemState.getShellDialect() == null || systemState.getShellDialect().getDumbMode().supportsAnyPossibleInteraction()) && (systemState.getT…` appears character-identically in 3 files — app/src/main/java/io/xpipe/app/hub/action/impl/ScanHubBatchProvider.java, ext/base/src/main/java/io/xpipe/ext/base/identity/IdentityApplyHubLeafProvider.java, ext/base/src/main/java/io/xpipe/ext/base/script/RunScriptActionProviderMenu.java. 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 app/src/main/java/io/xpipe/app/hub/category/StoreCategoryWrapper.java:157— `AppOperationMode.isInShutdown() || StoreViewState.get() == null` appears character-identically in 2 files — app/src/main/java/io/xpipe/app/hub/category/StoreCategoryWrapper.java, app/src/main/java/io/xpipe/app/hub/entry/StoreEntryWrapper.java. 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 app/src/main/java/io/xpipe/app/comp/base/SideMenuBarComp.java:48— `AppOperationMode.isInStartup() || AppOperationMode.isInShutdown()` appears character-identically in 3 files — app/src/main/java/io/xpipe/app/comp/base/SideMenuBarComp.java, app/src/main/java/io/xpipe/app/hub/list/StoreViewState.java, app/src/main/java/io/xpipe/app/webtop/WebtopDisplayScale.java. 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 app/src/main/java/io/xpipe/app/core/AppFontSizes.java:131— `AppPrefs.get() != null && !AppPrefs.get().useSystemFont().getValue()` appears character-identically in 2 files — app/src/main/java/io/xpipe/app/core/AppFontSizes.java, app/src/main/java/io/xpipe/app/core/AppStyle.java. 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 app/src/main/java/io/xpipe/app/core/AppTrayIcon.java:53— `DataStorage.get() != null && DataStorage.get().syncEnabled()` appears character-identically in 2 files — app/src/main/java/io/xpipe/app/core/AppTrayIcon.java, app/src/main/java/io/xpipe/app/core/window/AppMainWindow.java. 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 ext/base/src/main/java/io/xpipe/ext/base/identity/MultiIdentityStoreProvider.java:158— `DataStorageAccessHandler.getInstance().isAccessRestricted() && DataStorageAccessHandler.getInstance().getType() == DataStorageAccessType.ROL…` appears character-identically in 2 files — ext/base/src/main/java/io/xpipe/ext/base/identity/MultiIdentityStoreProvider.java, ext/base/src/main/java/io/xpipe/ext/base/identity/SyncedIdentityStoreProvider.java. 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 app/src/main/java/io/xpipe/app/comp/base/TextAreaComp.java:55— `Objects.equals(text.getText(), n) || (n == null && text.getText().isEmpty())` appears character-identically in 2 files — app/src/main/java/io/xpipe/app/comp/base/TextAreaComp.java, app/src/main/java/io/xpipe/app/comp/base/TextFieldComp.java. 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 app/src/main/java/io/xpipe/app/browser/BrowserFullSessionComp.java:81— `StoreViewState.get() != null && StoreViewState.get().isInitialized()` appears character-identically in 4 files — app/src/main/java/io/xpipe/app/browser/BrowserFullSessionComp.java, app/src/main/java/io/xpipe/app/hub/list/StoreLayoutComp.java, app/src/main/java/io/xpipe/app/prefs/HttpProxyCategory.java, app/src/main/java/io/xpipe/app/prefs/TerminalCategory.java. 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 app/src/main/java/io/xpipe/app/browser/action/impl/ComputeDirectorySizesActionProvider.java:33— `entries.size() == 1 && entries.getFirst().getRawFileEntry().equals(model.getCurrentDirectory())` appears character-identically in 2 files — app/src/main/java/io/xpipe/app/browser/action/impl/ComputeDirectorySizesActionProvider.java, app/src/main/java/io/xpipe/app/browser/menu/impl/ComputeDirectorySizesMenuProvider.java. 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 app/src/main/java/io/xpipe/app/browser/menu/impl/PasteMenuProvider.java:29— `entries.size() == 1 && entries.getFirst().getRawFileEntry().getKind() == FileKind.DIRECTORY` appears character-identically in 2 files — app/src/main/java/io/xpipe/app/browser/menu/impl/PasteMenuProvider.java, app/src/main/java/io/xpipe/app/browser/menu/impl/compress/CompressMenuProvider.java. 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 app/src/main/java/io/xpipe/app/comp/base/ModalOverlayComp.java:131— `event.getCode() == KeyCode.ENTER || event.getCode() == KeyCode.SPACE` appears character-identically in 2 files — app/src/main/java/io/xpipe/app/comp/base/ModalOverlayComp.java, app/src/main/java/io/xpipe/app/hub/entry/StoreEntryInformationComp.java. 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 app/src/main/java/io/xpipe/app/issue/ErrorHandlerComp.java:168— `event.getCustomActions().size() > 0 || event.getLink() != null` appears character-identically in 2 files — app/src/main/java/io/xpipe/app/issue/ErrorHandlerComp.java, app/src/main/java/io/xpipe/app/issue/ErrorHandlerDialog.java. 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 app/src/main/java/io/xpipe/app/prefs/ExternalEditorType.java:610— `existing != null && existing.isAvailable()` appears character-identically in 4 files — app/src/main/java/io/xpipe/app/prefs/ExternalEditorType.java, app/src/main/java/io/xpipe/app/rdp/ExternalRdpClient.java, app/src/main/java/io/xpipe/app/spice/ExternalSpiceClient.java, app/src/main/java/io/xpipe/app/terminal/ExternalTerminalType.java. 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 ext/base/src/main/java/io/xpipe/ext/base/identity/LocalIdentityStore.java:68— `getPassword() == null || getPassword() instanceof SecretNoneStrategy` appears character-identically in 2 files — ext/base/src/main/java/io/xpipe/ext/base/identity/LocalIdentityStore.java, ext/base/src/main/java/io/xpipe/ext/base/identity/SyncedIdentityStore.java. 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 ext/base/src/main/java/io/xpipe/ext/base/identity/LocalIdentityStore.java:69— `getSshIdentity() == null || getSshIdentity() instanceof NoIdentityStrategy` appears character-identically in 2 files — ext/base/src/main/java/io/xpipe/ext/base/identity/LocalIdentityStore.java, ext/base/src/main/java/io/xpipe/ext/base/identity/SyncedIdentityStore.java. 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 ext/base/src/main/java/io/xpipe/ext/base/service/FixedServiceStoreProvider.java:63— `host.get() == null || !tunnelToLocalhost.get()` appears character-identically in 2 files — ext/base/src/main/java/io/xpipe/ext/base/service/FixedServiceStoreProvider.java, ext/base/src/main/java/io/xpipe/ext/base/service/MappedServiceStoreProvider.java. 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 ext/system/src/main/java/io/xpipe/ext/system/incus/IncusContainerStore.java:118— `identity != null && identity.unwrap().getPassword() != null` appears character-identically in 2 files — ext/system/src/main/java/io/xpipe/ext/system/incus/IncusContainerStore.java, ext/system/src/main/java/io/xpipe/ext/system/lxd/LxdContainerStore.java. 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 app/src/main/java/io/xpipe/app/browser/file/BrowserFileInput.java:56— `info.getUid() != null && info.getUid().equals(sc.view().getPasswdFile().getUidForUserIfPresent(sc.view().user()).orElse(null)) || info.getUs…` appears character-identically in 2 files — app/src/main/java/io/xpipe/app/browser/file/BrowserFileInput.java, app/src/main/java/io/xpipe/app/browser/file/BrowserFileOutput.java. 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 app/src/main/java/io/xpipe/app/util/ControllableWindowProcess.java:62— `lastBounds != null && !lastBounds.equals(bounds)` appears character-identically in 2 files — app/src/main/java/io/xpipe/app/util/ControllableWindowProcess.java, app/src/main/java/io/xpipe/app/util/ControllableWindowsProcess.java. 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 app/src/main/java/io/xpipe/app/hub/category/StoreCategoryComp.java:152— `p.developerMode().getValue() && p.developerShowOrderIndices().get()` appears character-identically in 2 files — app/src/main/java/io/xpipe/app/hub/category/StoreCategoryComp.java, app/src/main/java/io/xpipe/app/hub/entry/StoreEntryComp.java. 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 app/src/main/java/io/xpipe/app/util/GroupFile.java:33— `sc.getOsType() == OsType.WINDOWS || sc.getOsType() == OsType.MACOS` appears character-identically in 2 files — app/src/main/java/io/xpipe/app/util/GroupFile.java, app/src/main/java/io/xpipe/app/util/PasswdFile.java. 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 app/src/main/java/io/xpipe/app/terminal/OhMyPoshTerminalPrompt.java:165— `sc.getShellDialect() == ShellDialects.CMD && !ClinkHelper.checkIfInstalled(sc)` appears character-identically in 2 files — app/src/main/java/io/xpipe/app/terminal/OhMyPoshTerminalPrompt.java, app/src/main/java/io/xpipe/app/terminal/StarshipTerminalPrompt.java. 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 ext/system/src/main/java/io/xpipe/ext/system/incus/IncusContainerStore.java:113— `state.getOsName() != null && state.getOsName().toLowerCase().contains("alpine")` appears character-identically in 2 files — ext/system/src/main/java/io/xpipe/ext/system/incus/IncusContainerStore.java, ext/system/src/main/java/io/xpipe/ext/system/lxd/LxdContainerStore.java. 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.
Fat interface: DataStorageSyncHandler (20 abstract methods) app/src/main/java/io/xpipe/app/storage/DataStorageSyncHandler.java:8— `DataStorageSyncHandler` declares 20 abstract methods: `addDataFile`, `afterStorageLoad`, `afterStorageSave`, `beforeStorageSave`, `getDataFile`, `getDirectory`, `getSavedDataFiles`, `handleCategory`, `handleDeletion`, `handleEntry`, `hasExternalStoredCredentials`, `init`, `prepareGpgIfNeeded`, `pullManually`, `pushManually`, `refreshRemoteData`, `reset`, `retrieveSyncedData`, `supportsSync`, `validateConnection`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants 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: ShellDialect (69 abstract methods) app/src/main/java/io/xpipe/app/process/ShellDialect.java:15— `ShellDialect` declares 69 abstract methods: `addToPathVariableCommand`, `assembleCommand`, `assignMissingExitCode`, `changeTitleCommand`, `clearDisplayCommand`, `createFileExistsCommand`, `createScriptTextFileWriteCommand`, `createStreamFileWriteCommand`, `createTextFileWriteCommand`, `deleteFileOrDirectory`, `determineCharset`, `directoryExists`, `doesEchoInputByDefault`, `environmentVariable`, `evaluateExpression`, `executeCommandWithShell`, `executeRobustBootstrapOutputCommand`, `fileArgument`, `formatError`, `getAskpass`, `getCatchAllVariable`, `getDiscardAllOperator`, `getDiscardStdoutOperator`, `getDisplayName`, `getDumbMode`, `getEchoCommand`, `getExecutableName`, `getFileCopyCommand`, `getFileDeleteCommand`, `getFileMoveCommand`, `getFileReadCommand`, `getFileTouchCommand`, `getId`, `getInitFileName`, `getLaunchCommand`, `getMkdirsCommand`, `getNewLine`, `getOpenScriptCommand`, `getPauseCommand`, `getPrintExitCodeCommand`, and 29 more. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants 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: ShellControl (59 abstract methods) app/src/main/java/io/xpipe/app/process/ShellControl.java:23— `ShellControl` declares 59 abstract methods: `buildElevatedCommand`, `checkLicenseOrThrow`, `closeStdout`, `command`, `elevated`, `exitAndWait`, `getActiveReplacementBackgroundSession`, `getEffectiveSecurityPolicy`, `getElevationHandler`, `getExitUuids`, `getLocalSystemAccess`, `getLock`, `getOriginalShellDialect`, `getOsName`, `getOsType`, `getParentControl`, `getParentSystemAccess`, `getSourceStore`, `getSourceStoreId`, `getStderr`, `getStdin`, `getStdout`, `getSubTemporaryDirectory`, `getSudoCache`, `getSystemTemporaryDirectory`, `getTtyState`, `isExiting`, `isInactive`, `isInitializing`, `isInteractive`, `isLocal`, `isSubShellActive`, `onExit`, `onInit`, `onKill`, `onStartupFail`, `prepareIntermediateTerminalOpen`, `requireLicensedFeature`, `restart`, `setDumbOpen`, and 19 more. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. Those 59 declarations carry 58 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 58 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. 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: CommandControl (24 abstract methods) app/src/main/java/io/xpipe/app/process/CommandControl.java:13— `CommandControl` declares 24 abstract methods: `complex`, `discardOrThrow`, `elevated`, `getDisplayCommand`, `getExitCode`, `getParent`, `getTerminalCommand`, `noActivity`, `notComplex`, `readRawBytesOrThrow`, `readStdoutAndStderr`, `readStdoutIfPossible`, `readStdoutOrThrow`, `sensitive`, `setExitTimeout`, `setStartTimeout`, `start`, `startExternalStdin`, `startExternalStdout`, `waitFor`, `withCustomCharset`, `withErrorFormatter`, `withExceptionConverter`, `withWorkingDirectory`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants 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: FileSystem (47 abstract methods) app/src/main/java/io/xpipe/app/fs/FileSystem.java:19— `FileSystem` declares 47 abstract methods: `cd`, `chgrp`, `chmod`, `chown`, `copy`, `createTransferOptimizedFileSystem`, `delete`, `directoryAccessible`, `directoryExists`, `fileExists`, `getDirectorySize`, `getFileInfo`, `getFileSeparator`, `getFileSize`, `getIdentifier`, `getRawShellControl`, `getShell`, `getSuffix`, `getTerminalShellControl`, `hasAccurateProgress`, `isRunning`, `kill`, `listCommonDirectories`, `listFiles`, `listRoots`, `makeFileSystemCompatible`, `mkdirs`, `move`, `open`, `openInput`, `openOutput`, `pwd`, `readInstantIfPossible`, `reinitIfNeeded`, `requiresReinit`, `supportsChgrp`, `supportsChmod`, `supportsChown`, `supportsDirectorySizes`, `supportsLinkCreation`, and 7 more. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants 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.
Blanket warning suppression app/src/main/java/io/xpipe/app/util/AppJacksonModule.java:412— `@SuppressWarnings("all")` switches every compiler and analyser warning off for the whole declaration — hidden debt. Suppress the specific warning on the specific member, with a justification, instead.
Blanket warning suppression app/src/main/java/io/xpipe/app/util/AppJacksonModule.java:432— `@SuppressWarnings("all")` switches every compiler and analyser warning off for the whole declaration — hidden debt. Suppress the specific warning on the specific member, with a justification, instead.
Blanket warning suppression app/src/main/java/io/xpipe/app/util/AppJacksonModule.java:494— `@SuppressWarnings("all")` switches every compiler and analyser warning off for the whole declaration — hidden debt. Suppress the specific warning on the specific member, with a justification, instead.
Silent fallback default in catch app/src/main/java/io/xpipe/app/secret/EncryptedSecretValue.java:61— `getSecret` swallows every exception into `return new char[0]` — a data error becomes a silent behavior change with no trail. Log the failure or let it propagate. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment in the catch or in the Javadoc, and the row stops firing.
Silent fallback default in catch app/src/main/java/io/xpipe/app/secret/EncryptedSecretValue.java:47— `getSecretRaw` swallows every exception into `return new byte[0]` — a data error becomes a silent behavior change with no trail. Log the failure or let it propagate. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment in the catch or in the Javadoc, and the row stops firing.
No ADRs found — No ADRs found. No recognised ADR directory (`docs/adr/`, `docs/decisions/`, `adr/`, `docs/rfcs/`, an `ADR0001/` folder, or their siblings) exists anywhere in this tree. What was searched, so you can tell an empty log from a search that missed one: every directory under the tree (build output, dependencies and VCS metadata excepted), for a document that is either any non-index page inside a recognised ADR directory, whatever its name and however deeply nested (`docs/adr/use-postgres.md`, `docs/adr/2024/0001-x.md`); or a file anywhere whose name is ADR-shaped (`0001-use-postgres.md`, `adr-012-caching.md`); or, when neither turned anything up, a document carrying the decision-record signature (an "Architecture Decision Record" heading, or Status / Context / Decision / Consequences as section headings). A decision log that clears none of these — unnumbered files outside any recognised directory, without those headings — is not seen by this check and this row is then wrong. If that is your case, say so rather than renaming anything; otherwise, consider recording architectural decisions in `docs/adr/`.
D26 · Project Cohesion· Projects may be oversized for their cohesion · ×1
Projects may be oversized for their cohesion — 2 of 6 project(s) overshoot their size bounds, lowering Project Cohesion to 4.3/10. The most over is `app` (82533 LoC, 1215 module-visible types across 45 directories). Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
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.
P10 · Library API & versioning· Large public API surface · ×1
Large public API surface — 1172/1347 types (87%) declared in the published library are public. For a library, every public type is a stability contract — keep implementation types off the surface and expose only the intended API.
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) — this repository has no CI pipeline yet, so run it locally to clear the existing findings, then make it a step of the first workflow you add so a regression fails the build. What was searched, so you can tell an absence from a miss: the 0 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.
X5 · Nullable reference types· Java packages are not null-marked everywhere · ×1
Java packages are not null-marked everywhere — 0/55 of this repository's Java package directories are under a non-null default: a `package-info.java` declaring `@NullMarked` (JSpecify) or `@NonNullApi`, `@ParametersAreNonnullByDefault`, `@NonNullByDefault`, `@DefaultQualifier(NonNull.class)`; a `module-info.java` declaring `@NullMarked`; every type in it `@NullMarked`; or a build that runs NullAway with the package in `AnnotatedPackages`, or the Checker Framework's `NullnessChecker`. Elsewhere every reference admits null and no checker warns on the dereference that throws a `NullPointerException`.
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.
none (dependency manifest found, not scanned for vulnerabilities here)
—
none (dependency manifest found, not scanned for vulnerabilities here): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Gradle build (build.gradle/build.gradle.kts) — not scanned yet).
trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
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 29 file(s) — `app/src/main/java/io/xpipe/app/browser/action/impl/OpenFileNativeDetailsActionProvider.java`, `app/src/main/java/io/xpipe/app/browser/menu/impl/BrowseInNativeManagerMenuProvider.java`, `app/src/main/java/io/xpipe/app/browser/menu/impl/EditFileMenuProvider.java`, `app/src/main/java/io/xpipe/app/browser/menu/impl/GradleRunMenuProvider.java`, `app/src/main/java/io/xpipe/app/browser/menu/impl/OpenFileDefaultMenuProvider.java`, … (+24 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.
provenance: not applicable — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
none (dependency manifest found, not scanned for vulnerabilities here)
—
none (dependency manifest found, not scanned for vulnerabilities here): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Gradle build (build.gradle/build.gradle.kts) — not scanned yet).
0
—
Run 01a16cbc-baa1-7c44-8929-c3963b881bf8 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 9 · Warnings: 546 · Recommendations: 43 — Appendix A · all findings · full markdown report.
Generated by Watchdog — deterministic code-health analysis. 24-10-2026 @ 07:07 UTC.
Downloadable artifacts
Machine-readable and reproducible from this commit + frozen rubric — drop them straight into a contract appendix, a CRA dossier, or a downstream SCA / VEX tool.