Public report of atsign-foundation/at_client_sdk, published 5 November 2026. It has the same score, grades and number of
findings as the full report. The details of security findings (where they are in the code, which known
vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive reportMeasured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.11.2). Assert signed this survey and filed it in the standard's public register, where anyone can look it up by its survey ID. Check this survey →
Signed and filed in the standard's public register, 5 November 2026, 21:34 UTC · Survey ID cd_f02253604a764edebfd6532afbe57721
atsign-foundation/at_client_sdk
Measured 5 November 2026, 21:33 UTC, at code version fd64538
CAI scoreWeak
CriticalWeakAdequateStrongExemplary
Up 6 since the last survey
The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.
A large codebase: 133,182 lines of product code in 35 projects, tests not counted · Estimated rebuild effort: about 2.4 person-years · Weakest lens: Production Readiness, 51
Findings by how serious they are
31 critical639 serious211 minor
16 dimensions are left out of the score. For each one, we either couldn't measure it in this code, or found no evidence of the safeguard we look for, such as a tested backup restore. They count neither for nor against the score, and Limitations lists each one with its reason.
This survey was produced by
Canine Code Analyzer
Producer
Canine Development
Analyzer
Canine Code Analyzer engine 1.0.0
Measured
5 November 2026, 21:33 UTC
A measurement, not a certificate. The Code Assurance Index records a number
together with the evidence it was worked out from, so anyone can recalculate it, but it doesn't certify or guarantee
the code. The standard was written by Canine Development, which also builds the Canine Code Analyzer. It is open to any tool that
implements it, and today the Canine Code Analyzer is the only one that does.
The score is deterministic, which means the same code always gets the same score. We work it out with tools that follow published rules, and an AI model never decides it, so anyone who applies the same rules to the same code gets the same number. How it is done is explained under Methodology ▸
71of 71 dimensions measured by tools.
866of 881 findings point to an exact file and line, so you can open each one in the code. The other 15 concern the repository as a whole, such as missing documentation.
71dimensions across 7 lenses, read from 133,182 lines of product code in 35 projects.
atsign-foundation/at_client_sdk falls short of our standard for production because its Security dimensions are rated Critical, and two passwords or keys sit in the current code. It scores 58 out of 100, which alone would earn Adequate, but it is rated Weak: a rating can't sit more than one step above its weakest group.
Production Readiness, at 51, is the weakest lens and counts most in the score. The best first step is replacing the two exposed passwords or keys and switching the old ones off, worth about 6 points. Adding a release approval comes next, worth about 3 points. Raising Production Readiness to 70 would lift the score to about 63.
Fifteen passwords or keys in the code's history and two in the code are open to anyone who can read the repository. Two secrets can leak from the build pipeline, and eight parts of the code are no longer understood by anyone working on it. Replacing each exposed password or key, limiting each secret to its own step and having someone learn the forgotten files would close these risks. Passing outside input through environment variables would fix the pipeline step that puts outside input straight into a shell command. Moving the business rules into the object that owns the data would take care of the three business objects that only hold data.
The product code is 133,182 lines, about €350,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.
We compare every finding with the previous survey's. A finding that has only moved to another line in the same file counts as the same finding, so only new findings appear here. Advisory notes from the AI model are left out, because the model words them afresh in every survey.
Fixed since the last survey: 59 findings
These 59 critical or serious findings were in the previous survey, on 21 October 2026, and are gone from this one.
€120,000 to €580,000, for 1,918 to 6,085 hours of work, about 2.4 person-years for 1 to 5 engineers
Difficulty of the problem
Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor
×0.8 at a score of 58. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
Size
Large: 133,182 lines of product code
What it is not
Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one.
How the estimate is made: We price the hours a team would need to write this code again, at €60 to €95 an hour. Declarations and boilerplate are priced at a fast rate and logic at a slower one, and the logic is then multiplied by the difficulty of the problem and by the quality factor. The estimate can be about 30% off either way, and it moves most with the hourly rate and the difficulty. For this code, every line is priced as straight logic, which keeps the estimate on the low side.
Top priorities
The three actions that raise the score most for the work they take. The full ranked list is in the Roadmap.
1
Resolve the 2 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED, REDACTED.
Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
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 €350,000 to build again, about 2.4 person-years of work. Its weakest lens is Production Readiness, at 51 (Adequate). Production Readiness is about whether the product is ready to run in production and to change without breaking. Because the weakest lens counts most in the score, work on Production Readiness also moves the score most.
Based on: the rebuild estimate · the Production Readiness grade · how much each lens counts
What to do: Start with the Production Readiness actions in Top priorities.
If you do one thing first · First action
Resolve the 2 Leaked secret finding(s) in REDACTED Scanning. Of all the actions in this report, it raises the score most for the work it takes: about 6 points for low effort, because it clears the 2 REDACTED Scanning findings. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
Architecture — module dependency graph
Project dependencies, layered top-to-bottom; arrows show direction. Any dashed red edge points upward or sideways, which only happens where the projects form a dependency cycle. A graph without cycles has none.
Architecture: which parts of the code depend on which
The code is divided into modules, groups of code that each handle one part of the product, and a module depends on another when it uses code from it. The table lists the modules both down the side and across the top, in an order where each module should only use modules listed above it. A number in a cell means the module on that row uses the module in that column, and it counts the pairs of building blocks (types) that connect them. The one thing to look for is a mark above the diagonal line. It means two or more modules use each other in a loop (a dependency cycle), so none of them can be changed, tested or released on its own.
24 modules, with 28 dependencies between them. One loop runs through 5 of the modules, marked above the diagonal.
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.
repository uses repository.map_content, so a change to repository.map_content can break repository, while a change to repository can't break repository.map_content.
Position
Below the diagonal: repository uses a module listed above it, which is the healthy direction.
16→17 repository.utils uses repository.servicespart of a loop✕
Connections
1 pair of types, where a type in repository.utils uses a type in repository.services.
repository.utils uses repository.services, so a change to repository.services can break repository.utils, while a change to repository.utils can't break repository.services.
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.
16→18 repository.utils uses repository.domainpart of a loop✕
Connections
1 pair of types, where a type in repository.utils uses a type in repository.domain.
repository.utils uses repository.domain, so a change to repository.domain can break repository.utils, while a change to repository.utils can't break repository.domain.
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.
repository.services uses repository.models, so a change to repository.models can break repository.services, while a change to repository.services can't break repository.models.
Position
Below the diagonal: repository.services uses a module listed above it, which is the healthy direction.
repository.services uses repository, so a change to repository can break repository.services, while a change to repository.services can't break repository.
Position
Below the diagonal: repository.services uses a module listed above it, which is the healthy direction.
repository.services uses repository.utils, so a change to repository.utils can break repository.services, while a change to repository.services can't break repository.utils.
Position
Below the diagonal: repository.services uses a module listed above it, which is the healthy direction.
17→18 repository.services uses repository.domainpart of a loop✕
Connections
2 pairs of types, where a type in repository.services uses a type in repository.domain.
repository.services uses repository.domain, so a change to repository.domain can break repository.services, while a change to repository.services can't break repository.domain.
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.
17→20 repository.services uses repository.srcpart of a loop✕
Connections
37 pairs of types, where a type in repository.services uses a type in repository.src. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
repository.services uses repository.src, so a change to repository.src can break repository.services, while a change to repository.services can't break repository.src.
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.
repository.domain uses repository.services, so a change to repository.services can break repository.domain, while a change to repository.domain can't break repository.services.
Position
Below the diagonal: repository.domain uses a module listed above it, which is the healthy direction.
repository.widgets uses repository.services, so a change to repository.services can break repository.widgets, while a change to repository.widgets can't break repository.services.
Position
Below the diagonal: repository.widgets uses a module listed above it, which is the healthy direction.
repository.widgets uses repository.domain, so a change to repository.domain can break repository.widgets, while a change to repository.widgets can't break repository.domain.
Position
Below the diagonal: repository.widgets uses a module listed above it, which is the healthy direction.
19→20 repository.widgets uses repository.srcpart of a loop✕
Connections
7 pairs of types, where a type in repository.widgets uses a type in repository.src.
repository.widgets uses repository.src, so a change to repository.src can break repository.widgets, while a change to repository.widgets can't break repository.src.
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.
repository.src uses repository.map_content, so a change to repository.map_content can break repository.src, while a change to repository.src can't break repository.map_content.
Position
Below the diagonal: repository.src uses a module listed above it, which is the healthy direction.
repository.src uses repository.widgets, so a change to repository.widgets can break repository.src, while a change to repository.src can't break repository.widgets.
Position
Below the diagonal: repository.src uses a module listed above it, which is the healthy direction.
repository.desktop_screens uses repository.models, so a change to repository.models can break repository.desktop_screens, while a change to repository.desktop_screens can't break repository.models.
Position
Below the diagonal: repository.desktop_screens uses a module listed above it, which is the healthy direction.
repository.desktop_screens uses repository.src, so a change to repository.src can break repository.desktop_screens, while a change to repository.desktop_screens can't break repository.src.
Position
Below the diagonal: repository.desktop_screens uses a module listed above it, which is the healthy direction.
repository.screens uses repository.location_modal, so a change to repository.location_modal can break repository.screens, while a change to repository.screens can't break repository.location_modal.
Position
Below the diagonal: repository.screens uses a module listed above it, which is the healthy direction.
repository.screens uses repository.map_content, so a change to repository.map_content can break repository.screens, while a change to repository.screens can't break repository.map_content.
Position
Below the diagonal: repository.screens uses a module listed above it, which is the healthy direction.
repository.screens uses repository.models, so a change to repository.models can break repository.screens, while a change to repository.screens can't break repository.models.
Position
Below the diagonal: repository.screens uses a module listed above it, which is the healthy direction.
repository.screens uses repository.services, so a change to repository.services can break repository.screens, while a change to repository.screens can't break repository.services.
Position
Below the diagonal: repository.screens uses a module listed above it, which is the healthy direction.
repository.screens uses repository.domain, so a change to repository.domain can break repository.screens, while a change to repository.screens can't break repository.domain.
Position
Below the diagonal: repository.screens uses a module listed above it, which is the healthy direction.
repository.screens uses repository.src, so a change to repository.src can break repository.screens, while a change to repository.screens can't break repository.src.
Position
Below the diagonal: repository.screens uses a module listed above it, which is the healthy direction.
repository.service uses repository.location_modal, so a change to repository.location_modal can break repository.service, while a change to repository.service can't break repository.location_modal.
Position
Below the diagonal: repository.service uses a module listed above it, which is the healthy direction.
repository.service uses repository.src, so a change to repository.src can break repository.service, while a change to repository.service can't break repository.src.
Position
Below the diagonal: repository.service uses a module listed above it, which is the healthy direction.
repository.common_components uses repository.widgets, so a change to repository.widgets can break repository.common_components, while a change to repository.common_components can't break repository.widgets.
Position
Below the diagonal: repository.common_components uses a module listed above it, which is the healthy direction.
repository.common_components uses repository.src, so a change to repository.src can break repository.common_components, while a change to repository.common_components can't break repository.src.
Position
Below the diagonal: repository.common_components uses a module listed above it, which is the healthy direction.
repository.common_components uses repository.desktop_screens, so a change to repository.desktop_screens can break repository.common_components, while a change to repository.common_components can't break repository.desktop_screens.
Position
Below the diagonal: repository.common_components 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
A07:2025 — Authentication Failures
18
High / Critical
A05:2025 — Injection
8
High / Critical
A03:2025 — Software Supply Chain Failures
4
Medium
Roadmap
Top priorities: Resolve the 2 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED, REDACTED; Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it; Move delegated behaviour onto the domain entity (or make it an immutable value object); keep invariants inside the type.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Resolve the 2 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED, REDACTED.
Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
Keep implementation types off the public surface (Dart: a `_` name, or keep it under `lib/src/` unexported; Kotlin: `internal`; Swift: leave it `internal` (the default) instead of `public`) so internals can change without breaking consumers.
Dart: await the async dart:io API (readAsString, writeAsString, Process.run, Future.delayed) instead of the *Sync variant or sleep(), or move heavy synchronous work to another isolate with Isolate.run.
Raise allocation-aware density on the hot paths — currently 14 use(s) across 124,481 production line(s) (~0.1/1k). More of the idioms below on the allocation-heavy paths climbs this toward 10.
Every finding carries one of four grades. Three say how serious it is. The fourth says this
survey could not settle it — and it is a grade, not a gap.
Critical — 31
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 — 639
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 — 211
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 16
Something this survey could not settle
from the outside, and which could be critical or serious. Either a control was required and no
positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves
nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean
result. These are excluded from the score rather than awarded a pass, so the number on the cover neither
rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each
one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 71 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.8, the weighted average across measured dimensions.
Every figure here is one of two kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10.
What we checked — 71 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, 866 of 881 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
This report answers yes to all three. That's the bar to hold any assessment to.
Tools & methods
The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.
Method
Backs
Version
Evaluator
Roslyn static analysis
Complexity, cohesion, coupling, dead code, API surface, layering
What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.
D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: test source is present (.dart) but the built-in coverage collector has no runner for this repository's ecosystem — so this suite was never executed by it. Not scored — this is a gap in the analyzer's language coverage, not a defect in the repo. To have real coverage read, produce a coverage report in a standard format (lcov — `flutter test --coverage` (or `dart test --coverage=coverage` then `dart run coverage:format_coverage --lcov`)) 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 (lcov — `flutter test --coverage` (or `dart test --coverage=coverage` then `dart run coverage:format_coverage --lcov`)) 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 — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.dart) but the built-in reliability runner does not support this repository's ecosystem, so flakiness couldn't be assessed. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
D12 Dependency Hygiene — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Not scored — 36 Maven/Gradle manifest(s) were read, stating a version for 0 dependency(ies) and leaving 18 to a parent or an imported BOM, but no build resolved the dependency graph, so the outdated signal was not established. NOT a finding that these dependencies are current or healthy.
D14 License Compliance — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Not scored — this repository declares a pubspec.yaml but commits no pubspec.lock, so its dependency graph was closed from the pubspec over pub.dev's published pubspecs, and part of it could not be read: no release of `chalkdart` that pub.dev publishes satisfies `>=2.0.9<4.0.0`. A licence verdict over part of a dependency graph is not a licence verdict. NOT a finding that this repository's licences are compliant: this dimension asserts nothing about its licensing in either direction.
D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is a COLLECTOR gap, not an environment fault: it declares a published package (packages/dart_utf7/pubspec.yaml), but no published-package marker D22 reads admitted any project here, so this ecosystem's public API has no collector, and the remedy is to write one — no change to the scan image can close it.
D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
D27 Navigability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
AX6 Interface segregation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
AXB1 Runtime evidence locked — no reproducible boot — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Subject: 1 markup document(s) — HTML, Razor, JSX, Vue, Svelte or server templates. The Runtime Evidence tier boots an app only via docker-compose, an Aspire AppHost, a Dockerfile, an npm dev script, a web service's own toolchain entry point (cargo, go, dotnet, Python, Spring Boot), or an Android app's own Gradle wrapper (run on an emulator); an Apple or Flutter app needs a host it lacks. None applied, so no live runtime a11y/egress/header evidence was collected. You can widen what we reach: add a docker-compose.yml (or an Aspire AppHost) that brings the app up with its dependencies. We then boot it in an isolated sandbox and gathers real runtime evidence — you change nothing in your pipeline (no CI step, no SDK).
C1 Data Protection — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 'package:hive' is imported (packages/at_client/lib/src/storage/hive/hive_at_client_storage.dart:10), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
C3 Audit Trail — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 'package:hive' is imported (packages/at_client/lib/src/storage/hive/hive_at_client_storage.dart:10), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
C4 Data Retention — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 'package:hive' is imported (packages/at_client/lib/src/storage/hive/hive_at_client_storage.dart:10), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
C5 Data-Subject Rights — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 'package:hive' is imported (packages/at_client/lib/src/storage/hive/hive_at_client_storage.dart:10), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
X2 Cancellation propagation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Go, PHP, Dart, Kotlin, Ruby, Scala, Java, Python and Rust source only, and no C# was loaded, and no named async function in this repository's JavaScript/TypeScript, nor any Go, PHP or Dart function or Kotlin suspend function, makes a request that can be cancelled (fetch, axios, ky, ofetch, got, undici, node:http; net/http, net.Dial; amphp; Dio; Ktor, OkHttp), so there is nothing to judge, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.
D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
D7 Architectural Integrity: Layering is checked against detected/declared rules — an architecture whose boundaries live in convention or in code review, not in a rule a scanner can read, is not enforced here.
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").
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
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.
DM4 Rich vs anemic domain model: Behaviour is detected as state mutation inside a method body — a method that enforces an invariant by validating-and-throwing without mutating reads as a query, and mutation delegated through an interface the scan can't resolve isn't credited; entities with zero public properties still drop out of the population. It detects that state changes, not whether the rule is correct.
M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
What it measures: How tangled the control flow is — methods with many branches are hard to test and change.
Method: Cyclomatic complexity per method (1 + decision points), computed exhaustively across production source; test projects separated by convention. Deterministic.
57 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was Query.watch at 34. A further 7 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 ContactInitialsColors.getColor at 29 — they are counted neither in the figure above nor in this dimension's score. 6 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: packages/at_chat_flutter/lib/utils/colors.dart (ContactInitialsColors.getColor at 29), packages/at_contacts_flutter/lib/utils/colors.dart (ContactInitialsColors.getColor at 29), packages/at_events_flutter/lib/utils/colors.dart (ContactInitialsColors.getColor at 29), packages/at_location_flutter/lib/utils/constants/colors.dart (ContactInitialsColors.getColor at 29), packages/at_commons/lib/src/exception/at_exception_utils.dart (AtExceptionUtils.get at 22), and 1 more not listed here. They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
+ 52 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 57 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with Query.watch (cyclomatic 34), _CreateEventState.build (cyclomatic 33), UpdateVerbBuilder.== (cyclomatic 33). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 57 together lifts Cyclomatic Complexity from 7.1 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.
+ 136 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 1 body over 60 down to 60 or less in Cognitive Complexity — start with SyncServiceImpl._pushFromSyncQueue (cognitive 82). — Refactoring it lifts Cognitive Complexity from 5.6 to about 6.1/10.
Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God 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 35 MethodTooLong finding(s) in God Classes — start with create_event.dart, recurring_event.dart, desktop_group_detail.dart. — One of this dimension's main actionable groups (35 warning-level).
Resolve the 19 FileTooLong finding(s) in God Classes — start with collections.dart, at_client_impl.dart, auth_cli.dart. — One of this dimension's main actionable groups (19 warning-level).
Resolve the 19 TooManyMethods finding(s) in God Classes — start with at_client_impl.dart, collections.dart, at_lookup_impl.dart. — One of this dimension's main actionable groups (19 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.
199 duplicated block group(s) detected. A further 13 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted. 49 of the 212 are in trees this repository does not ship — vendored, example/demo, project-template, fixture and benchmark code — and are ranked below the shipped groups rather than excluded from them: the duplication there is real and is still counted in this dimension's score. The dimensions that publish a production-file census leave those trees out of theirs, so this count is deliberately drawn over the wider population.
+ 92 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 16 Duplicated block (12 lines × 2) finding(s) in Code Duplication — start with request_location_sheet.dart (4), bottom_sheet_dialog.dart, aes_gcm_ffi_algo.dart. — One of this dimension's main actionable groups (16 warning-level).
Resolve the 10 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with group_contact_view.dart, person_vertical_tile.dart, overlapping_contacts.dart. — One of this dimension's main actionable groups (10 warning-level).
Resolve the 9 Duplicated block (14 lines × 2) finding(s) in Code Duplication — start with aes_gcm_ffi_algo.dart, pkam_signing_algo.dart, add_contacts_dialog.dart. — One of this dimension's main actionable groups (9 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 · Coupling9.8 / 10Stronggated by 1 serious finding✓ 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.
34 production modules (Gradle+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; 2 module(s) off the main sequence, with abstractness counted on 30 of the 34 (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: at_utils
Off the main sequence: at_commons
What to do
Resolve the 1 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (1 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 14 Low cohesion finding(s) in Cohesion (LCOM4) — start with custom_popup_route.dart (3), memory_at_key_value_store.dart, at_login_service.dart. — One of this dimension's main actionable groups (14 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.
What it measures: Whether the code respects its intended layering / architecture rules.
Method: Enforcement rung (Prevented/Verified/Documented) per checkable ADR via Roslyn, plus dependency cycles via the engine shared with D5/AX3. Deterministic, exact.
No mechanizable ADR was identified, so enforcement is not measured. Dependency cycles not checked (no project-reference graph; where this repository's language has an import-cycle lens, cycles are reported there).
What to do
Enforce Architectural Integrity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d7_recommendation.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.
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 2 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 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: Files that change often and are also complex — the riskiest hotspots.
Method: Per production file churn times cyclomatic complexity over a rolling window, computed from git and Roslyn/JS/Razor analysis. Exhaustive, deterministic per commit date.
Top hotspots: packages/at_client/lib/src/client/at_client_impl.dart (162×19=3078); packages/at_client/lib/src/service/sync_service_impl.dart (64×32=2048); packages/at_client/lib/src/crypto/nskey/published_nskey_key_ring.dart (84×21=1764) Repeated repair below the complexity floor: packages/at_client/lib/src/crypto/nskey/nskey_private_filing.dart (25 of 42 changes were fixes); packages/at_auth/lib/src/keys/io/file_io.dart (17 of 26 changes were fixes); packages/at_client/lib/src/service/envelope_enrollment_conveyance.dart (14 of 26 changes were fixes)
Resolve the 21 Hotspot finding(s) in Churn × Complexity Hotspots — start with at_client_impl.dart, sync_service_impl.dart, published_nskey_key_ring.dart. — One of this dimension's main actionable groups (21 warning-level).
Resolve the 16 Repeated repair finding(s) in Churn × Complexity Hotspots — start with nskey_private_filing.dart, file_io.dart, envelope_enrollment_conveyance.dart. — One of this dimension's main actionable groups (16 warning-level).
Detailed fixes: d15_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D16 · Bus Factor7.5 / 10Strong✓ Tool-verified
What it measures: Whether knowledge is concentrated in too few people (the "bus factor").
Method: Living knowledge per author via time-decayed commit attribution (6-month half-life, focus weighting) across largest source files. Deterministic, avoids blame's mechanical-refactor false positives.
104 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is packages/at_client/lib/src/collections/collections.dart. Counted over 409 of the 820 production source files in this repository: 407 are under the ~2,400-byte size floor this dimension measures over, and the remaining 4 have no attributable history left to measure.
Off-boarding risk: anonymized user #1 · ×2
Further sole-owners (lower concentration)
What to do
Resolve the 2 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (2 recommendation-level).
Resolve the 1 Further sole-owners (lower concentration) finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d16_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Acknowledged debt left in the code — TODOs, dead code, suppressed warnings.
Method: Roslyn syntactic debt markers (suppressions/TODO/FIXME/HACK/empty-catch/commented-code/Obsolete) plus SymbolFinder dead-code analysis; weighted-debt-per-KLoC density deducted 2.0x per unit. Deterministic, exhaustive.
33 deducted task-comment markers across 133182 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 33 TodoComment finding(s) in Explicit Debt — start with main.dart (4), at_chops_impl.dart (3), group_service.dart (2). — One of this dimension's main actionable groups (33 warning-level).
Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the project's documentation is clear, complete, and useful.
Method: Every README, docs/ document and root guide parsed by its markup and measured in Unicode letters. Published: a runnable or packaged .NET project whose README (or a document it links, or a root guide) shows no example, and a root README naming none of three or more projects. Overview, licence, boilerplate, wall-of-text, empty-section and XML-doc rows are measured and withheld (counted in gaps) after adjudication. Deterministic, exhaustive, advisory.
What it measures: Whether architecture decisions are recorded well (context, decision, consequences).
Method: Every ADR read by its section structure: nine located rules (a missing Decision, Context or Consequences section, a stale status, two records deciding the same question, a dangling supersede link, a number-only title, a single option, no named cost, no status where the log uses one, no enforcement field where the log adopted one), each a fixed deduction from 10; the score is the mean over evaluated records. Deterministic, no model. Advisory.
0 of 1 evaluated ADRs have a defect readable from the log itself (a missing or empty section, no title, a single option, consequences with no cost, no status, a missing enforcement field, a status the log contradicts, a dangling link, an unlinked second decision on one question, a date that is no calendar day). How well each record argues its case is not measured.
5 of 35 build units (Gradle, pub) flagged as possibly oversized/incoherent.
Projects may be oversized for their cohesion
What to do
Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d26_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.
Method: 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.
15 finding(s): 0 critical, 15 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 15 REDACTED finding(s) in Secrets (history) — start with REDACTED (5), REDACTED (2), REDACTED (2). — One of this dimension's main actionable groups (15 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).
8 finding(s): 0 critical, 3 high, 0 medium, 5 low. semgrep hit a parse error in 1 file(s) — `packages/at_client_flutter/example/invitations/demo/demo.sh` (line 62, line 63) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 2 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
REDACTED
REDACTED
REDACTED
What to do
Resolve the 5 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (5 recommendation-level).
Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any dependency has a known published vulnerability (CVE), direct or transitive, in ANY ecosystem the repository declares — Dart pub, Elixir and Erlang via Hex, Go modules, Java and Kotlin via Maven/Gradle, JavaScript/npm, .NET/NuGet, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift.
Method: Dependency-CVE scan across every ecosystem the repository declares, scored ONCE. Three sources are unioned and deduplicated by advisory identity (rule id + alias closure, CVE<->GHSA) scoped to package+version, keeping the worst severity: `osv-scanner --recursive` over osv.dev for Dart pub, Elixir/Hex (and Erlang, whose `rebar.lock` syft first converts to a CycloneDX SBOM the scanner reads, with rows attributed back to the lock), Go, Java and Kotlin via Maven/Gradle (and Scala, whose sbt build's pinned direct declarations are written into a CycloneDX SBOM the scanner reads, with rows attributed back to the build file), npm, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift; `trivy fs --scanners vuln` for npm lockfiles; and `dotnet list package --vulnerable --include-transitive` for NuGet (with per-advisory collapse of the project x target-framework fan-out), plus a DECLARED-dependency arm that resolves a published gem's gemspec against rubygems.org where no Gemfile.lock is committed. `SeverityScore(c,h,m,l, normalizer 8.0)`. NotApplicable only when NO ecosystem is readable; if any applicable ecosystem could not be scanned the findings are REPORTED and the score is withheld. Supersedes the npm and OSV arms, retired 2026-09-05. Advisory since rubric-2026.11.2 (CAI decision 0006): every row is a match against a vulnerability database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.
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.
166 of 413 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is packages/at_location_flutter/lib/map_content/flutter_map/src/layer/tile_layer.dart. Counted over 413 of the 820 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
Resolve the 158 Orphaned file finding(s) in Knowledge Freshness — start with text_styles.dart (4), colors.dart (3), circular_contacts.dart (2). — One of this dimension's main actionable groups (158 recommendation-level).
Resolve the 8 Orphaned knowledge finding(s) in Knowledge Freshness — start with tile_layer.dart, event_key_stream_service.dart, create_event.dart. — One of this dimension's main actionable groups (8 issue-level).
Resolve the 1 Further orphaned files (smaller) finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d34_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.
Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.
Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling. A non-source file is never a coupling PARTICIPANT either: documentation, schemas, config and data files are dropped with the rest, so a code↔docs pair — a command and the reference page that restates it — is not reported however strongly the two co-change; nor is coupling that runs THROUGH a build step or config file.
Resolve the 8 Change coupling finding(s) in Change Coupling — start with ml_dsa_65_ffi.dart, ml_kem_768_ffi.dart, at_chops_impl.dart. — One of this dimension's main actionable groups (8 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.
What it measures: Whether the repository publishes a coordinated-vulnerability-disclosure policy (SECURITY.md or security.txt) with a reporting contact, so finders know how to report a vulnerability. Presence of a policy file with a contact, not whether the policy is adequate or honoured.
Method: Vulnerability-disclosure policy read deterministically from the repo: a SECURITY.md (root/.github/docs) or .well-known/security.txt / security.txt, regex-checked for a reporting contact (email / URL / mailto). Present + contact → 10; present without a contact → 4; NotApplicable when no policy file exists (it may live off-repo). Detects the policy file's presence + contact, not its adequacy.
What it measures: Whether any dependency the repository declares is published as MALICIOUS rather than merely vulnerable — a package that is an attacker's work, in any ecosystem osv-scanner reads. Reported apart from D30 because the answer is binary: there is no safe version to upgrade to, and the fix is to remove the package and rotate every credential it could have read.
Method: The same dependency scan D30 reads, partitioned on the scanner's own classification rather than rescanned: a row is MALICIOUS when its id is in the `MAL-` space (the ossf/malicious-packages feed) OR its `database_specific.cwe_ids` carries `CWE-506` ("Embedded Malicious Code"). Both channels are structural; the summary text is deliberately NOT read, because a malicious-package record whose summary says only "Critical severity vulnerability" is a real shape ([GHSA redacted]) and a text matcher misses it. Scored BINARY: any surviving row is 0, whatever its severity and however many CVEs sit beside it — a hostile dependency is not a quantity. Applicability and degradation are D30's: NotApplicable only when no ecosystem is readable, and an unscannable ecosystem degrades rather than reading clean. Advisory since rubric-2026.11.2 (CAI decision 0006): the malicious-package feed is a database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.
What it measures: Whether anyone still ships security patches for the platform this repository RUNS ON — the runtime it pins and the framework majors its own constraints hold it to. Separate from D12 because the question differs: a current Django on an end-of-life Python is perfectly up to date and completely unsupported, and the fix is a migration rather than a version bump. What the repository says it merely SUPPORTS is never charged.
Method: End-of-life PLATFORM read from the repository's own declarations and graded against a FROZEN, dated table of vendor support dates — no network, no feed, no API, so this dimension answers identically inside a closed scan fence. Two subjects: a RUNTIME the project pins (a single or all-end-of-life TargetFramework, a .nvmrc or .python-version, a requires-python CAP) and a FRAMEWORK major a dependency constraint cannot move off (a caret, tilde or exact version; `vue@^2.7.16` pins Vue 2). A FLOOR is deliberately never charged — `requires-python = ">=3.8"` states what a package SUPPORTS, not what it runs on — and a multi-target project is charged only when EVERY target is out of support. Runtime 4.0/product capped 8.0, framework 1.5 capped 4.5. The table is safe to freeze because a statement about support that ended in the past cannot become false: it loses recall as it ages, never precision, and a test asserts every entry predates the freeze date. Disjoint from D31 (a container image's OS layer) and D29 (the toolchain a CI workflow installs). Abstains when the repository declares no platform this pass reads — never scores it clean.
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 14 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Other · Architecture — Whether any singleton service captures a scoped/transient dependency — a silent lifetime/threading bug.
Method: Roslyn scan: DI registrations parsed from AddSingleton/Scoped/Transient; each singleton checked for captured shorter-lifetime dependencies. Exhaustive, deterministic.
Other · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified. How each file's role is decided, because the split is only as good as that: a generated name or a build-output tree makes it Generated, a test project makes it Test, and otherwise the file's NAMESPACE and PATH words are matched against fixed vocabularies in a fixed ORDER — domain, then infrastructure, then application — so a file whose words hit two layers is counted under the earlier one. A production file matching none of them counts as application, so that share reads 'application or unclassified' rather than a measured application layer. Roles come from naming convention, never from what the code does. On this repository the split was taken from the source tree on disk rather than from a loaded .NET workspace, so a file's role is decided by its PATH segments alone — no declared namespace was available to add to the evidence — and generated output is excluded from the census entirely rather than counted as a generated share.
Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.
Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.
What to do
The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
Other · Architecture — Whether the project-reference graph is acyclic (cycles block independent build/deploy and signal eroding boundaries).
Method: Project reference cycles via elementary-DFS over real .csproj references, using the engine shared with D5/D7; cyclic versus acyclic. Exhaustive, deterministic.
Other · Architecture — Whether dependencies point inward (Domain ← Application ← Infrastructure/Web) — the clean-architecture dependency rule, checked across the project graph.
Method: Layer violations by name-segment inference (Domain/Core to Application to Infrastructure/Web) over the project-reference graph. Exhaustive over all projects, deterministic.
Do you agree with this assessment?
AX8 · Test isolation10.0 / 10Exemplary✓ Tool-verified
Other · Architecture — Whether production projects stay free of references to test projects — tests may depend on production, never the reverse.
Method: Csproj graph: each production project checked for references to test projects (identified by test-framework presence, not name). Zero violations is clean. Deterministic.
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.
Do you agree with this assessment?
DM4 · Rich vs anemic domain model3.0 / 10Weak✓ Tool-verified
Other · Domain Modelling — Whether domain entities own their behaviour — a data-only entity with public mutable state whose logic lives in a foreign service is anemic. Rich models enforce their own invariants; an immutable `@freezed`/`@immutable` value class is rich by construction.
Method: Roslyn (DDD-gated): entity method BODIES classified mutator-vs-query — only methods that mutate the entity's own declared state count as invariant-protecting behaviour, so a getter/passthrough doesn't rescue an anemic class. Deterministic, exhaustive over domain-layer entities.
Coverage: Population: entities by name/base convention; rich-vs-anemic judged by classifying each method body mutator-vs-query — logic-bearing domain types outside the convention are invisible.
`PublicData` is a data-only domain entity with public mutable state and no invariant-enforcing behaviour of its own, while the repo holds the logic in a foreign service/manager/use-case — the anemic domain model. Move the behaviour onto the entity so it enforces its own invariants (or make it an immutable `@freezed` value object) rather than being driven from outside. — packages/at_follows_flutter/lib/domain/atsign.dart:50
`ListStatus` is a data-only domain entity with public mutable state and no invariant-enforcing behaviour of its own, while the repo holds the logic in a foreign service/manager/use-case — the anemic domain model. Move the behaviour onto the entity so it enforces its own invariants (or make it an immutable `@freezed` value object) rather than being driven from outside. (×2) — packages/at_follows_flutter/lib/domain/connection_model.dart:192, packages/at_login_flutter/lib/domain/at_login_provider.dart:154
What to do
Move delegated behaviour onto the domain entity (or make it an immutable value object); keep invariants inside the type.
Other · Domain Modelling — Whether an entity protects its own invariants — a class whose identity is derived from its fields (value equality) but whose fields are publicly mutable bypasses that invariant. Encapsulated state keeps identity-bearing fields immutable.
Method: Roslyn (DDD-gated): entities scanned for publicly writable state — public setters, and (C#/VB) own mutable collections handed out through an auto-property, a public field or a bare-field expression getter, where a computed/copying getter is never charged. One finding per entity; score softened when Marten/EF rehydration frameworks present. Deterministic, framework-aware.
Coverage: Population: entities by convention; encapsulation (setter shape) checked exhaustively within the set.
Other · Code Health — Unreviewed-generation residue in this repository's Dart: methods whose whole body still throws UnimplementedError or a "not implemented" error, and placeholder text (lorem ipsum, changeme/replace_me…) left in strings of non-test, non-generated code. Scored as a quality signature, never as a claim about authorship.
Method: Roslyn syntax scan: NotImplementedException throws and placeholder string literals in non-test, non-generated shipped code. Deterministic, code-shape signature.
Other · Code Health — Unfinished work detected by code SHAPE, not keywords, in this repository's Dart: methods that only throw UnimplementedError or a "not implemented" exception, methods that take inputs and return a constant or do nothing, dead `if (false)` branches, and skeleton classes most of whose methods are holes.
Method: Roslyn syntax scan: incompleteness by code shape (constant-returning methods, async-never-await, #if false branches, guards that return what the code already falls through to, tests an earlier guard already decided, comparisons against NaN, skeleton types), not keyword-gated. Deterministic, code-shape heuristic.
`readPublicKey`'s body only throws an UnsupportedError or an UnimplementedError that gives its reason — sometimes a deliberate refusal, often an unfinished stub. Confirm it's intentional. — packages/at_chops/lib/src/at_chops_impl.dart:336
`handleRequest`'s body only throws an UnsupportedError or an UnimplementedError that gives its reason — sometimes a deliberate refusal, often an unfinished stub. Confirm it's intentional. — packages/at_client/lib/src/rpc/at_rpc.dart:109
`handleResponse`'s body only throws an UnsupportedError or an UnimplementedError that gives its reason — sometimes a deliberate refusal, often an unfinished stub. Confirm it's intentional. (×2) — packages/at_client/lib/src/rpc/at_rpc.dart:819, packages/at_policy/lib/src/policy/impl.dart:144
A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something. — packages/at_contact/test/at_group_test.dart:1
`checkInternetConnection` has an empty body — confirm it's an intentional no-op and not an unfinished method. — packages/at_location_flutter/lib/service/api_service.dart:124
What to do
Clear the softer debt: re-enable or delete tests marked `skip:`, decide whether each empty method or UnsupportedError is deliberate (and say so in a comment), and replace `// ignore_for_file: type=lint` with targeted, justified ignores.
Maturity · Maturity — Whether the repo and its projects have a README, and whether it's substantive and current.
Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.
What to do
Add a README to the 36 of 36 project(s) that lack one — worth up to 2 pts.
Maturity · Maturity — Whether the project's current-state documentation describes the code that exists.
Method: Every current-state document's checkable claims looked up in the tree (links, versions, and artefact counts an order of magnitude off), plus two README checks: an advertised infrastructure product with no footprint, and a module the CHANGELOG records as removed. Deterministic, no model. Advisory.
packages/at_contact/README.md links to `CONTRIBUTING.md`, but `packages/at_contact/CONTRIBUTING.md` does not exist. 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. — packages/at_contact/README.md:407
What to do
Reconcile the README with reality: packages/at_contact/README.md links to `CONTRIBUTING.md`, but `packages/at_contact/CONTRIBUTING.md` does not exist.
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 & versioning6.0 / 10Adequate✓ Tool-verified
Readiness · Readiness — For a library: a deliberate (small) public API surface and explicit semantic versioning so consumers can depend on it safely.
Method: Roslyn scan: public API surface area and semantic-versioning markers (SemVer attributes, changelog entries) for libraries; off .NET, a library is the ecosystem's publication act (an npm package that is not private and names an entry point, a PyPI distribution with a build system, a Rust library crate, a Maven/Gradle module that publishes, a Go module with no package main, a gemspec, a Composer library, a SwiftPM library product, a pub.dev or Hex package), its surface is the share of types the language's code 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.
1090/1217 types (90%) declared in the published library are public. For a library, every public type is a stability contract — keep implementation types off the surface and expose only the intended API.
What to do
Keep implementation types off the public surface (Dart: a `_` name, or keep it under `lib/src/` unexported; Kotlin: `internal`; Swift: leave it `internal` (the default) instead of `public`) so internals can change without breaking consumers.
Readiness · Readiness — Whether behaviour is captured as executable Gherkin specifications (a plus for shared understanding) — only assessed when a BDD framework is present.
Method: Filesystem scan: BDD framework presence (SpecFlow, Gherkin files) when a project references a BDD tool. Exhaustive, deterministic.
Do you agree with this assessment?
P2 · Observability7.0 / 10Strong✓ Tool-verified
Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.
Only 21/63 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `packages/at_chat_flutter/example`, `packages/at_chat_flutter/example/ios`, `packages/at_chat_flutter/example/macos`, `packages/at_client/example`, `packages/at_client_flutter/example/dockerstats/ios` and 37 more.
What to do
Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
Add a health-check endpoint (a /health route on your shelf router) so orchestrators and load balancers can probe liveness/readiness.
Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).
Method: Filesystem scan: SAST configuration, dependency-update automation, secret scanning, and a benchmark harness or benchmark step — in this repository's own ecosystem. Exhaustive, deterministic.
`.github/dependabot.yaml` schedules updates, but no `package-ecosystem` entry covers `gradle`, which this tree depends on — so those dependencies get no update pull requests and no advisory pressure, however complete the dep-scan credit looks. Add the missing entry to the `updates:` list. — .github/dependabot.yaml:2
What to do
Dependabot is configured but does not watch `gradle` — add that `package-ecosystem` entry to .github/dependabot.yml so those dependencies get the same automatic update and advisory pressure as the ones it already covers.
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
Readiness · Readiness — Whether releases are automated and safely reversible (probes, rolling updates, approval gates) — from manifests/pipeline files, not the live environment.
Method: Filesystem scan: deployment manifests/IaC (K8s YAML, Helm, Terraform) for rolling updates, probes, approval gates, migration hooks. Exhaustive, deterministic.
What to do
Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
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 14 use(s) across 124,481 production line(s) (~0.1/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.
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 each language's code model, a blocking call inside an async function (Python, TS/JS, Rust, Kotlin, Swift, Dart) or inside a Java method returning a Reactor Mono/Flux or a Scala method returning a Future or effect — and, for a .NET library with ≥5 awaits, the share of awaits using ConfigureAwait(false). Deterministic, syntax/text detection.
`_storage` is async and calls deleteSync, createSync — a blocking call inside async code stalls the isolate's event loop — every other event, on Flutter the next frame, waits for as long as it runs. — packages/at_client_flutter/example/invitations/lib/session.dart:232
`_probe` is async and calls createSync, writeAsStringSync, deleteSync — a blocking call inside async code stalls the isolate's event loop — every other event, on Flutter the next frame, waits for as long as it runs. — tools/wasm_shakedown/lib/runner.dart:114
`sendImageFile` is async and calls readAsBytesSync — a blocking call inside async code stalls the isolate's event loop — every other event, on Flutter the next frame, waits for as long as it runs. — packages/at_chat_flutter/lib/services/chat_service.dart:322
`onBackup` is async and calls writeAsStringSync — a blocking call inside async code stalls the isolate's event loop — every other event, on Flutter the next frame, waits for as long as it runs. — packages/at_client_flutter/example/lib/snippets/at_backup_key.dart:96
`_generateFile` is async and calls writeAsStringSync — a blocking call inside async code stalls the isolate's event loop — every other event, on Flutter the next frame, waits for as long as it runs. — packages/at_client_flutter/example/lib/snippets/at_backup_key.dart:232
`_acquire` is async and calls deleteSync — a blocking call inside async code stalls the isolate's event loop — every other event, on Flutter the next frame, waits for as long as it runs. — packages/at_auth/lib/src/keys/io/file_lock.dart:92
`createSecureSocket` is async and calls writeAsStringSync — a blocking call inside async code stalls the isolate's event loop — every other event, on Flutter the next frame, waits for as long as it runs. — packages/at_lookup/lib/src/io/secure_socket_util.dart:11
What to do
Dart: await the async dart:io API (readAsString, writeAsString, Process.run, Future.delayed) instead of the *Sync variant or sleep(), or move heavy synchronous work to another isolate with Isolate.run.
Other · Security — Read from this repository's Dart source: cryptographic hygiene (weak hash or cipher, key material fixed in the source) and outbound TLS certificate validation — facts about code that hold whether or not it serves anything itself. The TLS protocol version is not read: `dart:io` leaves the protocol floor to the platform's TLS library and has no switch that admits an obsolete version. This repository serves no HTTP of its own — no server framework among its pubspec dependencies, no `HttpServer` bound and no shelf, dart_frog or serverpod import in its production source or `bin/`. Its Flutter web build (`packages/at_notify_flutter/web/index.html`) compiles to static files that run in the browser and are served by whatever hosts them: static files cannot enforce HTTPS, send HSTS or any other response header, set an HttpOnly cookie or validate a request, so those controls are the host's, not this code's. Where this repository commits the host's configuration (an nginx, Caddy or Apache config, a serving Dockerfile, `_headers`, `vercel.json`, `netlify.toml`, `firebase.json`, `staticwebapp.config.json`) it is read for the security response headers it sets, and the shipped page is read for third-party scripts loaded without Subresource Integrity.
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.
MD5/SHA1 is computed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ (`sha256.convert(…)` from `package:crypto`) for content integrity, or a KDF (bcrypt/Argon2/scrypt) for password storage. If it only derives a non-security identifier (a cache key, an avatar URL, an ETag), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as xxhash or murmurhash says it in code — since the algorithm alone cannot distinguish the two uses. Where a protocol this code does not own fixes the digest (a k-anonymity range query, a legacy signature format), the protocol decides; say so beside the call. (×2) — packages/at_chops/lib/src/algorithm/hashing/md5.dart:9, packages/at_client/lib/src/util/encryption_util.dart:77
What to do
Review each MD5/SHA1 use by what it protects: replace it with SHA-256+ (or a KDF for passwords) where the digest is security-relevant, and switch it to a non-cryptographic hash (xxhash, murmurhash) where it only derives an identifier such as a cache key. This repository constructs a collision-broken hash (MD5/SHA1) at 2 sites, not one: `packages/at_chops/lib/src/algorithm/hashing/md5.dart:9` (md5.convert(…)), `packages/at_client/lib/src/util/encryption_util.dart:77` (md5.convert(…)). Each is a separate decision — fixing only the line this row cites leaves the others in place.
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.
`forEach` takes a `void` callback and never awaits what it returns, so the Future each `async` call returns is dropped: nothing can await it, the code after this loop runs before any of the awaited work has finished (a function that `await`s around this loop still returns early, and a resource it closes next is closed under the work), and an error is never handled — it surfaces as an uncaught asynchronous error, which terminates a command-line program and reaches only the zone's error handler in Flutter. Iterate with `for (final item in items) { await … }` when the work must run in order, or `await Future.wait(items.map((item) async { … }))` when it may run concurrently, so the enclosing function finishes only when the work does and its failures reach the caller. Where firing and forgetting is genuinely intended, make the callback's whole body a `try { … } catch (e) { … }` that handles the failure, so it cannot escape. (×2) — packages/at_events_flutter/lib/services/event_key_stream_service.dart:136, packages/at_events_flutter/lib/services/event_key_stream_service.dart:139
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.
`MapState` carries a disposal duty — it declares its own release — and it creates `_positionSink` itself (line 87, `StreamController.broadcast`), which makes that instance its own. Nothing in the class releases it — no `_positionSink.close()`, 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, `StreamController.broadcast` 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: `_positionSink.close();` in `dispose()` before `super.dispose()`. — packages/at_location_flutter/lib/map_content/flutter_map/src/map/map.dart:87
`_ChatScreenState` carries a disposal duty — a `State`, so the framework calls its `dispose()` when it leaves the tree — and it creates `_scrollController` itself (line 72, `ScrollController`), which makes that instance its own. Nothing in the class releases it — no `_scrollController.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, `ScrollController` 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: `_scrollController.dispose();` in `dispose()` before `super.dispose()`. — REDACTED:72
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. Also whether a `finally` that gives the primitive back unconditionally can run in a state where the method does not hold it: after a timed wait whose result was discarded, after an acquire inside the `try` that can fail, after the body already released it, or never, because a `return` left between the acquire and the `try`.
Method: Roslyn syntax: `try` statements whose `finally` releases a synchronisation primitive under a bare local-bool guard, where the method also TOOK that same primitive before the `try`, checked for a `return` of a bool literal whose value disagrees with the flag state the method's own straight-line assignments put it in. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether the work a diagnostic log line costs is paid only when that line is wanted — C# evaluates a call's arguments BEFORE the call, so a trace/debug message joined or projected out of a collection is built in full on every pass, and then discarded by a sink the shipped configuration leaves switched off.
Method: Roslyn syntax: log calls at a diagnostic level (a `Log`-prefixed method naming Trace/Debug/Verbose, or a bare `Debug`/`Trace`/`Verbose` on a receiver named for a logger), whose argument list is read for a call whose cost scales with a sequence — a LINQ operator, a materialisation, `string.Join`, a serializer — with no enclosing level check or conditional-compilation region. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `debug`/`trace`/`verbose` call on a receiver named for a logger, or a `log`-prefixed method naming the level, whose argument calls an array operator (`map`/`filter`/`reduce`/`sort`/…), `Array.from`, `Object.keys/values/entries`, `JSON.stringify`/`util.inspect` over anything but a literal, or an array `join` — outside any arrow or function passed as an argument, which the logger calls only when the level is on — with no enclosing `if`, `&&` or `?:` whose condition names a level, a level string, or the `NODE_ENV`/`__DEV__`/`DEV` build switch. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X24 · Document value interpolated into markup unescaped10.0 / 10Exemplary○ Nothing flagged
Other · Security — Whether text read out of the document being converted is escaped before it is written into generated markup — a value the document's author chose, interpolated into an attribute the surrounding literal delimits, can close that attribute and open another.
Method: Roslyn semantic model over the whole compilation: a string-typed `Value`/`InnerText`/`InnerXml`/`Text` member declared inside `DocumentFormat.OpenXml` or `System.Xml` is a taint SOURCE, propagated through assignments, returns, arguments, tuple elements and string composition to its transitive closure, then read at interpolated-string holes that sit in a markup position the surrounding literal itself delimits. Escaper/encoder calls and enclosing validator conditions cut the flow. Flow- and container-insensitive by construction. A second arm needs no provenance at all and reports a type that CONTRADICTS ITSELF — the same expression escaped at one delimited markup hole and interpolated raw at another hole in the same markup position of the same type, which the type's own escaping proves is a defect without knowing where the value came from. On a repository with no .NET source it reads JavaScript/TypeScript off the token stream with the same rule: a DOM read of raw document text (`getAttribute`, `textContent`, `innerText`, `nodeValue`) is the source, propagated through local bindings and string composition, and judged at template-literal and concatenation holes in the same two delimited markup positions; escapers and validating conditions cut it, and documentation-site, test, vendored and minified scripts are not read. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a value the caller is invited to supply is the value the type actually uses — a constructor parameter stored in a private field that nothing ever reads while the default it was given is spelled out a second time at the site that should have read it, a keyed lookup that falls back to a different setting than the one its key names while the same type falls back to the matching one for that same key, or a culture-sensitive parse given no format provider by a type that feeds its own settable culture to the same kind of parse elsewhere, or a number an entry point writes to standard output under the host's culture while the same entry point formats with the invariant culture elsewhere. Either way, every caller who supplies a value silently gets something else.
Method: Roslyn syntax: private instance fields of a non-partial type assigned in a constructor from one of its own parameters with a `??` fallback, checked for whether anything in the type body reads the field and whether that same fallback expression is spelled out again outside the constructor; and `??` fallbacks onto a member access from a lookup call carrying exactly one string literal, grouped by that key across the type and checked for a fallback member whose folded name disagrees with the key while a sibling site for the same key agrees with it. On a repository with no .NET source the first two arms read JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `#x`, `private` or `private` parameter-property instance field filled in the constructor from a parameter (or one member of one) through `??`/`||` or a parameter default, never read anywhere in the file by name, whose constructed default is spelled again in the class body; and `lookup("key") ?? s.member` grouped by key per class, or per module outside every class. The culture arm has no JavaScript counterpart: its parses take no locale. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a value handed from a callback to the body that waits on it crosses on something built to be crossed — a `Queue<T>`/`List<T>`/`Dictionary<K,V>` written inside an event handler and read back outside it is mutated by two flows at once, and the semaphore or completion source beside it orders how MANY items exist while leaving the collection's own head, tail and backing array unprotected.
Method: Roslyn syntax: method, accessor, local-function and lambda bodies that declare BOTH a non-thread-safe generic collection (`Queue`/`Stack`/`List`/`Dictionary`/`HashSet`/`Sorted*`/`LinkedList`) and a synchronisation primitive (`SemaphoreSlim`/`TaskCompletionSource`/`ManualResetEvent(Slim)`/`AutoResetEvent`/`CountdownEvent`) as locals, then read for a `+=`-registered lambda that raises that primitive while the body outside every lambda waits on it — and, in that scope, a mutating call on the collection inside the lambda paired with a mention of it outside. Any `lock` in the scope abstains it. On a repository with no .NET source the same handoff is read in Java off the engine’s own token stream (test source sets, vendored and demonstration paths not): an `ArrayList`/`LinkedList`/`ArrayDeque`/`PriorityQueue`/`Hash*`/`LinkedHash*`/`Tree*` local and a `CountDownLatch`/`Semaphore`/`CompletableFuture` local, a lambda or anonymous class that raises the primitive and mutates the collection, and a wait outside it; any `synchronized` or `lock()` abstains the body. Because each of those primitives orders what the callback wrote before raising it, only a touch that provably overlaps the callback is convicted: one after the registration and before the next wait, or one in a loop registered-before, waiting on every pass and not declaring the collection. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X27 · Collection changed while being enumerated10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether 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 (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.
`on Object` 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. (×2) — packages/at_telemetry/lib/src/signers/at_telemetry_ed25519_signer.dart:64, packages/at_telemetry/lib/src/http_signatures/at_telemetry_http_signature.dart:263
`catch (e)` 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. (×12) — packages/at_location_flutter/lib/service/contact_service.dart:83, packages/at_location_flutter/lib/service/master_location_service.dart:213, packages/at_location_flutter/lib/service/request_location_service.dart:353, …
`on Exception` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. (×10) — packages/at_commons/lib/src/verb/notify_list_verb_builder.dart:32, packages/at_client_flutter/lib/src/widgets/authorisation/containers/enrollment_request_list.dart:163, packages/at_client_cli/lib/src/commands/auth_cli.dart:1009, …
`catch (_)` 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. (×8) — packages/at_client_flutter/lib/src/widgets/atsign_rootdomain_dialog.dart:60, packages/at_client_flutter/lib/src/widgets/atsign_rootdomain_dialog.dart:72, packages/at_client/lib/src/secret_sharing/enrollment_directory.dart:314, …
An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. — packages/at_client_cli/lib/src/commands/auth_cli.dart:123
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 Dart's sound null safety is on and is not undermined by null assertions — a package whose `environment: sdk:` lower bound is 2.12 or above is null safe, so `String` cannot hold null and `String?` must be checked before use, and each postfix `!` is a run-time `Null check operator used on a null value` the author has told the analyzer cannot happen.
Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.
~25.7 `!` null assertions per 1k Dart product lines — 3212 across the 124809 line(s) of the 788 Dart file(s) read (generated, test and example code not counted; a file opted out with a `// @dart=` comment below 2.12 counts once). Densest: packages/at_events_flutter/lib/services/event_key_stream_service.dart (164), packages/at_events_flutter/lib/screens/recurring_event.dart (125), packages/at_location_flutter/lib/map_content/flutter_map_marker_cluster/src/marker_cluster_layer.dart (122). Each one tells the analyzer to trust the author about null and becomes a `Null check operator used on a null value` the first time the author is wrong.
What to do
Raise every package's `environment: sdk:` lower bound to 2.12 or above (`^3.0.0` today) and migrate with `dart migrate` on an SDK that still has it, so `String` and `String?` mean different things. Then replace assertions rather than adding to them: each `!` is a run-time null check the analyzer could not prove — promote the value with a null check or an early return, use `?.` / `??` where absence is legitimate, make the field non-nullable and `late final` only where initialisation is truly guaranteed, or change the API so the null cannot arrive.
Do you agree with this assessment?
Reference — by lens
The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.
Unscored — 2 check(s) recorded observations but carry no score
These checks ran and found something, but they do not carry a score — either by design (an advisory check reports evidence rather than grading it) or because they could not be scored here. They are excluded from the score for that reason, not because there was nothing to see.
X10 Duplicated predicate — 24 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X7 Silent fallback defaults — 2 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 4 control(s) we could not find positive evidence for
These checks grade a working control, and the repository shows no evidence of one. That is deliberately not scored as a zero: a repository cannot show an ops runbook, a database TTL or an infrastructure-side audit log, so absence of evidence here is not evidence the control is missing. It is also not a statement that the check is irrelevant to this codebase — the thing it grades applies; we just could not see it. Excluded from the score either way.
C3 Audit Trail — Not assessed: this repository stores data through 'package:hive' (packages/at_client/lib/src/storage/hive/hive_at_client_storage.dart:10) but declares no persisted model this check reads (Drift tables, ObjectBox/Floor @Entity, Isar @collection and Hive @HiveType classes, Serverpod table models). Personal data may be written through raw SQL or a hosted backend, so whether its changes need an audit trail could not be established, and the trail's absence is not scored.
C4 Data Retention — Not assessed: this repository stores data through 'package:hive' (packages/at_client/lib/src/storage/hive/hive_at_client_storage.dart:10) but declares no persisted model this check reads (Drift tables, ObjectBox/Floor @Entity, Isar @collection and Hive @HiveType classes, Serverpod table models). Personal data may be written through raw SQL or a hosted backend, so whether a retention limit applies here could not be established, and its absence is not scored.
C5 Data-Subject Rights — Not assessed: this repository stores data through 'package:hive' (packages/at_client/lib/src/storage/hive/hive_at_client_storage.dart:10) but declares no persisted model this check reads (Drift tables, ObjectBox/Floor @Entity, Isar @collection and Hive @HiveType classes, Serverpod table models). Personal data may be written through raw SQL or a hosted backend, so whether data-subject rights apply here could not be established, and their absence is not scored.
P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 50 check(s) not relevant to this codebase
These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.
AC1 Text alternatives — Frontend below the scale floor (16 DOM element(s) < 25) — too little surface to assess accessibility.
AC2 Forms & labels — Frontend below the scale floor (16 DOM element(s) < 25) — too little surface to assess accessibility.
AC3 Page structure — Frontend below the scale floor (16 DOM element(s) < 25) — too little surface to assess accessibility.
AC4 Keyboard semantics — Frontend below the scale floor (16 DOM element(s) < 25) — too little surface to assess accessibility.
AC5 ARIA correctness — Frontend below the scale floor (16 DOM element(s) < 25) — too little surface to assess accessibility.
AC6 Visual & motion safety — Frontend below the scale floor (16 DOM element(s) < 25) — too little surface to assess accessibility.
AC7 A11y enforcement — Frontend below the scale floor (16 DOM element(s) < 25) — too little surface to assess accessibility.
AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No class in this Kotlin code is a Spring, JSR-330 or CDI singleton bean. No function in this Python code is served by a threaded web framework (a Flask, Bottle or FastAPI route, a Django or Pyramid view), so no module is shared between request threads. No Swift request handler (a Vapor, Hummingbird, Kitura, Swifter or Perfect route handler, as a method or a registered closure) is declared, so no state is shared between request threads. Dart isolates share no mutable memory, so no two requests write one object at the same instant. TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX6 Interface segregation — not assessed — interface segregation is computed over a type surface 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
AXB1 Runtime evidence locked — no reproducible boot — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
C1 Data Protection — Not assessed: this repository stores data through 'package:hive' (packages/at_client/lib/src/storage/hive/hive_at_client_storage.dart:10) but declares no persisted model this check reads (Drift tables, Isar/ObjectBox/Floor/Hive entities, Serverpod table models). Personal data may be written through raw SQL or a hosted backend, so the absence of a personal-data field here is not evidence that none is stored, and encryption at rest is not scored over a subject that could not be established.
C2 Access Controls — No access-control surface detected in the analyzed source — this repository stands up no server another machine can reach (no HttpServer or shelf server bound beyond loopback, no dart_frog route, no Serverpod endpoint, no Conduit, Alfred or Angel application) and keeps no data in a hosted backend. Access control is therefore N/A here — a Flutter app or pub package is authorized by the server it calls, not by itself; hiding a screen authorizes nothing. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
D10 Test Quality — ~156660 lines of test source are present (.dart) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
D11 Test Reliability — Test reliability not included — no .dart test runner
D12 Dependency Hygiene — Not scored — 36 Maven/Gradle manifest(s) were read, stating a version for 0 dependency(ies) and leaving 18 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 — pub package licences not graded — the lock-less pubspec's graph could not be read in full
D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
D21 Naming Consistency — Naming consistency is measured on C# and TypeScript only; Dart, JavaScript, Kotlin, Python, Swift, html not measured.
D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only; comments in this repository's .dart, .kt, .py, .swift source were not judged.
D25 ADR Conformance — None of 0 binding record(s) states a rule in checkable form (a backticked element with a prohibition, or an `adr-rules` block), so conformance cannot be read from the code. Write the rule as an `adr-rules` block (`forbid:` a symbol, a package or a dependency) to make it checkable.
D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.dart), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
D32 Data Compliance (PII/GDPR) — 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.
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.
D8 Code Coverage — Coverage not included — suite not readable by the collector
DM1 Aggregate boundaries — no aggregates detected — aggregate-boundary check not applicable
DM2 Strongly-typed ids — no in-repo typed-id idiom — primitive-obsession recorded as advisory DM8, DM2 not gated
DM3 Integration-event coupling — no integration events detected — coupling check not applicable
DM6 Domain ↔ infrastructure boundary — this Dart repository maps no type to a persistence framework (drift/floor/isar/objectbox/hive), so DM6's domain↔infrastructure fusion read has no population to be taken over
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
P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
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 (lcov — `flutter test --coverage` (or `dart test --coverage=coverage` then `dart run coverage:format_coverage --lcov`)) 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 classes extending benchmark_harness's `BenchmarkBase`, `AsyncBenchmarkBase` or `PerfBenchmarkBase` (directly or through a base of your own), `benchmark(…)` calls under the pub `benchmark` package, Flutter's `benchmarkWidgets`, `watchPerformance` or `traceAction` in a test importing flutter_test, integration_test or flutter_driver, or benchmark_harness, benchmark or web_benchmarks in a pubspec.yaml, 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 — 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
X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
X4 Structured logging — This check asks whether log calls keep a message's values apart from its text, which needs a logger that can carry them as fields. This repository's Dart was read, and it logs through none: package:logging, package:logger, talker and dart:developer take one finished message and no template arguments or fields (as log4net does in C#), so an interpolated message there loses nothing the API could have kept. Sentry's structured logs (`Sentry.logger`) would be judged.
X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
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.
Orphaned knowledge packages/at_location_flutter/lib/map_content/flutter_map/src/layer/tile_layer.dart:1— No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
Orphaned knowledge packages/at_events_flutter/lib/services/event_key_stream_service.dart:1— No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
Orphaned knowledge packages/at_events_flutter/lib/screens/create_event.dart:1— No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
Orphaned knowledge packages/at_location_flutter/lib/map_content/flutter_map_marker_cluster/src/marker_cluster_layer.dart:1— No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
Orphaned knowledge packages/at_contacts_group_flutter/lib/screens/group_contact_view/group_contact_view.dart:1— No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
Orphaned knowledge packages/at_contact/lib/src/at_contacts_impl.dart:1— No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
Orphaned knowledge packages/at_contacts_group_flutter/lib/screens/edit/group_edit.dart:1— No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
Orphaned knowledge packages/at_contacts_group_flutter/lib/desktop_screens/desktop_group_detail.dart:1— No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
DM4 · Rich vs anemic domain model· Anemic domain model · ×3
Anemic domain model: PublicData packages/at_follows_flutter/lib/domain/atsign.dart:50— `PublicData` is a data-only domain entity with public mutable state and no invariant-enforcing behaviour of its own, while the repo holds the logic in a foreign service/manager/use-case — the anemic domain model. Move the behaviour onto the entity so it enforces its own invariants (or make it an immutable `@freezed` value object) rather than being driven from outside.
Anemic domain model: ListStatus packages/at_follows_flutter/lib/domain/connection_model.dart:192— `ListStatus` is a data-only domain entity with public mutable state and no invariant-enforcing behaviour of its own, while the repo holds the logic in a foreign service/manager/use-case — the anemic domain model. Move the behaviour onto the entity so it enforces its own invariants (or make it an immutable `@freezed` value object) rather than being driven from outside.
Anemic domain model: ListStatus packages/at_login_flutter/lib/domain/at_login_provider.dart:154— `ListStatus` is a data-only domain entity with public mutable state and no invariant-enforcing behaviour of its own, while the repo holds the logic in a foreign service/manager/use-case — the anemic domain model. Move the behaviour onto the entity so it enforces its own invariants (or make it an immutable `@freezed` value object) rather than being driven from outside.
MethodTooLong: _CreateEventState.build packages/at_events_flutter/lib/screens/create_event.dart:73— MethodTooLong — build runs 276 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 176 over it, 2.76× 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: _RecurringEventState.build packages/at_events_flutter/lib/screens/recurring_event.dart:48— MethodTooLong — build runs 270 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 170 over it, 2.70× 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: _DesktopGroupDetailState.build packages/at_contacts_group_flutter/lib/desktop_screens/desktop_group_detail.dart:52— MethodTooLong — build runs 256 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 156 over it, 2.56× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: _GroupViewState.build packages/at_contacts_group_flutter/lib/screens/group_view/group_view.dart:52— MethodTooLong — build runs 232 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 132 over it, 2.32× 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: _EventNotificationDialogState.build packages/at_events_flutter/lib/screens/notification_dialog/event_notification_dialog.dart:108— MethodTooLong — build runs 216 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 116 over it, 2.16× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: _EventsCollapsedContentState.build packages/at_events_flutter/lib/screens/map_screen/events_collapsed_content.dart:45— MethodTooLong — build runs 200 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 100 over it, 2.00× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: _CollapsedContentState.build packages/at_location_flutter/lib/common_components/collapsed_content.dart:65— MethodTooLong — build runs 199 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 99 over it, 1.99× 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: _GroupContactViewState.build packages/at_contacts_group_flutter/lib/screens/group_contact_view/group_contact_view.dart:101— MethodTooLong — build runs 177 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 77 over it, 1.77× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: _DesktopContactsScreenState.build packages/at_contacts_flutter/lib/desktop_screens/desktop_contacts_screen.dart:65— MethodTooLong — build runs 176 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 76 over it, 1.76× 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: _GroupListState.build packages/at_contacts_group_flutter/lib/screens/list/group_list.dart:63— MethodTooLong — build runs 171 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 71 over it, 1.71× 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: _ApkamActivationDialogState.build packages/at_client_flutter/lib/src/widgets/apkam_dialog.dart:392— MethodTooLong — build runs 168 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 68 over it, 1.68× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: _SelectLocationState.build packages/at_events_flutter/lib/screens/select_location.dart:52— MethodTooLong — build runs 168 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 68 over it, 1.68× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: _OneDayEventState.build packages/at_events_flutter/lib/screens/one_day_event.dart:35— MethodTooLong — build runs 167 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 67 over it, 1.67× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: _GroupEditState.build packages/at_contacts_group_flutter/lib/screens/edit/group_edit.dart:93— MethodTooLong — build runs 158 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 58 over it, 1.58× 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: _FollowersState.build packages/at_follows_flutter/lib/widgets/followers.dart:47— MethodTooLong — build runs 157 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 57 over it, 1.57× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: _DesktopNewGroupState.build packages/at_contacts_group_flutter/lib/desktop_screens/desktop_new_group.dart:134— MethodTooLong — build runs 154 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 54 over it, 1.54× 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: _RegistrarCramDialogState.build packages/at_client_flutter/lib/src/widgets/registrar_cram_dialog.dart:162— MethodTooLong — build runs 146 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 46 over it, 1.46× 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: _EnrollmentRequestCardState.build packages/at_client_flutter/lib/src/widgets/authorisation/components/enrollment_request_card.dart:27— MethodTooLong — build runs 143 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 43 over it, 1.43× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: EnrollmentSubmitter._handleSelfEnrollmentRequest packages/at_auth/lib/src/enroll/enrollment_submitter.dart:418— MethodTooLong — _handleSelfEnrollmentRequest 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: _NewGroupState.build packages/at_contacts_group_flutter/lib/screens/new_group/new_group.dart:114— MethodTooLong — build runs 136 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 36 over it, 1.36× 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: SyncServiceImpl._pushFromSyncQueue packages/at_client/lib/src/service/sync_service_impl.dart:674— MethodTooLong — _pushFromSyncQueue runs 135 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 35 over it, 1.35× 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: _OverlappingContactsState.build packages/at_events_flutter/lib/common_components/overlapping_contacts.dart:23— MethodTooLong — build runs 130 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 30 over it, 1.30× 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: AtAuthImpl.onboard packages/at_auth/lib/src/at_auth_impl.dart:82— MethodTooLong — onboard runs 119 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 19 over it, 1.19× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: PqSigningChain.walkFrom packages/at_client/lib/src/crypto/nskey/pq_signing_chain.dart:349— MethodTooLong — walkFrom runs 118 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 18 over it, 1.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: _CircularContactsState.build packages/at_contacts_group_flutter/lib/widgets/circular_contacts.dart:96— MethodTooLong — build runs 117 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 17 over it, 1.17× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
TodoComment tests/at_client_cli_functional_tests/test/at_onboarding_cli_test.dart:233— /// ToDo: test should NOT exit with status 0 after activation is complete — 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 packages/at_lookup/test/secondary_address_cache_test.dart:133— // TODO Why are these tests commented out? — 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 packages/at_lookup/lib/src/at_lookup_impl.dart:288— // TODO: Can we remove the below catch block in next release once all the servers are migrated to new version. — 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 packages/at_login_flutter/lib/widgets/at_login_dashboard_widget.dart:215— // // TODO add confirmation dialog — 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 packages/at_login_flutter/example/lib/main.dart:21— // TODO set the rest of your AtClientPreference here — 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 packages/at_location_flutter/example/lib/main.dart:26— // TODO set the rest of your AtClientPreference here — 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 packages/at_follows_flutter/example/lib/main.dart:25— // TODO set the rest of your AtClientPreference here — 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 packages/at_contacts_flutter/example/lib/main.dart:26— // TODO set the rest of your AtClientPreference here — 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 packages/at_location_flutter/lib/utils/constants/init_location_service.dart:89— // TODO: verify receiver — 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 packages/at_events_flutter/lib/services/event_key_stream_service.dart:96— ///// TODO: Uncomment if any issues with keys — 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 packages/at_contacts_group_flutter/lib/services/group_service.dart:172— // TODO: Delete log — 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 packages/at_contacts_group_flutter/lib/services/group_service.dart:179— // TODO : delete log — 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 packages/at_contacts_group_flutter/lib/desktop_screens/desktop_empty_group.dart:8— /// TODO: — 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 packages/at_contact/lib/src/service/util_service.dart:1— // TODO intl is one of the plague packages of we should remove it — 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 packages/at_client_flutter/lib/src/keychain/keychain_storage.dart:65— // TODO(3.0.0): copy `_` to `:` then remove `_`. — 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 packages/at_client_flutter/lib/src/keychain/keychain_storage.dart:298— /// TODO(3.0.0): remove the `_` cleanup once `_` stores are deleted during — 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 packages/at_client_flutter/lib/src/keychain/keychain_store.dart:25— // TODO(3.0.0): remove once migration deletes `_` stores in-place. — 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 packages/at_client_flutter/example/todos/lib/services/todos_service.dart:308— // todo rather than stranding on the atServer. — 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 packages/at_client_cli/lib/src/commands/auth_cli.dart:834— // TODO Factor out code which is shared between here and main() — 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 packages/at_client/test/legacy_encryption_decryption_test.dart:168— // TODO: implement describe — 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 packages/at_client/lib/src/util/at_client_util.dart:129— // TODO Remove this once AtUtils.fixAtSign accepts and returns String? — 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 packages/at_client/lib/src/client/local_secondary.dart:405— // TODO Track this down; it's either in atServer receiving from another — 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 packages/at_client/example/lib/todos_tui/types.dart:8— /// todo paired with its current notes. — 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 packages/at_chops/test/hpke_wg_kem_vectors.dart:8— /// on 2026-09-03**. Its own appendix is titled "Test vectors # TODO: replace — 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 packages/at_chops/test/x_wing_algo_test.dart:54— // above come from an appendix its own authors mark TODO, in a draft that — 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.
Swallowed exception (caught, then discarded) packages/at_telemetry/lib/src/signers/at_telemetry_ed25519_signer.dart:64— `on Object` 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) packages/at_telemetry/lib/src/http_signatures/at_telemetry_http_signature.dart:263— `on Object` 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) packages/at_location_flutter/lib/service/contact_service.dart:83— `catch (e)` 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) packages/at_location_flutter/lib/service/master_location_service.dart:213— `catch (e)` 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) packages/at_location_flutter/lib/service/request_location_service.dart:353— `catch (e)` 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) packages/at_location_flutter/lib/map_content/flutter_map/src/geo/crs/crs.dart:46— `catch (e)` 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) packages/at_location_flutter/lib/map_content/flutter_map/src/geo/crs/crs.dart:273— `catch (e)` 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) packages/at_events_flutter/lib/utils/init_events_service.dart:123— `catch (e)` 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) packages/at_events_flutter/lib/utils/init_events_service.dart:153— `catch (e)` 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) packages/at_events_flutter/lib/services/contact_service.dart:91— `catch (e)` 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) packages/at_contacts_flutter/lib/services/contact_service.dart:502— `catch (e)` 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) packages/at_commons/lib/src/verb/notify_list_verb_builder.dart:32— `on Exception` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) packages/at_client_flutter/lib/src/widgets/atsign_rootdomain_dialog.dart:60— `catch (_)` 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) packages/at_client_flutter/lib/src/widgets/atsign_rootdomain_dialog.dart:72— `catch (_)` 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) packages/at_client_flutter/lib/src/widgets/authorisation/containers/enrollment_request_list.dart:163— `on Exception` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) packages/at_client_cli/lib/src/commands/auth_cli.dart:1009— `on Exception` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) packages/at_client_cli/lib/src/commands/auth_cli.dart:1142— `on Exception` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) packages/at_client/lib/src/storage/memory/memory_at_key_value_store.dart:443— `on Exception` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) packages/at_client/lib/src/secret_sharing/enrollment_directory.dart:314— `catch (_)` 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) packages/at_client/lib/src/crypto/nskey/pq_signing_root.dart:911— `catch (e)` 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) packages/at_client/lib/src/crypto/nskey/verified_advertisement_record.dart:150— `on Exception` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) packages/at_client/lib/src/crypto/nskey/verified_advertisement_record.dart:165— `on Exception` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) packages/at_client/lib/src/client/at_client_factory.dart:113— `on Exception` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) packages/at_client/lib/src/client/at_client_impl.dart:1254— `on Exception` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) packages/at_client/lib/src/client/local_secondary.dart:423— `on Exception` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Hotspot: packages/at_client/lib/src/client/at_client_impl.dart packages/at_client/lib/src/client/at_client_impl.dart:1861— packages/at_client/lib/src/client/at_client_impl.dart changed 162 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 19 in AtClientImpl._putInternal at line 1861. 61 of those changes were fix/bug commits, and the other 101 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-07..2026-11-05, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-07 19:58:15 +05:30' --until='2026-11-05 19:58:15 +05:30' --full-history --no-merges -- packages/at_client/lib/src/client/at_client_impl.dart`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/at_client/lib/src/service/sync_service_impl.dart packages/at_client/lib/src/service/sync_service_impl.dart:674— packages/at_client/lib/src/service/sync_service_impl.dart changed 64 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 32 in SyncServiceImpl._pushFromSyncQueue at line 674. 32 of those changes were fix/bug commits, and the other 32 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-07..2026-11-05, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-07 19:58:15 +05:30' --until='2026-11-05 19:58:15 +05:30' --full-history --no-merges -- packages/at_client/lib/src/service/sync_service_impl.dart`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/at_client/lib/src/crypto/nskey/published_nskey_key_ring.dart packages/at_client/lib/src/crypto/nskey/published_nskey_key_ring.dart:1104— packages/at_client/lib/src/crypto/nskey/published_nskey_key_ring.dart changed 84 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 21 in PublishedNskeyKeyRing._publishedAt at line 1104. 46 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-07..2026-11-05, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-07 19:58:15 +05:30' --until='2026-11-05 19:58:15 +05:30' --full-history --no-merges -- packages/at_client/lib/src/crypto/nskey/published_nskey_key_ring.dart`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/at_client/lib/src/crypto/nskey/pq_signing_chain.dart packages/at_client/lib/src/crypto/nskey/pq_signing_chain.dart:349— packages/at_client/lib/src/crypto/nskey/pq_signing_chain.dart changed 48 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 29 in PqSigningChain.walkFrom at line 349. 17 of those changes were fix/bug commits, and the other 31 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-07..2026-11-05, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-07 19:58:15 +05:30' --until='2026-11-05 19:58:15 +05:30' --full-history --no-merges -- packages/at_client/lib/src/crypto/nskey/pq_signing_chain.dart`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/at_client/lib/src/secret_sharing/pairwise_secret_sharing.dart packages/at_client/lib/src/secret_sharing/pairwise_secret_sharing.dart:875— packages/at_client/lib/src/secret_sharing/pairwise_secret_sharing.dart changed 47 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 27 in PairwiseSecretSharing._handleRequestPayload at line 875. 27 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-07..2026-11-05, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-07 19:58:15 +05:30' --until='2026-11-05 19:58:15 +05:30' --full-history --no-merges -- packages/at_client/lib/src/secret_sharing/pairwise_secret_sharing.dart`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/at_client/lib/src/crypto/nskey/ck_manager.dart packages/at_client/lib/src/crypto/nskey/ck_manager.dart:121— packages/at_client/lib/src/crypto/nskey/ck_manager.dart changed 52 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 23 in CkManager.ensureCurrent at line 121. 27 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-07..2026-11-05, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-07 19:58:15 +05:30' --until='2026-11-05 19:58:15 +05:30' --full-history --no-merges -- packages/at_client/lib/src/crypto/nskey/ck_manager.dart`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/at_lookup/lib/src/at_lookup_impl.dart packages/at_lookup/lib/src/at_lookup_impl.dart:205— packages/at_lookup/lib/src/at_lookup_impl.dart changed 55 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 20 in AtLookupImpl.executeVerb at line 205. 23 of those changes were fix/bug commits, and the other 32 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-07..2026-11-05, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-07 19:58:15 +05:30' --until='2026-11-05 19:58:15 +05:30' --full-history --no-merges -- packages/at_lookup/lib/src/at_lookup_impl.dart`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/at_client/lib/src/service/notification_service_impl.dart packages/at_client/lib/src/service/notification_service_impl.dart:659— packages/at_client/lib/src/service/notification_service_impl.dart changed 69 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 15 in NotificationServiceImpl.handleNotificationReceipt at line 659. 33 of those changes were fix/bug commits, and the other 36 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-07..2026-11-05, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-07 19:58:15 +05:30' --until='2026-11-05 19:58:15 +05:30' --full-history --no-merges -- packages/at_client/lib/src/service/notification_service_impl.dart`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/at_client/lib/src/signing/signing_key_minting.dart packages/at_client/lib/src/signing/signing_key_minting.dart:58— packages/at_client/lib/src/signing/signing_key_minting.dart changed 32 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 26 in SigningKeyMinting.reconcileSigningKeys at line 58. 10 of those changes were fix/bug commits, and the other 22 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-07..2026-11-05, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-07 19:58:15 +05:30' --until='2026-11-05 19:58:15 +05:30' --full-history --no-merges -- packages/at_client/lib/src/signing/signing_key_minting.dart`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/at_client/lib/src/crypto/nskey/nskey_seeding.dart packages/at_client/lib/src/crypto/nskey/nskey_seeding.dart:525— packages/at_client/lib/src/crypto/nskey/nskey_seeding.dart changed 48 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 17 in NskeySeeding.requestMissingPrivates at line 525. 24 of those changes were fix/bug commits, and the other 24 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-07..2026-11-05, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-07 19:58:15 +05:30' --until='2026-11-05 19:58:15 +05:30' --full-history --no-merges -- packages/at_client/lib/src/crypto/nskey/nskey_seeding.dart`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/at_client/lib/src/secret_sharing/key_package_minting.dart packages/at_client/lib/src/secret_sharing/key_package_minting.dart:92— packages/at_client/lib/src/secret_sharing/key_package_minting.dart changed 27 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 26 in KeyPackageMinting.reconcileKeyPackage at line 92. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-07..2026-11-05, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-07 19:58:15 +05:30' --until='2026-11-05 19:58:15 +05:30' --full-history --no-merges -- packages/at_client/lib/src/secret_sharing/key_package_minting.dart`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/at_auth/lib/src/at_auth_impl.dart packages/at_auth/lib/src/at_auth_impl.dart:399— packages/at_auth/lib/src/at_auth_impl.dart changed 35 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 15 in AtAuthImpl.validateAtServer at line 399. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-07..2026-11-05, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-07 19:58:15 +05:30' --until='2026-11-05 19:58:15 +05:30' --full-history --no-merges -- packages/at_auth/lib/src/at_auth_impl.dart`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/at_auth/lib/src/enroll/enrollment_submitter.dart packages/at_auth/lib/src/enroll/enrollment_submitter.dart:418— packages/at_auth/lib/src/enroll/enrollment_submitter.dart changed 30 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 17 in EnrollmentSubmitter._handleSelfEnrollmentRequest at line 418. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-07..2026-11-05, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-07 19:58:15 +05:30' --until='2026-11-05 19:58:15 +05:30' --full-history --no-merges -- packages/at_auth/lib/src/enroll/enrollment_submitter.dart`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/at_auth/lib/src/enroll/enrollment_handshake.dart packages/at_auth/lib/src/enroll/enrollment_handshake.dart:250— packages/at_auth/lib/src/enroll/enrollment_handshake.dart changed 23 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 21 in EnrollmentHandshake._waitForPkamAuthSuccess at line 250. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-07..2026-11-05, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-07 19:58:15 +05:30' --until='2026-11-05 19:58:15 +05:30' --full-history --no-merges -- packages/at_auth/lib/src/enroll/enrollment_handshake.dart`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/at_auth/lib/src/keys/serialization/assurance.dart packages/at_auth/lib/src/keys/serialization/assurance.dart:267— packages/at_auth/lib/src/keys/serialization/assurance.dart changed 26 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 18 in AtKeysAssurance.validateMapUpdate at line 267. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-07..2026-11-05, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-07 19:58:15 +05:30' --until='2026-11-05 19:58:15 +05:30' --full-history --no-merges -- packages/at_auth/lib/src/keys/serialization/assurance.dart`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/at_client/lib/src/crypto/nskey/symmetric_aes_gcm_provider.dart packages/at_client/lib/src/crypto/nskey/symmetric_aes_gcm_provider.dart:294— packages/at_client/lib/src/crypto/nskey/symmetric_aes_gcm_provider.dart changed 25 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 17 in SymmetricAesGcmProvider._resolveFromConveyance at line 294. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-07..2026-11-05, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-07 19:58:15 +05:30' --until='2026-11-05 19:58:15 +05:30' --full-history --no-merges -- packages/at_client/lib/src/crypto/nskey/symmetric_aes_gcm_provider.dart`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/at_client/lib/src/lifecycle/pending_enrollment.dart packages/at_client/lib/src/lifecycle/pending_enrollment.dart:90— packages/at_client/lib/src/lifecycle/pending_enrollment.dart changed 24 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 15 in PendingEnrollment.awaitApproval at line 90. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-07..2026-11-05, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-07 19:58:15 +05:30' --until='2026-11-05 19:58:15 +05:30' --full-history --no-merges -- packages/at_client/lib/src/lifecycle/pending_enrollment.dart`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/at_client/lib/src/collections/collections.dart packages/at_client/lib/src/collections/collections.dart:1411— packages/at_client/lib/src/collections/collections.dart changed 14 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 20 in AtCollection._getItemsAsStreamInternal at line 1411. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-07..2026-11-05, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-07 19:58:15 +05:30' --until='2026-11-05 19:58:15 +05:30' --full-history --no-merges -- packages/at_client/lib/src/collections/collections.dart`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/at_client_flutter/example/lib/snippets/at_backup_key.dart packages/at_client_flutter/example/lib/snippets/at_backup_key.dart:96— packages/at_client_flutter/example/lib/snippets/at_backup_key.dart changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 19 in BackupKeyWidget.onBackup at line 96. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-07..2026-11-05, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-07 19:58:15 +05:30' --until='2026-11-05 19:58:15 +05:30' --full-history --no-merges -- packages/at_client_flutter/example/lib/snippets/at_backup_key.dart`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/at_telemetry/lib/src/codecs/at_telemetry_logs_codec.dart packages/at_telemetry/lib/src/codecs/at_telemetry_logs_codec.dart:255— packages/at_telemetry/lib/src/codecs/at_telemetry_logs_codec.dart changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 19 in AtTelemetryLogsCodec._decodeValue at line 255. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-07..2026-11-05, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-07 19:58:15 +05:30' --until='2026-11-05 19:58:15 +05:30' --full-history --no-merges -- packages/at_telemetry/lib/src/codecs/at_telemetry_logs_codec.dart`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/at_client_flutter/example/invitations/lib/screens/received.dart packages/at_client_flutter/example/invitations/lib/screens/received.dart:135— packages/at_client_flutter/example/invitations/lib/screens/received.dart changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 15 in _ReceivedScreenState.build at line 135. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-07..2026-11-05, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-07 19:58:15 +05:30' --until='2026-11-05 19:58:15 +05:30' --full-history --no-merges -- packages/at_client_flutter/example/invitations/lib/screens/received.dart`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
FileTooLong: collections/collections.dart packages/at_client/lib/src/collections/collections.dart— FileTooLong — 2149 significant lines (blank, comment-only and punctuation-only lines excluded), about 62% of them inside a single declaration: EventSource (53-3450). The bar is 500 significant lines; this is 1649 over it, 4.30× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: client/at_client_impl.dart packages/at_client/lib/src/client/at_client_impl.dart— FileTooLong — 1382 significant lines (blank, comment-only and punctuation-only lines excluded), about 95% of them inside a single declaration: AtClientImpl (70-2426). The bar is 500 significant lines; this is 882 over it, 2.76× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: commands/auth_cli.dart packages/at_client_cli/lib/src/commands/auth_cli.dart— FileTooLong — 1071 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 571 over it, 2.14× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: nskey/published_nskey_key_ring.dart packages/at_client/lib/src/crypto/nskey/published_nskey_key_ring.dart— FileTooLong — 1041 significant lines (blank, comment-only and punctuation-only lines excluded), about 85% of them inside a single declaration: PublishedNskeyKeyRing (252-1752). The bar is 500 significant lines; this is 541 over it, 2.08× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: service/sync_service_impl.dart packages/at_client/lib/src/service/sync_service_impl.dart— FileTooLong — 980 significant lines (blank, comment-only and punctuation-only lines excluded), about 97% of them inside a single declaration: SyncServiceImpl (28-1730). The bar is 500 significant lines; this is 480 over it, 1.96× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: service/notification_service_impl.dart packages/at_client/lib/src/service/notification_service_impl.dart— FileTooLong — 813 significant lines (blank, comment-only and punctuation-only lines excluded), about 91% of them inside a single declaration: NotificationServiceImpl (45-1290). The bar is 500 significant lines; this is 313 over it, 1.63× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: secret_sharing/pairwise_secret_sharing.dart packages/at_client/lib/src/secret_sharing/pairwise_secret_sharing.dart— FileTooLong — 749 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 249 over it, 1.50× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: layer/tile_layer.dart packages/at_location_flutter/lib/map_content/flutter_map/src/layer/tile_layer.dart— FileTooLong — 735 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 235 over it, 1.47× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: keys/at_keys.dart packages/at_auth/lib/src/keys/at_keys.dart— FileTooLong — 733 significant lines (blank, comment-only and punctuation-only lines excluded), about 92% of them inside a single declaration: AtKeys (78-1466). The bar is 500 significant lines; this is 233 over it, 1.47× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: src/at_lookup_impl.dart packages/at_lookup/lib/src/at_lookup_impl.dart— FileTooLong — 661 significant lines (blank, comment-only and punctuation-only lines excluded), about 88% of them inside a single declaration: AtLookupImpl (72-1114). The bar is 500 significant lines; this is 161 over it, 1.32× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: nskey/pq_signing_root.dart packages/at_client/lib/src/crypto/nskey/pq_signing_root.dart— FileTooLong — 645 significant lines (blank, comment-only and punctuation-only lines excluded), about 91% of them inside a single declaration: PqSigningRoot (70-1062). The bar is 500 significant lines; this is 145 over it, 1.29× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: nskey/ck_manager.dart packages/at_client/lib/src/crypto/nskey/ck_manager.dart— FileTooLong — 635 significant lines (blank, comment-only and punctuation-only lines excluded), about 93% of them inside a single declaration: CkManager (70-1051). The bar is 500 significant lines; this is 135 over it, 1.27× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: client/local_secondary.dart packages/at_client/lib/src/client/local_secondary.dart— FileTooLong — 579 significant lines (blank, comment-only and punctuation-only lines excluded), about 95% of them inside a single declaration: LocalSecondary (27-1175). The bar is 500 significant lines; this is 79 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.
FileTooLong: nskey/pq_signing_chain.dart packages/at_client/lib/src/crypto/nskey/pq_signing_chain.dart— FileTooLong — 575 significant lines (blank, comment-only and punctuation-only lines excluded), about 78% of them inside a single declaration: PqSigningChain (214-890). The bar is 500 significant lines; this is 75 over it, 1.15× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: keystore/at_key.dart packages/at_commons/lib/src/keystore/at_key.dart— FileTooLong — 550 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 50 over it, 1.10× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: services/event_key_stream_service.dart packages/at_events_flutter/lib/services/event_key_stream_service.dart— FileTooLong — 527 significant lines (blank, comment-only and punctuation-only lines excluded), about 97% of them inside a single declaration: EventKeyStreamService (21-826). The bar is 500 significant lines; this is 27 over it, 1.05× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: commands/auth_cli_args.dart packages/at_client_cli/lib/src/commands/auth_cli_args.dart— FileTooLong — 524 significant lines (blank, comment-only and punctuation-only lines excluded), about 86% of them inside a single declaration: AuthCliArgs (86-709). The bar is 500 significant lines; this is 24 over it, 1.05× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: src/marker_cluster_layer.dart packages/at_location_flutter/lib/map_content/flutter_map_marker_cluster/src/marker_cluster_layer.dart— FileTooLong — 505 significant lines (blank, comment-only and punctuation-only lines excluded), about 95% of them inside a single declaration: _MarkerClusterLayerState (32-777). The bar is 500 significant lines; this is 5 over it, 1.01× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: rpc/at_rpc.dart packages/at_client/lib/src/rpc/at_rpc.dart— FileTooLong — 501 significant lines (blank, comment-only and punctuation-only lines excluded), about 78% of them inside a single declaration: AtRpc (162-805). The bar is 500 significant lines; this is 1 over it, 1.00× 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.
TooManyMethods: AtClientImpl packages/at_client/lib/src/client/at_client_impl.dart:69— TooManyMethods — 101 methods. The bar is 30 methods; this is 71 over it, 3.37× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: AtCollection packages/at_client/lib/src/collections/collections.dart:339— TooManyMethods — 97 methods. The bar is 30 methods; this is 67 over it, 3.23× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: AtLookupImpl packages/at_lookup/lib/src/at_lookup_impl.dart:72— TooManyMethods — 65 methods. The bar is 30 methods; this is 35 over it, 2.17× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: PublishedNskeyKeyRing packages/at_client/lib/src/crypto/nskey/published_nskey_key_ring.dart:246— TooManyMethods — 62 methods. The bar is 30 methods; this is 32 over it, 2.07× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: AtKeys packages/at_auth/lib/src/keys/at_keys.dart:53— TooManyMethods — 59 methods. The bar is 30 methods; this is 29 over it, 1.97× 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: SyncServiceImpl packages/at_client/lib/src/service/sync_service_impl.dart:27— TooManyMethods — 59 methods. The bar is 30 methods; this is 29 over it, 1.97× 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: LocalSecondary packages/at_client/lib/src/client/local_secondary.dart:25— TooManyMethods — 53 methods. The bar is 30 methods; this is 23 over it, 1.77× 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: KeyStreamMixin packages/at_client/lib/src/key_stream/key_stream_mixin.dart:16— TooManyMethods — 47 methods. The bar is 30 methods; this is 17 over it, 1.57× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: MemoryAtKeyValueStore packages/at_client/lib/src/storage/memory/memory_at_key_value_store.dart:8— TooManyMethods — 47 methods. The bar is 30 methods; this is 17 over it, 1.57× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: NotificationServiceImpl packages/at_client/lib/src/service/notification_service_impl.dart:45— 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: PseudoServerSocket packages/at_utils/lib/src/networking/pseudo_server_socket.dart:6— TooManyMethods — 42 methods. The bar is 30 methods; this is 12 over it, 1.40× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: PqSigningRoot packages/at_client/lib/src/crypto/nskey/pq_signing_root.dart:63— TooManyMethods — 37 methods. The bar is 30 methods; this is 7 over it, 1.23× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: GroupService packages/at_contacts_group_flutter/lib/services/group_service.dart:19— TooManyMethods — 36 methods. The bar is 30 methods; this is 6 over it, 1.20× 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: _TileLayerState packages/at_location_flutter/lib/map_content/flutter_map/src/layer/tile_layer.dart:388— TooManyMethods — 36 methods. The bar is 30 methods; this is 6 over it, 1.20× 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: CkManager packages/at_client/lib/src/crypto/nskey/ck_manager.dart:65— 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.
TooManyMethods: AuthCliArgs packages/at_client_cli/lib/src/commands/auth_cli_args.dart:84— TooManyMethods — 33 methods. The bar is 30 methods; this is 3 over it, 1.10× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: _MarkerClusterLayerState packages/at_location_flutter/lib/map_content/flutter_map_marker_cluster/src/marker_cluster_layer.dart:32— TooManyMethods — 33 methods. The bar is 30 methods; this is 3 over it, 1.10× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: PqSigningChain packages/at_client/lib/src/crypto/nskey/pq_signing_chain.dart:205— TooManyMethods — 31 methods. The bar is 30 methods; this is 1 over it, 1.03× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: MapState packages/at_location_flutter/lib/map_content/flutter_map/src/map/map.dart:67— TooManyMethods — 31 methods. The bar is 30 methods; this is 1 over it, 1.03× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: EventSource packages/at_client/lib/src/collections/collections.dart:32— ClassTooLong — 1342 significant lines (blank, comment-only and punctuation-only lines excluded), 0 methods. The bar is 400 significant lines; this is 942 over it, 3.36× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: AtClientImpl packages/at_client/lib/src/client/at_client_impl.dart:69— ClassTooLong — 1319 significant lines (blank, comment-only and punctuation-only lines excluded), 101 methods. The bar is 400 significant lines; this is 919 over it, 3.30× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: SyncServiceImpl packages/at_client/lib/src/service/sync_service_impl.dart:27— ClassTooLong — 946 significant lines (blank, comment-only and punctuation-only lines excluded), 59 methods. The bar is 400 significant lines; this is 546 over it, 2.37× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: PublishedNskeyKeyRing packages/at_client/lib/src/crypto/nskey/published_nskey_key_ring.dart:246— ClassTooLong — 881 significant lines (blank, comment-only and punctuation-only lines excluded), 62 methods. The bar is 400 significant lines; this is 481 over it, 2.20× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: NotificationServiceImpl packages/at_client/lib/src/service/notification_service_impl.dart:45— ClassTooLong — 741 significant lines (blank, comment-only and punctuation-only lines excluded), 45 methods. The bar is 400 significant lines; this is 341 over it, 1.85× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: AtKeys packages/at_auth/lib/src/keys/at_keys.dart:53— ClassTooLong — 674 significant lines (blank, comment-only and punctuation-only lines excluded), 59 methods. The bar is 400 significant lines; this is 274 over it, 1.69× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: CkManager packages/at_client/lib/src/crypto/nskey/ck_manager.dart:65— ClassTooLong — 591 significant lines (blank, comment-only and punctuation-only lines excluded), 34 methods. The bar is 400 significant lines; this is 191 over it, 1.48× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: PqSigningRoot packages/at_client/lib/src/crypto/nskey/pq_signing_root.dart:63— ClassTooLong — 586 significant lines (blank, comment-only and punctuation-only lines excluded), 37 methods. The bar is 400 significant lines; this is 186 over it, 1.47× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: AtLookupImpl packages/at_lookup/lib/src/at_lookup_impl.dart:72— ClassTooLong — 579 significant lines (blank, comment-only and punctuation-only lines excluded), 65 methods. The bar is 400 significant lines; this is 179 over it, 1.45× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: LocalSecondary packages/at_client/lib/src/client/local_secondary.dart:25— ClassTooLong — 552 significant lines (blank, comment-only and punctuation-only lines excluded), 53 methods. The bar is 400 significant lines; this is 152 over it, 1.38× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: EventKeyStreamService packages/at_events_flutter/lib/services/event_key_stream_service.dart:21— ClassTooLong — 512 significant lines (blank, comment-only and punctuation-only lines excluded), 30 methods. The bar is 400 significant lines; this is 112 over it, 1.28× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: _MarkerClusterLayerState packages/at_location_flutter/lib/map_content/flutter_map_marker_cluster/src/marker_cluster_layer.dart:32— ClassTooLong — 482 significant lines (blank, comment-only and punctuation-only lines excluded), 33 methods. The bar is 400 significant lines; this is 82 over it, 1.21× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: AuthCliArgs packages/at_client_cli/lib/src/commands/auth_cli_args.dart:84— ClassTooLong — 449 significant lines (blank, comment-only and punctuation-only lines excluded), 33 methods. The bar is 400 significant lines; this is 49 over it, 1.12× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: PqSigningChain packages/at_client/lib/src/crypto/nskey/pq_signing_chain.dart:205— ClassTooLong — 449 significant lines (blank, comment-only and punctuation-only lines excluded), 31 methods. The bar is 400 significant lines; this is 49 over it, 1.12× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: ContactService packages/at_contacts_flutter/lib/services/contact_service.dart:14— ClassTooLong — 445 significant lines (blank, comment-only and punctuation-only lines excluded), 30 methods. The bar is 400 significant lines; this is 45 over it, 1.11× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: AtContactsImpl packages/at_contact/lib/src/at_contacts_impl.dart:13— ClassTooLong — 420 significant lines (blank, comment-only and punctuation-only lines excluded), 30 methods. The bar is 400 significant lines; this is 20 over it, 1.05× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: _TileLayerState packages/at_location_flutter/lib/map_content/flutter_map/src/layer/tile_layer.dart:388— ClassTooLong — 419 significant lines (blank, comment-only and punctuation-only lines excluded), 36 methods. The bar is 400 significant lines; this is 19 over it, 1.05× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
Repeated repair: packages/at_client/lib/src/crypto/nskey/nskey_private_filing.dart packages/at_client/lib/src/crypto/nskey/nskey_private_filing.dart:419— packages/at_client/lib/src/crypto/nskey/nskey_private_filing.dart changed 42 times in last 90 days and 25 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 8 (its worst body is NskeyPrivateFiling.filedFor at line 419), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(at_client): a key filed after verifying counts at an offline restart”; “fix(at_client): a failed keyfile read refuses writes for 10 seconds”; “fix(at_client): a write waits for a held-namespace read in flight”; “fix(at_client): the held-namespace list is re-read at most once a minute”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-07..2026-11-05, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-07 19:58:15 +05:30' --until='2026-11-05 19:58:15 +05:30' --full-history --no-merges -- packages/at_client/lib/src/crypto/nskey/nskey_private_filing.dart`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: packages/at_auth/lib/src/keys/io/file_io.dart packages/at_auth/lib/src/keys/io/file_io.dart:168— packages/at_auth/lib/src/keys/io/file_io.dart changed 26 times in last 90 days and 17 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 6 (its worst body is FileAtKeysIo._readForWrite at line 168), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(at_auth): a keyfile's .bak never keeps a removed pending enrollment”; “fix(at_auth): root reads and writes a keyfile by its path”; “fix(at_auth): root reads and writes a keyfile within one opened directory”; “fix(at_auth): rewrite a typed keyfile with no typed key material flat”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-07..2026-11-05, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-07 19:58:15 +05:30' --until='2026-11-05 19:58:15 +05:30' --full-history --no-merges -- packages/at_auth/lib/src/keys/io/file_io.dart`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: packages/at_client/lib/src/service/envelope_enrollment_conveyance.dart packages/at_client/lib/src/service/envelope_enrollment_conveyance.dart:247— packages/at_client/lib/src/service/envelope_enrollment_conveyance.dart changed 26 times in last 90 days and 14 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 13 (its worst body is EnvelopeEnrollmentConveyance.sweepUnanchoredEnrollments at line 247), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(at_client): one enroll:link refusal per client, not one per step”; “fix(at_client): the link sweep stops on an atServer without enroll:link”; “fix(at_client): file a conveyed link and stamp it as it arrives”; “fix(at_client): check arriving nskey privates against the published key”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-07..2026-11-05, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-07 19:58:15 +05:30' --until='2026-11-05 19:58:15 +05:30' --full-history --no-merges -- packages/at_client/lib/src/service/envelope_enrollment_conveyance.dart`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: packages/at_client/lib/src/rpc/at_rpc.dart packages/at_client/lib/src/rpc/at_rpc.dart:469— packages/at_client/lib/src/rpc/at_rpc.dart changed 18 times in last 90 days and 11 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 12 (its worst body is AtRpc.handleRequestNotification at line 469), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(at_client): RPC payloads are logged at finest only”; “fix(at_client): AtRpcClient logs to stderr where there is one”; “fix(at_client): AtRpc answers a request it cannot parse with a NACK”; “fix(at_client): tighten the server mutex and MintLock lockTtl checks”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-07..2026-11-05, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-07 19:58:15 +05:30' --until='2026-11-05 19:58:15 +05:30' --full-history --no-merges -- packages/at_client/lib/src/rpc/at_rpc.dart`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: packages/at_client_flutter/lib/src/keychain/keychain_storage.dart packages/at_client_flutter/lib/src/keychain/keychain_storage.dart:487— packages/at_client_flutter/lib/src/keychain/keychain_storage.dart changed 18 times in last 90 days and 10 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 9 (its worst body is KeychainStorage._delete at line 487), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(at_client_flutter): migrate the legacy keychain entry under the lock”; “fix(at_client_flutter): take the keychain's write lock to remove keys”; “fix: deletion edge case”; “fix: `:` is now authoritative when present; `_` is not inspected”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-07..2026-11-05, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-07 19:58:15 +05:30' --until='2026-11-05 19:58:15 +05:30' --full-history --no-merges -- packages/at_client_flutter/lib/src/keychain/keychain_storage.dart`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: packages/at_auth/lib/src/keys/io/owner_only_mode_ffi.dart packages/at_auth/lib/src/keys/io/owner_only_mode_ffi.dart:277— packages/at_auth/lib/src/keys/io/owner_only_mode_ffi.dart changed 14 times in last 90 days and 8 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 6 (its worst body is _Libc._lookUp at line 277), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(at_auth): report a failed keyfile call in a locale that is not UTF-8”; “fix(at_auth): keep owner-only writes on when errno cannot be looked up”; “fix: defects on trunk found reviewing #2397”; “fix(at_auth): root reads and writes a keyfile by its path”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-07..2026-11-05, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-07 19:58:15 +05:30' --until='2026-11-05 19:58:15 +05:30' --full-history --no-merges -- packages/at_auth/lib/src/keys/io/owner_only_mode_ffi.dart`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: packages/at_client/lib/src/crypto/nskey/start_up_seeding.dart packages/at_client/lib/src/crypto/nskey/start_up_seeding.dart:115— packages/at_client/lib/src/crypto/nskey/start_up_seeding.dart changed 10 times in last 90 days and 7 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 6 (its worst body is StartUpSeeding.coveringBeyond at line 115), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(at_client): a write before start-up asks for its private waits too”; “fix(at_client): a write learns why start-up could not read its grants”; “fix(at_client): a sender's copy is sealed at its own level, never minted”; “fix(at_client): a failed grant read gives waiting writes its reason”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-07..2026-11-05, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-07 19:58:15 +05:30' --until='2026-11-05 19:58:15 +05:30' --full-history --no-merges -- packages/at_client/lib/src/crypto/nskey/start_up_seeding.dart`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: packages/at_client_flutter/lib/src/widgets/authorisation/containers/enrollment_request_list.dart packages/at_client_flutter/lib/src/widgets/authorisation/containers/enrollment_request_list.dart:288— packages/at_client_flutter/lib/src/widgets/authorisation/containers/enrollment_request_list.dart changed 11 times in last 90 days and 6 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 12 (its worst body is _EnrollmentRequestListState.build at line 288), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(at_client_flutter): the approved list reads every walk at once”; “fix(at_client_flutter): an approval's reload cannot fail the approval”; “fix(at_client_flutter): the approved section reports its own failures”; “fix(at_client): the rest of the adversarial review's findings”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-07..2026-11-05, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-07 19:58:15 +05:30' --until='2026-11-05 19:58:15 +05:30' --full-history --no-merges -- packages/at_client_flutter/lib/src/widgets/authorisation/containers/enrollment_request_list.dart`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: packages/at_client_flutter/lib/src/keychain/keychain_io_impl.dart packages/at_client_flutter/lib/src/keychain/keychain_io_impl.dart:99— packages/at_client_flutter/lib/src/keychain/keychain_io_impl.dart changed 7 times in last 90 days and 6 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 3 (its worst body is KeychainAtKeysIo._stampAtSign at line 99), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix: keep a link's envelope until it is stamped, not a keyfile copy”; “fix(at_client_flutter): take the keychain's write lock to remove keys”; “fix: serialise keychain writes, and require at_auth 4.0.0-rc5”; “fix(at_client_flutter): the keychain reports an absent atSign as absent”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-07..2026-11-05, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-07 19:58:15 +05:30' --until='2026-11-05 19:58:15 +05:30' --full-history --no-merges -- packages/at_client_flutter/lib/src/keychain/keychain_io_impl.dart`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: packages/at_client/lib/src/transformer/response_transformer/get_response_transformer.dart packages/at_client/lib/src/transformer/response_transformer/get_response_transformer.dart:28— packages/at_client/lib/src/transformer/response_transformer/get_response_transformer.dart changed 6 times in last 90 days and 5 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 13 (its worst body is GetResponseTransformer.transform at line 28), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(at_client): warn when a legacy guess finds no private key”; “fix(at_client): warn when a legacy ciphertext guess finds no key”; “fix(at_client): get decrypts legacy ciphertext flagged unencrypted”; “fix: a local value stored as given is never flagged encrypted”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-07..2026-11-05, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-07 19:58:15 +05:30' --until='2026-11-05 19:58:15 +05:30' --full-history --no-merges -- packages/at_client/lib/src/transformer/response_transformer/get_response_transformer.dart`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: packages/at_client/lib/src/transformer/response_transformer/notification_response_transformer.dart packages/at_client/lib/src/transformer/response_transformer/notification_response_transformer.dart:23— packages/at_client/lib/src/transformer/response_transformer/notification_response_transformer.dart changed 7 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 13 (its worst body is NotificationResponseTransformer.transform at line 23), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(at_client): a notification copy carries its own public key hash”; “fix(at_client): copies own their metadata; park bound counts notifications”; “fix(at_client): decrypt a notification once for all its subscribers”; “fix(pq): close the data-path defects an adversarial review found”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-07..2026-11-05, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-07 19:58:15 +05:30' --until='2026-11-05 19:58:15 +05:30' --full-history --no-merges -- packages/at_client/lib/src/transformer/response_transformer/notification_response_transformer.dart`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: packages/at_client_cli/lib/src/register/onboarding_util.dart packages/at_client_cli/lib/src/register/onboarding_util.dart:116— packages/at_client_cli/lib/src/register/onboarding_util.dart changed 6 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 12 (its worst body is OnboardingUtil.validateOtp at line 116), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(at_client_cli): the registrar tools fall back to a built-in key”; “fix(at_client_cli): check the registrar key before at_activate's prompt”; “fix(at_client_cli): a registrar API key a header cannot carry is refused”; “fix(at_client_cli): log a registrar request without its body”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-07..2026-11-05, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-07 19:58:15 +05:30' --until='2026-11-05 19:58:15 +05:30' --full-history --no-merges -- packages/at_client_cli/lib/src/register/onboarding_util.dart`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: packages/at_client/lib/src/crypto/nskey/pre_publish_conveyance.dart packages/at_client/lib/src/crypto/nskey/pre_publish_conveyance.dart:193— packages/at_client/lib/src/crypto/nskey/pre_publish_conveyance.dart changed 5 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 9 (its worst body is PrePublishConveyance.markIfRevoked at line 193), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(at_client): a rotation that fails after a mint's publish is logged”; “fix(at_client): a conveyance reports the fewest key packages reached”; “fix(at_client): a revocation before an nskey publish is rotated out”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-07..2026-11-05, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-07 19:58:15 +05:30' --until='2026-11-05 19:58:15 +05:30' --full-history --no-merges -- packages/at_client/lib/src/crypto/nskey/pre_publish_conveyance.dart`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: packages/at_chops/lib/src/algorithm/signing/rsa.dart packages/at_chops/lib/src/algorithm/signing/rsa.dart:109— packages/at_chops/lib/src/algorithm/signing/rsa.dart changed 5 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 6 (its worst body is RsaSignatureAlgo.verifyBytes at line 109), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(at_chops): loosen verifyBytes, bump pubspec, retain algotype in rsasigning to help with sizing and wire name”; “fix(at_chops): more verbose exceptions and tamper/interop tests”; “fix(at_chops): review fixes for RsaSignatureAlgo”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-07..2026-11-05, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-07 19:58:15 +05:30' --until='2026-11-05 19:58:15 +05:30' --full-history --no-merges -- packages/at_chops/lib/src/algorithm/signing/rsa.dart`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: packages/at_client/lib/src/mixins/invitations.dart packages/at_client/lib/src/mixins/invitations.dart:547— packages/at_client/lib/src/mixins/invitations.dart changed 4 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 10 (its worst body is Invitations._connect at line 547), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(at_client): invitation edge cases from review”; “fix(at_client): prefix the invitation typeTags and pin the wire format”; “fix(at_client): invitations survive bad records and failed decisions”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-07..2026-11-05, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-07 19:58:15 +05:30' --until='2026-11-05 19:58:15 +05:30' --full-history --no-merges -- packages/at_client/lib/src/mixins/invitations.dart`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: packages/at_client/lib/src/crypto/nskey/verified_advertisement_record.dart packages/at_client/lib/src/crypto/nskey/verified_advertisement_record.dart:73— packages/at_client/lib/src/crypto/nskey/verified_advertisement_record.dart changed 3 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 8 (its worst body is VerifiedAdvertisementRecord.vouchesFor at line 73), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(at_client): a key filed after verifying counts at an offline restart”; “fix(at_client): the primary enrollment keeps its verified-key record”; “fix(at_client): an unreadable verified record is replaced online”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-07..2026-11-05, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-07 19:58:15 +05:30' --until='2026-11-05 19:58:15 +05:30' --full-history --no-merges -- packages/at_client/lib/src/crypto/nskey/verified_advertisement_record.dart`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Duplicated block (12 lines × 2) packages/at_chat_flutter/lib/widgets/bottom_sheet_dialog.dart:33— packages/at_chat_flutter/lib/widgets/bottom_sheet_dialog.dart:33-44 | packages/at_chat_flutter/lib/widgets/bottom_sheet_dialog.dart:77-88 — 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) packages/at_chops/lib/src/algorithm/encryption/aes_gcm_ffi_algo.dart:91— packages/at_chops/lib/src/algorithm/encryption/aes_gcm_ffi_algo.dart:91-102 | packages/at_chops/lib/src/algorithm/encryption/aes_gcm_ffi_algo.dart:215-226 — 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) packages/at_chops/lib/src/algorithm/encryption/ml_kem_768_ffi.dart:61— packages/at_chops/lib/src/algorithm/encryption/ml_kem_768_ffi.dart:61-72 | packages/at_chops/lib/src/algorithm/encryption/x25519_ffi_algo.dart:31-42 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (12 lines × 2) packages/at_contacts_group_flutter/lib/screens/group_view/group_view.dart:201— packages/at_contacts_group_flutter/lib/screens/group_view/group_view.dart:201-212 | packages/at_location_flutter/lib/common_components/collapsed_content.dart:98-109 — 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 × 2) packages/at_contacts_group_flutter/lib/widgets/circular_group_contact.dart:17— packages/at_contacts_group_flutter/lib/widgets/circular_group_contact.dart:17-28 | packages/at_contacts_group_flutter/lib/widgets/person_horizontal_tile.dart:17-28 — before extracting anything, compare `packages/at_contacts_group_flutter/lib/widgets/circular_group_contact.dart` and `packages/at_contacts_group_flutter/lib/widgets/person_horizontal_tile.dart` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 54 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 × 2) packages/at_events_flutter/lib/common_components/concurrent_event_request_dialog.dart:40— packages/at_events_flutter/lib/common_components/concurrent_event_request_dialog.dart:40-51 | packages/at_events_flutter/lib/screens/notification_dialog/event_notification_dialog.dart:108-119 — 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 × 2) packages/at_events_flutter/lib/common_components/invite_card.dart:70— packages/at_events_flutter/lib/common_components/invite_card.dart:70-81 | packages/at_events_flutter/lib/screens/notification_dialog/event_notification_dialog.dart:144-156 — 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 × 2) packages/at_events_flutter/lib/screens/notification_dialog/event_notification_dialog.dart:359— packages/at_events_flutter/lib/screens/notification_dialog/event_notification_dialog.dart:359-370 | packages/at_location_flutter/lib/screens/notification_dialog/notification_dialog.dart:194-205 — 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 × 2) packages/at_location_flutter/lib/map_content/flutter_map/src/layer/marker_layer.dart:134— packages/at_location_flutter/lib/map_content/flutter_map/src/layer/marker_layer.dart:134-145 | packages/at_location_flutter/lib/map_content/flutter_map_marker_popup/src/popup_marker_layer.dart:40-51 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (12 lines × 2) packages/at_location_flutter/lib/screens/request_location/request_location_sheet.dart:33— packages/at_location_flutter/lib/screens/request_location/request_location_sheet.dart:33-44 | packages/at_location_flutter/lib/screens/share_location/share_location_sheet.dart:33-44 — `packages/at_location_flutter/lib/screens/request_location/request_location_sheet.dart` and `packages/at_location_flutter/lib/screens/share_location/share_location_sheet.dart` 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 4 separate duplicated blocks between them, totalling at least 48 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.
Duplicated block (12 lines × 2) packages/at_location_flutter/lib/screens/request_location/request_location_sheet.dart:87— packages/at_location_flutter/lib/screens/request_location/request_location_sheet.dart:87-98 | packages/at_location_flutter/lib/screens/share_location/share_location_sheet.dart:123-134 — `packages/at_location_flutter/lib/screens/request_location/request_location_sheet.dart` and `packages/at_location_flutter/lib/screens/share_location/share_location_sheet.dart` 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 4 separate duplicated blocks between them, totalling at least 48 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.
Duplicated block (12 lines × 2) packages/at_location_flutter/lib/screens/request_location/request_location_sheet.dart:114— packages/at_location_flutter/lib/screens/request_location/request_location_sheet.dart:114-125 | packages/at_location_flutter/lib/screens/share_location/share_location_sheet.dart:161-172 — `packages/at_location_flutter/lib/screens/request_location/request_location_sheet.dart` and `packages/at_location_flutter/lib/screens/share_location/share_location_sheet.dart` 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 4 separate duplicated blocks between them, totalling at least 48 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.
Duplicated block (12 lines × 2) packages/at_location_flutter/lib/screens/request_location/request_location_sheet.dart:127— packages/at_location_flutter/lib/screens/request_location/request_location_sheet.dart:127-138 | packages/at_location_flutter/lib/screens/share_location/share_location_sheet.dart:174-185 — `packages/at_location_flutter/lib/screens/request_location/request_location_sheet.dart` and `packages/at_location_flutter/lib/screens/share_location/share_location_sheet.dart` 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 4 separate duplicated blocks between them, totalling at least 48 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.
Duplicated block (12 lines × 2) packages/at_contacts_group_flutter/lib/widgets/triple_dot_loading.dart:69— packages/at_contacts_group_flutter/lib/widgets/triple_dot_loading.dart:69-80 | packages/at_events_flutter/lib/common_components/triple_dot_loading.dart:69-80 — before extracting anything, compare `packages/at_contacts_group_flutter/lib/widgets/triple_dot_loading.dart` and `packages/at_events_flutter/lib/common_components/triple_dot_loading.dart` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 51 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 (12 lines × 2) packages/at_follows_flutter/example/lib/services/notification_service.dart:34— packages/at_follows_flutter/example/lib/services/notification_service.dart:34-45 | packages/at_login_flutter/lib/services/notification_service.dart:35-46 — before extracting anything, compare `packages/at_follows_flutter/example/lib/services/notification_service.dart` and `packages/at_login_flutter/lib/services/notification_service.dart` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 34 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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 (12 lines × 2) packages/at_follows_flutter/lib/utils/strings.dart:56— packages/at_follows_flutter/lib/utils/strings.dart:56-67 | packages/at_login_flutter/lib/utils/strings.dart:45-56 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Low cohesion: MemoryAtKeyValueStore (LCOM4 20) packages/at_client/lib/src/storage/memory/memory_at_key_value_store.dart:8— MemoryAtKeyValueStore's methods fall into 20 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 20 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: CustomPopupRoutes (LCOM4 6) packages/at_events_flutter/lib/common_components/custom_popup_route.dart:3— CustomPopupRoutes's methods fall into 6 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 6 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: CustomPopupRoutes (LCOM4 6) packages/at_location_flutter/lib/common_components/custom_popup_route.dart:3— CustomPopupRoutes's methods fall into 6 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 6 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: AtLoginService (LCOM4 6) packages/at_login_flutter/lib/services/at_login_service.dart:15— AtLoginService's methods fall into 6 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 6 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: CustomPopupRoutes (LCOM4 6) packages/at_contacts_group_flutter/lib/widgets/custom_popup_route.dart:3— CustomPopupRoutes's methods fall into 6 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 6 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: MlDsa65PureDartAlgo (LCOM4 5) packages/at_chops/lib/src/algorithm/signing/ml_dsa_65_pure_dart.dart:11— MlDsa65PureDartAlgo's methods fall into 5 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 5 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: AtCollection (LCOM4 5) packages/at_client/lib/src/collections/collections.dart:339— AtCollection's methods fall into 5 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 5 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: _SecondScreenState (LCOM4 4) packages/at_sync_ui_flutter/example/lib/second_screen.dart:18— _SecondScreenState's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: _MyHomePageState (LCOM4 4) packages/at_sync_ui_flutter/example/lib/ui_options.dart:47— _MyHomePageState's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: AtEnrollmentImpl (LCOM4 4) packages/at_auth/lib/src/enroll/at_enrollment_impl.dart:15— AtEnrollmentImpl's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: AtChopsImpl (LCOM4 4) packages/at_chops/lib/src/at_chops_impl.dart:32— AtChopsImpl's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: PqStartupGates (LCOM4 4) packages/at_client/lib/src/client/pq_client_bootstrap.dart:36— PqStartupGates's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: PublishedNskeyKeyRing (LCOM4 4) packages/at_client/lib/src/crypto/nskey/published_nskey_key_ring.dart:246— PublishedNskeyKeyRing's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: HiveAtClientStorage (LCOM4 4) packages/at_client/lib/src/storage/hive/hive_at_client_storage.dart:15— HiveAtClientStorage's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Duplicated block (9 lines × 2) packages/at_contacts_group_flutter/lib/screens/group_contact_view/group_contact_view.dart:397— packages/at_contacts_group_flutter/lib/screens/group_contact_view/group_contact_view.dart:397-405 | packages/at_contacts_group_flutter/lib/screens/group_contact_view/group_contact_view.dart:415-424 — 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) packages/at_contacts_group_flutter/lib/widgets/person_vertical_tile.dart:49— packages/at_contacts_group_flutter/lib/widgets/person_vertical_tile.dart:49-57 | packages/at_location_flutter/lib/screens/notification_dialog/notification_dialog.dart:60-68 — 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) packages/at_events_flutter/lib/common_components/overlapping_contacts.dart:61— packages/at_events_flutter/lib/common_components/overlapping_contacts.dart:61-69 | packages/at_events_flutter/lib/common_components/overlapping_contacts.dart:180-190 — 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) packages/at_follows_flutter/lib/utils/color_constants.dart:42— packages/at_follows_flutter/lib/utils/color_constants.dart:42-50 | packages/at_login_flutter/lib/utils/color_constants.dart:41-49 — 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) packages/at_theme_flutter/lib/src/widgets/color_card.dart:29— packages/at_theme_flutter/lib/src/widgets/color_card.dart:29-37 | packages/at_theme_flutter/lib/src/widgets/theme_mode_card.dart:75-84 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (9 lines × 2) packages/at_chops/lib/src/algorithm/signing/ml_dsa_65_ffi.dart:273— packages/at_chops/lib/src/algorithm/signing/ml_dsa_65_ffi.dart:273-281 | packages/at_chops/lib/src/algorithm/signing/ml_dsa_65_pure_dart.dart:132-140 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (9 lines × 2) packages/at_follows_flutter/lib/services/notification_service.dart:21— packages/at_follows_flutter/lib/services/notification_service.dart:21-29 | packages/at_login_flutter/lib/services/notification_service.dart:18-26 — before extracting anything, compare `packages/at_follows_flutter/lib/services/notification_service.dart` and `packages/at_login_flutter/lib/services/notification_service.dart` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 47 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 (9 lines × 2) packages/at_chops/example/zariot/at_chops_secure_element.dart:29— packages/at_chops/example/zariot/at_chops_secure_element.dart:29-38 | packages/at_chops/lib/src/at_chops_impl.dart:325-333 — 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) packages/at_chops/example/zariot/external_signer.dart:109— packages/at_chops/example/zariot/external_signer.dart:109-117 | packages/at_chops/example/zariot/external_signer.dart:209-217 — 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) packages/at_client_flutter/example/dockerstats/lib/main.dart:31— packages/at_client_flutter/example/dockerstats/lib/main.dart:31-39 | packages/at_client_flutter/example/todos/lib/main.dart:29-37 — 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) packages/at_chops/lib/src/algorithm/encryption/aes_gcm_ffi_algo.dart:106— packages/at_chops/lib/src/algorithm/encryption/aes_gcm_ffi_algo.dart:106-119 | packages/at_chops/lib/src/algorithm/encryption/aes_gcm_ffi_algo.dart:230-243 — 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) packages/at_chops/lib/src/algorithm/pkam_signing_algo.dart:44— packages/at_chops/lib/src/algorithm/pkam_signing_algo.dart:44-58 | packages/at_chops/lib/src/algorithm/signing/rsa.dart:219-232 — 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) packages/at_contacts_flutter/lib/widgets/add_contacts_dialog.dart:43— packages/at_contacts_flutter/lib/widgets/add_contacts_dialog.dart:43-56 | packages/at_contacts_group_flutter/lib/widgets/add_contacts_group_dialog.dart:30-43 — before extracting anything, compare `packages/at_contacts_flutter/lib/widgets/add_contacts_dialog.dart` and `packages/at_contacts_group_flutter/lib/widgets/add_contacts_group_dialog.dart` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 68 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 (14 lines × 2) packages/at_events_flutter/lib/common_components/display_tile.dart:164— packages/at_events_flutter/lib/common_components/display_tile.dart:164-177 | packages/at_location_flutter/lib/common_components/display_tile.dart:167-180 — before extracting anything, compare `packages/at_events_flutter/lib/common_components/display_tile.dart` and `packages/at_location_flutter/lib/common_components/display_tile.dart` as WHOLE FILES: this scan already matched 3 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. 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 (14 lines × 2) packages/at_events_flutter/lib/common_components/draggable_symbol.dart:8— packages/at_events_flutter/lib/common_components/draggable_symbol.dart:8-21 | packages/at_location_flutter/lib/common_components/draggable_symbol.dart:8-21 — 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) packages/at_events_flutter/lib/screens/map_screen/events_collapsed_content.dart:62— packages/at_events_flutter/lib/screens/map_screen/events_collapsed_content.dart:62-75 | packages/at_location_flutter/lib/common_components/collapsed_content.dart:101-114 — 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) packages/at_sync_ui_flutter/lib/at_sync_cupertino.dart:395— packages/at_sync_ui_flutter/lib/at_sync_cupertino.dart:395-409 | packages/at_sync_ui_flutter/lib/at_sync_material.dart:167-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 (14 lines × 2) packages/at_client_flutter/example/lib/snippets/at_backup_key.dart:191— packages/at_client_flutter/example/lib/snippets/at_backup_key.dart:191-204 | packages/at_client_flutter/example/lib/snippets/at_backup_key.dart:261-274 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (14 lines × 2) packages/at_location_flutter/example/lib/second_screen.dart:231— packages/at_location_flutter/example/lib/second_screen.dart:231-244 | packages/at_sync_ui_flutter/example/lib/second_screen.dart:153-166 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (8 lines × 2) packages/at_client/lib/src/collections/collections.dart:2220— packages/at_client/lib/src/collections/collections.dart:2220-2227 | packages/at_client/lib/src/collections/collections.dart:2258-2265 — 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) packages/at_contacts_group_flutter/lib/widgets/triple_dot_loading.dart:46— packages/at_contacts_group_flutter/lib/widgets/triple_dot_loading.dart:46-53 | packages/at_events_flutter/lib/common_components/triple_dot_loading.dart:46-53 — before extracting anything, compare `packages/at_contacts_group_flutter/lib/widgets/triple_dot_loading.dart` and `packages/at_events_flutter/lib/common_components/triple_dot_loading.dart` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 51 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 (8 lines × 2) packages/at_events_flutter/lib/screens/recurring_event.dart:375— packages/at_events_flutter/lib/screens/recurring_event.dart:375-382 | packages/at_events_flutter/lib/screens/selected_location.dart:166-174 — 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) packages/at_location_flutter/lib/common_components/collapsed_content.dart:67— packages/at_location_flutter/lib/common_components/collapsed_content.dart:67-74 | packages/at_location_flutter/lib/screens/map_screen/map_screen.dart:36-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 (8 lines × 2) packages/at_chops/lib/src/algorithm/encryption/aes_gcm.dart:75— packages/at_chops/lib/src/algorithm/encryption/aes_gcm.dart:75-83 | packages/at_chops/lib/src/algorithm/encryption/aes_gcm_ffi_algo.dart:313-320 — before extracting anything, compare `packages/at_chops/lib/src/algorithm/encryption/aes_gcm.dart` and `packages/at_chops/lib/src/algorithm/encryption/aes_gcm_ffi_algo.dart` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 33 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) packages/at_chops/lib/src/algorithm/encryption/aes_gcm.dart:85— packages/at_chops/lib/src/algorithm/encryption/aes_gcm.dart:85-92 | packages/at_chops/lib/src/algorithm/encryption/aes_gcm_ffi_algo.dart:322-329 — before extracting anything, compare `packages/at_chops/lib/src/algorithm/encryption/aes_gcm.dart` and `packages/at_chops/lib/src/algorithm/encryption/aes_gcm_ffi_algo.dart` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 33 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) packages/at_chops/lib/src/algorithm/encryption/aes_gcm.dart:94— packages/at_chops/lib/src/algorithm/encryption/aes_gcm.dart:94-101 | packages/at_chops/lib/src/algorithm/encryption/aes_gcm_ffi_algo.dart:331-338 — before extracting anything, compare `packages/at_chops/lib/src/algorithm/encryption/aes_gcm.dart` and `packages/at_chops/lib/src/algorithm/encryption/aes_gcm_ffi_algo.dart` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 33 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) packages/at_chops/lib/src/algorithm/encryption/aes_gcm.dart:103— packages/at_chops/lib/src/algorithm/encryption/aes_gcm.dart:103-110 | packages/at_chops/lib/src/algorithm/encryption/aes_gcm_ffi_algo.dart:340-347 — before extracting anything, compare `packages/at_chops/lib/src/algorithm/encryption/aes_gcm.dart` and `packages/at_chops/lib/src/algorithm/encryption/aes_gcm_ffi_algo.dart` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 33 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) packages/at_client/example/lib/domain_objects.dart:14— packages/at_client/example/lib/domain_objects.dart:14-21 | packages/at_client_flutter/example/todos/lib/models/todo.dart:18-25 — 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.
Change coupling: ml_dsa_65_ffi.dart ↔ ml_dsa_65_pure_dart.dart packages/at_chops/lib/src/algorithm/signing/ml_dsa_65_ffi.dart:1— `packages/at_chops/lib/src/algorithm/signing/ml_dsa_65_ffi.dart` and `packages/at_chops/lib/src/algorithm/signing/ml_dsa_65_pure_dart.dart` change together 80% of the time (24 of the 30 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — 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 24 shared commits counted here, the most recent 3 are `36cac994` feat(at_chops): newSeed on AtSeededSignatureAlgorithm; correct FFI se…; `7a2429de` fix(at_chops): address review on seeded ML-DSA-65 keygen; `bd0910b4` feat(at_chops): seeded ML-DSA-65 key generation — run `git show` on any of them.
Change coupling: ml_kem_768_ffi.dart ↔ ml_kem_768_pure_dart.dart packages/at_chops/lib/src/algorithm/encryption/ml_kem_768_ffi.dart:1— `packages/at_chops/lib/src/algorithm/encryption/ml_kem_768_ffi.dart` and `packages/at_chops/lib/src/algorithm/encryption/ml_kem_768_pure_dart.dart` change together 75% of the time (9 of the 12 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — 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 9 shared commits counted here, the most recent 3 are `e0ef3463` feat(at_chops): harden ML-KEM-768/ML-DSA-65 validation and FFI gating; `645cffa4` refactor(at_chops): fold ml_dsa_65_validation into pq_validation; `50487977` refactor(at_chops): consolidate PQ output-length checks into checkOut… — run `git show` on any of them.
Change coupling: at_chops_impl.dart ↔ at_chops_keys.dart packages/at_chops/lib/src/at_chops_impl.dart:1— `packages/at_chops/lib/src/at_chops_impl.dart` and `packages/at_chops/lib/src/key/impl/at_chops_keys.dart` change together 64% of the time (7 of the 11 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `c2669cf6` feat: at_chops 2.0.0 major version changes; `f71a90c7` feat: changes for at_auth package; `5d287c47` fix: unit test failure and analyzer issues — run `git show` on any of them.
Change coupling: default_signing_algo.dart ↔ pkam_signing_algo.dart packages/at_chops/lib/src/algorithm/default_signing_algo.dart:1— `packages/at_chops/lib/src/algorithm/default_signing_algo.dart` and `packages/at_chops/lib/src/algorithm/pkam_signing_algo.dart` change together 57% of the time (8 of the 14 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — 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 8 shared commits counted here, the most recent 3 are `f973ef0b` fix(at_chops): review fixes for RsaSignatureAlgo; `149e2390` fix: at_chops remove unnecessary null check operator; `dc4a36bd` fix: analyzer fixes, remove unused variables — run `git show` on any of them.
Change coupling: pkam_signing_algo.dart ↔ ecc.dart packages/at_chops/lib/src/algorithm/pkam_signing_algo.dart:1— `packages/at_chops/lib/src/algorithm/pkam_signing_algo.dart` and `packages/at_chops/lib/src/algorithm/signing/ecc.dart` change together 55% of the time (6 of the 11 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `e590cd2f` refactor(at_chops): restore abstract sign/verify, implements on signi…; `dc4a36bd` fix: analyzer fixes, remove unused variables (at that commit the file was still `packages/at_chops/lib/src/algorithm/ecc_signing_algo.dart`); `3051f7e3` fix: refactored code, added tests, modified dart docs (at that commit the file was still `packages/at_chops/lib/src/algorithm/ecc_signing_algo.dart`) — run `git show` on any of them.
Change coupling: operation_enum.dart ↔ syntax.dart packages/at_commons/lib/src/verb/operation_enum.dart:1— `packages/at_commons/lib/src/verb/operation_enum.dart` and `packages/at_commons/lib/src/verb/syntax.dart` change together 50% of the time (7 of the 14 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — 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 7 shared commits counted here, the most recent 3 are `3ad31338` feat(at_commons): enroll:link in the enroll grammar and params; `54ccffdd` feat(at_commons): enroll:update, and _apsk as an array of signing keys; `a70a6f72` feat: add delete option to enroll verb (#654) — run `git show` on any of them.
Change coupling: apkam_dialog.dart ↔ pkam_dialog.dart packages/at_client_flutter/lib/src/widgets/apkam_dialog.dart:1— `packages/at_client_flutter/lib/src/widgets/apkam_dialog.dart` and `packages/at_client_flutter/lib/src/widgets/pkam_dialog.dart` change together 50% of the time (5 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — 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 5 shared commits counted here, the most recent 3 are `15489e47` feat(at_client_flutter): dialogs keep a pending enrollment until Cancel; `6a6dbe73` docs: every storage example passes a storage, and refusals are named; `0200333a` fix(at_client_flutter): prevent dialogs form hanging and improve api … — run `git show` on any of them.
Change coupling: cram_dialog.dart ↔ pkam_dialog.dart packages/at_client_flutter/lib/src/widgets/cram_dialog.dart:1— `packages/at_client_flutter/lib/src/widgets/cram_dialog.dart` and `packages/at_client_flutter/lib/src/widgets/pkam_dialog.dart` change together 50% of the time (5 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — 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 5 shared commits counted here, the most recent 3 are `6a6dbe73` docs: every storage example passes a storage, and refusals are named; `0200333a` fix(at_client_flutter): prevent dialogs form hanging and improve api …; `55dcf159` fix(at_client_flutter): harden onboarding dialogs for the bounded-tim… — run `git show` on any of them.
Duplicated block (5 lines × 2) packages/at_chops/lib/src/algorithm/signing/ml_dsa_65_ffi.dart:355— packages/at_chops/lib/src/algorithm/signing/ml_dsa_65_ffi.dart:355-359 | packages/at_chops/lib/src/algorithm/signing/ml_dsa_65_ffi.dart:372-376 — 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) packages/at_events_flutter/lib/common_components/overlapping_contacts.dart:48— packages/at_events_flutter/lib/common_components/overlapping_contacts.dart:48-52 | packages/at_events_flutter/lib/common_components/overlapping_contacts.dart:156-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 (5 lines × 2) packages/at_location_flutter/lib/common_components/marker_custom_painter.dart:7— packages/at_location_flutter/lib/common_components/marker_custom_painter.dart:7-11 | packages/at_location_flutter/lib/common_components/marker_custom_painter.dart:33-37 — 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) packages/at_location_flutter/lib/common_components/marker_custom_painter.dart:8— packages/at_location_flutter/lib/common_components/marker_custom_painter.dart:8-12 | packages/at_location_flutter/lib/common_components/marker_custom_painter.dart:42-46 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (5 lines × 2) packages/at_location_flutter/lib/map_content/flutter_map/src/layer/polygon_layer.dart:136— packages/at_location_flutter/lib/map_content/flutter_map/src/layer/polygon_layer.dart:136-140 | packages/at_location_flutter/lib/map_content/flutter_map/src/layer/polyline_layer.dart:117-121 — before extracting anything, compare `packages/at_location_flutter/lib/map_content/flutter_map/src/layer/polygon_layer.dart` and `packages/at_location_flutter/lib/map_content/flutter_map/src/layer/polyline_layer.dart` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 35 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) packages/at_client/lib/src/key_stream/key_stream_mixin.dart:398— packages/at_client/lib/src/key_stream/key_stream_mixin.dart:398-402 | packages/at_utils/lib/src/networking/pseudo_server_socket.dart:115-119 — 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) packages/at_client/lib/src/key_stream/key_stream_mixin.dart:476— packages/at_client/lib/src/key_stream/key_stream_mixin.dart:476-480 | packages/at_utils/lib/src/networking/pseudo_server_socket.dart:196-200 — 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) packages/at_client/example/lib/dockerstats/models.dart:102— packages/at_client/example/lib/dockerstats/models.dart:102-106 | packages/at_client_flutter/example/dockerstats/lib/models/stats_models.dart:41-45 — before extracting anything, compare `packages/at_client/example/lib/dockerstats/models.dart` and `packages/at_client_flutter/example/dockerstats/lib/models/stats_models.dart` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 39 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) packages/at_client_flutter/lib/src/widgets/authorisation/containers/enrollment_request_list.dart:206— packages/at_client_flutter/lib/src/widgets/authorisation/containers/enrollment_request_list.dart:206-218 | packages/at_client_flutter/lib/src/widgets/authorisation/containers/enrollment_request_list.dart:231-243 — 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) packages/at_contacts_group_flutter/lib/services/group_service.dart:407— packages/at_contacts_group_flutter/lib/services/group_service.dart:407-419 | packages/at_contacts_group_flutter/lib/services/group_service.dart:451-463 — 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) packages/at_contacts_group_flutter/lib/widgets/triple_dot_loading.dart:55— packages/at_contacts_group_flutter/lib/widgets/triple_dot_loading.dart:55-67 | packages/at_events_flutter/lib/common_components/triple_dot_loading.dart:55-67 — before extracting anything, compare `packages/at_contacts_group_flutter/lib/widgets/triple_dot_loading.dart` and `packages/at_events_flutter/lib/common_components/triple_dot_loading.dart` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 51 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) packages/at_follows_flutter/lib/widgets/custom_appbar.dart:73— packages/at_follows_flutter/lib/widgets/custom_appbar.dart:73-85 | packages/at_login_flutter/lib/widgets/custom_appbar.dart:69-81 — before extracting anything, compare `packages/at_follows_flutter/lib/widgets/custom_appbar.dart` and `packages/at_login_flutter/lib/widgets/custom_appbar.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 (13 lines × 2) packages/at_chat_flutter/example/lib/main.dart:124— packages/at_chat_flutter/example/lib/main.dart:124-136 | packages/at_follows_flutter/example/lib/main.dart:93-105 — 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 (13 lines × 2) packages/at_contacts_flutter/example/lib/second_screen.dart:140— packages/at_contacts_flutter/example/lib/second_screen.dart:140-152 | packages/at_contacts_group_flutter/example/lib/second_screen.dart:71-83 — before extracting anything, compare `packages/at_contacts_flutter/example/lib/second_screen.dart` and `packages/at_contacts_group_flutter/example/lib/second_screen.dart` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 41 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) packages/at_contacts_group_flutter/example/lib/second_screen.dart:32— packages/at_contacts_group_flutter/example/lib/second_screen.dart:32-44 | packages/at_sync_ui_flutter/example/lib/second_screen.dart:57-69 — 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) packages/at_chops/lib/src/algorithm/signing/ml_dsa_65_ffi.dart:283— packages/at_chops/lib/src/algorithm/signing/ml_dsa_65_ffi.dart:283-293 | packages/at_chops/lib/src/algorithm/signing/ml_dsa_65_pure_dart.dart:142-152 — 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) packages/at_contacts_flutter/lib/desktop_screens/desktop_contacts_screen.dart:233— packages/at_contacts_flutter/lib/desktop_screens/desktop_contacts_screen.dart:233-243 | packages/at_contacts_group_flutter/lib/screens/group_contact_view/group_contact_view.dart:247-257 — 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) packages/at_contacts_flutter/lib/widgets/circular_contacts.dart:34— packages/at_contacts_flutter/lib/widgets/circular_contacts.dart:34-44 | packages/at_contacts_group_flutter/lib/widgets/circular_contacts.dart:132-142 — 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) packages/at_follows_flutter/lib/widgets/custom_appbar.dart:93— packages/at_follows_flutter/lib/widgets/custom_appbar.dart:93-103 | packages/at_login_flutter/lib/widgets/custom_appbar.dart:90-100 — before extracting anything, compare `packages/at_follows_flutter/lib/widgets/custom_appbar.dart` and `packages/at_login_flutter/lib/widgets/custom_appbar.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 (11 lines × 2) packages/at_location_flutter/lib/map_content/flutter_map_marker_cluster/src/marker_cluster_layer.dart:380— packages/at_location_flutter/lib/map_content/flutter_map_marker_cluster/src/marker_cluster_layer.dart:380-390 | packages/at_location_flutter/lib/map_content/flutter_map_marker_cluster/src/marker_cluster_layer.dart:399-409 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2) packages/at_follows_flutter/lib/services/size_config.dart:73— packages/at_follows_flutter/lib/services/size_config.dart:73-83 | packages/at_login_flutter/lib/services/size_config.dart:70-80 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (11 lines × 2) packages/at_client_flutter/example/todos/lib/screens/todo_detail.dart:60— packages/at_client_flutter/example/todos/lib/screens/todo_detail.dart:60-70 | packages/at_client_flutter/example/todos/lib/screens/todos_home.dart:154-164 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (7 lines × 2) packages/at_client/lib/src/crypto/nskey/nskey_private_filing.dart:309— packages/at_client/lib/src/crypto/nskey/nskey_private_filing.dart:309-315 | packages/at_client/lib/src/crypto/nskey/pq_signing_root.dart:539-545 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (7 lines × 2) packages/at_contacts_flutter/lib/widgets/bottom_sheet.dart:23— packages/at_contacts_flutter/lib/widgets/bottom_sheet.dart:23-31 | packages/at_contacts_group_flutter/lib/widgets/contacts_selction_bottom_sheet.dart:34-40 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (7 lines × 2) packages/at_contacts_group_flutter/lib/desktop_screens/desktop_group_detail.dart:141— packages/at_contacts_group_flutter/lib/desktop_screens/desktop_group_detail.dart:141-147 | packages/at_contacts_group_flutter/lib/screens/group_view/group_view.dart:195-201 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (7 lines × 2) packages/at_client/lib/src/crypto/nskey/nskey_provider.dart:394— packages/at_client/lib/src/crypto/nskey/nskey_provider.dart:394-400 | packages/at_client/lib/src/crypto/nskey/symmetric_aes_gcm_provider.dart:427-433 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (7 lines × 2) packages/at_contacts_group_flutter/lib/desktop_screens/desktop_new_group.dart:42— packages/at_contacts_group_flutter/lib/desktop_screens/desktop_new_group.dart:42-48 | packages/at_contacts_group_flutter/lib/screens/new_group/new_group.dart:56-62 — before extracting anything, compare `packages/at_contacts_group_flutter/lib/desktop_screens/desktop_new_group.dart` and `packages/at_contacts_group_flutter/lib/screens/new_group/new_group.dart` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 44 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (7 lines × 2) packages/at_client/example/lib/dockerstats/models.dart:186— packages/at_client/example/lib/dockerstats/models.dart:186-192 | packages/at_client_flutter/example/dockerstats/lib/models/stats_models.dart:104-110 — before extracting anything, compare `packages/at_client/example/lib/dockerstats/models.dart` and `packages/at_client_flutter/example/dockerstats/lib/models/stats_models.dart` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 39 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (7 lines × 2) packages/at_client_flutter/example/todos/lib/screens/todo_detail.dart:192— packages/at_client_flutter/example/todos/lib/screens/todo_detail.dart:192-198 | packages/at_client_flutter/example/todos/lib/screens/todos_home.dart:503-509 — 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.
Sync-over-async blocking packages/at_client_flutter/example/invitations/lib/session.dart:232— `_storage` is async and calls deleteSync, createSync — a blocking call inside async code stalls the isolate's event loop — every other event, on Flutter the next frame, waits for as long as it runs.
Sync-over-async blocking tools/wasm_shakedown/lib/runner.dart:114— `_probe` is async and calls createSync, writeAsStringSync, deleteSync — a blocking call inside async code stalls the isolate's event loop — every other event, on Flutter the next frame, waits for as long as it runs.
Sync-over-async blocking packages/at_chat_flutter/lib/services/chat_service.dart:322— `sendImageFile` is async and calls readAsBytesSync — a blocking call inside async code stalls the isolate's event loop — every other event, on Flutter the next frame, waits for as long as it runs.
Sync-over-async blocking packages/at_client_flutter/example/lib/snippets/at_backup_key.dart:96— `onBackup` is async and calls writeAsStringSync — a blocking call inside async code stalls the isolate's event loop — every other event, on Flutter the next frame, waits for as long as it runs.
Sync-over-async blocking packages/at_client_flutter/example/lib/snippets/at_backup_key.dart:232— `_generateFile` is async and calls writeAsStringSync — a blocking call inside async code stalls the isolate's event loop — every other event, on Flutter the next frame, waits for as long as it runs.
Sync-over-async blocking packages/at_auth/lib/src/keys/io/file_lock.dart:92— `_acquire` is async and calls deleteSync — a blocking call inside async code stalls the isolate's event loop — every other event, on Flutter the next frame, waits for as long as it runs.
Sync-over-async blocking packages/at_lookup/lib/src/io/secure_socket_util.dart:11— `createSecureSocket` is async and calls writeAsStringSync — a blocking call inside async code stalls the isolate's event loop — every other event, on Flutter the next frame, waits for as long as it runs.
Duplicated block (17–18 lines × 2) packages/at_chops/lib/src/algorithm/encryption/aes_ctr_ffi_algo.dart:141— packages/at_chops/lib/src/algorithm/encryption/aes_ctr_ffi_algo.dart:141-158 | packages/at_chops/lib/src/algorithm/encryption/aes_gcm_ffi_algo.dart:134-150 — before extracting anything, compare `packages/at_chops/lib/src/algorithm/encryption/aes_ctr_ffi_algo.dart` and `packages/at_chops/lib/src/algorithm/encryption/aes_gcm_ffi_algo.dart` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 62 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (17–18 lines × 2) packages/at_client_flutter/lib/src/widgets/apkam_dialog.dart:402— packages/at_client_flutter/lib/src/widgets/apkam_dialog.dart:402-418 | packages/at_client_flutter/lib/src/widgets/registrar_cram_dialog.dart:165-182 — before extracting anything, compare `packages/at_client_flutter/lib/src/widgets/apkam_dialog.dart` and `packages/at_client_flutter/lib/src/widgets/registrar_cram_dialog.dart` as WHOLE FILES: this scan already matched 5 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–18 lines × 2) packages/at_contacts_flutter/lib/screens/contacts_screen.dart:308— packages/at_contacts_flutter/lib/screens/contacts_screen.dart:308-325 | packages/at_contacts_group_flutter/lib/screens/group_contact_view/group_contact_view.dart:517-533 — 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 (17–18 lines × 2) packages/at_contacts_flutter/lib/screens/contacts_screen.dart:334— packages/at_contacts_flutter/lib/screens/contacts_screen.dart:334-351 | packages/at_contacts_group_flutter/lib/screens/group_contact_view/group_contact_view.dart:550-566 — 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 (17–18 lines × 2) packages/at_events_flutter/lib/common_components/floating_icon.dart:38— packages/at_events_flutter/lib/common_components/floating_icon.dart:38-55 | packages/at_location_flutter/lib/common_components/floating_icon.dart:39-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 (16 lines × 2) packages/at_contacts_group_flutter/lib/screens/edit/group_edit.dart:584— packages/at_contacts_group_flutter/lib/screens/edit/group_edit.dart:584-599 | packages/at_contacts_group_flutter/lib/screens/group_view/group_view.dart:392-407 — before extracting anything, compare `packages/at_contacts_group_flutter/lib/screens/edit/group_edit.dart` and `packages/at_contacts_group_flutter/lib/screens/group_view/group_view.dart` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 79 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (16 lines × 2) packages/at_contacts_group_flutter/lib/widgets/desktop_person_horizontal_tile.dart:51— packages/at_contacts_group_flutter/lib/widgets/desktop_person_horizontal_tile.dart:51-66 | packages/at_contacts_group_flutter/lib/widgets/person_horizontal_tile.dart:54-69 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (16 lines × 2) packages/at_contacts_group_flutter/lib/widgets/desktop_person_vertical_tile.dart:62— packages/at_contacts_group_flutter/lib/widgets/desktop_person_vertical_tile.dart:62-77 | packages/at_contacts_group_flutter/lib/widgets/person_vertical_tile.dart:68-83 — before extracting anything, compare `packages/at_contacts_group_flutter/lib/widgets/desktop_person_vertical_tile.dart` and `packages/at_contacts_group_flutter/lib/widgets/person_vertical_tile.dart` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 71 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) packages/at_client_flutter/example/lib/main.dart:201— packages/at_client_flutter/example/lib/main.dart:201-216 | packages/at_client_flutter/example/lib/main.dart:227-242 — 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) packages/at_contacts_flutter/example/lib/second_screen.dart:108— packages/at_contacts_flutter/example/lib/second_screen.dart:108-123 | packages/at_contacts_group_flutter/example/lib/second_screen.dart:36-51 — before extracting anything, compare `packages/at_contacts_flutter/example/lib/second_screen.dart` and `packages/at_contacts_group_flutter/example/lib/second_screen.dart` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 41 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) packages/at_chops/lib/src/algorithm/encryption/aes_gcm_ffi_algo.dart:121— packages/at_chops/lib/src/algorithm/encryption/aes_gcm_ffi_algo.dart:121-135 | packages/at_chops/lib/src/algorithm/encryption/aes_gcm_ffi_algo.dart:245-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 (15 lines × 2) packages/at_contacts_group_flutter/lib/desktop_screens/desktop_new_group.dart:63— packages/at_contacts_group_flutter/lib/desktop_screens/desktop_new_group.dart:63-77 | packages/at_contacts_group_flutter/lib/screens/new_group/new_group.dart:75-89 — before extracting anything, compare `packages/at_contacts_group_flutter/lib/desktop_screens/desktop_new_group.dart` and `packages/at_contacts_group_flutter/lib/screens/new_group/new_group.dart` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 44 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) packages/at_contacts_group_flutter/lib/screens/list/group_list.dart:192— packages/at_contacts_group_flutter/lib/screens/list/group_list.dart:192-206 | packages/at_contacts_group_flutter/lib/screens/list/group_list.dart:252-266 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (15 lines × 2) packages/at_contacts_group_flutter/lib/widgets/desktop_person_vertical_tile.dart:84— packages/at_contacts_group_flutter/lib/widgets/desktop_person_vertical_tile.dart:84-98 | packages/at_contacts_group_flutter/lib/widgets/person_vertical_tile.dart:90-104 — before extracting anything, compare `packages/at_contacts_group_flutter/lib/widgets/desktop_person_vertical_tile.dart` and `packages/at_contacts_group_flutter/lib/widgets/person_vertical_tile.dart` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 71 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) packages/at_events_flutter/lib/common_components/floating_icon.dart:22— packages/at_events_flutter/lib/common_components/floating_icon.dart:22-36 | packages/at_location_flutter/lib/common_components/floating_icon.dart:23-37 — 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) packages/at_auth/lib/src/enroll/enrollment_handshake.dart:220— packages/at_auth/lib/src/enroll/enrollment_handshake.dart:220-229 | packages/at_auth/lib/src/enroll/enrollment_handshake.dart:235-244 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2) packages/at_chat_flutter/lib/widgets/incoming_message_bubble.dart:65— packages/at_chat_flutter/lib/widgets/incoming_message_bubble.dart:65-74 | packages/at_chat_flutter/lib/widgets/outgoing_message_bubble.dart:73-82 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (10 lines × 2) packages/at_location_flutter/lib/map_content/flutter_map/src/layer/polygon_layer.dart:198— packages/at_location_flutter/lib/map_content/flutter_map/src/layer/polygon_layer.dart:198-207 | packages/at_location_flutter/lib/map_content/flutter_map/src/layer/polyline_layer.dart:202-211 — before extracting anything, compare `packages/at_location_flutter/lib/map_content/flutter_map/src/layer/polygon_layer.dart` and `packages/at_location_flutter/lib/map_content/flutter_map/src/layer/polyline_layer.dart` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 35 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (10 lines × 2) packages/at_contacts_group_flutter/example/lib/main.dart:50— packages/at_contacts_group_flutter/example/lib/main.dart:50-59 | packages/at_events_flutter/example/lib/main.dart:50-59 — before extracting anything, compare `packages/at_contacts_group_flutter/example/lib/main.dart` and `packages/at_events_flutter/example/lib/main.dart` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 196 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) packages/at_sync_ui_flutter/example/lib/ui_options.dart:321— packages/at_sync_ui_flutter/example/lib/ui_options.dart:321-330 | packages/at_sync_ui_flutter/example/lib/ui_options.dart:334-343 — 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 × 3) packages/at_chops/lib/src/algorithm/encryption/ml_kem_768_ffi.dart:64— packages/at_chops/lib/src/algorithm/encryption/ml_kem_768_ffi.dart:64-73 | packages/at_chops/lib/src/algorithm/encryption/x25519_ffi_algo.dart:34-43 | packages/at_chops/lib/src/algorithm/signing/ml_dsa_65_ffi.dart:70-78 — before extracting anything, compare `packages/at_chops/lib/src/algorithm/encryption/x25519_ffi_algo.dart` and `packages/at_chops/lib/src/algorithm/signing/ml_dsa_65_ffi.dart` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 64 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 (9 lines × 3) packages/at_contacts_group_flutter/lib/widgets/custom_popup_route.dart:40— packages/at_contacts_group_flutter/lib/widgets/custom_popup_route.dart:40-48 | packages/at_events_flutter/lib/common_components/custom_popup_route.dart:40-48 | packages/at_location_flutter/lib/common_components/custom_popup_route.dart:40-48 — 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 (9 lines × 3) packages/at_location_flutter/lib/map_content/flutter_map/src/layer/circle_layer.dart:55— packages/at_location_flutter/lib/map_content/flutter_map/src/layer/circle_layer.dart:55-63 | packages/at_location_flutter/lib/map_content/flutter_map/src/layer/polygon_layer.dart:75-83 | packages/at_location_flutter/lib/map_content/flutter_map/src/layer/polyline_layer.dart:73-81 — before extracting anything, compare `packages/at_location_flutter/lib/map_content/flutter_map/src/layer/polygon_layer.dart` and `packages/at_location_flutter/lib/map_content/flutter_map/src/layer/polyline_layer.dart` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 35 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 × 3) packages/at_events_flutter/example/lib/second_screen.dart:153— packages/at_events_flutter/example/lib/second_screen.dart:153-161 | packages/at_location_flutter/example/lib/second_screen.dart:228-238 | packages/at_sync_ui_flutter/example/lib/second_screen.dart:150-160 — 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 (9 lines × 3) packages/at_client/example/lib/dockerstats/models.dart:194— packages/at_client/example/lib/dockerstats/models.dart:194-202 | packages/at_client_flutter/example/dockerstats/lib/models/stats_models.dart:112-120 | packages/at_client_flutter/example/dockerstats/lib/services/samples_db.dart:439-447 — before extracting anything, compare `packages/at_client/example/lib/dockerstats/models.dart` and `packages/at_client_flutter/example/dockerstats/lib/models/stats_models.dart` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 39 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) packages/at_location_flutter/lib/map_content/flutter_map/src/layer/polygon_layer.dart:141— packages/at_location_flutter/lib/map_content/flutter_map/src/layer/polygon_layer.dart:141-146 | packages/at_location_flutter/lib/map_content/flutter_map/src/layer/polyline_layer.dart:122-127 — before extracting anything, compare `packages/at_location_flutter/lib/map_content/flutter_map/src/layer/polygon_layer.dart` and `packages/at_location_flutter/lib/map_content/flutter_map/src/layer/polyline_layer.dart` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 35 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) packages/at_client/lib/src/storage/memory/in_memory_at_client_storage.dart:43— packages/at_client/lib/src/storage/memory/in_memory_at_client_storage.dart:43-48 | packages/at_client/lib/src/storage/sqlite/sqlite_at_client_storage.dart:65-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.
Duplicated block (6 lines × 2) packages/at_client/lib/src/key_stream/key_stream_mixin.dart:327— packages/at_client/lib/src/key_stream/key_stream_mixin.dart:327-333 | packages/at_utils/lib/src/networking/pseudo_server_socket.dart:42-47 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (6 lines × 2) packages/at_contacts_flutter/lib/utils/text_styles.dart:82— packages/at_contacts_flutter/lib/utils/text_styles.dart:82-87 | packages/at_contacts_group_flutter/lib/utils/text_styles.dart:73-78 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (6 lines × 2) packages/at_client/example/lib/domain_objects.dart:23— packages/at_client/example/lib/domain_objects.dart:23-28 | packages/at_client_flutter/example/todos/lib/models/todo.dart:27-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.
D4 · Code Duplication· Members sharing a duplicated core (4 members, 50+ identical tokens) · ×4
Members sharing a duplicated core (4 members, 50+ identical tokens) packages/at_chops/lib/src/algorithm/encryption/aes_ctr_ffi_algo.dart:101— packages/at_chops/lib/src/algorithm/encryption/aes_ctr_ffi_algo.dart:101-168 | packages/at_chops/lib/src/algorithm/encryption/aes_ctr_ffi_algo.dart:170-233 | packages/at_chops/lib/src/algorithm/encryption/aes_gcm_ffi_algo.dart:73-186 | packages/at_chops/lib/src/algorithm/encryption/aes_gcm_ffi_algo.dart:188-309 — 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) packages/at_contacts_flutter/lib/widgets/add_contacts_dialog.dart:43— packages/at_contacts_flutter/lib/widgets/add_contacts_dialog.dart:43-188 | packages/at_contacts_flutter/lib/widgets/add_singular_contact_dialog.dart:26-105 | packages/at_contacts_group_flutter/lib/widgets/add_contacts_group_dialog.dart:30-156 | packages/at_contacts_group_flutter/lib/widgets/add_single_contact_group.dart:25-120 — 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) packages/at_contacts_group_flutter/lib/screens/edit/person_horizontal.dart:34— packages/at_contacts_group_flutter/lib/screens/edit/person_horizontal.dart:34-52 | packages/at_contacts_group_flutter/lib/widgets/confirmation_dialog.dart:49-62 | packages/at_contacts_group_flutter/lib/widgets/person_vertical_tile.dart:44-66 | packages/at_location_flutter/lib/screens/notification_dialog/notification_dialog.dart:57-70 — 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) packages/at_events_flutter/lib/common_components/concurrent_event_request_dialog.dart:40— packages/at_events_flutter/lib/common_components/concurrent_event_request_dialog.dart:40-114 | packages/at_events_flutter/lib/common_components/error_screen.dart:9-37 | packages/at_events_flutter/lib/screens/recurring_event.dart:48-387 | packages/at_events_flutter/lib/screens/selected_location.dart:36-185 — 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 (18 lines × 2) packages/at_chops/lib/src/algorithm/encryption/aes_ctr_ffi_algo.dart:64— packages/at_chops/lib/src/algorithm/encryption/aes_ctr_ffi_algo.dart:64-81 | packages/at_chops/lib/src/algorithm/encryption/aes_gcm_ffi_algo.dart:44-61 — before extracting anything, compare `packages/at_chops/lib/src/algorithm/encryption/aes_ctr_ffi_algo.dart` and `packages/at_chops/lib/src/algorithm/encryption/aes_gcm_ffi_algo.dart` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 62 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (18 lines × 2) packages/at_contacts_group_flutter/lib/widgets/triple_dot_loading.dart:103— packages/at_contacts_group_flutter/lib/widgets/triple_dot_loading.dart:103-120 | packages/at_events_flutter/lib/common_components/triple_dot_loading.dart:105-122 — before extracting anything, compare `packages/at_contacts_group_flutter/lib/widgets/triple_dot_loading.dart` and `packages/at_events_flutter/lib/common_components/triple_dot_loading.dart` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 51 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 (18 lines × 2) packages/at_location_flutter/lib/map_content/flutter_map_marker_cluster/src/marker_cluster_layer.dart:226— packages/at_location_flutter/lib/map_content/flutter_map_marker_cluster/src/marker_cluster_layer.dart:226-243 | packages/at_location_flutter/lib/map_content/flutter_map_marker_cluster/src/marker_cluster_layer.dart:333-350 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (18 lines × 2) packages/at_client/example/lib/dockerstats/models.dart:167— packages/at_client/example/lib/dockerstats/models.dart:167-184 | packages/at_client_flutter/example/dockerstats/lib/models/stats_models.dart:85-102 — before extracting anything, compare `packages/at_client/example/lib/dockerstats/models.dart` and `packages/at_client_flutter/example/dockerstats/lib/models/stats_models.dart` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 39 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 (8 lines × 3) packages/at_contacts_group_flutter/lib/screens/edit/person_horizontal.dart:34— packages/at_contacts_group_flutter/lib/screens/edit/person_horizontal.dart:34-41 | packages/at_contacts_group_flutter/lib/widgets/confirmation_dialog.dart:49-56 | packages/at_contacts_group_flutter/lib/widgets/person_vertical_tile.dart: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.
Duplicated block (8 lines × 3) packages/at_contacts_group_flutter/lib/widgets/bottom_sheet.dart:66— packages/at_contacts_group_flutter/lib/widgets/bottom_sheet.dart:66-73 | packages/at_contacts_group_flutter/lib/widgets/confirmation_dialog.dart:147-155 | packages/at_contacts_group_flutter/lib/widgets/error_screen.dart:36-43 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once.
Duplicated block (8 lines × 3) packages/at_contacts_flutter/macos/Classes/AtContactsFlutterPlugin.swift:11— packages/at_contacts_flutter/macos/Classes/AtContactsFlutterPlugin.swift:11-18 | packages/at_contacts_group_flutter/macos/Classes/AtContactsGroupFlutterPlugin.swift:11-18 | packages/at_login_flutter/macos/Classes/AtLoginFlutterPlugin.swift:11-18 — 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 (8 lines × 3) packages/at_sync_ui_flutter/example/lib/ui_options.dart:321— packages/at_sync_ui_flutter/example/lib/ui_options.dart:321-328 | packages/at_sync_ui_flutter/example/lib/ui_options.dart:334-341 | packages/at_sync_ui_flutter/example/lib/ui_options.dart:347-354 — 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 (22 lines × 2) packages/at_contacts_group_flutter/lib/desktop_screens/desktop_new_group.dart:282— packages/at_contacts_group_flutter/lib/desktop_screens/desktop_new_group.dart:282-303 | packages/at_contacts_group_flutter/lib/screens/new_group/new_group.dart:226-247 — before extracting anything, compare `packages/at_contacts_group_flutter/lib/desktop_screens/desktop_new_group.dart` and `packages/at_contacts_group_flutter/lib/screens/new_group/new_group.dart` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 44 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) packages/at_follows_flutter/lib/services/size_config.dart:36— packages/at_follows_flutter/lib/services/size_config.dart:36-57 | packages/at_login_flutter/lib/services/size_config.dart:33-54 — 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 (22 lines × 2) packages/at_theme_flutter/example/lib/src/pages/profile_page.dart:240— packages/at_theme_flutter/example/lib/src/pages/profile_page.dart:240-261 | packages/at_theme_flutter/example/lib/src/pages/profile_page.dart:298-319 — 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–16 lines × 2) packages/at_chops/lib/src/algorithm/encryption/aes_ctr_ffi_algo.dart:203— packages/at_chops/lib/src/algorithm/encryption/aes_ctr_ffi_algo.dart:203-218 | packages/at_chops/lib/src/algorithm/encryption/aes_gcm_ffi_algo.dart:258-272 — before extracting anything, compare `packages/at_chops/lib/src/algorithm/encryption/aes_ctr_ffi_algo.dart` and `packages/at_chops/lib/src/algorithm/encryption/aes_gcm_ffi_algo.dart` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 62 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (15–16 lines × 2) packages/at_chops/lib/src/algorithm/encryption/ml_kem_768_ffi.dart:172— packages/at_chops/lib/src/algorithm/encryption/ml_kem_768_ffi.dart:172-186 | packages/at_chops/lib/src/algorithm/encryption/ml_kem_768_ffi.dart:337-352 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (15–16 lines × 2) packages/at_chops/lib/src/algorithm/encryption/x25519_ffi_algo.dart:34— packages/at_chops/lib/src/algorithm/encryption/x25519_ffi_algo.dart:34-49 | packages/at_chops/lib/src/algorithm/signing/ml_dsa_65_ffi.dart:70-84 — before extracting anything, compare `packages/at_chops/lib/src/algorithm/encryption/x25519_ffi_algo.dart` and `packages/at_chops/lib/src/algorithm/signing/ml_dsa_65_ffi.dart` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 64 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 × 4) packages/at_chops/lib/src/algorithm/encryption/aes_ctr_ffi_algo.dart:138— packages/at_chops/lib/src/algorithm/encryption/aes_ctr_ffi_algo.dart:138-147 | packages/at_chops/lib/src/algorithm/encryption/aes_ctr_ffi_algo.dart:200-209 | packages/at_chops/lib/src/algorithm/encryption/aes_gcm_ffi_algo.dart:131-140 | packages/at_chops/lib/src/algorithm/encryption/aes_gcm_ffi_algo.dart:255-264 — before extracting anything, compare `packages/at_chops/lib/src/algorithm/encryption/aes_ctr_ffi_algo.dart` and `packages/at_chops/lib/src/algorithm/encryption/aes_gcm_ffi_algo.dart` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 62 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (10 lines × 4) packages/at_client_flutter/example/lib/main.dart:200— packages/at_client_flutter/example/lib/main.dart:200-209 | packages/at_client_flutter/example/lib/main.dart:226-235 | packages/at_client_flutter/example/lib/main.dart:271-280 | packages/at_client_flutter/example/lib/main.dart:300-309 — 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 (10 lines × 4) packages/at_client_flutter/example/dockerstats/ios/Runner/AppDelegate.swift:6— packages/at_client_flutter/example/dockerstats/ios/Runner/AppDelegate.swift:6-15 | packages/at_client_flutter/example/invitations/ios/Runner/AppDelegate.swift:6-15 | packages/at_client_flutter/example/ios/Runner/AppDelegate.swift:6-15 | packages/at_client_flutter/example/todos/ios/Runner/AppDelegate.swift:6-15 — before extracting anything, compare `packages/at_client_flutter/example/dockerstats/ios/Runner/AppDelegate.swift` and `packages/at_client_flutter/example/invitations/ios/Runner/AppDelegate.swift` as WHOLE FILES: 100% 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.
Duplicated block (39 lines × 2) packages/at_client_flutter/lib/src/widgets/apkam_dialog.dart:466— packages/at_client_flutter/lib/src/widgets/apkam_dialog.dart:466-504 | packages/at_client_flutter/lib/src/widgets/registrar_cram_dialog.dart:219-257 — before extracting anything, compare `packages/at_client_flutter/lib/src/widgets/apkam_dialog.dart` and `packages/at_client_flutter/lib/src/widgets/registrar_cram_dialog.dart` as WHOLE FILES: this scan already matched 5 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 (39 lines × 2) packages/at_follows_flutter/lib/widgets/custom_appbar.dart:30— packages/at_follows_flutter/lib/widgets/custom_appbar.dart:30-68 | packages/at_login_flutter/lib/widgets/custom_appbar.dart:26-64 — before extracting anything, compare `packages/at_follows_flutter/lib/widgets/custom_appbar.dart` and `packages/at_login_flutter/lib/widgets/custom_appbar.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) packages/at_contacts_flutter/lib/widgets/error_screen.dart:14— packages/at_contacts_flutter/lib/widgets/error_screen.dart:14-38 | packages/at_contacts_group_flutter/lib/widgets/error_screen.dart:13-37 — 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 (25 lines × 2) packages/at_sync_ui_flutter/lib/at_sync_cupertino.dart:192— packages/at_sync_ui_flutter/lib/at_sync_cupertino.dart:192-216 | packages/at_sync_ui_flutter/lib/at_sync_material.dart:82-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 (23–24 lines × 2) packages/at_client_flutter/lib/src/widgets/apkam_dialog.dart:599— packages/at_client_flutter/lib/src/widgets/apkam_dialog.dart:599-622 | packages/at_client_flutter/lib/src/widgets/registrar_cram_dialog.dart:341-363 — before extracting anything, compare `packages/at_client_flutter/lib/src/widgets/apkam_dialog.dart` and `packages/at_client_flutter/lib/src/widgets/registrar_cram_dialog.dart` as WHOLE FILES: this scan already matched 5 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 (23–24 lines × 2) packages/at_contacts_flutter/lib/screens/blocked_screen.dart:75— packages/at_contacts_flutter/lib/screens/blocked_screen.dart:75-97 | packages/at_contacts_group_flutter/lib/screens/list/group_list.dart:109-132 — 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) packages/at_contacts_group_flutter/lib/desktop_screens/desktop_empty_group.dart:90— packages/at_contacts_group_flutter/lib/desktop_screens/desktop_empty_group.dart:90-113 | packages/at_contacts_group_flutter/lib/screens/empty_group/empty_group.dart:35-58 — 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) packages/at_events_flutter/lib/common_components/contacts_initials.dart:17— packages/at_events_flutter/lib/common_components/contacts_initials.dart:17-40 | packages/at_location_flutter/lib/common_components/contacts_initial.dart:17-40 — 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) packages/at_chops/lib/src/algorithm/encryption/x25519_ffi_algo.dart:153— packages/at_chops/lib/src/algorithm/encryption/x25519_ffi_algo.dart:153-171 | packages/at_chops/lib/src/algorithm/signing/ml_dsa_65_ffi.dart:314-332 — before extracting anything, compare `packages/at_chops/lib/src/algorithm/encryption/x25519_ffi_algo.dart` and `packages/at_chops/lib/src/algorithm/signing/ml_dsa_65_ffi.dart` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 64 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 (19 lines × 2) packages/at_chops/lib/src/algorithm/encryption/x25519_ffi_algo.dart:173— packages/at_chops/lib/src/algorithm/encryption/x25519_ffi_algo.dart:173-191 | packages/at_chops/lib/src/algorithm/signing/ml_dsa_65_ffi.dart:334-352 — before extracting anything, compare `packages/at_chops/lib/src/algorithm/encryption/x25519_ffi_algo.dart` and `packages/at_chops/lib/src/algorithm/signing/ml_dsa_65_ffi.dart` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 64 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) packages/at_contacts_flutter/lib/screens/blocked_screen.dart:137— packages/at_contacts_flutter/lib/screens/blocked_screen.dart:137-153 | packages/at_contacts_group_flutter/lib/screens/list/group_list.dart:208-225 — 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 (17 lines × 2) packages/at_follows_flutter/lib/screens/notifications.dart:7— packages/at_follows_flutter/lib/screens/notifications.dart:7-23 | packages/at_login_flutter/lib/widgets/notifications.dart:7-23 — 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–16 lines × 2) packages/at_contacts_group_flutter/lib/screens/edit/group_edit.dart:453— packages/at_contacts_group_flutter/lib/screens/edit/group_edit.dart:453-466 | packages/at_contacts_group_flutter/lib/screens/group_view/group_view.dart:119-134 — before extracting anything, compare `packages/at_contacts_group_flutter/lib/screens/edit/group_edit.dart` and `packages/at_contacts_group_flutter/lib/screens/group_view/group_view.dart` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 79 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (14–16 lines × 2) packages/at_follows_flutter/lib/services/notification_service.dart:69— packages/at_follows_flutter/lib/services/notification_service.dart:69-84 | packages/at_login_flutter/lib/services/notification_service.dart:65-78 — before extracting anything, compare `packages/at_follows_flutter/lib/services/notification_service.dart` and `packages/at_login_flutter/lib/services/notification_service.dart` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 47 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 × 3) packages/at_contacts_group_flutter/lib/widgets/custom_popup_route.dart:50— packages/at_contacts_group_flutter/lib/widgets/custom_popup_route.dart:50-62 | packages/at_events_flutter/lib/common_components/custom_popup_route.dart:50-62 | packages/at_location_flutter/lib/common_components/custom_popup_route.dart:50-62 — 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 (13 lines × 3) packages/at_contacts_flutter/example/lib/main.dart:54— packages/at_contacts_flutter/example/lib/main.dart:54-66 | packages/at_notify_flutter/example/lib/main.dart:49-61 | packages/at_sync_ui_flutter/example/lib/main.dart:51-63 — before extracting anything, compare `packages/at_contacts_flutter/example/lib/main.dart` and `packages/at_notify_flutter/example/lib/main.dart` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 123 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 × 3) packages/at_contacts_flutter/lib/widgets/custom_circle_avatar.dart:31— packages/at_contacts_flutter/lib/widgets/custom_circle_avatar.dart:31-41 | packages/at_contacts_group_flutter/lib/widgets/custom_circle_avatar.dart:11-21 | packages/at_location_flutter/lib/common_components/custom_circle_avatar.dart:22-33 — 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 (11–12 lines × 3) packages/at_follows_flutter/example/lib/services/notification_service.dart:65— packages/at_follows_flutter/example/lib/services/notification_service.dart:65-75 | packages/at_follows_flutter/lib/services/notification_service.dart:75-86 | packages/at_login_flutter/lib/services/notification_service.dart:69-80 — before extracting anything, compare `packages/at_follows_flutter/example/lib/services/notification_service.dart` and `packages/at_login_flutter/lib/services/notification_service.dart` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 34 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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 × 3) packages/at_follows_flutter/example/lib/services/notification_service.dart:47— packages/at_follows_flutter/example/lib/services/notification_service.dart:47-56 | packages/at_follows_flutter/lib/services/notification_service.dart:53-62 | packages/at_login_flutter/lib/services/notification_service.dart:48-57 — before extracting anything, compare `packages/at_follows_flutter/example/lib/services/notification_service.dart` and `packages/at_login_flutter/lib/services/notification_service.dart` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 34 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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 × 3) packages/at_client_flutter/example/dockerstats/macos/Runner/MainFlutterWindow.swift:5— packages/at_client_flutter/example/dockerstats/macos/Runner/MainFlutterWindow.swift:5-14 | packages/at_client_flutter/example/macos/Runner/MainFlutterWindow.swift:5-14 | packages/at_client_flutter/example/todos/macos/Runner/MainFlutterWindow.swift:5-14 — before extracting anything, compare `packages/at_client_flutter/example/dockerstats/macos/Runner/MainFlutterWindow.swift` and `packages/at_client_flutter/example/macos/Runner/MainFlutterWindow.swift` as WHOLE FILES: 100% 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.
Duplicated block (7 lines × 8) packages/at_client_flutter/example/dockerstats/macos/Runner/AppDelegate.swift:6— packages/at_client_flutter/example/dockerstats/macos/Runner/AppDelegate.swift:6-12 | packages/at_client_flutter/example/invitations/macos/Runner/AppDelegate.swift:6-12 | packages/at_client_flutter/example/macos/Runner/AppDelegate.swift:6-12 | packages/at_client_flutter/example/todos/macos/Runner/AppDelegate.swift:6-12 | packages/at_contacts_flutter/example/macos/Runner/AppDelegate.swift:6-12 | packages/at_contacts_group_flutter/example/macos/Runner/AppDelegate.swift:6-12 | packages/at_sync_ui_flutter/example/macos/Runner/AppDelegate.swift:6-12 | packages/at_theme_flutter/example/macos/Runner/AppDelegate.swift:6-12 — before extracting anything, compare `packages/at_client_flutter/example/dockerstats/macos/Runner/AppDelegate.swift` and `packages/at_client_flutter/example/invitations/macos/Runner/AppDelegate.swift` as WHOLE FILES: 100% 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.
Duplicated block (7 lines × 8) packages/at_chat_flutter/example/ios/Runner/AppDelegate.swift:6— packages/at_chat_flutter/example/ios/Runner/AppDelegate.swift:6-12 | packages/at_contacts_flutter/example/ios/Runner/AppDelegate.swift:6-12 | packages/at_contacts_group_flutter/example/ios/Runner/AppDelegate.swift:6-12 | packages/at_events_flutter/example/ios/Runner/AppDelegate.swift:6-12 | packages/at_location_flutter/example/ios/Runner/AppDelegate.swift:6-12 | packages/at_login_flutter/example/ios/Runner/AppDelegate.swift:6-12 | packages/at_sync_ui_flutter/example/ios/Runner/AppDelegate.swift:6-12 | packages/at_theme_flutter/example/ios/Runner/AppDelegate.swift:6-12 — before extracting anything, compare `packages/at_chat_flutter/example/ios/Runner/AppDelegate.swift` and `packages/at_contacts_group_flutter/example/ios/Runner/AppDelegate.swift` as WHOLE FILES: 100% 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.
Weak hash algorithm packages/at_chops/lib/src/algorithm/hashing/md5.dart:9— MD5/SHA1 is computed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ (`sha256.convert(…)` from `package:crypto`) for content integrity, or a KDF (bcrypt/Argon2/scrypt) for password storage. If it only derives a non-security identifier (a cache key, an avatar URL, an ETag), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as xxhash or murmurhash says it in code — since the algorithm alone cannot distinguish the two uses. Where a protocol this code does not own fixes the digest (a k-anonymity range query, a legacy signature format), the protocol decides; say so beside the call.
Weak hash algorithm packages/at_client/lib/src/util/encryption_util.dart:77— MD5/SHA1 is computed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ (`sha256.convert(…)` from `package:crypto`) for content integrity, or a KDF (bcrypt/Argon2/scrypt) for password storage. If it only derives a non-security identifier (a cache key, an avatar URL, an ETag), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as xxhash or murmurhash says it in code — since the algorithm alone cannot distinguish the two uses. Where a protocol this code does not own fixes the digest (a k-anonymity range query, a legacy signature format), the protocol decides; say so beside the call.
`async` callback passed to `forEach` packages/at_events_flutter/lib/services/event_key_stream_service.dart:136— `forEach` takes a `void` callback and never awaits what it returns, so the Future each `async` call returns is dropped: nothing can await it, the code after this loop runs before any of the awaited work has finished (a function that `await`s around this loop still returns early, and a resource it closes next is closed under the work), and an error is never handled — it surfaces as an uncaught asynchronous error, which terminates a command-line program and reaches only the zone's error handler in Flutter. Iterate with `for (final item in items) { await … }` when the work must run in order, or `await Future.wait(items.map((item) async { … }))` when it may run concurrently, so the enclosing function finishes only when the work does and its failures reach the caller. Where firing and forgetting is genuinely intended, make the callback's whole body a `try { … } catch (e) { … }` that handles the failure, so it cannot escape.
`async` callback passed to `forEach` packages/at_events_flutter/lib/services/event_key_stream_service.dart:139— `forEach` takes a `void` callback and never awaits what it returns, so the Future each `async` call returns is dropped: nothing can await it, the code after this loop runs before any of the awaited work has finished (a function that `await`s around this loop still returns early, and a resource it closes next is closed under the work), and an error is never handled — it surfaces as an uncaught asynchronous error, which terminates a command-line program and reaches only the zone's error handler in Flutter. Iterate with `for (final item in items) { await … }` when the work must run in order, or `await Future.wait(items.map((item) async { … }))` when it may run concurrently, so the enclosing function finishes only when the work does and its failures reach the caller. Where firing and forgetting is genuinely intended, make the callback's whole body a `try { … } catch (e) { … }` that handles the failure, so it cannot escape.
X18 · Disposal-pattern correctness· Owned disposable field is never released · ×2
Owned disposable field is never released packages/at_location_flutter/lib/map_content/flutter_map/src/map/map.dart:87— `MapState` carries a disposal duty — it declares its own release — and it creates `_positionSink` itself (line 87, `StreamController.broadcast`), which makes that instance its own. Nothing in the class releases it — no `_positionSink.close()`, 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, `StreamController.broadcast` 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: `_positionSink.close();` in `dispose()` before `super.dispose()`.
Owned disposable field is never released REDACTED:72— `_ChatScreenState` carries a disposal duty — a `State`, so the framework calls its `dispose()` when it leaves the tree — and it creates `_scrollController` itself (line 72, `ScrollController`), which makes that instance its own. Nothing in the class releases it — no `_scrollController.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, `ScrollController` 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: `_scrollController.dispose();` in `dispose()` before `super.dispose()`.
Query.watch (cyclomatic 34) packages/at_client/lib/src/collections/collections.dart:4076— Query.watch has cyclomatic complexity 34 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
_CreateEventState.build (cyclomatic 33) packages/at_events_flutter/lib/screens/create_event.dart:73— _CreateEventState.build has cyclomatic complexity 33 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
UpdateVerbBuilder.== (cyclomatic 33) packages/at_commons/lib/src/verb/update_verb_builder.dart:218— UpdateVerbBuilder.== has cyclomatic complexity 33 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
SyncServiceImpl._pushFromSyncQueue (cyclomatic 32) packages/at_client/lib/src/service/sync_service_impl.dart:674— SyncServiceImpl._pushFromSyncQueue has cyclomatic complexity 32 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Metadata.== (cyclomatic 31) packages/at_commons/lib/src/keystore/at_key.dart:786— Metadata.== has cyclomatic complexity 31 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
_CollapsedContentState.build (cyclomatic 30) packages/at_location_flutter/lib/common_components/collapsed_content.dart:65— _CollapsedContentState.build has cyclomatic complexity 30 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
_RecurringEventState.build (cyclomatic 29) packages/at_events_flutter/lib/screens/recurring_event.dart:48— _RecurringEventState.build has cyclomatic complexity 29 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
PqSigningChain.walkFrom (cyclomatic 29) packages/at_client/lib/src/crypto/nskey/pq_signing_chain.dart:349— PqSigningChain.walkFrom has cyclomatic complexity 29 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Event.fromJson (cyclomatic 28) packages/at_events_flutter/lib/models/event_notification.dart:140— Event.fromJson has cyclomatic complexity 28 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
AtLocationNotificationListener._notificationCallback (cyclomatic 28) packages/at_location_flutter/lib/service/at_location_notification_listener.dart:78— AtLocationNotificationListener._notificationCallback has cyclomatic complexity 28 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
PairwiseSecretSharing._handleRequestPayload (cyclomatic 27) packages/at_client/lib/src/secret_sharing/pairwise_secret_sharing.dart:875— PairwiseSecretSharing._handleRequestPayload has cyclomatic complexity 27 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
KeyPackageMinting.reconcileKeyPackage (cyclomatic 26) packages/at_client/lib/src/secret_sharing/key_package_minting.dart:92— KeyPackageMinting.reconcileKeyPackage has cyclomatic complexity 26 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
SyncServiceImpl.setMetadataFromCommitEntry (cyclomatic 26) packages/at_client/lib/src/service/sync_service_impl.dart:1485— SyncServiceImpl.setMetadataFromCommitEntry has cyclomatic complexity 26 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
SigningKeyMinting.reconcileSigningKeys (cyclomatic 26) packages/at_client/lib/src/signing/signing_key_minting.dart:58— SigningKeyMinting.reconcileSigningKeys has cyclomatic complexity 26 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
_ContactsScreenState.build (cyclomatic 25) packages/at_contacts_flutter/lib/screens/contacts_screen.dart:86— _ContactsScreenState.build has cyclomatic complexity 25 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
_EventsCollapsedContentState.build (cyclomatic 25) packages/at_events_flutter/lib/screens/map_screen/events_collapsed_content.dart:45— _EventsCollapsedContentState.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.
_EventNotificationDialogState.build (cyclomatic 25) packages/at_events_flutter/lib/screens/notification_dialog/event_notification_dialog.dart:108— _EventNotificationDialogState.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.
_DesktopContactsScreenState.build (cyclomatic 24) packages/at_contacts_flutter/lib/desktop_screens/desktop_contacts_screen.dart:65— _DesktopContactsScreenState.build has cyclomatic complexity 24 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
_GroupContactViewState.build (cyclomatic 23) packages/at_contacts_group_flutter/lib/screens/group_contact_view/group_contact_view.dart:101— _GroupContactViewState.build has cyclomatic complexity 23 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
AtCollection._cleanupOrphansFromRoot (cyclomatic 23) packages/at_client/lib/src/collections/collections.dart:2127— AtCollection._cleanupOrphansFromRoot has cyclomatic complexity 23 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
CkManager.ensureCurrent (cyclomatic 23) packages/at_client/lib/src/crypto/nskey/ck_manager.dart:121— CkManager.ensureCurrent has cyclomatic complexity 23 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Metadata.toAtProtocolFragment (cyclomatic 23) packages/at_commons/lib/src/keystore/at_key.dart:543— Metadata.toAtProtocolFragment has cyclomatic complexity 23 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
_AtLocationFlutterPluginState.build (cyclomatic 22) REDACTED:157— _AtLocationFlutterPluginState.build has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
_CustomListTileState.build (cyclomatic 22) packages/at_contacts_flutter/lib/widgets/custom_list_tile.dart:47— _CustomListTileState.build has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
_OneDayEventState.build (cyclomatic 21) packages/at_events_flutter/lib/screens/one_day_event.dart:35— _OneDayEventState.build has cyclomatic complexity 21 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
EnrollmentHandshake._waitForPkamAuthSuccess (cyclomatic 21) packages/at_auth/lib/src/enroll/enrollment_handshake.dart:250— EnrollmentHandshake._waitForPkamAuthSuccess has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
PublishedNskeyKeyRing._publishedAt (cyclomatic 21) packages/at_client/lib/src/crypto/nskey/published_nskey_key_ring.dart:1104— PublishedNskeyKeyRing._publishedAt has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
EventNotificationModel.fromJson (cyclomatic 20) packages/at_events_flutter/lib/models/event_notification.dart:23— EventNotificationModel.fromJson 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.
AtCollection._getItemsAsStreamInternal (cyclomatic 20) packages/at_client/lib/src/collections/collections.dart:1411— AtCollection._getItemsAsStreamInternal 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.
AtLookupImpl.executeVerb (cyclomatic 20) packages/at_lookup/lib/src/at_lookup_impl.dart:205— AtLookupImpl.executeVerb has cyclomatic complexity 20 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
log_volume.sync (cyclomatic 20) docs/projects/pq/tools/log_volume.py:115— log_volume.sync 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.
_GroupViewState.build (cyclomatic 19) packages/at_contacts_group_flutter/lib/screens/group_view/group_view.dart:52— _GroupViewState.build has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
AtClientImpl._putInternal (cyclomatic 19) packages/at_client/lib/src/client/at_client_impl.dart:1861— AtClientImpl._putInternal 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.
CkManager._collectUnused (cyclomatic 19) packages/at_client/lib/src/crypto/nskey/ck_manager.dart:466— CkManager._collectUnused has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
SecondaryUrlFinder._findSecondary (cyclomatic 19) packages/at_lookup/lib/src/io/cacheable_secondary_address_finder.dart:224— SecondaryUrlFinder._findSecondary has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
AtTelemetryLogsCodec._decodeValue (cyclomatic 19) packages/at_telemetry/lib/src/codecs/at_telemetry_logs_codec.dart:255— AtTelemetryLogsCodec._decodeValue has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
_FollowersState.build (cyclomatic 19) packages/at_follows_flutter/lib/widgets/followers.dart:47— _FollowersState.build has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
_OverlappingContactsState.build (cyclomatic 18) packages/at_events_flutter/lib/common_components/overlapping_contacts.dart:23— _OverlappingContactsState.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.
_MarkerClusterLayerState._buildLayer (cyclomatic 18) packages/at_location_flutter/lib/map_content/flutter_map_marker_cluster/src/marker_cluster_layer.dart:440— _MarkerClusterLayerState._buildLayer has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
_GroupContactViewState.getContactsForAlphabets (cyclomatic 18) packages/at_contacts_group_flutter/lib/screens/group_contact_view/group_contact_view.dart:618— _GroupContactViewState.getContactsForAlphabets has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
AtEventNotificationListener._notificationCallback (cyclomatic 18) packages/at_events_flutter/lib/services/at_event_notification_listener.dart:66— AtEventNotificationListener._notificationCallback 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.
ConnectionsService.getAtsignsList (cyclomatic 18) packages/at_follows_flutter/lib/services/connections_service.dart:46— ConnectionsService.getAtsignsList has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
AtKeysAssurance.validateMapUpdate (cyclomatic 18) packages/at_auth/lib/src/keys/serialization/assurance.dart:267— AtKeysAssurance.validateMapUpdate has cyclomatic complexity 18 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
UpdateVerbBuilder.getBuilder (cyclomatic 18) packages/at_commons/lib/src/verb/update_verb_builder.dart:96— UpdateVerbBuilder.getBuilder 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.
EnrollmentSubmitter._handleSelfEnrollmentRequest (cyclomatic 17) packages/at_auth/lib/src/enroll/enrollment_submitter.dart:418— EnrollmentSubmitter._handleSelfEnrollmentRequest has cyclomatic complexity 17 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
NskeySeeding.requestMissingPrivates (cyclomatic 17) packages/at_client/lib/src/crypto/nskey/nskey_seeding.dart:525— NskeySeeding.requestMissingPrivates has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
SymmetricAesGcmProvider._resolveFromConveyance (cyclomatic 17) packages/at_client/lib/src/crypto/nskey/symmetric_aes_gcm_provider.dart:294— SymmetricAesGcmProvider._resolveFromConveyance has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
SyncServiceImpl._setConflictInfo (cyclomatic 17) packages/at_client/lib/src/service/sync_service_impl.dart:1213— SyncServiceImpl._setConflictInfo has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
_NewGroupState.createGroup (cyclomatic 16) packages/at_contacts_group_flutter/lib/screens/new_group/new_group.dart:65— _NewGroupState.createGroup has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
_SelectLocationState.build (cyclomatic 16) packages/at_events_flutter/lib/screens/select_location.dart:52— _SelectLocationState.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.
AtCollection.updateSharedWith (cyclomatic 16) packages/at_client/lib/src/collections/collections.dart:1079— AtCollection.updateSharedWith has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This is NOT this file's highest cyclomatic complexity: CmpPredicate.evaluate (cyclomatic 20) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded method is counted neither in this dimension's figures nor in its score.
AtCollection._put (cyclomatic 16) packages/at_client/lib/src/collections/collections.dart:3195— AtCollection._put has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This is NOT this file's highest cyclomatic complexity: CmpPredicate.evaluate (cyclomatic 20) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded method is counted neither in this dimension's figures nor in its score.
NskeySeeding.seed (cyclomatic 16) packages/at_client/lib/src/crypto/nskey/nskey_seeding.dart:114— NskeySeeding.seed has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
NskeySeeding.rotateIfRevoked (cyclomatic 16) packages/at_client/lib/src/crypto/nskey/nskey_seeding.dart:395— NskeySeeding.rotateIfRevoked has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
PqSigningChain.voucher (cyclomatic 16) packages/at_client/lib/src/crypto/nskey/pq_signing_chain.dart:539— PqSigningChain.voucher has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
AtKey.toString (cyclomatic 16) packages/at_commons/lib/src/keystore/at_key.dart:118— AtKey.toString 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.
AtContactsImpl.getGroup (cyclomatic 16) packages/at_contact/lib/src/at_contacts_impl.dart:355— AtContactsImpl.getGroup has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
SyncServiceImpl._pushFromSyncQueue (cognitive 82) packages/at_client/lib/src/service/sync_service_impl.dart:674— SyncServiceImpl._pushFromSyncQueue has cognitive complexity 82 (threshold 15). Drivers by points: if/else 14 (45 pts), error handling 5 (13 pts), ternaries 3 (12 pts), boolean chains 7, loops 3 (5 pts) (nesting depth added 50). 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.
_AtLocationFlutterPluginState.build (cognitive 59) REDACTED:157— _AtLocationFlutterPluginState.build has cognitive complexity 59 (threshold 15). Drivers by points: if/else 10 (27 pts), ternaries 6 (18 pts), loops 2 (6 pts), boolean chains 5, error handling 1 (3 pts) (nesting depth added 35). 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.
AtCollection._cleanupOrphansFromRoot (cognitive 58) packages/at_client/lib/src/collections/collections.dart:2127— AtCollection._cleanupOrphansFromRoot has cognitive complexity 58 (threshold 15). Drivers by points: if/else 10 (29 pts), error handling 4 (10 pts), ternaries 3 (10 pts), loops 5 (9 pts) (nesting depth added 36). 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.
Event.fromJson (cognitive 57) packages/at_events_flutter/lib/models/event_notification.dart:140— Event.fromJson has cognitive complexity 57 (threshold 15). Drivers by points: ternaries 21 (49 pts), if/else 4, match/switch 2 (4 pts) (nesting depth added 30). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PqSigningChain.walkFrom (cognitive 57) packages/at_client/lib/src/crypto/nskey/pq_signing_chain.dart:349— PqSigningChain.walkFrom has cognitive complexity 57 (threshold 15). Drivers by points: if/else 15 (33 pts), error handling 5 (11 pts), ternaries 3 (8 pts), boolean chains 4, loops 1 (nesting depth added 29). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
_ContactsScreenState.build (cognitive 54) packages/at_contacts_flutter/lib/screens/contacts_screen.dart:86— _ContactsScreenState.build has cognitive complexity 54 (threshold 15). Drivers by points: if/else 16 (35 pts), loops 3 (11 pts), ternaries 6, boolean chains 2 (nesting depth added 27). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
_GroupListState.build (cognitive 52) packages/at_contacts_group_flutter/lib/screens/list/group_list.dart:63— _GroupListState.build has cognitive complexity 52 (threshold 15). Drivers by points: ternaries 9 (37 pts), if/else 9 (15 pts) (nesting depth added 34). 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.
AtCollection._getItemsAsStreamInternal (cognitive 51) packages/at_client/lib/src/collections/collections.dart:1411— AtCollection._getItemsAsStreamInternal has cognitive complexity 51 (threshold 15). Drivers by points: if/else 11 (40 pts), error handling 3 (6 pts), boolean chains 4, loops 1 (nesting depth added 32). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
_CreateEventState.build (cognitive 50) packages/at_events_flutter/lib/screens/create_event.dart:73— _CreateEventState.build has cognitive complexity 50 (threshold 15). Drivers by points: ternaries 18 (34 pts), boolean chains 11, if/else 4 (5 pts) (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SyncServiceImpl.setMetadataFromCommitEntry (cognitive 50) packages/at_client/lib/src/service/sync_service_impl.dart:1485— SyncServiceImpl.setMetadataFromCommitEntry has cognitive complexity 50 (threshold 15). Drivers by points: if/else 20 (39 pts), ternaries 3 (9 pts), boolean chains 2 (nesting depth added 25). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
NotificationServiceImpl.handleNotificationReceipt (cognitive 48) packages/at_client/lib/src/service/notification_service_impl.dart:659— NotificationServiceImpl.handleNotificationReceipt has cognitive complexity 48 (threshold 15). Drivers by points: if/else 10 (30 pts), error handling 4 (13 pts), loops 2 (5 pts) (nesting depth added 32). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
_NewGroupState.createGroup (cognitive 47) packages/at_contacts_group_flutter/lib/screens/new_group/new_group.dart:65— _NewGroupState.createGroup has cognitive complexity 47 (threshold 15). Drivers by points: ternaries 8 (28 pts), if/else 11 (19 pts) (nesting depth added 28). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
_GroupViewState.build (cognitive 45) packages/at_contacts_group_flutter/lib/screens/group_view/group_view.dart:52— _GroupViewState.build has cognitive complexity 45 (threshold 15). Drivers by points: if/else 25 (38 pts), ternaries 3 (6 pts), boolean chains 1 (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AtLocationNotificationListener._notificationCallback (cognitive 44) packages/at_location_flutter/lib/service/at_location_notification_listener.dart:78— AtLocationNotificationListener._notificationCallback has cognitive complexity 44 (threshold 15). Drivers by points: if/else 23 (37 pts), boolean chains 7 (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Query.watch (cognitive 44) packages/at_client/lib/src/collections/collections.dart:4076— Query.watch has cognitive complexity 44 (threshold 15). Drivers by points: if/else 22 (29 pts), boolean chains 7, loops 3, ternaries 1 (3 pts), error handling 2 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
EnrollmentHandshake._waitForPkamAuthSuccess (cognitive 43) packages/at_auth/lib/src/enroll/enrollment_handshake.dart:250— EnrollmentHandshake._waitForPkamAuthSuccess has cognitive complexity 43 (threshold 15). Drivers by points: if/else 16 (34 pts), error handling 3 (6 pts), boolean chains 2, loops 1 (nesting depth added 21). 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.
NskeySeeding.requestMissingPrivates (cognitive 43) packages/at_client/lib/src/crypto/nskey/nskey_seeding.dart:525— NskeySeeding.requestMissingPrivates has cognitive complexity 43 (threshold 15). Drivers by points: if/else 9 (29 pts), loops 4 (10 pts), boolean chains 2, error handling 1 (2 pts) (nesting depth added 27). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
_DesktopContactsScreenState.build (cognitive 40) packages/at_contacts_flutter/lib/desktop_screens/desktop_contacts_screen.dart:65— _DesktopContactsScreenState.build has cognitive complexity 40 (threshold 15). Drivers by points: if/else 16 (28 pts), boolean chains 6, ternaries 6 (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.
PairwiseSecretSharing._handleRequestPayload (cognitive 37) packages/at_client/lib/src/secret_sharing/pairwise_secret_sharing.dart:875— PairwiseSecretSharing._handleRequestPayload has cognitive complexity 37 (threshold 15). Drivers by points: if/else 15 (23 pts), boolean chains 6, ternaries 3 (6 pts), loops 2 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
_GroupContactViewState.build (cognitive 36) packages/at_contacts_group_flutter/lib/screens/group_contact_view/group_contact_view.dart:101— _GroupContactViewState.build has cognitive complexity 36 (threshold 15). Drivers by points: if/else 14 (25 pts), ternaries 10, 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.
ChatService.interleave (cognitive 36) packages/at_chat_flutter/lib/services/chat_service.dart:172— ChatService.interleave has cognitive complexity 36 (threshold 15). Drivers by points: if/else 11 (28 pts), loops 3 (7 pts), boolean chains 1 (nesting depth added 21). 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.
SecondaryUrlFinder._findSecondary (cognitive 36) packages/at_lookup/lib/src/io/cacheable_secondary_address_finder.dart:224— SecondaryUrlFinder._findSecondary has cognitive complexity 36 (threshold 15). Drivers by points: if/else 13 (29 pts), error handling 3 (4 pts), loops 1 (2 pts), boolean chains 1 (nesting depth added 18). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
_FollowersState.build (cognitive 36) packages/at_follows_flutter/lib/widgets/followers.dart:47— _FollowersState.build has cognitive complexity 36 (threshold 15). Drivers by points: if/else 12 (20 pts), ternaries 7 (15 pts), boolean chains 1 (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
EventKeyStreamService.updateLocationDataForExistingEvent (cognitive 35) packages/at_events_flutter/lib/services/event_key_stream_service.dart:257— EventKeyStreamService.updateLocationDataForExistingEvent has cognitive complexity 35 (threshold 15). Drivers by points: if/else 10 (31 pts), loops 2 (3 pts), boolean chains 1 (nesting depth added 22). 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.
CkManager.ensureCurrent (cognitive 35) packages/at_client/lib/src/crypto/nskey/ck_manager.dart:121— CkManager.ensureCurrent has cognitive complexity 35 (threshold 15). Drivers by points: if/else 14 (24 pts), boolean chains 6, ternaries 3 (5 pts) (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
_CollapsedContentState.build (cognitive 34) packages/at_location_flutter/lib/common_components/collapsed_content.dart:65— _CollapsedContentState.build has cognitive complexity 34 (threshold 15). Drivers by points: ternaries 17, if/else 11 (14 pts), error handling 2, boolean chains 1 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, 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.
log_volume.sync (cognitive 34) docs/projects/pq/tools/log_volume.py:115— log_volume.sync has cognitive complexity 34 (threshold 15). Drivers by points: if/else 13 (24 pts), loops 4 (5 pts), ternaries 2 (3 pts), boolean chains 2 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
_MarkerClusterLayerState._buildLayer (cognitive 33) packages/at_location_flutter/lib/map_content/flutter_map_marker_cluster/src/marker_cluster_layer.dart:440— _MarkerClusterLayerState._buildLayer has cognitive complexity 33 (threshold 15). Drivers by points: if/else 15 (27 pts), boolean chains 6 (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.
AtKeysFileLock._acquire (cognitive 33) packages/at_auth/lib/src/keys/io/file_lock.dart:92— AtKeysFileLock._acquire has cognitive complexity 33 (threshold 15). Drivers by points: if/else 7 (15 pts), error handling 4 (14 pts), ternaries 1 (3 pts), loops 1 (nesting depth added 20). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
KeyPackageMinting.reconcileKeyPackage (cognitive 33) packages/at_client/lib/src/secret_sharing/key_package_minting.dart:92— KeyPackageMinting.reconcileKeyPackage has cognitive complexity 33 (threshold 15). Drivers by points: if/else 15 (21 pts), loops 9, boolean chains 3 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
_CustomListTileState.build (cognitive 33) packages/at_contacts_flutter/lib/widgets/custom_list_tile.dart:47— _CustomListTileState.build has cognitive complexity 33 (threshold 15). Drivers by points: if/else 13 (19 pts), ternaries 6 (7 pts), boolean chains 4, error handling 1 (2 pts), loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
UpdateVerbBuilder.== (cognitive 32) packages/at_commons/lib/src/verb/update_verb_builder.dart:218— UpdateVerbBuilder.== has cognitive complexity 32 (threshold 15). Drivers by points: boolean chains 32. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
AesGcm256FfiAlgo.encrypt (cognitive 31) packages/at_chops/lib/src/algorithm/encryption/aes_gcm_ffi_algo.dart:73— AesGcm256FfiAlgo.encrypt has cognitive complexity 31 (threshold 15). Drivers by points: if/else 10 (29 pts), ternaries 1 (2 pts) (nesting depth added 20). 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.
AesGcm256FfiAlgo.decrypt (cognitive 31) packages/at_chops/lib/src/algorithm/encryption/aes_gcm_ffi_algo.dart:188— AesGcm256FfiAlgo.decrypt has cognitive complexity 31 (threshold 15). Drivers by points: if/else 11 (29 pts), ternaries 1 (2 pts) (nesting depth added 19). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
NskeySeeding.seed (cognitive 31) packages/at_client/lib/src/crypto/nskey/nskey_seeding.dart:114— NskeySeeding.seed has cognitive complexity 31 (threshold 15). Drivers by points: if/else 10 (24 pts), error handling 3 (5 pts), loops 2 (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PqSigningChain.linkKeysOf (cognitive 31) packages/at_client/lib/src/crypto/nskey/pq_signing_chain.dart:630— PqSigningChain.linkKeysOf has cognitive complexity 31 (threshold 15). Drivers by points: if/else 8 (21 pts), loops 2 (3 pts), ternaries 1 (3 pts), boolean chains 2, error handling 1 (2 pts) (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SigningKeyMinting.reconcileSigningKeys (cognitive 31) packages/at_client/lib/src/signing/signing_key_minting.dart:58— SigningKeyMinting.reconcileSigningKeys has cognitive complexity 31 (threshold 15). Drivers by points: if/else 11 (16 pts), loops 7 (8 pts), boolean chains 7 (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.
_GroupContactViewState.getContactsForAlphabets (cognitive 30) packages/at_contacts_group_flutter/lib/screens/group_contact_view/group_contact_view.dart:618— _GroupContactViewState.getContactsForAlphabets has cognitive complexity 30 (threshold 15). Drivers by points: if/else 6 (14 pts), boolean chains 8, loops 4 (8 pts) (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AtCollection._put (cognitive 30) packages/at_client/lib/src/collections/collections.dart:3195— AtCollection._put has cognitive complexity 30 (threshold 15). Drivers by points: if/else 8 (18 pts), error handling 3 (6 pts), loops 3 (5 pts), boolean chains 1 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CkManager._collectUnused (cognitive 30) packages/at_client/lib/src/crypto/nskey/ck_manager.dart:466— CkManager._collectUnused has cognitive complexity 30 (threshold 15). Drivers by points: if/else 11 (22 pts), boolean chains 5, ternaries 1 (2 pts), loops 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PublishedNskeyKeyRing._publishedAt (cognitive 30) packages/at_client/lib/src/crypto/nskey/published_nskey_key_ring.dart:1104— PublishedNskeyKeyRing._publishedAt has cognitive complexity 30 (threshold 15). Drivers by points: ternaries 7 (15 pts), error handling 3 (4 pts), if/else 3 (4 pts), loops 4, boolean chains 3 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Metadata.== (cognitive 30) packages/at_commons/lib/src/keystore/at_key.dart:786— Metadata.== has cognitive complexity 30 (threshold 15). Drivers by points: boolean chains 30. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
LocalSecondary._update (cognitive 29) packages/at_client/lib/src/client/local_secondary.dart:384— LocalSecondary._update has cognitive complexity 29 (threshold 15). Drivers by points: if/else 12 (22 pts), error handling 2 (3 pts), match/switch 1 (2 pts), ternaries 1 (2 pts) (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
_DesktopNewGroupState.createGroup (cognitive 28) packages/at_contacts_group_flutter/lib/desktop_screens/desktop_new_group.dart:50— _DesktopNewGroupState.createGroup has cognitive complexity 28 (threshold 15). Drivers by points: if/else 13 (28 pts) (nesting depth added 15). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
_EventsCollapsedContentState.build (cognitive 28) packages/at_events_flutter/lib/screens/map_screen/events_collapsed_content.dart:45— _EventsCollapsedContentState.build has cognitive complexity 28 (threshold 15). Drivers by points: ternaries 12 (14 pts), if/else 7 (8 pts), boolean chains 5, error handling 1 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, 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.
_RecurringEventState.build (cognitive 28) packages/at_events_flutter/lib/screens/recurring_event.dart:48— _RecurringEventState.build has cognitive complexity 28 (threshold 15). Drivers by points: ternaries 16, if/else 11, match/switch 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.
NotificationServiceImpl._migrateLegacyLastReceivedNotificationKeys (cognitive 27) packages/at_client/lib/src/service/notification_service_impl.dart:463— NotificationServiceImpl._migrateLegacyLastReceivedNotificationKeys has cognitive complexity 27 (threshold 15). Drivers by points: error handling 6 (14 pts), if/else 5 (12 pts), loops 1 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AtTelemetryLogsCodec._decodeValue (cognitive 27) packages/at_telemetry/lib/src/codecs/at_telemetry_logs_codec.dart:255— AtTelemetryLogsCodec._decodeValue has cognitive complexity 27 (threshold 15). Drivers by points: if/else 14 (21 pts), boolean chains 2, error handling 1 (2 pts), loops 1 (2 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
_EventNotificationDialogState.build (cognitive 26) packages/at_events_flutter/lib/screens/notification_dialog/event_notification_dialog.dart:108— _EventNotificationDialogState.build has cognitive complexity 26 (threshold 15). Drivers by points: ternaries 20, if/else 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.
ContactService.addAtSign (cognitive 26) packages/at_contacts_flutter/lib/services/contact_service.dart:375— ContactService.addAtSign has cognitive complexity 26 (threshold 15). Drivers by points: if/else 10 (20 pts), loops 1 (3 pts), boolean chains 2, error handling 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ConnectionsService.getAtsignsList (cognitive 26) packages/at_follows_flutter/lib/services/connections_service.dart:46— ConnectionsService.getAtsignsList has cognitive complexity 26 (threshold 15). Drivers by points: if/else 10 (17 pts), boolean chains 5, loops 1 (2 pts), ternaries 1 (2 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AtRpc.sendResponse (cognitive 26) packages/at_client/lib/src/rpc/at_rpc.dart:693— AtRpc.sendResponse has cognitive complexity 26 (threshold 15). Drivers by points: if/else 7 (20 pts), boolean chains 3, error handling 1 (2 pts), loops 1 (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SyncServiceImpl._setConflictInfo (cognitive 26) packages/at_client/lib/src/service/sync_service_impl.dart:1213— SyncServiceImpl._setConflictInfo has cognitive complexity 26 (threshold 15). Drivers by points: if/else 7 (15 pts), error handling 4 (6 pts), boolean chains 5 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AtKey.fromString (cognitive 26) packages/at_commons/lib/src/keystore/at_key.dart:262— AtKey.fromString has cognitive complexity 26 (threshold 15). Drivers by points: if/else 18 (24 pts), boolean chains 2 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
_DesktopGroupInitialScreenState.build (cognitive 25) packages/at_contacts_group_flutter/lib/desktop_screens/desktop_group_initial_screen.dart:43— _DesktopGroupInitialScreenState.build has cognitive complexity 25 (threshold 15). Drivers by points: if/else 10 (19 pts), ternaries 1 (5 pts), boolean chains 1 (nesting depth added 13). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
GroupService.getAllGroupsDetails (cognitive 25) packages/at_contacts_group_flutter/lib/services/group_service.dart:165— GroupService.getAllGroupsDetails has cognitive complexity 25 (threshold 15). Drivers by points: if/else 7 (16 pts), error handling 2 (4 pts), loops 2 (4 pts), boolean chains 1 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SymmetricAesGcmProvider._resolveFromConveyance (cognitive 25) packages/at_client/lib/src/crypto/nskey/symmetric_aes_gcm_provider.dart:294— SymmetricAesGcmProvider._resolveFromConveyance has cognitive complexity 25 (threshold 15). Drivers by points: if/else 7 (14 pts), error handling 6, loops 1 (2 pts), ternaries 1 (2 pts), boolean chains 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
EventNotificationModel.fromJson (cognitive 24) packages/at_events_flutter/lib/models/event_notification.dart:23— EventNotificationModel.fromJson has cognitive complexity 24 (threshold 15). Drivers by points: ternaries 10 (15 pts), boolean chains 6, if/else 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.
SharingLocationService.sendShareLocationEvent (cognitive 24) packages/at_location_flutter/lib/service/sharing_location_service.dart:78— SharingLocationService.sendShareLocationEvent has cognitive complexity 24 (threshold 15). Drivers by points: if/else 8 (16 pts), ternaries 2 (6 pts), boolean chains 1, error handling 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
GroupService.removeGroupContact (cognitive 24) packages/at_contacts_group_flutter/lib/services/group_service.dart:405— GroupService.removeGroupContact has cognitive complexity 24 (threshold 15). Drivers by points: if/else 7 (14 pts), loops 2 (5 pts), boolean chains 4, error handling 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AtClientImpl._onAvailableFire (cognitive 24) packages/at_client/lib/src/client/at_client_impl.dart:1236— AtClientImpl._onAvailableFire has cognitive complexity 24 (threshold 15). Drivers by points: error handling 6 (16 pts), if/else 2 (6 pts), loops 1 (2 pts) (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AtLookupImpl._reconnectNotifications (cognitive 24) packages/at_lookup/lib/src/at_lookup_impl.dart:770— AtLookupImpl._reconnectNotifications has cognitive complexity 24 (threshold 15). Drivers by points: if/else 5 (17 pts), error handling 1 (3 pts), boolean chains 2, loops 1 (2 pts) (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DistanceGrid.getNearObject (cognitive 23) packages/at_location_flutter/lib/map_content/flutter_map_marker_cluster/src/core/distance_grid.dart:70— DistanceGrid.getNearObject has cognitive complexity 23 (threshold 15). Drivers by points: if/else 3 (12 pts), loops 3 (9 pts), boolean chains 2 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
GroupService.addGroupContact (cognitive 23) packages/at_contacts_group_flutter/lib/services/group_service.dart:448— GroupService.addGroupContact has cognitive complexity 23 (threshold 15). Drivers by points: if/else 8 (16 pts), loops 2 (5 pts), boolean chains 1, error handling 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ConnectionsService._getAtsignData (cognitive 23) packages/at_follows_flutter/lib/services/connections_service.dart:341— ConnectionsService._getAtsignData has cognitive complexity 23 (threshold 15). Drivers by points: if/else 4 (17 pts), error handling 2 (4 pts), loops 1 (2 pts) (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PendingEnrollment.awaitApproval (cognitive 23) packages/at_client/lib/src/lifecycle/pending_enrollment.dart:90— PendingEnrollment.awaitApproval has cognitive complexity 23 (threshold 15). Drivers by points: if/else 9 (12 pts), ternaries 4 (7 pts), error handling 2 (4 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AtContactsImpl.get (cognitive 23) packages/at_contact/lib/src/at_contacts_impl.dart:56— AtContactsImpl.get has cognitive complexity 23 (threshold 15). Drivers by points: if/else 7 (11 pts), error handling 3 (7 pts), boolean chains 3, ternaries 1 (2 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AtTelemetryLogsCodec.decode (cognitive 23) packages/at_telemetry/lib/src/codecs/at_telemetry_logs_codec.dart:64— AtTelemetryLogsCodec.decode has cognitive complexity 23 (threshold 15). Drivers by points: if/else 3 (7 pts), loops 3 (6 pts), ternaries 2 (5 pts), error handling 2 (4 pts), boolean chains 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
_DesktopGroupDetailState.build (cognitive 22) packages/at_contacts_group_flutter/lib/desktop_screens/desktop_group_detail.dart:52— _DesktopGroupDetailState.build has cognitive complexity 22 (threshold 15). Drivers by points: if/else 8 (15 pts), ternaries 7 (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.
_OneDayEventState.build (cognitive 22) packages/at_events_flutter/lib/screens/one_day_event.dart:35— _OneDayEventState.build has cognitive complexity 22 (threshold 15). Drivers by points: if/else 9 (11 pts), ternaries 11 (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.
HomeScreenService.onLocationModelTap (cognitive 22) packages/at_location_flutter/lib/service/home_screen_service.dart:20— HomeScreenService.onLocationModelTap has cognitive complexity 22 (threshold 15). Drivers by points: ternaries 9 (18 pts), if/else 3 (4 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AtClientImpl._putInternal (cognitive 22) packages/at_client/lib/src/client/at_client_impl.dart:1861— AtClientImpl._putInternal has cognitive complexity 22 (threshold 15). Drivers by points: if/else 10 (12 pts), boolean chains 6, error handling 2 (4 pts) (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.
AtCollection._delete (cognitive 22) packages/at_client/lib/src/collections/collections.dart:3328— AtCollection._delete has cognitive complexity 22 (threshold 15). Drivers by points: if/else 6 (13 pts), error handling 2 (5 pts), loops 2 (3 pts), boolean chains 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CkManager._ownKey (cognitive 22) packages/at_client/lib/src/crypto/nskey/ck_manager.dart:718— CkManager._ownKey has cognitive complexity 22 (threshold 15). Drivers by points: if/else 8 (19 pts), ternaries 1 (2 pts), boolean chains 1 (nesting depth added 12). 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.
NskeyRotation.revokeEnrollmentAndRotate (cognitive 22) packages/at_client/lib/src/crypto/nskey/nskey_rotation.dart:154— NskeyRotation.revokeEnrollmentAndRotate has cognitive complexity 22 (threshold 15). Drivers by points: if/else 9 (14 pts), ternaries 2 (4 pts), error handling 1 (2 pts), boolean chains 1, loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Metadata.toAtProtocolFragment (cognitive 22) packages/at_commons/lib/src/keystore/at_key.dart:543— Metadata.toAtProtocolFragment has cognitive complexity 22 (threshold 15). Drivers by points: if/else 22. 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.
AtContactsImpl.getGroup (cognitive 22) packages/at_contact/lib/src/at_contacts_impl.dart:355— AtContactsImpl.getGroup has cognitive complexity 22 (threshold 15). Drivers by points: if/else 8 (12 pts), boolean chains 4, error handling 2 (4 pts), ternaries 1 (2 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SecondaryUrlFinder.findSecondaryUrl (cognitive 22) packages/at_lookup/lib/src/io/cacheable_secondary_address_finder.dart:176— SecondaryUrlFinder.findSecondaryUrl has cognitive complexity 22 (threshold 15). Drivers by points: if/else 6 (16 pts), ternaries 1 (3 pts), error handling 1 (2 pts), loops 1 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
_CircularContactsState.build (cognitive 22) packages/at_contacts_group_flutter/lib/widgets/circular_contacts.dart:96— _CircularContactsState.build has cognitive complexity 22 (threshold 15). Drivers by points: if/else 7 (13 pts), ternaries 6, boolean chains 3 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
_CustomListTileState.build (cognitive 22) packages/at_contacts_group_flutter/lib/widgets/custom_list_tile.dart:103— _CustomListTileState.build has cognitive complexity 22 (threshold 15). Drivers by points: if/else 7 (13 pts), ternaries 8, boolean chains 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
_TileLayerState._update (cognitive 21) packages/at_location_flutter/lib/map_content/flutter_map/src/layer/tile_layer.dart:860— _TileLayerState._update has cognitive complexity 21 (threshold 15). Drivers by points: if/else 7 (12 pts), loops 4 (5 pts), boolean chains 4 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
_GroupEditState._buildHeaderListMember (cognitive 21) packages/at_contacts_group_flutter/lib/screens/edit/group_edit.dart:321— _GroupEditState._buildHeaderListMember has cognitive complexity 21 (threshold 15). Drivers by points: if/else 12 (20 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.
ContactService.getContactDetails (cognitive 21) packages/at_contacts_flutter/lib/services/contact_service.dart:507— ContactService.getContactDetails has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (12 pts), error handling 4 (6 pts), boolean chains 2, ternaries 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
EventService.isEventTimeSlotOverlap (cognitive 21) packages/at_events_flutter/lib/services/event_services.dart:331— EventService.isEventTimeSlotOverlap has cognitive complexity 21 (threshold 15). Drivers by points: if/else 5 (17 pts), boolean chains 3, loops 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AtAuthImpl.validateAtServer (cognitive 21) packages/at_auth/lib/src/at_auth_impl.dart:399— AtAuthImpl.validateAtServer has cognitive complexity 21 (threshold 15). Drivers by points: if/else 4 (8 pts), ternaries 4 (7 pts), match/switch 1 (3 pts), error handling 1 (2 pts), loops 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AtCollection.updateSharedWith (cognitive 21) packages/at_client/lib/src/collections/collections.dart:1079— AtCollection.updateSharedWith has cognitive complexity 21 (threshold 15). Drivers by points: if/else 7 (11 pts), error handling 2 (4 pts), boolean chains 2, loops 2, ternaries 2 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PqSigningRoot.store (cognitive 21) packages/at_client/lib/src/crypto/nskey/pq_signing_root.dart:547— PqSigningRoot.store has cognitive complexity 21 (threshold 15). Drivers by points: if/else 6 (10 pts), loops 2 (4 pts), ternaries 2 (4 pts), boolean chains 2, error handling 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.
EnvelopeEnrollmentConveyance.sweepUnanchoredEnrollments (cognitive 21) packages/at_client/lib/src/service/envelope_enrollment_conveyance.dart:247— EnvelopeEnrollmentConveyance.sweepUnanchoredEnrollments has cognitive complexity 21 (threshold 15). Drivers by points: if/else 7 (15 pts), boolean chains 2, error handling 1 (2 pts), loops 2 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
GetResponseTransformer.transform (cognitive 21) packages/at_client/lib/src/transformer/response_transformer/get_response_transformer.dart:28— GetResponseTransformer.transform has cognitive complexity 21 (threshold 15). Drivers by points: if/else 12 (18 pts), error handling 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.
LatLngBounds.fromPoints (cognitive 20) packages/at_location_flutter/lib/map_content/flutter_map/src/geo/latlng_bounds.dart:15— LatLngBounds.fromPoints has cognitive complexity 20 (threshold 15). Drivers by points: if/else 5 (13 pts), boolean chains 5, loops 1 (2 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PolygonPainter._paintBorder (cognitive 20) packages/at_location_flutter/lib/map_content/flutter_map/src/layer/polygon_layer.dart:163— PolygonPainter._paintBorder has cognitive complexity 20 (threshold 15). Drivers by points: if/else 5 (10 pts), loops 2 (8 pts), boolean chains 2 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
GroupService.fetchGroupsAndContacts (cognitive 20) packages/at_contacts_group_flutter/lib/services/group_service.dart:325— GroupService.fetchGroupsAndContacts has cognitive complexity 20 (threshold 15). Drivers by points: if/else 5 (15 pts), loops 1 (3 pts), boolean chains 1, error handling 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AtEventNotificationListener._notificationCallback (cognitive 20) packages/at_events_flutter/lib/services/at_event_notification_listener.dart:66— AtEventNotificationListener._notificationCallback has cognitive complexity 20 (threshold 15). Drivers by points: if/else 10 (13 pts), boolean chains 7 (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.
Query.watchWithTree (cognitive 20) packages/at_client/lib/src/collections/collections.dart:3939— Query.watchWithTree has cognitive complexity 20 (threshold 15). Drivers by points: loops 7 (11 pts), if/else 5 (9 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.
NskeyProvider.encrypt (cognitive 20) packages/at_client/lib/src/crypto/nskey/nskey_provider.dart:156— NskeyProvider.encrypt has cognitive complexity 20 (threshold 15). Drivers by points: if/else 12 (19 pts), ternaries 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PairwiseSecretSharing.requestSecretsFromNamespace (cognitive 20) packages/at_client/lib/src/secret_sharing/pairwise_secret_sharing.dart:807— PairwiseSecretSharing.requestSecretsFromNamespace has cognitive complexity 20 (threshold 15). Drivers by points: if/else 4 (14 pts), error handling 1 (3 pts), boolean chains 2, loops 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PairwiseSecretSharing.shareAllSecretsWithEnrollment (cognitive 20) packages/at_client/lib/src/secret_sharing/pairwise_secret_sharing.dart:1301— PairwiseSecretSharing.shareAllSecretsWithEnrollment has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (16 pts), loops 3 (4 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
_EnrollmentRequestListState._fetchAndSubscribe (cognitive 20) packages/at_client_flutter/lib/src/widgets/authorisation/containers/enrollment_request_list.dart:63— _EnrollmentRequestListState._fetchAndSubscribe has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (16 pts), loops 1 (3 pts), error handling 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AtLookupImpl.executeVerb (cognitive 20) packages/at_lookup/lib/src/at_lookup_impl.dart:205— AtLookupImpl.executeVerb has cognitive complexity 20 (threshold 15). Drivers by points: if/else 16 (17 pts), error handling 3 (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.
KeyStreamService.mapUpdatedLocationDataToWidget (cognitive 19) packages/at_location_flutter/lib/service/key_stream_service.dart:226— KeyStreamService.mapUpdatedLocationDataToWidget has cognitive complexity 19 (threshold 15). Drivers by points: if/else 12 (17 pts), boolean chains 1, loops 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
LocationService.addDetails (cognitive 19) packages/at_location_flutter/lib/service/location_service.dart:259— LocationService.addDetails has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (15 pts), loops 1 (3 pts), error handling 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
EnrollmentSubmitter._handleSelfEnrollmentRequest (cognitive 19) packages/at_auth/lib/src/enroll/enrollment_submitter.dart:418— EnrollmentSubmitter._handleSelfEnrollmentRequest has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9, error handling 4 (6 pts), boolean chains 3, match/switch 1 (nesting depth added 2). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
AtClientImpl.create (cognitive 19) packages/at_client/lib/src/client/at_client_impl.dart:680— AtClientImpl.create has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (10 pts), ternaries 2 (4 pts), error handling 2 (3 pts), boolean chains 2 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AtClientImpl._settleEnrollmentIdentity (cognitive 19) packages/at_client/lib/src/client/at_client_impl.dart:2168— AtClientImpl._settleEnrollmentIdentity has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (11 pts), error handling 3 (4 pts), boolean chains 3, ternaries 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AtCollection.getDescendant (cognitive 19) packages/at_client/lib/src/collections/collections.dart:1713— AtCollection.getDescendant has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (15 pts), loops 2, ternaries 1 (2 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PqSigningChain.voucher (cognitive 19) packages/at_client/lib/src/crypto/nskey/pq_signing_chain.dart:539— PqSigningChain.voucher has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (11 pts), boolean chains 5, loops 2, ternaries 1 (nesting depth added 3). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
KeyPackageMinting._publishedPackageStale (cognitive 19) packages/at_client/lib/src/secret_sharing/key_package_minting.dart:242— KeyPackageMinting._publishedPackageStale has cognitive complexity 19 (threshold 15). Drivers by points: if/else 4 (9 pts), ternaries 2 (5 pts), boolean chains 2, match/switch 1 (2 pts), error handling 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.
NotificationServiceImpl.send (cognitive 19) packages/at_client/lib/src/service/notification_service_impl.dart:750— NotificationServiceImpl.send has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (11 pts), boolean chains 5, error handling 1 (2 pts), ternaries 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AtTelemetryLogsCodec._decodeLogRecord (cognitive 19) packages/at_telemetry/lib/src/codecs/at_telemetry_logs_codec.dart:158— AtTelemetryLogsCodec._decodeLogRecord has cognitive complexity 19 (threshold 15). Drivers by points: if/else 5 (7 pts), ternaries 3 (6 pts), boolean chains 5, error handling 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
_TileLayerState._handleMove (cognitive 18) packages/at_location_flutter/lib/map_content/flutter_map/src/layer/tile_layer.dart:812— _TileLayerState._handleMove has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (15 pts), boolean chains 3 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
_ConnectionsState.build (cognitive 18) packages/at_follows_flutter/lib/screens/connections.dart:79— _ConnectionsState.build has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (11 pts), boolean chains 4, ternaries 2, loops 1 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, 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.
KeyStreamService.checkForPendingLocations (cognitive 18) packages/at_location_flutter/lib/service/key_stream_service.dart:112— KeyStreamService.checkForPendingLocations has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (12 pts), boolean chains 6 (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.
AtKeys.toJson (cognitive 18) packages/at_auth/lib/src/keys/at_keys.dart:986— AtKeys.toJson has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (15 pts), loops 1 (2 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.
AtKeysAssurance.validateMapUpdate (cognitive 18) packages/at_auth/lib/src/keys/serialization/assurance.dart:267— AtKeysAssurance.validateMapUpdate has cognitive complexity 18 (threshold 15). Drivers by points: boolean chains 10, if/else 7 (8 pts) (nesting depth added 1). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
PqClientBootstrap.startup (cognitive 18) packages/at_client/lib/src/client/pq_client_bootstrap.dart:339— PqClientBootstrap.startup has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (13 pts), error handling 1 (3 pts), loops 1 (2 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
NskeySeeding.rotateIfRevoked (cognitive 18) packages/at_client/lib/src/crypto/nskey/nskey_seeding.dart:395— NskeySeeding.rotateIfRevoked has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (11 pts), boolean chains 3, error handling 3, ternaries 1 (nesting depth added 3). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
UpdateVerbBuilder.getBuilder (cognitive 18) packages/at_commons/lib/src/verb/update_verb_builder.dart:96— UpdateVerbBuilder.getBuilder has cognitive complexity 18 (threshold 15). Drivers by points: if/else 17, boolean chains 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.
_OverlappingContactsState.build (cognitive 17) packages/at_events_flutter/lib/common_components/overlapping_contacts.dart:23— _OverlappingContactsState.build has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 10, boolean chains 5, if/else 2. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
_TileLayerState._tileReady (cognitive 17) packages/at_location_flutter/lib/map_content/flutter_map/src/layer/tile_layer.dart:983— _TileLayerState._tileReady has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (11 pts), boolean chains 3, ternaries 2 (3 pts) (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
_SelectLocationState.build (cognitive 17) packages/at_events_flutter/lib/screens/select_location.dart:52— _SelectLocationState.build has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 9, if/else 8. 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.
MasterLocationService.getHybridModel (cognitive 17) packages/at_location_flutter/lib/service/master_location_service.dart:45— MasterLocationService.getHybridModel has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (11 pts), boolean chains 6 (nesting depth added 6). 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.
MlKem768FfiAlgo._generateKeyPairFromSeed (cognitive 17) packages/at_chops/lib/src/algorithm/encryption/ml_kem_768_ffi.dart:164— MlKem768FfiAlgo._generateKeyPairFromSeed has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (17 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
LocalSecondary._getEnrollmentDetails (cognitive 17) packages/at_client/lib/src/client/local_secondary.dart:1012— LocalSecondary._getEnrollmentDetails has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 4 (9 pts), if/else 4 (5 pts), error handling 2, boolean chains 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PqClientBootstrap._reconcileEnrollmentSnapshot (cognitive 17) packages/at_client/lib/src/client/pq_client_bootstrap.dart:736— PqClientBootstrap._reconcileEnrollmentSnapshot has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (13 pts), boolean chains 3, error handling 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PqSigningRoot.pushToFullyPrivileged (cognitive 17) packages/at_client/lib/src/crypto/nskey/pq_signing_root.dart:446— PqSigningRoot.pushToFullyPrivileged has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (10 pts), error handling 2 (4 pts), loops 1 (2 pts), boolean chains 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ApkamSignedAdvertisedKeys.verify (cognitive 17) packages/at_client/lib/src/crypto/nskey/published_nskey_key_ring.dart:111— ApkamSignedAdvertisedKeys.verify has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (13 pts), error handling 3, loops 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
EnvelopeEnrollmentConveyance.conveySecretsTo (cognitive 17) packages/at_client/lib/src/service/envelope_enrollment_conveyance.dart:98— EnvelopeEnrollmentConveyance.conveySecretsTo has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (12 pts), boolean chains 2, error handling 1 (2 pts), loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SigningKeyMinting._publishLinkAndRetire (cognitive 17) packages/at_client/lib/src/signing/signing_key_minting.dart:150— SigningKeyMinting._publishLinkAndRetire has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (9 pts), boolean chains 6, loops 2 (nesting depth added 3). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SigningKeyMinting._ownLinkState (cognitive 17) packages/at_client/lib/src/signing/signing_key_minting.dart:211— SigningKeyMinting._ownLinkState has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (11 pts), loops 2 (4 pts), boolean chains 1, error handling 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.
AtKey.toString (cognitive 17) packages/at_commons/lib/src/keystore/at_key.dart:118— AtKey.toString has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (11 pts), boolean chains 6 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
EventKeyStreamService.mapUpdatedEventDataToWidget (cognitive 16) packages/at_events_flutter/lib/services/event_key_stream_service.dart:201— EventKeyStreamService.mapUpdatedEventDataToWidget has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (14 pts), boolean chains 1, loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AtAuthImpl.onboard (cognitive 16) packages/at_auth/lib/src/at_auth_impl.dart:82— AtAuthImpl.onboard has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (9 pts), error handling 5 (7 pts) (nesting depth added 3). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
AtKeysAssurance._assertMaterialsPreserved (cognitive 16) packages/at_auth/lib/src/keys/serialization/assurance.dart:427— AtKeysAssurance._assertMaterialsPreserved has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (13 pts), loops 2, boolean chains 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MlKem768FfiAlgo._importPublicKey (cognitive 16) packages/at_chops/lib/src/algorithm/encryption/ml_kem_768_ffi.dart:334— MlKem768FfiAlgo._importPublicKey has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (16 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MlDsa65FfiAlgo.keyPairFromSeed (cognitive 16) packages/at_chops/lib/src/algorithm/signing/ml_dsa_65_ffi.dart:158— MlDsa65FfiAlgo.keyPairFromSeed has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (16 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AtCollection._cascadeFromParentDelete (cognitive 16) packages/at_client/lib/src/collections/collections.dart:2009— AtCollection._cascadeFromParentDelete has cognitive complexity 16 (threshold 15). Drivers by points: if/else 3 (8 pts), error handling 4 (7 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.
PairwiseSecretSharing.shareAllSecretsWith (cognitive 16) packages/at_client/lib/src/secret_sharing/pairwise_secret_sharing.dart:1180— PairwiseSecretSharing.shareAllSecretsWith has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (11 pts), boolean chains 2, error handling 1 (2 pts), loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
EnvelopeEnrollmentConveyance._linkKeysOf (cognitive 16) packages/at_client/lib/src/service/envelope_enrollment_conveyance.dart:200— EnvelopeEnrollmentConveyance._linkKeysOf has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (8 pts), ternaries 1 (3 pts), boolean chains 2, loops 1 (2 pts), error handling 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AtSyncQueue.adopt (cognitive 16) packages/at_client/lib/src/sync/at_sync_queue.dart:223— AtSyncQueue.adopt has cognitive complexity 16 (threshold 15). Drivers by points: if/else 3 (9 pts), error handling 2 (4 pts), loops 1 (2 pts), boolean chains 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AtContactsImpl._addToGroupList (cognitive 16) packages/at_contact/lib/src/at_contacts_impl.dart:532— AtContactsImpl._addToGroupList has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (6 pts), error handling 2 (4 pts), ternaries 2 (4 pts), boolean chains 2 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
log_volume.levels (cognitive 16) docs/projects/pq/tools/log_volume.py:224— log_volume.levels has cognitive complexity 16 (threshold 15). Drivers by points: if/else 3 (9 pts), loops 3 (6 pts), boolean chains 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D4 · Code Duplication· Near-duplicate member family (3 members, 34 shared lines) · ×1
Near-duplicate member family (3 members, 34 shared lines) packages/at_chat_flutter/lib/utils/colors.dart:12— packages/at_chat_flutter/lib/utils/colors.dart:12-75 | packages/at_contacts_flutter/lib/utils/colors.dart:25-88 | packages/at_location_flutter/lib/utils/constants/colors.dart:42-105 — These 3 members are variants of one another: a block of 34 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 3 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 3 times.
Near-duplicate member pair (193 shared lines) packages/at_client_flutter/lib/src/widgets/apkam_dialog.dart:392— packages/at_client_flutter/lib/src/widgets/apkam_dialog.dart:392-627 | packages/at_client_flutter/lib/src/widgets/registrar_cram_dialog.dart:162-371 — These two members are variants of one another: 193 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.
Near-duplicate member pair (97 shared lines) packages/at_events_flutter/lib/common_components/display_tile.dart:64— packages/at_events_flutter/lib/common_components/display_tile.dart:64-177 | packages/at_location_flutter/lib/common_components/display_tile.dart:66-180 — These two members are variants of one another: 97 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.
Near-duplicate member pair (63 shared lines) packages/at_follows_flutter/lib/widgets/custom_appbar.dart:25— packages/at_follows_flutter/lib/widgets/custom_appbar.dart:25-113 | packages/at_login_flutter/lib/widgets/custom_appbar.dart:23-110 — These two members are variants of one another: 63 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.
Near-duplicate member pair (59 shared lines) packages/at_contacts_group_flutter/lib/widgets/desktop_person_vertical_tile.dart:62— packages/at_contacts_group_flutter/lib/widgets/desktop_person_vertical_tile.dart:62-143 | packages/at_contacts_group_flutter/lib/widgets/person_vertical_tile.dart:68-146 — These two members are variants of one another: 59 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.
D4 · Code Duplication· Edited copy of a member (13 corresponding lines) · ×1
Edited copy of a member (13 corresponding lines) packages/at_location_flutter/lib/map_content/flutter_map/src/layer/polygon_layer.dart:134— packages/at_location_flutter/lib/map_content/flutter_map/src/layer/polygon_layer.dart:134-146 | packages/at_location_flutter/lib/map_content/flutter_map/src/layer/polyline_layer.dart:115-127 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Members sharing a duplicated core (5 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (5 members, 50+ identical tokens) packages/at_follows_flutter/lib/domain/connection_model.dart:68— packages/at_follows_flutter/lib/domain/connection_model.dart:68-84 | packages/at_follows_flutter/lib/domain/connection_model.dart:101-121 | packages/at_follows_flutter/lib/domain/connection_model.dart:123-142 | packages/at_login_flutter/lib/domain/at_login_provider.dart:63-79 | packages/at_login_flutter/lib/domain/at_login_provider.dart:96-115 — 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 (77 lines × 2) packages/at_client_flutter/lib/src/widgets/apkam_dialog.dart:507— packages/at_client_flutter/lib/src/widgets/apkam_dialog.dart:507-583 | packages/at_client_flutter/lib/src/widgets/registrar_cram_dialog.dart:260-336 — before extracting anything, compare `packages/at_client_flutter/lib/src/widgets/apkam_dialog.dart` and `packages/at_client_flutter/lib/src/widgets/registrar_cram_dialog.dart` as WHOLE FILES: this scan already matched 5 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 (53 lines × 2) packages/at_events_flutter/lib/common_components/display_tile.dart:64— packages/at_events_flutter/lib/common_components/display_tile.dart:64-116 | packages/at_location_flutter/lib/common_components/display_tile.dart:66-118 — before extracting anything, compare `packages/at_events_flutter/lib/common_components/display_tile.dart` and `packages/at_location_flutter/lib/common_components/display_tile.dart` as WHOLE FILES: this scan already matched 3 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. 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 (46 lines × 2) packages/at_contacts_group_flutter/lib/screens/edit/group_edit.dart:221— packages/at_contacts_group_flutter/lib/screens/edit/group_edit.dart:221-266 | packages/at_contacts_group_flutter/lib/screens/new_group/new_group.dart:179-224 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (37–38 lines × 2) packages/at_contacts_flutter/lib/desktop_screens/desktop_contacts_screen.dart:177— packages/at_contacts_flutter/lib/desktop_screens/desktop_contacts_screen.dart:177-213 | packages/at_contacts_flutter/lib/desktop_screens/desktop_contacts_screen.dart:261-298 — 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 (36–37 lines × 2) packages/at_client_flutter/lib/src/widgets/apkam_dialog.dart:422— packages/at_client_flutter/lib/src/widgets/apkam_dialog.dart:422-457 | packages/at_client_flutter/lib/src/widgets/registrar_cram_dialog.dart:182-218 — before extracting anything, compare `packages/at_client_flutter/lib/src/widgets/apkam_dialog.dart` and `packages/at_client_flutter/lib/src/widgets/registrar_cram_dialog.dart` as WHOLE FILES: this scan already matched 5 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 (30 lines × 2) packages/at_events_flutter/lib/common_components/display_tile.dart:132— packages/at_events_flutter/lib/common_components/display_tile.dart:132-161 | packages/at_location_flutter/lib/common_components/display_tile.dart:133-162 — before extracting anything, compare `packages/at_events_flutter/lib/common_components/display_tile.dart` and `packages/at_location_flutter/lib/common_components/display_tile.dart` as WHOLE FILES: this scan already matched 3 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. 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 (26–28 lines × 2) packages/at_contacts_group_flutter/lib/widgets/circular_group_contact.dart:36— packages/at_contacts_group_flutter/lib/widgets/circular_group_contact.dart:36-61 | packages/at_contacts_group_flutter/lib/widgets/person_horizontal_tile.dart:36-63 — before extracting anything, compare `packages/at_contacts_group_flutter/lib/widgets/circular_group_contact.dart` and `packages/at_contacts_group_flutter/lib/widgets/person_horizontal_tile.dart` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 54 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 (27 lines × 2) packages/at_contacts_group_flutter/lib/widgets/desktop_person_vertical_tile.dart:101— packages/at_contacts_group_flutter/lib/widgets/desktop_person_vertical_tile.dart:101-127 | packages/at_contacts_group_flutter/lib/widgets/person_vertical_tile.dart:107-133 — before extracting anything, compare `packages/at_contacts_group_flutter/lib/widgets/desktop_person_vertical_tile.dart` and `packages/at_contacts_group_flutter/lib/widgets/person_vertical_tile.dart` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 71 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–25 lines × 2) packages/at_contacts_group_flutter/lib/screens/edit/group_edit.dart:334— packages/at_contacts_group_flutter/lib/screens/edit/group_edit.dart:334-352 | packages/at_contacts_group_flutter/lib/screens/group_view/group_view.dart:257-281 — before extracting anything, compare `packages/at_contacts_group_flutter/lib/screens/edit/group_edit.dart` and `packages/at_contacts_group_flutter/lib/screens/group_view/group_view.dart` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 79 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (22–24 lines × 2) packages/at_contacts_group_flutter/lib/screens/list/group_list.dart:167— packages/at_contacts_group_flutter/lib/screens/list/group_list.dart:167-190 | packages/at_contacts_group_flutter/lib/screens/list/group_list.dart:229-250 — 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 (21–23 lines × 2) packages/at_contacts_flutter/lib/widgets/add_contacts_dialog.dart:149— packages/at_contacts_flutter/lib/widgets/add_contacts_dialog.dart:149-171 | packages/at_contacts_group_flutter/lib/widgets/add_contacts_group_dialog.dart:119-139 — before extracting anything, compare `packages/at_contacts_flutter/lib/widgets/add_contacts_dialog.dart` and `packages/at_contacts_group_flutter/lib/widgets/add_contacts_group_dialog.dart` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 68 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–22 lines × 2) packages/at_contacts_group_flutter/lib/screens/edit/group_edit.dart:561— packages/at_contacts_group_flutter/lib/screens/edit/group_edit.dart:561-580 | packages/at_contacts_group_flutter/lib/screens/group_view/group_view.dart:366-387 — before extracting anything, compare `packages/at_contacts_group_flutter/lib/screens/edit/group_edit.dart` and `packages/at_contacts_group_flutter/lib/screens/group_view/group_view.dart` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 79 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (20–21 lines × 2) packages/at_contacts_flutter/lib/widgets/add_contacts_dialog.dart:97— packages/at_contacts_flutter/lib/widgets/add_contacts_dialog.dart:97-116 | packages/at_contacts_group_flutter/lib/widgets/add_contacts_group_dialog.dart:83-103 — before extracting anything, compare `packages/at_contacts_flutter/lib/widgets/add_contacts_dialog.dart` and `packages/at_contacts_group_flutter/lib/widgets/add_contacts_group_dialog.dart` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 68 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 × 2) packages/at_contacts_flutter/lib/widgets/add_singular_contact_dialog.dart:31— packages/at_contacts_flutter/lib/widgets/add_singular_contact_dialog.dart:31-50 | packages/at_contacts_group_flutter/lib/widgets/add_single_contact_group.dart:31-50 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (18–19 lines × 2) packages/at_contacts_group_flutter/lib/desktop_screens/desktop_bottom_sheet.dart:46— packages/at_contacts_group_flutter/lib/desktop_screens/desktop_bottom_sheet.dart:46-63 | packages/at_contacts_group_flutter/lib/desktop_screens/desktop_group_list.dart:112-130 — 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 (18 lines × 3) packages/at_chat_flutter/lib/utils/colors.dart:12— packages/at_chat_flutter/lib/utils/colors.dart:12-29 | packages/at_contacts_flutter/lib/utils/colors.dart:25-42 | packages/at_location_flutter/lib/utils/constants/colors.dart:42-59 — 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 (15–17 lines × 2) packages/at_events_flutter/lib/screens/notification_dialog/event_notification_dialog.dart:281— packages/at_events_flutter/lib/screens/notification_dialog/event_notification_dialog.dart:281-297 | packages/at_events_flutter/lib/screens/notification_dialog/event_notification_dialog.dart:331-345 — 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 × 3) packages/at_chat_flutter/lib/utils/colors.dart:60— packages/at_chat_flutter/lib/utils/colors.dart:60-75 | packages/at_contacts_flutter/lib/utils/colors.dart:73-88 | packages/at_location_flutter/lib/utils/constants/colors.dart:90-105 — 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 (13–16 lines × 2) packages/at_contacts_group_flutter/lib/desktop_screens/desktop_group_detail.dart:209— packages/at_contacts_group_flutter/lib/desktop_screens/desktop_group_detail.dart:209-224 | packages/at_contacts_group_flutter/lib/desktop_screens/desktop_group_detail.dart:409-421 — 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–15 lines × 2) packages/at_chops/lib/src/algorithm/encryption/aes_ctr_ffi_algo.dart:128— packages/at_chops/lib/src/algorithm/encryption/aes_ctr_ffi_algo.dart:128-142 | packages/at_chops/lib/src/algorithm/encryption/aes_ctr_ffi_algo.dart:191-204 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (12–15 lines × 2) packages/at_contacts_group_flutter/lib/desktop_screens/desktop_group_initial_screen.dart:49— packages/at_contacts_group_flutter/lib/desktop_screens/desktop_group_initial_screen.dart:49-60 | packages/at_contacts_group_flutter/lib/screens/list/group_list.dart:134-148 — 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 × 3) packages/at_contacts_group_flutter/lib/widgets/circular_group_contact.dart:34— packages/at_contacts_group_flutter/lib/widgets/circular_group_contact.dart:34-47 | packages/at_contacts_group_flutter/lib/widgets/desktop_person_horizontal_tile.dart:33-46 | packages/at_contacts_group_flutter/lib/widgets/person_horizontal_tile.dart:34-47 — before extracting anything, compare `packages/at_contacts_group_flutter/lib/widgets/circular_group_contact.dart` and `packages/at_contacts_group_flutter/lib/widgets/person_horizontal_tile.dart` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 54 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–14 lines × 2) packages/at_contacts_group_flutter/lib/widgets/bottom_sheet.dart:61— packages/at_contacts_group_flutter/lib/widgets/bottom_sheet.dart:61-72 | packages/at_contacts_group_flutter/lib/widgets/confirmation_dialog.dart:142-155 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (12–13 lines × 3) packages/at_contacts_flutter/lib/widgets/circular_contacts.dart:59— packages/at_contacts_flutter/lib/widgets/circular_contacts.dart:59-70 | packages/at_contacts_group_flutter/lib/widgets/desktop_person_vertical_tile.dart:100-112 | packages/at_contacts_group_flutter/lib/widgets/person_vertical_tile.dart:106-118 — before extracting anything, compare `packages/at_contacts_group_flutter/lib/widgets/desktop_person_vertical_tile.dart` and `packages/at_contacts_group_flutter/lib/widgets/person_vertical_tile.dart` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 71 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 × 2) packages/at_contacts_group_flutter/lib/screens/empty_group/empty_group.dart:88— packages/at_contacts_group_flutter/lib/screens/empty_group/empty_group.dart:88-100 | packages/at_contacts_group_flutter/lib/widgets/bottom_sheet.dart:66-75 — 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–12 lines × 5) packages/at_follows_flutter/lib/domain/connection_model.dart:74— packages/at_follows_flutter/lib/domain/connection_model.dart:74-84 | packages/at_follows_flutter/lib/domain/connection_model.dart:110-121 | packages/at_follows_flutter/lib/domain/connection_model.dart:132-142 | packages/at_login_flutter/lib/domain/at_login_provider.dart:69-79 | packages/at_login_flutter/lib/domain/at_login_provider.dart:104-115 — 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 (11–12 lines × 2) packages/at_client/lib/src/key_stream/key_stream_iterable_base.dart:32— packages/at_client/lib/src/key_stream/key_stream_iterable_base.dart:32-42 | packages/at_client/lib/src/key_stream/key_stream_map_base.dart:21-32 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (9–11 lines × 2) packages/at_chops/lib/src/algorithm/encryption/aes_ctr_ffi_algo.dart:113— packages/at_chops/lib/src/algorithm/encryption/aes_ctr_ffi_algo.dart:113-123 | packages/at_chops/lib/src/algorithm/encryption/aes_ctr_ffi_algo.dart:178-186 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10–11 lines × 2) packages/at_client/lib/src/client/at_client_impl.dart:2391— packages/at_client/lib/src/client/at_client_impl.dart:2391-2400 | packages/at_client/lib/src/client/at_client_impl.dart:2407-2417 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8–10 lines × 4) packages/at_contacts_flutter/lib/widgets/add_contacts_dialog.dart:51— packages/at_contacts_flutter/lib/widgets/add_contacts_dialog.dart:51-58 | packages/at_contacts_flutter/lib/widgets/add_singular_contact_dialog.dart:32-41 | packages/at_contacts_group_flutter/lib/widgets/add_contacts_group_dialog.dart:38-45 | packages/at_contacts_group_flutter/lib/widgets/add_single_contact_group.dart:32-41 — before extracting anything, compare `packages/at_contacts_flutter/lib/widgets/add_contacts_dialog.dart` and `packages/at_contacts_group_flutter/lib/widgets/add_contacts_group_dialog.dart` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 68 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 (9–10 lines × 3) packages/at_events_flutter/lib/screens/recurring_event.dart:82— packages/at_events_flutter/lib/screens/recurring_event.dart:82-91 | packages/at_events_flutter/lib/screens/recurring_event.dart:130-138 | packages/at_location_flutter/lib/screens/share_location/share_location_sheet.dart:74-83 — 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 (8–9 lines × 2) packages/at_contacts_group_flutter/lib/widgets/bottom_sheet.dart:34— packages/at_contacts_group_flutter/lib/widgets/bottom_sheet.dart:34-42 | packages/at_contacts_group_flutter/lib/widgets/contacts_selction_bottom_sheet.dart:39-46 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (7–8 lines × 2) packages/at_client/lib/src/util/at_client_util.dart:86— packages/at_client/lib/src/util/at_client_util.dart:86-93 | packages/at_commons/lib/src/keystore/at_key.dart:747-753 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (7 lines × 4) packages/at_events_flutter/lib/common_components/concurrent_event_request_dialog.dart:86— packages/at_events_flutter/lib/common_components/concurrent_event_request_dialog.dart:86-94 | packages/at_events_flutter/lib/common_components/error_screen.dart:21-27 | packages/at_events_flutter/lib/screens/recurring_event.dart:374-380 | packages/at_events_flutter/lib/screens/selected_location.dart:165-173 — 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 (4–7 lines × 3) packages/at_location_flutter/lib/map_content/flutter_map/src/layer/marker_layer.dart:116— packages/at_location_flutter/lib/map_content/flutter_map/src/layer/marker_layer.dart:116-122 | packages/at_location_flutter/lib/map_content/flutter_map_marker_cluster/src/marker_cluster_layer.dart:418-421 | packages/at_location_flutter/lib/map_content/flutter_map_marker_popup/src/popup_marker_layer.dart:21-27 — 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 (5 lines × 6) packages/at_location_flutter/lib/map_content/flutter_map/src/layer/circle_layer.dart:41— packages/at_location_flutter/lib/map_content/flutter_map/src/layer/circle_layer.dart:41-45 | packages/at_location_flutter/lib/map_content/flutter_map/src/layer/group_layer.dart:23-27 | packages/at_location_flutter/lib/map_content/flutter_map/src/layer/marker_layer.dart:101-105 | packages/at_location_flutter/lib/map_content/flutter_map/src/layer/overlay_image_layer.dart:38-42 | packages/at_location_flutter/lib/map_content/flutter_map/src/layer/polygon_layer.dart:60-64 | packages/at_location_flutter/lib/map_content/flutter_map/src/layer/polyline_layer.dart:58-62 — before extracting anything, compare `packages/at_location_flutter/lib/map_content/flutter_map/src/layer/polygon_layer.dart` and `packages/at_location_flutter/lib/map_content/flutter_map/src/layer/polyline_layer.dart` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 35 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 × 8) packages/at_chat_flutter/ios/Classes/SwiftAtChatFlutterPlugin.swift:5— packages/at_chat_flutter/ios/Classes/SwiftAtChatFlutterPlugin.swift:5-9 | packages/at_contacts_flutter/ios/Classes/SwiftAtContactsFlutterPlugin.swift:5-9 | packages/at_contacts_group_flutter/ios/Classes/SwiftAtContactsGroupFlutterPlugin.swift:5-9 | packages/at_events_flutter/ios/Classes/SwiftAtEventsFlutterPlugin.swift:5-9 | packages/at_follows_flutter/ios/Classes/SwiftAtFollowsFlutterPlugin.swift:5-9 | packages/at_location_flutter/ios/Classes/SwiftAtLocationFlutterPlugin.swift:5-9 | packages/at_login_flutter/ios/Classes/SwiftAtLoginFlutterPlugin.swift:5-9 | packages/at_notify_flutter/ios/Classes/SwiftAtNotifyFlutterPlugin.swift:5-9 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 8 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 8 times.
Duplicated block (5 lines × 3) packages/at_contacts_flutter/macos/Classes/AtContactsFlutterPlugin.swift:5— packages/at_contacts_flutter/macos/Classes/AtContactsFlutterPlugin.swift:5-9 | packages/at_contacts_group_flutter/macos/Classes/AtContactsGroupFlutterPlugin.swift:5-9 | packages/at_login_flutter/macos/Classes/AtLoginFlutterPlugin.swift:5-9 — 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.
D4 · Code Duplication· Near-duplicate member family (6 members, 47 shared lines) · ×1
Near-duplicate member family (6 members, 47 shared lines) packages/at_contacts_flutter/example/lib/main.dart:45— packages/at_contacts_flutter/example/lib/main.dart:45-163 | packages/at_contacts_group_flutter/example/lib/main.dart:41-147 | packages/at_events_flutter/example/lib/main.dart:40-147 | packages/at_location_flutter/example/lib/main.dart:44-156 | packages/at_notify_flutter/example/lib/main.dart:40-150 | packages/at_sync_ui_flutter/example/lib/main.dart:41-154 — These 6 members are variants of one another: a block of 47 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 (6 members, 34 shared lines) · ×1
Near-duplicate member family (6 members, 34 shared lines) packages/at_contacts_group_flutter/example/lib/main.dart:41— packages/at_contacts_group_flutter/example/lib/main.dart:41-147 | packages/at_events_flutter/example/lib/main.dart:40-147 | packages/at_location_flutter/example/lib/main.dart:44-156 | packages/at_notify_flutter/example/lib/main.dart:40-150 | packages/at_sync_ui_flutter/example/lib/main.dart:41-154 | packages/at_theme_flutter/example/lib/main.dart:45-134 — These 6 members are variants of one another: a block of 34 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.
Duplicated block (43 lines × 2) packages/at_client_flutter/example/dockerstats/lib/main.dart:49— packages/at_client_flutter/example/dockerstats/lib/main.dart:49-91 | packages/at_client_flutter/example/todos/lib/main.dart:47-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 (37 lines × 2) packages/at_client_flutter/example/dockerstats/lib/screens/dashboard.dart:535— packages/at_client_flutter/example/dockerstats/lib/screens/dashboard.dart:535-571 | packages/at_client_flutter/example/dockerstats/lib/screens/dashboard.dart:647-683 — 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 (25–28 lines × 6) packages/at_contacts_flutter/example/lib/main.dart:69— packages/at_contacts_flutter/example/lib/main.dart:69-96 | packages/at_contacts_group_flutter/example/lib/main.dart:61-85 | packages/at_events_flutter/example/lib/main.dart:61-85 | packages/at_location_flutter/example/lib/main.dart:70-94 | packages/at_notify_flutter/example/lib/main.dart:63-88 | packages/at_sync_ui_flutter/example/lib/main.dart:66-91 — before extracting anything, compare `packages/at_contacts_flutter/example/lib/main.dart` and `packages/at_contacts_group_flutter/example/lib/main.dart` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 110 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (26 lines × 4) packages/at_contacts_group_flutter/example/lib/main.dart:92— packages/at_contacts_group_flutter/example/lib/main.dart:92-117 | packages/at_events_flutter/example/lib/main.dart:92-117 | packages/at_location_flutter/example/lib/main.dart:101-126 | packages/at_notify_flutter/example/lib/main.dart:95-120 — before extracting anything, compare `packages/at_contacts_group_flutter/example/lib/main.dart` and `packages/at_events_flutter/example/lib/main.dart` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 196 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 × 5) packages/at_contacts_flutter/example/lib/main.dart:133— packages/at_contacts_flutter/example/lib/main.dart:133-157 | packages/at_contacts_group_flutter/example/lib/main.dart:117-141 | packages/at_events_flutter/example/lib/main.dart:117-141 | packages/at_location_flutter/example/lib/main.dart:126-150 | packages/at_notify_flutter/example/lib/main.dart:120-144 — before extracting anything, compare `packages/at_contacts_flutter/example/lib/main.dart` and `packages/at_contacts_group_flutter/example/lib/main.dart` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 110 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (21–22 lines × 6) packages/at_contacts_flutter/example/lib/main.dart:142— packages/at_contacts_flutter/example/lib/main.dart:142-163 | packages/at_contacts_group_flutter/example/lib/main.dart:126-147 | packages/at_events_flutter/example/lib/main.dart:126-147 | packages/at_location_flutter/example/lib/main.dart:135-156 | packages/at_notify_flutter/example/lib/main.dart:129-150 | packages/at_sync_ui_flutter/example/lib/main.dart:134-154 — before extracting anything, compare `packages/at_contacts_flutter/example/lib/main.dart` and `packages/at_contacts_group_flutter/example/lib/main.dart` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 110 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (20–21 lines × 6) packages/at_contacts_flutter/example/lib/main.dart:137— packages/at_contacts_flutter/example/lib/main.dart:137-156 | packages/at_contacts_group_flutter/example/lib/main.dart:121-140 | packages/at_events_flutter/example/lib/main.dart:121-140 | packages/at_location_flutter/example/lib/main.dart:130-149 | packages/at_notify_flutter/example/lib/main.dart:124-143 | packages/at_theme_flutter/example/lib/main.dart:110-130 — before extracting anything, compare `packages/at_contacts_flutter/example/lib/main.dart` and `packages/at_contacts_group_flutter/example/lib/main.dart` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 110 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (17 lines × 6) packages/at_contacts_group_flutter/example/lib/main.dart:85— packages/at_contacts_group_flutter/example/lib/main.dart:85-101 | packages/at_events_flutter/example/lib/main.dart:85-101 | packages/at_location_flutter/example/lib/main.dart:94-110 | packages/at_notify_flutter/example/lib/main.dart:88-104 | packages/at_sync_ui_flutter/example/lib/main.dart:91-107 | packages/at_theme_flutter/example/lib/main.dart:66-82 — before extracting anything, compare `packages/at_contacts_group_flutter/example/lib/main.dart` and `packages/at_events_flutter/example/lib/main.dart` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 196 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 × 5) packages/at_contacts_group_flutter/example/lib/main.dart:104— packages/at_contacts_group_flutter/example/lib/main.dart:104-120 | packages/at_events_flutter/example/lib/main.dart:104-120 | packages/at_location_flutter/example/lib/main.dart:113-129 | packages/at_notify_flutter/example/lib/main.dart:107-123 | packages/at_sync_ui_flutter/example/lib/main.dart:111-127 — before extracting anything, compare `packages/at_contacts_group_flutter/example/lib/main.dart` and `packages/at_events_flutter/example/lib/main.dart` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 196 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 (16 lines × 6) packages/at_contacts_group_flutter/example/lib/main.dart:104— packages/at_contacts_group_flutter/example/lib/main.dart:104-119 | packages/at_events_flutter/example/lib/main.dart:104-119 | packages/at_location_flutter/example/lib/main.dart:113-128 | packages/at_notify_flutter/example/lib/main.dart:107-122 | packages/at_sync_ui_flutter/example/lib/main.dart:111-126 | packages/at_theme_flutter/example/lib/main.dart:89-106 — before extracting anything, compare `packages/at_contacts_group_flutter/example/lib/main.dart` and `packages/at_events_flutter/example/lib/main.dart` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 196 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 (14–15 lines × 3) packages/at_events_flutter/example/lib/main.dart:40— packages/at_events_flutter/example/lib/main.dart:40-53 | packages/at_location_flutter/example/lib/main.dart:44-58 | packages/at_sync_ui_flutter/example/lib/main.dart:41-55 — before extracting anything, compare `packages/at_events_flutter/example/lib/main.dart` and `packages/at_location_flutter/example/lib/main.dart` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 201 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–14 lines × 3) packages/at_contacts_flutter/example/lib/main.dart:45— packages/at_contacts_flutter/example/lib/main.dart:45-58 | packages/at_contacts_group_flutter/example/lib/main.dart:41-53 | packages/at_notify_flutter/example/lib/main.dart:40-53 — before extracting anything, compare `packages/at_contacts_flutter/example/lib/main.dart` and `packages/at_contacts_group_flutter/example/lib/main.dart` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 110 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (13–14 lines × 2) packages/at_client_flutter/example/dockerstats/lib/screens/dashboard.dart:577— packages/at_client_flutter/example/dockerstats/lib/screens/dashboard.dart:577-589 | packages/at_client_flutter/example/dockerstats/lib/screens/dashboard.dart:689-702 — 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 × 7) packages/at_contacts_group_flutter/example/lib/main.dart:91— packages/at_contacts_group_flutter/example/lib/main.dart:91-102 | packages/at_events_flutter/example/lib/main.dart:91-102 | packages/at_location_flutter/example/lib/main.dart:100-111 | packages/at_login_flutter/example/lib/main.dart:51-62 | packages/at_notify_flutter/example/lib/main.dart:94-105 | packages/at_sync_ui_flutter/example/lib/main.dart:97-108 | packages/at_theme_flutter/example/lib/main.dart:72-83 — before extracting anything, compare `packages/at_contacts_group_flutter/example/lib/main.dart` and `packages/at_events_flutter/example/lib/main.dart` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 196 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 (12 lines × 3) packages/at_chops/example/zariot/external_signer.dart:80— packages/at_chops/example/zariot/external_signer.dart:80-91 | packages/at_chops/example/zariot/external_signer.dart:131-142 | packages/at_chops/example/zariot/external_signer.dart:155-166 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (11 lines × 3) packages/at_contacts_flutter/example/lib/second_screen.dart:106— packages/at_contacts_flutter/example/lib/second_screen.dart:106-117 | packages/at_contacts_group_flutter/example/lib/second_screen.dart:34-45 | packages/at_sync_ui_flutter/example/lib/second_screen.dart:59-69 — before extracting anything, compare `packages/at_contacts_flutter/example/lib/second_screen.dart` and `packages/at_contacts_group_flutter/example/lib/second_screen.dart` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 41 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 × 4) packages/at_client_flutter/example/invitations/lib/screens/home.dart:141— packages/at_client_flutter/example/invitations/lib/screens/home.dart:141-146 | packages/at_client_flutter/example/invitations/lib/screens/received.dart:128-133 | packages/at_client_flutter/example/todos/lib/screens/todo_detail.dart:72-77 | packages/at_client_flutter/example/todos/lib/screens/todos_home.dart:166-171 — 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 (9–10 lines × 2) packages/at_follows_flutter/example/ios/Runner/AppDelegate.swift:6— packages/at_follows_flutter/example/ios/Runner/AppDelegate.swift:6-14 | packages/at_notify_flutter/example/ios/Runner/AppDelegate.swift:6-15 — 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 (10 lines × 8) packages/at_chat_flutter/example/macos/Runner/MainFlutterWindow.swift:5— packages/at_chat_flutter/example/macos/Runner/MainFlutterWindow.swift:5-14 | packages/at_contacts_flutter/example/macos/Runner/MainFlutterWindow.swift:5-14 | packages/at_contacts_group_flutter/example/macos/Runner/MainFlutterWindow.swift:5-14 | packages/at_events_flutter/example/macos/Runner/MainFlutterWindow.swift:5-14 | packages/at_location_flutter/example/macos/Runner/MainFlutterWindow.swift:5-14 | packages/at_notify_flutter/example/macos/Runner/MainFlutterWindow.swift:5-14 | packages/at_sync_ui_flutter/example/macos/Runner/MainFlutterWindow.swift:5-14 | packages/at_theme_flutter/example/macos/Runner/MainFlutterWindow.swift:5-14 — before extracting anything, compare `packages/at_chat_flutter/example/macos/Runner/MainFlutterWindow.swift` and `packages/at_contacts_flutter/example/macos/Runner/MainFlutterWindow.swift` as WHOLE FILES: 100% 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.
Off the main sequence: at_utils — at_utils: abstractness 0.15, instability 0.10, distance 0.75 — zone of pain — concrete and depended on by 9 project(s), so it's rigid to change.
Swallowed exception (empty catch) packages/at_client_cli/lib/src/commands/auth_cli.dart:123— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Orphaned file packages/at_location_flutter/lib/service/send_location_notification.dart:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/at_contacts_flutter/lib/desktop_screens/desktop_contacts_screen.dart:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/at_events_flutter/lib/screens/notification_dialog/event_notification_dialog.dart:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/at_contacts_group_flutter/lib/screens/group_view/group_view.dart:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/at_location_flutter/lib/common_components/collapsed_content.dart:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/at_contacts_group_flutter/lib/services/group_service.dart:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/at_follows_flutter/lib/services/connections_service.dart:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/at_events_flutter/lib/screens/recurring_event.dart:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/at_location_flutter/lib/service/key_stream_service.dart:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/at_events_flutter/lib/screens/map_screen/events_collapsed_content.dart:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/at_location_flutter/lib/service/request_location_service.dart:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/at_contacts_group_flutter/lib/screens/list/group_list.dart:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/at_events_flutter/lib/screens/select_location.dart:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/at_login_flutter/lib/widgets/at_login_widget.dart:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/at_chat_flutter/lib/services/chat_service.dart:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/at_follows_flutter/lib/widgets/followers.dart:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/at_contacts_group_flutter/lib/desktop_screens/desktop_new_group.dart:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/at_contacts_flutter/lib/screens/contacts_screen.dart:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/at_location_flutter/lib/service/sharing_location_service.dart:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/at_location_flutter/lib/map_content/flutter_map/src/geo/crs/crs.dart:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file REDACTED:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/at_contacts_group_flutter/lib/screens/new_group/new_group.dart:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/at_sync_ui_flutter/lib/at_sync_cupertino.dart:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/at_events_flutter/lib/screens/one_day_event.dart:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/at_sync_ui_flutter/lib/at_sync_material.dart:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Duplicated predicate packages/at_client_flutter/lib/src/widgets/apkam_dialog.dart:542— `!mounted || !_pinScrollController.hasClients` appears character-identically in 2 files — packages/at_client_flutter/lib/src/widgets/apkam_dialog.dart, packages/at_client_flutter/lib/src/widgets/registrar_cram_dialog.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 packages/at_location_flutter/lib/service/request_location_service.dart:80— `(!locationNotificationModel.isAccepted) && (locationNotificationModel.isExited)` appears character-identically in 2 files — packages/at_location_flutter/lib/service/request_location_service.dart, packages/at_location_flutter/lib/service/sharing_location_service.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 packages/at_events_flutter/lib/services/home_event_service.dart:195— `(MasterLocationService().locationReceivedData[_atsign] != null) && (MasterLocationService() .locationReceivedData[_atsign]! .locationSharing…` appears character-identically in 2 files — packages/at_events_flutter/lib/services/home_event_service.dart, packages/at_location_flutter/lib/utils/constants/init_location_service.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 packages/at_location_flutter/lib/service/master_location_service.dart:117— `(_atValue != null) && (_atValue.value != null)` appears character-identically in 2 files — packages/at_location_flutter/lib/service/master_location_service.dart, packages/at_location_flutter/lib/service/send_location_notification.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 packages/at_events_flutter/lib/services/event_key_stream_service.dart:150— `(allRegexResponses != null) && (allRegexResponses.isNotEmpty)` appears character-identically in 2 files — packages/at_events_flutter/lib/services/event_key_stream_service.dart, packages/at_location_flutter/lib/service/key_stream_service.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 packages/at_location_flutter/lib/service/request_location_service.dart:128— `(alreadyExists[0]) && (!KeyStreamService().isPastNotification(alreadyExists[1]))` appears character-identically in 2 files — packages/at_location_flutter/lib/service/request_location_service.dart, packages/at_location_flutter/lib/service/sharing_location_service.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 packages/at_events_flutter/lib/services/at_event_notification_listener.dart:68— `(notification.id == '-1') || compareAtSign(notification.from, AtClientManager.getInstance().atClient.getCurrentAtSign()!)` appears character-identically in 2 files — packages/at_events_flutter/lib/services/at_event_notification_listener.dart, packages/at_location_flutter/lib/service/at_location_notification_listener.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 packages/at_location_flutter/lib/screens/home/home_screen.dart:55— `(permission == LocationPermission.always) || (permission == LocationPermission.whileInUse)` appears character-identically in 4 files — packages/at_location_flutter/lib/screens/home/home_screen.dart, packages/at_location_flutter/lib/service/location_service.dart, packages/at_location_flutter/lib/service/my_location.dart, packages/at_location_flutter/lib/service/send_location_notification.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 packages/at_events_flutter/lib/services/event_key_stream_service.dart:91— `(value.value != null) && (value.value != 'null')` appears character-identically in 2 files — packages/at_events_flutter/lib/services/event_key_stream_service.dart, packages/at_location_flutter/lib/service/key_stream_service.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 packages/at_commons/lib/src/verb/llookup_verb_builder.dart:74— `atKey.key.isNotEmpty && atKey.sharedBy != null` appears character-identically in 3 files — packages/at_commons/lib/src/verb/llookup_verb_builder.dart, packages/at_commons/lib/src/verb/lookup_verb_builder.dart, packages/at_commons/lib/src/verb/plookup_verb_builder.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 packages/at_auth/lib/src/keys/io/file_io.dart:225— `atKeys.atsign != null && atKeys.atsign != normalized` appears character-identically in 2 files — packages/at_auth/lib/src/keys/io/file_io.dart, packages/at_client_flutter/lib/src/keychain/keychain_io_impl.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 packages/at_contacts_group_flutter/lib/screens/edit/person_horizontal.dart:40— `contact.tags != null && contact.tags!['image'] != null` appears character-identically in 9 files — packages/at_contacts_group_flutter/lib/screens/edit/person_horizontal.dart, packages/at_contacts_group_flutter/lib/widgets/confirmation_dialog.dart, packages/at_contacts_group_flutter/lib/widgets/person_vertical_tile.dart, packages/at_events_flutter/lib/common_components/display_tile.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 packages/at_contacts_group_flutter/lib/screens/edit/person_horizontal.dart:46— `contact.tags != null && contact.tags!['name'] != null` appears character-identically in 2 files — packages/at_contacts_group_flutter/lib/screens/edit/person_horizontal.dart, packages/at_contacts_group_flutter/lib/widgets/person_vertical_tile.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 packages/at_events_flutter/lib/services/at_event_notification_listener.dart:99— `decryptedMessage == null || decryptedMessage == ''` appears character-identically in 2 files — packages/at_events_flutter/lib/services/at_event_notification_listener.dart, packages/at_location_flutter/lib/service/at_location_notification_listener.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 packages/at_client/lib/src/lifecycle/enrollments.dart:25— `expiry != null && DateTime.now().isAfter(expiry)` appears character-identically in 2 files — packages/at_client/lib/src/lifecycle/enrollments.dart, packages/at_client_flutter/lib/src/keychain/keychain_data.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 packages/at_chops/lib/src/algorithm/encryption/aes_gcm.dart:95— `iv == null || iv.ivBytes.length != nonceLength` appears character-identically in 2 files — packages/at_chops/lib/src/algorithm/encryption/aes_gcm.dart, packages/at_chops/lib/src/algorithm/encryption/aes_gcm_ffi_algo.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 packages/at_events_flutter/lib/models/event_member_location.dart:25— `json['lat'] != 'null' && json['lat'] != null` appears character-identically in 2 files — packages/at_events_flutter/lib/models/event_member_location.dart, packages/at_location_flutter/lib/location_modal/location_notification.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 packages/at_events_flutter/lib/models/event_member_location.dart:28— `json['long'] != 'null' && json['long'] != null` appears character-identically in 2 files — packages/at_events_flutter/lib/models/event_member_location.dart, packages/at_location_flutter/lib/location_modal/location_notification.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 packages/at_client/lib/src/crypto/nskey/nskey_key_ring.dart:152— `key.alg == alg && key.use == use && key.offeredForNewOperations` appears character-identically in 2 files — packages/at_client/lib/src/crypto/nskey/nskey_key_ring.dart, packages/at_client/lib/src/secret_sharing/key_package.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 packages/at_auth/lib/src/enroll/apsk_advertisement.dart:155— `kid is! String || use is! String || alg is! String || pub is! String` appears character-identically in 2 files — packages/at_auth/lib/src/enroll/apsk_advertisement.dart, packages/at_client/lib/src/secret_sharing/key_package.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 packages/at_auth/lib/src/enroll/enrollment_handshake.dart:225— `lookupResult == null || lookupResult.isEmpty` appears character-identically in 2 files — packages/at_auth/lib/src/enroll/enrollment_handshake.dart, packages/at_auth/lib/src/enroll/enrollment_submitter.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 packages/at_auth/lib/src/registrar/registrar_admin_service.dart:65— `response.statusCode == 401 || response.statusCode == 403` appears character-identically in 2 files — packages/at_auth/lib/src/registrar/registrar_admin_service.dart, packages/at_auth/lib/src/registrar/registrar_service.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 REDACTED:149— `snapshot.data == null || snapshot.data!.isEmpty` appears character-identically in 5 files — REDACTED, packages/at_contacts_flutter/lib/desktop_screens/desktop_contacts_screen.dart, packages/at_contacts_flutter/lib/screens/contacts_screen.dart, packages/at_contacts_group_flutter/lib/screens/group_contact_view/group_contact_view.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 packages/at_contacts_group_flutter/lib/widgets/desktop_person_vertical_tile.dart:73— `widget.isAssetImage && widget.imageLocation != null` appears character-identically in 2 files — packages/at_contacts_group_flutter/lib/widgets/desktop_person_vertical_tile.dart, packages/at_contacts_group_flutter/lib/widgets/person_vertical_tile.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.
IC1 · Incompleteness & stubs· Member throws UnsupportedError · ×4
Member throws UnsupportedError packages/at_chops/lib/src/at_chops_impl.dart:336— `readPublicKey`'s body only throws an UnsupportedError or an UnimplementedError that gives its reason — sometimes a deliberate refusal, often an unfinished stub. Confirm it's intentional.
Member throws UnsupportedError packages/at_client/lib/src/rpc/at_rpc.dart:109— `handleRequest`'s body only throws an UnsupportedError or an UnimplementedError that gives its reason — sometimes a deliberate refusal, often an unfinished stub. Confirm it's intentional.
Member throws UnsupportedError packages/at_client/lib/src/rpc/at_rpc.dart:819— `handleResponse`'s body only throws an UnsupportedError or an UnimplementedError that gives its reason — sometimes a deliberate refusal, often an unfinished stub. Confirm it's intentional.
Member throws UnsupportedError packages/at_policy/lib/src/policy/impl.dart:144— `handleResponse`'s body only throws an UnsupportedError or an UnimplementedError that gives its reason — sometimes a deliberate refusal, often an unfinished stub. Confirm it's intentional.
Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 97 significant file(s) lose their only recent owner: packages/at_client/lib/src/collections/collections.dart, packages/at_client/lib/src/crypto/nskey/published_nskey_key_ring.dart, packages/at_client/lib/src/secret_sharing/pairwise_secret_sharing.dart, packages/at_client/lib/src/client/local_secondary.dart, packages/at_client/lib/src/crypto/nskey/pq_signing_root.dart, packages/at_client/lib/src/client/pq_client_bootstrap.dart, packages/at_client/lib/src/crypto/nskey/pq_signing_chain.dart, packages/at_auth/lib/src/enroll/enrollment_submitter.dart (+89 more). Pair on, review, or document these before any departure.
Off-boarding risk: anonymized user #2 — If anonymized user #2 becomes unavailable, 5 significant file(s) lose their only recent owner: packages/at_telemetry/lib/src/codecs/at_telemetry_logs_codec.dart, packages/at_telemetry/lib/src/http_signatures/at_telemetry_http_signature.dart, packages/at_telemetry/lib/src/exporters/at_telemetry_notification_exporter.dart, packages/at_telemetry/lib/src/at_telemetry.dart, packages/at_commons/lib/src/telemetry/at_telemetry.dart. Pair on, review, or document these before any departure.
Silent fallback default on parse failure packages/at_client/lib/src/crypto/nskey/pq_signing_chain.dart:139— `_keysOf` answers `[]` when `FormatException` is thrown, with no log or rethrow — a malformed value silently becomes that default. Log the input or fail validation. 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 at the `catch` or in the `///` doc, and the row stops firing.
Silent fallback default on parse failure packages/at_client/lib/src/crypto/nskey/pq_signing_chain.dart:805— `_readByAtServer` answers `{}` when `FormatException` is thrown, with no log or rethrow — a malformed value silently becomes that default. Log the input or fail validation. 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 at the `catch` or in the `///` doc, and the row stops firing.
D16 · Bus Factor· Further sole-owners (lower concentration) · ×1
Further sole-owners (lower concentration) — 1 other contributor(s) are each the sole owner of a small amount of code below the off-boarding threshold — folded into the bus-factor score and metrics (104 single-owned of 409 analysed files in total, counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated, example/demo and scaffolding-template trees and test files identified by path convention, largest first; 409 of the 820 production source files in this repository met that bar). They are anonymized user #3 (2 file(s)) — spread or document their files in the same way, at lower priority than the named off-boarding risks above. The files folded here: tools/wasm_shakedown/lib/wasm_shakedown.dart, packages/at_auth/lib/src/registrar/registrar_admin_service.dart.
D26 · Project Cohesion· Projects may be oversized for their cohesion · ×1
Projects may be oversized for their cohesion — 5 of 35 project(s) overshoot their size bounds, lowering Project Cohesion to 7.6/10. The most over is `packages/at_client` (41999 LoC, 285 module-visible types across 34 directories). Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
D28 · Secrets (history)· Rotate the exposed credentials · ×1
REDACTED
D34 · Knowledge Freshness· Further orphaned files (smaller) · ×1
Further orphaned files (smaller) — 158 smaller file(s) also have no living knowledge — folded into the freshness score and metrics rather than raised one row each — most significant first: packages/at_location_flutter/lib/service/send_location_notification.dart, packages/at_contacts_flutter/lib/desktop_screens/desktop_contacts_screen.dart, packages/at_events_flutter/lib/screens/notification_dialog/event_notification_dialog.dart, packages/at_contacts_group_flutter/lib/screens/group_view/group_view.dart, packages/at_location_flutter/lib/common_components/collapsed_content.dart, packages/at_contacts_group_flutter/lib/services/group_service.dart, packages/at_follows_flutter/lib/services/connections_service.dart, packages/at_events_flutter/lib/screens/recurring_event.dart (and 150 more) (166 orphaned of 413 analysed files in total, counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated, example/demo and scaffolding-template trees and test files identified by path convention, largest first; 413 of the 820 production source files in this repository met that bar). Attach the read to the next change that touches one of them: have a second person review that change, and leave behind a short comment or test recording what the file is for, so the knowledge comes back at the cost of a change you were making anyway.
Disabled test packages/at_contact/test/at_group_test.dart:1— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
IC1 · Incompleteness & stubs· Empty method body · ×1
Empty method body packages/at_location_flutter/lib/service/api_service.dart:124— `checkInternetConnection` has an empty body — confirm it's an intentional no-op and not an unfinished method.
README/code drift packages/at_contact/README.md:407— packages/at_contact/README.md links to `CONTRIBUTING.md`, but `packages/at_contact/CONTRIBUTING.md` does not exist. 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.
P10 · Library API & versioning· Large public API surface · ×1
Large public API surface — 1090/1217 types (90%) declared in the published library are public. For a library, every public type is a stability contract — keep implementation types off the surface and expose only the intended API.
Logging is not universal — Only 21/63 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `packages/at_chat_flutter/example`, `packages/at_chat_flutter/example/ios`, `packages/at_chat_flutter/example/macos`, `packages/at_client/example`, `packages/at_client_flutter/example/dockerstats/ios` and 37 more.
P3 · Security & performance tooling· Dependabot does not watch gradle · ×1
Dependabot does not watch gradle .github/dependabot.yaml:2— `.github/dependabot.yaml` schedules updates, but no `package-ecosystem` entry covers `gradle`, which this tree depends on — so those dependencies get no update pull requests and no advisory pressure, however complete the dep-scan credit looks. Add the missing entry to the `updates:` list.
Null assertions (`!`) reduce the null safety score — ~25.7 `!` null assertions per 1k Dart product lines — 3212 across the 124809 line(s) of the 788 Dart file(s) read (generated, test and example code not counted; a file opted out with a `// @dart=` comment below 2.12 counts once). Densest: packages/at_events_flutter/lib/services/event_key_stream_service.dart (164), packages/at_events_flutter/lib/screens/recurring_event.dart (125), packages/at_location_flutter/lib/map_content/flutter_map_marker_cluster/src/marker_cluster_layer.dart (122). Each one tells the analyzer to trust the author about null and becomes a `Null check operator used on a null value` the first time the author is wrong.
Off the main sequence: at_commons — at_commons: abstractness 0.09, instability 0.00, distance 0.91 — the shape a shared-kernel / building-block library has BY DESIGN — concrete and widely depended-on is what makes it useful, and this dimension does not penalise it (the distance is reported for completeness, not as a defect). Worth a look only if it has grown past one coherent kernel into an everything-bucket.
Appendix B — Reproduction & audit trail
Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.
semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
Run 01a1ada1-a308-7eba-af3e-8400603ac51b · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 31 · Warnings: 639 · Recommendations: 210 · Info: 1 — Appendix A · all findings · full markdown report.
Generated by the Canine Code Analyzer: deterministic code-health analysis. 05-11-2026 @ 21:33 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.