Public report of aeecleclair/Titan, published 17 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.4). Assert signed this survey and filed it in the standard's public register, where anyone can look it up by its survey ID. Check this survey →
Signed and filed in the standard's public register, 17 November 2026, 18:31 UTC · Survey ID cd_1d73c135c4d24d858680b6d460287e1d
aeecleclair/Titan
Measured 17 November 2026, 18:31 UTC, at code version 9dd1e9e
First survey, so nothing to compare with yet
CAI scoreWeak
CriticalWeakAdequateStrongExemplary
The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.
A medium codebase: 72,900 lines of product code in 3 projects, tests not counted · Estimated rebuild effort: about 0.5 person-years · Weakest lens: Accessibility, 26.1
Findings by how serious they are
32 critical636 serious253 minor
6 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
17 November 2026, 18:31 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 ▸
54of 54 dimensions measured by tools.
908of 921 findings point to an exact file and line, so you can open each one in the code. The other 13 concern the repository as a whole, such as missing documentation.
54dimensions across 8 lenses, read from 72,900 lines of product code in 3 projects.
aeecleclair/Titan falls short of our standard for production, held back most by its Accessibility lens, the interface's usability with a keyboard or assistive technology. It scores 45.0 out of 100 and is rated Weak, and 29 of its 32 critical findings are security problems.
Accessibility, at 26.1, is the weakest lens and counts most in the score. The best first step is fixing focus, motion and contrast, worth about 14.8 points. Structuring the pages comes next, worth about 10.2 points. Raising Accessibility to 70 would lift the score to about 59.7.
Twenty pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Five secrets can leak from the build pipeline, and one automatic update takes new releases before a bad one can be spotted. Pinning each tool to an exact version, limiting each secret to its own step and setting a waiting period for automatic updates would close these risks. Passing outside input through environment variables would fix the pipeline step that puts outside input straight into a shell command, and the password or key in the code's history needs replacing, with the old one switched off. The page that doesn't say its language needs its language set.
The product code is 72,900 lines, about €72,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.
If Accessibility rose from 26.1 to 70, the lowest score rated Strong, the score would rise from 45.0 to about 59.7.
Code composition: what the lines of code are
Product code 89%Tests 11%
Rebuild cost: about €72,000 · Estimate
Cost to rebuild
€24,000 to €120,000, for 399 to 1,265 hours of work, about 0.5 person-years for one engineer
Difficulty of the problem
Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor
×0.7 at a score of 45. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
Size
Medium: 72,900 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
Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
Raises the score by about 10.2 points · Medium effort · Page structure
3
Resolve the 1 No ADRs found finding(s) in ADR Quality — start with main.dart.
Raises the score by about 2.9 points · Low effort · ADR Quality
Diagnosis: what the measurements show together
Each conclusion below combines several dimensions into one point that no single dimension shows, and lists the measurements it rests on.
Where the investment is most exposed · Value at risk
This code would cost about €72,000 to build again, about 0.5 person-years of work. Its weakest lens is Accessibility, at 26.1 (Weak). Accessibility is about whether the interface is built so that everyone can use it, including people who can't see the screen or can't use a mouse. Because the weakest lens counts most in the score, work on Accessibility also moves the score most.
Based on: the rebuild estimate · the Accessibility grade · how much each lens counts
What to do: Start with the Accessibility actions in Top priorities.
If you do one thing first · First action
Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1. Of all the actions in this report, it raises the score most for the work it takes: about 14.8 points for medium effort. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
What hard-to-read code costs each year · Cost
Four dimensions measure how easy the code is to work in: two measure how tangled its logic is, one how much of it is copied, and one how well each part sticks to a single job. In this codebase they average 6.2 out of 10. Code at that level is slower to change than clean code, and we estimate the extra work at 4% to 10% on every change. The history of the code shows how much it changes: about 7,306 lines over the last 90 days, which is about 29,630 lines a year. At that pace, the extra work comes to an estimated 3.3 to 19.8 engineer-days a year, and it grows as more code changes.
How this is estimated: The number of changed lines is measured from the history of the code. The rest rests on two assumptions of our own: code scoring 8 out of 10 or more adds no extra work, and each point below 8 adds 2.5% to 5.6% to every change, never less than 2% to 5% and never more than 40% to 60% in all; and an engineer changes 150 to 400 lines in a day. The result is a range for planning, not a measurement.
Based on: Cyclomatic Complexity · Cognitive Complexity · Code Duplication · Cohesion (LCOM4) · the code's change history
What to do: Start with the files listed under Churn × Complexity Hotspots, which change often and are hard to read, because that is where the extra work is paid most often.
Architecture: which parts of the code depend on which
The code is divided into modules, groups of code that each handle one part of the product, and a module depends on another when it uses code from it. The table lists the modules both down the side and across the top, in an order where each module should only use modules listed above it. A number in a cell means the module on that row uses the module in that column, and it counts the pairs of building blocks (types) that connect them. The one thing to look for is a mark above the diagonal line. It means two or more modules use each other in a loop (a dependency cycle), so none of them can be changed, tested or released on its own.
30 modules, with 43 dependencies between them. 2 loops run 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.service uses repository.tools, so a change to repository.tools can break repository.service, while a change to repository.service can't break repository.tools.
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.tools uses repository.service, so a change to repository.service can break repository.tools, while a change to repository.tools can't break repository.service.
Position
Below the diagonal: repository.tools uses a module listed above it, which is the healthy direction.
repository.auth uses repository.tools, so a change to repository.tools can break repository.auth, while a change to repository.auth can't break repository.tools.
Position
Below the diagonal: repository.auth uses a module listed above it, which is the healthy direction.
repository.centralassociation uses repository.tools, so a change to repository.tools can break repository.centralassociation, while a change to repository.centralassociation can't break repository.tools.
Position
Below the diagonal: repository.centralassociation uses a module listed above it, which is the healthy direction.
repository.centralisation uses repository.tools, so a change to repository.tools can break repository.centralisation, while a change to repository.centralisation can't break repository.tools.
Position
Below the diagonal: repository.centralisation uses a module listed above it, which is the healthy direction.
repository.cinema uses repository.tools, so a change to repository.tools can break repository.cinema, while a change to repository.cinema can't break repository.tools.
Position
Below the diagonal: repository.cinema uses a module listed above it, which is the healthy direction.
repository.ph uses repository.tools, so a change to repository.tools can break repository.ph, while a change to repository.ph can't break repository.tools.
Position
Below the diagonal: repository.ph uses a module listed above it, which is the healthy direction.
repository.recommendation uses repository.tools, so a change to repository.tools can break repository.recommendation, while a change to repository.recommendation can't break repository.tools.
Position
Below the diagonal: repository.recommendation uses a module listed above it, which is the healthy direction.
repository.seed-library uses repository.tools, so a change to repository.tools can break repository.seed-library, while a change to repository.seed-library can't break repository.tools.
Position
Below the diagonal: repository.seed-library uses a module listed above it, which is the healthy direction.
repository.settings uses repository.tools, so a change to repository.tools can break repository.settings, while a change to repository.settings can't break repository.tools.
Position
Below the diagonal: repository.settings uses a module listed above it, which is the healthy direction.
repository.user uses repository.tools, so a change to repository.tools can break repository.user, while a change to repository.user can't break repository.tools.
Position
Below the diagonal: repository.user uses a module listed above it, which is the healthy direction.
17→28 repository.user uses repository.adminpart of a loop✕
Connections
2 pairs of types, where a type in repository.user uses a type in repository.admin.
repository.user uses repository.admin, so a change to repository.admin can break repository.user, while a change to repository.user can't break repository.admin.
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.version uses repository.tools, so a change to repository.tools can break repository.version, while a change to repository.version can't break repository.tools.
Position
Below the diagonal: repository.version uses a module listed above it, which is the healthy direction.
repository.amap uses repository.tools, so a change to repository.tools can break repository.amap, while a change to repository.amap can't break repository.tools.
Position
Below the diagonal: repository.amap uses a module listed above it, which is the healthy direction.
repository.amap uses repository.user, so a change to repository.user can break repository.amap, while a change to repository.amap can't break repository.user.
Position
Below the diagonal: repository.amap uses a module listed above it, which is the healthy direction.
repository.booking uses repository.service, so a change to repository.service can break repository.booking, while a change to repository.booking can't break repository.service.
Position
Below the diagonal: repository.booking uses a module listed above it, which is the healthy direction.
repository.booking uses repository.tools, so a change to repository.tools can break repository.booking, while a change to repository.booking can't break repository.tools.
Position
Below the diagonal: repository.booking uses a module listed above it, which is the healthy direction.
repository.booking uses repository.user, so a change to repository.user can break repository.booking, while a change to repository.booking can't break repository.user.
Position
Below the diagonal: repository.booking uses a module listed above it, which is the healthy direction.
repository.event uses repository.service, so a change to repository.service can break repository.event, while a change to repository.event can't break repository.service.
Position
Below the diagonal: repository.event uses a module listed above it, which is the healthy direction.
repository.event uses repository.tools, so a change to repository.tools can break repository.event, while a change to repository.event can't break repository.tools.
Position
Below the diagonal: repository.event uses a module listed above it, which is the healthy direction.
repository.event uses repository.user, so a change to repository.user can break repository.event, while a change to repository.event can't break repository.user.
Position
Below the diagonal: repository.event uses a module listed above it, which is the healthy direction.
repository.flappybird uses repository.tools, so a change to repository.tools can break repository.flappybird, while a change to repository.flappybird can't break repository.tools.
Position
Below the diagonal: repository.flappybird uses a module listed above it, which is the healthy direction.
repository.flappybird uses repository.user, so a change to repository.user can break repository.flappybird, while a change to repository.flappybird can't break repository.user.
Position
Below the diagonal: repository.flappybird uses a module listed above it, which is the healthy direction.
repository.loan uses repository.tools, so a change to repository.tools can break repository.loan, while a change to repository.loan can't break repository.tools.
Position
Below the diagonal: repository.loan uses a module listed above it, which is the healthy direction.
repository.loan uses repository.seed-library, so a change to repository.seed-library can break repository.loan, while a change to repository.loan can't break repository.seed-library.
Position
Below the diagonal: repository.loan uses a module listed above it, which is the healthy direction.
repository.loan uses repository.user, so a change to repository.user can break repository.loan, while a change to repository.loan can't break repository.user.
Position
Below the diagonal: repository.loan uses a module listed above it, which is the healthy direction.
28 pairs of types, where a type in repository.mypayment uses a type in repository.tools. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
repository.mypayment uses repository.tools, so a change to repository.tools can break repository.mypayment, while a change to repository.mypayment can't break repository.tools.
Position
Below the diagonal: repository.mypayment uses a module listed above it, which is the healthy direction.
repository.mypayment uses repository.user, so a change to repository.user can break repository.mypayment, while a change to repository.mypayment can't break repository.user.
Position
Below the diagonal: repository.mypayment uses a module listed above it, which is the healthy direction.
24→28 repository.mypayment uses repository.adminpart of a loop✕
Connections
1 pair of types, where a type in repository.mypayment uses a type in repository.admin.
repository.mypayment uses repository.admin, so a change to repository.admin can break repository.mypayment, while a change to repository.mypayment can't break repository.admin.
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.phonebook uses repository.tools, so a change to repository.tools can break repository.phonebook, while a change to repository.phonebook can't break repository.tools.
Position
Below the diagonal: repository.phonebook uses a module listed above it, which is the healthy direction.
repository.phonebook uses repository.user, so a change to repository.user can break repository.phonebook, while a change to repository.phonebook can't break repository.user.
Position
Below the diagonal: repository.phonebook uses a module listed above it, which is the healthy direction.
repository.purchases uses repository.tools, so a change to repository.tools can break repository.purchases, while a change to repository.purchases can't break repository.tools.
Position
Below the diagonal: repository.purchases uses a module listed above it, which is the healthy direction.
repository.purchases uses repository.user, so a change to repository.user can break repository.purchases, while a change to repository.purchases can't break repository.user.
Position
Below the diagonal: repository.purchases uses a module listed above it, which is the healthy direction.
repository.vote uses repository.tools, so a change to repository.tools can break repository.vote, while a change to repository.vote can't break repository.tools.
Position
Below the diagonal: repository.vote uses a module listed above it, which is the healthy direction.
repository.vote uses repository.user, so a change to repository.user can break repository.vote, while a change to repository.vote can't break repository.user.
Position
Below the diagonal: repository.vote uses a module listed above it, which is the healthy direction.
repository.admin uses repository.tools, so a change to repository.tools can break repository.admin, while a change to repository.admin can't break repository.tools.
Position
Below the diagonal: repository.admin uses a module listed above it, which is the healthy direction.
repository.admin uses repository.user, so a change to repository.user can break repository.admin, while a change to repository.admin can't break repository.user.
Position
Below the diagonal: repository.admin uses a module listed above it, which is the healthy direction.
repository.admin uses repository.mypayment, so a change to repository.mypayment can break repository.admin, while a change to repository.admin can't break repository.mypayment.
Position
Below the diagonal: repository.admin uses a module listed above it, which is the healthy direction.
repository.advert uses repository.tools, so a change to repository.tools can break repository.advert, while a change to repository.advert can't break repository.tools.
Position
Below the diagonal: repository.advert uses a module listed above it, which is the healthy direction.
repository.advert uses repository.admin, so a change to repository.admin can break repository.advert, while a change to repository.advert can't break repository.admin.
Position
Below the diagonal: repository.advert uses a module listed above it, which is the healthy direction.
repository.raffle uses repository.tools, so a change to repository.tools can break repository.raffle, while a change to repository.raffle can't break repository.tools.
Position
Below the diagonal: repository.raffle uses a module listed above it, which is the healthy direction.
repository.raffle uses repository.user, so a change to repository.user can break repository.raffle, while a change to repository.raffle can't break repository.user.
Position
Below the diagonal: repository.raffle uses a module listed above it, which is the healthy direction.
repository.raffle uses repository.admin, so a change to repository.admin can break repository.raffle, while a change to repository.raffle can't break repository.admin.
Position
Below the diagonal: repository.raffle uses a module listed above it, which is the healthy direction.
At a glance — Code Health · 73.3 · Adequate · gated by D3, D4 ·
Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).
OWASP category
Findings
Severity
A05:2025 — Injection
30
High / Critical
A03:2025 — Software Supply Chain Failures
10
Medium
A02:2025 — Security Misconfiguration
3
High / Critical
A07:2025 — Authentication Failures
2
High / Critical
A01:2025 — Broken Access Control
1
Medium
Roadmap
Top priorities: Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1; Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh; Resolve the 1 No ADRs found finding(s) in ADR Quality — start with main.dart.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
Add a SAST step to CI running what this repository's stack ships: the Dart analyzer's security lints plus `semgrep --config=auto` — so a security regression fails the build instead of landing.
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.
God Classes: MethodTooLong: MemberEditableCard.build
lib/user/repositories/user_repository.dart
6.3
Mixed
Code Duplication: Edited copy of a member (10 corresponding lines)
lib/raffle/repositories/prize_repository.dart
6.3
Mixed
Code Duplication: Edited copy of a member (3 corresponding lines)
REDACTED
6.4
Mixed
Data Compliance (PII/GDPR): Medium: REDACTED
lib/main.dart
6.5
Mixed
Cognitive Complexity: MyApp.build (cognitive 16)
How the grades work
Every finding carries one of four grades. Three say how serious it is. The fourth says this
survey could not settle it — and it is a grade, not a gap.
Critical — 32
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 — 636
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 — 253
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 6
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 54 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
Every figure here is one of two kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10.
What we checked — 54 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, 908 of 921 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 READ here — but this repository measures it: a coverage step in CI (`flutter test --flavor prod --dart-define=flavor=prod --cover…`), uploaded by `codecov/codecov-action` and a Codecov configuration (.github/codecov.yml) shows that coverage is collected and tracked in your own CI. The built-in collector has no runner for this ecosystem (.dart), so the analyzer could not read the number — a gap in the analyzer's language coverage, not an unmeasured repo. Not scored.
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 — 2 Maven/Gradle manifest(s) were read, stating a version for 0 dependency(ies) and leaving 0 to a parent or an imported BOM, but no build resolved the dependency graph, so the outdated signal was not established. NOT a finding that these dependencies are current or healthy.
D14 License Compliance — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares a Gradle build (build.gradle/build.gradle.kts), but the licence verdict published here was taken over its pub package dependencies. Nothing was read about its Gradle dependencies' licensing in either direction, and a clean score on this card must not be read as covering 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. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
D22 Internal API Consistency — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. This repository's source is written only in languages whose packages are published through a manifest, and no manifest in the tree makes a publication act: either there is no package manifest of any ecosystem (no package.json, pyproject.toml, setup.py, gemspec, Cargo.toml, pom.xml, build.gradle, composer.json, pubspec.yaml or mix.exs), or every one present declares in its package manager's own terms that it is not published (an npm package marked "private": true, a Cargo package with publish = false, a pubspec with publish_to: none, a Composer "project", a Poetry project with package-mode = false, or the "Private :: Do Not Upload" classifier). With no publication act there is no intentionally-exposed surface for API consistency to be judged over.
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.
P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.
D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
D13 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
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.
D32 Data Compliance (PII/GDPR): PII/GDPR signals are heuristic pattern matches in code — they flag likely handling concerns, not legal compliance, and cannot trace where data actually flows at runtime.
D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (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.
AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
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.
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.
+ 19 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 24 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with AddEditBookingPage.build (cyclomatic 40), AddEditEventPage.build (cyclomatic 40), LoanCard.build (cyclomatic 34). — 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 24 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.
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.
+ 47 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 2 bodies over 60 down to 60 or less in Cognitive Complexity — start with AddEditBookingPage.build (cognitive 75), AddEditEventPage.build (cognitive 67). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 2 together lifts Cognitive Complexity from 6.2 to about 6.5/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes3.3 / 10Weak✓ 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 101 MethodTooLong finding(s) in God Classes — start with REDACTED (6), admin_page.dart (4), detail_page.dart (4). — One of this dimension's main actionable groups (101 warning-level).
Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D4 · Code Duplication3.8 / 10Weak✓ Tool-verified
What it measures: How much of the production code is copy-pasted: the share of production lines inside a reported copy (every copy of a duplicated block or of an edited member, each line once), 10 at none and 0 at a quarter of the lines.
Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), scored on the share of production lines inside a reported copy (each line once; 10 at none, 0 at a quarter). Deterministic.
237 duplicated block group(s) detected. 15.4 % of the production lines (11,260 of 72,900) are in a reported copy. A further 108 rows report members as variants of one another; the share counts each copied line once, however many rows cite it.
+ 151 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 13 Duplicated block (12 lines × 2) finding(s) in Code Duplication — start with detail.dart (2), add_edit_structure_page.dart, order_ui.dart. — One of this dimension's main actionable groups (13 warning-level).
Resolve the 11 Duplicated block (14 lines × 2) finding(s) in Code Duplication — start with search_user.dart, order_ui.dart, add_edit_manager_page.dart. — One of this dimension's main actionable groups (11 warning-level).
Resolve the 10 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with event_list_provider.dart (2), loan_list_provider.dart (2), loaner_list_provider.dart (2). — One of this dimension's main actionable groups (10 warning-level).
Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling10.0 / 10Exemplary✓ Tool-verified
What it measures: Whether volatile projects sit underneath others that depend on them (so their churn ripples upward), and whether project dependencies form cycles. A widely-depended-on but stable shared/kernel project is healthy, not penalised.
Method: Dependency cycles via elementary-DFS over real .csproj references, plus Martin instability (afferent/efferent) per project. Exhaustive over the reference graph, deterministic.
Coverage: Exhaustive · type-level: afferent/efferent coupling + cycles computed over every production type — the population is all types, not a name convention.
3 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; 0 module(s) off the main sequence, with abstractness counted on 2 of the 3 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
What it measures: Whether a class's methods are focused on a single responsibility.
Method: LCOM4 cohesion per production class with at least two methods: connected components of methods sharing state or calls, computed syntactically. Deterministic, not a proxy.
Coverage: Exhaustive · type-level: LCOM4 cohesion computed over every production class — the population is all types, not a name convention.
Resolve the 52 Low cohesion finding(s) in Cohesion (LCOM4) — start with cash_repository.dart (2), delivery_list_repository.dart, loan_repository.dart. — One of this dimension's main actionable groups (52 warning-level).
Detailed fixes: d6_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.
Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.
What it measures: Whether the licenses of third-party packages are compatible with your policy.
Method: Third-party package licenses resolved from declared package metadata and checked against the configured policy (allow/deny/copyleft). Deterministic; clean = no incompatible license found at metadata depth.
0 of 199 resolved pub package(s) use a banned license. Licences were read from pub.dev's analysis of each package's licence file, over every package this repository's pubspec.lock resolves from pub.dev, direct and transitive, at the locked version; the 5 package(s) the lock marks direct dev are excluded, and SDK, path and git packages have no registry release to read. pub.dev analyses only recent releases, so for 99 package(s) locked at an older version the licence read is that of the package's latest analysed release, not of the locked one. 6 of them carry no licence pub.dev recognises; that is missing data, not a violation, and none of them is charged. ★ COVERAGE OF THIS VERDICT: it grades this repository's pub package dependencies and nothing else. The repository also declares a Gradle build (build.gradle/build.gradle.kts), and the licences of those dependencies were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.
What it measures: Files that change often and are also complex — the riskiest hotspots.
Method: Per production file churn times cyclomatic complexity over a rolling window, computed from git and Roslyn/JS/Razor analysis. Exhaustive, deterministic per commit date.
Resolve the 3 Hotspot finding(s) in Churn × Complexity Hotspots — start with loan_card.dart, seller_right_card.dart, transaction_card.dart. — One of this dimension's main actionable groups (3 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 Factor9.9 / 10Exemplary✓ 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.
2 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is lib/purchases/ui/pages/main_page/main_page.dart. Counted over 330 of the 1029 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
Off-boarding risk: anonymized user #1
Further sole-owners (lower concentration)
✓ On the Gold path — maintain.
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.
1 deducted task-comment markers across 72900 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.
What it measures: Whether the project's documentation is clear, complete, and useful.
Method: Every README, docs/ document and root guide parsed by its markup and measured in Unicode letters. Published: a runnable or packaged .NET project whose README (or a document it links, or a root guide) shows no example, and a root README naming none of three or more projects. Overview, licence, boilerplate, wall-of-text, empty-section and XML-doc rows are measured and withheld (counted in gaps) after adjudication. Deterministic, exhaustive, advisory.
1 of 1 documentation facets pass in full. 2 document(s) read across 3 unit(s).
✓ On the Gold path — maintain.
Detailed fixes: d19_recommendation.md.
Do you agree with this assessment?
D20 · ADR Quality0.0 / 10Critical✓ Tool-verified
What it measures: Whether architecture decisions are recorded well (context, decision, consequences).
Method: Every ADR read by its section structure: nine located rules (a missing Decision, Context or Consequences section, a stale status, two records deciding the same question, a dangling supersede link, a number-only title, a single option, no named cost, no status where the log uses one, no enforcement field where the log adopted one), each a fixed deduction from 10; the score is the mean over evaluated records. Deterministic, no model. Advisory.
Resolve the 1 No ADRs found finding(s) in ADR Quality — start with main.dart. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d20_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D26 · Project Cohesion3.3 / 10Weak✓ Tool-verified
What it measures: Whether each project is a focused, coherent unit rather than an oversized grab-bag.
1 of 3 build units (Gradle, Xcode, pub) flagged as possibly oversized/incoherent.
Projects may be oversized for their cohesionpubspec.yaml:1
What to do
Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion — start with pubspec.yaml. — 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.
1 finding(s): 0 critical, 1 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 1 REDACTED finding(s) in Secrets (history) — start with REDACTED. — One of this dimension's main actionable groups (1 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).
30 finding(s): 0 critical, 27 high, 3 medium, 0 low. 20 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. 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
REDACTED
REDACTED
+ 1 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 5 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3), REDACTED, REDACTED. — One of this dimension's main actionable groups (5 issue-level).
Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
No action in Static Analysis (SAST) — all 20 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (20 issue-level, 0 of them charged here).
Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any dependency has a known published vulnerability (CVE), direct or transitive, in ANY ecosystem the repository declares — Dart pub, Elixir and Erlang via Hex, Go modules, Java and Kotlin via Maven/Gradle, JavaScript/npm, .NET/NuGet, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift.
Method: Dependency-CVE scan across every ecosystem the repository declares, scored ONCE. Three sources are unioned and deduplicated by advisory identity (rule id + alias closure, CVE<->GHSA) scoped to package+version, keeping the worst severity: `osv-scanner --recursive` over osv.dev for Dart pub, Elixir/Hex (and Erlang, whose `rebar.lock` syft first converts to a CycloneDX SBOM the scanner reads, with rows attributed back to the lock), Go, Java and Kotlin via Maven/Gradle (and Scala, whose sbt build's pinned direct declarations are written into a CycloneDX SBOM the scanner reads, with rows attributed back to the build file), npm, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift; `trivy fs --scanners vuln` for npm lockfiles; and `dotnet list package --vulnerable --include-transitive` for NuGet (with per-advisory collapse of the project x target-framework fan-out), plus a DECLARED-dependency arm that resolves a published gem's gemspec against rubygems.org where no Gemfile.lock is committed. `SeverityScore(c,h,m,l, normalizer 8.0)`. NotApplicable only when NO ecosystem is readable; if any applicable ecosystem could not be scanned the findings are REPORTED and the score is withheld. Supersedes the npm and OSV arms, retired 2026-09-05. Advisory since rubric-2026.11.2 (CAI decision 0006): every row is a match against a vulnerability database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.
Resolve the 1 High IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 1 Medium IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 Low IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d31_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D32 · Data Compliance (PII/GDPR)9.0 / 10Stronggated by 1 serious finding✓ Tool-verified
What it measures: Likely personal-data (PII / GDPR) handling concerns — logging or storing data without safeguards.
Method: Heuristic PII/GDPR LEAK scan via semgrep across the repo, using our own ruleset: personal data crossing a boundary it should not — reaching a log/console sink, a URL or query string, or unprotected browser storage. Matches map to severity and a 0-10 wide normalizer. A clean sweep is unscored rather than an unearned 10, and is a statement about the leak paths checked only — this dimension does not inventory the personal data a repository holds (the personal-data map and the C1-C5 compliance cards do that), so it never reports that a repository has no personal-data surface. Reported LOUDLY as a measurement gap if the ruleset is missing from the analyzer image. Exhaustive over the leak paths, advisory-leaning; degrades on parse failure.
Resolve the 1 REDACTED finding(s) in Data Compliance (PII/GDPR) — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d32_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether anyone still has living knowledge of each file, or it has been orphaned — last understood long ago by someone now gone quiet. The sibling of the bus factor: D16 asks who owns it, D34 asks whether anyone still knows it.
Method: File orphaning as total living-knowledge decay below one focused-commit's worth within a year, computed per-file from the D16 decay model. Exhaustive, deterministic over fixed history.
225 of 330 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is lib/vote/ui/pages/admin_page/admin_page.dart. Counted over 330 of the 1029 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
Most significant orphaned file · ×3lib/vote/ui/pages/admin_page/admin_page.dart:1
Concentrated knowledge decay
What to do
Resolve the 222 Orphaned file finding(s) in Knowledge Freshness — start with REDACTED (15), constants.dart (8), router.dart (8). — One of this dimension's main actionable groups (222 recommendation-level).
Resolve the 3 Most significant orphaned file finding(s) in Knowledge Freshness — start with admin_page.dart, add_edit_event_page.dart, add_edit_contender.dart. — One of this dimension's main actionable groups (3 recommendation-level).
Resolve the 1 Concentrated knowledge decay 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 1 Boundary-crossing change coupling finding(s) in Change Coupling — start with account_handler.dart. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 19 Change coupling finding(s) in Change Coupling — start with admin_page.dart (3), admin_session_card.dart (2), association_research_bar.dart. — One of this dimension's main actionable groups (19 warning-level).
Resolve the 7 Change-coupling hub finding(s) in Change Coupling — start with REDACTED (2), association_editor_page.dart, add_edit_ph_page.dart. — One of this dimension's main actionable groups (7 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.
+ 1 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 4 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (4 warning-level).
Resolve the 2 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d36_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether 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 2 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.
✓ On the Gold path — maintain.
Detailed fixes: d44_recommendation.md.
Do you agree with this assessment?
Frontend & cross-cutting dimensions
R = React/JS · M = Maturity · P = Readiness.
AC3 · Page structure4.8 / 10Weak✓ Tool-verified
Other · Accessibility — Whether pages declare a language (well-formed BCP-47) and a non-empty title, expose exactly one main landmark and a sane heading order with non-empty headings, keep zoom enabled, title their iframes, give data tables header cells, and avoid meta-refresh. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: html lang, document <title>, a main landmark and heading order on full documents only, plus zoom-disabling viewports, untitled iframes and meta-refresh anywhere. Deterministic, per structural checkpoint.
Coverage: Population: the PARSED MARKUP documents (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx). The page-level checks — lang, title, single main landmark — fire ONCE PER FULL DOCUMENT (an <html> root) and never on a partial or component fragment, so a repo of fragments is assessed only on the per-element checks (heading order, table headers, iframe titles, meta-refresh, zoom). Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en"). — REDACTED:2
What to do
Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
Other · Accessibility — Whether focus outlines aren't removed without a replacement, motion respects prefers-reduced-motion, and literal CSS colour pairs meet contrast — PARTIAL: inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS literals are read (hex/rgb/hsl/named), never computed/runtime/external-CDN colour. Static markup readiness, not a WCAG conformance claim.
Method: Static markup/CSS scan: inline outline:none/0, literal inline colour/background contrast against the 4.5:1 AA floor, and <style>-block animation without a prefers-reduced-motion guard. Deterministic but PARTIAL — only inline styles and in-repo CSS literals are visible.
Coverage: Population: styled elements in the PARSED MARKUP files (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx), plus in-repo <style> blocks, in-repo .css files and CSS-in-JS literals. Colour contrast is computed from LITERAL colour pairs only (hex/rgb/hsl/named, including var() tokens and Tailwind neutral utilities) — computed, runtime-themed and external-CDN colour is never resolved, so this is a partial read of contrast by construction. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
`.container` moves (`animation: anirotate 10s linear infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — REDACTED:43
`.dot:nth-child(1)` moves (`animation: ani1 2s infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — REDACTED:74
`.dot:nth-child(2)` moves (`animation: ani2 2s infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — REDACTED:79
`.dot:nth-child(3)` moves (`animation: ani3 2s infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — REDACTED:84
What to do
Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
Other · Architecture — 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.
Other · Architecture — Whether the project-reference graph is acyclic (cycles block independent build/deploy and signal eroding boundaries).
Method: Project reference cycles via elementary-DFS over real .csproj references, using the engine shared with D5/D7; cyclic versus acyclic. Exhaustive, deterministic.
Other · Architecture — Whether dependencies point inward (Domain ← Application ← Infrastructure/Web) — the clean-architecture dependency rule, checked across the project graph.
Method: Layer violations by name-segment inference (Domain/Core to Application to Infrastructure/Web) over the project-reference graph. Exhaustive over all projects, deterministic.
Other · Architecture — Whether interfaces stay focused rather than fat — the Interface-Segregation principle (SOLID 'I').
Method: Roslyn scan: public interface declared-member counts (accessors fold into their property/event); fat-interface threshold (over 15 declared members) flagged per type. Each finding also reports the distinct-OPERATION count — members counted by name, so an overload group counts once — which decides whether it states the caller-side ISP harm or the implementer-side burden of an overload set. TypeScript: exported interfaces that declare behaviour, counted over their REQUIRED operations (method signatures and function-typed properties with no `?`, once per signature) — data-shape interfaces and ambient .d.ts declarations are outside the population; JavaScript declares no interfaces and is not applicable. Deterministic, type-level.
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.
`KeyService.getKeyPair` is a read-named query yet it performs a durable write on the read path (a persist to a store/repository). A query must stay side-effect-free so reads are safe to retry, cache, and route to a read replica; move the write into a command. — lib/mypayment/tools/key_service.dart:58
What to do
Keep query handlers read-only — move the writes/event-publishes into a command handler so reads stay safe to retry, cache, and route to a read replica.
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.
Maturity · Maturity — Whether the repository and its projects have a README, and whether it is substantive.
Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.
Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.
Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.
No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
What to do
Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
Maturity · Maturity — Whether the repository is organised deliberately: production code and tests are set apart in a way its ecosystem or the repository itself declares.
Method: Filesystem scan: src/test folder separation and namespace-prefix consistency (majority RootNamespace agreement). Exhaustive across projects, deterministic.
Maturity · Maturity — Whether the project's current-state documentation describes the code that exists.
Method: Every current-state document's checkable claims looked up in the tree (links, versions, and artefact counts an order of magnitude off), plus two README checks: an advertised infrastructure product with no footprint, and a module the CHANGELOG records as removed. Deterministic, no model. Advisory.
Only 1/2 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `ios`.
What to do
Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).
Method: Filesystem scan: SAST configuration, dependency-update automation, secret scanning, and a benchmark harness or benchmark step — in this repository's own ecosystem. Exhaustive, deterministic.
No static application security testing detected. For this repository's stack, add the Dart analyzer's security lints plus `semgrep --config=auto` as a CI step. What was searched, so you can tell an absence from a miss: the 7 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — REDACTED:10
`REDACTED` 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. — REDACTED:5
What to do
Add a SAST step to CI running what this repository's stack ships: the Dart analyzer's security lints plus `semgrep --config=auto` — so a security regression fails the build instead of landing.
Dependabot is configured but does not watch `gradle` — add that `package-ecosystem` entry to REDACTED 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 · Readiness — Whether releases are traceable — a maintained changelog and explicit version stamping.
Method: Filesystem scan: changelog file presence and version tags in csproj or git tags. Exhaustive, deterministic.
No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
Readiness · Performance — Whether 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.
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. Markup this repository SHIPS is scored for third-party script integrity whether or not the repository serves it itself, since a page handed to a consumer runs in that consumer’s origin. This repository commits the configuration that serves its own HTTP surface, so that configuration was read in full for the security response headers it sets. 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 (`REDACTED`) 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 REDACTED, `_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.
`https://cdn.jsdelivr.net/npm/pdfjs-dist@4.6.82/build/pdf.min.mjs` is executed by this page with no Subresource Integrity. Whoever can answer that request — the CDN, anyone who compromises it, anyone on the network path — runs arbitrary script in this page's origin, with its session. — REDACTED:136
What to do
Pin third-party scripts and verify them: name an exact version in the URL and add an `integrity="sha384-…"` hash alongside `crossorigin="anonymous"` (both are required — an integrity hash on a cross-origin script without `crossorigin` is not evaluated, it blocks the script). Where the vendor ships a continuously-updated loader and publishes no stable hash (tag managers, analytics, chat widgets), Subresource Integrity is not available: constrain it instead with a `Content-Security-Policy` that names the exact origins allowed to execute, and drop the script from the pages that do not need it. Where the page is shipped inside a package that others host, prefer vendoring the asset and serving it from the app’s own origin, so no consumer inherits a third-party dependency they did not choose.
Other · Code Health — Whether the code avoids sync-over-async (deadlock-prone blocking on tasks) and async void.
Method: Roslyn syntax scan: async methods scanned for .Wait()/.GetAwaiter().GetResult() and async-void outside event handlers. Deterministic, hard fact per invocation.
Other · Code Health — Whether any branch is dead by construction — a switch arm whose label can never equal a case-normalised subject, or an `else if` whose predicate the arm above has already swallowed.
Method: Roslyn syntax + semantics: switch labels compared against the subject's own case normaliser, and if/else-if chains checked for a literal an earlier arm's containment test already swallows. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a loop that shortens a string until it fits a length budget has a floor — one with none grinds the value down to the empty string, or past it into a negative-length `Substring`.
Method: Roslyn syntax + semantics: while/do loops whose body's only effect on a string is to drop its last character, checked for whether anything — a direct comparison on the length, a body guard, a break — bounds that length below. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `while`/`do` loop whose body’s one assignment to a value is `x = x.slice(0, -1)` or `x = x.slice|substring|substr(0, x.length - 1)`, driven by a condition that reads `x.length` only as a term of a larger expression — never compared directly, never tested for truthiness, and with no other read of `x` — and whose body has no `break`, `return`, `throw` or `if` naming `x`. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a type's disposal matches what it OWNS — releasing what it created, leaving alone what it was handed, and not declaring a finalizer for state that has nothing unmanaged to finalize.
Method: Roslyn syntax + semantics: every assignment to a disposable field is read to decide whether the type CREATED the value or was handed it, and the type's disposal is checked against that answer — an injected interface it disposes, a value it constructed and never releases, a finalizer on a type holding nothing unmanaged, and a disposable local whose every reference is a plain member read. A value handed to a container that disposes its contents (a parent control's `Controls` collection, a component `IContainer`) is released by that container and is not reported; generated code is out of population. On a repository with no .NET source the same ownership questions are read in JavaScript/TypeScript off the engine’s own token stream (test, vendored, generated and minified paths not): a class declaring `dispose()`, `[Symbol.dispose]()` or `[Symbol.asyncDispose]()` that disposes a field it was handed through a constructor parameter typed as a repository interface or resolved by a dependency-injection container; that assigns a field only ever from `new X(…)` of a disposable class and neither releases it anywhere in the class nor names it in its disposal member or a method that member calls, nor hands it to anything else; and a `const`/`let` local built from literals only whose every reference opens a statement operating on a non-release member of it. A class is disposable when every repository declaration of its name declares or inherits a disposal member, or when it is a documented library disposable (`vscode` EventEmitter, CancellationTokenSource and Disposable; three.js geometries, materials, textures, render targets, renderers, controls and composers). The finalizer arm has no JavaScript counterpart: a class cannot declare one. Dart is read for the owned-and-never-released arm: a Flutter `State` (or a class declaring `dispose()`/`close()`) whose library-private field is written only with direct creations of a framework controller, `FocusNode`, `StreamController` or periodic `Timer` (or a `.listen(…)` into a field declared `StreamSubscription`), which nothing in the class or its library releases (`dispose`/`close`/`cancel`) and which is never handed on except as a named argument. Ruby is read for the owned-and-never-released arm and the abandoned-local arm: a class declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose instance variable is written only with a blockless core descriptor creation (`File.open`/`new`, `Tempfile`, `Dir.open`, `IO.popen`, the `socket` and `openssl` socket classes) that no method of the class closes and that is never handed on (passed, returned, stored, exposed by `attr_reader`, delegated) — a class whose superclass or mixin lies outside the repository is not judged — and a blockless creation read through and dropped (`File.open(path).read`) or held in a local that is never closed, returned, passed or stored (a `&:read` block-pass, an `autoclose: false` borrow and a `fileno` hand-over are not abandonment). PHP is read for the same two arms: a class (not a trait, and not one using a trait) declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose `private` property (or a `final` class's `protected` one) is written only with a direct core `fopen`, `tmpfile`, `popen`, `proc_open`, `fsockopen`, `stream_socket_client`/`server` or `opendir` that nothing in the class closes (`fclose`, `pclose`, `closedir`, `unset`, a reset to `null`) and that is never handed on, and a handle held in a function's local, or read through as the argument of a reader, that is never closed, returned, passed, captured or stored; a `php://` stream, `curl_init`, `SplFileObject`, `PDO` and a function the repository declares under the core name are not read. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X27 · Collection changed while being enumerated10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — 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?
X29 · Per-element action decided by a fixed element10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a decision taken once per element is taken ABOUT that element — a test inside a counted loop that reads a fixed subscript of the very collection its guarded statement indexes by the loop variable applies element zero's answer to all of them, so the elements that differ from it are all handled wrongly, and in the same direction.
Method: Roslyn syntax only, no semantic model: every `for` statement declaring exactly ONE loop variable, and every `if` inside its body that is not under a nested loop or a lambda. A site enters the population when the `if`’s condition never mentions the loop variable while the statement it guards indexes some collection by that variable ALONE (`c[i]`; `c[i + 1]` and `c[i, j]` are outside it). A finding additionally needs the AGREEING TWIN at the same-collection grain: the condition must read THAT SAME collection at a subscript that does not move — written into the condition, or reached through a local declared BEFORE the loop, so an alias bound inside the body is not followed. Both collection expressions must be simple identifiers. On a repository with no .NET source the same rule reads JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `for (let|var|const x = …; …; …)` with one declarator and a braced body, an alias followed only when it is declared before the loop in a block that encloses it and never assigned inside the loop. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether exceptions are handled rather than silently swallowed or rethrown with lost stack traces.
Method: Roslyn syntax scan: every catch clause counted; empty catches and bare rethrows flagged. Population is all catch clauses, not estimated. Deterministic, hard fact.
`catch (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) — lib/vote/repositories/status_repository.dart:21, lib/vote/repositories/status_repository.dart:30, lib/vote/repositories/status_repository.dart:39, …
`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. — lib/tools/functions.dart:588
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. — lib/tools/web-window-callback/js_interop.dart:36
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.
Do you agree with this assessment?
WCAG coverage — what static analysis assessed
Statically assessed 8 of 55 WCAG 2.2 Level A/AA success criteria (15%; ≈16% of the 50 WCAG 2.1 AA criteria for EN 301 549). The other 47 require runtime or manual evaluation. Partial signal only (a clean result is necessary, not sufficient; static analysis fully verifies none). This is accessibility readiness, not a conformance claim — a WCAG conformance claim requires manual evaluation (WCAG-EM 1.0).
The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.
Unscored — 2 check(s) recorded observations but carry no score
These checks ran and found something, but they do not carry a score — either by design (an advisory check reports evidence rather than grading it) or because they could not be scored here. They are excluded from the score for that reason, not because there was nothing to see.
P12 CI test-gate honesty — 1 observation(s) recorded · Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
X10 Duplicated predicate — 12 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 1 control(s) we could not find positive evidence for
These checks grade a working control, and the repository shows no evidence of one. That is deliberately not scored as a zero: a repository cannot show an ops runbook, a database TTL or an infrastructure-side audit log, so absence of evidence here is not evidence the control is missing. It is also not a statement that the check is irrelevant to this codebase — the thing it grades applies; we just could not see it. Excluded from the score either way.
P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 66 check(s) not relevant to this codebase
These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.
AC1 Text alternatives — No image/media element found in the parsed markup — AC1 not applicable here.
AC2 Forms & labels — No form control/button found in the parsed markup — AC2 not applicable here.
AC4 Keyboard semantics — No interactive element found in the parsed markup — AC4 not applicable here.
AC5 ARIA correctness — No ARIA usage found in the parsed markup — AC5 not applicable here.
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 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
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
AX8 Test isolation — no test/production split to check
AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
AXR1 Runtime accessibility — docker build failed (exit 1) — 3 | >>> COPY ./build/web/ /app/html 4 | RUN find /app/html/ -type f -size +512c -regex '.*\.\(html\|css\|js\|json\|svg\|ttf\|otf\|woff2\|wasm\|mjs\|symbols\|yaml\|env\)' -exec gzip -k9 {} + -------------------- ERROR: failed to solve: failed to compute cache key: failed to calculate checksum of ref fa603d9f-6c3c-47df-a784-90278ae2b00e::ra48xmlp7gy68ttqer0c5579f: "/build/web": not found; likely cause (the repository): a file the REDACTED copies (`build/web`) is not in the repository's build context (it may be produced by a build step outside the REDACTED, or excluded by .dockerignore); runtime evidence skipped The cause is in the repository, not in our sandbox: a file the REDACTED copies (`build/web`) is not in the repository's build context (it may be produced by a build step outside the REDACTED, or excluded by .dockerignore). Nothing here says the surface is inaccessible, only that it was never rendered.
C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Drift table, an Isar, ObjectBox, Floor or Hive entity, or a Serverpod table model — and no database or data-store client (sqflite, Drift, Isar, Hive, Realm, Firestore, Supabase, postgres, …) in the source either, so this repository keeps no data at rest for these controls to protect.
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.
C3 Audit Trail — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Drift table, an ObjectBox/Floor @Entity, an Isar @collection, a Hive @HiveType or a Serverpod table model — and no database or data-store client (sqflite, Firestore, Supabase, postgres, …) imported either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a hosted backend configured outside this repository, for instance), the trail belongs to wherever that data is stored.
C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Drift table, an ObjectBox/Floor @Entity, an Isar @collection, a Hive @HiveType or a Serverpod table model — and no database or data-store client (sqflite, Firestore, Supabase, postgres, …) imported either, so this repository keeps no personal data whose lifetime a retention limit would bound.
C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Drift table, an ObjectBox/Floor @Entity, an Isar @collection, a Hive @HiveType or a Serverpod table model — and no database or data-store client (sqflite, Firestore, Supabase, postgres, …) imported either, so this repository keeps no personal data for a data subject to erase, export or consent over.
D10 Test Quality — ~8585 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 — 2 Maven/Gradle manifest(s) were read, stating a version for 0 dependency(ies) and leaving 0 to a parent or an imported BOM, but no build resolved the dependency graph, so the outdated signal was not established. NOT a finding that these dependencies are current or healthy.
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 — D21 withholds its sibling role token rows: 1 candidate(s) found and not reported.
D22 Internal API Consistency — No intentionally-exposed public API to evaluate for consistency.
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, .swift source were not judged.
D25 ADR Conformance — no ADRs to check
D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.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.
D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
D8 Code Coverage — Coverage not included — suite not readable by the collector
DM1 Aggregate boundaries — not scored for Dart: aggregate-vs-value-object classification cannot be told apart in source (every class-holding-class reads alike), and a child COLLECTION (legitimate membership) vs a single embedded aggregate is indistinguishable — reported as guidance rather than measured
DM2 Strongly-typed ids — no in-repo typed-id idiom — primitive-obsession recorded as advisory DM8, DM2 not gated
DM3 Integration-event coupling — not scored for Dart: a cross-package domain leak cannot be told apart in source from a legitimate shared-kernel package, and most repositories ship a single package — reported as guidance rather than measured
DM4 Rich vs anemic domain model — this Dart repository declares no domain-layer entity carrying stored data (every type is a typed-id wrapper, DTO/config, ORM row or presentation container), so DM4's rich-vs-anemic read has no population to be taken over
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 — not scored for Dart: 'a repository per CHILD entity' needs the aggregate-root structure, which is not source-resolvable — 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, 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
P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the Dart, JVM, JavaScript/TypeScript, 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 — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for 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.
PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X2 Cancellation propagation — no C# was loaded; this repository's Dart was read, and no request in it can be cancelled by a caller (Dio, or package:http's Abortable requests) — package:http's get and post, HttpClient and Firebase or gRPC stubs offer their callers no token to take
X20 Mistyped argument guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X21 Side-effecting pattern guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X24 Document value interpolated into markup unescaped — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X25 Inert configuration knob — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
X4 Structured logging — This check asks whether log calls keep a message's values apart from its text, which needs a logger that can carry them as fields. This repository's 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.
X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
The findings behind the scores, grouped by severity, then by dimension and kind. The high-severity issues are enumerated in full below; items per group are capped at 25 with any overflow stated explicitly per group, never silently truncated. The complete machine-readable list of every finding (all severities) is the companion findings.md in this report's bundle.
<html> without a lang REDACTED:2— The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
AX9 · CQS / query purity· Query writes persistent state on the read path · ×1
Query writes persistent state on the read path: KeyService.getKeyPair lib/mypayment/tools/key_service.dart:58— `KeyService.getKeyPair` is a read-named query yet it performs a durable write on the read path (a persist to a store/repository). A query must stay side-effect-free so reads are safe to retry, cache, and route to a read replica; move the write into a command.
Boundary-crossing change coupling: account_handler.dart ↔ on_going_loan.dart lib/amap/ui/pages/admin_page/account_handler.dart:1— `lib/amap/ui/pages/admin_page/account_handler.dart` (context amap) and `lib/loan/ui/pages/admin_page/on_going_loan.dart` (context loan) sit in DIFFERENT parts of the tree yet 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 — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 8 shared commits counted here, the most recent 3 are `58e8629e` fix searchbar; `72af4332` Using ListView.builder instead of Row; `ef7fe54a` Refacto search_bar — run `git show` on any of them.
MethodTooLong: AddEditEventPage.build lib/event/ui/pages/event_pages/add_edit_event_page.dart:32— MethodTooLong — build runs 388 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 288 over it, 3.88× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: AdminPage.build lib/vote/ui/pages/admin_page/admin_page.dart:33— MethodTooLong — build runs 386 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 286 over it, 3.86× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: AddEditBookingPage.build lib/booking/ui/pages/booking_pages/add_edit_booking_page.dart:39— MethodTooLong — build runs 361 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 261 over it, 3.61× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: AddEditContenderPage.build lib/vote/ui/pages/contender_pages/add_edit_contender.dart:38— MethodTooLong — build runs 309 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 209 over it, 3.09× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: ScanPage.build lib/mypayment/ui/pages/scan_page/scan_page.dart:27— MethodTooLong — build runs 299 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 199 over it, 2.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: DeliveryUi.build lib/amap/ui/pages/admin_page/delivery_ui.dart:28— MethodTooLong — build runs 290 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 190 over it, 2.90× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: EditUserPage.build lib/settings/ui/pages/edit_user_page/edit_user_page.dart:28— MethodTooLong — build runs 279 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 179 over it, 2.79× 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: AddEditSpeciesPage.build lib/seed-library/ui/pages/add_edit_species_page/add_edit_species_page.dart:23— MethodTooLong — build runs 252 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 152 over it, 2.52× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: CreationPage.build lib/raffle/ui/pages/creation_edit_page/creation_edit_page.dart:37— MethodTooLong — build runs 251 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 151 over it, 2.51× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: AssociationInformationEditor.build lib/phonebook/ui/pages/association_editor_page/association_information_editor.dart:23— MethodTooLong — build runs 248 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 148 over it, 2.48× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: AddEditSessionPage.build lib/cinema/ui/pages/session_pages/add_edit_session.dart:29— MethodTooLong — build runs 241 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 141 over it, 2.41× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: DetailPage.build lib/cinema/ui/pages/detail_page/detail_page.dart:24— MethodTooLong — build runs 239 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 139 over it, 2.39× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: EmailChangeDialog.build lib/drawer/ui/email_change_popup.dart:28— MethodTooLong — build runs 235 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 135 over it, 2.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: EventUi.build lib/event/ui/components/event_ui.dart:35— 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: AssociationEditorPage.build lib/phonebook/ui/pages/association_editor_page/association_editor_page.dart:35— MethodTooLong — build runs 230 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 130 over it, 2.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: AddEditStructurePage.build lib/admin/ui/pages/structure_page/add_edit_structure_page/add_edit_structure_page.dart:27— MethodTooLong — build runs 227 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 127 over it, 2.27× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: AdvertCard.build lib/advert/ui/components/advert_card.dart:21— MethodTooLong — build runs 225 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 125 over it, 2.25× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: SellerRightCard.build lib/mypayment/ui/pages/store_admin_page/seller_right_card.dart:24— MethodTooLong — build runs 222 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 122 over it, 2.22× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: SettingsMainPage.build REDACTED:30— MethodTooLong — build runs 220 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 120 over it, 2.20× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: DevicesPage.build lib/mypayment/ui/pages/devices_page/devices_page.dart:30— MethodTooLong — build runs 214 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 114 over it, 2.14× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: AdvertAddEditAdvertPage.build lib/advert/ui/pages/form_page/add_edit_advert_page.dart:30— MethodTooLong — build runs 211 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 111 over it, 2.11× 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: DrawerTopBar.build lib/drawer/ui/drawer_top_bar.dart:26— MethodTooLong — build runs 208 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 108 over it, 2.08× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: ConfirmPaymentDialog.build lib/raffle/ui/pages/raffle_page/confirm_payment.dart:28— MethodTooLong — build runs 207 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 107 over it, 2.07× 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: AmapMainPage.build lib/amap/ui/pages/main_page/main_page.dart:34— MethodTooLong — build runs 206 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 106 over it, 2.06× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: ToolBar.build lib/mypayment/ui/pages/store_stats_page/tool_bar.dart:20— MethodTooLong — build runs 201 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 101 over it, 2.01× 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.
Low cohesion: DeliveryListRepository (LCOM4 10) lib/amap/repositories/delivery_list_repository.dart:7— DeliveryListRepository's methods fall into 10 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 10 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: LoanRepository (LCOM4 9) lib/loan/repositories/loan_repository.dart:6— LoanRepository's methods fall into 9 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 9 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: StructuresRepository (LCOM4 9) lib/mypayment/repositories/structures_repository.dart:8— StructuresRepository's methods fall into 9 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 9 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: PlantsRepository (LCOM4 9) lib/seed-library/repositories/plants_repository.dart:8— PlantsRepository's methods fall into 9 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 9 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: BookingRepository (LCOM4 8) lib/booking/repositories/booking_repository.dart:7— BookingRepository's methods fall into 8 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 8 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: EventRepository (LCOM4 8) lib/event/repositories/event_repository.dart:6— EventRepository's methods fall into 8 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 8 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: GroupRepository (LCOM4 7) lib/admin/repositories/group_repository.dart:8— GroupRepository's methods fall into 7 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 7 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: RaffleRepository (LCOM4 7) lib/raffle/repositories/raffle_repositories.dart:4— RaffleRepository's methods fall into 7 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 7 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: UserRepository (LCOM4 7) lib/user/repositories/user_repository.dart:6— UserRepository's methods fall into 7 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 7 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: PermissionRepository (LCOM4 6) lib/admin/repositories/permission_repository.dart:4— PermissionRepository'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: AnnouncerRepository (LCOM4 6) lib/advert/repositories/announcer_repository.dart:4— AnnouncerRepository'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: UserOrderListNotifier (LCOM4 6) lib/amap/providers/user_order_list_provider.dart:11— UserOrderListNotifier'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: LoanerRepository (LCOM4 6) lib/loan/repositories/loaner_repository.dart:6— LoanerRepository'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: InvoiceRepository (LCOM4 6) lib/mypayment/repositories/invoices_repository.dart:31— InvoiceRepository'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: AssociationRepository (LCOM4 6) lib/phonebook/repositories/association_repository.dart:4— AssociationRepository'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: LotRepository (LCOM4 6) lib/raffle/repositories/prize_repository.dart:5— LotRepository'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: LotRepository (LCOM4 6) lib/raffle/repositories/prizes_repository.dart:5— LotRepository'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: SpeciesRepository (LCOM4 6) lib/seed-library/repositories/species_repository.dart:7— SpeciesRepository'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: NotificationRepository (LCOM4 6) lib/service/repositories/notification_repository.dart:7— NotificationRepository'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: StatusRepository (LCOM4 6) lib/vote/repositories/status_repository.dart:8— StatusRepository'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: AssociationMembershipRepository (LCOM4 5) lib/admin/repositories/association_membership_repository.dart:8— AssociationMembershipRepository'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: AssociationMembershipUserRepository (LCOM4 5) lib/admin/repositories/association_membership_user_repository.dart:7— AssociationMembershipUserRepository'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: SchoolRepository (LCOM4 5) lib/admin/repositories/school_repository.dart:6— SchoolRepository'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: AdvertRepository (LCOM4 5) lib/advert/repositories/advert_repository.dart:4— AdvertRepository'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: OrderListRepository (LCOM4 5) lib/amap/repositories/order_list_repository.dart:6— OrderListRepository'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.
Change coupling: association_research_bar.dart ↔ research_bar.dart lib/phonebook/ui/pages/admin_page/association_research_bar.dart:1— `lib/phonebook/ui/pages/admin_page/association_research_bar.dart` and `lib/phonebook/ui/pages/main_page/research_bar.dart` change together 100% of the time (11 of the 11 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 11 shared commits counted here, the most recent 3 are `05d3e897` fix: filtering is managed by it's own provider; `0aa3aa85` Fix: Update to refacto and bug fix; `190e29ee` lint: apply new linting — run `git show` on any of them.
Change coupling: add_edit_contender.dart ↔ detail_page.dart lib/vote/ui/pages/contender_pages/add_edit_contender.dart:1— `lib/vote/ui/pages/contender_pages/add_edit_contender.dart` and `lib/vote/ui/pages/detail_page/detail_page.dart` change together 85% of the time (11 of the 13 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 11 shared commits counted here, the most recent 3 are `2bc8013a` fix: update on vote; `4986e79d` Refacto vote; `a3582bb7` Changin vote routing (at that commit the file was still `lib/vote/ui/pages/pretendance_pages/add_edit_pretendance.dart`) — run `git show` on any of them.
Change coupling: item_card.dart ↔ loan_card.dart lib/loan/ui/pages/admin_page/item_card.dart:1— `lib/loan/ui/pages/admin_page/item_card.dart` and `lib/loan/ui/pages/admin_page/loan_card.dart` change together 79% of the time (11 of the 14 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency between them. They sit in the same directory, but in this ecosystem each file is its own module — a sibling reference still needs an import — so the missing import edge is real: the coupling runs through shared behaviour, not a declared dependency. If they duplicate structure, extract the common part into one unit; otherwise the coupling is hidden and worth breaking. You can check this without leaving the row: of the 11 shared commits counted here, the most recent 3 are `996cddf5` feat: resizing cards; `28f3c09e` Adding Hero for page transition animation on card layout; `7a846ab8` Refacto card_layout — run `git show` on any of them.
Change coupling: ph_list.dart ↔ view_ph.dart lib/ph/ui/pages/past_ph_selection_page/ph_list.dart:1— `lib/ph/ui/pages/past_ph_selection_page/ph_list.dart` and `lib/ph/ui/pages/view_ph/view_ph.dart` change together 77% of the time (10 of the 13 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 10 shared commits counted here, the most recent 3 are `d642d7c7` Revert "Merge pull request #394 from aeecleclair/fix/ph"; `90b68a25` fix the module for android by removing pdfx package; `dd23d106` fix : format — run `git show` on any of them.
Change coupling: admin_page.dart ↔ REDACTED lib/booking/ui/pages/admin_pages/admin_page.dart:1— `lib/booking/ui/pages/admin_pages/admin_page.dart` and `lib/booking/ui/pages/main_page/main_page.dart` change together 66% of the time (25 of the 38 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 25 shared commits counted here, the most recent 3 are `a3b177e4` expand calendar if the height of the screen allows it; `87359bb9` fix refresh issue when adding a reservation for a room we don't manage; `02205c59` use a new endpoint to show on manager page calendar only bookings tha… — run `git show` on any of them.
Change coupling: admin_session_card.dart ↔ detail_page.dart lib/cinema/ui/pages/admin_page/admin_session_card.dart:1— `lib/cinema/ui/pages/admin_page/admin_session_card.dart` and `lib/cinema/ui/pages/detail_page/detail_page.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 — 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 `dea2b65d` fix: update on cinema; `34d32005` optimization: use select on providers; `b64772d0` Removing ToggleMapNotifier — run `git show` on any of them.
Change coupling: admin_session_card.dart ↔ session_card.dart lib/cinema/ui/pages/admin_page/admin_session_card.dart:1— `lib/cinema/ui/pages/admin_page/admin_session_card.dart` and `lib/cinema/ui/pages/main_page/session_card.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 — 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 `dea2b65d` fix: update on cinema; `34d32005` optimization: use select on providers; `d93a361e` fix: Fixing cinema UI — run `git show` on any of them.
Change coupling: group_ui.dart ↔ REDACTED lib/admin/ui/pages/groups/group_page/group_ui.dart:1— `lib/admin/ui/pages/groups/group_page/group_ui.dart` and `lib/admin/ui/pages/main_page/main_page.dart` change together 62% of the time (10 of the 16 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 10 shared commits counted here, the most recent 3 are `0bebeb42` Add Schools system (#447) (at that commit the file was still `lib/admin/ui/pages/group_page/group_ui.dart`); `9cba17d9` Adding shrinkbutton where possible (at that commit the file was still `lib/admin/ui/pages/main_page/asso_ui.dart`); `d9bc5cc1` Update admin edit page (at that commit the file was still `lib/admin/ui/pages/main_page/asso_ui.dart`) — run `git show` on any of them.
Change coupling: ph_list_provider.dart ↔ admin_ph_card.dart lib/ph/providers/ph_list_provider.dart:1— `lib/ph/providers/ph_list_provider.dart` and `lib/ph/ui/pages/admin_page/admin_ph_card.dart` change together 60% of the time (6 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `e669caf0` fix : format; `aae7a8cc` Fix edit and delete; `8d0b8e49` Adding delete option (at that commit the file was still `lib/ph/ui/pages/admin_page/ph_card.dart`) — run `git show` on any of them.
Change coupling: admin_page.dart ↔ association_creation_page.dart lib/phonebook/ui/pages/admin_page/admin_page.dart:1— `lib/phonebook/ui/pages/admin_page/admin_page.dart` and `lib/phonebook/ui/pages/association_creation_page/association_creation_page.dart` change together 56% of the time (9 of the 16 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 9 shared commits counted here, the most recent 3 are `cbcc484e` remove call to non existing endpoint; `b6270009` refacto: add components folder; `54b236c6` refacto: KindsBar — run `git show` on any of them.
Change coupling: on_going_loan.dart ↔ REDACTED lib/loan/ui/pages/admin_page/on_going_loan.dart:1— `lib/loan/ui/pages/admin_page/on_going_loan.dart` and `lib/loan/ui/pages/main_page/main_page.dart` change together 56% of the time (10 of the 18 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 10 shared commits counted here, the most recent 3 are `e31bc837` Added late loan count on admin page and main page (#709); `72af4332` Using ListView.builder instead of Row; `aecffb7f` Using Horizontal list view — run `git show` on any of them.
Change coupling: association_list_provider.dart ↔ association_research_bar.dart lib/phonebook/providers/association_list_provider.dart:1— `lib/phonebook/providers/association_list_provider.dart` and `lib/phonebook/ui/pages/admin_page/association_research_bar.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 — 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 `05d3e897` fix: filtering is managed by it's own provider; `0aa3aa85` Fix: Update to refacto and bug fix; `0fcc38ab` UI improvement and member list fix — run `git show` on any of them.
Change coupling: detail_page.dart ↔ REDACTED lib/vote/ui/pages/detail_page/detail_page.dart:1— `lib/vote/ui/pages/detail_page/detail_page.dart` and `lib/vote/ui/pages/main_page/main_page.dart` change together 54% of the time (7 of the 13 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `2bc8013a` fix: update on vote; `a3582bb7` Changin vote routing; `37630294` Fixing vote update + Fixing is_admin (now based on uuid) + Adding lis… — run `git show` on any of them.
Change coupling: ph_card.dart ↔ view_ph.dart lib/ph/ui/pages/past_ph_selection_page/ph_card.dart:1— `lib/ph/ui/pages/past_ph_selection_page/ph_card.dart` and `lib/ph/ui/pages/view_ph/view_ph.dart` change together 54% of the time (7 of the 13 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `d642d7c7` Revert "Merge pull request #394 from aeecleclair/fix/ph"; `90b68a25` fix the module for android by removing pdfx package; `dd23d106` fix : format — run `git show` on any of them.
Change coupling: member_card.dart ↔ membership_editor_page.dart lib/phonebook/ui/pages/association_page/member_card.dart:1— `lib/phonebook/ui/pages/association_page/member_card.dart` and `lib/phonebook/ui/pages/membership_editor_page/membership_editor_page.dart` change together 53% of the time (8 of the 15 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 8 shared commits counted here, the most recent 3 are `6295855c` Fix phonebook and CoreGroup associated with Association (#351); `12a98aac` fix: memberships; `0aa3aa85` Fix: Update to refacto and bug fix — run `git show` on any of them.
Change coupling: admin_page.dart ↔ research_bar.dart lib/phonebook/ui/pages/admin_page/admin_page.dart:1— `lib/phonebook/ui/pages/admin_page/admin_page.dart` and `lib/phonebook/ui/pages/main_page/research_bar.dart` change together 53% of the time (8 of the 15 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 8 shared commits counted here, the most recent 3 are `05d3e897` fix: filtering is managed by it's own provider; `0aa3aa85` Fix: Update to refacto and bug fix; `190e29ee` lint: apply new linting — run `git show` on any of them.
Change coupling: function.dart ↔ membership_editor_page.dart lib/phonebook/tools/function.dart:1— `lib/phonebook/tools/function.dart` and `lib/phonebook/ui/pages/membership_editor_page/membership_editor_page.dart` change together 53% of the time (9 of the 17 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 9 shared commits counted here, the most recent 3 are `6295855c` Fix phonebook and CoreGroup associated with Association (#351); `9e90fbb3` fix: sorting for member is done on it's own provider; `03e15451` fix: simplify membership add edit checkbox behavior — run `git show` on any of them.
Change coupling: main.dart ↔ no_internet_page.dart lib/main.dart:1— `lib/main.dart` and `lib/others/ui/no_internet_page.dart` change together 50% of the time (8 of the 16 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 8 shared commits counted here, the most recent 3 are `2dd11330` [.env] Minimal Hyperion Version (#480); `c868ec83` Changing cache library (at that commit the file was still `lib/others/ui/no_internert_page.dart`); `eb02367e` Fixing reloading with connection (at that commit the file was still `lib/others/ui/no_internert_page.dart`) — run `git show` on any of them.
Change coupling: router.dart ↔ ph_list.dart lib/ph/router.dart:1— `lib/ph/router.dart` and `lib/ph/ui/pages/past_ph_selection_page/ph_list.dart` change together 50% of the time (8 of the 16 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 8 shared commits counted here, the most recent 3 are `d642d7c7` Revert "Merge pull request #394 from aeecleclair/fix/ph"; `90b68a25` fix the module for android by removing pdfx package; `fef6686a` fix : format — run `git show` on any of them.
Duplicated block (12 lines × 2) lib/admin/ui/pages/structure_page/add_edit_structure_page/add_edit_structure_page.dart:256— lib/admin/ui/pages/structure_page/add_edit_structure_page/add_edit_structure_page.dart:256-267 | lib/admin/ui/pages/structure_page/add_edit_structure_page/add_edit_structure_page.dart:274-285 — 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) lib/advert/ui/pages/detail_page/detail.dart:88— lib/advert/ui/pages/detail_page/detail.dart:88-99 | lib/cinema/ui/pages/detail_page/detail_page.dart:111-122 — before extracting anything, compare `lib/advert/ui/pages/detail_page/detail.dart` and `lib/cinema/ui/pages/detail_page/detail_page.dart` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 38 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `lib/advert/ui/pages/detail_page/detail.dart:88` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (12 lines × 2) lib/advert/ui/pages/detail_page/detail.dart:155— lib/advert/ui/pages/detail_page/detail.dart:155-167 | lib/cinema/ui/pages/detail_page/detail_page.dart:195-206 — before extracting anything, compare `lib/advert/ui/pages/detail_page/detail.dart` and `lib/cinema/ui/pages/detail_page/detail_page.dart` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 38 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `lib/advert/ui/pages/detail_page/detail.dart:155` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (12 lines × 2) lib/amap/ui/components/order_ui.dart:160— lib/amap/ui/components/order_ui.dart:160-171 | lib/amap/ui/pages/detail_delivery_page/order_detail_ui.dart:137-148 — before extracting anything, compare `lib/amap/ui/components/order_ui.dart` and `lib/amap/ui/pages/detail_delivery_page/order_detail_ui.dart` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 49 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `lib/amap/ui/components/order_ui.dart:160` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) lib/amap/ui/pages/admin_page/adding_user_card.dart:33— lib/amap/ui/pages/admin_page/adding_user_card.dart:33-44 | lib/raffle/ui/pages/admin_module_page/adding_user_card.dart:29-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. Read the line range as the matched WINDOW rather than a finished unit: at `lib/amap/ui/pages/admin_page/adding_user_card.dart:33` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (12 lines × 2) lib/amap/ui/pages/admin_page/user_cash_ui.dart:148— lib/amap/ui/pages/admin_page/user_cash_ui.dart:148-159 | lib/raffle/ui/pages/creation_edit_page/user_cash_ui.dart:222-233 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `lib/amap/ui/pages/admin_page/user_cash_ui.dart:148` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) lib/home/ui/day_card.dart:83— lib/home/ui/day_card.dart:83-94 | lib/home/ui/day_card.dart:99-110 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `lib/home/ui/day_card.dart:83` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (12 lines × 2) lib/mypayment/ui/pages/main_page/account_card/device_dialog_box.dart:57— lib/mypayment/ui/pages/main_page/account_card/device_dialog_box.dart:57-68 | lib/mypayment/ui/pages/store_admin_page/seller_right_dialog.dart:58-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 (12 lines × 2) lib/raffle/ui/pages/pack_ticket_page/add_edit_pack_ticket_page.dart:37— lib/raffle/ui/pages/pack_ticket_page/add_edit_pack_ticket_page.dart:37-48 | lib/raffle/ui/pages/prize_page/add_edit_prize_page.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. Read the line range as the matched WINDOW rather than a finished unit: at `lib/raffle/ui/pages/pack_ticket_page/add_edit_pack_ticket_page.dart:37` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) lib/settings/ui/pages/log_page/log_tab.dart:25— lib/settings/ui/pages/log_page/log_tab.dart:25-36 | lib/settings/ui/pages/log_page/notification_tab.dart:25-36 — before extracting anything, compare `lib/settings/ui/pages/log_page/log_tab.dart` and `lib/settings/ui/pages/log_page/notification_tab.dart` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 65 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `lib/settings/ui/pages/log_page/log_tab.dart:25` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (12 lines × 2) lib/tools/constants.dart:107— lib/tools/constants.dart:107-118 | lib/tools/constants.dart:134-145 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `lib/tools/constants.dart:107` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (12 lines × 2) lib/vote/ui/pages/admin_page/contender_card.dart:58— lib/vote/ui/pages/admin_page/contender_card.dart:58-69 | lib/vote/ui/pages/main_page/contender_card.dart:183-195 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `lib/vote/ui/pages/admin_page/contender_card.dart:58` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) lib/admin/providers/association_membership_list_provider.dart:44— lib/admin/providers/association_membership_list_provider.dart:44-55 | lib/phonebook/providers/association_groupement_list_provider.dart:48-59 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Swallowed exception (caught, then discarded) lib/vote/repositories/status_repository.dart:21— `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) lib/vote/repositories/status_repository.dart:30— `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) lib/vote/repositories/status_repository.dart:39— `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) lib/vote/repositories/status_repository.dart:48— `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) lib/vote/repositories/status_repository.dart:57— `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) lib/user/repositories/user_repository.dart:48— `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) lib/user/repositories/user_repository.dart:56— `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) lib/user/providers/profile_picture_provider.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) lib/user/providers/profile_picture_provider.dart:99— `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) lib/tools/functions.dart:588— `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) lib/phonebook/providers/complete_member_provider.dart:33— `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) lib/mypayment/tools/platform_info.dart:19— `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) lib/auth/providers/is_connected_provider.dart:14— `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.
Duplicated block (14 lines × 2) lib/admin/ui/pages/structure_page/add_edit_structure_page/search_user.dart:31— lib/admin/ui/pages/structure_page/add_edit_structure_page/search_user.dart:31-44 | lib/mypayment/ui/pages/transfer_structure_page/transfer_structure_page.dart:30-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. Read the line range as the matched WINDOW rather than a finished unit: at `lib/admin/ui/pages/structure_page/add_edit_structure_page/search_user.dart:31` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14 lines × 2) lib/amap/ui/components/order_ui.dart:193— lib/amap/ui/components/order_ui.dart:193-206 | lib/amap/ui/components/product_ui.dart:95-108 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `lib/amap/ui/components/order_ui.dart:193` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14 lines × 2) lib/booking/ui/pages/admin_pages/add_edit_manager_page.dart:138— lib/booking/ui/pages/admin_pages/add_edit_manager_page.dart:138-151 | lib/booking/ui/pages/admin_pages/add_edit_room_page.dart:136-149 — before extracting anything, compare `lib/booking/ui/pages/admin_pages/add_edit_manager_page.dart` and `lib/booking/ui/pages/admin_pages/add_edit_room_page.dart` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 72 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `lib/booking/ui/pages/admin_pages/add_edit_manager_page.dart:138` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (14 lines × 2) lib/booking/ui/pages/manager_page/list_booking.dart:58— lib/booking/ui/pages/manager_page/list_booking.dart:58-71 | lib/event/ui/pages/admin_page/list_event.dart:50-63 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `lib/booking/ui/pages/manager_page/list_booking.dart:58` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (14 lines × 2) lib/loan/ui/pages/admin_page/loan_history.dart:53— lib/loan/ui/pages/admin_page/loan_history.dart:53-66 | lib/loan/ui/pages/admin_page/on_going_loan.dart:73-86 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `lib/loan/ui/pages/admin_page/loan_history.dart:53` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (14 lines × 2) lib/loan/ui/pages/loan_group_page/add_edit_loan_page.dart:85— lib/loan/ui/pages/loan_group_page/add_edit_loan_page.dart:85-98 | lib/mypayment/ui/pages/store_admin_page/store_admin_page.dart:125-138 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `lib/loan/ui/pages/loan_group_page/add_edit_loan_page.dart:85` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14 lines × 2) lib/mypayment/ui/pages/main_page/account_card/device_dialog_box.dart:49— lib/mypayment/ui/pages/main_page/account_card/device_dialog_box.dart:49-62 | lib/tools/ui/widgets/custom_dialog_box.dart:52-65 — before extracting anything, compare `lib/mypayment/ui/pages/main_page/account_card/device_dialog_box.dart` and `lib/tools/ui/widgets/custom_dialog_box.dart` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 52 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `lib/mypayment/ui/pages/main_page/account_card/device_dialog_box.dart:49` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14 lines × 2) lib/mypayment/ui/pages/pay_page/qr_code.dart:34— lib/mypayment/ui/pages/pay_page/qr_code.dart:34-47 | lib/purchases/ui/pages/ticket_page/ticket_page.dart:45-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. Read the line range as the matched WINDOW rather than a finished unit: at `lib/purchases/ui/pages/ticket_page/ticket_page.dart:45` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (14 lines × 2) lib/mypayment/ui/pages/store_admin_page/seller_right_dialog.dart:67— lib/mypayment/ui/pages/store_admin_page/seller_right_dialog.dart:67-80 | lib/tools/ui/widgets/custom_dialog_box.dart:69-82 — before extracting anything, compare `lib/mypayment/ui/pages/store_admin_page/seller_right_dialog.dart` and `lib/tools/ui/widgets/custom_dialog_box.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. Read the line range as the matched WINDOW rather than a finished unit: at `lib/mypayment/ui/pages/store_admin_page/seller_right_dialog.dart:67` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14 lines × 2) lib/mypayment/ui/pages/structure_admin_page/add_store_card.dart:28— lib/mypayment/ui/pages/structure_admin_page/add_store_card.dart:28-41 | lib/mypayment/ui/pages/structure_admin_page/admin_store_card.dart:32-45 — 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) lib/raffle/ui/pages/raffle_page/buy_pack_ticket_card.dart:136— lib/raffle/ui/pages/raffle_page/buy_pack_ticket_card.dart:136-149 | lib/raffle/ui/pages/raffle_page/confirm_payment.dart:174-187 — before extracting anything, compare `lib/raffle/ui/pages/raffle_page/buy_pack_ticket_card.dart` and `lib/raffle/ui/pages/raffle_page/confirm_payment.dart` as WHOLE FILES: this scan already matched 5 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. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `lib/raffle/ui/pages/raffle_page/buy_pack_ticket_card.dart:136` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) lib/amap/tools/amap_background_painter.dart:40— lib/amap/tools/amap_background_painter.dart:40-47 | lib/raffle/tools/winning_ticket_background_painter.dart:65-72 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `lib/amap/tools/amap_background_painter.dart:40` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) lib/tools/repository/logo_repository.dart:101— lib/tools/repository/logo_repository.dart:101-108 | lib/tools/repository/pdf_repository.dart:129-136 — before extracting anything, compare `lib/tools/repository/logo_repository.dart` and `lib/tools/repository/pdf_repository.dart` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 50 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `lib/tools/repository/logo_repository.dart:101` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (8 lines × 2) lib/booking/providers/manager_booking_list_provider.dart:17— lib/booking/providers/manager_booking_list_provider.dart:17-24 | lib/booking/providers/user_booking_list_provider.dart:20-27 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (8 lines × 2) lib/event/providers/event_list_provider.dart:20— lib/event/providers/event_list_provider.dart:20-27 | lib/event/providers/user_event_list_provider.dart:25-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 (8 lines × 2) lib/event/providers/event_list_provider.dart:29— lib/event/providers/event_list_provider.dart:29-36 | lib/event/providers/user_event_list_provider.dart:34-41 — 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) lib/loan/providers/loan_list_provider.dart:28— lib/loan/providers/loan_list_provider.dart:28-35 | lib/loan/providers/loaner_loan_list_provider.dart:32-39 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (8 lines × 2) lib/loan/providers/loan_list_provider.dart:37— lib/loan/providers/loan_list_provider.dart:37-44 | lib/loan/providers/loaner_loan_list_provider.dart:41-48 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (8 lines × 2) lib/loan/providers/loaner_list_provider.dart:20— lib/loan/providers/loaner_list_provider.dart:20-27 | lib/loan/providers/user_loaner_list_provider.dart:20-27 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (8 lines × 2) lib/loan/providers/loaner_list_provider.dart:29— lib/loan/providers/loaner_list_provider.dart:29-36 | lib/loan/providers/user_loaner_list_provider.dart:29-36 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (8 lines × 2) lib/mypayment/providers/invoice_list_provider.dart:73— lib/mypayment/providers/invoice_list_provider.dart:73-80 | lib/mypayment/providers/stores_list_provider.dart:41-48 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (13 lines × 2) lib/admin/ui/pages/memberships/add_edit_user_membership_page/add_edit_user_membership_page.dart:60— lib/admin/ui/pages/memberships/add_edit_user_membership_page/add_edit_user_membership_page.dart:60-72 | lib/phonebook/ui/pages/membership_editor_page/membership_editor_page.dart:75-87 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `lib/admin/ui/pages/memberships/add_edit_user_membership_page/add_edit_user_membership_page.dart:60` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 2) lib/advert/ui/pages/detail_page/detail.dart:58— lib/advert/ui/pages/detail_page/detail.dart:58-70 | lib/cinema/ui/pages/detail_page/detail_page.dart:81-93 — before extracting anything, compare `lib/advert/ui/pages/detail_page/detail.dart` and `lib/cinema/ui/pages/detail_page/detail_page.dart` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 38 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `lib/advert/ui/pages/detail_page/detail.dart:58` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 2) lib/booking/ui/pages/admin_pages/add_edit_manager_page.dart:51— lib/booking/ui/pages/admin_pages/add_edit_manager_page.dart:51-63 | lib/booking/ui/pages/admin_pages/add_edit_room_page.dart:51-63 — before extracting anything, compare `lib/booking/ui/pages/admin_pages/add_edit_manager_page.dart` and `lib/booking/ui/pages/admin_pages/add_edit_room_page.dart` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 72 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `lib/booking/ui/pages/admin_pages/add_edit_manager_page.dart:51` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (13 lines × 2) lib/phonebook/ui/pages/association_page/web_member_card.dart:124— lib/phonebook/ui/pages/association_page/web_member_card.dart:124-136 | lib/phonebook/ui/pages/association_page/web_member_card.dart:208-220 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `lib/phonebook/ui/pages/association_page/web_member_card.dart:124` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 2) lib/phonebook/ui/pages/main_page/research_bar.dart:10— lib/phonebook/ui/pages/main_page/research_bar.dart:10-22 | lib/purchases/ui/pages/history_page/research_bar.dart:11-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. Read the line range as the matched WINDOW rather than a finished unit: at `lib/phonebook/ui/pages/main_page/research_bar.dart:10` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (13 lines × 2) lib/raffle/ui/pages/main_page/ticket_card.dart:50— lib/raffle/ui/pages/main_page/ticket_card.dart:50-62 | lib/raffle/ui/pages/raffle_page/confirm_payment.dart:100-112 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `lib/raffle/ui/pages/main_page/ticket_card.dart:49` calls `only` and `lib/raffle/ui/pages/raffle_page/confirm_payment.dart:99` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (13 lines × 2) lib/seed-library/ui/pages/add_edit_species_page/add_edit_species_page.dart:235— lib/seed-library/ui/pages/add_edit_species_page/add_edit_species_page.dart:235-247 | lib/seed-library/ui/pages/add_edit_species_page/add_edit_species_page.dart:284-296 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `lib/seed-library/ui/pages/add_edit_species_page/add_edit_species_page.dart:235` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (13 lines × 2) lib/tools/providers/list_notifier.dart:8— lib/tools/providers/list_notifier.dart:8-20 | lib/tools/providers/single_notifier.dart:8-20 — before extracting anything, compare `lib/tools/providers/list_notifier.dart` and `lib/tools/providers/single_notifier.dart` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 52 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (13 lines × 2) lib/admin/providers/association_membership_list_provider.dart:30— lib/admin/providers/association_membership_list_provider.dart:30-42 | lib/phonebook/providers/association_groupement_list_provider.dart:34-46 — 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) lib/admin/ui/pages/memberships/association_membership_page/association_membership_page.dart:119— lib/admin/ui/pages/memberships/association_membership_page/association_membership_page.dart:119-135 | lib/admin/ui/pages/schools/school_page/school_page.dart:71-87 — before extracting anything, compare `lib/admin/ui/pages/memberships/association_membership_page/association_membership_page.dart` and `lib/admin/ui/pages/schools/school_page/school_page.dart` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 65 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `lib/admin/ui/pages/memberships/association_membership_page/association_membership_page.dart:119` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (17 lines × 2) lib/amap/ui/components/order_ui.dart:115— lib/amap/ui/components/order_ui.dart:115-131 | lib/amap/ui/pages/detail_delivery_page/order_detail_ui.dart:111-127 — before extracting anything, compare `lib/amap/ui/components/order_ui.dart` and `lib/amap/ui/pages/detail_delivery_page/order_detail_ui.dart` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 49 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `lib/amap/ui/components/order_ui.dart:115` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (17 lines × 2) lib/cinema/ui/pages/session_pages/add_edit_session.dart:270— lib/cinema/ui/pages/session_pages/add_edit_session.dart:270-286 | lib/cinema/ui/pages/session_pages/add_edit_session.dart:293-309 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `lib/cinema/ui/pages/session_pages/add_edit_session.dart:270` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (17 lines × 2) lib/loan/ui/pages/loan_group_page/search_result.dart:18— lib/loan/ui/pages/loan_group_page/search_result.dart:18-34 | lib/vote/ui/pages/contender_pages/search_result.dart:24-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. Read the line range as the matched WINDOW rather than a finished unit: at `lib/loan/ui/pages/loan_group_page/search_result.dart:18` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (17 lines × 2) lib/mypayment/ui/pages/main_page/account_card/day_divider.dart:11— lib/mypayment/ui/pages/main_page/account_card/day_divider.dart:11-27 | lib/mypayment/ui/pages/main_page/seller_card/store_divider.dart:10-26 — before extracting anything, compare `lib/mypayment/ui/pages/main_page/account_card/day_divider.dart` and `lib/mypayment/ui/pages/main_page/seller_card/store_divider.dart` as WHOLE FILES: 83% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `lib/mypayment/ui/pages/main_page/account_card/day_divider.dart:11` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (17 lines × 2) lib/mypayment/ui/pages/store_stats_page/tool_bar.dart:107— lib/mypayment/ui/pages/store_stats_page/tool_bar.dart:107-123 | lib/mypayment/ui/pages/store_stats_page/tool_bar.dart:198-214 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `lib/mypayment/ui/pages/store_stats_page/tool_bar.dart:107` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (17 lines × 2) lib/tools/ui/builders/async_child.dart:184— lib/tools/ui/builders/async_child.dart:184-200 | lib/tools/ui/builders/async_child.dart:244-260 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `lib/tools/ui/builders/async_child.dart:184` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (17 lines × 2) lib/vote/ui/pages/admin_page/admin_page.dart:454— lib/vote/ui/pages/admin_page/admin_page.dart:454-470 | lib/vote/ui/pages/admin_page/admin_page.dart:533-549 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `lib/vote/ui/pages/admin_page/admin_page.dart:454` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (15 lines × 2) lib/admin/ui/pages/main_page/main_page.dart:22— lib/admin/ui/pages/main_page/main_page.dart:22-36 | lib/seed-library/ui/pages/main_page/main_page.dart:44-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. Read the line range as the matched WINDOW rather than a finished unit: at `lib/admin/ui/pages/main_page/main_page.dart:22` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (15 lines × 2) lib/amap/providers/delivery_list_provider.dart:84— lib/amap/providers/delivery_list_provider.dart:84-98 | lib/amap/providers/user_order_list_provider.dart:83-97 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `lib/amap/providers/delivery_list_provider.dart:84` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (15 lines × 2) lib/booking/ui/pages/admin_pages/add_edit_manager_page.dart:34— lib/booking/ui/pages/admin_pages/add_edit_manager_page.dart:34-48 | lib/booking/ui/pages/admin_pages/add_edit_room_page.dart:34-48 — before extracting anything, compare `lib/booking/ui/pages/admin_pages/add_edit_manager_page.dart` and `lib/booking/ui/pages/admin_pages/add_edit_room_page.dart` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 72 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `lib/booking/ui/pages/admin_pages/add_edit_manager_page.dart:34` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (15 lines × 2) lib/cinema/ui/pages/detail_page/detail_page.dart:85— lib/cinema/ui/pages/detail_page/detail_page.dart:85-99 | lib/cinema/ui/pages/detail_page/detail_page.dart:240-254 — 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) lib/phonebook/ui/pages/association_page/member_card.dart:27— lib/phonebook/ui/pages/association_page/member_card.dart:27-41 | lib/phonebook/ui/pages/association_page/web_member_card.dart:28-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. Read the line range as the matched WINDOW rather than a finished unit: at `lib/phonebook/ui/pages/association_page/member_card.dart:27` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (15 lines × 2) lib/raffle/ui/pages/admin_module_page/confirm_creation.dart:23— lib/raffle/ui/pages/admin_module_page/confirm_creation.dart:23-37 | lib/raffle/ui/pages/raffle_page/confirm_payment.dart:49-63 — before extracting anything, compare `lib/raffle/ui/pages/admin_module_page/confirm_creation.dart` and `lib/raffle/ui/pages/raffle_page/confirm_payment.dart` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 115 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `lib/raffle/ui/pages/admin_module_page/confirm_creation.dart:23` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (15 lines × 2) lib/settings/ui/pages/edit_user_page/edit_user_page.dart:271— lib/settings/ui/pages/edit_user_page/edit_user_page.dart:271-285 | lib/settings/ui/pages/edit_user_page/picture_button.dart:19-33 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `lib/settings/ui/pages/edit_user_page/edit_user_page.dart:271` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `lib/settings/ui/pages/edit_user_page/edit_user_page.dart:286` calls `circular` and `lib/settings/ui/pages/edit_user_page/picture_button.dart:34` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (15 lines × 2) lib/vote/ui/pages/main_page/contender_card.dart:49— lib/vote/ui/pages/main_page/contender_card.dart:49-63 | lib/vote/ui/pages/main_page/contender_card.dart:134-148 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `lib/vote/ui/pages/main_page/contender_card.dart:49` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) lib/admin/providers/permissions_list_provider.dart:28— lib/admin/providers/permissions_list_provider.dart:28-34 | lib/admin/providers/permissions_list_provider.dart:85-91 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `lib/admin/providers/permissions_list_provider.dart:28` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) lib/amap/ui/pages/main_page/delivery_section.dart:23— lib/amap/ui/pages/main_page/delivery_section.dart:23-29 | lib/amap/ui/pages/main_page/orders_section.dart:31-37 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `lib/amap/ui/pages/main_page/delivery_section.dart:23` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `lib/amap/ui/pages/main_page/orders_section.dart:29` calls `watch`, `read` and `lib/amap/ui/pages/main_page/delivery_section.dart:22` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (7 lines × 2) lib/booking/ui/calendar/calendar_dialog.dart:27— lib/booking/ui/calendar/calendar_dialog.dart:27-33 | lib/booking/ui/components/booking_card.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) lib/seed-library/class/plant_complete.dart:102— lib/seed-library/class/plant_complete.dart:102-108 | lib/seed-library/class/plant_simple.dart:88-94 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (7 lines × 2) lib/user/repositories/user_repository.dart:24— lib/user/repositories/user_repository.dart:24-30 | lib/user/repositories/user_repository.dart:35-41 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) lib/admin/providers/group_list_provider.dart:45— lib/admin/providers/group_list_provider.dart:45-51 | lib/admin/providers/school_list_provider.dart:39-45 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (7 lines × 2) lib/amap/providers/orders_by_delivery_provider.dart:11— lib/amap/providers/orders_by_delivery_provider.dart:11-17 | lib/amap/providers/user_order_list_provider.dart:23-29 — 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) lib/admin/repositories/association_membership_repository.dart:68— lib/admin/repositories/association_membership_repository.dart:68-74 | lib/phonebook/repositories/association_groupement_repository.dart:28-34 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Change-coupling hub: REDACTED → admin_page.dart, admin_ph_list.dart, pdf_picker.dart, add_edit_ph_page.dart, ph_card.dart, ph_list.dart, view_ph.dart lib/ph/ui/pages/main_page/main_page.dart— `lib/ph/ui/pages/main_page/main_page.dart` changes together with 7 other files — `lib/ph/ui/pages/admin_page/admin_page.dart`, `lib/ph/ui/pages/admin_page/admin_ph_list.dart`, `lib/ph/ui/pages/file_picker/pdf_picker.dart`, `lib/ph/ui/pages/form_page/add_edit_ph_page.dart`, `lib/ph/ui/pages/past_ph_selection_page/ph_card.dart`, `lib/ph/ui/pages/past_ph_selection_page/ph_list.dart`, `lib/ph/ui/pages/view_ph/view_ph.dart` — none of which declares a dependency on it: one file is the hub of 7 separate couplings, not 7 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 7.
Change-coupling hub: REDACTED → association_repository.dart, admin_page.dart, association_research_bar.dart, association_creation_page.dart, association_page.dart, member_card.dart, member_detail_page.dart lib/phonebook/ui/pages/main_page/main_page.dart— `lib/phonebook/ui/pages/main_page/main_page.dart` changes together with 7 other files — `lib/phonebook/repositories/association_repository.dart`, `lib/phonebook/ui/pages/admin_page/admin_page.dart`, `lib/phonebook/ui/pages/admin_page/association_research_bar.dart`, `lib/phonebook/ui/pages/association_creation_page/association_creation_page.dart`, `lib/phonebook/ui/pages/association_page/association_page.dart`, `lib/phonebook/ui/pages/association_page/member_card.dart`, `lib/phonebook/ui/pages/member_detail_page/member_detail_page.dart` — none of which declares a dependency on it: one file is the hub of 7 separate couplings, not 7 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 7.
Change-coupling hub: association_editor_page.dart → association_repository.dart, admin_page.dart, association_research_bar.dart, association_creation_page.dart, association_page.dart, member_card.dart, REDACTED, member_detail_page.dart, membership_editor_page.dart lib/phonebook/ui/pages/association_editor_page/association_editor_page.dart— `lib/phonebook/ui/pages/association_editor_page/association_editor_page.dart` changes together with 9 other files — `lib/phonebook/repositories/association_repository.dart`, `lib/phonebook/ui/pages/admin_page/admin_page.dart`, `lib/phonebook/ui/pages/admin_page/association_research_bar.dart`, `lib/phonebook/ui/pages/association_creation_page/association_creation_page.dart`, `lib/phonebook/ui/pages/association_page/association_page.dart`, `lib/phonebook/ui/pages/association_page/member_card.dart`, `lib/phonebook/ui/pages/main_page/main_page.dart`, `lib/phonebook/ui/pages/member_detail_page/member_detail_page.dart`, `lib/phonebook/ui/pages/membership_editor_page/membership_editor_page.dart` — none of which declares a dependency on it: one file is the hub of 9 separate couplings, not 9 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 9.
Change-coupling hub: add_edit_ph_page.dart → admin_page.dart, admin_ph_list.dart, ph_card.dart, ph_list.dart, view_ph.dart lib/ph/ui/pages/form_page/add_edit_ph_page.dart— `lib/ph/ui/pages/form_page/add_edit_ph_page.dart` changes together with 5 other files — `lib/ph/ui/pages/admin_page/admin_page.dart`, `lib/ph/ui/pages/admin_page/admin_ph_list.dart`, `lib/ph/ui/pages/past_ph_selection_page/ph_card.dart`, `lib/ph/ui/pages/past_ph_selection_page/ph_list.dart`, `lib/ph/ui/pages/view_ph/view_ph.dart` — none of which declares a dependency on it: one file is the hub of 5 separate couplings, not 5 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 5.
Change-coupling hub: association_page.dart → association_list_provider.dart, association_research_bar.dart, member_detail_page.dart, membership_editor_page.dart lib/phonebook/ui/pages/association_page/association_page.dart— `lib/phonebook/ui/pages/association_page/association_page.dart` changes together with 4 other files — `lib/phonebook/providers/association_list_provider.dart`, `lib/phonebook/ui/pages/admin_page/association_research_bar.dart`, `lib/phonebook/ui/pages/member_detail_page/member_detail_page.dart`, `lib/phonebook/ui/pages/membership_editor_page/membership_editor_page.dart` — none of which declares a dependency on it: one file is the hub of 4 separate couplings, not 4 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 4.
Change-coupling hub: association_repository.dart → association_member_list_provider.dart, admin_page.dart, association_research_bar.dart, member_editable_card.dart, association_page.dart lib/phonebook/repositories/association_repository.dart— `lib/phonebook/repositories/association_repository.dart` changes together with 5 other files — `lib/phonebook/providers/association_member_list_provider.dart`, `lib/phonebook/ui/pages/admin_page/admin_page.dart`, `lib/phonebook/ui/pages/admin_page/association_research_bar.dart`, `lib/phonebook/ui/pages/association_editor_page/member_editable_card.dart`, `lib/phonebook/ui/pages/association_page/association_page.dart` — none of which declares a dependency on it: one file is the hub of 5 separate couplings, not 5 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 5.
Change-coupling hub: member_editable_card.dart → is_phonebook_admin_provider.dart, member_card.dart, membership_editor_page.dart lib/phonebook/ui/pages/association_editor_page/member_editable_card.dart— `lib/phonebook/ui/pages/association_editor_page/member_editable_card.dart` changes together with 3 other files — `lib/phonebook/providers/is_phonebook_admin_provider.dart`, `lib/phonebook/ui/pages/association_page/member_card.dart`, `lib/phonebook/ui/pages/membership_editor_page/membership_editor_page.dart` — none of which declares a dependency on it: one file is the hub of 3 separate couplings, not 3 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 3.
D4 · Code Duplication· Edited copy of a member (9 corresponding lines) · ×7
Edited copy of a member (9 corresponding lines) lib/amap/providers/cash_list_provider.dart:21— lib/amap/providers/cash_list_provider.dart:21-29 | lib/raffle/providers/cash_provider.dart:24-32 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (9 corresponding lines) lib/cinema/class/the_movie_db_genre.dart:31— lib/cinema/class/the_movie_db_genre.dart:31-40 | lib/cinema/class/the_movie_db_search_result.dart:29-37 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (9 corresponding lines) lib/cinema/class/session.dart:22— lib/cinema/class/session.dart:22-30 | lib/phonebook/class/association.dart:20-28 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (9 corresponding lines) lib/mypayment/class/history.dart:53— lib/mypayment/class/history.dart:53-61 | lib/mypayment/class/transaction.dart:41-50 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (9 corresponding lines) lib/centralassociation/router.dart:23— lib/centralassociation/router.dart:23-31 | lib/centralisation/router.dart:23-31 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (9 corresponding lines) lib/settings/providers/module_list_provider.dart:172— lib/settings/providers/module_list_provider.dart:172-182 | lib/booking/providers/selected_days_provider.dart:12-20 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (9 corresponding lines) lib/purchases/providers/scanned_users_list_provider.dart:15— lib/purchases/providers/scanned_users_list_provider.dart:15-25 | lib/purchases/providers/tag_list_provider.dart:13-21 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (24 lines × 2) lib/admin/ui/pages/groups/add_group_page/add_group_page.dart:64— lib/admin/ui/pages/groups/add_group_page/add_group_page.dart:64-87 | lib/admin/ui/pages/schools/add_school_page/add_school_page.dart:64-87 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `lib/admin/ui/pages/groups/add_group_page/add_group_page.dart:64` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (24 lines × 2) lib/booking/ui/pages/detail_pages/detail_booking.dart:32— lib/booking/ui/pages/detail_pages/detail_booking.dart:32-55 | lib/loan/ui/pages/detail_pages/detail_loan.dart:22-45 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `lib/booking/ui/pages/detail_pages/detail_booking.dart:32` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (24 lines × 2) lib/booking/ui/pages/detail_pages/detail_booking.dart:90— lib/booking/ui/pages/detail_pages/detail_booking.dart:90-113 | lib/event/ui/pages/detail_page/detail_page.dart:74-97 — before extracting anything, compare `lib/booking/ui/pages/detail_pages/detail_booking.dart` and `lib/event/ui/pages/detail_page/detail_page.dart` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 73 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `lib/event/ui/pages/detail_page/detail_page.dart:72` calls `Column` and `lib/booking/ui/pages/detail_pages/detail_booking.dart:89` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (24 lines × 2) lib/event/ui/pages/detail_page/detail_page.dart:26— lib/event/ui/pages/detail_page/detail_page.dart:26-49 | lib/vote/ui/pages/detail_page/detail_page.dart:25-48 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `lib/event/ui/pages/detail_page/detail_page.dart:26` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (24 lines × 2) lib/loan/ui/pages/loan_group_page/item_bar.dart:106— lib/loan/ui/pages/loan_group_page/item_bar.dart:106-129 | lib/loan/ui/pages/loan_group_page/item_bar.dart:173-196 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `lib/loan/ui/pages/loan_group_page/item_bar.dart:106` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (24 lines × 2) lib/tools/repository/logo_repository.dart:56— lib/tools/repository/logo_repository.dart:56-79 | lib/tools/repository/pdf_repository.dart:73-96 — before extracting anything, compare `lib/tools/repository/logo_repository.dart` and `lib/tools/repository/pdf_repository.dart` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 50 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `lib/tools/repository/logo_repository.dart:56` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (24 lines × 2) lib/event/providers/room_list_provider.dart:12— lib/event/providers/room_list_provider.dart:12-35 | lib/service/providers/room_list_provider.dart:12-35 — before extracting anything, compare `lib/event/providers/room_list_provider.dart` and `lib/service/providers/room_list_provider.dart` 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.
D4 · Code Duplication· Members sharing a duplicated core (4 members, 50+ identical tokens) · ×6
Members sharing a duplicated core (4 members, 50+ identical tokens) lib/admin/ui/pages/groups/edit_group_page/results.dart:17— lib/admin/ui/pages/groups/edit_group_page/results.dart:17-94 | lib/admin/ui/pages/structure_page/add_edit_structure_page/results.dart:12-61 | lib/mypayment/ui/pages/structure_administrators_page/results.dart:16-93 | lib/mypayment/ui/pages/transfer_structure_page/search_result.dart:18-105 — 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) lib/admin/ui/pages/groups/group_page/group_button.dart:14— lib/admin/ui/pages/groups/group_page/group_button.dart:14-36 | lib/admin/ui/pages/memberships/association_membership_page/association_membership_button.dart:14-36 | lib/admin/ui/pages/schools/school_page/school_button.dart:14-36 | lib/admin/ui/pages/structure_page/structure_button.dart:14-36 — 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) lib/admin/ui/pages/memberships/association_membership_detail_page/association_membership_information_editor.dart:18— lib/admin/ui/pages/memberships/association_membership_detail_page/association_membership_information_editor.dart:18-166 | lib/phonebook/ui/pages/association_creation_page/association_creation_page.dart:25-166 | lib/phonebook/ui/pages/association_editor_page/association_information_editor.dart:23-380 | lib/settings/ui/pages/edit_user_page/edit_user_page.dart:28-423 — 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) lib/amap/ui/components/order_ui.dart:31— lib/amap/ui/components/order_ui.dart:31-218 | lib/amap/ui/components/product_ui.dart:25-124 | lib/amap/ui/pages/admin_page/delivery_ui.dart:28-416 | lib/amap/ui/pages/detail_delivery_page/order_detail_ui.dart:30-204 — 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) lib/drawer/ui/email_change_popup.dart:28— lib/drawer/ui/email_change_popup.dart:28-361 | lib/mypayment/ui/pages/main_page/account_card/device_dialog_box.dart:27-181 | lib/mypayment/ui/pages/store_admin_page/seller_right_dialog.dart:29-161 | lib/tools/ui/widgets/custom_dialog_box.dart:31-201 — 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) lib/tools/ui/builders/async_child.dart:97— lib/tools/ui/builders/async_child.dart:97-111 | lib/tools/ui/builders/async_child.dart:131-150 | lib/tools/ui/builders/async_child.dart:177-202 | lib/tools/ui/builders/async_child.dart:236-263 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
D4 · Code Duplication· Edited copy of a member (3 corresponding lines) · ×6
Edited copy of a member (3 corresponding lines) lib/raffle/repositories/prize_repository.dart:10— lib/raffle/repositories/prize_repository.dart:10-12 | lib/raffle/repositories/prizes_repository.dart:10-12 — These two members are one piece of code written twice and then edited apart: 3 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (3 corresponding lines) lib/amap/class/cash.dart:27— lib/amap/class/cash.dart:27-33 | lib/raffle/class/cash.dart:19-21 — These two members are one piece of code written twice and then edited apart: 3 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (3 corresponding lines) lib/cinema/repositories/session_poster_repository.dart:23— lib/cinema/repositories/session_poster_repository.dart:23-28 | lib/vote/repositories/contender_logo_repository.dart:22-24 — These two members are one piece of code written twice and then edited apart: 3 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (3 corresponding lines) lib/raffle/repositories/prize_repository.dart:22— lib/raffle/repositories/prize_repository.dart:22-24 | lib/raffle/repositories/prizes_repository.dart:22-24 — These two members are one piece of code written twice and then edited apart: 3 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (3 corresponding lines) lib/admin/providers/members_provider.dart:11— lib/admin/providers/members_provider.dart:11-13 | lib/advert/providers/announcer_provider.dart:17-19 — These two members are one piece of code written twice and then edited apart: 3 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (3 corresponding lines) lib/amap/providers/user_amount_provider.dart:13— lib/amap/providers/user_amount_provider.dart:13-15 | lib/raffle/providers/user_amount_provider.dart:15-17 — These two members are one piece of code written twice and then edited apart: 3 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (14 lines × 3) lib/admin/ui/pages/groups/group_page/group_ui.dart:65— lib/admin/ui/pages/groups/group_page/group_ui.dart:65-78 | lib/admin/ui/pages/memberships/association_membership_page/association_membership_ui.dart:53-66 | lib/admin/ui/pages/schools/school_page/school_ui.dart:56-69 — before extracting anything, compare `lib/admin/ui/pages/groups/group_page/group_ui.dart` and `lib/admin/ui/pages/memberships/association_membership_page/association_membership_ui.dart` as WHOLE FILES: this scan already matched 3 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. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `lib/admin/ui/pages/groups/group_page/group_ui.dart:65` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14 lines × 3) lib/amap/providers/delivery_list_provider.dart:86— lib/amap/providers/delivery_list_provider.dart:86-99 | lib/amap/providers/user_order_list_provider.dart:65-78 | lib/amap/providers/user_order_list_provider.dart:85-98 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `lib/amap/providers/delivery_list_provider.dart:86` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14 lines × 3) lib/booking/ui/pages/detail_pages/detail_booking.dart:44— lib/booking/ui/pages/detail_pages/detail_booking.dart:44-57 | lib/event/ui/pages/detail_page/detail_page.dart:41-54 | lib/loan/ui/pages/detail_pages/detail_loan.dart:34-47 — before extracting anything, compare `lib/booking/ui/pages/detail_pages/detail_booking.dart` and `lib/event/ui/pages/detail_page/detail_page.dart` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 73 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `lib/booking/ui/pages/detail_pages/detail_booking.dart:44` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (14 lines × 3) lib/raffle/ui/pages/admin_module_page/tombola_card.dart:17— lib/raffle/ui/pages/admin_module_page/tombola_card.dart:17-30 | lib/raffle/ui/pages/creation_edit_page/user_cash_ui.dart:70-83 | lib/raffle/ui/pages/creation_edit_page/user_cash_ui.dart:161-174 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `lib/raffle/ui/pages/admin_module_page/tombola_card.dart:17` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14 lines × 3) lib/raffle/ui/pages/main_page/ticket_card_background.dart:65— lib/raffle/ui/pages/main_page/ticket_card_background.dart:65-78 | lib/raffle/ui/pages/raffle_page/buy_pack_ticket_card.dart:49-62 | lib/raffle/ui/pages/raffle_page/buy_type_ticket_card.dart:49-62 — before extracting anything, compare `lib/raffle/ui/pages/raffle_page/buy_pack_ticket_card.dart` and `lib/raffle/ui/pages/raffle_page/buy_type_ticket_card.dart` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 231 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `lib/raffle/ui/pages/main_page/ticket_card_background.dart:65` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14 lines × 3) lib/raffle/ui/pages/raffle_page/buy_pack_ticket_card.dart:108— lib/raffle/ui/pages/raffle_page/buy_pack_ticket_card.dart:108-121 | lib/raffle/ui/pages/raffle_page/buy_type_ticket_card.dart:108-121 | lib/raffle/ui/pages/raffle_page/confirm_payment.dart:140-154 — before extracting anything, compare `lib/raffle/ui/pages/raffle_page/buy_pack_ticket_card.dart` and `lib/raffle/ui/pages/raffle_page/buy_type_ticket_card.dart` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 231 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `lib/raffle/ui/pages/raffle_page/buy_pack_ticket_card.dart:108` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication· Edited copy of a member (8 corresponding lines) · ×5
Edited copy of a member (8 corresponding lines) lib/admin/providers/group_list_provider.dart:44— lib/admin/providers/group_list_provider.dart:44-51 | lib/admin/providers/school_list_provider.dart:38-45 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) lib/flappybird/providers/bird_image_provider.dart:13— lib/flappybird/providers/bird_image_provider.dart:13-20 | lib/flappybird/providers/pipe_image_provider.dart:13-22 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) lib/admin/class/group.dart:25— lib/admin/class/group.dart:25-32 | lib/amap/class/delivery.dart:34-42 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) lib/phonebook/class/member.dart:25— lib/phonebook/class/member.dart:25-32 | lib/user/class/applicant.dart:25-33 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) lib/recommendation/class/recommendation.dart:28— lib/recommendation/class/recommendation.dart:28-35 | lib/service/class/message.dart:21-28 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (22 lines × 2) lib/booking/ui/calendar/calendar.dart:176— lib/booking/ui/calendar/calendar.dart:176-197 | lib/tools/ui/widgets/calendar.dart:138-159 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `lib/booking/ui/calendar/calendar.dart:176` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `lib/booking/ui/calendar/calendar.dart:198` calls `of` and `lib/tools/ui/widgets/calendar.dart:160` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (22 lines × 2) lib/mypayment/ui/pages/store_stats_page/tool_bar.dart:76— lib/mypayment/ui/pages/store_stats_page/tool_bar.dart:76-97 | lib/mypayment/ui/pages/store_stats_page/tool_bar.dart:113-134 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `lib/mypayment/ui/pages/store_stats_page/tool_bar.dart:76` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (22 lines × 2) lib/mypayment/ui/pages/store_stats_page/tool_bar.dart:167— lib/mypayment/ui/pages/store_stats_page/tool_bar.dart:167-188 | lib/mypayment/ui/pages/store_stats_page/tool_bar.dart:204-225 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `lib/mypayment/ui/pages/store_stats_page/tool_bar.dart:167` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (22 lines × 2) lib/raffle/ui/pages/creation_edit_page/prize_card.dart:84— lib/raffle/ui/pages/creation_edit_page/prize_card.dart:84-105 | lib/raffle/ui/pages/creation_edit_page/prize_card.dart:151-172 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (22 lines × 2) lib/seed-library/ui/pages/plants_page/personal_plant_card.dart:20— lib/seed-library/ui/pages/plants_page/personal_plant_card.dart:20-41 | lib/seed-library/ui/pages/stock_page/plant_card.dart:15-36 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `lib/seed-library/ui/pages/plants_page/personal_plant_card.dart:20` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (20 lines × 2) lib/admin/ui/pages/groups/edit_group_page/results.dart:72— lib/admin/ui/pages/groups/edit_group_page/results.dart:72-91 | lib/mypayment/ui/pages/structure_administrators_page/results.dart:71-90 — before extracting anything, compare `lib/admin/ui/pages/groups/edit_group_page/results.dart` and `lib/mypayment/ui/pages/structure_administrators_page/results.dart` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 85 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `lib/admin/ui/pages/groups/edit_group_page/results.dart:72` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (20 lines × 2) lib/centralassociation/ui/pages/link_card.dart:15— lib/centralassociation/ui/pages/link_card.dart:15-34 | lib/centralisation/ui/pages/module_card.dart:18-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. Read the line range as the matched WINDOW rather than a finished unit: at `lib/centralassociation/ui/pages/link_card.dart:15` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `lib/centralisation/ui/pages/module_card.dart:15` calls `watch`, `read` and `lib/centralassociation/ui/pages/link_card.dart:14` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (20 lines × 2) lib/mypayment/ui/pages/scan_page/scanner.dart:152— lib/mypayment/ui/pages/scan_page/scanner.dart:152-171 | lib/purchases/ui/pages/scan_page/qr_code_scanner.dart:105-124 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (20 lines × 2) lib/raffle/ui/pages/creation_edit_page/ticket_ui.dart:21— lib/raffle/ui/pages/creation_edit_page/ticket_ui.dart:21-40 | lib/raffle/ui/pages/creation_edit_page/winning_ticket_card.dart:17-36 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `lib/raffle/ui/pages/creation_edit_page/ticket_ui.dart:21` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (20 lines × 2) lib/vote/ui/pages/admin_page/admin_page.dart:395— lib/vote/ui/pages/admin_page/admin_page.dart:395-414 | lib/vote/ui/pages/admin_page/admin_page.dart:472-491 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `lib/vote/ui/pages/admin_page/admin_page.dart:395` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (19 lines × 2) lib/amap/ui/pages/presentation_page/presentation_page.dart:39— lib/amap/ui/pages/presentation_page/presentation_page.dart:39-57 | lib/amap/ui/pages/presentation_page/presentation_page.dart:85-103 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `lib/amap/ui/pages/presentation_page/presentation_page.dart:39` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (19 lines × 2) lib/loan/providers/history_loaner_loan_list_provider.dart:79— lib/loan/providers/history_loaner_loan_list_provider.dart:79-97 | lib/loan/providers/loaner_loan_list_provider.dart:78-96 — 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 (19 lines × 2) lib/mypayment/ui/pages/invoices_admin_page/invoices_admin_page.dart:58— lib/mypayment/ui/pages/invoices_admin_page/invoices_admin_page.dart:58-76 | lib/mypayment/ui/pages/invoices_structure_page/invoices_structure_page.dart:47-65 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `lib/mypayment/ui/pages/invoices_admin_page/invoices_admin_page.dart:58` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (19 lines × 2) lib/mypayment/ui/pages/main_page/account_card/device_dialog_box.dart:70— lib/mypayment/ui/pages/main_page/account_card/device_dialog_box.dart:70-88 | lib/tools/ui/widgets/custom_dialog_box.dart:73-91 — before extracting anything, compare `lib/mypayment/ui/pages/main_page/account_card/device_dialog_box.dart` and `lib/tools/ui/widgets/custom_dialog_box.dart` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 52 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `lib/mypayment/ui/pages/main_page/account_card/device_dialog_box.dart:70` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (19 lines × 2) lib/amap/repositories/cash_repository.dart:11— lib/amap/repositories/cash_repository.dart:11-29 | lib/raffle/repositories/cash_repository.dart:9-27 — before extracting anything, compare `lib/amap/repositories/cash_repository.dart` and `lib/raffle/repositories/cash_repository.dart` as WHOLE FILES: 87% 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 (11 lines × 2) lib/admin/ui/pages/groups/edit_group_page/edit_group_page.dart:94— lib/admin/ui/pages/groups/edit_group_page/edit_group_page.dart:94-104 | lib/admin/ui/pages/schools/edit_school_page/edit_school_page.dart:70-80 — before extracting anything, compare `lib/admin/ui/pages/groups/edit_group_page/edit_group_page.dart` and `lib/admin/ui/pages/schools/edit_school_page/edit_school_page.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. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `lib/admin/ui/pages/groups/edit_group_page/edit_group_page.dart:94` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (11 lines × 2) lib/admin/ui/pages/memberships/add_edit_user_membership_page/add_edit_user_membership_page.dart:101— lib/admin/ui/pages/memberships/add_edit_user_membership_page/add_edit_user_membership_page.dart:101-111 | lib/phonebook/ui/pages/membership_editor_page/membership_editor_page.dart:161-172 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `lib/admin/ui/pages/memberships/add_edit_user_membership_page/add_edit_user_membership_page.dart:101` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (11 lines × 2) lib/raffle/ui/pages/main_page/main_page.dart:158— lib/raffle/ui/pages/main_page/main_page.dart:158-168 | lib/raffle/ui/pages/main_page/main_page.dart:170-180 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `lib/raffle/ui/pages/main_page/main_page.dart:158` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) lib/seed-library/ui/pages/plant_deposit_page/small_plant_card.dart:25— lib/seed-library/ui/pages/plant_deposit_page/small_plant_card.dart:25-35 | lib/seed-library/ui/pages/plant_deposit_page/small_species_card.dart:18-28 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `lib/seed-library/ui/pages/plant_deposit_page/small_plant_card.dart:25` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `lib/seed-library/ui/pages/plant_deposit_page/small_plant_card.dart:21` calls `firstWhere` and `lib/seed-library/ui/pages/plant_deposit_page/small_species_card.dart:17` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (11 lines × 2) lib/cinema/providers/cinema_topic_provider.dart:34— lib/cinema/providers/cinema_topic_provider.dart:34-44 | lib/service/providers/topic_provider.dart:35-45 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (10 lines × 2) lib/admin/ui/pages/groups/group_page/group_ui.dart:54— lib/admin/ui/pages/groups/group_page/group_ui.dart:54-63 | lib/admin/ui/pages/memberships/association_membership_page/association_membership_ui.dart:42-51 — before extracting anything, compare `lib/admin/ui/pages/groups/group_page/group_ui.dart` and `lib/admin/ui/pages/memberships/association_membership_page/association_membership_ui.dart` as WHOLE FILES: this scan already matched 3 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. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `lib/admin/ui/pages/groups/group_page/group_ui.dart:54` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (10 lines × 2) lib/event/ui/components/event_ui.dart:200— lib/event/ui/components/event_ui.dart:200-209 | lib/event/ui/components/event_ui.dart:254-263 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2) lib/mypayment/ui/pages/main_page/seller_card/admin_invoice_card.dart:19— lib/mypayment/ui/pages/main_page/seller_card/admin_invoice_card.dart:19-28 | lib/mypayment/ui/pages/main_page/seller_card/structure_admin_card.dart:32-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. Read the line range as the matched WINDOW rather than a finished unit: at `lib/mypayment/ui/pages/main_page/seller_card/admin_invoice_card.dart:19` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `lib/mypayment/ui/pages/main_page/seller_card/structure_admin_card.dart:30` calls `Column` and `lib/mypayment/ui/pages/main_page/seller_card/admin_invoice_card.dart:18` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (10 lines × 2) lib/seed-library/ui/pages/edit_plant_detail_page/editable_plant_detail.dart:140— lib/seed-library/ui/pages/edit_plant_detail_page/editable_plant_detail.dart:140-149 | lib/seed-library/ui/pages/edit_plant_detail_page/editable_plant_detail.dart:272-281 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `lib/seed-library/ui/pages/edit_plant_detail_page/editable_plant_detail.dart:140` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) lib/tools/repository/logo_repository.dart:33— lib/tools/repository/logo_repository.dart:33-42 | lib/tools/repository/logo_repository.dart:115-124 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `lib/tools/repository/logo_repository.dart:33` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 2) lib/admin/class/association_membership_simple.dart:11— lib/admin/class/association_membership_simple.dart:11-15 | lib/phonebook/class/association_groupement.dart:12-16 — 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) lib/admin/providers/user_association_membership_list_provider.dart:22— lib/admin/providers/user_association_membership_list_provider.dart:22-28 | lib/loan/providers/loaner_loan_list_provider.dart:14-18 — 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) lib/centralassociation/providers/centralassociation_asso_provider.dart:15— lib/centralassociation/providers/centralassociation_asso_provider.dart:15-19 | lib/centralisation/providers/centralisation_section_provider.dart:16-20 — 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) lib/cinema/providers/session_poster_provider.dart:23— lib/cinema/providers/session_poster_provider.dart:23-27 | lib/vote/providers/contender_logo_provider.dart:24-28 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (5 lines × 2) lib/raffle/class/cash.dart:13— lib/raffle/class/cash.dart:13-17 | lib/vote/class/votes.dart:6-10 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
AC6 · Visual & motion safety· Animation without a prefers-reduced-motion guard · ×4
Animation without a prefers-reduced-motion guard REDACTED:43— `.container` moves (`animation: anirotate 10s linear infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard REDACTED:74— `.dot:nth-child(1)` moves (`animation: ani1 2s infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard REDACTED:79— `.dot:nth-child(2)` moves (`animation: ani2 2s infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard REDACTED:84— `.dot:nth-child(3)` moves (`animation: ani3 2s infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
D4 · Code Duplication· Edited copy of a member (11 corresponding lines) · ×4
Edited copy of a member (11 corresponding lines) lib/mypayment/class/seller.dart:22— lib/mypayment/class/seller.dart:22-32 | lib/mypayment/class/user_store.dart:21-32 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (11 corresponding lines) lib/centralisation/class/module.dart:37— lib/centralisation/class/module.dart:37-49 | lib/drawer/class/module.dart:33-43 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (11 corresponding lines) lib/cinema/ui/pages/session_pages/tmdb_button.dart:7— lib/cinema/ui/pages/session_pages/tmdb_button.dart:7-17 | lib/vote/ui/pages/admin_page/admin_button.dart:7-17 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (11 corresponding lines) lib/mypayment/ui/mypayment.dart:9— lib/mypayment/ui/mypayment.dart:9-19 | lib/vote/ui/vote.dart:10-20 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (4 corresponding lines) · ×4
Edited copy of a member (4 corresponding lines) lib/advert/repositories/advert_poster_repository.dart:21— lib/advert/repositories/advert_poster_repository.dart:21-24 | lib/recommendation/repositories/recommendation_logo_repository.dart:19-22 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (4 corresponding lines) lib/phonebook/repositories/association_picture_repository.dart:19— lib/phonebook/repositories/association_picture_repository.dart:19-25 | lib/raffle/repositories/tombola_logo_repository.dart:20-23 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (4 corresponding lines) lib/amap/class/cash.dart:14— lib/amap/class/cash.dart:14-18 | lib/raffle/class/cash.dart:8-11 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (4 corresponding lines) lib/ph/repositories/ph_cover_repository.dart:12— lib/ph/repositories/ph_cover_repository.dart:12-15 | lib/recommendation/repositories/recommendation_logo_repository.dart:14-17 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (21 lines × 2) lib/advert/ui/components/advert_card.dart:213— lib/advert/ui/components/advert_card.dart:213-233 | lib/advert/ui/components/advert_card.dart:279-299 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `lib/advert/ui/components/advert_card.dart:213` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (21 lines × 2) lib/mypayment/ui/pages/fund_page/fund_page.dart:38— lib/mypayment/ui/pages/fund_page/fund_page.dart:38-58 | lib/mypayment/ui/pages/pay_page/pay_page.dart:30-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. Read the line range as the matched WINDOW rather than a finished unit: at `lib/mypayment/ui/pages/fund_page/fund_page.dart:38` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (21 lines × 2) lib/phonebook/ui/pages/admin_page/association_research_bar.dart:21— lib/phonebook/ui/pages/admin_page/association_research_bar.dart:21-41 | lib/phonebook/ui/pages/main_page/research_bar.dart:22-42 — before extracting anything, compare `lib/phonebook/ui/pages/admin_page/association_research_bar.dart` and `lib/phonebook/ui/pages/main_page/research_bar.dart` as WHOLE FILES: 87% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (21 lines × 2) lib/phonebook/ui/pages/association_editor_page/association_information_editor.dart:81— lib/phonebook/ui/pages/association_editor_page/association_information_editor.dart:81-101 | lib/phonebook/ui/pages/association_editor_page/association_information_editor.dart:129-149 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `lib/phonebook/ui/pages/association_editor_page/association_information_editor.dart:81` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (16 lines × 2) lib/amap/providers/user_amount_provider.dart:18— lib/amap/providers/user_amount_provider.dart:18-33 | lib/raffle/providers/user_amount_provider.dart:20-35 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (16 lines × 2) lib/mypayment/ui/pages/store_admin_page/seller_right_dialog.dart:94— lib/mypayment/ui/pages/store_admin_page/seller_right_dialog.dart:94-109 | lib/tools/ui/widgets/custom_dialog_box.dart:137-152 — before extracting anything, compare `lib/mypayment/ui/pages/store_admin_page/seller_right_dialog.dart` and `lib/tools/ui/widgets/custom_dialog_box.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. Read the line range as the matched WINDOW rather than a finished unit: at `lib/mypayment/ui/pages/store_admin_page/seller_right_dialog.dart:94` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (16 lines × 2) lib/raffle/ui/pages/pack_ticket_page/add_edit_pack_ticket_page.dart:59— lib/raffle/ui/pages/pack_ticket_page/add_edit_pack_ticket_page.dart:59-74 | lib/raffle/ui/pages/pack_ticket_page/add_edit_pack_ticket_page.dart:84-99 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `lib/raffle/ui/pages/pack_ticket_page/add_edit_pack_ticket_page.dart:59` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (16 lines × 2) lib/seed-library/ui/pages/add_edit_species_page/add_edit_species_page.dart:154— lib/seed-library/ui/pages/add_edit_species_page/add_edit_species_page.dart:154-169 | lib/seed-library/ui/pages/add_edit_species_page/add_edit_species_page.dart:174-189 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `lib/seed-library/ui/pages/add_edit_species_page/add_edit_species_page.dart:154` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14–15 lines × 2) lib/advert/ui/pages/detail_page/detail.dart:140— lib/advert/ui/pages/detail_page/detail.dart:140-153 | lib/advert/ui/pages/detail_page/detail.dart:165-179 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `lib/advert/ui/pages/detail_page/detail.dart:165` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14–15 lines × 2) lib/amap/ui/pages/list_products_page/category_page.dart:150— lib/amap/ui/pages/list_products_page/category_page.dart:150-164 | lib/vote/ui/pages/main_page/list_contender_card.dart:164-177 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `lib/amap/ui/pages/list_products_page/category_page.dart:150` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (14–15 lines × 2) lib/booking/ui/pages/booking_pages/add_edit_booking_page.dart:79— lib/booking/ui/pages/booking_pages/add_edit_booking_page.dart:79-92 | lib/event/ui/pages/event_pages/add_edit_event_page.dart:76-90 — before extracting anything, compare `lib/booking/ui/pages/booking_pages/add_edit_booking_page.dart` and `lib/event/ui/pages/event_pages/add_edit_event_page.dart` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 55 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `lib/event/ui/pages/event_pages/add_edit_event_page.dart:76` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `lib/event/ui/pages/event_pages/add_edit_event_page.dart:91` calls `watch` and `lib/booking/ui/pages/booking_pages/add_edit_booking_page.dart:93` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (14–15 lines × 2) lib/phonebook/ui/pages/association_page/web_member_card.dart:107— lib/phonebook/ui/pages/association_page/web_member_card.dart:107-121 | lib/phonebook/ui/pages/association_page/web_member_card.dart:193-206 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `lib/phonebook/ui/pages/association_page/web_member_card.dart:107` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (9 lines × 2) lib/booking/ui/calendar/calendar.dart:43— lib/booking/ui/calendar/calendar.dart:43-51 | lib/booking/ui/pages/manager_page/list_booking.dart:47-55 — before extracting anything, compare `lib/booking/ui/calendar/calendar.dart` and `lib/booking/ui/pages/manager_page/list_booking.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 (9 lines × 2) lib/booking/ui/calendar/calendar_dialog_button.dart:32— lib/booking/ui/calendar/calendar_dialog_button.dart:32-40 | lib/booking/ui/pages/detail_pages/contact_button.dart:10-18 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `lib/booking/ui/calendar/calendar_dialog_button.dart:32` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) lib/others/ui/loading_page.dart:18— lib/others/ui/loading_page.dart:18-26 | lib/tools/ui/layouts/app_template.dart:14-22 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `lib/others/ui/loading_page.dart:18` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `lib/others/ui/loading_page.dart:27` calls `read` and `lib/tools/ui/layouts/app_template.dart:23` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (9 lines × 2) lib/booking/providers/confirmed_booking_list_provider.dart:22— lib/booking/providers/confirmed_booking_list_provider.dart:22-30 | lib/booking/providers/manager_confirmed_booking_list_provider.dart:22-30 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (6 lines × 2) lib/user/class/simple_users.dart:19— lib/user/class/simple_users.dart:19-24 | lib/user/class/user.dart:37-42 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (6 lines × 2) lib/advert/class/tag.dart:12— lib/advert/class/tag.dart:12-17 | lib/loan/class/item_simple.dart:11-16 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (6 lines × 2) lib/user/class/simple_users.dart:45— lib/user/class/simple_users.dart:45-50 | lib/user/class/user.dart:135-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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (6 lines × 2) lib/admin/class/account_type.dart:19— lib/admin/class/account_type.dart:19-24 | lib/seed-library/class/species_type.dart:16-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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Hotspot: lib/loan/ui/pages/admin_page/loan_card.dart lib/loan/ui/pages/admin_page/loan_card.dart:29— lib/loan/ui/pages/admin_page/loan_card.dart changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 34 in LoanCard.build at line 29. 1 of those changes was a fix/bug commit, and the other 1 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-06..2026-11-04, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-06 13:29:44 +01:00' --until='2026-11-04 13:29:44 +01:00' --full-history --no-merges -- lib/loan/ui/pages/admin_page/loan_card.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: lib/mypayment/ui/pages/store_admin_page/seller_right_card.dart lib/mypayment/ui/pages/store_admin_page/seller_right_card.dart:24— lib/mypayment/ui/pages/store_admin_page/seller_right_card.dart changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 28 in SellerRightCard.build at line 24. 1 of those changes was a fix/bug commit, and the other 1 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-06..2026-11-04, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-06 13:29:44 +01:00' --until='2026-11-04 13:29:44 +01:00' --full-history --no-merges -- lib/mypayment/ui/pages/store_admin_page/seller_right_card.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: lib/mypayment/ui/components/transaction_card.dart lib/mypayment/ui/components/transaction_card.dart:22— lib/mypayment/ui/components/transaction_card.dart changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 17 in TransactionCard.build at line 22. 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-06..2026-11-04, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-06 13:29:44 +01:00' --until='2026-11-04 13:29:44 +01:00' --full-history --no-merges -- lib/mypayment/ui/components/transaction_card.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.
D4 · Code Duplication· Edited copy of a member (26 corresponding lines) · ×3
Edited copy of a member (26 corresponding lines) lib/seed-library/ui/pages/plant_deposit_page/small_plant_card.dart:19— lib/seed-library/ui/pages/plant_deposit_page/small_plant_card.dart:19-48 | lib/seed-library/ui/pages/plant_deposit_page/small_species_card.dart:16-41 — These two members are one piece of code written twice and then edited apart: 26 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (26 corresponding lines) lib/phonebook/ui/pages/main_page/association_card.dart:19— lib/phonebook/ui/pages/main_page/association_card.dart:19-45 | lib/phonebook/ui/pages/member_detail_page/membership_card.dart:19-44 — These two members are one piece of code written twice and then edited apart: 26 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (26 corresponding lines) lib/amap/ui/amap.dart:12— lib/amap/ui/amap.dart:12-37 | lib/seed-library/ui/seed_library.dart:12-39 — These two members are one piece of code written twice and then edited apart: 26 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (14 corresponding lines) · ×3
Edited copy of a member (14 corresponding lines) lib/amap/ui/pages/admin_page/adding_user_container.dart:13— lib/amap/ui/pages/admin_page/adding_user_container.dart:13-26 | lib/amap/ui/pages/admin_page/cash_container.dart:13-27 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (14 corresponding lines) lib/tools/providers/map_provider.dart:65— lib/tools/providers/map_provider.dart:65-78 | lib/tools/providers/map_provider.dart:80-93 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (14 corresponding lines) lib/purchases/ui/purchases.dart:11— lib/purchases/ui/purchases.dart:11-24 | lib/raffle/ui/raffle.dart:11-24 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (13 corresponding lines) · ×3
Edited copy of a member (13 corresponding lines) lib/loan/providers/history_loaner_loan_list_provider.dart:65— lib/loan/providers/history_loaner_loan_list_provider.dart:65-77 | lib/loan/providers/loaner_loan_list_provider.dart:64-76 — 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.
Edited copy of a member (13 corresponding lines) lib/mypayment/repositories/invoices_repository.dart:36— lib/mypayment/repositories/invoices_repository.dart:36-48 | lib/mypayment/repositories/invoices_repository.dart:50-63 — 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.
Edited copy of a member (13 corresponding lines) lib/mypayment/class/store.dart:57— lib/mypayment/class/store.dart:57-69 | lib/mypayment/class/wallet_device.dart:49-63 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (7 corresponding lines) · ×3
Edited copy of a member (7 corresponding lines) lib/loan/providers/history_loaner_loan_list_provider.dart:25— lib/loan/providers/history_loaner_loan_list_provider.dart:25-31 | lib/loan/providers/loaner_loan_list_provider.dart:24-30 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (7 corresponding lines) lib/admin/providers/group_logo_provider.dart:14— lib/admin/providers/group_logo_provider.dart:14-20 | lib/advert/repositories/advert_poster_repository.dart:13-19 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (7 corresponding lines) lib/mypayment/class/qr_code_data.dart:28— lib/mypayment/class/qr_code_data.dart:28-35 | lib/mypayment/class/qr_code_signature_data.dart:25-31 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (25 lines × 2) lib/mypayment/ui/pages/invoices_admin_page/invoices_admin_page.dart:78— lib/mypayment/ui/pages/invoices_admin_page/invoices_admin_page.dart:78-102 | lib/mypayment/ui/pages/invoices_structure_page/invoices_structure_page.dart:67-91 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `lib/mypayment/ui/pages/invoices_admin_page/invoices_admin_page.dart:78` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (25 lines × 2) lib/raffle/ui/pages/admin_module_page/confirm_creation.dart:39— lib/raffle/ui/pages/admin_module_page/confirm_creation.dart:39-63 | lib/raffle/ui/pages/raffle_page/confirm_payment.dart:65-89 — before extracting anything, compare `lib/raffle/ui/pages/admin_module_page/confirm_creation.dart` and `lib/raffle/ui/pages/raffle_page/confirm_payment.dart` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 115 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `lib/raffle/ui/pages/admin_module_page/confirm_creation.dart:39` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (25 lines × 2) lib/drawer/providers/animation_provider.dart:7— lib/drawer/providers/animation_provider.dart:7-31 | lib/login/providers/animation_provider.dart:7-31 — before extracting anything, compare `lib/drawer/providers/animation_provider.dart` and `lib/login/providers/animation_provider.dart` as WHOLE FILES: 86% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (23 lines × 2) lib/mypayment/ui/pages/main_page/account_card/last_transactions.dart:19— lib/mypayment/ui/pages/main_page/account_card/last_transactions.dart:19-41 | lib/mypayment/ui/pages/main_page/seller_card/store_list.dart:23-45 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `lib/mypayment/ui/pages/main_page/account_card/last_transactions.dart:19` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `lib/mypayment/ui/pages/main_page/seller_card/store_list.dart:20` calls `watch` and `lib/mypayment/ui/pages/main_page/account_card/last_transactions.dart:17` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (23 lines × 2) lib/raffle/ui/pages/creation_edit_page/creation_edit_page.dart:325— lib/raffle/ui/pages/creation_edit_page/creation_edit_page.dart:325-347 | lib/raffle/ui/pages/creation_edit_page/creation_edit_page.dart:353-375 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `lib/raffle/ui/pages/creation_edit_page/creation_edit_page.dart:325` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (23 lines × 2) lib/raffle/ui/pages/raffle_page/buy_pack_ticket_card.dart:22— lib/raffle/ui/pages/raffle_page/buy_pack_ticket_card.dart:22-44 | lib/raffle/ui/pages/raffle_page/buy_type_ticket_card.dart:22-44 — before extracting anything, compare `lib/raffle/ui/pages/raffle_page/buy_pack_ticket_card.dart` and `lib/raffle/ui/pages/raffle_page/buy_type_ticket_card.dart` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 231 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `lib/raffle/ui/pages/raffle_page/buy_pack_ticket_card.dart:22` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (21–22 lines × 2) lib/admin/ui/pages/groups/edit_group_page/edit_group_page.dart:112— lib/admin/ui/pages/groups/edit_group_page/edit_group_page.dart:112-133 | lib/admin/ui/pages/schools/edit_school_page/edit_school_page.dart:88-108 — before extracting anything, compare `lib/admin/ui/pages/groups/edit_group_page/edit_group_page.dart` and `lib/admin/ui/pages/schools/edit_school_page/edit_school_page.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. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `lib/admin/ui/pages/groups/edit_group_page/edit_group_page.dart:112` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (21–22 lines × 2) lib/drawer/ui/email_change_popup.dart:340— lib/drawer/ui/email_change_popup.dart:340-361 | lib/tools/ui/widgets/custom_dialog_box.dart:181-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. Read the line range as the matched WINDOW rather than a finished unit: at `lib/drawer/ui/email_change_popup.dart:340` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (21–22 lines × 2) lib/settings/ui/pages/edit_user_page/edit_user_page.dart:112— lib/settings/ui/pages/edit_user_page/edit_user_page.dart:112-132 | lib/settings/ui/pages/edit_user_page/edit_user_page.dart:143-164 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `lib/settings/ui/pages/edit_user_page/edit_user_page.dart:112` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (20 lines × 3) lib/admin/ui/pages/groups/group_page/group_page.dart:57— lib/admin/ui/pages/groups/group_page/group_page.dart:57-76 | lib/admin/ui/pages/memberships/association_membership_page/association_membership_page.dart:61-80 | lib/admin/ui/pages/schools/school_page/school_page.dart:46-65 — before extracting anything, compare `lib/admin/ui/pages/memberships/association_membership_page/association_membership_page.dart` and `lib/admin/ui/pages/schools/school_page/school_page.dart` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 65 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `lib/admin/ui/pages/groups/group_page/group_page.dart:57` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (20 lines × 3) lib/amap/ui/components/order_ui.dart:183— lib/amap/ui/components/order_ui.dart:183-202 | lib/amap/ui/pages/admin_page/delivery_ui.dart:230-249 | lib/amap/ui/pages/detail_delivery_page/order_detail_ui.dart:176-195 — before extracting anything, compare `lib/amap/ui/components/order_ui.dart` and `lib/amap/ui/pages/detail_delivery_page/order_detail_ui.dart` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 49 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `lib/amap/ui/components/order_ui.dart:183` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (20 lines × 3) lib/raffle/ui/pages/creation_edit_page/prize_handler.dart:82— lib/raffle/ui/pages/creation_edit_page/prize_handler.dart:82-101 | lib/raffle/ui/pages/creation_edit_page/ticket_handler.dart:30-49 | lib/raffle/ui/pages/creation_edit_page/winning_ticket_handler.dart:13-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 all 3 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `lib/raffle/ui/pages/creation_edit_page/prize_handler.dart:82` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (18 lines × 2) lib/booking/ui/pages/admin_pages/admin_page.dart:114— lib/booking/ui/pages/admin_pages/admin_page.dart:114-131 | lib/booking/ui/pages/admin_pages/admin_page.dart:188-205 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `lib/booking/ui/pages/admin_pages/admin_page.dart:114` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (18 lines × 2) lib/booking/ui/pages/detail_pages/detail_booking.dart:130— lib/booking/ui/pages/detail_pages/detail_booking.dart:130-147 | lib/event/ui/pages/detail_page/detail_page.dart:101-118 — before extracting anything, compare `lib/booking/ui/pages/detail_pages/detail_booking.dart` and `lib/event/ui/pages/detail_page/detail_page.dart` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 73 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `lib/booking/ui/pages/detail_pages/detail_booking.dart:130` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (18 lines × 2) lib/mypayment/ui/pages/main_page/account_card/day_divider.dart:29— lib/mypayment/ui/pages/main_page/account_card/day_divider.dart:29-46 | lib/mypayment/ui/pages/main_page/seller_card/store_divider.dart:28-45 — before extracting anything, compare `lib/mypayment/ui/pages/main_page/account_card/day_divider.dart` and `lib/mypayment/ui/pages/main_page/seller_card/store_divider.dart` as WHOLE FILES: 83% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `lib/mypayment/ui/pages/main_page/account_card/day_divider.dart:29` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (16–17 lines × 2) lib/admin/ui/pages/groups/edit_group_page/edit_group_page.dart:61— lib/admin/ui/pages/groups/edit_group_page/edit_group_page.dart:61-77 | lib/admin/ui/pages/schools/edit_school_page/edit_school_page.dart:41-56 — before extracting anything, compare `lib/admin/ui/pages/groups/edit_group_page/edit_group_page.dart` and `lib/admin/ui/pages/schools/edit_school_page/edit_school_page.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. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `lib/admin/ui/pages/groups/edit_group_page/edit_group_page.dart:61` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (16–17 lines × 2) lib/mypayment/ui/pages/main_page/seller_card/admin_invoice_card.dart:38— lib/mypayment/ui/pages/main_page/seller_card/admin_invoice_card.dart:38-54 | lib/mypayment/ui/pages/main_page/seller_card/structure_admin_card.dart:50-65 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `lib/mypayment/ui/pages/main_page/seller_card/admin_invoice_card.dart:38` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (16–17 lines × 2) lib/mypayment/ui/pages/stats_page/sum_up_chart.dart:123— lib/mypayment/ui/pages/stats_page/sum_up_chart.dart:123-139 | lib/mypayment/ui/pages/stats_page/sum_up_chart.dart:145-160 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `lib/mypayment/ui/pages/stats_page/sum_up_chart.dart:123` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `lib/mypayment/ui/pages/stats_page/sum_up_chart.dart:120` calls `Row` and `lib/mypayment/ui/pages/stats_page/sum_up_chart.dart:144` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (10–12 lines × 2) lib/admin/ui/pages/groups/edit_group_page/edit_group_page.dart:79— lib/admin/ui/pages/groups/edit_group_page/edit_group_page.dart:79-90 | lib/admin/ui/pages/schools/edit_school_page/edit_school_page.dart:58-67 — before extracting anything, compare `lib/admin/ui/pages/groups/edit_group_page/edit_group_page.dart` and `lib/admin/ui/pages/schools/edit_school_page/edit_school_page.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. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `lib/admin/ui/pages/groups/edit_group_page/edit_group_page.dart:79` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (10–12 lines × 2) lib/mypayment/ui/pages/invoices_admin_page/invoice_card.dart:95— lib/mypayment/ui/pages/invoices_admin_page/invoice_card.dart:95-106 | lib/mypayment/ui/pages/invoices_admin_page/invoice_card.dart:127-136 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `lib/mypayment/ui/pages/invoices_admin_page/invoice_card.dart:95` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (10–12 lines × 2) lib/phonebook/ui/pages/association_editor_page/association_information_editor.dart:334— lib/phonebook/ui/pages/association_editor_page/association_information_editor.dart:334-345 | lib/settings/ui/pages/edit_user_page/edit_user_page.dart:363-372 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `lib/phonebook/ui/pages/association_editor_page/association_information_editor.dart:334` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (11 lines × 3) lib/admin/ui/pages/memberships/association_membership_detail_page/association_membership_information_editor.dart:113— lib/admin/ui/pages/memberships/association_membership_detail_page/association_membership_information_editor.dart:113-123 | lib/phonebook/ui/pages/association_creation_page/association_creation_page.dart:84-94 | lib/settings/ui/pages/edit_user_page/edit_user_page.dart:361-371 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `lib/admin/ui/pages/memberships/association_membership_detail_page/association_membership_information_editor.dart:113` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 3) lib/drawer/ui/email_change_popup.dart:56— lib/drawer/ui/email_change_popup.dart:56-66 | lib/mypayment/ui/pages/main_page/account_card/device_dialog_box.dart:47-57 | lib/tools/ui/widgets/custom_dialog_box.dart:50-60 — before extracting anything, compare `lib/mypayment/ui/pages/main_page/account_card/device_dialog_box.dart` and `lib/tools/ui/widgets/custom_dialog_box.dart` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 52 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `lib/drawer/ui/email_change_popup.dart:56` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 3) lib/phonebook/ui/pages/main_page/association_card.dart:19— lib/phonebook/ui/pages/main_page/association_card.dart:19-29 | lib/phonebook/ui/pages/member_detail_page/membership_card.dart:19-29 | lib/purchases/ui/pages/history_page/purchase_card.dart:17-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. Read the line range as the matched WINDOW rather than a finished unit: at `lib/phonebook/ui/pages/main_page/association_card.dart:19` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (9 lines × 3) lib/admin/ui/pages/groups/group_page/group_ui.dart:53— lib/admin/ui/pages/groups/group_page/group_ui.dart:53-61 | lib/admin/ui/pages/memberships/association_membership_page/association_membership_ui.dart:41-49 | lib/admin/ui/pages/schools/school_page/school_ui.dart:42-50 — before extracting anything, compare `lib/admin/ui/pages/groups/group_page/group_ui.dart` and `lib/admin/ui/pages/memberships/association_membership_page/association_membership_ui.dart` as WHOLE FILES: this scan already matched 3 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. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `lib/admin/ui/pages/groups/group_page/group_ui.dart:53` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (9 lines × 3) lib/booking/ui/pages/booking_pages/add_edit_booking_page.dart:311— lib/booking/ui/pages/booking_pages/add_edit_booking_page.dart:311-319 | lib/cinema/ui/pages/session_pages/add_edit_session.dart:230-238 | lib/event/ui/pages/event_pages/add_edit_event_page.dart:384-392 — before extracting anything, compare `lib/booking/ui/pages/booking_pages/add_edit_booking_page.dart` and `lib/event/ui/pages/event_pages/add_edit_event_page.dart` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 55 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `lib/booking/ui/pages/booking_pages/add_edit_booking_page.dart:311` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 3) lib/tools/repository/csv_repository.dart:13— lib/tools/repository/csv_repository.dart:13-21 | lib/tools/repository/logo_repository.dart:16-24 | lib/tools/repository/pdf_repository.dart:17-25 — before extracting anything, compare `lib/tools/repository/csv_repository.dart` and `lib/tools/repository/pdf_repository.dart` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 85 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `lib/tools/repository/csv_repository.dart:13` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (5 lines × 3) lib/admin/providers/is_expanded_list_provider.dart:8— lib/admin/providers/is_expanded_list_provider.dart:8-12 | lib/amap/providers/selected_list_provider.dart:20-24 | lib/event/providers/selected_days_provider.dart:11-15 — 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 × 3) lib/amap/repositories/delivery_product_list_repository.dart:11— lib/amap/repositories/delivery_product_list_repository.dart:11-15 | lib/loan/repositories/item_repository.dart:17-21 | lib/mypayment/repositories/store_sellers_repository.dart:11-15 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (5 lines × 3) lib/purchases/providers/ticket_list_provider.dart:13— lib/purchases/providers/ticket_list_provider.dart:13-17 | lib/raffle/providers/pack_ticket_list_provider.dart:16-20 | lib/raffle/providers/user_tickets_provider.dart:14-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 (7 lines × 3) lib/advert/class/announcer.dart:17— lib/advert/class/announcer.dart:17-23 | lib/loan/class/loaner.dart:13-19 | lib/ph/class/ph_admin.dart:13-19 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (7 lines × 3) lib/cinema/providers/cinema_topic_provider.dart:18— lib/cinema/providers/cinema_topic_provider.dart:18-24 | lib/cinema/providers/cinema_topic_provider.dart:26-32 | lib/service/providers/topic_provider.dart:19-25 — 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 (7 lines × 3) lib/cinema/repositories/session_poster_repository.dart:15— lib/cinema/repositories/session_poster_repository.dart:15-21 | lib/raffle/repositories/tombola_logo_repository.dart:12-18 | lib/vote/repositories/contender_logo_repository.dart:14-20 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication· Edited copy of a member (27 corresponding lines) · ×2
Edited copy of a member (27 corresponding lines) lib/tools/constants.dart:95— lib/tools/constants.dart:95-121 | lib/tools/constants.dart:122-148 — These two members are one piece of code written twice and then edited apart: 27 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (27 corresponding lines) lib/booking/ui/pages/booking_pages/checkbox_entry.dart:14— lib/booking/ui/pages/booking_pages/checkbox_entry.dart:14-43 | lib/event/ui/pages/event_pages/checkbox_entry.dart:14-40 — These two members are one piece of code written twice and then edited apart: 27 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (31 corresponding lines) · ×2
Edited copy of a member (31 corresponding lines) lib/booking/class/booking.dart:74— lib/booking/class/booking.dart:74-104 | lib/event/class/event.dart:81-112 — These two members are one piece of code written twice and then edited apart: 31 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (31 corresponding lines) lib/admin/ui/pages/main_page/menu_card_ui.dart:9— lib/admin/ui/pages/main_page/menu_card_ui.dart:9-39 | lib/seed-library/ui/pages/main_page/menu_card_ui.dart:10-40 — These two members are one piece of code written twice and then edited apart: 31 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (21 corresponding lines) · ×2
Edited copy of a member (21 corresponding lines) lib/centralassociation/repositories/asso_repository.dart:18— lib/centralassociation/repositories/asso_repository.dart:18-38 | lib/centralisation/repositories/section_repository.dart:18-41 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (21 corresponding lines) lib/amap/tools/amap_background_painter.dart:40— lib/amap/tools/amap_background_painter.dart:40-64 | lib/raffle/tools/winning_ticket_background_painter.dart:65-85 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (19 corresponding lines) · ×2
Edited copy of a member (19 corresponding lines) lib/amap/providers/delivery_list_provider.dart:79— lib/amap/providers/delivery_list_provider.dart:79-99 | lib/amap/providers/user_order_list_provider.dart:80-98 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (19 corresponding lines) lib/mypayment/class/seller.dart:46— lib/mypayment/class/seller.dart:46-64 | lib/mypayment/class/user_store.dart:48-70 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (10 corresponding lines) · ×2
Edited copy of a member (10 corresponding lines) lib/user/repositories/user_repository.dart:23— lib/user/repositories/user_repository.dart:23-32 | lib/user/repositories/user_repository.dart:34-43 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (10 corresponding lines) lib/amap/repositories/delivery_list_repository.dart:50— lib/amap/repositories/delivery_list_repository.dart:50-59 | lib/phonebook/repositories/association_member_repository.dart:10-19 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (6 corresponding lines) · ×2
Edited copy of a member (6 corresponding lines) lib/admin/class/group.dart:16— lib/admin/class/group.dart:16-23 | lib/centralassociation/class/asso.dart:10-15 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (6 corresponding lines) lib/admin/class/group.dart:34— lib/admin/class/group.dart:34-44 | lib/admin/class/simple_group.dart:25-30 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 8+ corresponding lines) · ×2
Edited copies of one member (3 members, 8+ corresponding lines) lib/admin/providers/association_membership_members_list_provider.dart:57— lib/admin/providers/association_membership_members_list_provider.dart:57-70 | lib/mypayment/providers/invoice_list_provider.dart:55-62 | lib/phonebook/providers/association_member_list_provider.dart:39-49 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 8+ corresponding lines) lib/amap/providers/delivery_product_list_provider.dart:33— lib/amap/providers/delivery_product_list_provider.dart:33-40 | lib/loan/providers/item_list_provider.dart:29-36 | lib/mypayment/providers/structure_list_provider.dart:26-34 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (12 corresponding lines) · ×2
Edited copy of a member (12 corresponding lines) lib/purchases/class/purchase.dart:34— lib/purchases/class/purchase.dart:34-45 | lib/purchases/class/ticket.dart:37-49 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (12 corresponding lines) lib/seed-library/class/information.dart:42— lib/seed-library/class/information.dart:42-54 | lib/vote/class/section.dart:7-18 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 5+ corresponding lines) · ×2
Edited copies of one member (3 members, 5+ corresponding lines) lib/purchases/repositories/user_information_repository.dart:16— lib/purchases/repositories/user_information_repository.dart:16-20 | lib/raffle/repositories/prize_repository.dart:30-37 | lib/raffle/repositories/prizes_repository.dart:30-37 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 5 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 5+ corresponding lines) lib/advert/class/announcer.dart:11— lib/advert/class/announcer.dart:11-15 | lib/loan/class/loaner.dart:7-11 | lib/ph/class/ph_admin.dart:7-11 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 5 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (5 corresponding lines) · ×2
Edited copy of a member (5 corresponding lines) lib/phonebook/class/member.dart:19— lib/phonebook/class/member.dart:19-23 | lib/user/class/applicant.dart:19-23 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (5 corresponding lines) lib/raffle/providers/ticket_list_provider.dart:22— lib/raffle/providers/ticket_list_provider.dart:22-26 | lib/raffle/providers/user_tickets_provider.dart:24-28 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 4+ corresponding lines) · ×2
Edited copies of one member (3 members, 4+ corresponding lines) lib/phonebook/class/association_groupement.dart:18— lib/phonebook/class/association_groupement.dart:18-25 | lib/purchases/class/seller.dart:14-17 | lib/purchases/class/ticket_generator.dart:26-35 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 4 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 4+ corresponding lines) lib/phonebook/class/member.dart:76— lib/phonebook/class/member.dart:76-79 | lib/purchases/class/user_ticket.dart:50-53 | lib/user/class/applicant.dart:65-68 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 4 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Duplicated block (53 lines × 2) lib/mypayment/ui/pages/devices_page/devices_page.dart:151— lib/mypayment/ui/pages/devices_page/devices_page.dart:151-203 | lib/mypayment/ui/pages/devices_page/devices_page.dart:269-321 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `lib/mypayment/ui/pages/devices_page/devices_page.dart:151` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (53 lines × 2) lib/tools/repository/csv_repository.dart:14— lib/tools/repository/csv_repository.dart:14-66 | lib/tools/repository/pdf_repository.dart:18-70 — before extracting anything, compare `lib/tools/repository/csv_repository.dart` and `lib/tools/repository/pdf_repository.dart` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 85 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `lib/tools/repository/csv_repository.dart:14` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (29–30 lines × 2) lib/mypayment/ui/pages/stats_page/month_section_summary.dart:32— lib/mypayment/ui/pages/stats_page/month_section_summary.dart:32-60 | lib/mypayment/ui/pages/stats_page/sum_up_card.dart:36-65 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `lib/mypayment/ui/pages/stats_page/month_section_summary.dart:32` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (29–30 lines × 2) lib/phonebook/ui/pages/association_page/association_page.dart:138— lib/phonebook/ui/pages/association_page/association_page.dart:138-166 | lib/phonebook/ui/pages/association_page/association_page.dart:183-212 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `lib/phonebook/ui/pages/association_page/association_page.dart:138` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (26–27 lines × 2) lib/mypayment/ui/pages/scan_page/scanner.dart:125— lib/mypayment/ui/pages/scan_page/scanner.dart:125-150 | lib/purchases/ui/pages/scan_page/qr_code_scanner.dart:38-64 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (26–27 lines × 2) lib/raffle/ui/pages/creation_edit_page/user_cash_ui.dart:68— lib/raffle/ui/pages/creation_edit_page/user_cash_ui.dart:68-94 | lib/raffle/ui/pages/creation_edit_page/user_cash_ui.dart:159-184 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `lib/raffle/ui/pages/creation_edit_page/user_cash_ui.dart:68` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (27 lines × 2) lib/raffle/ui/pages/admin_module_page/confirm_creation.dart:77— lib/raffle/ui/pages/admin_module_page/confirm_creation.dart:77-103 | lib/raffle/ui/pages/raffle_page/confirm_payment.dart:215-241 — before extracting anything, compare `lib/raffle/ui/pages/admin_module_page/confirm_creation.dart` and `lib/raffle/ui/pages/raffle_page/confirm_payment.dart` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 115 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (27 lines × 2) lib/seed-library/ui/pages/edit_plant_detail_page/editable_plant_detail.dart:66— lib/seed-library/ui/pages/edit_plant_detail_page/editable_plant_detail.dart:66-92 | lib/seed-library/ui/pages/plant_detail_page/plant_detail_page.dart:63-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 (22–23 lines × 2) lib/raffle/ui/pages/pack_ticket_page/add_edit_pack_ticket_page.dart:132— lib/raffle/ui/pages/pack_ticket_page/add_edit_pack_ticket_page.dart:132-154 | lib/raffle/ui/pages/prize_page/add_edit_prize_page.dart:99-120 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `lib/raffle/ui/pages/pack_ticket_page/add_edit_pack_ticket_page.dart:132` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (22–23 lines × 2) lib/seed-library/ui/pages/edit_plant_detail_page/editable_plant_detail.dart:93— lib/seed-library/ui/pages/edit_plant_detail_page/editable_plant_detail.dart:93-114 | lib/seed-library/ui/pages/plant_detail_page/plant_detail_page.dart:103-125 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `lib/seed-library/ui/pages/edit_plant_detail_page/editable_plant_detail.dart:93` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (18 lines × 3) lib/phonebook/ui/pages/association_editor_page/member_editable_card.dart:80— lib/phonebook/ui/pages/association_editor_page/member_editable_card.dart:80-97 | lib/phonebook/ui/pages/association_page/member_card.dart:68-85 | lib/phonebook/ui/pages/association_page/web_member_card.dart:69-86 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `lib/phonebook/ui/pages/association_editor_page/member_editable_card.dart:80` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (18 lines × 3) lib/seed-library/ui/pages/add_edit_species_page/add_edit_species_page.dart:199— lib/seed-library/ui/pages/add_edit_species_page/add_edit_species_page.dart:199-216 | lib/seed-library/ui/pages/edit_presentation_page/edit_information_page.dart:84-101 | lib/seed-library/ui/pages/plant_deposit_page/plant_deposit_page.dart:189-206 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `lib/seed-library/ui/pages/add_edit_species_page/add_edit_species_page.dart:199` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (17 lines × 4) lib/booking/ui/pages/detail_pages/detail_booking.dart:136— lib/booking/ui/pages/detail_pages/detail_booking.dart:136-152 | lib/booking/ui/pages/detail_pages/detail_booking.dart:163-179 | lib/event/ui/pages/detail_page/detail_page.dart:107-123 | lib/event/ui/pages/detail_page/detail_page.dart:153-169 — before extracting anything, compare `lib/booking/ui/pages/detail_pages/detail_booking.dart` and `lib/event/ui/pages/detail_page/detail_page.dart` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 73 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `lib/booking/ui/pages/detail_pages/detail_booking.dart:136` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (17 lines × 4) lib/raffle/ui/pages/admin_module_page/account_handler.dart:91— lib/raffle/ui/pages/admin_module_page/account_handler.dart:91-107 | lib/raffle/ui/pages/admin_module_page/tombola_handler.dart:101-117 | lib/raffle/ui/pages/creation_edit_page/user_cash_ui.dart:72-88 | lib/raffle/ui/pages/creation_edit_page/user_cash_ui.dart:163-179 — before extracting anything, compare `lib/raffle/ui/pages/admin_module_page/account_handler.dart` and `lib/raffle/ui/pages/admin_module_page/tombola_handler.dart` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 85 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `lib/raffle/ui/pages/admin_module_page/account_handler.dart:91` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13–14 lines × 3) lib/admin/ui/pages/memberships/association_membership_detail_page/association_membership_information_editor.dart:46— lib/admin/ui/pages/memberships/association_membership_detail_page/association_membership_information_editor.dart:46-58 | lib/phonebook/ui/pages/association_editor_page/association_information_editor.dart:66-79 | lib/phonebook/ui/pages/association_editor_page/association_information_editor.dart:114-127 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `lib/admin/ui/pages/memberships/association_membership_detail_page/association_membership_information_editor.dart:46` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (13–14 lines × 3) lib/tools/repository/csv_repository.dart:35— lib/tools/repository/csv_repository.dart:35-48 | lib/tools/repository/pdf_repository.dart:39-52 | lib/tools/repository/pdf_repository.dart:149-161 — before extracting anything, compare `lib/tools/repository/csv_repository.dart` and `lib/tools/repository/pdf_repository.dart` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 85 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `lib/tools/repository/csv_repository.dart:35` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (13 lines × 5) lib/admin/ui/pages/groups/edit_group_page/search_user.dart:76— lib/admin/ui/pages/groups/edit_group_page/search_user.dart:76-88 | lib/admin/ui/pages/structure_page/add_edit_structure_page/search_user.dart:42-54 | lib/mypayment/ui/pages/structure_administrators_page/structure_administrator_page.dart:73-85 | lib/others/ui/no_internet_page.dart:49-61 | lib/settings/ui/pages/edit_user_page/edit_user_page.dart:267-279 — before extracting anything, compare `lib/admin/ui/pages/groups/edit_group_page/search_user.dart` and `lib/admin/ui/pages/structure_page/add_edit_structure_page/search_user.dart` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 49 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `lib/admin/ui/pages/groups/edit_group_page/search_user.dart:76` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 5) lib/raffle/ui/pages/admin_module_page/account_handler.dart:90— lib/raffle/ui/pages/admin_module_page/account_handler.dart:90-103 | lib/raffle/ui/pages/admin_module_page/tombola_card.dart:18-30 | lib/raffle/ui/pages/admin_module_page/tombola_handler.dart:100-113 | lib/raffle/ui/pages/creation_edit_page/user_cash_ui.dart:71-84 | lib/raffle/ui/pages/creation_edit_page/user_cash_ui.dart:162-175 — before extracting anything, compare `lib/raffle/ui/pages/admin_module_page/account_handler.dart` and `lib/raffle/ui/pages/admin_module_page/tombola_handler.dart` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 85 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `lib/raffle/ui/pages/admin_module_page/account_handler.dart:90` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (13 lines × 3) lib/admin/ui/pages/memberships/association_membership_detail_page/research_bar.dart:18— lib/admin/ui/pages/memberships/association_membership_detail_page/research_bar.dart:18-30 | lib/phonebook/ui/pages/admin_page/association_research_bar.dart:18-30 | lib/phonebook/ui/pages/main_page/research_bar.dart:19-31 — before extracting anything, compare `lib/admin/ui/pages/memberships/association_membership_detail_page/research_bar.dart` and `lib/phonebook/ui/pages/main_page/research_bar.dart` as WHOLE FILES: 87% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `lib/admin/ui/pages/memberships/association_membership_detail_page/research_bar.dart:18` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (13 lines × 3) lib/raffle/ui/pages/raffle_page/buy_pack_ticket_card.dart:94— lib/raffle/ui/pages/raffle_page/buy_pack_ticket_card.dart:94-106 | lib/raffle/ui/pages/raffle_page/buy_type_ticket_card.dart:94-106 | lib/raffle/ui/pages/raffle_page/confirm_payment.dart:125-138 — before extracting anything, compare `lib/raffle/ui/pages/raffle_page/buy_pack_ticket_card.dart` and `lib/raffle/ui/pages/raffle_page/buy_type_ticket_card.dart` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 231 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `lib/raffle/ui/pages/raffle_page/buy_pack_ticket_card.dart:94` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (12 lines × 3) lib/centralassociation/ui/pages/link_card.dart:17— lib/centralassociation/ui/pages/link_card.dart:17-28 | lib/centralisation/ui/pages/liked_card.dart:24-35 | lib/centralisation/ui/pages/module_card.dart:20-31 — 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 (12 lines × 3) lib/settings/ui/pages/log_page/log_tab.dart:51— lib/settings/ui/pages/log_page/log_tab.dart:51-62 | lib/settings/ui/pages/log_page/notification_tab.dart:51-62 | lib/tools/ui/widgets/admin_button.dart:38-49 — before extracting anything, compare `lib/settings/ui/pages/log_page/log_tab.dart` and `lib/settings/ui/pages/log_page/notification_tab.dart` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 65 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `lib/settings/ui/pages/log_page/log_tab.dart:51` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (8 lines × 3) lib/mypayment/ui/pages/main_page/account_card/device_dialog_box.dart:57— lib/mypayment/ui/pages/main_page/account_card/device_dialog_box.dart:57-64 | lib/mypayment/ui/pages/store_admin_page/seller_right_dialog.dart:58-65 | lib/tools/ui/widgets/custom_dialog_box.dart:60-67 — before extracting anything, compare `lib/mypayment/ui/pages/main_page/account_card/device_dialog_box.dart` and `lib/tools/ui/widgets/custom_dialog_box.dart` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 52 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `lib/mypayment/ui/pages/main_page/account_card/device_dialog_box.dart:57` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 3) lib/raffle/providers/prize_list_provider.dart:29— lib/raffle/providers/prize_list_provider.dart:29-36 | lib/seed-library/providers/plants_list_provider.dart:28-35 | lib/seed-library/providers/species_list_provider.dart:30-37 — 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.
AddEditBookingPage.build (cyclomatic 40) lib/booking/ui/pages/booking_pages/add_edit_booking_page.dart:39— AddEditBookingPage.build has cyclomatic complexity 40 (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.
AddEditEventPage.build (cyclomatic 40) lib/event/ui/pages/event_pages/add_edit_event_page.dart:32— AddEditEventPage.build has cyclomatic complexity 40 (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.
LoanCard.build (cyclomatic 34) lib/loan/ui/pages/admin_page/loan_card.dart:29— LoanCard.build 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.
AddEditStructurePage.build (cyclomatic 32) lib/admin/ui/pages/structure_page/add_edit_structure_page/add_edit_structure_page.dart:27— AddEditStructurePage.build has cyclomatic complexity 32 (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.
DeliveryUi.build (cyclomatic 32) lib/amap/ui/pages/admin_page/delivery_ui.dart:28— DeliveryUi.build has cyclomatic complexity 32 (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.
BookingCard.build (cyclomatic 31) lib/booking/ui/components/booking_card.dart:32— BookingCard.build has cyclomatic complexity 31 (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.
EventUi.build (cyclomatic 30) lib/event/ui/components/event_ui.dart:35— EventUi.build has cyclomatic complexity 30 (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.
AddEditSessionPage.build (cyclomatic 28) lib/cinema/ui/pages/session_pages/add_edit_session.dart:29— AddEditSessionPage.build 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.
SellerRightCard.build (cyclomatic 28) lib/mypayment/ui/pages/store_admin_page/seller_right_card.dart:24— SellerRightCard.build 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.
AssociationEditorPage.build (cyclomatic 25) lib/phonebook/ui/pages/association_editor_page/association_editor_page.dart:35— AssociationEditorPage.build has cyclomatic complexity 25 (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.
DevicesPage.build (cyclomatic 24) lib/mypayment/ui/pages/devices_page/devices_page.dart:30— DevicesPage.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.
AdvertAddEditAdvertPage.build (cyclomatic 22) lib/advert/ui/pages/form_page/add_edit_advert_page.dart:30— AdvertAddEditAdvertPage.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.
MembershipEditorPage.build (cyclomatic 22) lib/phonebook/ui/pages/membership_editor_page/membership_editor_page.dart:31— MembershipEditorPage.build has cyclomatic complexity 22 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
AdminPage.build (cyclomatic 22) lib/vote/ui/pages/admin_page/admin_page.dart:33— AdminPage.build has cyclomatic complexity 22 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
InvoiceCard.build (cyclomatic 21) lib/mypayment/ui/pages/invoices_admin_page/invoice_card.dart:23— InvoiceCard.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.
AddEditSpeciesPage.build (cyclomatic 21) lib/seed-library/ui/pages/add_edit_species_page/add_edit_species_page.dart:23— AddEditSpeciesPage.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.
RaffleMainPage.build (cyclomatic 19) lib/raffle/ui/pages/main_page/main_page.dart:26— RaffleMainPage.build has cyclomatic complexity 19 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
PlantDepositPage.build (cyclomatic 19) lib/seed-library/ui/pages/plant_deposit_page/plant_deposit_page.dart:31— PlantDepositPage.build has cyclomatic complexity 19 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
AddEditContenderPage.build (cyclomatic 19) lib/vote/ui/pages/contender_pages/add_edit_contender.dart:38— AddEditContenderPage.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.
CreationPage.build (cyclomatic 18) lib/raffle/ui/pages/creation_edit_page/creation_edit_page.dart:37— CreationPage.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.
TextEntry.build (cyclomatic 18) lib/tools/ui/widgets/text_entry.dart:42— TextEntry.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.
TransactionCard.build (cyclomatic 17) lib/mypayment/ui/components/transaction_card.dart:22— TransactionCard.build has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
WebMemberCard.build (cyclomatic 16) lib/phonebook/ui/pages/association_page/web_member_card.dart:28— WebMemberCard.build 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.
VoteButton.build (cyclomatic 16) lib/vote/ui/pages/main_page/vote_button.dart:18— VoteButton.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.
TodoComment lib/admin/ui/pages/structure_page/add_edit_structure_page/results.dart:43— // TODO: 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.
AddEditBookingPage.build (cognitive 75) lib/booking/ui/pages/booking_pages/add_edit_booking_page.dart:39— AddEditBookingPage.build has cognitive complexity 75 (threshold 15). Drivers by points: if/else 18 (34 pts), ternaries 20 (32 pts), boolean chains 5, error handling 1 (4 pts) (nesting depth added 31). 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.
AddEditEventPage.build (cognitive 67) lib/event/ui/pages/event_pages/add_edit_event_page.dart:32— AddEditEventPage.build has cognitive complexity 67 (threshold 15). Drivers by points: ternaries 25 (33 pts), if/else 16 (32 pts), boolean chains 2 (nesting depth added 24). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SellerRightCard.build (cognitive 55) lib/mypayment/ui/pages/store_admin_page/seller_right_card.dart:24— SellerRightCard.build has cognitive complexity 55 (threshold 15). Drivers by points: if/else 12 (26 pts), ternaries 5 (17 pts), boolean chains 10, loops 2 (nesting depth added 26). 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.
BookingCard.build (cognitive 49) lib/booking/ui/components/booking_card.dart:32— BookingCard.build has cognitive complexity 49 (threshold 15). Drivers by points: ternaries 13 (25 pts), if/else 12 (20 pts), boolean chains 3, match/switch 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.
AddEditSessionPage.build (cognitive 48) lib/cinema/ui/pages/session_pages/add_edit_session.dart:29— AddEditSessionPage.build has cognitive complexity 48 (threshold 15). Drivers by points: if/else 15 (28 pts), ternaries 11 (16 pts), match/switch 1 (2 pts), boolean chains 1, error handling 1 (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.
EventUi.build (cognitive 45) lib/event/ui/components/event_ui.dart:35— EventUi.build has cognitive complexity 45 (threshold 15). Drivers by points: ternaries 20 (32 pts), if/else 9 (12 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.
LoanCard.build (cognitive 43) lib/loan/ui/pages/admin_page/loan_card.dart:29— LoanCard.build has cognitive complexity 43 (threshold 15). Drivers by points: ternaries 24 (34 pts), boolean chains 5, if/else 4 (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.
DeliveryUi.build (cognitive 41) lib/amap/ui/pages/admin_page/delivery_ui.dart:28— DeliveryUi.build has cognitive complexity 41 (threshold 15). Drivers by points: if/else 13 (20 pts), ternaries 18, loops 1 (2 pts), match/switch 1 (nesting depth added 8). 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.
DevicesPage.build (cognitive 40) lib/mypayment/ui/pages/devices_page/devices_page.dart:30— DevicesPage.build has cognitive complexity 40 (threshold 15). Drivers by points: if/else 21 (34 pts), boolean chains 4, ternaries 1 (2 pts) (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AddEditStructurePage.build (cognitive 38) lib/admin/ui/pages/structure_page/add_edit_structure_page/add_edit_structure_page.dart:27— AddEditStructurePage.build has cognitive complexity 38 (threshold 15). Drivers by points: ternaries 17 (22 pts), if/else 9 (10 pts), boolean chains 6 (nesting depth added 6). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
AddEditContenderPage.build (cognitive 36) lib/vote/ui/pages/contender_pages/add_edit_contender.dart:38— AddEditContenderPage.build has cognitive complexity 36 (threshold 15). Drivers by points: if/else 18 (29 pts), ternaries 4 (6 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.
AdvertAddEditAdvertPage.build (cognitive 34) lib/advert/ui/pages/form_page/add_edit_advert_page.dart:30— AdvertAddEditAdvertPage.build has cognitive complexity 34 (threshold 15). Drivers by points: if/else 12 (19 pts), ternaries 8 (11 pts), boolean chains 4 (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.
AddEditButton.build (cognitive 34) lib/loan/ui/pages/loan_group_page/add_edit_button.dart:33— AddEditButton.build has cognitive complexity 34 (threshold 15). Drivers by points: if/else 11 (20 pts), ternaries 5 (14 pts) (nesting depth added 18). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
AdminPage.build (cognitive 34) lib/vote/ui/pages/admin_page/admin_page.dart:33— AdminPage.build has cognitive complexity 34 (threshold 15). Drivers by points: if/else 21 (27 pts), boolean chains 3, ternaries 2 (3 pts), loops 1 (nesting depth added 7). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
AddEditPackTicketPage.build (cognitive 33) lib/raffle/ui/pages/pack_ticket_page/add_edit_pack_ticket_page.dart:19— AddEditPackTicketPage.build has cognitive complexity 33 (threshold 15). Drivers by points: if/else 11 (20 pts), ternaries 6 (12 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.
MembershipEditorPage.build (cognitive 31) lib/phonebook/ui/pages/membership_editor_page/membership_editor_page.dart:31— MembershipEditorPage.build has cognitive complexity 31 (threshold 15). Drivers by points: if/else 15 (19 pts), boolean chains 6, ternaries 5 (6 pts) (nesting depth added 5). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
AssociationEditorPage.build (cognitive 28) lib/phonebook/ui/pages/association_editor_page/association_editor_page.dart:35— AssociationEditorPage.build has cognitive complexity 28 (threshold 15). Drivers by points: boolean chains 14, if/else 7 (8 pts), ternaries 6 (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.
AddEditRecommendationPage.build (cognitive 28) lib/recommendation/ui/pages/add_edit_page.dart:26— AddEditRecommendationPage.build has cognitive complexity 28 (threshold 15). Drivers by points: if/else 10 (17 pts), ternaries 6 (10 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.
Repository.getList (cognitive 28) lib/tools/repository/repository.dart:28— Repository.getList has cognitive complexity 28 (threshold 15). Drivers by points: if/else 7 (15 pts), error handling 6 (13 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. This shape REPEATS in the file: one other method here (Repository.getOne) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
Repository.getOne (cognitive 28) lib/tools/repository/repository.dart:91— Repository.getOne has cognitive complexity 28 (threshold 15). Drivers by points: if/else 7 (15 pts), error handling 6 (13 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. This shape REPEATS in the file: one other method here (Repository.getList) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
InvoiceCard.build (cognitive 27) lib/mypayment/ui/pages/invoices_admin_page/invoice_card.dart:23— InvoiceCard.build has cognitive complexity 27 (threshold 15). Drivers by points: if/else 11 (14 pts), ternaries 7 (8 pts), boolean chains 4, error handling 1 (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
WebMemberCard.build (cognitive 25) lib/phonebook/ui/pages/association_page/web_member_card.dart:28— WebMemberCard.build has cognitive complexity 25 (threshold 15). Drivers by points: if/else 10 (14 pts), ternaries 6 (9 pts), boolean chains 2 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AddEditSpeciesPage.build (cognitive 25) lib/seed-library/ui/pages/add_edit_species_page/add_edit_species_page.dart:23— AddEditSpeciesPage.build has cognitive complexity 25 (threshold 15). Drivers by points: ternaries 14 (16 pts), if/else 8 (9 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.
PlantDepositPage.build (cognitive 24) lib/seed-library/ui/pages/plant_deposit_page/plant_deposit_page.dart:31— PlantDepositPage.build has cognitive complexity 24 (threshold 15). Drivers by points: ternaries 9 (12 pts), if/else 8 (9 pts), boolean chains 3 (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, 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.
AddEditProduct.build (cognitive 23) lib/amap/ui/pages/product_pages/add_edit_product.dart:24— AddEditProduct.build has cognitive complexity 23 (threshold 15). Drivers by points: if/else 8 (13 pts), ternaries 7 (10 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.
AdminPage.build (cognitive 23) lib/phonebook/ui/pages/admin_page/admin_page.dart:29— AdminPage.build has cognitive complexity 23 (threshold 15). Drivers by points: if/else 8 (13 pts), boolean chains 6, ternaries 3 (4 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AddEditItemPage.build (cognitive 22) lib/loan/ui/pages/item_group_page/add_edit_item_page.dart:22— AddEditItemPage.build has cognitive complexity 22 (threshold 15). Drivers by points: if/else 9 (14 pts), ternaries 6 (8 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.
CreationPage.build (cognitive 22) lib/raffle/ui/pages/creation_edit_page/creation_edit_page.dart:37— CreationPage.build has cognitive complexity 22 (threshold 15). Drivers by points: if/else 7 (11 pts), ternaries 7, loops 1 (2 pts), boolean chains 1, match/switch 1 (nesting depth added 5). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
RaffleMainPage.build (cognitive 22) lib/raffle/ui/pages/main_page/main_page.dart:26— RaffleMainPage.build has cognitive complexity 22 (threshold 15). Drivers by points: if/else 9 (12 pts), boolean chains 4, loops 3, match/switch 1 (2 pts), ternaries 1 (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
EditUserPage.build (cognitive 22) lib/settings/ui/pages/edit_user_page/edit_user_page.dart:28— EditUserPage.build has cognitive complexity 22 (threshold 15). Drivers by points: if/else 14 (17 pts), ternaries 5 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
AddEditUserMembershipPage.build (cognitive 21) lib/admin/ui/pages/memberships/add_edit_user_membership_page/add_edit_user_membership_page.dart:24— AddEditUserMembershipPage.build has cognitive complexity 21 (threshold 15). Drivers by points: if/else 13 (16 pts), ternaries 4, 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.
AddEditDeliveryPage.build (cognitive 20) lib/amap/ui/pages/delivery_pages/add_edit_delivery_cmd_page.dart:28— AddEditDeliveryPage.build has cognitive complexity 20 (threshold 15). Drivers by points: if/else 9 (14 pts), ternaries 4 (6 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.
ScanDialog.build (cognitive 20) lib/purchases/ui/pages/scan_page/scan_dialog.dart:31— ScanDialog.build has cognitive complexity 20 (threshold 15). Drivers by points: ternaries 5 (9 pts), if/else 5 (8 pts), error handling 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.
TextEntry.build (cognitive 20) lib/tools/ui/widgets/text_entry.dart:42— TextEntry.build has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (10 pts), boolean chains 6, ternaries 4 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
PhAddEditPhPage.build (cognitive 19) lib/ph/ui/pages/form_page/add_edit_ph_page.dart:27— PhAddEditPhPage.build has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (9 pts), ternaries 4 (8 pts), boolean chains 2 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AddEditPrizePage.build (cognitive 19) lib/raffle/ui/pages/prize_page/add_edit_prize_page.dart:22— AddEditPrizePage.build has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (13 pts), ternaries 4 (6 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.
ProductChoiceButton.build (cognitive 18) lib/amap/ui/pages/list_products_page/product_choice_button.dart:21— ProductChoiceButton.build has cognitive complexity 18 (threshold 15). Drivers by points: if/else 10 (15 pts), ternaries 1 (2 pts), boolean chains 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ListBooking.build (cognitive 18) lib/booking/ui/pages/manager_page/list_booking.dart:33— ListBooking.build has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (13 pts), ternaries 2 (5 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DrawerTopBar.build (cognitive 18) lib/drawer/ui/drawer_top_bar.dart:26— DrawerTopBar.build has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (10 pts), ternaries 6 (8 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.
ReFundPage.build (cognitive 18) lib/mypayment/ui/pages/store_stats_page/refund_page.dart:21— ReFundPage.build has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (11 pts), boolean chains 4, ternaries 2 (3 pts) (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DetailBookingPage.build (cognitive 17) lib/booking/ui/pages/detail_pages/detail_booking.dart:18— DetailBookingPage.build has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (9 pts), error handling 3 (8 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.
FundPage.build (cognitive 17) lib/mypayment/ui/pages/fund_page/fund_page.dart:16— FundPage.build has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (11 pts), boolean chains 3, ternaries 2 (3 pts) (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PayPage.build (cognitive 17) lib/mypayment/ui/pages/pay_page/pay_page.dart:15— PayPage.build has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (11 pts), boolean chains 3, ternaries 2 (3 pts) (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ScannerState._handleBarcode (cognitive 17) lib/mypayment/ui/pages/scan_page/scanner.dart:67— ScannerState._handleBarcode has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (14 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.
AssociationInformationEditor.build (cognitive 17) lib/phonebook/ui/pages/association_editor_page/association_information_editor.dart:23— AssociationInformationEditor.build has cognitive complexity 17 (threshold 15). Drivers by points: if/else 11 (13 pts), boolean chains 3, ternaries 1 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
EditablePlantDetail.build (cognitive 17) lib/seed-library/ui/pages/edit_plant_detail_page/editable_plant_detail.dart:21— EditablePlantDetail.build has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (9 pts), ternaries 5 (6 pts), boolean chains 2 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
VoteButton.build (cognitive 17) lib/vote/ui/pages/main_page/vote_button.dart:18— VoteButton.build has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 7, boolean chains 6, if/else 3 (4 pts) (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
MyApp.build (cognitive 16) lib/main.dart:51— MyApp.build has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (13 pts), error handling 1 (2 pts), 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.
OpenIdTokenProvider.getTokenFromRequest (cognitive 16) lib/auth/providers/openid_provider.dart:142— OpenIdTokenProvider.getTokenFromRequest has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (8 pts), error handling 3 (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.
AddEditManagerPage.build (cognitive 16) lib/booking/ui/pages/admin_pages/add_edit_manager_page.dart:25— AddEditManagerPage.build has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 8 (10 pts), if/else 5 (6 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.
AddEditRoomPage.build (cognitive 16) lib/booking/ui/pages/admin_pages/add_edit_room_page.dart:25— AddEditRoomPage.build has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 8 (10 pts), if/else 5 (6 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.
LoanMainPage.build (cognitive 16) lib/loan/ui/pages/main_page/main_page.dart:23— LoanMainPage.build has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (7 pts), ternaries 5 (7 pts), loops 1 (2 pts) (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Near-duplicate member pair (145 shared lines) lib/raffle/ui/pages/raffle_page/buy_pack_ticket_card.dart:22— lib/raffle/ui/pages/raffle_page/buy_pack_ticket_card.dart:22-189 | lib/raffle/ui/pages/raffle_page/buy_type_ticket_card.dart:22-189 — These two members are variants of one another: 145 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 (115 shared lines) lib/raffle/ui/pages/admin_module_page/confirm_creation.dart:19— lib/raffle/ui/pages/admin_module_page/confirm_creation.dart:19-171 | lib/raffle/ui/pages/raffle_page/confirm_payment.dart:28-324 — These two members are variants of one another: 115 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 (78 shared lines) lib/booking/ui/pages/detail_pages/detail_booking.dart:18— lib/booking/ui/pages/detail_pages/detail_booking.dart:18-211 | lib/event/ui/pages/detail_page/detail_page.dart:15-222 — These two members are variants of one another: 78 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 (72 shared lines) lib/booking/ui/pages/admin_pages/add_edit_manager_page.dart:25— lib/booking/ui/pages/admin_pages/add_edit_manager_page.dart:25-185 | lib/booking/ui/pages/admin_pages/add_edit_room_page.dart:25-184 — These two members are variants of one another: 72 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 (65 shared lines) lib/admin/ui/pages/memberships/association_membership_page/association_membership_page.dart:25— lib/admin/ui/pages/memberships/association_membership_page/association_membership_page.dart:25-201 | lib/admin/ui/pages/schools/school_page/school_page.dart:22-144 — These two members are variants of one another: 65 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 (58 shared lines) lib/admin/ui/pages/groups/edit_group_page/edit_group_page.dart:25— lib/admin/ui/pages/groups/edit_group_page/edit_group_page.dart:25-152 | lib/admin/ui/pages/schools/edit_school_page/edit_school_page.dart:21-121 — These two members are variants of one another: 58 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.
D4 · Code Duplication· Members sharing a duplicated core (8 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (8 members, 50+ identical tokens) lib/amap/providers/user_order_list_provider.dart:100— lib/amap/providers/user_order_list_provider.dart:100-136 | lib/tools/providers/list_notifier.dart:22-55 | lib/tools/providers/list_notifier.dart:57-93 | lib/tools/providers/list_notifier.dart:95-135 | lib/tools/providers/list_notifier.dart:137-178 | lib/tools/providers/single_notifier.dart:22-54 | lib/tools/providers/single_notifier.dart:56-91 | lib/tools/providers/single_notifier.dart:93-132 — These 8 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 8 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 8 times.
D4 · Code Duplication· Members sharing a duplicated core (5 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (5 members, 50+ identical tokens) lib/tools/repository/csv_repository.dart:12— lib/tools/repository/csv_repository.dart:12-66 | lib/tools/repository/logo_repository.dart:15-53 | lib/tools/repository/logo_repository.dart:100-129 | lib/tools/repository/pdf_repository.dart:16-70 | lib/tools/repository/pdf_repository.dart:128-168 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
D4 · Code Duplication· Edited copy of a member (134 corresponding lines) · ×1
Edited copy of a member (134 corresponding lines) lib/admin/ui/pages/groups/edit_group_page/search_user.dart:23— lib/admin/ui/pages/groups/edit_group_page/search_user.dart:23-156 | lib/mypayment/ui/pages/structure_administrators_page/structure_administrator_page.dart:21-157 — These two members are one piece of code written twice and then edited apart: 134 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (115 corresponding lines) · ×1
Edited copy of a member (115 corresponding lines) lib/mypayment/ui/pages/fund_page/fund_page.dart:16— lib/mypayment/ui/pages/fund_page/fund_page.dart:16-137 | lib/mypayment/ui/pages/pay_page/pay_page.dart:15-129 — These two members are one piece of code written twice and then edited apart: 115 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (133 corresponding lines) · ×1
Edited copy of a member (133 corresponding lines) lib/raffle/ui/pages/pack_ticket_page/add_edit_pack_ticket_page.dart:19— lib/raffle/ui/pages/pack_ticket_page/add_edit_pack_ticket_page.dart:19-189 | lib/raffle/ui/pages/prize_page/add_edit_prize_page.dart:22-154 — These two members are one piece of code written twice and then edited apart: 133 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (70 corresponding lines) · ×1
Edited copy of a member (70 corresponding lines) lib/settings/ui/pages/log_page/log_tab.dart:13— lib/settings/ui/pages/log_page/log_tab.dart:13-82 | lib/settings/ui/pages/log_page/notification_tab.dart:13-82 — These two members are one piece of code written twice and then edited apart: 70 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (61 corresponding lines) · ×1
Edited copy of a member (61 corresponding lines) lib/admin/ui/pages/memberships/add_edit_user_membership_page/search_result.dart:10— lib/admin/ui/pages/memberships/add_edit_user_membership_page/search_result.dart:10-74 | lib/phonebook/ui/pages/membership_editor_page/search_result.dart:11-71 — These two members are one piece of code written twice and then edited apart: 61 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (69 corresponding lines) · ×1
Edited copy of a member (69 corresponding lines) lib/admin/ui/pages/groups/add_group_page/add_group_page.dart:19— lib/admin/ui/pages/groups/add_group_page/add_group_page.dart:19-87 | lib/admin/ui/pages/schools/add_school_page/add_school_page.dart:19-87 — These two members are one piece of code written twice and then edited apart: 69 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (44 corresponding lines) · ×1
Edited copy of a member (44 corresponding lines) lib/tools/repository/logo_repository.dart:55— lib/tools/repository/logo_repository.dart:55-98 | lib/tools/repository/pdf_repository.dart:72-126 — These two members are one piece of code written twice and then edited apart: 44 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (54 corresponding lines) · ×1
Edited copy of a member (54 corresponding lines) lib/amap/ui/pages/admin_page/adding_user_card.dart:15— lib/amap/ui/pages/admin_page/adding_user_card.dart:15-71 | lib/raffle/ui/pages/admin_module_page/adding_user_card.dart:14-67 — These two members are one piece of code written twice and then edited apart: 54 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (60 corresponding lines) · ×1
Edited copy of a member (60 corresponding lines) lib/admin/ui/pages/structure_page/add_edit_structure_page/search_user.dart:15— lib/admin/ui/pages/structure_page/add_edit_structure_page/search_user.dart:15-74 | lib/mypayment/ui/pages/transfer_structure_page/transfer_structure_page.dart:15-75 — These two members are one piece of code written twice and then edited apart: 60 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 47+ corresponding lines) · ×1
Edited copies of one member (3 members, 47+ corresponding lines) lib/admin/ui/pages/groups/group_page/group_ui.dart:22— lib/admin/ui/pages/groups/group_page/group_ui.dart:22-78 | lib/admin/ui/pages/memberships/association_membership_page/association_membership_ui.dart:20-66 | lib/admin/ui/pages/schools/school_page/school_ui.dart:21-69 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 47 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (45 corresponding lines) · ×1
Edited copy of a member (45 corresponding lines) lib/loan/ui/pages/loan_group_page/search_result.dart:11— lib/loan/ui/pages/loan_group_page/search_result.dart:11-55 | lib/vote/ui/pages/contender_pages/search_result.dart:17-62 — These two members are one piece of code written twice and then edited apart: 45 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (46 corresponding lines) · ×1
Edited copy of a member (46 corresponding lines) lib/mypayment/ui/pages/stats_page/month_section_summary.dart:17— lib/mypayment/ui/pages/stats_page/month_section_summary.dart:17-62 | lib/mypayment/ui/pages/stats_page/sum_up_card.dart:18-68 — These two members are one piece of code written twice and then edited apart: 46 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (5 members, 43+ corresponding lines) · ×1
Edited copies of one member (5 members, 43+ corresponding lines) lib/amap/router.dart:45— lib/amap/router.dart:45-101 | lib/event/router.dart:33-77 | lib/loan/router.dart:36-82 | lib/raffle/router.dart:38-92 | lib/vote/router.dart:36-78 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 43 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (38 corresponding lines) · ×1
Edited copy of a member (38 corresponding lines) lib/tools/ui/layouts/card_button.dart:22— lib/tools/ui/layouts/card_button.dart:22-59 | lib/tools/ui/layouts/card_layout.dart:28-72 — These two members are one piece of code written twice and then edited apart: 38 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (42 corresponding lines) · ×1
Edited copy of a member (42 corresponding lines) lib/purchases/ui/pages/main_page/custom_button.dart:22— lib/purchases/ui/pages/main_page/custom_button.dart:22-63 | lib/tools/ui/widgets/admin_button.dart:20-66 — These two members are one piece of code written twice and then edited apart: 42 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (36 corresponding lines) · ×1
Edited copy of a member (36 corresponding lines) lib/mypayment/ui/pages/main_page/account_card/day_divider.dart:11— lib/mypayment/ui/pages/main_page/account_card/day_divider.dart:11-46 | lib/mypayment/ui/pages/main_page/seller_card/store_divider.dart:10-45 — These two members are one piece of code written twice and then edited apart: 36 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (39 corresponding lines) · ×1
Edited copy of a member (39 corresponding lines) lib/advert/router.dart:37— lib/advert/router.dart:37-77 | lib/cinema/router.dart:34-72 — These two members are one piece of code written twice and then edited apart: 39 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 32+ corresponding lines) · ×1
Edited copies of one member (3 members, 32+ corresponding lines) lib/admin/ui/pages/memberships/association_membership_detail_page/research_bar.dart:10— lib/admin/ui/pages/memberships/association_membership_detail_page/research_bar.dart:10-43 | lib/phonebook/ui/pages/admin_page/association_research_bar.dart:10-43 | lib/purchases/ui/pages/history_page/research_bar.dart:11-42 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 32 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 29+ corresponding lines) · ×1
Edited copies of one member (3 members, 29+ corresponding lines) lib/mypayment/class/structure.dart:93— lib/mypayment/class/structure.dart:93-124 | lib/seed-library/class/plant_complete.dart:84-117 | lib/user/class/user.dart:95-123 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 29 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 24+ corresponding lines) · ×1
Edited copies of one member (4 members, 24+ corresponding lines) lib/admin/providers/permissions_list_provider.dart:20— lib/admin/providers/permissions_list_provider.dart:20-48 | lib/admin/providers/permissions_list_provider.dart:50-73 | lib/admin/providers/permissions_list_provider.dart:75-105 | lib/admin/providers/permissions_list_provider.dart:107-133 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 24 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (22 corresponding lines) · ×1
Edited copy of a member (22 corresponding lines) lib/centralassociation/ui/pages/asso_list.dart:9— lib/centralassociation/ui/pages/asso_list.dart:9-30 | lib/centralisation/ui/pages/section_list.dart:9-30 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (23 corresponding lines) · ×1
Edited copy of a member (23 corresponding lines) lib/phonebook/ui/pages/admin_page/edition_button.dart:14— lib/phonebook/ui/pages/admin_page/edition_button.dart:14-39 | lib/seed-library/ui/components/edition_button.dart:15-37 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (16 corresponding lines) · ×1
Edited copy of a member (16 corresponding lines) lib/booking/class/booking.dart:57— lib/booking/class/booking.dart:57-72 | lib/event/class/event.dart:64-79 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 19+ corresponding lines) · ×1
Edited copies of one member (3 members, 19+ corresponding lines) lib/phonebook/class/association.dart:43— lib/phonebook/class/association.dart:43-61 | lib/purchases/class/product_variant.dart:43-61 | lib/seed-library/class/plant_simple.dart:76-98 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 19 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 18+ corresponding lines) · ×1
Edited copies of one member (3 members, 18+ corresponding lines) lib/phonebook/class/member.dart:34— lib/phonebook/class/member.dart:34-55 | lib/user/class/applicant.dart:35-56 | lib/vote/class/members.dart:17-34 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 18 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (15 corresponding lines) · ×1
Edited copy of a member (15 corresponding lines) lib/mypayment/class/qr_code_data.dart:50— lib/mypayment/class/qr_code_data.dart:50-66 | lib/mypayment/class/qr_code_signature_data.dart:45-59 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 9+ corresponding lines) · ×1
Edited copies of one member (4 members, 9+ corresponding lines) lib/amap/class/product.dart:45— lib/amap/class/product.dart:45-53 | lib/cinema/class/session.dart:32-42 | lib/loan/class/item.dart:28-37 | lib/raffle/class/prize.dart:23-31 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 9+ corresponding lines) · ×1
Edited copies of one member (3 members, 9+ corresponding lines) lib/centralisation/class/module.dart:23— lib/centralisation/class/module.dart:23-35 | lib/raffle/class/raffle.dart:27-35 | lib/user/class/simple_users.dart:28-36 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (7 members, 7+ corresponding lines) · ×1
Edited copies of one member (7 members, 7+ corresponding lines) lib/amap/providers/delivery_product_list_provider.dart:24— lib/amap/providers/delivery_product_list_provider.dart:24-31 | lib/booking/providers/manager_booking_list_provider.dart:26-33 | lib/event/providers/event_list_provider.dart:38-45 | lib/loan/providers/history_loaner_loan_list_provider.dart:51-59 | lib/loan/providers/item_list_provider.dart:21-27 | lib/loan/providers/loaner_loan_list_provider.dart:50-58 | lib/mypayment/providers/device_list_provider.dart:15-22 — These 7 members are one piece of code written 7 times and then edited apart: every two of them correspond over at least 7 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 7 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 17+ corresponding lines) · ×1
Edited copies of one member (3 members, 17+ corresponding lines) lib/admin/providers/association_membership_members_list_provider.dart:18— lib/admin/providers/association_membership_members_list_provider.dart:18-36 | lib/mypayment/providers/invoice_list_provider.dart:12-28 | lib/mypayment/providers/invoice_list_provider.dart:30-46 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 17 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 7+ corresponding lines) · ×1
Edited copies of one member (3 members, 7+ corresponding lines) lib/amap/providers/cash_list_provider.dart:31— lib/amap/providers/cash_list_provider.dart:31-39 | lib/booking/providers/confirmed_booking_list_provider.dart:32-39 | lib/raffle/providers/prize_list_provider.dart:46-52 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 7 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (5 members, 9+ corresponding lines) · ×1
Edited copies of one member (5 members, 9+ corresponding lines) lib/amap/providers/delivery_list_provider.dart:29— lib/amap/providers/delivery_list_provider.dart:29-37 | lib/amap/providers/delivery_list_provider.dart:39-47 | lib/amap/providers/delivery_list_provider.dart:49-57 | lib/amap/providers/delivery_product_list_provider.dart:42-51 | lib/phonebook/providers/association_list_provider.dart:44-52 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (7 members, 12+ corresponding lines) · ×1
Edited copies of one member (7 members, 12+ corresponding lines) lib/booking/ui/booking.dart:10— lib/booking/ui/booking.dart:10-24 | lib/centralassociation/ui/centralassociation.dart:10-26 | lib/centralisation/ui/centralisation.dart:10-26 | lib/event/ui/event.dart:10-21 | lib/ph/ui/pages/ph.dart:10-21 | lib/recommendation/ui/widgets/recommendation_template.dart:10-24 | lib/settings/ui/settings.dart:10-24 — These 7 members are one piece of code written 7 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 7 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 3+ corresponding lines) · ×1
Edited copies of one member (4 members, 3+ corresponding lines) lib/amap/providers/user_order_list_provider.dart:163— lib/amap/providers/user_order_list_provider.dart:163-165 | lib/loan/providers/history_loaner_loan_list_provider.dart:61-63 | lib/loan/providers/item_list_provider.dart:38-40 | lib/loan/providers/loaner_loan_list_provider.dart:60-62 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 3 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
Duplicated block (92 lines × 2) lib/raffle/ui/pages/raffle_page/buy_pack_ticket_card.dart:51— lib/raffle/ui/pages/raffle_page/buy_pack_ticket_card.dart:51-142 | lib/raffle/ui/pages/raffle_page/buy_type_ticket_card.dart:51-142 — before extracting anything, compare `lib/raffle/ui/pages/raffle_page/buy_pack_ticket_card.dart` and `lib/raffle/ui/pages/raffle_page/buy_type_ticket_card.dart` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 231 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `lib/raffle/ui/pages/raffle_page/buy_pack_ticket_card.dart:51` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (63 lines × 2) lib/booking/ui/calendar/calendar.dart:199— lib/booking/ui/calendar/calendar.dart:199-261 | lib/tools/ui/widgets/calendar.dart:160-222 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `lib/booking/ui/calendar/calendar.dart:199` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `lib/booking/ui/calendar/calendar.dart:198` calls `of` and `lib/tools/ui/widgets/calendar.dart:159` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (48 lines × 2) lib/raffle/ui/pages/admin_module_page/confirm_creation.dart:117— lib/raffle/ui/pages/admin_module_page/confirm_creation.dart:117-164 | lib/raffle/ui/pages/raffle_page/confirm_payment.dart:269-316 — before extracting anything, compare `lib/raffle/ui/pages/admin_module_page/confirm_creation.dart` and `lib/raffle/ui/pages/raffle_page/confirm_payment.dart` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 115 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `lib/raffle/ui/pages/admin_module_page/confirm_creation.dart:117` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (43 lines × 2) lib/amap/ui/pages/admin_page/user_cash_ui.dart:28— lib/amap/ui/pages/admin_page/user_cash_ui.dart:28-70 | lib/raffle/ui/pages/creation_edit_page/user_cash_ui.dart:24-66 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `lib/amap/ui/pages/admin_page/user_cash_ui.dart:28` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `lib/amap/ui/pages/admin_page/user_cash_ui.dart:27` calls `watch` and `lib/raffle/ui/pages/creation_edit_page/user_cash_ui.dart:23` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (40–41 lines × 2) lib/raffle/ui/pages/creation_edit_page/creation_edit_page.dart:98— lib/raffle/ui/pages/creation_edit_page/creation_edit_page.dart:98-137 | lib/vote/ui/pages/contender_pages/add_edit_contender.dart:94-134 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `lib/raffle/ui/pages/creation_edit_page/creation_edit_page.dart:98` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (41 lines × 2) lib/settings/ui/pages/log_page/log_tab.dart:42— lib/settings/ui/pages/log_page/log_tab.dart:42-82 | lib/settings/ui/pages/log_page/notification_tab.dart:42-82 — before extracting anything, compare `lib/settings/ui/pages/log_page/log_tab.dart` and `lib/settings/ui/pages/log_page/notification_tab.dart` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 65 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `lib/settings/ui/pages/log_page/log_tab.dart:42` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (40 lines × 2) lib/admin/ui/pages/memberships/add_edit_user_membership_page/search_result.dart:19— lib/admin/ui/pages/memberships/add_edit_user_membership_page/search_result.dart:19-58 | lib/phonebook/ui/pages/membership_editor_page/search_result.dart:17-56 — before extracting anything, compare `lib/admin/ui/pages/memberships/add_edit_user_membership_page/search_result.dart` and `lib/phonebook/ui/pages/membership_editor_page/search_result.dart` as WHOLE FILES: 82% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `lib/admin/ui/pages/memberships/add_edit_user_membership_page/search_result.dart:19` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (37–38 lines × 2) lib/event/ui/pages/detail_page/detail_page.dart:110— lib/event/ui/pages/detail_page/detail_page.dart:110-146 | lib/event/ui/pages/detail_page/detail_page.dart:156-193 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `lib/event/ui/pages/detail_page/detail_page.dart:110` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (38 lines × 2) lib/raffle/ui/pages/admin_module_page/account_handler.dart:76— lib/raffle/ui/pages/admin_module_page/account_handler.dart:76-113 | lib/raffle/ui/pages/admin_module_page/tombola_handler.dart:86-123 — before extracting anything, compare `lib/raffle/ui/pages/admin_module_page/account_handler.dart` and `lib/raffle/ui/pages/admin_module_page/tombola_handler.dart` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 85 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `lib/raffle/ui/pages/admin_module_page/account_handler.dart:76` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (36–37 lines × 2) lib/raffle/ui/pages/creation_edit_page/prize_card.dart:109— lib/raffle/ui/pages/creation_edit_page/prize_card.dart:109-145 | lib/raffle/ui/pages/creation_edit_page/ticket_ui.dart:99-134 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `lib/raffle/ui/pages/creation_edit_page/prize_card.dart:109` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (34 lines × 2) lib/admin/router.dart:117— lib/admin/router.dart:117-150 | lib/admin/router.dart:162-195 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `lib/admin/router.dart:117` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (30 lines × 2) lib/booking/ui/pages/admin_pages/add_edit_manager_page.dart:75— lib/booking/ui/pages/admin_pages/add_edit_manager_page.dart:75-104 | lib/booking/ui/pages/admin_pages/add_edit_room_page.dart:75-104 — before extracting anything, compare `lib/booking/ui/pages/admin_pages/add_edit_manager_page.dart` and `lib/booking/ui/pages/admin_pages/add_edit_room_page.dart` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 72 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `lib/booking/ui/pages/admin_pages/add_edit_manager_page.dart:75` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (28 lines × 3) lib/admin/ui/pages/groups/group_page/group_page.dart:168— lib/admin/ui/pages/groups/group_page/group_page.dart:168-195 | lib/admin/ui/pages/memberships/association_membership_page/association_membership_page.dart:174-201 | lib/admin/ui/pages/schools/school_page/school_page.dart:117-144 — before extracting anything, compare `lib/admin/ui/pages/memberships/association_membership_page/association_membership_page.dart` and `lib/admin/ui/pages/schools/school_page/school_page.dart` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 65 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `lib/admin/ui/pages/groups/group_page/group_page.dart:168` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (28 lines × 2) lib/raffle/ui/pages/raffle_page/buy_pack_ticket_card.dart:144— lib/raffle/ui/pages/raffle_page/buy_pack_ticket_card.dart:144-171 | lib/raffle/ui/pages/raffle_page/buy_type_ticket_card.dart:144-171 — before extracting anything, compare `lib/raffle/ui/pages/raffle_page/buy_pack_ticket_card.dart` and `lib/raffle/ui/pages/raffle_page/buy_type_ticket_card.dart` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 231 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `lib/raffle/ui/pages/raffle_page/buy_pack_ticket_card.dart:144` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (25–27 lines × 2) lib/admin/ui/pages/groups/edit_group_page/results.dart:24— lib/admin/ui/pages/groups/edit_group_page/results.dart:24-50 | lib/mypayment/ui/pages/structure_administrators_page/results.dart:23-47 — before extracting anything, compare `lib/admin/ui/pages/groups/edit_group_page/results.dart` and `lib/mypayment/ui/pages/structure_administrators_page/results.dart` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 85 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `lib/admin/ui/pages/groups/edit_group_page/results.dart:24` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (26 lines × 3) lib/mypayment/ui/pages/fund_page/fund_page.dart:78— lib/mypayment/ui/pages/fund_page/fund_page.dart:78-103 | lib/mypayment/ui/pages/pay_page/pay_page.dart:73-98 | lib/mypayment/ui/pages/store_stats_page/refund_page.dart:80-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. Read the line range as the matched WINDOW rather than a finished unit: at `lib/mypayment/ui/pages/fund_page/fund_page.dart:78` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (25–26 lines × 2) lib/mypayment/ui/pages/store_admin_page/seller_right_dialog.dart:32— lib/mypayment/ui/pages/store_admin_page/seller_right_dialog.dart:32-56 | lib/tools/ui/widgets/custom_dialog_box.dart:33-58 — before extracting anything, compare `lib/mypayment/ui/pages/store_admin_page/seller_right_dialog.dart` and `lib/tools/ui/widgets/custom_dialog_box.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. Read the line range as the matched WINDOW rather than a finished unit: at `lib/mypayment/ui/pages/store_admin_page/seller_right_dialog.dart:32` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (23–24 lines × 3) lib/admin/ui/pages/groups/edit_group_page/search_user.dart:71— lib/admin/ui/pages/groups/edit_group_page/search_user.dart:71-93 | lib/admin/ui/pages/structure_page/add_edit_structure_page/search_user.dart:37-59 | lib/mypayment/ui/pages/structure_administrators_page/structure_administrator_page.dart:68-91 — before extracting anything, compare `lib/admin/ui/pages/groups/edit_group_page/search_user.dart` and `lib/admin/ui/pages/structure_page/add_edit_structure_page/search_user.dart` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 49 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `lib/admin/ui/pages/groups/edit_group_page/search_user.dart:71` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (23 lines × 7) lib/tools/providers/list_notifier.dart:29— lib/tools/providers/list_notifier.dart:29-51 | lib/tools/providers/list_notifier.dart:67-89 | lib/tools/providers/list_notifier.dart:109-131 | lib/tools/providers/list_notifier.dart:152-174 | lib/tools/providers/single_notifier.dart:28-50 | lib/tools/providers/single_notifier.dart:65-87 | lib/tools/providers/single_notifier.dart:106-128 — before extracting anything, compare `lib/tools/providers/list_notifier.dart` and `lib/tools/providers/single_notifier.dart` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 52 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `lib/tools/providers/list_notifier.dart:29` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `lib/tools/providers/list_notifier.dart:27` calls `add` and `lib/tools/providers/single_notifier.dart:26` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (23 lines × 4) lib/admin/ui/pages/groups/group_page/group_button.dart:14— lib/admin/ui/pages/groups/group_page/group_button.dart:14-36 | lib/admin/ui/pages/memberships/association_membership_page/association_membership_button.dart:14-36 | lib/admin/ui/pages/schools/school_page/school_button.dart:14-36 | lib/admin/ui/pages/structure_page/structure_button.dart:14-36 — before extracting anything, compare `lib/admin/ui/pages/groups/group_page/group_button.dart` and `lib/admin/ui/pages/memberships/association_membership_page/association_membership_button.dart` as WHOLE FILES: 88% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (21–23 lines × 2) lib/mypayment/ui/pages/scan_page/scan_page.dart:305— lib/mypayment/ui/pages/scan_page/scan_page.dart:305-325 | lib/mypayment/ui/pages/scan_page/scan_page.dart:399-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. Read the line range as the matched WINDOW rather than a finished unit: at `lib/mypayment/ui/pages/scan_page/scan_page.dart:305` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (21 lines × 4) lib/admin/ui/pages/groups/edit_group_page/results.dart:30— lib/admin/ui/pages/groups/edit_group_page/results.dart:30-50 | lib/admin/ui/pages/structure_page/add_edit_structure_page/results.dart:20-40 | lib/mypayment/ui/pages/structure_administrators_page/results.dart:27-47 | lib/mypayment/ui/pages/transfer_structure_page/search_result.dart:62-82 — before extracting anything, compare `lib/admin/ui/pages/groups/edit_group_page/results.dart` and `lib/mypayment/ui/pages/structure_administrators_page/results.dart` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 85 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `lib/admin/ui/pages/groups/edit_group_page/results.dart:30` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind `context` to `BuildContext` in one and `context` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `lib/admin/ui/pages/groups/edit_group_page/results.dart:26` calls `displayToastWithContext`, `displayToast` and `lib/admin/ui/pages/structure_page/add_edit_structure_page/results.dart:18` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (18–21 lines × 2) lib/booking/ui/pages/booking_pages/add_edit_booking_page.dart:347— lib/booking/ui/pages/booking_pages/add_edit_booking_page.dart:347-364 | lib/event/ui/pages/event_pages/add_edit_event_page.dart:420-440 — before extracting anything, compare `lib/booking/ui/pages/booking_pages/add_edit_booking_page.dart` and `lib/event/ui/pages/event_pages/add_edit_event_page.dart` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 55 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `lib/booking/ui/pages/booking_pages/add_edit_booking_page.dart:347` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `lib/event/ui/pages/event_pages/add_edit_event_page.dart:419` calls `tokenExpireWrapper` and `lib/booking/ui/pages/booking_pages/add_edit_booking_page.dart:346` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (20–21 lines × 2) lib/event/ui/pages/main_page/main_page.dart:70— lib/event/ui/pages/main_page/main_page.dart:70-89 | lib/seed-library/ui/pages/species_page/species_page.dart:68-88 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `lib/event/ui/pages/main_page/main_page.dart:70` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (19–20 lines × 3) lib/raffle/ui/pages/main_page/ticket_card.dart:87— lib/raffle/ui/pages/main_page/ticket_card.dart:87-106 | lib/raffle/ui/pages/raffle_page/buy_pack_ticket_card.dart:111-129 | lib/raffle/ui/pages/raffle_page/buy_type_ticket_card.dart:111-129 — before extracting anything, compare `lib/raffle/ui/pages/raffle_page/buy_pack_ticket_card.dart` and `lib/raffle/ui/pages/raffle_page/buy_type_ticket_card.dart` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 231 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `lib/raffle/ui/pages/main_page/ticket_card.dart:87` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (16–18 lines × 2) lib/booking/ui/calendar/calendar.dart:98— lib/booking/ui/calendar/calendar.dart:98-113 | lib/booking/ui/pages/manager_page/list_booking.dart:151-168 — before extracting anything, compare `lib/booking/ui/calendar/calendar.dart` and `lib/booking/ui/pages/manager_page/list_booking.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. Read the line range as the matched WINDOW rather than a finished unit: at `lib/booking/ui/calendar/calendar.dart:98` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (17 lines × 3) lib/admin/ui/pages/groups/edit_group_page/results.dart:78— lib/admin/ui/pages/groups/edit_group_page/results.dart:78-94 | lib/admin/ui/pages/structure_page/add_edit_structure_page/results.dart:45-61 | lib/mypayment/ui/pages/structure_administrators_page/results.dart:77-93 — before extracting anything, compare `lib/admin/ui/pages/groups/edit_group_page/results.dart` and `lib/mypayment/ui/pages/structure_administrators_page/results.dart` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 85 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `lib/admin/ui/pages/groups/edit_group_page/results.dart:78` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14–17 lines × 2) lib/booking/ui/calendar/calendar.dart:67— lib/booking/ui/calendar/calendar.dart:67-80 | lib/booking/ui/pages/manager_page/list_booking.dart:115-131 — before extracting anything, compare `lib/booking/ui/calendar/calendar.dart` and `lib/booking/ui/pages/manager_page/list_booking.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. Read the line range as the matched WINDOW rather than a finished unit: at `lib/booking/ui/calendar/calendar.dart:67` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (15–17 lines × 2) lib/loan/ui/pages/main_page/main_page.dart:73— lib/loan/ui/pages/main_page/main_page.dart:73-89 | lib/loan/ui/pages/main_page/main_page.dart:122-136 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `lib/loan/ui/pages/main_page/main_page.dart:73` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (16 lines × 8) lib/amap/providers/user_order_list_provider.dart:121— lib/amap/providers/user_order_list_provider.dart:121-136 | lib/tools/providers/list_notifier.dart:40-55 | lib/tools/providers/list_notifier.dart:78-93 | lib/tools/providers/list_notifier.dart:120-135 | lib/tools/providers/list_notifier.dart:163-178 | lib/tools/providers/single_notifier.dart:39-54 | lib/tools/providers/single_notifier.dart:76-91 | lib/tools/providers/single_notifier.dart:117-132 — before extracting anything, compare `lib/tools/providers/list_notifier.dart` and `lib/tools/providers/single_notifier.dart` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 52 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `lib/amap/providers/user_order_list_provider.dart:121` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `lib/amap/providers/user_order_list_provider.dart:120` calls `error` and `lib/tools/providers/list_notifier.dart:39` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (15–16 lines × 5) lib/raffle/ui/pages/admin_module_page/account_handler.dart:96— lib/raffle/ui/pages/admin_module_page/account_handler.dart:96-111 | lib/raffle/ui/pages/admin_module_page/tombola_handler.dart:106-121 | lib/raffle/ui/pages/creation_edit_page/prize_handler.dart:123-137 | lib/raffle/ui/pages/creation_edit_page/user_cash_ui.dart:77-92 | lib/raffle/ui/pages/creation_edit_page/user_cash_ui.dart:168-183 — before extracting anything, compare `lib/raffle/ui/pages/admin_module_page/account_handler.dart` and `lib/raffle/ui/pages/admin_module_page/tombola_handler.dart` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 85 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `lib/raffle/ui/pages/admin_module_page/account_handler.dart:96` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (16 lines × 4) lib/mypayment/ui/pages/store_stats_page/tool_bar.dart:73— lib/mypayment/ui/pages/store_stats_page/tool_bar.dart:73-88 | lib/mypayment/ui/pages/store_stats_page/tool_bar.dart:110-125 | lib/mypayment/ui/pages/store_stats_page/tool_bar.dart:164-179 | lib/mypayment/ui/pages/store_stats_page/tool_bar.dart:201-216 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `lib/mypayment/ui/pages/store_stats_page/tool_bar.dart:73` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `lib/mypayment/ui/pages/store_stats_page/tool_bar.dart:162` calls `Row` and `lib/mypayment/ui/pages/store_stats_page/tool_bar.dart:109` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (15–16 lines × 3) lib/admin/ui/pages/groups/add_group_page/add_group_page.dart:25— lib/admin/ui/pages/groups/add_group_page/add_group_page.dart:25-39 | lib/admin/ui/pages/schools/add_school_page/add_school_page.dart:25-39 | lib/admin/ui/pages/structure_page/add_edit_structure_page/add_edit_structure_page.dart:63-78 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `lib/admin/ui/pages/groups/add_group_page/add_group_page.dart:25` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (14–15 lines × 3) lib/raffle/ui/pages/raffle_page/buy_pack_ticket_card.dart:69— lib/raffle/ui/pages/raffle_page/buy_pack_ticket_card.dart:69-82 | lib/raffle/ui/pages/raffle_page/buy_type_ticket_card.dart:69-82 | lib/raffle/ui/pages/raffle_page/confirm_payment.dart:95-109 — before extracting anything, compare `lib/raffle/ui/pages/raffle_page/buy_pack_ticket_card.dart` and `lib/raffle/ui/pages/raffle_page/buy_type_ticket_card.dart` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 231 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `lib/raffle/ui/pages/raffle_page/buy_pack_ticket_card.dart:69` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (10–14 lines × 4) lib/tools/ui/builders/async_child.dart:100— lib/tools/ui/builders/async_child.dart:100-109 | lib/tools/ui/builders/async_child.dart:134-146 | lib/tools/ui/builders/async_child.dart:184-197 | lib/tools/ui/builders/async_child.dart:244-257 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `lib/tools/ui/builders/async_child.dart:134` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (13–14 lines × 2) lib/raffle/ui/pages/admin_module_page/tombola_card.dart:24— lib/raffle/ui/pages/admin_module_page/tombola_card.dart:24-37 | lib/raffle/ui/pages/creation_edit_page/prize_card.dart:34-46 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `lib/raffle/ui/pages/admin_module_page/tombola_card.dart:24` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 4) lib/amap/ui/pages/detail_page/detail_page.dart:17— lib/amap/ui/pages/detail_page/detail_page.dart:17-29 | lib/event/ui/pages/detail_page/detail_page.dart:24-36 | lib/loan/ui/pages/detail_pages/detail_loan.dart:17-29 | lib/vote/ui/pages/detail_page/detail_page.dart:23-35 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times. Read the line range as the matched WINDOW rather than a finished unit: at `lib/amap/ui/pages/detail_page/detail_page.dart:17` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12–13 lines × 2) lib/cinema/ui/pages/detail_page/detail_page.dart:182— lib/cinema/ui/pages/detail_page/detail_page.dart:182-193 | lib/cinema/ui/pages/detail_page/detail_page.dart:205-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. Read the line range as the matched WINDOW rather than a finished unit: at `lib/cinema/ui/pages/detail_page/detail_page.dart:205` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 6) lib/admin/ui/pages/groups/edit_group_page/search_user.dart:77— lib/admin/ui/pages/groups/edit_group_page/search_user.dart:77-88 | lib/admin/ui/pages/structure_page/add_edit_structure_page/search_user.dart:43-54 | lib/mypayment/ui/pages/structure_administrators_page/structure_administrator_page.dart:74-85 | lib/others/ui/no_internet_page.dart:50-61 | lib/settings/ui/pages/edit_user_page/edit_user_page.dart:268-279 | lib/settings/ui/pages/edit_user_page/picture_button.dart:16-27 — before extracting anything, compare `lib/admin/ui/pages/groups/edit_group_page/search_user.dart` and `lib/admin/ui/pages/structure_page/add_edit_structure_page/search_user.dart` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 49 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `lib/admin/ui/pages/groups/edit_group_page/search_user.dart:77` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11–12 lines × 2) lib/raffle/ui/pages/creation_edit_page/prize_card.dart:29— lib/raffle/ui/pages/creation_edit_page/prize_card.dart:29-39 | lib/raffle/ui/pages/creation_edit_page/prize_handler.dart:118-129 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `lib/raffle/ui/pages/creation_edit_page/prize_card.dart:29` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (10–11 lines × 3) lib/admin/ui/pages/memberships/association_membership_detail_page/association_membership_information_editor.dart:115— lib/admin/ui/pages/memberships/association_membership_detail_page/association_membership_information_editor.dart:115-124 | lib/phonebook/ui/pages/association_creation_page/association_creation_page.dart:86-95 | lib/phonebook/ui/pages/association_editor_page/association_information_editor.dart:154-164 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `lib/admin/ui/pages/memberships/association_membership_detail_page/association_membership_information_editor.dart:115` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `lib/admin/ui/pages/memberships/association_membership_detail_page/association_membership_information_editor.dart:114` calls `SizedBox`, `WaitingButton` and `lib/phonebook/ui/pages/association_editor_page/association_information_editor.dart:154` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (9–10 lines × 2) lib/booking/ui/pages/booking_pages/add_edit_booking_page.dart:312— lib/booking/ui/pages/booking_pages/add_edit_booking_page.dart:312-320 | lib/event/ui/pages/event_pages/add_edit_event_page.dart:385-394 — before extracting anything, compare `lib/booking/ui/pages/booking_pages/add_edit_booking_page.dart` and `lib/event/ui/pages/event_pages/add_edit_event_page.dart` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 55 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `lib/booking/ui/pages/booking_pages/add_edit_booking_page.dart:312` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (9 lines × 5) lib/tools/repository/csv_repository.dart:37— lib/tools/repository/csv_repository.dart:37-45 | lib/tools/repository/logo_repository.dart:33-41 | lib/tools/repository/logo_repository.dart:115-123 | lib/tools/repository/pdf_repository.dart:41-49 | lib/tools/repository/pdf_repository.dart:151-159 — before extracting anything, compare `lib/tools/repository/csv_repository.dart` and `lib/tools/repository/pdf_repository.dart` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 85 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `lib/tools/repository/csv_repository.dart:37` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 4) lib/raffle/ui/pages/main_page/ticket_card.dart:50— lib/raffle/ui/pages/main_page/ticket_card.dart:50-59 | lib/raffle/ui/pages/raffle_page/buy_pack_ticket_card.dart:74-82 | lib/raffle/ui/pages/raffle_page/buy_type_ticket_card.dart:74-82 | lib/raffle/ui/pages/raffle_page/confirm_payment.dart:100-109 — before extracting anything, compare `lib/raffle/ui/pages/raffle_page/buy_pack_ticket_card.dart` and `lib/raffle/ui/pages/raffle_page/buy_type_ticket_card.dart` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 231 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `lib/raffle/ui/pages/main_page/ticket_card.dart:50` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `lib/raffle/ui/pages/main_page/ticket_card.dart:49` calls `only` and `lib/raffle/ui/pages/raffle_page/buy_pack_ticket_card.dart:73` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (7–8 lines × 2) lib/amap/providers/cash_list_provider.dart:45— lib/amap/providers/cash_list_provider.dart:45-51 | lib/raffle/providers/cash_provider.dart:39-46 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `lib/amap/providers/cash_list_provider.dart:45` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 13) lib/admin/repositories/account_type_repository.dart:11— lib/admin/repositories/account_type_repository.dart:11-15 | lib/admin/repositories/association_membership_repository.dart:13-17 | lib/admin/repositories/group_repository.dart:13-17 | lib/admin/repositories/permission_repository.dart:9-13 | lib/amap/repositories/delivery_list_repository.dart:12-16 | lib/amap/repositories/product_repository.dart:11-15 | lib/booking/repositories/manager_repository.dart:9-13 | lib/mypayment/repositories/structures_repository.dart:17-21 | lib/phonebook/repositories/association_groupement_repository.dart:9-13 | lib/phonebook/repositories/association_repository.dart:9-13 | lib/recommendation/repositories/recommendation_repository.dart:11-15 | lib/seed-library/repositories/species_repository.dart:12-16 | lib/user/repositories/user_list_repository.dart:11-15 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 13 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 13 times.
Duplicated block (7 lines × 5) lib/admin/repositories/association_membership_user_repository.dart:12— lib/admin/repositories/association_membership_user_repository.dart:12-19 | lib/advert/repositories/announcer_repository.dart:15-21 | lib/booking/repositories/booking_repository.dart:18-24 | lib/booking/repositories/booking_repository.dart:52-58 | lib/loan/repositories/loaner_repository.dart:17-23 — there are 5 copies across 4 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 5 sites; resolving a subset leaves the remainder to drift apart.
Duplicated block (7 lines × 4) lib/advert/class/announcer.dart:25— lib/advert/class/announcer.dart:25-31 | lib/booking/class/manager.dart:21-27 | lib/loan/class/loaner.dart:21-27 | lib/service/class/room.dart:21-27 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (5 lines × 6) lib/amap/repositories/amap_user_repository.dart:12— lib/amap/repositories/amap_user_repository.dart:12-16 | lib/amap/repositories/order_list_repository.dart:23-27 | lib/event/repositories/event_repository.dart:21-25 | lib/loan/repositories/item_repository.dart:11-15 | lib/raffle/repositories/raffle_detail_repository.dart:28-32 | lib/raffle/repositories/user_tickets_repository.dart:18-22 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 6 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 6 times.
Duplicated block (7 lines × 10) lib/amap/repositories/order_list_repository.dart:29— lib/amap/repositories/order_list_repository.dart:29-35 | lib/loan/repositories/loan_repository.dart:11-17 | lib/loan/repositories/loan_repository.dart:51-57 | lib/mypayment/repositories/store_sellers_repository.dart:17-23 | lib/mypayment/repositories/structures_repository.dart:40-46 | lib/purchases/repositories/product_repository.dart:9-15 | lib/raffle/repositories/raffle_detail_repository.dart:12-18 | lib/raffle/repositories/raffle_detail_repository.dart:20-26 | lib/raffle/repositories/user_tickets_repository.dart:10-16 | lib/seed-library/repositories/plants_repository.dart:27-33 — there are 10 copies across 8 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 10 sites; resolving a subset leaves the remainder to drift apart.
P12 · CI test-gate honesty· Coverage collected but not gated · ×1
Coverage collected but not gated — CI collects a coverage report but no step enforces a minimum — coverage could halve and CI stays green. Add a step that fails the build when coverage drops below a floor (your coverage tool's minimum-threshold flag, or a coverage-gate action) so the number guards something. What was searched, so you can tell an absence from a miss: this repository's CI files AND its coverage configuration — the well-known coverage and test-runner config files, read at the repository root and inside workspace package directories two levels down, so a floor declared beside the tests rather than in the pipeline is credited — matched against the threshold settings this check knows by name. A floor set in your coverage service's web UI rather than in a committed file, or under a setting whose name is not one of those, is not seen here.
Third-party script without Subresource Integrity REDACTED:136— `https://cdn.jsdelivr.net/npm/pdfjs-dist@4.6.82/build/pdf.min.mjs` is executed by this page with no Subresource Integrity. Whoever can answer that request — the CDN, anyone who compromises it, anyone on the network path — runs arbitrary script in this page's origin, with its session.
Swallowed exception (empty catch) lib/tools/web-window-callback/js_interop.dart:36— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Orphaned file lib/amap/ui/pages/admin_page/delivery_ui.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 lib/settings/ui/pages/edit_user_page/edit_user_page.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 lib/raffle/ui/pages/creation_edit_page/creation_edit_page.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 lib/tools/functions.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 lib/cinema/ui/pages/session_pages/add_edit_session.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 lib/advert/ui/pages/form_page/add_edit_advert_page.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 lib/advert/ui/components/advert_card.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 lib/event/ui/components/event_ui.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 lib/amap/ui/pages/main_page/main_page.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 lib/cinema/ui/pages/detail_page/detail_page.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 lib/drawer/ui/drawer_top_bar.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 lib/raffle/ui/pages/raffle_page/confirm_payment.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 lib/phonebook/ui/pages/admin_page/admin_page.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 lib/phonebook/ui/pages/membership_editor_page/membership_editor_page.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 lib/phonebook/ui/pages/association_page/web_member_card.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 lib/raffle/ui/pages/creation_edit_page/user_cash_ui.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 lib/amap/ui/pages/delivery_pages/add_edit_delivery_cmd_page.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 lib/cinema/ui/pages/main_page/session_card.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 lib/amap/ui/pages/product_pages/add_edit_product.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 lib/vote/ui/pages/main_page/contender_card.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 lib/raffle/ui/pages/creation_edit_page/prize_handler.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 lib/event/ui/pages/detail_page/detail_page.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 lib/auth/providers/openid_provider.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 lib/booking/ui/components/booking_card.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 lib/mypayment/ui/pages/scan_page/scanner.dart:134— `!controller.value.hasCameraPermission && mounted` appears character-identically in 2 files — lib/mypayment/ui/pages/scan_page/scanner.dart, lib/purchases/ui/pages/scan_page/qr_code_scanner.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 lib/tools/ui/layouts/card_button.dart:26— `!useColors || (useColors && colors!.last == Theme.of(context).colorScheme.primary)` appears character-identically in 2 files — lib/tools/ui/layouts/card_button.dart, lib/tools/ui/layouts/card_layout.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 lib/mypayment/providers/selected_transactions_provider.dart:26— `(element.status == TransactionStatus.confirmed || element.status == TransactionStatus.refunded) && element.creation.year == currentMonth.yea…` appears character-identically in 3 files — lib/mypayment/providers/selected_transactions_provider.dart, lib/mypayment/ui/pages/stats_page/month_bar.dart, lib/mypayment/ui/pages/stats_page/sum_up_chart.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 lib/amap/providers/cash_list_provider.dart:47— `cash.user.name.toLowerCase().contains(lowerQuery) || cash.user.firstname.toLowerCase().contains(lowerQuery) || (cash.user.nickname != null &…` appears character-identically in 2 files — lib/amap/providers/cash_list_provider.dart, lib/raffle/providers/cash_provider.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 lib/booking/ui/calendar/calendar.dart:54— `details.targetElement == CalendarElement.appointment || details.targetElement == CalendarElement.agenda` appears character-identically in 2 files — lib/booking/ui/calendar/calendar.dart, lib/tools/ui/widgets/calendar.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 lib/loan/providers/history_loaner_loan_list_provider.dart:71— `e is AppException && e.type == ErrorType.tokenExpire` appears character-identically in 4 files — lib/loan/providers/history_loaner_loan_list_provider.dart, lib/loan/providers/loaner_loan_list_provider.dart, lib/tools/providers/list_notifier.dart, lib/tools/providers/single_notifier.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 lib/phonebook/ui/pages/association_editor_page/association_editor_page.dart:193— `element.associationId == association.id && element.mandateYear == association.mandateYear` appears character-identically in 4 files — lib/phonebook/ui/pages/association_editor_page/association_editor_page.dart, lib/phonebook/ui/pages/association_editor_page/member_editable_card.dart, lib/phonebook/ui/pages/association_page/member_card.dart, lib/phonebook/ui/pages/association_page/web_member_card.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 lib/booking/ui/pages/booking_pages/add_edit_booking_page.dart:324— `end.text.contains("/") && isDateBefore( processDateBack(end.text), processDateBack(start.text), )` appears character-identically in 2 files — lib/booking/ui/pages/booking_pages/add_edit_booking_page.dart, lib/event/ui/pages/event_pages/add_edit_event_page.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 lib/amap/providers/user_order_list_provider.dart:121— `error is AppException && error.type == ErrorType.tokenExpire` appears character-identically in 5 files — lib/amap/providers/user_order_list_provider.dart, lib/purchases/ui/pages/scan_page/scan_dialog.dart, lib/raffle/providers/cash_provider.dart, lib/tools/providers/list_notifier.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 lib/user/class/simple_users.dart:21— `json['nickname'] != "" && json['nickname'] != null` appears character-identically in 2 files — lib/user/class/simple_users.dart, lib/user/class/user.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 lib/phonebook/ui/pages/association_editor_page/member_editable_card.dart:56— `memberships.associationId == association.id && memberships.mandateYear == association.mandateYear` appears character-identically in 3 files — lib/phonebook/ui/pages/association_editor_page/member_editable_card.dart, lib/phonebook/ui/pages/association_page/member_card.dart, lib/phonebook/ui/pages/association_page/web_member_card.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 lib/seed-library/ui/pages/edit_plant_detail_page/editable_plant_detail.dart:93— `plantSpecies.card != null && plantSpecies.card != ""` appears character-identically in 2 files — lib/seed-library/ui/pages/edit_plant_detail_page/editable_plant_detail.dart, lib/seed-library/ui/pages/plant_detail_page/plant_detail_page.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.
D34 · Knowledge Freshness· Most significant orphaned file · ×3
Most significant orphaned file lib/vote/ui/pages/admin_page/admin_page.dart:1— One of the orphaned files carrying the most lost knowledge — ranked by size weighted by the file's role in the codebase, the same weighting behind the score above, so core code outranks equally large plumbing. A reasonable place to start a read-through before the aggregate risk above bites.
Most significant orphaned file lib/event/ui/pages/event_pages/add_edit_event_page.dart:1— One of the orphaned files carrying the most lost knowledge — ranked by size weighted by the file's role in the codebase, the same weighting behind the score above, so core code outranks equally large plumbing. A reasonable place to start a read-through before the aggregate risk above bites.
Most significant orphaned file lib/vote/ui/pages/contender_pages/add_edit_contender.dart:1— One of the orphaned files carrying the most lost knowledge — ranked by size weighted by the file's role in the codebase, the same weighting behind the score above, so core code outranks equally large plumbing. A reasonable place to start a read-through before the aggregate risk above bites.
Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 1 significant file(s) lose their only recent owner: lib/purchases/ui/pages/main_page/main_page.dart. Pair on, review, or document these before any departure.
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 (2 single-owned of 330 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; 330 of the 1029 production source files in this repository met that bar). They are anonymized user #2 (1 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: lib/purchases/router.dart.
No ADRs found lib/main.dart:28— No ADRs found. No recognised ADR directory (`docs/adr/`, `docs/decisions/`, `adr/`, `docs/rfcs/`, an `ADR0001/` folder, or their siblings) exists anywhere in this tree. What was searched, so you can tell an empty log from a search that missed one: every directory under the tree (build output, dependencies and VCS metadata excepted), for a document that is either any non-index page inside a recognised ADR directory, whatever its name and however deeply nested (`docs/adr/use-postgres.md`, `docs/adr/2024/0001-x.md`); or a file anywhere whose name is ADR-shaped (`0001-use-postgres.md`, `adr-012-caching.md`); or, when neither turned anything up, a document carrying the decision-record signature (an "Architecture Decision Record" heading, or Status / Context / Decision / Consequences as section headings). A decision log that clears none of these — unnumbered files outside any recognised directory, without those headings — is not seen by this check and this row is then wrong. If that is your case, say so rather than renaming anything; otherwise, consider recording architectural decisions in `docs/adr/`. ADRs are expected here because `lib/main.dart` makes this repository a deployable product (line 28).
D26 · Project Cohesion· Projects may be oversized for their cohesion · ×1
Projects may be oversized for their cohesion pubspec.yaml:1— `(repository root)` (72887 LoC, 1017 module-visible types across 277 directories) overshoots its size bounds. 1 of 3 build unit(s) (Gradle, Xcode, pub) overshoot their size bounds, lowering Project Cohesion to 3.3/10. Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
D28 · Secrets (history)· Rotate the exposed credentials · ×1
Concentrated knowledge decay — 225 of 330 significant files have no living knowledge, while the repository is still being changed at a low rate (14 commit(s) in the last 90 days) — so this is one repo-wide knowledge-decay state, not 225 separate risks. Counted over 330 of the 1029 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over. The code moved on without the people who understood these files: document them or schedule a read-through before the next change lands in them.
No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
M2 · Architecture documentation· No architecture diagram/doc · ×1
No architecture diagram/doc — No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
Logging is not universal — Only 1/2 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `ios`.
No SAST REDACTED:10— No static application security testing detected. For this repository's stack, add the Dart analyzer's security lints plus `semgrep --config=auto` as a CI step. What was searched, so you can tell an absence from a miss: the 7 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
P3 · Security & performance tooling· Dependabot does not watch gradle · ×1
Dependabot does not watch gradle REDACTED:5— `REDACTED` 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.
No changelog — No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
Appendix B — Reproduction & audit trail
Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.
disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
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 01a1eac7-2d83-789d-9a22-df704f48c64e · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 32 · Warnings: 636 · Recommendations: 253 — Appendix A · all findings · full markdown report.
Generated by the Canine Code Analyzer: deterministic code-health analysis. 17-11-2026 @ 18:31 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.