Public report of sndnv/stasis, published 21 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, 21 October 2026, 13:41 UTC · Survey ID cd_db891a9688e8473bbeffc692565b0849
sndnv/stasis
Measured 21 October 2026, 13:37 UTC, at code version 2413bec
CAI scoreAdequate
CriticalWeakAdequateStrongExemplary
No change since the last survey
The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.
A medium codebase: 84,004 lines of product code in 13 projects, tests not counted · Estimated rebuild effort: about 1.3 person-years · Weakest lens: Accessibility, 40
Findings by how serious they are
39 critical424 serious50 minor
12 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
21 October 2026, 13:37 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 ▸
69of 73 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.
497of 513 findings point to an exact file and line, so you can open each one in the code. The other 16 concern the repository as a whole, such as missing documentation.
73dimensions across 8 lenses, read from 84,004 lines of product code in 13 projects.
sndnv/stasis scores 52 out of 100 and is rated Adequate, while seven of its eight lenses score higher still: Architecture at 86, Domain Modelling at 74, Security and Compliance at 66, Maturity at 60 and Production Readiness at 56, all rated Adequate, and Code Health and Performance at 78, both rated Strong.
The score is lower than those seven because the weakest lens counts most, and here that is Accessibility, which scores 40 and is rated Weak. Its weakest dimension is A11y enforcement, which scores 4 out of 10. The first actions are to enforce accessibility in the toolchain your project already uses: assert accessibility in your UI test suite with your toolkit's own matcher (Flutter `meetsGuideline`, Espresso `AccessibilityChecks`, XCTest `performAccessibilityAudit`), then gate that test in CI so a regression blocks the merge and to resolve the 1 No ADRs found finding(s) in ADR Quality, and if Accessibility rose to 70, the score would rise from 52 to about 61.
39 findings are critical: 15 in IaC & Container Security, 12 in REDACTED Scanning, eight in Secrets (history) and four in Static Analysis (SAST).
Watchdog couldn't measure 12 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 84,004 lines, which would take an estimated 1.3 person-years, around €190,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: 7 findings
These 7 critical or serious findings were in the previous survey, on 6 October 2026, and are gone from this one.
Code Duplication · Edited copy of a member (26 corresponding lines) client-cli/client_cli/api/__init__.py
Code Duplication · Members sharing a duplicated core (5 members, 50+ identical tokens) client-cli/client_cli/cli/maintenance.py
Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) client/src/main/scala/stasis/client/ops/Metrics.scala
Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) client/src/main/scala/stasis/client/service/components/Secrets.scala
Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) client-android/lib/src/main/kotlin/stasis/client_android/lib/ops/scheduling/DefaultOperationExecutor.kt
Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) identity-ui/deployment/production/build.py
Supply-chain Provenance & Signing REDACTED
Rebuild cost: about €190,000 · Estimate
Cost to rebuild
€64,000 to €320,000, for 1,075 to 3,409 hours of work, about 1.3 person-years for 1 to 3 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 52. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
Size
Medium: 84,004 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
Enforce accessibility in the toolchain your project already uses: assert accessibility in your UI test suite with your toolkit's own matcher (Flutter `meetsGuideline`, Espresso `AccessibilityChecks`, XCTest `performAccessibilityAudit`), then gate that test in CI so a regression blocks the merge.
Raises the score by about 10 points · Medium effort · A11y enforcement
2
Resolve the 1 No ADRs found finding(s) in ADR Quality.
Raises the score by about 2 points · Low effort · ADR Quality
3
Resolve the 12 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (7), REDACTED (2), REDACTED (2).
Raises the score by about 3 points · Medium effort · REDACTED Scanning
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 €190,000 to build again, about 1.3 person-years of work. Its weakest lens is Accessibility, at 40 (Weak). Accessibility is about whether the interface is built so that everyone can use it, including people who can't see the screen or can't use a mouse. Because the weakest lens counts most in the score, work on Accessibility also moves the score most.
Based on: the rebuild estimate · the Accessibility grade · how much each lens counts
What to do: Start with the Accessibility actions in Top priorities.
If you do one thing first · First action
Enforce accessibility in the toolchain your project already uses: assert accessibility in your UI test suite with your toolkit's own matcher (Flutter `meetsGuideline`, Espresso `AccessibilityChecks`, XCTest `performAccessibilityAudit`), then gate that test in CI so a regression blocks the merge. Of all the actions in this report, it raises the score most for the work it takes: about 10 points for medium effort. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
Architecture — module dependency graph
Project dependencies, layered top-to-bottom; arrows show direction. Any dashed red edge points upward or sideways — a layering smell or cycle. A clean layered graph has none.
Architecture: which parts of the code depend on which
The code is divided into modules, groups of code that each handle one part of the product, and a module depends on another when it uses code from it. The table lists the modules both down the side and across the top, in an order where each module should only use modules listed above it. A number in a cell means the module on that row uses the module in that column, and it counts the pairs of building blocks (types) that connect them. The one thing to look for is a mark above the diagonal line. It means two or more modules use each other in a loop (a dependency cycle), so none of them can be changed, tested or released on its own.
773 modules, with 1442 dependencies between them. 21 loops run through 93 of the modules, marked above the diagonal.
The table shows the 40 modules with the most connections; 733 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.
client.ops.backup uses client.analysis.PlatformMetadata, so a change to client.analysis.PlatformMetadata can break client.ops.backup, while a change to client.ops.backup can't break client.analysis.PlatformMetadata.
Position
Below the diagonal: client.ops.backup uses a module listed above it, which is the healthy direction.
15→34 client.ops.backup uses client.api.clientspart of a loop✕
Connections
1 pair of types, where a type in client.ops.backup uses a type in client.api.clients.
client.ops.backup uses client.api.clients, so a change to client.api.clients can break client.ops.backup, while a change to client.ops.backup can't break client.api.clients.
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.
client_android.lib.security uses client_android.lib.encryption.secrets, so a change to client_android.lib.encryption.secrets can break client_android.lib.security, while a change to client_android.lib.security can't break client_android.lib.encryption.secrets.
Position
Below the diagonal: client_android.lib.security uses a module listed above it, which is the healthy direction.
client_android.lib.security uses client_android.lib.utils, so a change to client_android.lib.utils can break client_android.lib.security, while a change to client_android.lib.security can't break client_android.lib.utils.
Position
Below the diagonal: client_android.lib.security uses a module listed above it, which is the healthy direction.
16→21 client_android.lib.security uses client_android.lib.api.clientspart of a loop✕
Connections
2 pairs of types, where a type in client_android.lib.security uses a type in client_android.lib.api.clients.
client_android.lib.security uses client_android.lib.api.clients, so a change to client_android.lib.api.clients can break client_android.lib.security, while a change to client_android.lib.security can't break client_android.lib.api.clients.
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.
core.persistence.Metrics uses core.packaging, so a change to core.packaging can break core.persistence.Metrics, while a change to core.persistence.Metrics can't break core.packaging.
Position
Below the diagonal: core.persistence.Metrics uses a module listed above it, which is the healthy direction.
identity.model.GrantType uses identity.model, so a change to identity.model can break identity.model.GrantType, while a change to identity.model.GrantType can't break identity.model.
Position
Below the diagonal: identity.model.GrantType uses a module listed above it, which is the healthy direction.
server.security uses shared.security, so a change to shared.security can break server.security, while a change to server.security can't break shared.security.
Position
Below the diagonal: server.security uses a module listed above it, which is the healthy direction.
client.ops.backup.Backup uses client.api.http.routes, so a change to client.api.http.routes can break client.ops.backup.Backup, while a change to client.ops.backup.Backup can't break client.api.http.routes.
Position
Below the diagonal: client.ops.backup.Backup uses a module listed above it, which is the healthy direction.
client.ops.backup.Backup uses client.encryption.secrets, so a change to client.encryption.secrets can break client.ops.backup.Backup, while a change to client.ops.backup.Backup can't break client.encryption.secrets.
Position
Below the diagonal: client.ops.backup.Backup uses a module listed above it, which is the healthy direction.
client.ops.backup.Backup uses shared.model.datasets, so a change to shared.model.datasets can break client.ops.backup.Backup, while a change to client.ops.backup.Backup can't break shared.model.datasets.
Position
Below the diagonal: client.ops.backup.Backup uses a module listed above it, which is the healthy direction.
client.ops.backup.Backup uses client.ops.backup, so a change to client.ops.backup can break client.ops.backup.Backup, while a change to client.ops.backup.Backup can't break client.ops.backup.
Position
Below the diagonal: client.ops.backup.Backup uses a module listed above it, which is the healthy direction.
client_android.lib.api.clients uses client_android.lib.model.server.datasets, so a change to client_android.lib.model.server.datasets can break client_android.lib.api.clients, while a change to client_android.lib.api.clients can't break client_android.lib.model.server.datasets.
Position
Below the diagonal: client_android.lib.api.clients uses a module listed above it, which is the healthy direction.
client_android.lib.api.clients uses client_android.lib.utils, so a change to client_android.lib.utils can break client_android.lib.api.clients, while a change to client_android.lib.api.clients can't break client_android.lib.utils.
Position
Below the diagonal: client_android.lib.api.clients uses a module listed above it, which is the healthy direction.
client_android.lib.api.clients uses client_android.lib.security, so a change to client_android.lib.security can break client_android.lib.api.clients, while a change to client_android.lib.api.clients can't break client_android.lib.security.
Position
Below the diagonal: client_android.lib.api.clients uses a module listed above it, which is the healthy direction.
21→24 client_android.lib.api.clients uses client_android.lib.modelpart of a loop✕
Connections
3 pairs of types, where a type in client_android.lib.api.clients uses a type in client_android.lib.model.
client_android.lib.api.clients uses client_android.lib.model, so a change to client_android.lib.model can break client_android.lib.api.clients, while a change to client_android.lib.api.clients can't break client_android.lib.model.
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.
identity.api uses core.discovery.ServiceApiEndpoint, so a change to core.discovery.ServiceApiEndpoint can break identity.api, while a change to identity.api can't break core.discovery.ServiceApiEndpoint.
Position
Below the diagonal: identity.api uses a module listed above it, which is the healthy direction.
identity.api uses identity.model.GrantType, so a change to identity.model.GrantType can break identity.api, while a change to identity.api can't break identity.model.GrantType.
Position
Below the diagonal: identity.api uses a module listed above it, which is the healthy direction.
identity.api.oauth.directives uses client.api.clients.CachedServerApiEndpointClient, so a change to client.api.clients.CachedServerApiEndpointClient can break identity.api.oauth.directives, while a change to identity.api.oauth.directives can't break client.api.clients.CachedServerApiEndpointClient.
Position
Below the diagonal: identity.api.oauth.directives uses a module listed above it, which is the healthy direction.
identity.api.oauth.directives uses core.discovery.ServiceApiEndpoint, so a change to core.discovery.ServiceApiEndpoint can break identity.api.oauth.directives, while a change to identity.api.oauth.directives can't break core.discovery.ServiceApiEndpoint.
Position
Below the diagonal: identity.api.oauth.directives uses a module listed above it, which is the healthy direction.
identity.api.oauth.directives uses identity.model, so a change to identity.model can break identity.api.oauth.directives, while a change to identity.api.oauth.directives can't break identity.model.
Position
Below the diagonal: identity.api.oauth.directives uses a module listed above it, which is the healthy direction.
identity.api.oauth.directives uses client.ops.backup, so a change to client.ops.backup can break identity.api.oauth.directives, while a change to identity.api.oauth.directives can't break client.ops.backup.
Position
Below the diagonal: identity.api.oauth.directives uses a module listed above it, which is the healthy direction.
identity.api.oauth.directives uses identity.model.GrantType, so a change to identity.model.GrantType can break identity.api.oauth.directives, while a change to identity.api.oauth.directives can't break identity.model.GrantType.
Position
Below the diagonal: identity.api.oauth.directives uses a module listed above it, which is the healthy direction.
client_android.lib.model uses client_android.lib.api.clients, so a change to client_android.lib.api.clients can break client_android.lib.model, while a change to client_android.lib.model can't break client_android.lib.api.clients.
Position
Below the diagonal: client_android.lib.model uses a module listed above it, which is the healthy direction.
client_android.lib.ops.recovery uses client_android.lib.api.clients, so a change to client_android.lib.api.clients can break client_android.lib.ops.recovery, while a change to client_android.lib.ops.recovery can't break client_android.lib.api.clients.
Position
Below the diagonal: client_android.lib.ops.recovery uses a module listed above it, which is the healthy direction.
core.routing uses client.ops.backup.Backup, so a change to client.ops.backup.Backup can break core.routing, while a change to core.routing can't break client.ops.backup.Backup.
Position
Below the diagonal: core.routing uses a module listed above it, which is the healthy direction.
server.service uses client.api.clients.CachedServerApiEndpointClient, so a change to client.api.clients.CachedServerApiEndpointClient can break server.service, while a change to server.service can't break client.api.clients.CachedServerApiEndpointClient.
Position
Below the diagonal: server.service uses a module listed above it, which is the healthy direction.
server.service uses core.persistence.Metrics, so a change to core.persistence.Metrics can break server.service, while a change to server.service can't break core.persistence.Metrics.
Position
Below the diagonal: server.service uses a module listed above it, which is the healthy direction.
server.service uses server.security, so a change to server.security can break server.service, while a change to server.service can't break server.security.
Position
Below the diagonal: server.service uses a module listed above it, which is the healthy direction.
server.service uses client.ops.backup.Backup, so a change to client.ops.backup.Backup can break server.service, while a change to server.service can't break client.ops.backup.Backup.
Position
Below the diagonal: server.service uses a module listed above it, which is the healthy direction.
shared.model.devices uses client.ops.backup.Backup, so a change to client.ops.backup.Backup can break shared.model.devices, while a change to shared.model.devices can't break client.ops.backup.Backup.
Position
Below the diagonal: shared.model.devices uses a module listed above it, which is the healthy direction.
client_android.api.clients uses client_android.lib.model.server.datasets, so a change to client_android.lib.model.server.datasets can break client_android.api.clients, while a change to client_android.api.clients can't break client_android.lib.model.server.datasets.
Position
Below the diagonal: client_android.api.clients uses a module listed above it, which is the healthy direction.
client_android.api.clients uses client_android.lib.utils, so a change to client_android.lib.utils can break client_android.api.clients, while a change to client_android.api.clients can't break client_android.lib.utils.
Position
Below the diagonal: client_android.api.clients uses a module listed above it, which is the healthy direction.
client_android.api.clients uses client_android.lib.security, so a change to client_android.lib.security can break client_android.api.clients, while a change to client_android.api.clients can't break client_android.lib.security.
Position
Below the diagonal: client_android.api.clients uses a module listed above it, which is the healthy direction.
client_android.api.clients uses client_android.lib.api.clients, so a change to client_android.lib.api.clients can break client_android.api.clients, while a change to client_android.api.clients can't break client_android.lib.api.clients.
Position
Below the diagonal: client_android.api.clients uses a module listed above it, which is the healthy direction.
client_android.api.clients uses client_android.lib.model, so a change to client_android.lib.model can break client_android.api.clients, while a change to client_android.api.clients can't break client_android.lib.model.
Position
Below the diagonal: client_android.api.clients uses a module listed above it, which is the healthy direction.
client_android.lib.ops.scheduling uses client_android.lib.collection.rules, so a change to client_android.lib.collection.rules can break client_android.lib.ops.scheduling, while a change to client_android.lib.ops.scheduling can't break client_android.lib.collection.rules.
Position
Below the diagonal: client_android.lib.ops.scheduling uses a module listed above it, which is the healthy direction.
client_android.lib.ops.scheduling uses client_android.lib.encryption.secrets, so a change to client_android.lib.encryption.secrets can break client_android.lib.ops.scheduling, while a change to client_android.lib.ops.scheduling can't break client_android.lib.encryption.secrets.
Position
Below the diagonal: client_android.lib.ops.scheduling uses a module listed above it, which is the healthy direction.
client_android.lib.ops.scheduling uses client_android.lib.ops.recovery, so a change to client_android.lib.ops.recovery can break client_android.lib.ops.scheduling, while a change to client_android.lib.ops.scheduling can't break client_android.lib.ops.recovery.
Position
Below the diagonal: client_android.lib.ops.scheduling uses a module listed above it, which is the healthy direction.
client_android.lib.tracking.state uses client_android.lib.utils, so a change to client_android.lib.utils can break client_android.lib.tracking.state, while a change to client_android.lib.tracking.state can't break client_android.lib.utils.
Position
Below the diagonal: client_android.lib.tracking.state uses a module listed above it, which is the healthy direction.
client_android.lib.tracking.state uses client_android.lib.model, so a change to client_android.lib.model can break client_android.lib.tracking.state, while a change to client_android.lib.tracking.state can't break client_android.lib.model.
Position
Below the diagonal: client_android.lib.tracking.state uses a module listed above it, which is the healthy direction.
core.api uses client.api.clients.CachedServerApiEndpointClient, so a change to client.api.clients.CachedServerApiEndpointClient can break core.api, while a change to core.api can't break client.api.clients.CachedServerApiEndpointClient.
Position
Below the diagonal: core.api uses a module listed above it, which is the healthy direction.
core.api uses core.discovery.ServiceApiEndpoint, so a change to core.discovery.ServiceApiEndpoint can break core.api, while a change to core.api can't break core.discovery.ServiceApiEndpoint.
Position
Below the diagonal: core.api uses a module listed above it, which is the healthy direction.
core.api uses client.ops.backup.Backup, so a change to client.ops.backup.Backup can break core.api, while a change to core.api can't break client.ops.backup.Backup.
Position
Below the diagonal: core.api uses a module listed above it, which is the healthy direction.
shared.api uses client.analysis.PlatformMetadata, so a change to client.analysis.PlatformMetadata can break shared.api, while a change to shared.api can't break client.analysis.PlatformMetadata.
Position
Below the diagonal: shared.api uses a module listed above it, which is the healthy direction.
shared.api uses client.api.http.routes, so a change to client.api.http.routes can break shared.api, while a change to shared.api can't break client.api.http.routes.
Position
Below the diagonal: shared.api uses a module listed above it, which is the healthy direction.
shared.api uses client.encryption.secrets, so a change to client.encryption.secrets can break shared.api, while a change to shared.api can't break client.encryption.secrets.
Position
Below the diagonal: shared.api uses a module listed above it, which is the healthy direction.
shared.api uses shared.model.datasets, so a change to shared.model.datasets can break shared.api, while a change to shared.api can't break shared.model.datasets.
Position
Below the diagonal: shared.api uses a module listed above it, which is the healthy direction.
shared.api uses client.ops.backup.Backup, so a change to client.ops.backup.Backup can break shared.api, while a change to shared.api can't break client.ops.backup.Backup.
Position
Below the diagonal: shared.api uses a module listed above it, which is the healthy direction.
shared.api uses shared.model.devices, so a change to shared.model.devices can break shared.api, while a change to shared.api can't break shared.model.devices.
Position
Below the diagonal: shared.api uses a module listed above it, which is the healthy direction.
client.api.clients uses client.api.clients.CachedServerApiEndpointClient, so a change to client.api.clients.CachedServerApiEndpointClient can break client.api.clients, while a change to client.api.clients can't break client.api.clients.CachedServerApiEndpointClient.
Position
Below the diagonal: client.api.clients uses a module listed above it, which is the healthy direction.
client.api.clients uses client.api.http.routes, so a change to client.api.http.routes can break client.api.clients, while a change to client.api.clients can't break client.api.http.routes.
Position
Below the diagonal: client.api.clients uses a module listed above it, which is the healthy direction.
client.api.clients uses core.packaging, so a change to core.packaging can break client.api.clients, while a change to client.api.clients can't break core.packaging.
Position
Below the diagonal: client.api.clients uses a module listed above it, which is the healthy direction.
client.api.clients uses shared.model.datasets, so a change to shared.model.datasets can break client.api.clients, while a change to client.api.clients can't break shared.model.datasets.
Position
Below the diagonal: client.api.clients uses a module listed above it, which is the healthy direction.
client.api.clients uses shared.model.devices, so a change to shared.model.devices can break client.api.clients, while a change to client.api.clients can't break shared.model.devices.
Position
Below the diagonal: client.api.clients uses a module listed above it, which is the healthy direction.
client_android.providers uses client_android.lib.utils, so a change to client_android.lib.utils can break client_android.providers, while a change to client_android.providers can't break client_android.lib.utils.
Position
Below the diagonal: client_android.providers uses a module listed above it, which is the healthy direction.
client_android.providers uses client_android.lib.security, so a change to client_android.lib.security can break client_android.providers, while a change to client_android.providers can't break client_android.lib.security.
Position
Below the diagonal: client_android.providers uses a module listed above it, which is the healthy direction.
client_android.providers uses client_android.lib.api.clients, so a change to client_android.lib.api.clients can break client_android.providers, while a change to client_android.providers can't break client_android.lib.api.clients.
Position
Below the diagonal: client_android.providers uses a module listed above it, which is the healthy direction.
client_android.providers uses client_android.lib.ops.scheduling, so a change to client_android.lib.ops.scheduling can break client_android.providers, while a change to client_android.providers can't break client_android.lib.ops.scheduling.
Position
Below the diagonal: client_android.providers uses a module listed above it, which is the healthy direction.
client.model uses client.api.clients, so a change to client.api.clients can break client.model, while a change to client.model can't break client.api.clients.
Position
Below the diagonal: client.model uses a module listed above it, which is the healthy direction.
client.service.components uses client.api.clients.CachedServerApiEndpointClient, so a change to client.api.clients.CachedServerApiEndpointClient can break client.service.components, while a change to client.service.components can't break client.api.clients.CachedServerApiEndpointClient.
Position
Below the diagonal: client.service.components uses a module listed above it, which is the healthy direction.
client.service.components uses client.encryption.secrets, so a change to client.encryption.secrets can break client.service.components, while a change to client.service.components can't break client.encryption.secrets.
Position
Below the diagonal: client.service.components uses a module listed above it, which is the healthy direction.
client.service.components uses client.api.clients, so a change to client.api.clients can break client.service.components, while a change to client.service.components can't break client.api.clients.
Position
Below the diagonal: client.service.components uses a module listed above it, which is the healthy direction.
client_android uses client_android.lib.model.server.datasets, so a change to client_android.lib.model.server.datasets can break client_android, while a change to client_android can't break client_android.lib.model.server.datasets.
Position
Below the diagonal: client_android uses a module listed above it, which is the healthy direction.
client_android uses client_android.lib.utils, so a change to client_android.lib.utils can break client_android, while a change to client_android can't break client_android.lib.utils.
Position
Below the diagonal: client_android uses a module listed above it, which is the healthy direction.
client_android uses client_android.lib.model, so a change to client_android.lib.model can break client_android, while a change to client_android can't break client_android.lib.model.
Position
Below the diagonal: client_android uses a module listed above it, which is the healthy direction.
client_android uses client_android.providers, so a change to client_android.providers can break client_android, while a change to client_android can't break client_android.providers.
Position
Below the diagonal: client_android uses a module listed above it, which is the healthy direction.
client_android.api uses client_android.lib.model.server.datasets, so a change to client_android.lib.model.server.datasets can break client_android.api, while a change to client_android.api can't break client_android.lib.model.server.datasets.
Position
Below the diagonal: client_android.api uses a module listed above it, which is the healthy direction.
client_android.api uses client_android.lib.utils, so a change to client_android.lib.utils can break client_android.api, while a change to client_android.api can't break client_android.lib.utils.
Position
Below the diagonal: client_android.api uses a module listed above it, which is the healthy direction.
client_android.api uses client_android.lib.model, so a change to client_android.lib.model can break client_android.api, while a change to client_android.api can't break client_android.lib.model.
Position
Below the diagonal: client_android.api uses a module listed above it, which is the healthy direction.
client_android.api uses client_android.providers, so a change to client_android.providers can break client_android.api, while a change to client_android.api can't break client_android.providers.
Position
Below the diagonal: client_android.api uses a module listed above it, which is the healthy direction.
client.api.http uses client.api.http.routes, so a change to client.api.http.routes can break client.api.http, while a change to client.api.http can't break client.api.http.routes.
Position
Below the diagonal: client.api.http uses a module listed above it, which is the healthy direction.
client.api.http uses client.ops.backup, so a change to client.ops.backup can break client.api.http, while a change to client.api.http can't break client.ops.backup.
Position
Below the diagonal: client.api.http uses a module listed above it, which is the healthy direction.
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
A02:2025 — Security Misconfiguration
49
High / Critical
A07:2025 — Authentication Failures
21
High / Critical
A05:2025 — Injection
4
High / Critical
A03:2025 — Software Supply Chain Failures
4
Medium
Roadmap
First, enforce accessibility standards by integrating platform-specific checks into the UI test suite and gating merges on CI. Second, immediately resolve all leaked secrets in configuration and source files, and wire static analysis tools into the CI pipeline to fail builds on regressions. Finally, address the lack of architectural documentation by creating an ADR folder and recording significant design decisions with their context and consequences.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Enforce accessibility in the toolchain your project already uses: assert accessibility in your UI test suite with your toolkit's own matcher (Flutter `meetsGuideline`, Espresso `AccessibilityChecks`, XCTest `performAccessibilityAudit`), then gate that test in CI so a regression blocks the merge.
Your ecosystem's static analyzer is declared as a dependency but is not wired into CI — run it as a required step on push/PR (e.g. `composer phpstan` / `mix sobelow` / `bundle exec brakeman` / the spotbugs Gradle task / `sbt scalafixAll --check` / `golangci-lint run` / `rebar3 lint`) so a regression fails the build instead of relying on someone running it locally.
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.
Reconcile the README with reality: deployment/dev/README.md names `docker-compose-no-auth-has.yml`, but no file or folder `docker-compose-no-auth-has.yml` exists; deployment/production/README.md names `.stasis.internal`, but no file or folder `.stasis.internal` exists.
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 — 39
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 — 424
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 — 50
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 12
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. 69 of 73 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 — 73 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, 497 of 513 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 READ here — but this repository measures it: a coverage step in CI (`codecov/codecov-action`) shows that coverage is collected and tracked in your own CI. The built-in collector has no runner for this ecosystem (.kt, .py, .dart, .scala), so the analyzer could not read the number — a gap in the analyzer's language coverage, not an unmeasured repo. Not scored. To have the real number read, produce a coverage report in a standard format (JaCoCo XML — `mvn jacoco:report` or the Gradle `jacocoTestReport` task, or `coverage run -m pytest` then `coverage xml`, or lcov — `flutter test --coverage` (or `dart test --coverage=coverage` then `dart run coverage:format_coverage --lcov`), or `addSbtPlugin("org.scoverage" % "sbt-scoverage" % "<version>")` in `project/plugins.sbt`, then `sbt clean coverage test coverageReport`) 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 — `mvn jacoco:report` or the Gradle `jacocoTestReport` task, or `coverage run -m pytest` then `coverage xml`, or lcov — `flutter test --coverage` (or `dart test --coverage=coverage` then `dart run coverage:format_coverage --lcov`), or `addSbtPlugin("org.scoverage" % "sbt-scoverage" % "<version>")` in `project/plugins.sbt`, then `sbt clean coverage test coverageReport`) 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 reliability NOT SCORED: this repository's production source includes .kt, .dart, and the built-in reliability runner cannot re-run the .dart test suite(s); the jvm executor ran against the .kt half and did not finish re-running within its tier budget — so reliability was not measured for the repository as a whole. The Scala (repository root, 418 test files): measured (0 flaky) suite(s) did re-run, and came back with 0 flaky across 1 measured tier(s) — but that is a figure for one half of the product, and we do not publish a partial one as if it were complete. This is OUR limitation, not a defect in the repo — test reliability is excluded from the score rather than counted. The half was driven by a runner we ship, so this is not a missing-runner gap.
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 — 3 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 — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares an sbt build (build.sbt), but the licence verdict published here was taken over its JVM dependencies. Nothing was read about its sbt dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
D14 License Compliance — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares a Dart pubspec.yaml, but the licence verdict published here was taken over its JVM dependencies. Nothing was read about its Dart dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
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 (2 contributor(s) across 662 commit(s) sampled, automation and bot accounts excluded). One of them holds 100% of the history; the other 1 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.
D22 Internal API Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is a COLLECTOR gap, not an environment fault: no published-package marker D22 reads admitted any project here, so this ecosystem's public API has no collector, and the remedy is to write one — no change to the scan image can close it.
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. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
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. `client-android/lib/src/main/kotlin/stasis/client_android/lib/utils/ConcatSource.kt` 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.
DM9 Scattered domain decisions — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Some of this repository's production types come from a frontend that does not bind comparison operands to the members they read, which arm one needs, and those types were not walked for this dimension. The counts above speak for the languages that declare it.
DM9 Scattered domain decisions — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The frontend declares that it computes whether a construction is produced or passed, yet 9 of 380 constructions arrived without the answer. Arm two skipped them; it did not clear them.
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 this repository's Kotlin, Python, Swift, c, cpp is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
IC1 Incompleteness & stubs — not measured this run — 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, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and this repository's Kotlin, Python, Swift, c, cpp is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
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.
D13 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
D19 Documentation Quality: Documentation quality 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.
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").
D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
AC7 A11y enforcement: Enforcement is scored from in-repo config/CI evidence only — an a11y gate enforced in external tooling with no in-repo trace can't be credited, and a configured linter is presence, not proof the rules actually run or block a merge.
AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
DM6 Domain ↔ infrastructure boundary: Infrastructure reached through a hand-rolled wrapper, a domain-named facade, reflection, or a string-keyed service locator resolves to a non-infra type and isn't seen; the body scan is symbol resolution over syntax, not full dataflow. A clean result means "no resolved infra reference in a domain body", not a proof of purity.
M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
P5 DR & Backup: Backup/restore and disaster-recovery readiness is judged from in-repo evidence — a config that exists is not a tested restore, so the absence of positive evidence is reported as "not evidenced", never scored as present.
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, D26, 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.
22 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was MainActivity.initNavigation at 48. A further 2 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being DefaultBackupTracker.updateState at 16 — they are counted neither in the figure above nor in this dimension's score. 2 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: client-android/app/src/main/java/stasis/client_android/activities/fragments/settings/PermissionsDialogFragment.kt (PermissionsListItemAdapter.getView at 16), client/src/main/scala/stasis/client/tracking/trackers/DefaultBackupTracker.scala (DefaultBackupTracker.updateState at 16). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
+ 17 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 22 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with MainActivity.initNavigation (cyclomatic 48), Secrets.apply (cyclomatic 37), Devices.routes (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 22 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.
Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d1_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How hard the code is for a person to follow, beyond raw branching.
Method: Cognitive complexity per method (Sonar-style nesting-penalized score), computed exhaustively over production code, excluding test projects. Deterministic.
+ 46 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 4 bodies over 60 down to 60 or less in Cognitive Complexity — start with Secrets.apply (cognitive 277), Secrets.apply (cognitive 201), Secrets.apply (cognitive 138). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 4 together lifts Cognitive Complexity from 4.9 to about 6.5/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes7.8 / 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 31 MethodTooLong finding(s) in God Classes — start with SettingsFragment.kt, client_bootstrap_form.dart, client_credentials_reset_form.dart. — One of this dimension's main actionable groups (31 warning-level).
Resolve the 6 TooManyMethods finding(s) in God Classes — start with default_api_client.dart, default_client_api.py, inactive_client_api.py. — One of this dimension's main actionable groups (6 warning-level).
Resolve the 1 ClassTooLong finding(s) in God Classes — start with SettingsFragment.kt. — One of this dimension's main actionable groups (1 warning-level).
Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Copy-pasted code that should be shared instead.
Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), density-scored per KLoC of production code. Deterministic.
232 duplicated block group(s) detected. A further 19 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted.
Members sharing a duplicated core (4 members, 50+ identical tokens) · ×8client/src/main/scala/stasis/client/ops/Metrics.scala:50
+ 109 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 14 Duplicated block (13 lines × 2) finding(s) in Code Duplication — start with DatasetDefinitionDetailsFragment.kt (3), DefaultCredentialsProvider.scala, HomeFragment.kt. — One of this dimension's main actionable groups (14 warning-level).
Resolve the 11 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with status.dart (2), DefaultBackupTracker.scala, Owners.scala. — One of this dimension's main actionable groups (11 warning-level).
Resolve the 11 Duplicated block (5 lines × 2) finding(s) in Code Duplication — start with Service.scala (3), default_client_api.dart (2), Devices.scala. — One of this dimension's main actionable groups (11 warning-level).
Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling8.8 / 10Strong✓ Tool-verified
What it measures: Whether volatile projects sit underneath others that depend on them (so their churn ripples upward), and whether project dependencies form cycles. A widely-depended-on but stable shared/kernel project is healthy, not penalised.
Method: Dependency cycles via elementary-DFS over real .csproj references, plus Martin instability (afferent/efferent) per project. Exhaustive over the reference graph, deterministic.
Coverage: Exhaustive · type-level: afferent/efferent coupling + cycles computed over every production type — the population is all types, not a name convention.
13 production modules (Gradle+Python+sbt+pub), 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; a dependsOn spread (deps: _*) and a project whose directory a helper computes are not visible there; 2 module(s) off the main sequence, with abstractness counted on 12 of the 13 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
Off the main sequence: :lib · ×2
What to do
Resolve the 2 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (2 warning-level).
Enforce Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d5_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether a class's methods are focused on a single responsibility.
Method: LCOM4 cohesion per production class with at least two methods: connected components of methods sharing state or calls, computed syntactically. Deterministic, not a proxy.
Coverage: Exhaustive · type-level: LCOM4 cohesion computed over every production class — the population is all types, not a name convention.
Resolve the 2 Low cohesion finding(s) in Cohesion (LCOM4) — start with DefaultServerApiEndpointClient.scala, Metrics.scala. — One of this dimension's main actionable groups (2 warning-level).
Enforce Cohesion (LCOM4) in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
Detailed fixes: d6_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D9 · Test Distribution10.0 / 10Exemplary✓ Tool-verified
What it measures: Whether the test suite has a healthy mix of unit / integration / end-to-end tests.
Method: Test projects classified (Unit/Integration/BDD/E2E) from compiled metadata; test methods counted exhaustively across projects with placement-agnostic disk fallback. Deterministic.
2315 test methods: 2315 unit, 0 integration, 0 BDD, 0 e2e. The Python suite contributes 329 test function(s) across 36 file(s) declaring at least one — every `def test…` in a file pytest or unittest would collect, which is those frameworks' own definition of a case; a parametrize table counts once, so this is a floor. Its tier split is read from file names and paths only. The Scala suite contributes 1986 test case(s) across 327 file(s) in a test source set declaring at least one — every `test("…")`, `it("…")`, `property("…")` and `"…" in {…}` registration and every JUnit `@Test`, which is how munit, ScalaTest, utest, ZIO Test and specs2 declare a case; a case registered under a computed name is not counted, so this is a floor. Its tier split is INFERRED from paths and file names, except sbt's src/it source set, which the build declares.
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 12 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (7), REDACTED (2), REDACTED (2). — One of this dimension's main actionable groups (12 issue-level).
Enforce REDACTED Scanning in CI to reach Verified (currently Documented). — 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: Whether the licenses of third-party packages are compatible with your policy.
Method: Third-party package licenses resolved from declared package metadata and checked against the configured policy (allow/deny/copyleft). Deterministic; clean = no incompatible license found at metadata depth.
0 of 27 declared JVM dependency artifact(s) use a banned license. Licences were resolved from the POMs Maven Central publishes, over the coordinates this repository's 3 Maven/Gradle manifest(s) declare with a version resolvable from the manifest itself — the same declaration-site closure this analysis reads for dependency currency. The JVM has no lockfile a checkout is guaranteed to carry, so this is deliberately NOT the transitive closure. A further 19 coordinate(s) are not published to Maven Central — another repository (Google's Maven hosts androidx), a SNAPSHOT, or a private artifact — so their licences are not readable from here and they are outside this verdict. ★ COVERAGE OF THIS VERDICT: it grades this repository's JVM dependencies and nothing else. The repository also declares an sbt build (build.sbt) and a Dart pubspec.yaml, and the licences of those dependency graphs were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.
What it measures: Files that change often and are also complex — the riskiest hotspots.
Method: Per production file churn times cyclomatic complexity over a rolling window, computed from git and Roslyn/JS/Razor analysis. Exhaustive, deterministic per commit date.
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.
6 deducted task-comment markers across 84004 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 6 TodoComment finding(s) in Explicit Debt — start with DefaultOperationExecutor.kt (3), DefaultOperationExecutor.scala (3). — One of this dimension's main actionable groups (6 warning-level).
Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the project's documentation is clear, complete, and useful.
Method: 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 is a well-written fiction-themed stasis definition with an outstandingly clear overview (stasis as a confined space/time field in sci-fi) and a rich, multi-media CLI/Android client showcase. The assets README documents its own directory, the client-android README covers development setup, service connections, TLS certificates, and a clipped Why? section that is not penalized; similarly for client-cli, client-ui, core, deployment/dev, and deployment/production. All visible documents are well-structured with headings and an outline (stasis; Desktop Client CLI; Desktop Client UI; Android Client; Why?; Goals; Features; Installation; Server; Clients; Linux and macOS; Removing; Updating; Windows; Removing; Updating; Android; Testing; Development; Contributing; Versioning; License).
Documentation: no installation or build instructions · ×3README.md
✓ On the Gold path — maintain.
Detailed fixes: d19_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D20 · ADR Quality0.0 / 10Critical✓ Tool-verified
What it measures: Whether architecture decisions are recorded well (context, decision, consequences).
Method: Per-ADR judgment by language model at low temperature with two-pass stability; confidence is share of ADRs evaluated; enforcement-field presence detected deterministically. Advisory.
What it measures: Whether 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.
What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.
Method: REDACTED 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.
8 finding(s): 0 critical, 8 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
REDACTED
REDACTED
What to do
Resolve the 8 REDACTED finding(s) in Secrets (history) — start with REDACTED (4), REDACTED (2), REDACTED. — One of this dimension's main actionable groups (8 issue-level).
Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d28_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.
Method: Polyglot static analysis via semgrep across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.
Coverage: semgrep pattern rules over all files — exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).
4 finding(s): 0 critical, 4 high, 0 medium, 0 low. semgrep hit a parse error in 1 file(s) — `client-android/gradlew` (lines 144–145, line 146, line 147, …) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 2 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
REDACTED
REDACTED
What to do
Resolve the 3 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (3 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.
Resolve the 32 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (16), REDACTED (6), REDACTED (6). — One of this dimension's main actionable groups (32 warning-level).
Resolve the 15 High IaC finding(s) in IaC & Container Security — start with REDACTED (6), REDACTED (2), REDACTED (2). — One of this dimension's main actionable groups (15 issue-level).
Resolve the 2 Low IaC finding(s) in IaC & Container Security — start with REDACTED (2). — One of this dimension's main actionable groups (2 recommendation-level).
Detailed fixes: d31_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether anyone still has living knowledge of each file, or it has been orphaned — last understood long ago by someone now gone quiet. The sibling of the bus factor: D16 asks who owns it, D34 asks whether anyone still knows it.
Method: File orphaning as total living-knowledge decay below one focused-commit's worth within a year, computed per-file from the D16 decay model. Exhaustive, deterministic over fixed history.
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 431 of the 1078 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 1 Change coupling finding(s) in Change Coupling — start with default_client_api.py. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d35_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the build pipeline provides supply-chain integrity — generated provenance/attestation, signed artifacts (cosign/sigstore), an SBOM, and pinned build actions. Presence of the configuration, not a runtime guarantee.
Method: Supply-chain provenance/signing read deterministically from CI/build config (.github/workflows, .gitlab-ci.yml, azure-pipelines, Jenkinsfile, .circleci) + the release surface: four signals — generated provenance/attestation (SLSA/in-toto/actions-attest), artifact signing (cosign/sigstore/gitsign), an SBOM (syft/sbom-action/*.spdx.json/*.cdx.json), and SHA-pinned build actions — scored 10·present/denom. NotApplicable without a build pipeline. Detects configuration presence, not runtime enforcement.
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d36_recommendation.md · top locations in Appendix A, every location in findings.md.
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 3 platform declaration(s) and 52 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
✓ On the Gold path — maintain.
Detailed fixes: d44_recommendation.md.
Do you agree with this assessment?
Frontend & cross-cutting dimensions
R = React/JS · M = Maturity · P = Readiness.
AC7 · A11y enforcement4.0 / 10Weak✓ Tool-verified
Other · Accessibility — Whether accessibility is ENFORCED in the toolchain — an accessibility checker configured over the markup (an a11y lint rule set, e.g. eslint-plugin-jsx-a11y or vuejs-accessibility where the project lints JavaScript) and an automated accessibility assertion wired into tests or CI (axe/pa11y/Lighthouse or an equivalent) — on the Documented→Verified→Prevented ladder.
Method: Repo config/CI scan: an accessibility checker configured over the markup (an a11y lint rule set such as eslint-plugin-jsx-a11y / vuejs-accessibility where JavaScript is linted) and an automated accessibility assertion in tests or CI (axe/pa11y/Lighthouse or equivalent), graded on the Documented→Verified→Prevented rungs. Deterministic, presence/rung detection.
Coverage: Population: the repository's own tooling configuration — lint config, test and CI files — NOT the markup. It is read for a configured accessibility checker and an automated accessibility assertion (axe/pa11y/Lighthouse, or a native-toolkit equivalent), and it credits an INVOCATION, never a mention: a licence filename, an import comment or a doc reference earns no rung. Enforcement configured entirely outside the repository leaves no evidence here and cannot be credited.
No accessibility enforcement found — no accessibility linting at author time and no automated accessibility check in tests or CI. Add your UI toolkit's own accessibility assertion to the test suite (Flutter `meetsGuideline`, Espresso `AccessibilityChecks`, XCTest `performAccessibilityAudit`), then gate that test in the pipeline. What was searched, so you can tell an absence from a miss: the 2 markup file(s) this pass actually assessed, the linter configuration checked in beside them, and this repository's test and CI files — matched by name against the accessibility checkers this dimension carries. An audit run outside the repository, a hosted scanner, or a check whose name is not one of those, is not seen here.
What to do
Enforce accessibility in the toolchain your project already uses: assert accessibility in your UI test suite with your toolkit's own matcher (Flutter `meetsGuideline`, Espresso `AccessibilityChecks`, XCTest `performAccessibilityAudit`), then gate that test in CI so a regression blocks the merge.
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 singleton services avoid mutable shared instance state that concurrent callers would race on.
Method: Roslyn scan: singleton field mutations unguarded by lock or Interlocked, per type; syntax-based guard detection. Deterministic, traceable per field.
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.
`ServerApiEndpointClient` declares 25 abstract members: `self`, `server`, `datasetDefinitions`, `datasetDefinition`, `createDatasetDefinition`, `updateDatasetDefinition`, `deleteDatasetDefinition`, `datasetEntries`, `datasetEntry`, `latestEntry`, `createDatasetEntry`, `deleteDatasetEntry`, `publicSchedules`, `publicSchedule`, `datasetMetadata`, `datasetMetadata`, `user`, `resetUserSalt`, `resetUserPassword`, `device`, `pushDeviceKey`, `pullDeviceKey`, `deviceKeyExists`, `ping`, `commands`. Counted over its ABSTRACT members — a `def` with no body or a `val`/`var` with no initializer, once per signature; concrete members, private and protected members, and members of a companion `object` are not counted, because no implementer is forced to write them. Those 25 declarations carry 24 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 24 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. — client/src/main/scala/stasis/client/api/clients/ServerApiEndpointClient.scala:28
What to do
Split fat interfaces into focused role-interfaces so clients depend only on what they use.
Other · Architecture — Whether read (query) handlers stay side-effect-free — a query that writes persistent state or raises events breaks CQS and makes reads unsafe to retry, cache, or route to a read replica.
Method: Roslyn scan: CQRS handlers classified query-vs-command by interface (IQueryHandler/ICommandHandler/IRequestHandler<TQuery,TResult>) and name convention (*Query/Get*/Find* vs *Command); each query handler's body checked for persistent-state writes (SaveChanges/repository Add-Update) or event publishes by resolved invocation. Deterministic, type-level, exhaustive over the detected handlers.
Coverage: Population: CQRS handlers identified by IQueryHandler/ICommandHandler/IRequestHandler interface + *Query/Get*/Find*/*Command NAME convention; query purity then checked exhaustively within that set — a query handler using neither convention is invisible, and mutation is a resolved persistence/publish CALL, not full dataflow.
Other · Domain Modelling — Whether aggregates reference each other by identity (id) rather than by direct object reference — the core DDD consistency-boundary rule.
Method: Roslyn (DDD-gated): aggregate roots identified by convention; each aggregate field checked for direct references to other aggregates versus id-only. Deterministic, DDD-native.
Coverage: Population: aggregate roots identified by AggregateRoot/IAggregateRoot base/interface NAME convention; reference-by-identity then checked exhaustively within that set — a root not using those names is invisible.
Do you agree with this assessment?
DM10 · One transaction, one aggregate10.0 / 10Exemplary○ Nothing flagged
Other · Domain Modelling — Whether a single operation mutates more than one aggregate root. An aggregate is a consistency boundary, so saving two together fuses them into one — the second's invariants come to depend on the first's transaction, and the pair can no longer be separated. Reads of other aggregates are not counted.
Method: Neutral body surface (DDD-gated): every method body scanned for repository WRITE calls (Add/Update/Save/Remove/Delete/Insert/Store and their async forms), keyed on the ARGUMENT type rather than the repository type — three `IRepository<T>` writes collapse to one repository but are three distinct aggregates. Reads (Get/Find/Load/Query) are excluded, so loading another aggregate for context never counts. Score is offending methods over methods that write at all. Deterministic.
Other · Domain Modelling — Whether an aggregate can be constructed in a state its own rules forbid — a public constructor that takes a raw primitive, stores it, and validates nothing, with no factory beside it. A constructor taking only value objects is not counted: each parameter has already validated itself.
Method: Neutral surface (DDD-gated): each non-abstract entity/aggregate checked for a PUBLIC constructor taking at least one RAW PRIMITIVE parameter whose body contains no guard token (throw / Guard. / Ensure. / ArgumentException / CheckRule), on a type that also offers no static Create/Of/From/New factory. A constructor taking only value objects is never charged -- measured: 64 of 87 unguarded public constructors on the C# corpus take value objects only, so ignoring parameter types would be 73% false positives. One finding per entity. Deterministic.
`RuleEntity`'s public constructor takes `directory`, `pattern` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule` or `Requires.` — a guard reached through a helper method those tokens do not name is not seen; for a FACTORY, only this type's OWN static members were read, and only names beginning `Create`, `Of`, `From`, `New` or `Build` — one inherited from a base type, one on a companion builder, or one called `Parse`, `Make` or `Rehydrate` is not seen. If either exists, this row is wrong. If neither does, a caller can build a `RuleEntity` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — client-android/app/src/main/java/stasis/client_android/persistence/rules/RuleEntity.kt:9
`ActiveScheduleEntity`'s public constructor takes `type`, `data` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule` or `Requires.` — a guard reached through a helper method those tokens do not name is not seen; for a FACTORY, only this type's OWN static members were read, and only names beginning `Create`, `Of`, `From`, `New` or `Build` — one inherited from a base type, one on a companion builder, or one called `Parse`, `Make` or `Rehydrate` is not seen. If either exists, this row is wrong. If neither does, a caller can build a `ActiveScheduleEntity` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — client-android/app/src/main/java/stasis/client_android/persistence/schedules/ActiveScheduleEntity.kt:8
`LocalScheduleEntity`'s public constructor takes `info` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule` or `Requires.` — a guard reached through a helper method those tokens do not name is not seen; for a FACTORY, only this type's OWN static members were read, and only names beginning `Create`, `Of`, `From`, `New` or `Build` — one inherited from a base type, one on a companion builder, or one called `Parse`, `Make` or `Rehydrate` is not seen. If either exists, this row is wrong. If neither does, a caller can build a `LocalScheduleEntity` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — client-android/app/src/main/java/stasis/client_android/persistence/schedules/LocalScheduleEntity.kt:11
What to do
Give each aggregate one way in that can refuse — a guarded constructor, value-object parameters that validate themselves, or a private constructor behind a factory that returns a failure.
Other · Domain Modelling — Whether the domain layer stays free of infrastructure dependencies (EF/Marten/HTTP/ASP.NET) — the clean-architecture dependency rule.
Method: Roslyn (DDD-gated): domain-layer types scanned for infrastructure usage in member SIGNATURES and inside method/accessor BODIES — resolved calls and object-creations into EF/Marten/HTTP/Mongo/Redis/message-bus types (not just a namespace allowlist). Deterministic, symbol-resolved, exhaustive over domain-layer bodies, DDD-native.
Coverage: Domain layer identified by NAMESPACE heuristic; infrastructure then resolved by symbol in member SIGNATURES and method/accessor BODIES — rename the layer and the check evaporates.
Other · Domain Modelling — Whether clusters of primitives that travel together (a missing value object) are extracted — a low-weight suggestion, LLM-confirmed when configured.
Method: Roslyn (DDD-gated): primitive parameter clusters recurring three or more times across signatures extracted, then confirmed by language model when configured. Advisory, low-weight.
Other · Domain Modelling — Whether one domain rule is decided — or one measurement produced — in more than one place, rather than living on the type that owns it.
Method: Neutral body surface plus Roslyn (DDD-gated), two arms. DECISION (Roslyn only): a predicate over a domain type's members judged in two or more types, where none of those decisions live on the owning type — operands of comparisons and relational property patterns only, so a member merely passed as an argument is not judged. DERIVATION: a plain all-numeric carrier of ≥2 members, with no base type and exactly one constructor, CONSTRUCTED as the result of a method (returned or assigned, never inline as an argument) in two or more types other than its own — the same measurement produced twice, which centralising the judgement does not fix. DERIVATION runs on every language whose frontend declares the produced-or-passed fact per construction (Roslyn and the Java sidecar today); a target with only the derivation arm carries an engine gap naming the decision arm as not assessed, and a frontend that declares nothing keeps the dimension not measured rather than clean. Single-member rules, test code and generated code are out of population for both. Advisory.
Maturity · Maturity — Whether the 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 an 'Architecture' / 'How it works' section to the root README — the high-level shape.
Add a README to the 2 of 3 project(s) that lack one — worth up to 1.3 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.
deployment/dev/README.md names `docker-compose-no-auth-has.yml`, but no file or folder `docker-compose-no-auth-has.yml` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — deployment/dev/README.md:10
deployment/production/README.md names `.stasis.internal`, but no file or folder `.stasis.internal` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — deployment/production/README.md:64
What to do
Reconcile the README with reality: deployment/dev/README.md names `docker-compose-no-auth-has.yml`, but no file or folder `docker-compose-no-auth-has.yml` exists; deployment/production/README.md names `.stasis.internal`, but no file or folder `.stasis.internal` exists.
Readiness · Readiness — Whether an automated pipeline builds and tests every change.
Method: Filesystem scan: CI workflow files (.github/workflows, .gitlab-ci.yml, etc.) for build and test stages. Exhaustive, deterministic.
Do you agree with this assessment?
P10 · Library API & versioning10.0 / 10Exemplary○ Nothing flagged
Readiness · Readiness — For a library: a deliberate (small) public API surface and explicit semantic versioning so consumers can depend on it safely.
Method: Roslyn scan: public API surface area and semantic-versioning markers (SemVer attributes, changelog entries) for libraries; off .NET, a library is the ecosystem's publication act (an npm package that is not private and names an entry point, a PyPI distribution with a build system, a Rust library crate, a Maven/Gradle module that publishes, a Go module with no package main, a gemspec, a Composer library, a SwiftPM library product, a pub.dev or Hex package), its surface is the share of types the language model records as public (Rust, Swift, Java, Kotlin, Go, Dart; not measured where the model records no type visibility or, as in TypeScript, only module-level export), and its version is read from the manifest, a semver CHANGELOG, release tooling or semver git tags. Exhaustive, deterministic.
Do you agree with this assessment?
P2 · Observability8.3 / 10Strong✓ Tool-verified
Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.
Only 3/7 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `client-ui`, `client-ui/macos`, `identity-ui`, `server-ui`.
What to do
Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).
Method: Filesystem scan: SAST configuration, dependency-update automation, secret scanning, and a benchmark harness or benchmark step — in this repository's own ecosystem. Exhaustive, deterministic.
What to do
Your ecosystem's static analyzer is declared as a dependency but is not wired into CI — run it as a required step on push/PR (e.g. `composer phpstan` / `mix sobelow` / `bundle exec brakeman` / the spotbugs Gradle task / `sbt scalafixAll --check` / `golangci-lint run` / `rebar3 lint`) so a regression fails the build instead of relying on someone running it locally.
Enable Dependabot/Renovate or a dependency-review gate.
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
Readiness · Readiness — Whether releases are automated and safely reversible (probes, rolling updates, approval gates) — from manifests/pipeline files, not the live environment.
Method: Filesystem scan: deployment manifests/IaC (K8s YAML, Helm, Terraform) for rolling updates, probes, approval gates, migration hooks. Exhaustive, deterministic.
Deployment automation exists but no readiness/liveness probes, rolling-update strategy, lifecycle hooks or migration job were evidenced — a bad release is harder to detect and reverse.
What to do
Add readiness/liveness probes and a rolling-update (or blue/green) strategy so a bad release is caught and rolled back automatically.
Do you agree with this assessment?
P5 · DR & Backup7.0 / 10Strong✓ Tool-verified
Readiness · Readiness — Whether disaster recovery is planned and codified — backups, geo-recovery, RTO/RPO, persistence guarantees — from IaC + container manifests + docs, never the live cloud.
Method: Filesystem scan: disaster recovery, backup, geo-recovery, RTO/RPO, persistence guarantees from IaC, manifests, and docs. Exhaustive, deterministic, never a live environment.
What to do
Document RTO/RPO and a tested restore procedure (a backup config alone isn't disaster recovery).
Readiness · Readiness — Whether releases are traceable — a maintained changelog and explicit version stamping.
Method: Filesystem scan: changelog file presence and version tags in csproj or git tags. Exhaustive, deterministic.
No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
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 35 use(s) across 90,542 production line(s) (~0.4/1k). More of the idioms below on the allocation-heavy paths climbs this toward 10.
Dart: on hot paths, hold numbers in dart:typed_data lists (Int32List, Float64List …) instead of boxed List<int>/List<double>, read through views (sublistView, buffer.asInt32List, asByteData) instead of copying, make lists that never grow growable: false, compute in the SIMD types (Float32x4List …), and build bytes with BytesBuilder(copy: false).
Kotlin: on hot paths, use primitive arrays (IntArray, LongArray …) and @JvmInline value classes instead of boxed values, primitive collections (androidx.collection, fastutil) instead of boxed ones, and presize collections and StringBuilders.
Scala: on hot paths, make small wrappers value classes (extends AnyVal), @specialized generic code over primitives, use primitive collections, and presize builders.
Swift: on hot paths, reserveCapacity before appending, use ContiguousArray for class-element arrays, work in place with withUnsafeBufferPointer/withUnsafeTemporaryAllocation, and make large values ~Copyable with borrowing/consuming parameters.
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.
Other · Security — Only what this repository's own non-C# files could be read for was assessed — and because this repository commits the configuration that serves its own HTTP surface, that configuration could be read in full for the security response headers it sets. Nothing else in this dimension was assessed: the transport, cookie, input-validation and crypto controls are read from a source model that was not loaded for this repository’s language, so their absence here is not a finding about this repository.
Method: Roslyn plus filesystem scan: HSTS/security headers, secure cookies, input validation, middleware order, weak crypto (MD5/SHA1/DES); HTTPS-metadata context-aware. On a repository with no .NET source it reads JavaScript/TypeScript, Dart, Ruby, Scala, Rust or Elixir source itself (test, vendored, generated and minified paths not) for the arms that hold whether or not the code serves HTTP: a weak hash or cipher, key material fixed in the source, a TLS client that accepts any certificate, and (JavaScript/TypeScript, Ruby, Scala, Rust and Elixir) an obsolete TLS version; the server controls are not assessed there, and a Dart, Ruby, Scala, Rust or Elixir repository that serves no HTTP of its own is N/A on them. Deterministic.
None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is configured — defense in depth, even when a reverse proxy could set them. This is reported because `REDACTED` builds the web-server image that serves this application, so the configuration that would carry these headers is in this repository and was read in full. (−2.0 on this card.) — REDACTED:1
What to do
Set security response headers on the surface this repository serves: an `add_header` directive per header in the nginx/Caddy/Apache config, a `_headers` / `vercel.json` / `netlify.toml` entry for a static host, or `helmet()` in the HTTP server. `Content-Security-Policy` is the one that pays for itself first — it is what contains an injected script once one reaches the page — followed by `X-Content-Type-Options: nosniff` and a frame policy (`X-Frame-Options: DENY`, or CSP `frame-ancestors`). Where the app is served from a build container, the header configuration belongs in the image beside the built assets, so it ships with them rather than depending on where it lands.
Other · Code Health — Whether the code avoids sync-over-async (deadlock-prone blocking on tasks) and async void.
Method: Roslyn syntax scan: async methods scanned for .Wait()/.GetAwaiter().GetResult() and async-void outside event handlers. Deterministic, hard fact per invocation.
Other · Code Health — Whether any branch is dead by construction — a switch arm whose label can never equal a case-normalised subject, or an `else if` whose predicate the arm above has already swallowed.
Method: Roslyn syntax + semantics: switch labels compared against the subject's own case normaliser, and if/else-if chains checked for a literal an earlier arm's containment test already swallows. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X13 · Undrained process stream10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a child process that has BOTH standard streams redirected drains both — reading one to the end while the other is never read deadlocks once the child fills the unread pipe.
Method: Roslyn syntax + semantics: ProcessStartInfo launches with both streams redirected, checked for a drain of each stream across the enclosing type. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `spawn` imported from `child_process` whose stdout and stderr are both pipes (no options, no `stdio`, or `stdio` of `'pipe'`), bound to a local that never leaves its scope, where exactly one of the two streams is read, the other never, and the child’s `close`/`exit` (or the read stream’s end) is awaited; a shell redirect in the call’s arguments or a `kill` of the child suppresses it. The same rule reads Python’s `subprocess.Popen`, Dart’s `Process.start`, Ruby’s `Open3.popen3`, and Scala’s JDK process starts (`new ProcessBuilder(…).start()` with no `redirectErrorStream`/`redirectError`/`redirectOutput`/`inheritIO`, `Runtime.getRuntime.exec`) where one of `getInputStream`/`getErrorStream` is read and the other never while `waitFor()` is called or the read stream is read to its end. Deterministic, provable per finding. Advisory.
Other · Security — Whether a hand-rolled public/private IP check can be walked past — a method that unwraps IPv4-mapped IPv6 but returns the opposite verdict for the same host written as IPv4-compatible, 6to4 or NAT64.
Method: Roslyn syntax + semantics: methods that unwrap IPv4-mapped IPv6 and hand-roll IPv4 range carve-outs, checked for whether the IPv6 branch also accounts for the IPv4-compatible, 6to4 and NAT64 embeddings. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X15 · Unvalidated length from an untrusted reader10.0 / 10Exemplary○ Nothing flagged
Other · Security — Whether a length read out of the stream being parsed is bounded before it is allocated or read — an unchecked count taken from the input lets the input choose the allocation.
Method: Roslyn syntax + semantics: integer lengths read from a BinaryReader and spent on a bulk read or an array allocation, checked for any comparison or bounding call on the value anywhere in the method. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a loop that shortens a string until it fits a length budget has a floor — one with none grinds the value down to the empty string, or past it into a negative-length `Substring`.
Method: Roslyn syntax + semantics: while/do loops whose body's only effect on a string is to drop its last character, checked for whether anything — a direct comparison on the length, a body guard, a break — bounds that length below. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `while`/`do` loop whose body’s one assignment to a value is `x = x.slice(0, -1)` or `x = x.slice|substring|substr(0, x.length - 1)`, driven by a condition that reads `x.length` only as a term of a larger expression — never compared directly, never tested for truthiness, and with no other read of `x` — and whose body has no `break`, `return`, `throw` or `if` naming `x`. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X17 · Uncapped recursion over a caller-supplied document10.0 / 10Exemplary○ Nothing flagged
Other · Security — Whether a walk that recurses through a JSON/XML tree handed in by its caller bounds how deep it will go — an uncapped walk lets the document's nesting choose the stack depth, and the resulting StackOverflowException cannot be caught.
Method: Roslyn syntax + semantics: methods that take a JSON/XML document node and call themselves with a child of it, reachable from an externally-callable member of the same type that accepts a document, checked for any depth parameter, descent counter or threaded arithmetic anywhere in the walk. On a repository with no .NET source it reads TypeScript off the engine’s own token stream (test, vendored, generated and minified paths and `.d.ts` not) with the same rule: a function or method with a parameter typed as a document value — `unknown`, `any`, `object`, `Record<string, unknown|any>`, a JSON alias (`JsonValue`, `JSONObject`, …) or a DOM node global the file does not rebind — that calls itself (bare, or through `this` for a method, or hands itself to a call over the value as in `value.map(walk)`) with something it took out of that value and never through an ancestor accessor such as `closest()` or `parentElement`, that is exported or reached from an exported function (a public method of the same exported class) taking such a value, and that names no depth, level, nesting, recursion, remaining or budget anywhere and threads no `+`/`-` arithmetic through a self-call. Plain JavaScript is not read: with no annotation nothing tells a parsed document from a tree the code built itself. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a type's disposal matches what it OWNS — releasing what it created, leaving alone what it was handed, and not declaring a finalizer for state that has nothing unmanaged to finalize.
Method: Roslyn syntax + semantics: every assignment to a disposable field is read to decide whether the type CREATED the value or was handed it, and the type's disposal is checked against that answer — an injected interface it disposes, a value it constructed and never releases, a finalizer on a type holding nothing unmanaged, and a disposable local whose every reference is a plain member read. A value handed to a container that disposes its contents (a parent control's `Controls` collection, a component `IContainer`) is released by that container and is not reported; generated code is out of population. On a repository with no .NET source the same ownership questions are read in JavaScript/TypeScript off the engine’s own token stream (test, vendored, generated and minified paths not): a class declaring `dispose()`, `[Symbol.dispose]()` or `[Symbol.asyncDispose]()` that disposes a field it was handed through a constructor parameter typed as a repository interface or resolved by a dependency-injection container; that assigns a field only ever from `new X(…)` of a disposable class and neither releases it anywhere in the class nor names it in its disposal member or a method that member calls, nor hands it to anything else; and a `const`/`let` local built from literals only whose every reference opens a statement operating on a non-release member of it. A class is disposable when every repository declaration of its name declares or inherits a disposal member, or when it is a documented library disposable (`vscode` EventEmitter, CancellationTokenSource and Disposable; three.js geometries, materials, textures, render targets, renderers, controls and composers). The finalizer arm has no JavaScript counterpart: a class cannot declare one. Dart is read for the owned-and-never-released arm: a Flutter `State` (or a class declaring `dispose()`/`close()`) whose library-private field is written only with direct creations of a framework controller, `FocusNode`, `StreamController` or periodic `Timer` (or a `.listen(…)` into a field declared `StreamSubscription`), which nothing in the class or its library releases (`dispose`/`close`/`cancel`) and which is never handed on except as a named argument. Ruby is read for the owned-and-never-released arm and the abandoned-local arm: a class declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose instance variable is written only with a blockless core descriptor creation (`File.open`/`new`, `Tempfile`, `Dir.open`, `IO.popen`, the `socket` and `openssl` socket classes) that no method of the class closes and that is never handed on (passed, returned, stored, exposed by `attr_reader`, delegated) — a class whose superclass or mixin lies outside the repository is not judged — and a blockless creation read through and dropped (`File.open(path).read`) or held in a local that is never closed, returned, passed or stored (a `&:read` block-pass, an `autoclose: false` borrow and a `fileno` hand-over are not abandonment). PHP is read for the same two arms: a class (not a trait, and not one using a trait) declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose `private` property (or a `final` class's `protected` one) is written only with a direct core `fopen`, `tmpfile`, `popen`, `proc_open`, `fsockopen`, `stream_socket_client`/`server` or `opendir` that nothing in the class closes (`fclose`, `pclose`, `closedir`, `unset`, a reset to `null`) and that is never handed on, and a handle held in a function's local, or read through as the argument of a reader, that is never closed, returned, passed, captured or stored; a `php://` stream, `curl_init`, `SplFileObject`, `PDO` and a function the repository declares under the core name are not read. Deterministic, provable per finding. Advisory.
`_SearchState` carries a disposal duty — a `State`, so the framework calls its `dispose()` when it leaves the tree — and it creates `_searchController` itself (line 27, `TextEditingController`), which makes that instance its own. Nothing in the class releases it — no `_searchController.dispose()`, no tear-off of it, on any path — nothing elsewhere in the library releases it through another instance, and it is never handed on as a value (passed positionally, returned, stored, collected), so no other owner can be ending it. Passing it as a named argument does not: a widget or animation never disposes a controller it was given. On what was read, `TextEditingController` outlives the object that made it — its listeners, and through them this object and everything it references, stay reachable, and a ticker, timer or subscription keeps calling into a disposed object. Release it where the duty is discharged: `_searchController.dispose();` in `dispose()` before `super.dispose()`. — client-ui/lib/pages/search.dart:27
`_RecoverState` carries a disposal duty — a `State`, so the framework calls its `dispose()` when it leaves the tree — and it creates `_definitionController` itself (line 27, `TextEditingController`), which makes that instance its own. Nothing in the class releases it — no `_definitionController.dispose()`, no tear-off of it, on any path — nothing elsewhere in the library releases it through another instance, and it is never handed on as a value (passed positionally, returned, stored, collected), so no other owner can be ending it. Passing it as a named argument does not: a widget or animation never disposes a controller it was given. On what was read, `TextEditingController` outlives the object that made it — its listeners, and through them this object and everything it references, stay reachable, and a ticker, timer or subscription keeps calling into a disposed object. Release it where the duty is discharged: `_definitionController.dispose();` in `dispose()` before `super.dispose()`. — client-ui/lib/pages/recover.dart:27
`_RecoverState` carries a disposal duty — a `State`, so the framework calls its `dispose()` when it leaves the tree — and it creates `_queryController` itself (line 29, `TextEditingController`), which makes that instance its own. Nothing in the class releases it — no `_queryController.dispose()`, no tear-off of it, on any path — nothing elsewhere in the library releases it through another instance, and it is never handed on as a value (passed positionally, returned, stored, collected), so no other owner can be ending it. Passing it as a named argument does not: a widget or animation never disposes a controller it was given. On what was read, `TextEditingController` outlives the object that made it — its listeners, and through them this object and everything it references, stay reachable, and a ticker, timer or subscription keeps calling into a disposed object. Release it where the duty is discharged: `_queryController.dispose();` in `dispose()` before `super.dispose()`. — client-ui/lib/pages/recover.dart:29
`_EntityTableState` carries a disposal duty — a `State`, so the framework calls its `dispose()` when it leaves the tree — and it creates `_filterController` itself (line 37, `TextEditingController`), which makes that instance its own. Nothing in the class releases it — no `_filterController.dispose()`, no tear-off of it, on any path — nothing elsewhere in the library releases it through another instance, and it is never handed on as a value (passed positionally, returned, stored, collected), so no other owner can be ending it. Passing it as a named argument does not: a widget or animation never disposes a controller it was given. On what was read, `TextEditingController` outlives the object that made it — its listeners, and through them this object and everything it references, stay reachable, and a ticker, timer or subscription keeps calling into a disposed object. Release it where the duty is discharged: `_filterController.dispose();` in `dispose()` before `super.dispose()`. — server-ui/lib/pages/manage/components/entity_table.dart:37
What to do
Each finding names the value and the span that decides who owns it — the `new` that created it, or the constructor parameter that handed it over. Confirm ownership from that span, then make the disposal match it: release what this type created, leave what it was injected with to whoever created THAT, and drop a finalizer whose type holds nothing unmanaged to release.
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.
`debug` at line 159 is called with an argument built by `"…".join(command)` (line 159), whose cost grows with the collection it walks. Python evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isEnabledFor(logging.DEBUG)` test, no debug flag, no `lambda` the logger calls only when the level is on. — release.py:159
`debug` at line 57 is called with an argument built by `(endpoints.api.map(_.id) ++ endpoints.core.map(_.id) ++ endpoints.discovery.map(_.id)).mkString("…", "…", "…")` (line 60), whose cost grows with the collection it walks. Scala evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: the logger takes a built `String` (SLF4J, Akka/Pekko `LoggingAdapter`, `context.log`), and there is no `isDebugEnabled`/`isTraceEnabled` test and no debug flag. — core/src/main/scala/stasis/core/discovery/providers/server/ServiceDiscoveryProvider.scala:57
What to do
In Python, put the construction behind the logger's own check (`if logger.isEnabledFor(logging.DEBUG):`), or pass the collection itself with a `%s` placeholder (`logger.debug("Items %s", items)`) so the logging module renders it only when the record is emitted. The placeholder alone is not the fix when the argument is still built first: it defers the formatting, not a `json.dumps`, a `join` or a comprehension in the argument, and an f-string defers nothing at all. In Scala, put the construction behind the logger's own check (`if (log.isDebugEnabled)`), or log through a logger that takes the message by name or by macro and so builds it only when the level is on — scala-logging's `LazyLogging`/`StrictLogging` (`logger.debug(s"rows: ${rows.mkString(", ")}")` expands to that check), log4s or log4cats. Interpolating into an `s"…"` is not the fix on SLF4J or Akka's `LoggingAdapter`: their `debug` takes a `String`, so the interpolation and every `mkString` inside it run before the call is entered.
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 a `for` loop leaves the `dict`, `set` or `deque` it is walking alone — CPython's iterators over those check that the collection has not changed size since the loop began, so a body that removes from (or empties) the very collection the loop is walking makes the next step raise `RuntimeError: dictionary changed size during iteration` and the remaining items are never seen. Whether a `for … in` loop leaves the `List`, `Map` or `Set` it is walking alone — Dart's collection iterators check that the collection has not changed since the loop began, so a body that adds to or removes from the very collection the loop is walking (or the map whose `keys`, `values` or `entries` it walks) makes the next step throw `ConcurrentModificationError` and the remaining elements are never seen. Whether a `for` comprehension or `foreach` leaves the mutable collection it is walking alone — an `ArrayBuffer` or `ListBuffer` counts its changes and its iterator checks the count, an `ArrayDeque` (and `mutable.Queue`/`mutable.Stack`) is walked by index up to its starting length, and a `java.util` collection walked through `asScala` is fail-fast, so a body that adds to or removes from the very collection the loop is walking makes a later step throw `ConcurrentModificationException` (`IndexOutOfBoundsException` for a deque) and the remaining elements are never seen. Whether a `for (x in c)` or `c.forEach { … }` leaves the collection it is walking alone — a `mutableListOf`/`ArrayList`, `mutableMapOf`/`HashMap` or `mutableSetOf`/`HashSet` is a `java.util` collection on the JVM and is walked by its own fail-fast iterator, so a body that adds to or removes from the very collection the loop is walking makes the next step throw `ConcurrentModificationException` and the remaining elements are never seen.
Method: Roslyn syntax + semantics: `foreach` statements whose body calls a structural mutator (`Add`/`Remove`/`Clear`/`Insert`/…) on the very expression the loop is enumerating. Two arms. ARM A — the source is a concrete fragile BCL collection, or a live `Keys`/`Values` view over one, and the mutator resolves to that same collection's own member; concurrent and immutable collections and arrays are outside the population by construction, since their enumerators survive a structural change. ARM B — the source is an argument-less accessor CALL on a receiver whose body is in source: the accessor must return a stored field VERBATIM and a sibling member must structurally change that same field, both read off the implementations rather than from the members' names. A mutation the loop provably exits immediately after (`break`/`return`/`throw`/`goto`), or one written inside a nested loop or a lambda, is counted and never reported. Deterministic, provable per finding. Advisory.
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.
`except` 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) — deployment/dev/scripts/generate_artifacts.py:25, identity-ui/deployment/production/stage.py:18, identity-ui/deployment/production/build.py: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.
`error` at line 71 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — core/src/main/scala/stasis/core/persistence/staging/StagingStore.scala:71
Other · Code Health — Whether Scala's null is held to the type system and not undermined by assertions — a file compiled with `-Yexplicit-nulls` is one where `String` excludes null and `String | Null` admits it, a file under WartRemover's `Null` wart or Scalafix's `DisableSyntax.noNulls` is one whose code cannot write `null` and must say `Option`, and each `.nn`, `import scala.language.unsafeNulls` or null-lint suppression is the author overruling that.
Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.
Do you agree with this assessment?
WCAG coverage — what static analysis assessed
Statically assessed 0 of 55 WCAG 2.2 Level A/AA success criteria (0%; ≈0% of the 50 WCAG 2.1 AA criteria for EN 301 549). A further 3 got runtime (rendered axe-core) evidence this scan: 1.3.1, 2.5.8, 4.1.2. The other 52 require runtime or manual evaluation. Partial signal only (a clean result is necessary, not sufficient; static analysis fully verifies none). This is accessibility readiness, not a conformance claim — a WCAG conformance claim requires manual evaluation (WCAG-EM 1.0).
The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.
Unscored — 4 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.
AXR1 Runtime accessibility (rendered) — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
P12 CI test-gate honesty — 1 observation(s) recorded · Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
X10 Duplicated predicate — 21 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X7 Silent fallback defaults — 6 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 3 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.
Not included — 52 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 image/media element found in the parsed markup — AC1 not applicable here.
AC2 Forms & labels — No form control/button found in the parsed markup — AC2 not applicable here.
AC3 Page structure — No structural check found in the parsed markup — AC3 not applicable here.
AC4 Keyboard semantics — No interactive element found in the parsed markup — AC4 not applicable here.
AC5 ARIA correctness — No ARIA usage found in the parsed markup — AC5 not applicable here.
AC6 Visual & motion safety — No styled element found in the parsed markup — AC6 not applicable here.
AX1 Captive dependencies — Not applicable: Dagger rejects, at compile time, a component that holds a binding with a narrower scope than its own.
AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
AX8 Test isolation — no test/production split to check
AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
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.
D10 Test Quality — ~92211 lines of test source are present (.kt, .py, .dart, .scala) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
D11 Test Reliability — Test reliability not scored — polyglot repository, one half's runner produced no measurement
D12 Dependency Hygiene — Not scored — 3 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 — 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.
D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout nor 2+ sibling source directories each declaring an aggregate root. 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 reads resolved call sites in the languages it reads only — this repository's production source is .cc, .cpp, .dart, .kt, .py, .swift, which was left unread. 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 (an sbt build (build.sbt), a Gradle build (build.gradle/build.gradle.kts) and a Dart pubspec.yaml — not scanned yet).
D32 Data Compliance (PII/GDPR) — 1 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
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 (an sbt build (build.sbt), a Gradle build (build.gradle/build.gradle.kts) and a Dart pubspec.yaml — 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
DM12 Ambient inputs in the domain — no domain-layer types detected — ambient-input check not applicable
DM2 Strongly-typed ids — no id-bearing domain types detected — strongly-typed-id adoption not assessable
DM3 Integration-event coupling — no integration events detected — coupling check not applicable
DM4 Rich vs anemic model — no data-bearing entities detected — rich-vs-anemic model not assessable
DM5 Encapsulated state — no domain entities found — DM5 grades how entities protect their state, and this repository declares none
DM7 Repository granularity — no repository abstraction detected (e.g. uses a document session)
ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and this analysis resolves a call's owner only where the receiver's type is written down in the source. Reported as guidance rather than measured
ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, which this analysis does not build from source alone for this language. Reported as guidance rather than measured
ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the Dart, JVM, JavaScript/TypeScript, Python, Swift 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 (`addSbtPlugin("org.scoverage" % "sbt-scoverage" % "<version>")` in `project/plugins.sbt`, then `sbt clean coverage test coverageReport`) 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.
X2 Cancellation propagation — no C# was loaded; this repository's Dart, Scala, Python and Kotlin were read, and no request in it can be cancelled by a caller (Dio, or package:http's Abortable requests; Ktor, OkHttp's newCall or a URL stream, from a suspend function) — a Scala request takes no token: a Future cannot be cancelled, and cats-effect, ZIO and Monix interrupt the fiber that made the request from outside the call, not through a parameter; a Python request takes no token: asyncio cancels the task and trio or anyio the scope that made it, from outside the call, and requests, httpx, aiohttp and gRPC take a timeout, not a cancellation; a Kotlin request outside a suspend function has no caller's cancellation to honour
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.
MethodTooLong: SettingsFragment.onCreatePreferences client-android/app/src/main/java/stasis/client_android/activities/fragments/SettingsFragment.kt:88— MethodTooLong — onCreatePreferences runs 442 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 342 over it, 4.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: _ClientBootstrapFormState.build client-ui/lib/pages/components/client_bootstrap_form.dart:47— MethodTooLong — build runs 248 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 148 over it, 2.48× 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: _ClientCredentialsResetFormState.build client-ui/lib/pages/components/client_credentials_reset_form.dart:44— MethodTooLong — build runs 218 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 118 over it, 2.18× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: _CredentialsFormState.build client-ui/lib/pages/components/credentials_form.dart:37— MethodTooLong — build runs 196 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 96 over it, 1.96× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: _ClientReEncryptDeviceSecretFormState.build client-ui/lib/pages/components/client_reencrypt_device_secret_form.dart:43— MethodTooLong — build runs 191 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 91 over it, 1.91× 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: AnalyticsDialogFragment.onCreateView client-android/app/src/main/java/stasis/client_android/activities/fragments/settings/AnalyticsDialogFragment.kt:44— MethodTooLong — onCreateView runs 187 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 87 over it, 1.87× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: MainActivity.initNavigation client-android/app/src/main/java/stasis/client_android/activities/MainActivity.kt:136— MethodTooLong — initNavigation runs 186 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 86 over it, 1.86× 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: _ClientPushDeviceSecretFormState.build client-ui/lib/pages/components/client_push_device_secret_form.dart:43— MethodTooLong — build runs 186 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 86 over it, 1.86× 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: OperationDetailsFragment.onCreateView client-android/app/src/main/java/stasis/client_android/activities/fragments/operations/OperationDetailsFragment.kt:46— MethodTooLong — onCreateView 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: DatasetDefinitionDetailsFragment.onCreateView client-android/app/src/main/java/stasis/client_android/activities/fragments/backup/DatasetDefinitionDetailsFragment.kt:55— MethodTooLong — onCreateView runs 164 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 64 over it, 1.64× 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: _ClientPullDeviceSecretFormState.build client-ui/lib/pages/components/client_pull_device_secret_form.dart:42— MethodTooLong — build runs 161 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 61 over it, 1.61× 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: ItemViewHolder.bind client-android/app/src/main/java/stasis/client_android/activities/fragments/schedules/ScheduleListItemAdapter.kt:82— MethodTooLong — bind runs 152 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 52 over it, 1.52× 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: ItemViewHolder.bind client-android/app/src/main/java/stasis/client_android/activities/fragments/operations/OperationListItemAdapter.kt:68— MethodTooLong — bind runs 151 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 51 over it, 1.51× 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: Status.build client-ui/lib/pages/status.dart:19— MethodTooLong — build runs 150 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 50 over it, 1.50× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: DatasetEntryDetailsFragment.onCreateView client-android/app/src/main/java/stasis/client_android/activities/fragments/backup/DatasetEntryDetailsFragment.kt:45— MethodTooLong — onCreateView 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: _SearchState.build client-ui/lib/pages/search.dart:32— MethodTooLong — build runs 140 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 40 over it, 1.40× 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: _DevicesState.build server-ui/lib/pages/manage/devices.dart:43— MethodTooLong — build runs 133 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 33 over it, 1.33× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: _UsersState.build server-ui/lib/pages/manage/users.dart:34— MethodTooLong — build 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: _OperationDetailsState.build client-ui/lib/pages/components/operation_details.dart:30— MethodTooLong — build 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: OperationSummary.build client-ui/lib/pages/components/operation_summary.dart:10— MethodTooLong — build 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: Home.build server-ui/lib/pages/default/home.dart:33— MethodTooLong — build 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: _BackupEntryMetadataState.build client-ui/lib/pages/components/backup_entry_metadata.dart:33— MethodTooLong — build 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: DefaultOperationScheduler.scheduler client/src/main/scala/stasis/client/ops/scheduling/DefaultOperationScheduler.scala:93— MethodTooLong — scheduler runs 123 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 23 over it, 1.23× 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: ServiceHandler.handleMessage client-android/app/src/main/java/stasis/client_android/scheduling/SchedulerService.kt:90— MethodTooLong — handleMessage runs 121 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 21 over it, 1.21× 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: ItemViewHolder.bind client-android/app/src/main/java/stasis/client_android/activities/fragments/search/SearchResultListItemAdapter.kt:49— MethodTooLong — bind 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.
Duplicated block (13 lines × 2) client/src/main/scala/stasis/client/security/DefaultCredentialsProvider.scala:195— client/src/main/scala/stasis/client/security/DefaultCredentialsProvider.scala:195-207 | client/src/main/scala/stasis/client/security/DefaultCredentialsProvider.scala:249-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 `client/src/main/scala/stasis/client/security/DefaultCredentialsProvider.scala:195` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (13 lines × 2) client-android/app/src/main/java/stasis/client_android/activities/fragments/HomeFragment.kt:324— client-android/app/src/main/java/stasis/client_android/activities/fragments/HomeFragment.kt:324-336 | client-android/app/src/main/java/stasis/client_android/activities/fragments/backup/DatasetDefinitionDetailsFragment.kt:182-194 — 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 `client-android/app/src/main/java/stasis/client_android/activities/fragments/HomeFragment.kt:324` 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, `client-android/app/src/main/java/stasis/client_android/activities/fragments/backup/DatasetDefinitionDetailsFragment.kt:196` calls `navigate`, `actionGlobalHomeFragment` and `client-android/app/src/main/java/stasis/client_android/activities/fragments/HomeFragment.kt:337` 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) client-android/app/src/main/java/stasis/client_android/activities/fragments/backup/DatasetDefinitionDetailsFragment.kt:101— client-android/app/src/main/java/stasis/client_android/activities/fragments/backup/DatasetDefinitionDetailsFragment.kt:101-114 | client-android/app/src/main/java/stasis/client_android/activities/fragments/backup/DatasetDefinitionListItemAdapter.kt:70-82 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `client-android/app/src/main/java/stasis/client_android/activities/fragments/backup/DatasetDefinitionDetailsFragment.kt:101` 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 (13 lines × 2) client-android/app/src/main/java/stasis/client_android/activities/fragments/backup/DatasetDefinitionDetailsFragment.kt:147— client-android/app/src/main/java/stasis/client_android/activities/fragments/backup/DatasetDefinitionDetailsFragment.kt:147-159 | client-android/app/src/main/java/stasis/client_android/activities/fragments/backup/DatasetDefinitionListItemAdapter.kt:115-127 — 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) client-android/app/src/main/java/stasis/client_android/activities/fragments/backup/DatasetDefinitionDetailsFragment.kt:162— client-android/app/src/main/java/stasis/client_android/activities/fragments/backup/DatasetDefinitionDetailsFragment.kt:162-174 | client-android/app/src/main/java/stasis/client_android/activities/fragments/backup/DatasetDefinitionListItemAdapter.kt:130-142 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (13 lines × 2) client-android/lib/src/main/kotlin/stasis/client_android/lib/encryption/secrets/UserKeyStoreEncryptionSecret.kt:17— client-android/lib/src/main/kotlin/stasis/client_android/lib/encryption/secrets/UserKeyStoreEncryptionSecret.kt:17-29 | client-android/lib/src/main/kotlin/stasis/client_android/lib/encryption/secrets/UserLocalEncryptionSecret.kt:17-29 — before extracting anything, compare `client-android/lib/src/main/kotlin/stasis/client_android/lib/encryption/secrets/UserKeyStoreEncryptionSecret.kt` and `client-android/lib/src/main/kotlin/stasis/client_android/lib/encryption/secrets/UserLocalEncryptionSecret.kt` as WHOLE FILES: 96% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. 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 (13 lines × 2) client-android/app/src/main/java/stasis/client_android/activities/fragments/SettingsFragment.kt:285— client-android/app/src/main/java/stasis/client_android/activities/fragments/SettingsFragment.kt:285-297 | client-android/app/src/main/java/stasis/client_android/activities/fragments/SettingsFragment.kt:356-368 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `client-android/app/src/main/java/stasis/client_android/activities/fragments/SettingsFragment.kt:285` 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 (13 lines × 2) client-ui/lib/pages/home.dart:199— client-ui/lib/pages/home.dart:199-211 | client-ui/lib/pages/home.dart:252-264 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (13 lines × 2) identity-ui/lib/api/oauth.dart:9— identity-ui/lib/api/oauth.dart:9-21 | server-ui/lib/api/oauth.dart:8-20 — before extracting anything, compare `identity-ui/lib/api/oauth.dart` and `server-ui/lib/api/oauth.dart` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 63 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 (13 lines × 2) identity-ui/lib/pages/manage/clients.dart:187— identity-ui/lib/pages/manage/clients.dart:187-199 | REDACTED:209-221 — before extracting anything, compare `identity-ui/lib/pages/manage/clients.dart` and `REDACTED` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 85 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 (13 lines × 2) server-ui/lib/pages/manage/components/forms/crate_store_field.dart:125— server-ui/lib/pages/manage/components/forms/crate_store_field.dart:125-137 | server-ui/lib/pages/manage/components/forms/crate_store_field.dart:198-210 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (13 lines × 2) server-ui/lib/pages/manage/definitions.dart:303— server-ui/lib/pages/manage/definitions.dart:303-315 | server-ui/lib/pages/manage/device_keys.dart:91-103 — before extracting anything, compare `server-ui/lib/pages/manage/definitions.dart` and `server-ui/lib/pages/manage/device_keys.dart` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 36 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 (13 lines × 2) server-ui/lib/pages/manage/schedules.dart:138— server-ui/lib/pages/manage/schedules.dart:138-150 | server-ui/lib/pages/manage/users.dart:233-245 — before extracting anything, compare `server-ui/lib/pages/manage/schedules.dart` and `server-ui/lib/pages/manage/users.dart` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 97 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 (13 lines × 2) identity-ui/lib/pages/manage/components/entity_table.dart:48— identity-ui/lib/pages/manage/components/entity_table.dart:48-60 | server-ui/lib/pages/manage/components/entity_table.dart:112-124 — 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) client/src/main/scala/stasis/client/tracking/trackers/DefaultBackupTracker.scala:327— client/src/main/scala/stasis/client/tracking/trackers/DefaultBackupTracker.scala:327-334 | client/src/main/scala/stasis/client/tracking/trackers/DefaultRecoveryTracker.scala:230-237 — 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 `client/src/main/scala/stasis/client/tracking/trackers/DefaultBackupTracker.scala:327` 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 (8 lines × 2) identity/src/main/scala/stasis/identity/api/manage/Owners.scala:108— identity/src/main/scala/stasis/identity/api/manage/Owners.scala:108-115 | identity/src/main/scala/stasis/identity/api/manage/Owners.scala:153-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. Read the line range as the matched WINDOW rather than a finished unit: at `identity/src/main/scala/stasis/identity/api/manage/Owners.scala:108` 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) identity/src/main/scala/stasis/identity/api/oauth/AuthorizationCodeGrant.scala:231— identity/src/main/scala/stasis/identity/api/oauth/AuthorizationCodeGrant.scala:231-238 | identity/src/main/scala/stasis/identity/api/oauth/PkceAuthorizationCodeGrant.scala:242-249 — before extracting anything, compare `identity/src/main/scala/stasis/identity/api/oauth/AuthorizationCodeGrant.scala` and `identity/src/main/scala/stasis/identity/api/oauth/PkceAuthorizationCodeGrant.scala` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 118 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) client-cli/client_cli/cli/bootstrap.py:34— client-cli/client_cli/cli/bootstrap.py:34-41 | client-cli/client_cli/cli/maintenance.py:98-105 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (8 lines × 2) client-ui/lib/api/api_client.dart:94— client-ui/lib/api/api_client.dart:94-101 | server-ui/lib/api/api_client.dart:55-62 — 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) client-ui/lib/pages/components/forms/date_time_field.dart:59— client-ui/lib/pages/components/forms/date_time_field.dart:59-66 | client-ui/lib/pages/components/forms/date_time_field.dart:74-81 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2) client-ui/lib/pages/status.dart:35— client-ui/lib/pages/status.dart:35-42 | server-ui/lib/pages/manage/users.dart:116-123 — 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) client-ui/lib/pages/status.dart:85— client-ui/lib/pages/status.dart:85-92 | server-ui/lib/pages/manage/devices.dart:132-139 — 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) identity-ui/lib/api/default_api_client.dart:149— identity-ui/lib/api/default_api_client.dart:149-156 | identity-ui/lib/api/default_api_client.dart:159-166 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2) identity-ui/lib/pages/default/home.dart:62— identity-ui/lib/pages/default/home.dart:62-69 | identity-ui/lib/pages/page_router.dart:251-258 — 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) identity-ui/lib/pages/manage/clients.dart:73— identity-ui/lib/pages/manage/clients.dart:73-80 | REDACTED:77-84 — before extracting anything, compare `identity-ui/lib/pages/manage/clients.dart` and `REDACTED` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 85 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 (5 lines × 2) server/src/main/scala/stasis/server/api/routes/Devices.scala:606— server/src/main/scala/stasis/server/api/routes/Devices.scala:606-610 | server/src/main/scala/stasis/server/api/routes/Devices.scala:647-651 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `server/src/main/scala/stasis/server/api/routes/Devices.scala:606` 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) client/src/main/scala/stasis/client/model/DatasetMetadata.scala:192— client/src/main/scala/stasis/client/model/DatasetMetadata.scala:192-196 | client/src/main/scala/stasis/client/model/FilesystemMetadata.scala:162-166 — 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) identity/src/main/scala/stasis/identity/service/Service.scala:291— identity/src/main/scala/stasis/identity/service/Service.scala:291-295 | server/src/main/scala/stasis/server/service/Service.scala:302-306 — 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) identity/src/main/scala/stasis/identity/service/Service.scala:321— identity/src/main/scala/stasis/identity/service/Service.scala:321-325 | server/src/main/scala/stasis/server/service/Service.scala:341-345 — 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) identity/src/main/scala/stasis/identity/service/Service.scala:386— identity/src/main/scala/stasis/identity/service/Service.scala:386-390 | server/src/main/scala/stasis/server/service/Service.scala:352-356 — 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) client-android/lib/src/main/kotlin/stasis/client_android/lib/encryption/secrets/UserHashedEncryptionPassword.kt:19— client-android/lib/src/main/kotlin/stasis/client_android/lib/encryption/secrets/UserHashedEncryptionPassword.kt:19-23 | client-android/lib/src/main/kotlin/stasis/client_android/lib/encryption/secrets/UserHashedEncryptionPassword.kt:39-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.
Duplicated block (5 lines × 2) client-android/lib/src/main/kotlin/stasis/client_android/lib/model/DatasetMetadata.kt:169— client-android/lib/src/main/kotlin/stasis/client_android/lib/model/DatasetMetadata.kt:169-173 | client-android/lib/src/main/kotlin/stasis/client_android/lib/model/FilesystemMetadata.kt:138-142 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `client-android/lib/src/main/kotlin/stasis/client_android/lib/model/FilesystemMetadata.kt:144` calls `getDefault` and `client-android/lib/src/main/kotlin/stasis/client_android/lib/model/DatasetMetadata.kt:174` 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 (5 lines × 2) client-ui/lib/pages/components/dataset_definition_summary.dart:63— client-ui/lib/pages/components/dataset_definition_summary.dart:63-67 | client-ui/lib/pages/home.dart:78-84 — 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) client-ui/lib/pages/page_router.dart:116— client-ui/lib/pages/page_router.dart:116-120 | client-ui/lib/pages/settings.dart:71-76 — 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) client-ui/lib/api/default_client_api.dart:150— client-ui/lib/api/default_client_api.dart:150-154 | server-ui/lib/api/default_api_client.dart:166-170 — 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) client-ui/lib/api/default_client_api.dart:310— client-ui/lib/api/default_client_api.dart:310-314 | server-ui/lib/api/default_api_client.dart:294-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 (9 lines × 2) client/src/main/scala/stasis/client/collection/rules/internal/FilesWalker.scala:34— client/src/main/scala/stasis/client/collection/rules/internal/FilesWalker.scala:34-42 | client/src/main/scala/stasis/client/collection/rules/internal/FilesWalker.scala:60-68 — 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 `client/src/main/scala/stasis/client/collection/rules/internal/FilesWalker.scala:34` 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) client/src/main/scala/stasis/client/encryption/secrets/UserHashedEncryptionPassword.scala:15— client/src/main/scala/stasis/client/encryption/secrets/UserHashedEncryptionPassword.scala:15-23 | client/src/main/scala/stasis/client/encryption/secrets/UserHashedEncryptionPassword.scala:30-38 — 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) client/src/main/scala/stasis/client/service/components/Tracking.scala:45— client/src/main/scala/stasis/client/service/components/Tracking.scala:45-53 | client/src/main/scala/stasis/client/service/components/Tracking.scala:58-66 — 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 `client/src/main/scala/stasis/client/service/components/Tracking.scala:45` 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) client/src/main/scala/stasis/client/service/components/bootstrap/Secrets.scala:104— client/src/main/scala/stasis/client/service/components/bootstrap/Secrets.scala:104-112 | client/src/main/scala/stasis/client/service/components/maintenance/Secrets.scala:121-129 — `client/src/main/scala/stasis/client/service/components/bootstrap/Secrets.scala` and `client/src/main/scala/stasis/client/service/components/maintenance/Secrets.scala` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 5 separate duplicated blocks between them, totalling at least 62 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `client/src/main/scala/stasis/client/service/components/bootstrap/Secrets.scala: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.
Duplicated block (9 lines × 2) core/src/main/scala/stasis/core/persistence/backends/slick/LegacyKeyValueStore.scala:37— core/src/main/scala/stasis/core/persistence/backends/slick/LegacyKeyValueStore.scala:37-45 | identity/src/main/scala/stasis/identity/persistence/internal/LegacyKeyValueStore.scala:37-45 — before extracting anything, compare `core/src/main/scala/stasis/core/persistence/backends/slick/LegacyKeyValueStore.scala` and `identity/src/main/scala/stasis/identity/persistence/internal/LegacyKeyValueStore.scala` as WHOLE FILES: 96% 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. 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 `core/src/main/scala/stasis/core/persistence/backends/slick/LegacyKeyValueStore.scala: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.
Duplicated block (9 lines × 2) client-android/app/src/main/java/stasis/client_android/utils/NotificationManagerExtensions.kt:77— client-android/app/src/main/java/stasis/client_android/utils/NotificationManagerExtensions.kt:77-85 | client-android/app/src/main/java/stasis/client_android/utils/NotificationManagerExtensions.kt:102-110 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `client-android/app/src/main/java/stasis/client_android/utils/NotificationManagerExtensions.kt:77` 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) deployment/dev/scripts/generate_self_signed_cert.py:14— deployment/dev/scripts/generate_self_signed_cert.py:14-22 | deployment/production/scripts/generate_cert.py:14-22 — before extracting anything, compare `deployment/dev/scripts/generate_self_signed_cert.py` and `deployment/production/scripts/generate_cert.py` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 50 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `deployment/production/scripts/generate_cert.py:23` calls `add_argument` and `deployment/dev/scripts/generate_self_signed_cert.py:23` 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 (9 lines × 2) client-ui/lib/pages/components/dataset_metadata_entity_summary.dart:129— client-ui/lib/pages/components/dataset_metadata_entity_summary.dart:129-137 | client-ui/lib/pages/search.dart:164-172 — 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) server-ui/lib/pages/manage/definitions.dart:214— server-ui/lib/pages/manage/definitions.dart:214-222 | server-ui/lib/pages/manage/devices.dart:349-357 — before extracting anything, compare `server-ui/lib/pages/manage/definitions.dart` and `server-ui/lib/pages/manage/devices.dart` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 115 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 (9 lines × 2) identity-ui/lib/api/oauth.dart:55— identity-ui/lib/api/oauth.dart:55-63 | server-ui/lib/api/oauth.dart:54-62 — before extracting anything, compare `identity-ui/lib/api/oauth.dart` and `server-ui/lib/api/oauth.dart` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 63 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication· Members sharing a duplicated core (4 members, 50+ identical tokens) · ×8
Members sharing a duplicated core (4 members, 50+ identical tokens) client/src/main/scala/stasis/client/ops/Metrics.scala:50— client/src/main/scala/stasis/client/ops/Metrics.scala:50-65 | client/src/main/scala/stasis/client/ops/Metrics.scala:67-82 | client/src/main/scala/stasis/client/ops/Metrics.scala:94-109 | client/src/main/scala/stasis/client/ops/Metrics.scala:111-126 — 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.
Members sharing a duplicated core (4 members, 50+ identical tokens) client/src/main/scala/stasis/client/service/components/Secrets.scala:37— client/src/main/scala/stasis/client/service/components/Secrets.scala:37-193 | client/src/main/scala/stasis/client/service/components/bootstrap/Secrets.scala:36-147 | client/src/main/scala/stasis/client/service/components/maintenance/Credentials.scala:23-82 | client/src/main/scala/stasis/client/service/components/maintenance/Secrets.scala:34-245 — 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.
Members sharing a duplicated core (4 members, 50+ identical tokens) client-android/lib/src/main/kotlin/stasis/client_android/lib/ops/scheduling/DefaultOperationExecutor.kt:58— client-android/lib/src/main/kotlin/stasis/client_android/lib/ops/scheduling/DefaultOperationExecutor.kt:58-89 | client-android/lib/src/main/kotlin/stasis/client_android/lib/ops/scheduling/DefaultOperationExecutor.kt:95-126 | client-android/lib/src/main/kotlin/stasis/client_android/lib/ops/scheduling/DefaultOperationExecutor.kt:174-206 | client-android/lib/src/main/kotlin/stasis/client_android/lib/ops/scheduling/DefaultOperationExecutor.kt:213-245 — 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.
Members sharing a duplicated core (4 members, 50+ identical tokens) identity-ui/deployment/production/build.py:23— identity-ui/deployment/production/build.py:23-33 | identity-ui/deployment/production/stage.py:23-33 | server-ui/deployment/production/build.py:23-33 | server-ui/deployment/production/stage.py:23-33 — 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.
Members sharing a duplicated core (4 members, 50+ identical tokens) client-ui/lib/pages/components/dataset_definition_summary.dart:9— client-ui/lib/pages/components/dataset_definition_summary.dart:9-96 | client-ui/lib/pages/components/dataset_entry_summary.dart:7-50 | client-ui/lib/pages/home.dart:170-211 | client-ui/lib/pages/rules.dart:22-142 — 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.
Members sharing a duplicated core (4 members, 50+ identical tokens) client-ui/lib/pages/components/dataset_definition_summary.dart:9— client-ui/lib/pages/components/dataset_definition_summary.dart:9-96 | client-ui/lib/pages/components/dataset_entry_summary.dart:7-50 | client-ui/lib/pages/components/operation_summary.dart:10-183 | client-ui/lib/pages/components/schedule_summary.dart:9-80 — 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.
Members sharing a duplicated core (4 members, 50+ identical tokens) identity-ui/lib/pages/manage/clients.dart:24— identity-ui/lib/pages/manage/clients.dart:24-110 | identity-ui/lib/pages/manage/codes.dart:20-67 | REDACTED:30-114 | identity-ui/lib/pages/manage/tokens.dart:20-69 — 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.
Members sharing a duplicated core (4 members, 50+ identical tokens) server-ui/lib/pages/manage/definitions.dart:39— server-ui/lib/pages/manage/definitions.dart:39-128 | server-ui/lib/pages/manage/devices.dart:43-221 | server-ui/lib/pages/manage/schedules.dart:30-111 | server-ui/lib/pages/manage/users.dart:34-207 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Duplicated block (16 lines × 2) client/src/main/scala/stasis/client/ops/backup/Backup.scala:187— client/src/main/scala/stasis/client/ops/backup/Backup.scala:187-202 | client/src/main/scala/stasis/client/ops/recovery/Recovery.scala:221-236 — 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 (16 lines × 2) client-android/app/src/main/java/stasis/client_android/scheduling/SchedulerService.kt:128— client-android/app/src/main/java/stasis/client_android/scheduling/SchedulerService.kt:128-143 | client-android/app/src/main/java/stasis/client_android/scheduling/SchedulerService.kt:266-281 — 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 `client-android/app/src/main/java/stasis/client_android/scheduling/SchedulerService.kt:128` 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 lines × 2) client-android/lib/src/main/kotlin/stasis/client_android/lib/ops/backup/stages/EntityProcessing.kt:68— client-android/lib/src/main/kotlin/stasis/client_android/lib/ops/backup/stages/EntityProcessing.kt:68-83 | client-android/lib/src/main/kotlin/stasis/client_android/lib/ops/recovery/stages/EntityProcessing.kt:73-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. Read the line range as the matched WINDOW rather than a finished unit: at `client-android/lib/src/main/kotlin/stasis/client_android/lib/ops/backup/stages/EntityProcessing.kt:68` 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 lines × 2) identity-ui/lib/pages/manage/clients.dart:130— identity-ui/lib/pages/manage/clients.dart:130-145 | REDACTED:138-153 — before extracting anything, compare `identity-ui/lib/pages/manage/clients.dart` and `REDACTED` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 85 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 (16 lines × 2) REDACTED:161— REDACTED:161-176 | REDACTED:282-297 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (16 lines × 2) server-ui/lib/pages/manage/commands.dart:152— server-ui/lib/pages/manage/commands.dart:152-167 | server-ui/lib/pages/manage/commands.dart:244-259 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (16 lines × 2) server-ui/lib/pages/manage/definitions.dart:161— server-ui/lib/pages/manage/definitions.dart:161-176 | server-ui/lib/pages/manage/devices.dart:300-315 — before extracting anything, compare `server-ui/lib/pages/manage/definitions.dart` and `server-ui/lib/pages/manage/devices.dart` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 115 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 (16 lines × 2) client-ui/lib/model/users/user.dart:19— client-ui/lib/model/users/user.dart:19-34 | server-ui/lib/model/users/user.dart:20-35 — 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) client/src/main/scala/stasis/client/service/components/Secrets.scala:72— client/src/main/scala/stasis/client/service/components/Secrets.scala:72-82 | client/src/main/scala/stasis/client/service/components/maintenance/Credentials.scala:34-44 — 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) server/src/main/scala/stasis/server/api/routes/Devices.scala:95— server/src/main/scala/stasis/server/api/routes/Devices.scala:95-105 | server/src/main/scala/stasis/server/api/routes/Devices.scala:270-280 — 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 `server/src/main/scala/stasis/server/api/routes/Devices.scala:95` 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 (11 lines × 2) client-ui/lib/pages/components/client_pull_device_secret_form.dart:281— client-ui/lib/pages/components/client_pull_device_secret_form.dart:281-291 | client-ui/lib/pages/components/client_push_device_secret_form.dart:316-326 — before extracting anything, compare `client-ui/lib/pages/components/client_pull_device_secret_form.dart` and `client-ui/lib/pages/components/client_push_device_secret_form.dart` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 274 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) client-ui/lib/pages/components/credentials_form.dart:285— client-ui/lib/pages/components/credentials_form.dart:285-295 | client-ui/lib/pages/settings.dart:399-410 — 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) client-ui/lib/pages/components/dataset_definition_summary.dart:28— client-ui/lib/pages/components/dataset_definition_summary.dart:28-38 | client-ui/lib/pages/components/dataset_entry_summary.dart:21-31 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (11 lines × 2) server-ui/lib/pages/manage/components/forms/crate_store_field.dart:217— server-ui/lib/pages/manage/components/forms/crate_store_field.dart:217-227 | server-ui/lib/pages/manage/components/forms/node_address_field.dart:96-106 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (11 lines × 2) server-ui/lib/pages/manage/definitions.dart:261— server-ui/lib/pages/manage/definitions.dart:261-271 | server-ui/lib/pages/manage/schedules.dart:197-207 — before extracting anything, compare `server-ui/lib/pages/manage/definitions.dart` and `server-ui/lib/pages/manage/schedules.dart` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 61 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) server-ui/lib/pages/manage/components/forms/device_limits_field.dart:134— server-ui/lib/pages/manage/components/forms/device_limits_field.dart:134-144 | server-ui/lib/pages/manage/components/forms/user_limits_field.dart:148-158 — before extracting anything, compare `server-ui/lib/pages/manage/components/forms/device_limits_field.dart` and `server-ui/lib/pages/manage/components/forms/user_limits_field.dart` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 94 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 (7 lines × 2) client/src/main/scala/stasis/client/service/ApplicationArguments.scala:346— client/src/main/scala/stasis/client/service/ApplicationArguments.scala:346-352 | client/src/main/scala/stasis/client/service/ApplicationArguments.scala:356-362 — 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 `client/src/main/scala/stasis/client/service/ApplicationArguments.scala:346` 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 (7 lines × 2) client/src/main/scala/stasis/client/service/ApplicationArguments.scala:380— client/src/main/scala/stasis/client/service/ApplicationArguments.scala:380-386 | client/src/main/scala/stasis/client/service/ApplicationArguments.scala:390-396 — 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 `client/src/main/scala/stasis/client/service/ApplicationArguments.scala:380` 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 (7 lines × 2) client/src/main/scala/stasis/client/service/ApplicationArguments.scala:414— client/src/main/scala/stasis/client/service/ApplicationArguments.scala:414-420 | client/src/main/scala/stasis/client/service/ApplicationArguments.scala:424-430 — 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 `client/src/main/scala/stasis/client/service/ApplicationArguments.scala:414` 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 (7 lines × 2) client/src/main/scala/stasis/client/ops/commands/DefaultCommandProcessor.scala:212— client/src/main/scala/stasis/client/ops/commands/DefaultCommandProcessor.scala:212-218 | client/src/main/scala/stasis/client/ops/monitoring/DefaultServerMonitor.scala:107-113 — 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 `client/src/main/scala/stasis/client/ops/commands/DefaultCommandProcessor.scala:212` 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 (7 lines × 2) client-ui/lib/pages/components/operation_details.dart:262— client-ui/lib/pages/components/operation_details.dart:262-268 | client-ui/lib/pages/components/operation_details.dart:273-279 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) client-ui/lib/pages/home.dart:171— client-ui/lib/pages/home.dart:171-177 | client-ui/lib/pages/home.dart:214-220 — 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) client-ui/lib/pages/components/operation_details.dart:95— client-ui/lib/pages/components/operation_details.dart:95-101 | client-ui/lib/pages/components/operation_details.dart:126-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.
TodoComment client-android/lib/src/main/kotlin/stasis/client_android/lib/ops/scheduling/DefaultOperationExecutor.kt:248— // TODO - implement — 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 client-android/lib/src/main/kotlin/stasis/client_android/lib/ops/scheduling/DefaultOperationExecutor.kt:252— // TODO - implement — 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 client-android/lib/src/main/kotlin/stasis/client_android/lib/ops/scheduling/DefaultOperationExecutor.kt:256— // TODO - implement — 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 client/src/main/scala/stasis/client/ops/scheduling/DefaultOperationExecutor.scala:162— // TODO - implement — 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 client/src/main/scala/stasis/client/ops/scheduling/DefaultOperationExecutor.scala:165— // TODO - implement — 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 client/src/main/scala/stasis/client/ops/scheduling/DefaultOperationExecutor.scala:168— // TODO - implement — 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.
TooManyMethods: DefaultApiClient server-ui/lib/api/default_api_client.dart:39— TooManyMethods — 49 methods. The bar is 30 methods; this is 19 over it, 1.63× 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: DefaultClientApi client-cli/client_cli/api/default_client_api.py:14— TooManyMethods — 45 methods. The bar is 30 methods; this is 15 over it, 1.50× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: InactiveClientApi client-cli/client_cli/api/inactive_client_api.py:10— TooManyMethods — 38 methods. The bar is 30 methods; this is 8 over it, 1.27× 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: MockApiClient client-ui/lib/api/mock_api_client.dart:31— TooManyMethods — 37 methods. The bar is 30 methods; this is 7 over it, 1.23× the bar. Most of these members implement api.ClientApi (34 of 37 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: DefaultClientApi client-ui/lib/api/default_client_api.dart:31— TooManyMethods — 36 methods. The bar is 30 methods; this is 6 over it, 1.20× the bar. Most of these members implement api.ClientApi (34 of 36 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: ClientApi client-ui/lib/api/api_client.dart:153— TooManyMethods — 34 methods. The bar is 30 methods; this is 4 over it, 1.13× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
Duplicated block (17 lines × 2) server/src/main/scala/stasis/server/api/ApiEndpoint.scala:122— server/src/main/scala/stasis/server/api/ApiEndpoint.scala:122-138 | server/src/main/scala/stasis/server/api/BootstrapEndpoint.scala:97-113 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. 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) client-android/lib/src/main/kotlin/stasis/client_android/lib/ops/backup/Backup.kt:56— client-android/lib/src/main/kotlin/stasis/client_android/lib/ops/backup/Backup.kt:56-72 | client-android/lib/src/main/kotlin/stasis/client_android/lib/ops/recovery/Recovery.kt:54-70 — 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 `client-android/lib/src/main/kotlin/stasis/client_android/lib/ops/backup/Backup.kt:56` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (17 lines × 2) deployment/dev/scripts/generate_self_signed_cert.py:23— deployment/dev/scripts/generate_self_signed_cert.py:23-39 | deployment/production/scripts/generate_cert.py:25-41 — before extracting anything, compare `deployment/dev/scripts/generate_self_signed_cert.py` and `deployment/production/scripts/generate_cert.py` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 50 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (17 lines × 2) client-ui/lib/pages/components/credentials_form.dart:41— client-ui/lib/pages/components/credentials_form.dart:41-57 | identity-ui/lib/pages/authorize/credentials_form.dart:49-65 — before extracting anything, compare `client-ui/lib/pages/components/credentials_form.dart` and `identity-ui/lib/pages/authorize/credentials_form.dart` 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. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (17 lines × 2) client-ui/lib/pages/components/update_user_credentials_form.dart:80— client-ui/lib/pages/components/update_user_credentials_form.dart:80-96 | client-ui/lib/pages/components/update_user_credentials_form.dart:101-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 (17 lines × 2) server-ui/lib/pages/manage/components/forms/password_field.dart:28— server-ui/lib/pages/manage/components/forms/password_field.dart:28-44 | server-ui/lib/pages/manage/components/forms/password_field.dart:49-65 — 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) client/src/main/scala/stasis/client/api/http/routes/Operations.scala:99— client/src/main/scala/stasis/client/api/http/routes/Operations.scala:99-110 | client/src/main/scala/stasis/client/api/http/routes/Operations.scala:136-147 — 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 `client/src/main/scala/stasis/client/api/http/routes/Operations.scala:99` 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) server/src/main/scala/stasis/server/api/routes/Analytics.scala:52— server/src/main/scala/stasis/server/api/routes/Analytics.scala:52-63 | server/src/main/scala/stasis/server/api/routes/DatasetEntries.scala:45-56 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `server/src/main/scala/stasis/server/api/routes/Analytics.scala:52` 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) client-android/app/src/main/java/stasis/client_android/activities/fragments/HomeFragment.kt:243— client-android/app/src/main/java/stasis/client_android/activities/fragments/HomeFragment.kt:243-254 | client-android/app/src/main/java/stasis/client_android/activities/fragments/operations/OperationDetailsFragment.kt:71-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. Read the line range as the matched WINDOW rather than a finished unit: at `client-android/app/src/main/java/stasis/client_android/activities/fragments/HomeFragment.kt:243` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) client-ui/lib/pages/components/operation_summary.dart:109— client-ui/lib/pages/components/operation_summary.dart:109-120 | client-ui/lib/pages/components/operation_summary.dart:133-144 — 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) client-ui/lib/pages/status.dart:30— client-ui/lib/pages/status.dart:30-41 | client-ui/lib/pages/status.dart:80-91 — 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) server-ui/lib/pages/manage/analytics.dart:155— server-ui/lib/pages/manage/analytics.dart:155-166 | server-ui/lib/pages/manage/codes.dart:92-103 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (10 lines × 2) client/src/main/scala/stasis/client/ops/commands/DefaultCommandProcessor.scala:139— client/src/main/scala/stasis/client/ops/commands/DefaultCommandProcessor.scala:139-148 | client/src/main/scala/stasis/client/ops/commands/DefaultCommandProcessor.scala:172-181 — 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 `client/src/main/scala/stasis/client/ops/commands/DefaultCommandProcessor.scala:139` 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) client/src/main/scala/stasis/client/service/components/bootstrap/Base.scala:54— client/src/main/scala/stasis/client/service/components/bootstrap/Base.scala:54-63 | client/src/main/scala/stasis/client/service/components/maintenance/Base.scala:65-74 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (10 lines × 2) core/src/main/scala/stasis/core/persistence/backends/file/container/ops/ContainerLogOps.scala:50— core/src/main/scala/stasis/core/persistence/backends/file/container/ops/ContainerLogOps.scala:50-59 | core/src/main/scala/stasis/core/persistence/backends/file/container/ops/ContainerOps.scala:58-67 — 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) client-ui/lib/pages/components/operation_summary.dart:38— client-ui/lib/pages/components/operation_summary.dart:38-47 | client-ui/lib/pages/home.dart:218-227 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (10 lines × 2) identity-ui/lib/api/oauth.dart:70— identity-ui/lib/api/oauth.dart:70-79 | server-ui/lib/api/oauth.dart:69-78 — before extracting anything, compare `identity-ui/lib/api/oauth.dart` and `server-ui/lib/api/oauth.dart` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 63 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 (10 lines × 2) identity-ui/lib/main.dart:18— identity-ui/lib/main.dart:18-27 | server-ui/lib/main.dart:19-28 — 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 (24 lines × 2) server/src/main/scala/stasis/server/api/routes/Devices.scala:612— server/src/main/scala/stasis/server/api/routes/Devices.scala:612-635 | server/src/main/scala/stasis/server/api/routes/Devices.scala:653-676 — 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 `server/src/main/scala/stasis/server/api/routes/Devices.scala:612` 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 (24 lines × 2) client-android/lib/src/main/kotlin/stasis/client_android/lib/ops/scheduling/DefaultOperationExecutor.kt:177— client-android/lib/src/main/kotlin/stasis/client_android/lib/ops/scheduling/DefaultOperationExecutor.kt:177-200 | client-android/lib/src/main/kotlin/stasis/client_android/lib/ops/scheduling/DefaultOperationExecutor.kt:216-239 — 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 `client-android/lib/src/main/kotlin/stasis/client_android/lib/ops/scheduling/DefaultOperationExecutor.kt:177` 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 (24 lines × 2) client-cli/client_cli/api/__init__.py:40— client-cli/client_cli/api/__init__.py:40-63 | client-cli/client_cli/api/__init__.py:100-123 — 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 `client-cli/client_cli/api/__init__.py: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.
Duplicated block (24 lines × 2) deployment/dev/scripts/generate_self_signed_cert.py:41— deployment/dev/scripts/generate_self_signed_cert.py:41-64 | deployment/production/scripts/generate_cert.py:45-68 — before extracting anything, compare `deployment/dev/scripts/generate_self_signed_cert.py` and `deployment/production/scripts/generate_cert.py` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 50 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 (24 lines × 2) identity-ui/lib/pages/default/not_found.dart:8— identity-ui/lib/pages/default/not_found.dart:8-31 | server-ui/lib/pages/default/not_found.dart:9-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.
Duplicated block (14 lines × 2) client/src/main/scala/stasis/client/api/clients/DefaultServerApiEndpointClient.scala:89— client/src/main/scala/stasis/client/api/clients/DefaultServerApiEndpointClient.scala:89-102 | client/src/main/scala/stasis/client/api/clients/DefaultServerApiEndpointClient.scala:322-335 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (14 lines × 2) client/src/main/scala/stasis/client/security/DefaultCredentialsProvider.scala:191— client/src/main/scala/stasis/client/security/DefaultCredentialsProvider.scala:191-204 | client/src/main/scala/stasis/client/security/DefaultCredentialsProvider.scala:214-227 — 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 `client/src/main/scala/stasis/client/security/DefaultCredentialsProvider.scala:191` 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) client/src/main/scala/stasis/client/service/components/maintenance/init/ViaStdIn.scala:54— client/src/main/scala/stasis/client/service/components/maintenance/init/ViaStdIn.scala:54-67 | client/src/main/scala/stasis/client/service/components/maintenance/init/ViaStdIn.scala:70-83 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (14 lines × 2) client-ui/lib/pages/backup_entries.dart:112— client-ui/lib/pages/backup_entries.dart:112-125 | client-ui/lib/pages/operations.dart:63-76 — 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) client-ui/lib/pages/home.dart:38— client-ui/lib/pages/home.dart:38-51 | client-ui/lib/pages/home.dart:53-66 — 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.
Swallowed exception (caught, then discarded) deployment/dev/scripts/generate_artifacts.py:25— `except` 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) identity-ui/deployment/production/stage.py:18— `except` 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) identity-ui/deployment/production/build.py:18— `except` 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) server-ui/deployment/production/stage.py:18— `except` 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) server-ui/deployment/production/build.py:18— `except` 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.
Duplicated block (18 lines × 2) server/src/main/scala/stasis/server/api/routes/Users.scala:315— server/src/main/scala/stasis/server/api/routes/Users.scala:315-332 | server/src/main/scala/stasis/server/api/routes/Users.scala:377-394 — 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 `server/src/main/scala/stasis/server/api/routes/Users.scala:315` 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, `server/src/main/scala/stasis/server/api/routes/Users.scala:397` calls `warnN`, `successful`, `complete` and `server/src/main/scala/stasis/server/api/routes/Users.scala:333` 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 (18 lines × 2) client-android/app/src/main/java/stasis/client_android/activities/fragments/HomeFragment.kt:183— client-android/app/src/main/java/stasis/client_android/activities/fragments/HomeFragment.kt:183-200 | client-android/app/src/main/java/stasis/client_android/activities/fragments/backup/DatasetEntryListItemAdapter.kt:91-108 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `client-android/app/src/main/java/stasis/client_android/activities/fragments/backup/DatasetEntryListItemAdapter.kt:88` calls `setSourceTransitionName` and `client-android/app/src/main/java/stasis/client_android/activities/fragments/HomeFragment.kt:180` 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 (18 lines × 2) client-ui/lib/pages/components/client_bootstrap_form.dart:94— client-ui/lib/pages/components/client_bootstrap_form.dart:94-111 | client-ui/lib/pages/components/client_bootstrap_form.dart:145-162 — 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 (18 lines × 2) client-ui/lib/pages/components/forms/file_size_field.dart:93— client-ui/lib/pages/components/forms/file_size_field.dart:93-110 | server-ui/lib/pages/manage/components/forms/file_size_field.dart:93-110 — before extracting anything, compare `client-ui/lib/pages/components/forms/file_size_field.dart` and `server-ui/lib/pages/manage/components/forms/file_size_field.dart` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 63 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 (15 lines × 2) core/src/main/scala/stasis/core/persistence/backends/slick/LegacyKeyValueStore.scala:47— core/src/main/scala/stasis/core/persistence/backends/slick/LegacyKeyValueStore.scala:47-61 | identity/src/main/scala/stasis/identity/persistence/internal/LegacyKeyValueStore.scala:47-61 — before extracting anything, compare `core/src/main/scala/stasis/core/persistence/backends/slick/LegacyKeyValueStore.scala` and `identity/src/main/scala/stasis/identity/persistence/internal/LegacyKeyValueStore.scala` as WHOLE FILES: 96% 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. 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 `core/src/main/scala/stasis/core/persistence/backends/slick/LegacyKeyValueStore.scala:47` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (15 lines × 2) client-ui/lib/pages/backup_entries.dart:121— client-ui/lib/pages/backup_entries.dart:121-135 | client-ui/lib/pages/components/backup_entry_metadata.dart:178-192 — 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 (15 lines × 2) client-ui/lib/pages/components/client_pull_device_secret_form.dart:115— client-ui/lib/pages/components/client_pull_device_secret_form.dart:115-129 | client-ui/lib/pages/components/client_push_device_secret_form.dart:148-162 — before extracting anything, compare `client-ui/lib/pages/components/client_pull_device_secret_form.dart` and `client-ui/lib/pages/components/client_push_device_secret_form.dart` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 274 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 (15 lines × 2) client-ui/lib/model/devices/device.dart:21— client-ui/lib/model/devices/device.dart:21-35 | server-ui/lib/model/devices/device.dart:21-35 — 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 (12 lines × 3) client/src/main/scala/stasis/client/service/components/Secrets.scala:84— client/src/main/scala/stasis/client/service/components/Secrets.scala:84-95 | client/src/main/scala/stasis/client/service/components/bootstrap/Secrets.scala:78-89 | client/src/main/scala/stasis/client/service/components/maintenance/Secrets.scala:92-103 — 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 `client/src/main/scala/stasis/client/service/components/Secrets.scala:84` 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) deployment/dev/scripts/generate_device_secret.py:23— deployment/dev/scripts/generate_device_secret.py:23-34 | deployment/dev/scripts/generate_user_password.py:18-29 | deployment/production/scripts/generate_user_password.py:18-29 — before extracting anything, compare `deployment/dev/scripts/generate_user_password.py` and `deployment/production/scripts/generate_user_password.py` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 92 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 `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 (12 lines × 3) server-ui/lib/pages/manage/devices.dart:233— server-ui/lib/pages/manage/devices.dart:233-244 | server-ui/lib/pages/manage/schedules.dart:137-148 | server-ui/lib/pages/manage/users.dart:232-243 — before extracting anything, compare `server-ui/lib/pages/manage/devices.dart` and `server-ui/lib/pages/manage/schedules.dart` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 89 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 (12 lines × 3) server-ui/lib/pages/manage/devices.dart:307— server-ui/lib/pages/manage/devices.dart:307-318 | server-ui/lib/pages/manage/schedules.dart:140-151 | server-ui/lib/pages/manage/users.dart:235-246 — before extracting anything, compare `server-ui/lib/pages/manage/devices.dart` and `server-ui/lib/pages/manage/schedules.dart` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 89 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 × 3) client/src/main/scala/stasis/client/security/DefaultCredentialsProvider.scala:195— client/src/main/scala/stasis/client/security/DefaultCredentialsProvider.scala:195-205 | client/src/main/scala/stasis/client/security/DefaultCredentialsProvider.scala:218-228 | client/src/main/scala/stasis/client/security/DefaultCredentialsProvider.scala:249-259 — 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 `client/src/main/scala/stasis/client/security/DefaultCredentialsProvider.scala:195` 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 × 3) client-android/app/src/main/java/stasis/client_android/activities/fragments/recover/RecoverFragment.kt:257— client-android/app/src/main/java/stasis/client_android/activities/fragments/recover/RecoverFragment.kt:257-267 | client-android/app/src/main/java/stasis/client_android/activities/fragments/schedules/LocalScheduleFormDialogFragment.kt:158-168 | client-android/app/src/main/java/stasis/client_android/activities/fragments/search/SearchFragment.kt:167-177 — 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 `client-android/app/src/main/java/stasis/client_android/activities/fragments/recover/RecoverFragment.kt:257` 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 × 3) server-ui/lib/pages/manage/components/forms/device_limits_field.dart:54— server-ui/lib/pages/manage/components/forms/device_limits_field.dart:54-64 | server-ui/lib/pages/manage/components/forms/user_limits_field.dart:37-47 | server-ui/lib/pages/manage/components/forms/user_limits_field.dart:61-71 — before extracting anything, compare `server-ui/lib/pages/manage/components/forms/device_limits_field.dart` and `server-ui/lib/pages/manage/components/forms/user_limits_field.dart` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 94 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 × 3) server-ui/lib/pages/manage/definitions.dart:261— server-ui/lib/pages/manage/definitions.dart:261-271 | server-ui/lib/pages/manage/devices.dart:498-508 | server-ui/lib/pages/manage/users.dart:318-328 — before extracting anything, compare `server-ui/lib/pages/manage/definitions.dart` and `server-ui/lib/pages/manage/devices.dart` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 115 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 (22 lines × 2) client-android/lib/src/main/kotlin/stasis/client_android/lib/ops/scheduling/DefaultOperationExecutor.kt:62— client-android/lib/src/main/kotlin/stasis/client_android/lib/ops/scheduling/DefaultOperationExecutor.kt:62-83 | client-android/lib/src/main/kotlin/stasis/client_android/lib/ops/scheduling/DefaultOperationExecutor.kt: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 `client-android/lib/src/main/kotlin/stasis/client_android/lib/ops/scheduling/DefaultOperationExecutor.kt:62` 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 × 2) client-ui/lib/api/default_client_api.dart:49— client-ui/lib/api/default_client_api.dart:49-70 | client-ui/lib/api/default_init_api.dart:16-37 — 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 (22 lines × 2) client-ui/lib/pages/components/credentials_form.dart:59— client-ui/lib/pages/components/credentials_form.dart:59-80 | identity-ui/lib/pages/authorize/credentials_form.dart:67-88 — before extracting anything, compare `client-ui/lib/pages/components/credentials_form.dart` and `identity-ui/lib/pages/authorize/credentials_form.dart` 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. 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 (22 lines × 2) identity-ui/lib/pages/authorize/derived_passwords.dart:6— identity-ui/lib/pages/authorize/derived_passwords.dart:6-27 | server-ui/lib/api/derived_passwords.dart:6-27 — 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 (20 lines × 2) client-android/app/src/main/java/stasis/client_android/activities/fragments/operations/OperationDetailsFragment.kt:91— client-android/app/src/main/java/stasis/client_android/activities/fragments/operations/OperationDetailsFragment.kt:91-110 | client-android/app/src/main/java/stasis/client_android/activities/fragments/operations/OperationListItemAdapter.kt:69-88 — 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 (20 lines × 2) client-ui/lib/model/users/permission.dart:14— client-ui/lib/model/users/permission.dart:14-33 | server-ui/lib/model/users/permission.dart:14-33 — 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 (20 lines × 2) client-ui/lib/pages/components/client_bootstrap_form.dart:70— client-ui/lib/pages/components/client_bootstrap_form.dart:70-89 | client-ui/lib/pages/components/client_bootstrap_form.dart:116-135 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (20 lines × 2) client-ui/lib/pages/components/client_credentials_reset_form.dart:98— client-ui/lib/pages/components/client_credentials_reset_form.dart:98-117 | client-ui/lib/pages/components/client_push_device_secret_form.dart:117-136 — before extracting anything, compare `client-ui/lib/pages/components/client_credentials_reset_form.dart` and `client-ui/lib/pages/components/client_push_device_secret_form.dart` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 271 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.
X18 · Disposal-pattern correctness· Owned disposable field is never released · ×4
Owned disposable field is never released client-ui/lib/pages/search.dart:27— `_SearchState` carries a disposal duty — a `State`, so the framework calls its `dispose()` when it leaves the tree — and it creates `_searchController` itself (line 27, `TextEditingController`), which makes that instance its own. Nothing in the class releases it — no `_searchController.dispose()`, no tear-off of it, on any path — nothing elsewhere in the library releases it through another instance, and it is never handed on as a value (passed positionally, returned, stored, collected), so no other owner can be ending it. Passing it as a named argument does not: a widget or animation never disposes a controller it was given. On what was read, `TextEditingController` outlives the object that made it — its listeners, and through them this object and everything it references, stay reachable, and a ticker, timer or subscription keeps calling into a disposed object. Release it where the duty is discharged: `_searchController.dispose();` in `dispose()` before `super.dispose()`.
Owned disposable field is never released client-ui/lib/pages/recover.dart:27— `_RecoverState` carries a disposal duty — a `State`, so the framework calls its `dispose()` when it leaves the tree — and it creates `_definitionController` itself (line 27, `TextEditingController`), which makes that instance its own. Nothing in the class releases it — no `_definitionController.dispose()`, no tear-off of it, on any path — nothing elsewhere in the library releases it through another instance, and it is never handed on as a value (passed positionally, returned, stored, collected), so no other owner can be ending it. Passing it as a named argument does not: a widget or animation never disposes a controller it was given. On what was read, `TextEditingController` outlives the object that made it — its listeners, and through them this object and everything it references, stay reachable, and a ticker, timer or subscription keeps calling into a disposed object. Release it where the duty is discharged: `_definitionController.dispose();` in `dispose()` before `super.dispose()`.
Owned disposable field is never released client-ui/lib/pages/recover.dart:29— `_RecoverState` carries a disposal duty — a `State`, so the framework calls its `dispose()` when it leaves the tree — and it creates `_queryController` itself (line 29, `TextEditingController`), which makes that instance its own. Nothing in the class releases it — no `_queryController.dispose()`, no tear-off of it, on any path — nothing elsewhere in the library releases it through another instance, and it is never handed on as a value (passed positionally, returned, stored, collected), so no other owner can be ending it. Passing it as a named argument does not: a widget or animation never disposes a controller it was given. On what was read, `TextEditingController` outlives the object that made it — its listeners, and through them this object and everything it references, stay reachable, and a ticker, timer or subscription keeps calling into a disposed object. Release it where the duty is discharged: `_queryController.dispose();` in `dispose()` before `super.dispose()`.
Owned disposable field is never released server-ui/lib/pages/manage/components/entity_table.dart:37— `_EntityTableState` carries a disposal duty — a `State`, so the framework calls its `dispose()` when it leaves the tree — and it creates `_filterController` itself (line 37, `TextEditingController`), which makes that instance its own. Nothing in the class releases it — no `_filterController.dispose()`, no tear-off of it, on any path — nothing elsewhere in the library releases it through another instance, and it is never handed on as a value (passed positionally, returned, stored, collected), so no other owner can be ending it. Passing it as a named argument does not: a widget or animation never disposes a controller it was given. On what was read, `TextEditingController` outlives the object that made it — its listeners, and through them this object and everything it references, stay reachable, and a ticker, timer or subscription keeps calling into a disposed object. Release it where the duty is discharged: `_filterController.dispose();` in `dispose()` before `super.dispose()`.
D4 · Code Duplication· Members sharing a duplicated core (5 members, 50+ identical tokens) · ×3
Members sharing a duplicated core (5 members, 50+ identical tokens) client-cli/client_cli/cli/maintenance.py:18— client-cli/client_cli/cli/maintenance.py:18-52 | client-cli/client_cli/cli/maintenance.py:95-152 | client-cli/client_cli/cli/maintenance.py:176-231 | client-cli/client_cli/cli/maintenance.py:245-295 | client-cli/client_cli/cli/maintenance.py:309-356 — 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.
Members sharing a duplicated core (5 members, 50+ identical tokens) client-ui/lib/api/app_processes.dart:52— client-ui/lib/api/app_processes.dart:52-88 | client-ui/lib/api/app_processes.dart:90-132 | client-ui/lib/api/app_processes.dart:134-176 | client-ui/lib/api/app_processes.dart:178-219 | client-ui/lib/api/app_processes.dart:221-262 — 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.
Members sharing a duplicated core (5 members, 50+ identical tokens) server-ui/lib/pages/manage/definitions.dart:39— server-ui/lib/pages/manage/definitions.dart:39-128 | server-ui/lib/pages/manage/devices.dart:43-221 | server-ui/lib/pages/manage/nodes.dart:26-97 | server-ui/lib/pages/manage/reservations.dart:23-80 | server-ui/lib/pages/manage/schedules.dart:30-111 — 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.
Duplicated block (9 lines × 3) client/src/main/scala/stasis/client/service/ApplicationArguments.scala:343— client/src/main/scala/stasis/client/service/ApplicationArguments.scala:343-351 | client/src/main/scala/stasis/client/service/ApplicationArguments.scala:377-385 | client/src/main/scala/stasis/client/service/ApplicationArguments.scala:411-419 — 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 `client/src/main/scala/stasis/client/service/ApplicationArguments.scala:343` 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) client-ui/lib/api/default_client_api.dart:217— client-ui/lib/api/default_client_api.dart:217-225 | client-ui/lib/api/default_client_api.dart:240-248 | client-ui/lib/api/default_client_api.dart:260-268 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (9 lines × 3) client-ui/lib/pages/components/entity_form.dart:78— client-ui/lib/pages/components/entity_form.dart:78-86 | identity-ui/lib/pages/manage/components/entity_form.dart:60-68 | server-ui/lib/pages/manage/components/entity_form.dart:80-88 — before extracting anything, compare `identity-ui/lib/pages/manage/components/entity_form.dart` and `server-ui/lib/pages/manage/components/entity_form.dart` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 36 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 (15 lines × 3) client-android/app/src/main/java/stasis/client_android/scheduling/SchedulerService.kt:128— client-android/app/src/main/java/stasis/client_android/scheduling/SchedulerService.kt:128-142 | client-android/app/src/main/java/stasis/client_android/scheduling/SchedulerService.kt:166-180 | client-android/app/src/main/java/stasis/client_android/scheduling/SchedulerService.kt:266-280 — 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. 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 × 3) client-ui/lib/pages/components/client_bootstrap_form.dart:151— client-ui/lib/pages/components/client_bootstrap_form.dart:151-165 | client-ui/lib/pages/components/client_credentials_reset_form.dart:104-118 | client-ui/lib/pages/components/client_push_device_secret_form.dart:123-137 — before extracting anything, compare `client-ui/lib/pages/components/client_bootstrap_form.dart` and `client-ui/lib/pages/components/client_credentials_reset_form.dart` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 195 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 (15 lines × 3) server-ui/lib/pages/manage/commands.dart:148— server-ui/lib/pages/manage/commands.dart:148-162 | server-ui/lib/pages/manage/definitions.dart:162-176 | server-ui/lib/pages/manage/devices.dart:301-315 — before extracting anything, compare `server-ui/lib/pages/manage/commands.dart` and `server-ui/lib/pages/manage/definitions.dart` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 49 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) client-android/app/src/main/java/stasis/client_android/tracking/DefaultBackupTracker.kt:51— client-android/app/src/main/java/stasis/client_android/tracking/DefaultBackupTracker.kt:51-56 | client-android/app/src/main/java/stasis/client_android/tracking/DefaultRecoveryTracker.kt:46-51 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (6 lines × 2) identity-ui/lib/pages/manage/components/entity_form.dart:49— identity-ui/lib/pages/manage/components/entity_form.dart:49-54 | server-ui/lib/pages/manage/components/entity_form.dart:69-74 — before extracting anything, compare `identity-ui/lib/pages/manage/components/entity_form.dart` and `server-ui/lib/pages/manage/components/entity_form.dart` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 36 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 (6 lines × 2) client-ui/lib/pages/components/credentials_form.dart:342— client-ui/lib/pages/components/credentials_form.dart:342-347 | identity-ui/lib/pages/authorize/credentials_form.dart:243-248 — before extracting anything, compare `client-ui/lib/pages/components/credentials_form.dart` and `identity-ui/lib/pages/authorize/credentials_form.dart` 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. 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 (5 lines × 5) deployment/dev/scripts/generate_artifacts.py:22— deployment/dev/scripts/generate_artifacts.py:22-26 | identity-ui/deployment/production/build.py:15-19 | identity-ui/deployment/production/stage.py:15-19 | server-ui/deployment/production/build.py:15-19 | server-ui/deployment/production/stage.py:15-19 — before extracting anything, compare `identity-ui/deployment/production/build.py` and `identity-ui/deployment/production/stage.py` as WHOLE FILES: 90% 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 (5 lines × 5) server-ui/lib/pages/manage/definitions.dart:61— server-ui/lib/pages/manage/definitions.dart:61-65 | server-ui/lib/pages/manage/devices.dart:66-70 | server-ui/lib/pages/manage/nodes.dart:46-50 | server-ui/lib/pages/manage/reservations.dart:40-44 | server-ui/lib/pages/manage/schedules.dart:52-56 — before extracting anything, compare `server-ui/lib/pages/manage/definitions.dart` and `server-ui/lib/pages/manage/devices.dart` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 115 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 (5 lines × 5) server-ui/lib/api/bootstrap_api_client.dart:18— server-ui/lib/api/bootstrap_api_client.dart:18-22 | server-ui/lib/api/default_api_client.dart:81-85 | server-ui/lib/api/default_api_client.dart:98-102 | server-ui/lib/api/default_api_client.dart:190-194 | server-ui/lib/api/default_api_client.dart:230-234 — there are 5 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 5 sites; resolving a subset leaves the remainder to drift apart.
Duplicated block (31 lines × 2) client-ui/lib/api/app_processes.dart:179— client-ui/lib/api/app_processes.dart:179-209 | client-ui/lib/api/app_processes.dart:222-252 — 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 (31 lines × 2) identity-ui/lib/api/oauth.dart:23— identity-ui/lib/api/oauth.dart:23-53 | server-ui/lib/api/oauth.dart:22-52 — before extracting anything, compare `identity-ui/lib/api/oauth.dart` and `server-ui/lib/api/oauth.dart` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 63 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 (31 lines × 2) identity-ui/lib/pages/manage/components/entity_form.dart:139— identity-ui/lib/pages/manage/components/entity_form.dart:139-169 | server-ui/lib/pages/manage/components/forms/state_field.dart:33-63 — 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 (14 lines × 4) client-ui/lib/api/app_processes.dart:94— client-ui/lib/api/app_processes.dart:94-107 | client-ui/lib/api/app_processes.dart:138-151 | client-ui/lib/api/app_processes.dart:182-195 | client-ui/lib/api/app_processes.dart:225-238 — 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.
Duplicated block (14 lines × 4) client-ui/lib/pages/components/client_credentials_reset_form.dart:152— client-ui/lib/pages/components/client_credentials_reset_form.dart:152-165 | client-ui/lib/pages/components/client_pull_device_secret_form.dart:114-127 | client-ui/lib/pages/components/client_push_device_secret_form.dart:147-160 | client-ui/lib/pages/components/client_reencrypt_device_secret_form.dart:122-135 — before extracting anything, compare `client-ui/lib/pages/components/client_credentials_reset_form.dart` and `client-ui/lib/pages/components/client_pull_device_secret_form.dart` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 218 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 (14 lines × 4) server-ui/lib/pages/manage/commands.dart:149— server-ui/lib/pages/manage/commands.dart:149-162 | server-ui/lib/pages/manage/commands.dart:241-254 | server-ui/lib/pages/manage/definitions.dart:163-176 | server-ui/lib/pages/manage/devices.dart:302-315 — before extracting anything, compare `server-ui/lib/pages/manage/commands.dart` and `server-ui/lib/pages/manage/definitions.dart` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 49 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.
DM11 · Constructible invalid state· Constructible in an invalid state · ×3
Constructible in an invalid state: RuleEntity client-android/app/src/main/java/stasis/client_android/persistence/rules/RuleEntity.kt:9— `RuleEntity`'s public constructor takes `directory`, `pattern` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule` or `Requires.` — a guard reached through a helper method those tokens do not name is not seen; for a FACTORY, only this type's OWN static members were read, and only names beginning `Create`, `Of`, `From`, `New` or `Build` — one inherited from a base type, one on a companion builder, or one called `Parse`, `Make` or `Rehydrate` is not seen. If either exists, this row is wrong. If neither does, a caller can build a `RuleEntity` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse.
Constructible in an invalid state: ActiveScheduleEntity client-android/app/src/main/java/stasis/client_android/persistence/schedules/ActiveScheduleEntity.kt:8— `ActiveScheduleEntity`'s public constructor takes `type`, `data` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule` or `Requires.` — a guard reached through a helper method those tokens do not name is not seen; for a FACTORY, only this type's OWN static members were read, and only names beginning `Create`, `Of`, `From`, `New` or `Build` — one inherited from a base type, one on a companion builder, or one called `Parse`, `Make` or `Rehydrate` is not seen. If either exists, this row is wrong. If neither does, a caller can build a `ActiveScheduleEntity` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse.
Constructible in an invalid state: LocalScheduleEntity client-android/app/src/main/java/stasis/client_android/persistence/schedules/LocalScheduleEntity.kt:11— `LocalScheduleEntity`'s public constructor takes `info` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule` or `Requires.` — a guard reached through a helper method those tokens do not name is not seen; for a FACTORY, only this type's OWN static members were read, and only names beginning `Create`, `Of`, `From`, `New` or `Build` — one inherited from a base type, one on a companion builder, or one called `Parse`, `Make` or `Rehydrate` is not seen. If either exists, this row is wrong. If neither does, a caller can build a `LocalScheduleEntity` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse.
LegacyKeyValueStore.asMigration (cognitive 18) core/src/main/scala/stasis/core/persistence/backends/slick/LegacyKeyValueStore.scala:36— LegacyKeyValueStore.asMigration has cognitive complexity 18 (threshold 15). Drivers by points: loops 6 (13 pts), match/switch 1 (3 pts), boolean chains 1, if/else 1 (nesting depth added 9). 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.
LegacyKeyValueStore.asMigration (cognitive 18) identity/src/main/scala/stasis/identity/persistence/internal/LegacyKeyValueStore.scala:36— LegacyKeyValueStore.asMigration has cognitive complexity 18 (threshold 15). Drivers by points: loops 6 (13 pts), match/switch 1 (3 pts), boolean chains 1, if/else 1 (nesting depth added 9). 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.
TrackingHandler.handleMessage (cognitive 18) client-android/app/src/main/java/stasis/client_android/tracking/DefaultBackupTracker.kt:202— TrackingHandler.handleMessage has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (10 pts), match/switch 4 (8 pts) (nesting depth added 7). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
TrackingHandler.handleMessage (cognitive 18) client-android/app/src/main/java/stasis/client_android/tracking/DefaultRecoveryTracker.kt:169— TrackingHandler.handleMessage has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (10 pts), match/switch 4 (8 pts) (nesting depth added 7). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
D4 · Code Duplication· Members sharing a duplicated core (6 members, 50+ identical tokens) · ×2
Members sharing a duplicated core (6 members, 50+ identical tokens) client-ui/lib/pages/components/client_bootstrap_form.dart:410— client-ui/lib/pages/components/client_bootstrap_form.dart:410-451 | client-ui/lib/pages/components/client_credentials_reset_form.dart:364-399 | client-ui/lib/pages/components/client_pull_device_secret_form.dart:281-316 | client-ui/lib/pages/components/client_push_device_secret_form.dart:316-351 | client-ui/lib/pages/components/client_reencrypt_device_secret_form.dart:329-364 | client-ui/lib/pages/components/client_regenerate_api_certificate_form.dart:199-226 — 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.
Members sharing a duplicated core (6 members, 50+ identical tokens) client-ui/lib/pages/components/client_bootstrap_form.dart:473— client-ui/lib/pages/components/client_bootstrap_form.dart:473-484 | client-ui/lib/pages/components/client_credentials_reset_form.dart:421-432 | client-ui/lib/pages/components/client_pull_device_secret_form.dart:338-349 | client-ui/lib/pages/components/client_push_device_secret_form.dart:373-384 | client-ui/lib/pages/components/client_reencrypt_device_secret_form.dart:386-397 | client-ui/lib/pages/components/client_regenerate_api_certificate_form.dart:248-259 — 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.
Duplicated block (19–20 lines × 2) client/src/main/scala/stasis/client/api/http/routes/User.scala:50— client/src/main/scala/stasis/client/api/http/routes/User.scala:50-68 | client/src/main/scala/stasis/client/api/http/routes/User.scala:78-97 — 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 `client/src/main/scala/stasis/client/api/http/routes/User.scala:50` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (19–20 lines × 2) REDACTED:185— REDACTED:185-203 | REDACTED:301-320 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (15 lines × 4) client/src/main/scala/stasis/client/ops/Metrics.scala:51— client/src/main/scala/stasis/client/ops/Metrics.scala:51-65 | client/src/main/scala/stasis/client/ops/Metrics.scala:68-82 | client/src/main/scala/stasis/client/ops/Metrics.scala:95-109 | client/src/main/scala/stasis/client/ops/Metrics.scala:112-126 — 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. 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 × 4) server-ui/lib/pages/manage/devices.dart:535— server-ui/lib/pages/manage/devices.dart:535-549 | server-ui/lib/pages/manage/nodes.dart:174-188 | server-ui/lib/pages/manage/schedules.dart:236-250 | server-ui/lib/pages/manage/users.dart:433-447 — before extracting anything, compare `server-ui/lib/pages/manage/devices.dart` and `server-ui/lib/pages/manage/nodes.dart` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 55 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–12 lines × 3) client/src/main/scala/stasis/client/service/components/Secrets.scala:44— client/src/main/scala/stasis/client/service/components/Secrets.scala:44-55 | client/src/main/scala/stasis/client/service/components/bootstrap/Secrets.scala:66-76 | client/src/main/scala/stasis/client/service/components/maintenance/Secrets.scala:43-54 — 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 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 (11–12 lines × 3) client-ui/lib/pages/components/credentials_form.dart:208— client-ui/lib/pages/components/credentials_form.dart:208-219 | client-ui/lib/pages/components/credentials_form.dart:227-238 | client-ui/lib/pages/components/credentials_form.dart:244-254 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (9 lines × 4) client/src/main/scala/stasis/client/service/ApplicationArguments.scala:304— client/src/main/scala/stasis/client/service/ApplicationArguments.scala:304-312 | client/src/main/scala/stasis/client/service/ApplicationArguments.scala:353-361 | client/src/main/scala/stasis/client/service/ApplicationArguments.scala:387-395 | client/src/main/scala/stasis/client/service/ApplicationArguments.scala:421-429 — 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 `client/src/main/scala/stasis/client/service/ApplicationArguments.scala:304` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (9 lines × 4) identity-ui/deployment/production/build.py:23— identity-ui/deployment/production/build.py:23-31 | identity-ui/deployment/production/stage.py:23-31 | server-ui/deployment/production/build.py:23-31 | server-ui/deployment/production/stage.py:23-31 — before extracting anything, compare `identity-ui/deployment/production/build.py` and `identity-ui/deployment/production/stage.py` as WHOLE FILES: 90% 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.
Duplicated block (8–9 lines × 2) server/src/main/scala/stasis/server/service/components/AuthenticatorsComponentLoader.scala:165— server/src/main/scala/stasis/server/service/components/AuthenticatorsComponentLoader.scala:165-172 | server/src/main/scala/stasis/server/service/components/AuthenticatorsComponentLoader.scala:175-183 — 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 `server/src/main/scala/stasis/server/service/components/AuthenticatorsComponentLoader.scala:175` 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 (8–9 lines × 2) client-ui/lib/pages/settings.dart:40— client-ui/lib/pages/settings.dart:40-47 | client-ui/lib/pages/settings.dart:418-426 — 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 (18 lines × 3) client-android/app/src/main/java/stasis/client_android/activities/fragments/HomeFragment.kt:163— client-android/app/src/main/java/stasis/client_android/activities/fragments/HomeFragment.kt:163-180 | client-android/app/src/main/java/stasis/client_android/activities/fragments/backup/DatasetEntryDetailsFragment.kt:90-107 | client-android/app/src/main/java/stasis/client_android/activities/fragments/backup/DatasetEntryListItemAdapter.kt:59-76 — 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.
Duplicated block (18 lines × 3) client-ui/lib/pages/components/client_credentials_reset_form.dart:147— client-ui/lib/pages/components/client_credentials_reset_form.dart:147-164 | client-ui/lib/pages/components/client_push_device_secret_form.dart:142-159 | client-ui/lib/pages/components/client_reencrypt_device_secret_form.dart:117-134 — before extracting anything, compare `client-ui/lib/pages/components/client_credentials_reset_form.dart` and `client-ui/lib/pages/components/client_push_device_secret_form.dart` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 271 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 × 3) client-android/app/src/main/java/stasis/client_android/persistence/rules/RuleViewModel.kt:34— client-android/app/src/main/java/stasis/client_android/persistence/rules/RuleViewModel.kt:34-41 | client-android/app/src/main/java/stasis/client_android/persistence/schedules/ActiveScheduleViewModel.kt:34-41 | client-android/app/src/main/java/stasis/client_android/persistence/schedules/LocalScheduleViewModel.kt:35-42 — 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 (8 lines × 3) client-android/app/src/main/java/stasis/client_android/persistence/rules/RuleViewModel.kt:52— client-android/app/src/main/java/stasis/client_android/persistence/rules/RuleViewModel.kt:52-59 | client-android/app/src/main/java/stasis/client_android/persistence/schedules/ActiveScheduleViewModel.kt:43-50 | client-android/app/src/main/java/stasis/client_android/persistence/schedules/LocalScheduleViewModel.kt:44-51 — 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 (23 lines × 2) client-cli/client_cli/api/default_client_api.py:208— client-cli/client_cli/api/default_client_api.py:208-230 | client-cli/client_cli/api/default_client_api.py:258-280 — 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 `client-cli/client_cli/api/default_client_api.py: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. 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 (23 lines × 2) client-ui/lib/model/datasets/dataset_definition.dart:21— client-ui/lib/model/datasets/dataset_definition.dart:21-43 | server-ui/lib/model/datasets/dataset_definition.dart:21-43 — 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 (53 lines × 2) client-ui/lib/pages/components/forms/policy_field.dart:37— client-ui/lib/pages/components/forms/policy_field.dart:37-89 | server-ui/lib/pages/manage/components/forms/policy_field.dart:37-89 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (53 lines × 2) server-ui/lib/pages/manage/components/forms/device_limits_field.dart:47— server-ui/lib/pages/manage/components/forms/device_limits_field.dart:47-99 | server-ui/lib/pages/manage/components/forms/user_limits_field.dart:54-106 — before extracting anything, compare `server-ui/lib/pages/manage/components/forms/device_limits_field.dart` and `server-ui/lib/pages/manage/components/forms/user_limits_field.dart` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 94 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 (19 lines × 2) client-ui/lib/pages/components/forms/date_time_field.dart:88— client-ui/lib/pages/components/forms/date_time_field.dart:88-106 | server-ui/lib/pages/manage/components/forms/date_time_field.dart:92-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.
Duplicated block (19 lines × 2) server-ui/lib/pages/manage/components/forms/device_limits_field.dart:33— server-ui/lib/pages/manage/components/forms/device_limits_field.dart:33-51 | server-ui/lib/pages/manage/components/forms/user_limits_field.dart:16-34 — before extracting anything, compare `server-ui/lib/pages/manage/components/forms/device_limits_field.dart` and `server-ui/lib/pages/manage/components/forms/user_limits_field.dart` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 94 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 (13 lines × 4) client-ui/lib/pages/backup.dart:110— client-ui/lib/pages/backup.dart:110-122 | client-ui/lib/pages/components/backup_entry_metadata.dart:159-171 | client-ui/lib/pages/operations.dart:57-69 | client-ui/lib/pages/schedules.dart:61-73 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times.
Duplicated block (13 lines × 4) server-ui/lib/pages/default/home.dart:229— server-ui/lib/pages/default/home.dart:229-241 | server-ui/lib/pages/manage/commands.dart:154-166 | server-ui/lib/pages/manage/commands.dart:246-258 | server-ui/lib/pages/manage/nodes.dart:103-115 — before extracting anything, compare `server-ui/lib/pages/default/home.dart` and `server-ui/lib/pages/manage/nodes.dart` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 40 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 (6 lines × 3) client-ui/lib/pages/components/dataset_definition_summary.dart:28— client-ui/lib/pages/components/dataset_definition_summary.dart:28-33 | client-ui/lib/pages/components/dataset_entry_summary.dart:21-26 | client-ui/lib/pages/home.dart:181-186 — 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.
Duplicated block (6 lines × 3) client-ui/lib/pages/components/operation_summary.dart:108— client-ui/lib/pages/components/operation_summary.dart:108-113 | client-ui/lib/pages/components/operation_summary.dart:132-137 | client-ui/lib/pages/components/operation_summary.dart:156-161 — 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.
Off the main sequence: :lib — :lib: abstractness 0.20, instability 0.00, distance 0.80 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
Off the main sequence: proto — proto: abstractness 0.20, instability 0.00, distance 0.80 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
Low cohesion: DefaultServerApiEndpointClient (LCOM4 9) client/src/main/scala/stasis/client/api/clients/DefaultServerApiEndpointClient.scala:45— DefaultServerApiEndpointClient's methods fall into 9 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 9 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: Default (LCOM4 5) core/src/main/scala/stasis/core/routing/Metrics.scala:75— Default's methods fall into 5 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 5 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
AC7 · A11y enforcement· Accessibility enforcement below the top rung · ×1
Accessibility enforcement below the top rung — No accessibility enforcement found — no accessibility linting at author time and no automated accessibility check in tests or CI. Add your UI toolkit's own accessibility assertion to the test suite (Flutter `meetsGuideline`, Espresso `AccessibilityChecks`, XCTest `performAccessibilityAudit`), then gate that test in the pipeline. What was searched, so you can tell an absence from a miss: the 2 markup file(s) this pass actually assessed, the linter configuration checked in beside them, and this repository's test and CI files — matched by name against the accessibility checkers this dimension carries. An audit run outside the repository, a hosted scanner, or a check whose name is not one of those, is not seen here.
AXR1 · Runtime accessibility (rendered)· WCAG 4.1.2 reproducibly failed on a screen of the running app · ×1
WCAG 4.1.2 reproducibly failed on a screen of the running app — Accessibility-tree rule(s) android-accessible-name, android-editable-name failed on: /FrameLayout[0]/LinearLayout[0]/FrameLayout[0]/LinearLayout[0]/FrameLayout[0]/LinearLayout[0]/FrameLayout[0]/FrameLayout[0]/ViewGroup[0]/ScrollView[1]/LinearLayout[0]/LinearLayout[0]/FrameLayout[0]/LinearLayout[1]/ImageButton[0]#stasis.client.android:id/text_input_start_icon. Read from the Android accessibility tree on an emulator (advisory — not scored); fix and re-scan to verify it clears.
MainActivity.initNavigation (cyclomatic 48) client-android/app/src/main/java/stasis/client_android/activities/MainActivity.kt:136— MainActivity.initNavigation has cyclomatic complexity 48 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
Secrets.apply (cyclomatic 37) client/src/main/scala/stasis/client/service/components/maintenance/Secrets.scala:34— Secrets.apply has cyclomatic complexity 37 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
Devices.routes (cyclomatic 35) server/src/main/scala/stasis/server/api/routes/Devices.scala:40— Devices.routes has cyclomatic complexity 35 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
_ClientBootstrapFormState.build (cyclomatic 35) client-ui/lib/pages/components/client_bootstrap_form.dart:47— _ClientBootstrapFormState.build has cyclomatic complexity 35 (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.
Users.routes (cyclomatic 31) server/src/main/scala/stasis/server/api/routes/Users.scala:31— Users.routes has cyclomatic complexity 31 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
_ClientCredentialsResetFormState.build (cyclomatic 31) client-ui/lib/pages/components/client_credentials_reset_form.dart:44— _ClientCredentialsResetFormState.build has cyclomatic complexity 31 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
SettingsFragment.onCreatePreferences (cyclomatic 28) client-android/app/src/main/java/stasis/client_android/activities/fragments/SettingsFragment.kt:88— SettingsFragment.onCreatePreferences has cyclomatic complexity 28 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
_ClientReEncryptDeviceSecretFormState.build (cyclomatic 25) client-ui/lib/pages/components/client_reencrypt_device_secret_form.dart:43— _ClientReEncryptDeviceSecretFormState.build 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.
Operations.routes (cyclomatic 24) client/src/main/scala/stasis/client/api/http/routes/Operations.scala:39— Operations.routes has cyclomatic complexity 24 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
TrackingHandler.handleMessage (cyclomatic 24) client-android/app/src/main/java/stasis/client_android/tracking/DefaultBackupTracker.kt:202— TrackingHandler.handleMessage has cyclomatic complexity 24 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
Secrets.apply (cyclomatic 23) client/src/main/scala/stasis/client/service/components/bootstrap/Secrets.scala:36— Secrets.apply has cyclomatic complexity 23 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
DefaultOperationScheduler.scheduler (cyclomatic 22) client/src/main/scala/stasis/client/ops/scheduling/DefaultOperationScheduler.scala:93— DefaultOperationScheduler.scheduler has cyclomatic complexity 22 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
ApplicationArguments.parser (cyclomatic 20) client/src/main/scala/stasis/client/service/ApplicationArguments.scala:213— ApplicationArguments.parser has cyclomatic complexity 20 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
ViaStdIn.retrieveCredentials (cyclomatic 20) client/src/main/scala/stasis/client/service/components/maintenance/init/ViaStdIn.scala:12— ViaStdIn.retrieveCredentials has cyclomatic complexity 20 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
ServiceHandler.handleMessage (cyclomatic 20) client-android/app/src/main/java/stasis/client_android/scheduling/SchedulerService.kt:90— ServiceHandler.handleMessage 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.
TrackingHandler.handleMessage (cyclomatic 20) client-android/app/src/main/java/stasis/client_android/tracking/DefaultRecoveryTracker.kt:169— TrackingHandler.handleMessage has cyclomatic complexity 20 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
DefaultCredentialsProvider.provider (cyclomatic 19) client/src/main/scala/stasis/client/security/DefaultCredentialsProvider.scala:124— DefaultCredentialsProvider.provider has cyclomatic complexity 19 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
Secrets.apply (cyclomatic 19) client/src/main/scala/stasis/client/service/components/Secrets.scala:37— Secrets.apply has cyclomatic complexity 19 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
_CredentialsFormState.build (cyclomatic 19) identity-ui/lib/pages/authorize/credentials_form.dart:47— _CredentialsFormState.build 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.
_ClientPushDeviceSecretFormState.build (cyclomatic 18) client-ui/lib/pages/components/client_push_device_secret_form.dart:43— _ClientPushDeviceSecretFormState.build 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.
OperationDetailsFragment.onCreateView (cyclomatic 17) client-android/app/src/main/java/stasis/client_android/activities/fragments/operations/OperationDetailsFragment.kt:46— OperationDetailsFragment.onCreateView 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.
_ClientPullDeviceSecretFormState.build (cyclomatic 16) client-ui/lib/pages/components/client_pull_device_secret_form.dart:42— _ClientPullDeviceSecretFormState.build 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.
Secrets.apply (cognitive 277) client/src/main/scala/stasis/client/service/components/maintenance/Secrets.scala:34— Secrets.apply has cognitive complexity 277 (threshold 15). Drivers by points: loops 20 (194 pts), match/switch 8 (66 pts), if/else 3 (17 pts) (nesting depth added 246). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
Secrets.apply (cognitive 201) client/src/main/scala/stasis/client/service/components/bootstrap/Secrets.scala:36— Secrets.apply has cognitive complexity 201 (threshold 15). Drivers by points: loops 18 (185 pts), match/switch 2 (16 pts) (nesting depth added 181). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
Secrets.apply (cognitive 138) client/src/main/scala/stasis/client/service/components/Secrets.scala:37— Secrets.apply has cognitive complexity 138 (threshold 15). Drivers by points: loops 16 (127 pts), match/switch 1 (11 pts) (nesting depth added 121). 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.
Parameters.process (cognitive 67) client/src/main/scala/stasis/client/service/components/bootstrap/Parameters.scala:56— Parameters.process has cognitive complexity 67 (threshold 15). Drivers by points: loops 11 (66 pts), match/switch 1 (nesting depth added 55). 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.
_ClientBootstrapFormState.build (cognitive 50) client-ui/lib/pages/components/client_bootstrap_form.dart:47— _ClientBootstrapFormState.build has cognitive complexity 50 (threshold 15). Drivers by points: if/else 30 (31 pts), ternaries 10 (14 pts), boolean chains 5 (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.
Credentials.apply (cognitive 46) client/src/main/scala/stasis/client/service/components/maintenance/Credentials.scala:23— Credentials.apply has cognitive complexity 46 (threshold 15). Drivers by points: loops 8 (44 pts), if/else 1, match/switch 1 (nesting depth added 36). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
ServerPersistence.migrate (cognitive 45) server/src/main/scala/stasis/server/service/ServerPersistence.scala:129— ServerPersistence.migrate has cognitive complexity 45 (threshold 15). Drivers by points: loops 9 (45 pts) (nesting depth added 36). 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. This shape REPEATS in the file: 2 other methods here (ServerPersistence.init, ServerPersistence.drop) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
ServerPersistence.init (cognitive 45) server/src/main/scala/stasis/server/service/ServerPersistence.scala:152— ServerPersistence.init has cognitive complexity 45 (threshold 15). Drivers by points: loops 9 (45 pts) (nesting depth added 36). 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. This shape REPEATS in the file: 2 other methods here (ServerPersistence.migrate, ServerPersistence.drop) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
ServerPersistence.drop (cognitive 45) server/src/main/scala/stasis/server/service/ServerPersistence.scala:167— ServerPersistence.drop has cognitive complexity 45 (threshold 15). Drivers by points: loops 9 (45 pts) (nesting depth added 36). 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. This shape REPEATS in the file: 2 other methods here (ServerPersistence.migrate, ServerPersistence.init) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
_ClientCredentialsResetFormState.build (cognitive 45) client-ui/lib/pages/components/client_credentials_reset_form.dart:44— _ClientCredentialsResetFormState.build has cognitive complexity 45 (threshold 15). Drivers by points: if/else 26 (27 pts), ternaries 10 (14 pts), boolean chains 4 (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.
ViaStdIn.retrieveCredentials (cognitive 44) client/src/main/scala/stasis/client/service/components/maintenance/init/ViaStdIn.scala:12— ViaStdIn.retrieveCredentials has cognitive complexity 44 (threshold 15). Drivers by points: loops 12 (36 pts), if/else 4, match/switch 4 (nesting depth added 24). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
Devices.routes (cognitive 41) server/src/main/scala/stasis/server/api/routes/Devices.scala:40— Devices.routes has cognitive complexity 41 (threshold 15). Drivers by points: loops 6 (15 pts), match/switch 12 (15 pts), if/else 11 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
_ClientReEncryptDeviceSecretFormState.build (cognitive 38) client-ui/lib/pages/components/client_reencrypt_device_secret_form.dart:43— _ClientReEncryptDeviceSecretFormState.build has cognitive complexity 38 (threshold 15). Drivers by points: if/else 20 (21 pts), ternaries 10 (14 pts), boolean chains 3 (nesting depth added 5). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
ServiceHandler.handleMessage (cognitive 36) client-android/app/src/main/java/stasis/client_android/scheduling/SchedulerService.kt:90— ServiceHandler.handleMessage has cognitive complexity 36 (threshold 15). Drivers by points: if/else 11 (23 pts), match/switch 6 (13 pts) (nesting depth added 19). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
SettingsFragment.onCreatePreferences (cognitive 35) client-android/app/src/main/java/stasis/client_android/activities/fragments/SettingsFragment.kt:88— SettingsFragment.onCreatePreferences has cognitive complexity 35 (threshold 15). Drivers by points: if/else 22 (24 pts), match/switch 6 (11 pts) (nesting depth added 7). 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.
DeviceBootstrap.execute (cognitive 33) server/src/main/scala/stasis/server/api/routes/DeviceBootstrap.scala:142— DeviceBootstrap.execute has cognitive complexity 33 (threshold 15). Drivers by points: loops 7 (24 pts), match/switch 4 (9 pts) (nesting depth added 22). 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.
MainActivity.initNavigation (cognitive 29) client-android/app/src/main/java/stasis/client_android/activities/MainActivity.kt:136— MainActivity.initNavigation has cognitive complexity 29 (threshold 15). Drivers by points: if/else 14 (15 pts), match/switch 7 (10 pts), boolean chains 4 (nesting depth added 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.
Operations.routes (cognitive 28) client/src/main/scala/stasis/client/api/http/routes/Operations.scala:39— Operations.routes has cognitive complexity 28 (threshold 15). Drivers by points: loops 9 (14 pts), match/switch 7 (11 pts), if/else 3 (nesting depth added 9). 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.
OperationDetailsFragment.onCreateView (cognitive 27) client-android/app/src/main/java/stasis/client_android/activities/fragments/operations/OperationDetailsFragment.kt:46— OperationDetailsFragment.onCreateView has cognitive complexity 27 (threshold 15). Drivers by points: if/else 17 (19 pts), match/switch 5 (6 pts), boolean chains 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, 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.
DefaultRouter.push (cognitive 25) core/src/main/scala/stasis/core/routing/DefaultRouter.scala:53— DefaultRouter.push has cognitive complexity 25 (threshold 15). Drivers by points: loops 2 (9 pts), if/else 4 (8 pts), match/switch 3 (8 pts) (nesting depth added 16). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
_ClientPushDeviceSecretFormState.build (cognitive 25) client-ui/lib/pages/components/client_push_device_secret_form.dart:43— _ClientPushDeviceSecretFormState.build has cognitive complexity 25 (threshold 15). Drivers by points: if/else 15, ternaries 7 (8 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.
_ClientAppState.build (cognitive 24) client-ui/lib/client_app.dart:37— _ClientAppState.build has cognitive complexity 24 (threshold 15). Drivers by points: if/else 10 (21 pts), error handling 2, boolean chains 1 (nesting depth added 11). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
DefaultRouter.discard (cognitive 23) core/src/main/scala/stasis/core/routing/DefaultRouter.scala:281— DefaultRouter.discard has cognitive complexity 23 (threshold 15). Drivers by points: loops 3 (15 pts), if/else 4 (7 pts), match/switch 1 (nesting depth added 15). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
_CredentialsFormState.build (cognitive 23) identity-ui/lib/pages/authorize/credentials_form.dart:47— _CredentialsFormState.build has cognitive complexity 23 (threshold 15). Drivers by points: if/else 13, boolean chains 5, ternaries 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.
LoginFragment.onCreateView (cognitive 21) client-android/app/src/main/java/stasis/client_android/activities/fragments/login/LoginFragment.kt:38— LoginFragment.onCreateView has cognitive complexity 21 (threshold 15). Drivers by points: if/else 9 (11 pts), match/switch 4 (8 pts), boolean chains 2 (nesting depth added 6). 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.
ConfigFactory._loadFromHocon (cognitive 21) client-ui/lib/config/config.dart:111— ConfigFactory._loadFromHocon has cognitive complexity 21 (threshold 15). Drivers by points: if/else 10 (17 pts), boolean chains 2, error handling 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.
_ClientPullDeviceSecretFormState.build (cognitive 21) client-ui/lib/pages/components/client_pull_device_secret_form.dart:42— _ClientPullDeviceSecretFormState.build has cognitive complexity 21 (threshold 15). Drivers by points: if/else 11, ternaries 7 (8 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.
Users.routes (cognitive 20) server/src/main/scala/stasis/server/api/routes/Users.scala:31— Users.routes has cognitive complexity 20 (threshold 15). Drivers by points: match/switch 10 (11 pts), if/else 8 (9 pts) (nesting depth added 2). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
ItemViewHolder.bind (cognitive 20) client-android/app/src/main/java/stasis/client_android/activities/fragments/operations/OperationListItemAdapter.kt:68— ItemViewHolder.bind has cognitive complexity 20 (threshold 15). Drivers by points: if/else 15 (17 pts), boolean chains 2, match/switch 1 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
_UpdateUserCredentialsFormState._actionHandler (cognitive 20) client-ui/lib/pages/components/update_user_credentials_form.dart:169— _UpdateUserCredentialsFormState._actionHandler has cognitive complexity 20 (threshold 15). Drivers by points: if/else 6 (13 pts), error handling 2 (6 pts), boolean chains 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ApplicationArguments.parser (cognitive 19) client/src/main/scala/stasis/client/service/ApplicationArguments.scala:213— ApplicationArguments.parser has cognitive complexity 19 (threshold 15). Drivers by points: match/switch 19. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
ItemViewHolder.bind (cognitive 19) client-android/app/src/main/java/stasis/client_android/activities/fragments/schedules/ScheduleListItemAdapter.kt:82— ItemViewHolder.bind has cognitive complexity 19 (threshold 15). Drivers by points: if/else 11 (17 pts), boolean chains 1, match/switch 1 (nesting depth added 6). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
AnalyticsDialogFragment.onCreateView (cognitive 19) client-android/app/src/main/java/stasis/client_android/activities/fragments/settings/AnalyticsDialogFragment.kt:44— AnalyticsDialogFragment.onCreateView has cognitive complexity 19 (threshold 15). Drivers by points: if/else 12 (18 pts), match/switch 1 (nesting depth added 6). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
refresh_assets.main (cognitive 19) assets/refresh_assets.py:89— refresh_assets.main has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (11 pts), loops 3 (7 pts), ternaries 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.
_UpdateUserCredentialsFormState.build (cognitive 19) client-ui/lib/pages/components/update_user_credentials_form.dart:37— _UpdateUserCredentialsFormState.build has cognitive complexity 19 (threshold 15). Drivers by points: if/else 13, boolean chains 4, ternaries 1 (2 pts) (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.
User.routes (cognitive 18) client/src/main/scala/stasis/client/api/http/routes/User.scala:20— User.routes has cognitive complexity 18 (threshold 15). Drivers by points: loops 5 (14 pts), if/else 4 (nesting depth added 9). 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.
Certificates.regenerateApiCertificate (cognitive 18) client/src/main/scala/stasis/client/service/components/maintenance/Certificates.scala:36— Certificates.regenerateApiCertificate has cognitive complexity 18 (threshold 15). Drivers by points: loops 4 (14 pts), match/switch 2 (3 pts), if/else 1 (nesting depth added 11). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
_CredentialsFormState.build (cognitive 18) client-ui/lib/pages/components/credentials_form.dart:37— _CredentialsFormState.build has cognitive complexity 18 (threshold 15). Drivers by points: if/else 14, boolean chains 2, ternaries 1 (2 pts) (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.
_OperationDetailsState.build (cognitive 18) client-ui/lib/pages/components/operation_details.dart:30— _OperationDetailsState.build has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (10 pts), ternaries 3 (6 pts), boolean chains 2 (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.
_OperationDetailsState._renderStages (cognitive 18) client-ui/lib/pages/components/operation_details.dart:215— _OperationDetailsState._renderStages has cognitive complexity 18 (threshold 15). Drivers by points: ternaries 4 (9 pts), if/else 5 (6 pts), match/switch 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.
_UserLimitsFieldState.build (cognitive 18) server-ui/lib/pages/manage/components/forms/user_limits_field.dart:16— _UserLimitsFieldState.build has cognitive complexity 18 (threshold 15). Drivers by points: if/else 13 (15 pts), boolean chains 2, 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.
DefaultOperationScheduler.scheduler (cognitive 17) client/src/main/scala/stasis/client/ops/scheduling/DefaultOperationScheduler.scala:93— DefaultOperationScheduler.scheduler has cognitive complexity 17 (threshold 15). Drivers by points: match/switch 6 (12 pts), loops 2 (5 pts) (nesting depth added 9). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
DefaultRouter.pull (cognitive 17) core/src/main/scala/stasis/core/routing/DefaultRouter.scala:168— DefaultRouter.pull has cognitive complexity 17 (threshold 15). Drivers by points: match/switch 6 (13 pts), if/else 3 (4 pts) (nesting depth added 8). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
BootstrapProvideCodeFragment.onCreateView (cognitive 17) client-android/app/src/main/java/stasis/client_android/activities/fragments/bootstrap/BootstrapProvideCodeFragment.kt:64— BootstrapProvideCodeFragment.onCreateView has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (8 pts), match/switch 7 (8 pts), boolean chains 1 (nesting depth added 2). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
api.create_client_api (cognitive 17) client-cli/client_cli/api/__init__.py:16— api.create_client_api has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (10 pts), error handling 1 (3 pts), boolean chains 2, ternaries 1 (2 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
_LoginState.build (cognitive 17) client-ui/lib/pages/login.dart:35— _LoginState.build has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (14 pts), boolean chains 3 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DefaultServerApiEndpointClient.createDatasetDefinition (cognitive 16) client/src/main/scala/stasis/client/api/clients/DefaultServerApiEndpointClient.scala:64— DefaultServerApiEndpointClient.createDatasetDefinition has cognitive complexity 16 (threshold 15). Drivers by points: loops 4 (14 pts), if/else 2 (nesting depth added 10). 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.
RefreshTokenConsumption.consumeRefreshToken (cognitive 16) identity/src/main/scala/stasis/identity/api/oauth/directives/RefreshTokenConsumption.scala:34— RefreshTokenConsumption.consumeRefreshToken has cognitive complexity 16 (threshold 15). Drivers by points: loops 4 (10 pts), if/else 2 (3 pts), match/switch 2 (3 pts) (nesting depth added 8). 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.
operations._transform_stages_to_files (cognitive 16) client-cli/client_cli/render/default/operations.py:192— operations._transform_stages_to_files has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (12 pts), loops 2 (3 pts), boolean chains 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.
ClassTooLong: SettingsFragment client-android/app/src/main/java/stasis/client_android/activities/fragments/SettingsFragment.kt:70— ClassTooLong — 514 significant lines (blank, comment-only and punctuation-only lines excluded), 9 methods. The bar is 400 significant lines; this is 114 over it, 1.29× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
FileTooLong: fragments/SettingsFragment.kt client-android/app/src/main/java/stasis/client_android/activities/fragments/SettingsFragment.kt— FileTooLong — 581 significant lines (blank, comment-only and punctuation-only lines excluded), about 88% of them inside a single declaration: SettingsFragment (70-831). The bar is 500 significant lines; this is 81 over it, 1.16× 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.
Change coupling: default_client_api.py ↔ inactive_client_api.py client-cli/client_cli/api/default_client_api.py:1— `client-cli/client_cli/api/default_client_api.py` and `client-cli/client_cli/api/inactive_client_api.py` change together 100% of the time (14 of the 14 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency between them. They sit in the same directory, but in this ecosystem each file is its own module — a sibling reference still needs an import — so the missing import edge is real: the coupling runs through shared behaviour, not a declared dependency. If they duplicate structure, extract the common part into one unit; otherwise the coupling is hidden and worth breaking. You can check this without leaving the row: of the 14 shared commits counted here, the most recent 3 are `fa874e89` [client] Add support for sending analytics on demand; `db9857c4` [client-cli] Update to render client analytics information; `8183ecfa` [client-cli] Add support for handling device commands — run `git show` on any of them.
D4 · Code Duplication· Near-duplicate member family (6 members, 73 shared lines) · ×1
Near-duplicate member family (6 members, 73 shared lines) client-ui/lib/pages/components/client_bootstrap_form.dart:47— client-ui/lib/pages/components/client_bootstrap_form.dart:47-395 | client-ui/lib/pages/components/client_credentials_reset_form.dart:44-352 | client-ui/lib/pages/components/client_pull_device_secret_form.dart:42-270 | client-ui/lib/pages/components/client_push_device_secret_form.dart:43-304 | client-ui/lib/pages/components/client_reencrypt_device_secret_form.dart:43-318 | client-ui/lib/pages/components/client_regenerate_api_certificate_form.dart:39-191 — These 6 members are variants of one another: a block of 73 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 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· Near-duplicate member family (4 members, 45 shared lines) · ×1
Near-duplicate member family (4 members, 45 shared lines) client-ui/lib/pages/components/forms/duration_field.dart:35— client-ui/lib/pages/components/forms/duration_field.dart:35-84 | client-ui/lib/pages/components/forms/file_size_field.dart:42-91 | server-ui/lib/pages/manage/components/forms/duration_field.dart:35-84 | server-ui/lib/pages/manage/components/forms/file_size_field.dart:42-91 — These 4 members are variants of one another: a block of 45 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
D4 · Code Duplication· Edited copy of a member (17 corresponding lines) · ×1
Edited copy of a member (17 corresponding lines) client-ui/lib/api/default_client_api.dart:236— client-ui/lib/api/default_client_api.dart:236-255 | client-ui/lib/api/default_client_api.dart:257-275 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (26 corresponding lines) · ×1
Edited copy of a member (26 corresponding lines) client-cli/client_cli/api/__init__.py:17— client-cli/client_cli/api/__init__.py:17-79 | client-cli/client_cli/api/__init__.py:83-135 — These two members are one piece of code written twice and then edited apart: 26 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Members sharing a duplicated core (42 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (42 members, 50+ identical tokens) client-ui/lib/pages/backup.dart:162— client-ui/lib/pages/backup.dart:162-246 | client-ui/lib/pages/backup_entries.dart:26-139 | client-ui/lib/pages/components/dataset_metadata_entity_summary.dart:118-142 | client-ui/lib/pages/recover.dart:31-160 | client-ui/lib/pages/search.dart:32-236 | identity-ui/lib/pages/manage/apis.dart:69-105 | identity-ui/lib/pages/manage/apis.dart:107-143 | identity-ui/lib/pages/manage/clients.dart:112-179 | identity-ui/lib/pages/manage/clients.dart:181-231 | identity-ui/lib/pages/manage/clients.dart:233-272 | identity-ui/lib/pages/manage/clients.dart:274-306 | identity-ui/lib/pages/manage/codes.dart:69-101 | REDACTED:205-253 | REDACTED:322-354 | identity-ui/lib/pages/manage/tokens.dart:71-103 | server-ui/lib/pages/default/home.dart:222-280 | server-ui/lib/pages/default/home.dart:282-317 | server-ui/lib/pages/manage/codes.dart:91-122 | server-ui/lib/pages/manage/commands.dart:145-201 | server-ui/lib/pages/manage/commands.dart:235-275 | server-ui/lib/pages/manage/definitions.dart:130-207 | server-ui/lib/pages/manage/definitions.dart:235-300 | server-ui/lib/pages/manage/definitions.dart:302-332 | server-ui/lib/pages/manage/device_keys.dart:90-120 | server-ui/lib/pages/manage/devices.dart:223-269 | server-ui/lib/pages/manage/devices.dart:271-343 | server-ui/lib/pages/manage/devices.dart:450-490 | server-ui/lib/pages/manage/devices.dart:492-532 | server-ui/lib/pages/manage/devices.dart:534-566 | server-ui/lib/pages/manage/entries.dart:108-135 | server-ui/lib/pages/manage/nodes.dart:99-131 | server-ui/lib/pages/manage/nodes.dart:133-171 | server-ui/lib/pages/manage/nodes.dart:173-205 | server-ui/lib/pages/manage/schedules.dart:113-175 | server-ui/lib/pages/manage/schedules.dart:177-233 | server-ui/lib/pages/manage/schedules.dart:235-267 | server-ui/lib/pages/manage/users.dart:209-270 | server-ui/lib/pages/manage/users.dart:272-310 | server-ui/lib/pages/manage/users.dart:312-350 | server-ui/lib/pages/manage/users.dart:352-391 | server-ui/lib/pages/manage/users.dart:393-430 | server-ui/lib/pages/manage/users.dart:432-464 — These 42 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 42 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 42 times.
D4 · Code Duplication· Members sharing a duplicated core (8 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (8 members, 50+ identical tokens) client-ui/lib/pages/components/client_bootstrap_form.dart:462— client-ui/lib/pages/components/client_bootstrap_form.dart:462-471 | client-ui/lib/pages/components/client_credentials_reset_form.dart:410-419 | client-ui/lib/pages/components/client_pull_device_secret_form.dart:327-336 | client-ui/lib/pages/components/client_push_device_secret_form.dart:362-371 | client-ui/lib/pages/components/client_reencrypt_device_secret_form.dart:375-384 | client-ui/lib/pages/components/client_regenerate_api_certificate_form.dart:237-246 | client-ui/lib/pages/components/credentials_form.dart:349-358 | client-ui/lib/pages/components/update_user_credentials_form.dart:226-235 — These 8 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 8 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 8 times.
Duplicated block (52 lines × 2) identity/src/main/scala/stasis/identity/api/oauth/AuthorizationCodeGrant.scala:131— identity/src/main/scala/stasis/identity/api/oauth/AuthorizationCodeGrant.scala:131-182 | identity/src/main/scala/stasis/identity/api/oauth/PkceAuthorizationCodeGrant.scala:137-188 — before extracting anything, compare `identity/src/main/scala/stasis/identity/api/oauth/AuthorizationCodeGrant.scala` and `identity/src/main/scala/stasis/identity/api/oauth/PkceAuthorizationCodeGrant.scala` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 118 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 `identity/src/main/scala/stasis/identity/api/oauth/AuthorizationCodeGrant.scala:131` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (41 lines × 2) identity/src/main/scala/stasis/identity/api/oauth/AuthorizationCodeGrant.scala:83— identity/src/main/scala/stasis/identity/api/oauth/AuthorizationCodeGrant.scala:83-123 | identity/src/main/scala/stasis/identity/api/oauth/PkceAuthorizationCodeGrant.scala:89-129 — before extracting anything, compare `identity/src/main/scala/stasis/identity/api/oauth/AuthorizationCodeGrant.scala` and `identity/src/main/scala/stasis/identity/api/oauth/PkceAuthorizationCodeGrant.scala` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 118 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 `identity/src/main/scala/stasis/identity/api/oauth/AuthorizationCodeGrant.scala: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 (35 lines × 2) identity/src/main/scala/stasis/identity/api/oauth/RefreshTokenGrant.scala:52— identity/src/main/scala/stasis/identity/api/oauth/RefreshTokenGrant.scala:52-86 | identity/src/main/scala/stasis/identity/api/oauth/ResourceOwnerPasswordCredentialsGrant.scala:54-88 — before extracting anything, compare `identity/src/main/scala/stasis/identity/api/oauth/RefreshTokenGrant.scala` and `identity/src/main/scala/stasis/identity/api/oauth/ResourceOwnerPasswordCredentialsGrant.scala` as WHOLE FILES: 84% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. 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 `identity/src/main/scala/stasis/identity/api/oauth/RefreshTokenGrant.scala:52` 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 (3–21 lines × 4) client/src/main/scala/stasis/client/service/components/Secrets.scala:40— client/src/main/scala/stasis/client/service/components/Secrets.scala:40-60 | client/src/main/scala/stasis/client/service/components/bootstrap/Secrets.scala:54-56 | client/src/main/scala/stasis/client/service/components/maintenance/Credentials.scala:28-31 | client/src/main/scala/stasis/client/service/components/maintenance/Secrets.scala:39-59 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `client/src/main/scala/stasis/client/service/components/Secrets.scala: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 (21 lines × 2) server/src/main/scala/stasis/server/api/routes/Users.scala:140— server/src/main/scala/stasis/server/api/routes/Users.scala:140-160 | server/src/main/scala/stasis/server/api/routes/Users.scala:257-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 `server/src/main/scala/stasis/server/api/routes/Users.scala:140` 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 × 3) server/src/main/scala/stasis/server/api/routes/Users.scala:139— server/src/main/scala/stasis/server/api/routes/Users.scala:139-158 | server/src/main/scala/stasis/server/api/routes/Users.scala:193-212 | server/src/main/scala/stasis/server/api/routes/Users.scala:256-275 — 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 `server/src/main/scala/stasis/server/api/routes/Users.scala:139` 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, `server/src/main/scala/stasis/server/api/routes/Users.scala:214` calls `onSuccess` and `server/src/main/scala/stasis/server/api/routes/Users.scala:159` 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 (16–18 lines × 2) client/src/main/scala/stasis/client/ops/commands/DefaultCommandProcessor.scala:111— client/src/main/scala/stasis/client/ops/commands/DefaultCommandProcessor.scala:111-128 | client/src/main/scala/stasis/client/ops/commands/DefaultCommandProcessor.scala:148-163 — 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 `client/src/main/scala/stasis/client/ops/commands/DefaultCommandProcessor.scala:111` 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–13 lines × 2) server/src/main/scala/stasis/server/api/routes/DatasetDefinitions.scala:60— server/src/main/scala/stasis/server/api/routes/DatasetDefinitions.scala:60-71 | server/src/main/scala/stasis/server/api/routes/DatasetDefinitions.scala:152-164 — 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 `server/src/main/scala/stasis/server/api/routes/DatasetDefinitions.scala:60` 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 (4–12 lines × 3) identity/src/main/scala/stasis/identity/api/oauth/AuthorizationCodeGrant.scala:69— identity/src/main/scala/stasis/identity/api/oauth/AuthorizationCodeGrant.scala:69-80 | identity/src/main/scala/stasis/identity/api/oauth/ImplicitGrant.scala:51-54 | identity/src/main/scala/stasis/identity/api/oauth/PkceAuthorizationCodeGrant.scala:73-83 — before extracting anything, compare `identity/src/main/scala/stasis/identity/api/oauth/AuthorizationCodeGrant.scala` and `identity/src/main/scala/stasis/identity/api/oauth/PkceAuthorizationCodeGrant.scala` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 118 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 `identity/src/main/scala/stasis/identity/api/oauth/AuthorizationCodeGrant.scala: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. 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 (10–11 lines × 2) server/src/main/scala/stasis/server/api/routes/Schedules.scala:69— server/src/main/scala/stasis/server/api/routes/Schedules.scala:69-79 | server/src/main/scala/stasis/server/api/routes/Schedules.scala:87-96 — 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 `server/src/main/scala/stasis/server/api/routes/Schedules.scala:69` 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, `server/src/main/scala/stasis/server/api/routes/Schedules.scala:84` calls `concat` and `server/src/main/scala/stasis/server/api/routes/Schedules.scala:66` 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 (7–8 lines × 4) client/src/main/scala/stasis/client/service/components/ApiClients.scala:46— client/src/main/scala/stasis/client/service/components/ApiClients.scala:46-53 | client/src/main/scala/stasis/client/service/components/ApiClients.scala:66-73 | client/src/main/scala/stasis/client/service/components/bootstrap/Secrets.scala:109-115 | client/src/main/scala/stasis/client/service/components/maintenance/Secrets.scala:126-133 — `client/src/main/scala/stasis/client/service/components/bootstrap/Secrets.scala` and `client/src/main/scala/stasis/client/service/components/maintenance/Secrets.scala` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 5 separate duplicated blocks between them, totalling at least 62 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `client/src/main/scala/stasis/client/service/components/ApiClients.scala:46` 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, `client/src/main/scala/stasis/client/service/components/ApiClients.scala:45` calls `getInt` and `client/src/main/scala/stasis/client/service/components/bootstrap/Secrets.scala:108` 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 (7–8 lines × 2) client/src/main/scala/stasis/client/api/clients/DefaultServerBootstrapEndpointClient.scala:86— client/src/main/scala/stasis/client/api/clients/DefaultServerBootstrapEndpointClient.scala:86-93 | core/src/main/scala/stasis/core/discovery/http/HttpServiceDiscoveryClient.scala:94-100 — 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 `client/src/main/scala/stasis/client/api/clients/DefaultServerBootstrapEndpointClient.scala:86` 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 × 3) identity/src/main/scala/stasis/identity/api/oauth/AuthorizationCodeGrant.scala:64— identity/src/main/scala/stasis/identity/api/oauth/AuthorizationCodeGrant.scala:64-68 | identity/src/main/scala/stasis/identity/api/oauth/ImplicitGrant.scala:46-50 | identity/src/main/scala/stasis/identity/api/oauth/PkceAuthorizationCodeGrant.scala:68-72 — before extracting anything, compare `identity/src/main/scala/stasis/identity/api/oauth/AuthorizationCodeGrant.scala` and `identity/src/main/scala/stasis/identity/api/oauth/PkceAuthorizationCodeGrant.scala` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 118 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 `identity/src/main/scala/stasis/identity/api/oauth/AuthorizationCodeGrant.scala:64` 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 (29 lines × 2) server/src/main/scala/stasis/server/persistence/datasets/DatasetDefinitionStore.scala:66— server/src/main/scala/stasis/server/persistence/datasets/DatasetDefinitionStore.scala:66-94 | server/src/main/scala/stasis/server/persistence/datasets/DatasetEntryStore.scala:88-116 — 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 (70–72 lines × 2) client-android/app/src/main/java/stasis/client_android/tracking/DefaultBackupTracker.kt:240— client-android/app/src/main/java/stasis/client_android/tracking/DefaultBackupTracker.kt:240-309 | client-android/app/src/main/java/stasis/client_android/tracking/DefaultRecoveryTracker.kt:229-300 — 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 `client-android/app/src/main/java/stasis/client_android/tracking/DefaultBackupTracker.kt:240` 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 (32 lines × 2) client-android/app/src/main/java/stasis/client_android/activities/fragments/HomeFragment.kt:160— client-android/app/src/main/java/stasis/client_android/activities/fragments/HomeFragment.kt:160-191 | client-android/app/src/main/java/stasis/client_android/activities/fragments/backup/DatasetEntryDetailsFragment.kt:87-118 — 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 `client-android/app/src/main/java/stasis/client_android/activities/fragments/HomeFragment.kt:160` 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–22 lines × 3) client-android/app/src/main/java/stasis/client_android/activities/fragments/HomeFragment.kt:257— client-android/app/src/main/java/stasis/client_android/activities/fragments/HomeFragment.kt:257-277 | client-android/app/src/main/java/stasis/client_android/activities/fragments/operations/OperationDetailsFragment.kt:124-145 | client-android/app/src/main/java/stasis/client_android/activities/fragments/operations/OperationListItemAdapter.kt:115-135 — 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 `client-android/app/src/main/java/stasis/client_android/activities/fragments/HomeFragment.kt:257` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (19 lines × 4) client-android/lib/src/main/kotlin/stasis/client_android/lib/ops/scheduling/DefaultOperationExecutor.kt:71— client-android/lib/src/main/kotlin/stasis/client_android/lib/ops/scheduling/DefaultOperationExecutor.kt:71-89 | client-android/lib/src/main/kotlin/stasis/client_android/lib/ops/scheduling/DefaultOperationExecutor.kt:108-126 | client-android/lib/src/main/kotlin/stasis/client_android/lib/ops/scheduling/DefaultOperationExecutor.kt:188-206 | client-android/lib/src/main/kotlin/stasis/client_android/lib/ops/scheduling/DefaultOperationExecutor.kt:227-245 — 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 `client-android/lib/src/main/kotlin/stasis/client_android/lib/ops/scheduling/DefaultOperationExecutor.kt:71` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 4) client-android/lib/src/main/kotlin/stasis/client_android/lib/api/clients/caching/DefaultCacheRefreshHandler.kt:170— client-android/lib/src/main/kotlin/stasis/client_android/lib/api/clients/caching/DefaultCacheRefreshHandler.kt:170-175 | client-android/lib/src/main/kotlin/stasis/client_android/lib/discovery/providers/client/ServiceDiscoveryProvider.kt:119-124 | client-android/lib/src/main/kotlin/stasis/client_android/lib/ops/commands/DefaultCommandProcessor.kt:113-118 | client-android/lib/src/main/kotlin/stasis/client_android/lib/ops/monitoring/DefaultServerMonitor.kt:61-66 — 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 block (29 lines × 4) client-cli/client_cli/cli/maintenance.py:107— client-cli/client_cli/cli/maintenance.py:107-135 | client-cli/client_cli/cli/maintenance.py:183-211 | client-cli/client_cli/cli/maintenance.py:247-275 | client-cli/client_cli/cli/maintenance.py:311-339 — 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. 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 (28 lines × 2) deployment/dev/scripts/generate_user_password.py:66— deployment/dev/scripts/generate_user_password.py:66-93 | deployment/production/scripts/generate_user_password.py:66-93 — before extracting anything, compare `deployment/dev/scripts/generate_user_password.py` and `deployment/production/scripts/generate_user_password.py` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 92 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 (27 lines × 2) deployment/dev/scripts/generate_user_password.py:36— deployment/dev/scripts/generate_user_password.py:36-62 | deployment/production/scripts/generate_user_password.py:36-62 — before extracting anything, compare `deployment/dev/scripts/generate_user_password.py` and `deployment/production/scripts/generate_user_password.py` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 92 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 `deployment/dev/scripts/generate_user_password.py:36` 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 (25–26 lines × 2) assets/refresh_assets.py:33— assets/refresh_assets.py:33-57 | assets/refresh_assets.py:61-86 — 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–25 lines × 3) deployment/dev/scripts/generate_device_secret.py:86— deployment/dev/scripts/generate_device_secret.py:86-110 | deployment/dev/scripts/generate_user_password.py:33-54 | deployment/production/scripts/generate_user_password.py:33-54 — before extracting anything, compare `deployment/dev/scripts/generate_user_password.py` and `deployment/production/scripts/generate_user_password.py` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 92 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 `deployment/dev/scripts/generate_device_secret.py:86` 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 (16 lines × 5) client-cli/client_cli/cli/maintenance.py:37— client-cli/client_cli/cli/maintenance.py:37-52 | client-cli/client_cli/cli/maintenance.py:137-152 | client-cli/client_cli/cli/maintenance.py:216-231 | client-cli/client_cli/cli/maintenance.py:280-295 | client-cli/client_cli/cli/maintenance.py:341-356 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `client-cli/client_cli/cli/maintenance.py:155` calls `group`, `credentials`, `add_command` and `client-cli/client_cli/cli/maintenance.py:234` 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 (7 lines × 4) identity-ui/deployment/dev/run_browser.py:11— identity-ui/deployment/dev/run_browser.py:11-17 | identity-ui/deployment/dev/run_server.py:8-14 | server-ui/deployment/dev/run_browser.py:11-17 | server-ui/deployment/dev/run_server.py:8-14 — before extracting anything, compare `identity-ui/deployment/dev/run_browser.py` and `server-ui/deployment/dev/run_browser.py` as WHOLE FILES: 92% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `identity-ui/deployment/dev/run_browser.py:7` calls `dirname`, `realpath` and `identity-ui/deployment/dev/run_server.py:4` 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 (72 lines × 2) identity-ui/lib/pages/authorize/authorization_callback.dart:15— identity-ui/lib/pages/authorize/authorization_callback.dart:15-86 | server-ui/lib/pages/authorize/authorization_callback.dart:15-86 — 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 (53 lines × 5) client-ui/lib/pages/components/client_credentials_reset_form.dart:202— client-ui/lib/pages/components/client_credentials_reset_form.dart:202-254 | client-ui/lib/pages/components/client_pull_device_secret_form.dart:139-191 | client-ui/lib/pages/components/client_push_device_secret_form.dart:172-224 | client-ui/lib/pages/components/client_reencrypt_device_secret_form.dart:172-224 | client-ui/lib/pages/components/client_regenerate_api_certificate_form.dart:67-119 — before extracting anything, compare `client-ui/lib/pages/components/client_credentials_reset_form.dart` and `client-ui/lib/pages/components/client_pull_device_secret_form.dart` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 218 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 (45 lines × 6) client-ui/lib/pages/components/client_bootstrap_form.dart:343— client-ui/lib/pages/components/client_bootstrap_form.dart:343-387 | client-ui/lib/pages/components/client_credentials_reset_form.dart:300-344 | client-ui/lib/pages/components/client_pull_device_secret_form.dart:218-262 | client-ui/lib/pages/components/client_push_device_secret_form.dart:252-296 | client-ui/lib/pages/components/client_reencrypt_device_secret_form.dart:266-310 | client-ui/lib/pages/components/client_regenerate_api_certificate_form.dart:139-183 — before extracting anything, compare `client-ui/lib/pages/components/client_bootstrap_form.dart` and `client-ui/lib/pages/components/client_credentials_reset_form.dart` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 195 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 (43 lines × 3) client-ui/lib/pages/components/client_bootstrap_form.dart:203— client-ui/lib/pages/components/client_bootstrap_form.dart:203-245 | client-ui/lib/pages/components/client_credentials_reset_form.dart:164-206 | client-ui/lib/pages/components/client_reencrypt_device_secret_form.dart:134-176 — before extracting anything, compare `client-ui/lib/pages/components/client_bootstrap_form.dart` and `client-ui/lib/pages/components/client_credentials_reset_form.dart` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 195 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 (34 lines × 2) client-ui/lib/pages/status.dart:45— client-ui/lib/pages/status.dart:45-78 | client-ui/lib/pages/status.dart:90-123 — 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 (33 lines × 2) client-ui/lib/pages/components/forms/retention_field.dart:23— client-ui/lib/pages/components/forms/retention_field.dart:23-55 | server-ui/lib/pages/manage/components/forms/retention_field.dart:23-55 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (30 lines × 3) client-ui/lib/pages/components/client_pull_device_secret_form.dart:42— client-ui/lib/pages/components/client_pull_device_secret_form.dart:42-71 | client-ui/lib/pages/components/client_push_device_secret_form.dart:43-72 | client-ui/lib/pages/components/client_reencrypt_device_secret_form.dart:43-72 — before extracting anything, compare `client-ui/lib/pages/components/client_pull_device_secret_form.dart` and `client-ui/lib/pages/components/client_push_device_secret_form.dart` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 274 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 (30 lines × 2) client-ui/lib/api/app_processes.dart:91— client-ui/lib/api/app_processes.dart:91-120 | client-ui/lib/api/app_processes.dart:135-164 — 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 (28 lines × 4) client-ui/lib/pages/components/forms/duration_field.dart:35— client-ui/lib/pages/components/forms/duration_field.dart:35-62 | client-ui/lib/pages/components/forms/file_size_field.dart:42-69 | server-ui/lib/pages/manage/components/forms/duration_field.dart:35-62 | server-ui/lib/pages/manage/components/forms/file_size_field.dart:42-69 — before extracting anything, compare `client-ui/lib/pages/components/forms/file_size_field.dart` and `server-ui/lib/pages/manage/components/forms/file_size_field.dart` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 63 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 (25 lines × 2) server-ui/lib/pages/manage/devices.dart:137— server-ui/lib/pages/manage/devices.dart:137-161 | server-ui/lib/pages/manage/users.dart:126-150 — before extracting anything, compare `server-ui/lib/pages/manage/devices.dart` and `server-ui/lib/pages/manage/users.dart` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 159 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 (23 lines × 5) client-ui/lib/api/app_processes.dart:66— client-ui/lib/api/app_processes.dart:66-88 | client-ui/lib/api/app_processes.dart:110-132 | client-ui/lib/api/app_processes.dart:154-176 | client-ui/lib/api/app_processes.dart:197-219 | client-ui/lib/api/app_processes.dart:240-262 — 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.
Duplicated block (18–21 lines × 3) client-ui/lib/pages/components/entity_form.dart:35— client-ui/lib/pages/components/entity_form.dart:35-55 | identity-ui/lib/pages/manage/components/entity_form.dart:21-38 | server-ui/lib/pages/manage/components/entity_form.dart:41-58 — before extracting anything, compare `identity-ui/lib/pages/manage/components/entity_form.dart` and `server-ui/lib/pages/manage/components/entity_form.dart` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 36 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 (20 lines × 6) client-ui/lib/pages/components/client_bootstrap_form.dart:235— client-ui/lib/pages/components/client_bootstrap_form.dart:235-254 | client-ui/lib/pages/components/client_credentials_reset_form.dart:196-215 | client-ui/lib/pages/components/client_pull_device_secret_form.dart:133-152 | client-ui/lib/pages/components/client_push_device_secret_form.dart:166-185 | client-ui/lib/pages/components/client_reencrypt_device_secret_form.dart:166-185 | client-ui/lib/pages/components/client_regenerate_api_certificate_form.dart:61-80 — before extracting anything, compare `client-ui/lib/pages/components/client_bootstrap_form.dart` and `client-ui/lib/pages/components/client_credentials_reset_form.dart` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 195 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 (19–20 lines × 5) client-ui/lib/pages/components/client_credentials_reset_form.dart:380— client-ui/lib/pages/components/client_credentials_reset_form.dart:380-399 | client-ui/lib/pages/components/client_pull_device_secret_form.dart:297-316 | client-ui/lib/pages/components/client_push_device_secret_form.dart:332-351 | client-ui/lib/pages/components/client_reencrypt_device_secret_form.dart:345-364 | client-ui/lib/pages/components/client_regenerate_api_certificate_form.dart:208-226 — before extracting anything, compare `client-ui/lib/pages/components/client_credentials_reset_form.dart` and `client-ui/lib/pages/components/client_pull_device_secret_form.dart` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 218 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 (16–18 lines × 3) client-ui/lib/pages/components/client_bootstrap_form.dart:67— client-ui/lib/pages/components/client_bootstrap_form.dart:67-84 | client-ui/lib/pages/components/client_bootstrap_form.dart:91-106 | client-ui/lib/pages/components/client_bootstrap_form.dart:113-130 — 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 (15–17 lines × 9) client-ui/lib/pages/components/client_bootstrap_form.dart:122— client-ui/lib/pages/components/client_bootstrap_form.dart:122-138 | client-ui/lib/pages/components/client_credentials_reset_form.dart:50-64 | client-ui/lib/pages/components/client_credentials_reset_form.dart:75-91 | client-ui/lib/pages/components/client_pull_device_secret_form.dart:68-84 | client-ui/lib/pages/components/client_pull_device_secret_form.dart:95-111 | client-ui/lib/pages/components/client_push_device_secret_form.dart:69-85 | client-ui/lib/pages/components/client_push_device_secret_form.dart:96-112 | client-ui/lib/pages/components/client_reencrypt_device_secret_form.dart:69-85 | client-ui/lib/pages/components/client_reencrypt_device_secret_form.dart:96-112 — before extracting anything, compare `client-ui/lib/pages/components/client_bootstrap_form.dart` and `client-ui/lib/pages/components/client_credentials_reset_form.dart` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 195 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 (17 lines × 4) client-ui/lib/pages/components/forms/duration_field.dart:68— client-ui/lib/pages/components/forms/duration_field.dart:68-84 | client-ui/lib/pages/components/forms/file_size_field.dart:75-91 | server-ui/lib/pages/manage/components/forms/duration_field.dart:68-84 | server-ui/lib/pages/manage/components/forms/file_size_field.dart:75-91 — before extracting anything, compare `client-ui/lib/pages/components/forms/file_size_field.dart` and `server-ui/lib/pages/manage/components/forms/file_size_field.dart` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 63 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 (15–17 lines × 3) identity-ui/lib/pages/manage/apis.dart:108— identity-ui/lib/pages/manage/apis.dart:108-124 | identity-ui/lib/pages/manage/codes.dart:70-84 | REDACTED:323-337 — before extracting anything, compare `identity-ui/lib/pages/manage/apis.dart` and `identity-ui/lib/pages/manage/codes.dart` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 40 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 (13–15 lines × 14) identity-ui/lib/pages/manage/apis.dart:129— identity-ui/lib/pages/manage/apis.dart:129-143 | identity-ui/lib/pages/manage/clients.dart:294-306 | identity-ui/lib/pages/manage/codes.dart:89-101 | REDACTED:342-354 | identity-ui/lib/pages/manage/tokens.dart:91-103 | server-ui/lib/pages/default/home.dart:305-317 | server-ui/lib/pages/manage/codes.dart:108-122 | server-ui/lib/pages/manage/definitions.dart:320-332 | server-ui/lib/pages/manage/device_keys.dart:108-120 | server-ui/lib/pages/manage/devices.dart:554-566 | server-ui/lib/pages/manage/entries.dart:123-135 | server-ui/lib/pages/manage/nodes.dart:193-205 | server-ui/lib/pages/manage/schedules.dart:255-267 | server-ui/lib/pages/manage/users.dart:452-464 — before extracting anything, compare `identity-ui/lib/pages/manage/apis.dart` and `identity-ui/lib/pages/manage/codes.dart` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 40 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 (14–15 lines × 2) client-ui/lib/pages/components/client_credentials_reset_form.dart:278— client-ui/lib/pages/components/client_credentials_reset_form.dart:278-291 | client-ui/lib/pages/components/client_reencrypt_device_secret_form.dart:243-257 — before extracting anything, compare `client-ui/lib/pages/components/client_credentials_reset_form.dart` and `client-ui/lib/pages/components/client_reencrypt_device_secret_form.dart` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 308 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 (14 lines × 6) server-ui/lib/pages/manage/devices.dart:456— server-ui/lib/pages/manage/devices.dart:456-469 | server-ui/lib/pages/manage/devices.dart:498-511 | server-ui/lib/pages/manage/users.dart:278-291 | server-ui/lib/pages/manage/users.dart:318-331 | server-ui/lib/pages/manage/users.dart:359-372 | server-ui/lib/pages/manage/users.dart:398-411 — before extracting anything, compare `server-ui/lib/pages/manage/devices.dart` and `server-ui/lib/pages/manage/users.dart` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 159 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 (14 lines × 3) client-ui/lib/pages/components/client_bootstrap_form.dart:292— client-ui/lib/pages/components/client_bootstrap_form.dart:292-305 | client-ui/lib/pages/components/client_credentials_reset_form.dart:253-266 | client-ui/lib/pages/components/client_reencrypt_device_secret_form.dart:223-236 — before extracting anything, compare `client-ui/lib/pages/components/client_bootstrap_form.dart` and `client-ui/lib/pages/components/client_credentials_reset_form.dart` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 195 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–13 lines × 4) identity-ui/lib/pages/manage/clients.dart:40— identity-ui/lib/pages/manage/clients.dart:40-52 | identity-ui/lib/pages/manage/codes.dart:31-40 | REDACTED:46-57 | identity-ui/lib/pages/manage/tokens.dart:31-41 — before extracting anything, compare `identity-ui/lib/pages/manage/clients.dart` and `identity-ui/lib/pages/manage/codes.dart` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 36 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 (13 lines × 3) server-ui/lib/pages/default/home.dart:225— server-ui/lib/pages/default/home.dart:225-237 | server-ui/lib/pages/manage/devices.dart:232-244 | server-ui/lib/pages/manage/users.dart:231-243 — before extracting anything, compare `server-ui/lib/pages/default/home.dart` and `server-ui/lib/pages/manage/devices.dart` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 40 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 (11–12 lines × 21) identity-ui/lib/pages/manage/clients.dart:168— identity-ui/lib/pages/manage/clients.dart:168-179 | identity-ui/lib/pages/manage/clients.dart:220-231 | identity-ui/lib/pages/manage/clients.dart:261-272 | REDACTED:242-253 | server-ui/lib/pages/default/home.dart:269-280 | server-ui/lib/pages/manage/commands.dart:264-275 | server-ui/lib/pages/manage/definitions.dart:195-205 | server-ui/lib/pages/manage/definitions.dart:289-300 | server-ui/lib/pages/manage/devices.dart:258-269 | server-ui/lib/pages/manage/devices.dart:331-341 | server-ui/lib/pages/manage/devices.dart:479-490 | server-ui/lib/pages/manage/devices.dart:521-532 | server-ui/lib/pages/manage/nodes.dart:120-131 | server-ui/lib/pages/manage/nodes.dart:160-171 | server-ui/lib/pages/manage/schedules.dart:164-175 | server-ui/lib/pages/manage/schedules.dart:222-233 | server-ui/lib/pages/manage/users.dart:259-270 | server-ui/lib/pages/manage/users.dart:299-310 | server-ui/lib/pages/manage/users.dart:339-350 | server-ui/lib/pages/manage/users.dart:380-391 | server-ui/lib/pages/manage/users.dart:419-430 — before extracting anything, compare `identity-ui/lib/pages/manage/clients.dart` and `REDACTED` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 85 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 (12 lines × 5) client-ui/lib/pages/components/client_bootstrap_form.dart:428— client-ui/lib/pages/components/client_bootstrap_form.dart:428-439 | client-ui/lib/pages/components/client_credentials_reset_form.dart:376-387 | client-ui/lib/pages/components/client_pull_device_secret_form.dart:293-304 | client-ui/lib/pages/components/client_push_device_secret_form.dart:328-339 | client-ui/lib/pages/components/client_reencrypt_device_secret_form.dart:341-352 — before extracting anything, compare `client-ui/lib/pages/components/client_bootstrap_form.dart` and `client-ui/lib/pages/components/client_credentials_reset_form.dart` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 195 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–12 lines × 2) client-ui/lib/pages/status.dart:143— client-ui/lib/pages/status.dart:143-154 | client-ui/lib/pages/status.dart:172-182 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10–12 lines × 2) server-ui/lib/pages/manage/devices.dart:127— server-ui/lib/pages/manage/devices.dart:127-138 | server-ui/lib/pages/manage/users.dart:113-122 — before extracting anything, compare `server-ui/lib/pages/manage/devices.dart` and `server-ui/lib/pages/manage/users.dart` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 159 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 × 6) client-ui/lib/pages/components/client_bootstrap_form.dart:474— client-ui/lib/pages/components/client_bootstrap_form.dart:474-484 | client-ui/lib/pages/components/client_credentials_reset_form.dart:422-432 | client-ui/lib/pages/components/client_pull_device_secret_form.dart:339-349 | client-ui/lib/pages/components/client_push_device_secret_form.dart:374-384 | client-ui/lib/pages/components/client_reencrypt_device_secret_form.dart:387-397 | client-ui/lib/pages/components/client_regenerate_api_certificate_form.dart:249-259 — before extracting anything, compare `client-ui/lib/pages/components/client_bootstrap_form.dart` and `client-ui/lib/pages/components/client_credentials_reset_form.dart` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 195 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 (9–11 lines × 2) client-ui/lib/pages/backup_entries.dart:89— client-ui/lib/pages/backup_entries.dart:89-99 | client-ui/lib/pages/search.dart:172-180 — 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 × 8) client-ui/lib/pages/components/client_bootstrap_form.dart:462— client-ui/lib/pages/components/client_bootstrap_form.dart:462-471 | client-ui/lib/pages/components/client_credentials_reset_form.dart:410-419 | client-ui/lib/pages/components/client_pull_device_secret_form.dart:327-336 | client-ui/lib/pages/components/client_push_device_secret_form.dart:362-371 | client-ui/lib/pages/components/client_reencrypt_device_secret_form.dart:375-384 | client-ui/lib/pages/components/client_regenerate_api_certificate_form.dart:237-246 | client-ui/lib/pages/components/credentials_form.dart:349-358 | client-ui/lib/pages/components/update_user_credentials_form.dart:226-235 — before extracting anything, compare `client-ui/lib/pages/components/client_bootstrap_form.dart` and `client-ui/lib/pages/components/client_credentials_reset_form.dart` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 195 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 (9–10 lines × 4) server-ui/lib/pages/manage/definitions.dart:95— server-ui/lib/pages/manage/definitions.dart:95-103 | server-ui/lib/pages/manage/devices.dart:185-194 | server-ui/lib/pages/manage/schedules.dart:75-83 | server-ui/lib/pages/manage/users.dart:156-164 — before extracting anything, compare `server-ui/lib/pages/manage/definitions.dart` and `server-ui/lib/pages/manage/devices.dart` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 115 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 (9–10 lines × 2) client-ui/lib/pages/components/dataset_definition_summary.dart:25— client-ui/lib/pages/components/dataset_definition_summary.dart:25-33 | client-ui/lib/pages/rules.dart:50-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.
Duplicated block (6–8 lines × 38) client-ui/lib/pages/backup.dart:217— client-ui/lib/pages/backup.dart:217-222 | client-ui/lib/pages/backup.dart:233-239 | client-ui/lib/pages/recover.dart:103-108 | identity-ui/lib/pages/manage/apis.dart:91-98 | identity-ui/lib/pages/manage/apis.dart:128-135 | identity-ui/lib/pages/manage/clients.dart:167-172 | identity-ui/lib/pages/manage/clients.dart:219-224 | identity-ui/lib/pages/manage/clients.dart:260-265 | identity-ui/lib/pages/manage/clients.dart:293-298 | identity-ui/lib/pages/manage/codes.dart:88-93 | REDACTED:241-246 | REDACTED:341-346 | identity-ui/lib/pages/manage/tokens.dart:90-95 | server-ui/lib/pages/manage/codes.dart:107-114 | server-ui/lib/pages/manage/commands.dart:184-189 | server-ui/lib/pages/manage/commands.dart:263-268 | server-ui/lib/pages/manage/definitions.dart:194-199 | server-ui/lib/pages/manage/definitions.dart:288-293 | server-ui/lib/pages/manage/definitions.dart:319-324 | server-ui/lib/pages/manage/device_keys.dart:107-112 | server-ui/lib/pages/manage/devices.dart:257-262 | server-ui/lib/pages/manage/devices.dart:330-335 | server-ui/lib/pages/manage/devices.dart:478-483 | server-ui/lib/pages/manage/devices.dart:520-525 | server-ui/lib/pages/manage/devices.dart:553-558 | server-ui/lib/pages/manage/entries.dart:122-127 | server-ui/lib/pages/manage/nodes.dart:119-124 | server-ui/lib/pages/manage/nodes.dart:159-164 | server-ui/lib/pages/manage/nodes.dart:192-197 | server-ui/lib/pages/manage/schedules.dart:163-168 | server-ui/lib/pages/manage/schedules.dart:221-226 | server-ui/lib/pages/manage/schedules.dart:254-259 | server-ui/lib/pages/manage/users.dart:258-263 | server-ui/lib/pages/manage/users.dart:298-303 | server-ui/lib/pages/manage/users.dart:338-343 | server-ui/lib/pages/manage/users.dart:379-384 | server-ui/lib/pages/manage/users.dart:418-423 | server-ui/lib/pages/manage/users.dart:451-456 — before extracting anything, compare `identity-ui/lib/pages/manage/apis.dart` and `identity-ui/lib/pages/manage/codes.dart` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 40 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 × 6) client-ui/lib/pages/components/client_bootstrap_form.dart:388— client-ui/lib/pages/components/client_bootstrap_form.dart:388-395 | client-ui/lib/pages/components/client_credentials_reset_form.dart:345-352 | client-ui/lib/pages/components/client_pull_device_secret_form.dart:263-270 | client-ui/lib/pages/components/client_push_device_secret_form.dart:297-304 | client-ui/lib/pages/components/client_reencrypt_device_secret_form.dart:311-318 | client-ui/lib/pages/components/client_regenerate_api_certificate_form.dart:184-191 — before extracting anything, compare `client-ui/lib/pages/components/client_bootstrap_form.dart` and `client-ui/lib/pages/components/client_credentials_reset_form.dart` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 195 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 (5–7 lines × 5) client-ui/lib/pages/backup_entries.dart:89— client-ui/lib/pages/backup_entries.dart:89-95 | client-ui/lib/pages/components/dataset_metadata_entity_summary.dart:137-142 | client-ui/lib/pages/search.dart:172-176 | server-ui/lib/pages/default/home.dart:269-273 | server-ui/lib/pages/default/home.dart:305-309 — there are 5 copies across 4 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 5 sites; resolving a subset leaves the remainder to drift apart.
Duplicated block (7 lines × 3) client-ui/lib/pages/backup_entries.dart:124— client-ui/lib/pages/backup_entries.dart:124-130 | client-ui/lib/pages/components/backup_entry_metadata.dart:125-131 | client-ui/lib/pages/components/backup_entry_metadata.dart:181-187 — 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.
Duplicated block (4–5 lines × 4) client-ui/lib/pages/components/dataset_definition_summary.dart:15— client-ui/lib/pages/components/dataset_definition_summary.dart:15-19 | client-ui/lib/pages/components/dataset_entry_summary.dart:10-14 | client-ui/lib/pages/components/operation_summary.dart:15-19 | client-ui/lib/pages/components/schedule_summary.dart:14-17 — 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 (8 lines × 5) client-ui/lib/pages/components/client_credentials_reset_form.dart:401— client-ui/lib/pages/components/client_credentials_reset_form.dart:401-408 | client-ui/lib/pages/components/client_pull_device_secret_form.dart:318-325 | client-ui/lib/pages/components/client_push_device_secret_form.dart:353-360 | client-ui/lib/pages/components/client_reencrypt_device_secret_form.dart:366-373 | client-ui/lib/pages/components/client_regenerate_api_certificate_form.dart:228-235 — before extracting anything, compare `client-ui/lib/pages/components/client_credentials_reset_form.dart` and `client-ui/lib/pages/components/client_pull_device_secret_form.dart` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 218 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 (5 lines × 6) client-ui/lib/api/default_client_api.dart:108— client-ui/lib/api/default_client_api.dart:108-112 | client-ui/lib/api/default_client_api.dart:120-124 | server-ui/lib/api/default_api_client.dart:104-108 | server-ui/lib/api/default_api_client.dart:288-292 | server-ui/lib/api/default_api_client.dart:318-322 | server-ui/lib/api/default_api_client.dart:356-360 — there are 6 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 6 sites; resolving a subset leaves the remainder to drift apart.
Duplicated block (5 lines × 9) client-ui/lib/api/default_client_api.dart:114— client-ui/lib/api/default_client_api.dart:114-118 | client-ui/lib/api/default_client_api.dart:138-142 | client-ui/lib/api/default_client_api.dart:207-211 | server-ui/lib/api/default_api_client.dart:116-120 | server-ui/lib/api/default_api_client.dart:254-258 | server-ui/lib/api/default_api_client.dart:312-316 | server-ui/lib/api/default_api_client.dart:336-340 | server-ui/lib/api/default_api_client.dart:350-354 | server-ui/lib/api/default_api_client.dart:382-386 — there are 9 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 9 sites; resolving a subset leaves the remainder to drift apart.
Duplicated block (5 lines × 7) client-ui/lib/api/default_client_api.dart:283— client-ui/lib/api/default_client_api.dart:283-287 | server-ui/lib/api/default_api_client.dart:122-126 | server-ui/lib/api/default_api_client.dart:128-132 | server-ui/lib/api/default_api_client.dart:134-138 | server-ui/lib/api/default_api_client.dart:140-144 | server-ui/lib/api/default_api_client.dart:306-310 | server-ui/lib/api/default_api_client.dart:330-334 — there are 7 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 7 sites; resolving a subset leaves the remainder to drift apart.
Duplicated block (5 lines × 4) server-ui/lib/api/bootstrap_api_client.dart:12— server-ui/lib/api/bootstrap_api_client.dart:12-16 | server-ui/lib/api/default_api_client.dart:56-60 | server-ui/lib/api/default_api_client.dart:172-176 | server-ui/lib/api/default_api_client.dart:216-220 — there are 4 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 4 sites; resolving a subset leaves the remainder to drift apart.
P12 · CI test-gate honesty· Coverage collected but not gated · ×1
Coverage collected but not gated — CI collects a coverage report but no step enforces a minimum — coverage could halve and CI stays green. Add a step that fails the build when coverage drops below a floor (your coverage tool's minimum-threshold flag, or a coverage-gate action) so the number guards something. What was searched, so you can tell an absence from a miss: this repository's CI files AND its coverage configuration — the well-known coverage and test-runner config files, read at the repository root and inside workspace package directories two levels down, so a floor declared beside the tests rather than in the pipeline is credited — matched against the threshold settings this check knows by name. A floor set in your coverage service's web UI rather than in a committed file, or under a setting whose name is not one of those, is not seen here.
Duplicated predicate server-ui/lib/pages/manage/components/forms/device_limits_field.dart:136— `_maxCrates != null && _maxStorage != null && _maxStoragePerCrate != null && _maxRetention != null && _minRetention != null` appears character-identically in 2 files — server-ui/lib/pages/manage/components/forms/device_limits_field.dart, server-ui/lib/pages/manage/components/forms/user_limits_field.dart. 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 client-ui/lib/pages/components/forms/policy_field.dart:40— `_policyVersions != null || _policyType != 'at-most'` appears character-identically in 2 files — client-ui/lib/pages/components/forms/policy_field.dart, server-ui/lib/pages/manage/components/forms/policy_field.dart. 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 client-ui/lib/pages/components/forms/policy_field.dart:59— `_showPolicyVersions && (actualValue == null || actualValue <= 0)` appears character-identically in 2 files — client-ui/lib/pages/components/forms/policy_field.dart, server-ui/lib/pages/manage/components/forms/policy_field.dart. 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 identity-ui/lib/api/oauth.dart:58— `credentials != null && (!credentials.isExpired || credentials.canRefresh)` appears character-identically in 2 files — identity-ui/lib/api/oauth.dart, server-ui/lib/api/oauth.dart. 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 client-ui/lib/pages/components/entity_form.dart:113— `errorMessage != null && (actualValue == null || actualValue.isEmpty)` appears character-identically in 3 files — client-ui/lib/pages/components/entity_form.dart, identity-ui/lib/pages/manage/components/entity_form.dart, server-ui/lib/pages/manage/components/entity_form.dart. 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 client-ui/lib/utils/pair.dart:14— `other is Pair && a == other.a && b == other.b` appears character-identically in 2 files — client-ui/lib/utils/pair.dart, server-ui/lib/utils/pair.dart. 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 client-ui/lib/utils/triple.dart:15— `other is Triple && a == other.a && b == other.b && c == other.c` appears character-identically in 2 files — client-ui/lib/utils/triple.dart, server-ui/lib/utils/triple.dart. 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 identity-ui/lib/pages/default/components.dart:11— `parameterValue != null && parameterValue.trim().isNotEmpty` appears character-identically in 2 files — identity-ui/lib/pages/default/components.dart, server-ui/lib/pages/default/components.dart. 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 client-ui/lib/api/api_client.dart:311— `response.statusCode >= 400 && response.statusCode < 500` appears character-identically in 3 files — client-ui/lib/api/api_client.dart, identity-ui/lib/api/default_api_client.dart, server-ui/lib/api/api_client.dart. 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 client-ui/lib/pages/common/components.dart:43— `snapshot.data != null && snapshot.connectionState == ConnectionState.done` appears character-identically in 9 files — client-ui/lib/pages/common/components.dart, client-ui/lib/pages/components/forms/dataset_entry_field.dart, client-ui/lib/pages/login.dart, identity-ui/lib/pages/authorize/authorization_callback.dart. 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 identity-ui/lib/pages/page_router.dart:244— `snapshot.error == null || snapshot.error.runtimeType == RedirectPending` appears character-identically in 2 files — identity-ui/lib/pages/page_router.dart, server-ui/lib/pages/page_router.dart. 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 client-ui/lib/pages/components/forms/duration_field.dart:44— `widget.errorMessage != null && (actualValue == null || actualValue <= 0)` appears character-identically in 4 files — client-ui/lib/pages/components/forms/duration_field.dart, client-ui/lib/pages/components/forms/file_size_field.dart, server-ui/lib/pages/manage/components/forms/duration_field.dart, server-ui/lib/pages/manage/components/forms/file_size_field.dart. 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 client-android/lib/src/main/kotlin/stasis/client_android/lib/model/SourceEntity.kt:29— `existing.size != current.size || existing.checksum != current.checksum` appears character-identically in 2 files — client-android/lib/src/main/kotlin/stasis/client_android/lib/model/SourceEntity.kt, client-android/lib/src/main/kotlin/stasis/client_android/lib/model/TargetEntity.kt. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate client-android/app/src/main/java/stasis/client_android/activities/fragments/login/MoreOptionsReEncryptDialogFragment.kt:86— `it is Failure && it.exception is InvalidUserCredentials` appears character-identically in 3 files — client-android/app/src/main/java/stasis/client_android/activities/fragments/login/MoreOptionsReEncryptDialogFragment.kt, client-android/app/src/main/java/stasis/client_android/activities/fragments/settings/UpdatePasswordFragment.kt, client-android/app/src/main/java/stasis/client_android/activities/fragments/settings/UpdateSaltFragment.kt. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate client-android/app/src/main/java/stasis/client_android/activities/fragments/settings/ImportDialogFragment.kt:74— `it is Try.Failure && it.exception is InvalidUserCredentials` appears character-identically in 3 files — client-android/app/src/main/java/stasis/client_android/activities/fragments/settings/ImportDialogFragment.kt, client-android/app/src/main/java/stasis/client_android/activities/fragments/settings/PullDialogFragment.kt, client-android/app/src/main/java/stasis/client_android/activities/fragments/settings/PushDialogFragment.kt. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate client-android/app/src/main/java/stasis/client_android/activities/fragments/settings/ImportDialogFragment.kt:64— `password == passwordConfirmation && password.isNotEmpty()` appears character-identically in 3 files — client-android/app/src/main/java/stasis/client_android/activities/fragments/settings/ImportDialogFragment.kt, client-android/app/src/main/java/stasis/client_android/activities/fragments/settings/PullDialogFragment.kt, client-android/app/src/main/java/stasis/client_android/activities/fragments/settings/PushDialogFragment.kt. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate client-cli/client_cli/cli/bootstrap.py:48— `not force and len(_get_processes(main_class=ctx.obj.service_main_class)) > 0` appears character-identically in 2 files — client-cli/client_cli/cli/bootstrap.py, client-cli/client_cli/cli/maintenance.py. 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 client-cli/client_cli/cli/bootstrap.py:113— `not response['successful'] and not isinstance(ctx.obj.rendering, JsonWriter)` appears character-identically in 2 files — client-cli/client_cli/cli/bootstrap.py, client-cli/client_cli/cli/maintenance.py. 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 identity/src/main/scala/stasis/identity/api/oauth/AuthorizationCodeGrant.scala:129— `client.id == request.client_id && request.redirect_uri.forall(_ == client.redirectUri)` appears character-identically in 2 files — identity/src/main/scala/stasis/identity/api/oauth/AuthorizationCodeGrant.scala, identity/src/main/scala/stasis/identity/api/oauth/PkceAuthorizationCodeGrant.scala. 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 client/src/main/scala/stasis/client/model/SourceEntity.scala:26— `existing.size != current.size || existing.checksum != current.checksum` appears character-identically in 2 files — client/src/main/scala/stasis/client/model/SourceEntity.scala, client/src/main/scala/stasis/client/model/TargetEntity.scala. 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 core/src/main/scala/stasis/core/persistence/backends/slick/LegacyKeyValueStore.scala:49— `keyCol.name.toLowerCase == "key" && valueCol.name.toLowerCase == "value"` appears character-identically in 2 files — core/src/main/scala/stasis/core/persistence/backends/slick/LegacyKeyValueStore.scala, identity/src/main/scala/stasis/identity/persistence/internal/LegacyKeyValueStore.scala. 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.
Silent fallback default in catch client/src/main/scala/stasis/client/ops/recovery/stages/EntityProcessing.scala:165— `partIdFromPath` swallows every exception into `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 case or in the Scaladoc, and the row stops firing.
Silent fallback default in catch deployment/dev/scripts/generate_artifacts.py:25— `container_executable` swallows every exception into `return 'docker'` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch identity-ui/deployment/production/build.py:18— `container_executable` swallows every exception into `return 'docker'` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch identity-ui/deployment/production/stage.py:18— `container_executable` swallows every exception into `return 'docker'` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch server-ui/deployment/production/build.py:18— `container_executable` swallows every exception into `return 'docker'` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch server-ui/deployment/production/stage.py:18— `container_executable` swallows every exception into `return 'docker'` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Documentation: no installation or build instructions README.md— There are no installation/build/run commands for any of the submodules, despite a visible Why? section. Add install steps (e.g. clone, build with sbt or gradle, run ./qa.py) under the heading.
Documentation: no usage examples README.md— There are no usage examples for any of the submodules shown in the README. Add a short 'How to Run It' section with commands like stasis start or ./qa.py.
Documentation: no contributor guidance README.md— No contribution/guidance guidance is present among the visible documents. Add Contributing notes covering PR/merge process, CI, and any required environment setup.
README/code drift deployment/dev/README.md:10— deployment/dev/README.md names `docker-compose-no-auth-has.yml`, but no file or folder `docker-compose-no-auth-has.yml` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift deployment/production/README.md:64— deployment/production/README.md names `.stasis.internal`, but no file or folder `.stasis.internal` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
X23 · Unguarded diagnostic materialisation· Diagnostic log message is built whether or not it is wanted · ×2
Diagnostic log message is built whether or not it is wanted release.py:159— `debug` at line 159 is called with an argument built by `"…".join(command)` (line 159), whose cost grows with the collection it walks. Python evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isEnabledFor(logging.DEBUG)` test, no debug flag, no `lambda` the logger calls only when the level is on.
Diagnostic log message is built whether or not it is wanted core/src/main/scala/stasis/core/discovery/providers/server/ServiceDiscoveryProvider.scala:57— `debug` at line 57 is called with an argument built by `(endpoints.api.map(_.id) ++ endpoints.core.map(_.id) ++ endpoints.discovery.map(_.id)).mkString("…", "…", "…")` (line 60), whose cost grows with the collection it walks. Scala evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: the logger takes a built `String` (SLF4J, Akka/Pekko `LoggingAdapter`, `context.log`), and there is no `isDebugEnabled`/`isTraceEnabled` test and no debug flag.
Fat interface: ServerApiEndpointClient (25 abstract members) client/src/main/scala/stasis/client/api/clients/ServerApiEndpointClient.scala:28— `ServerApiEndpointClient` declares 25 abstract members: `self`, `server`, `datasetDefinitions`, `datasetDefinition`, `createDatasetDefinition`, `updateDatasetDefinition`, `deleteDatasetDefinition`, `datasetEntries`, `datasetEntry`, `latestEntry`, `createDatasetEntry`, `deleteDatasetEntry`, `publicSchedules`, `publicSchedule`, `datasetMetadata`, `datasetMetadata`, `user`, `resetUserSalt`, `resetUserPassword`, `device`, `pushDeviceKey`, `pullDeviceKey`, `deviceKeyExists`, `ping`, `commands`. Counted over its ABSTRACT members — a `def` with no body or a `val`/`var` with no initializer, once per signature; concrete members, private and protected members, and members of a companion `object` are not counted, because no implementer is forced to write them. Those 25 declarations carry 24 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 24 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.
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/`.
No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
Logging is not universal — Only 3/7 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `client-ui`, `client-ui/macos`, `identity-ui`, `server-ui`.
P4 · Deployment & Rollback· No rollback/health safety · ×1
No rollback/health safety — Deployment automation exists but no readiness/liveness probes, rolling-update strategy, lifecycle hooks or migration job were evidenced — a bad release is harder to detect and reverse.
No changelog — No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
No security response headers detected REDACTED:1— None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is configured — defense in depth, even when a reverse proxy could set them. This is reported because `REDACTED` builds the web-server image that serves this application, so the configuration that would carry these headers is in this repository and was read in full. (−2.0 on this card.)
Interpolated log message defeats structured logging core/src/main/scala/stasis/core/persistence/staging/StagingStore.scala:71— `error` at line 71 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix.
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 (an sbt build (build.sbt), a Gradle build (build.gradle/build.gradle.kts) and a Dart pubspec.yaml — not scanned yet).
semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 1 file(s) — `client-android/lib/src/main/kotlin/stasis/client_android/lib/utils/ConcatSource.kt` — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
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 (an sbt build (build.sbt), a Gradle build (build.gradle/build.gradle.kts) and a Dart pubspec.yaml — not scanned yet).
0
—
Run 01a15eae-1a7f-7bc5-a0d3-30864118ed02 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 39 · Warnings: 424 · Recommendations: 50 — Appendix A · all findings · full markdown report.
Generated by Watchdog — deterministic code-health analysis. 21-10-2026 @ 13:37 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.