Public report of foss42/apidash, published 23 October 2026. It has the same score, grades and number of
findings as the full report. The details of security findings (where they are in the code, which known
vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive reportMeasured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.10.5). Watchdog signed this survey and filed it in the standard's public register, where anyone can look it up by its survey ID. Check this survey →
Signed and filed in the standard's public register, 23 October 2026, 15:23 UTC · Survey ID cd_d99cb097f49c4497af53b5433d1dffbb
foss42/apidash
Measured 23 October 2026, 15:21 UTC, at code version 7a184a8
No regression since the last survey
A regression is a drop of 0.5 points or more in the score, or of 2.5 or more out of 10 in a dimension, since the last survey.
CAI scoreAdequate
CriticalWeakAdequateStrongExemplary
No change since the last survey
The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.
A medium codebase: 54,959 lines of product code in 13 projects, tests not counted · Estimated rebuild effort: about 0.9 person-years · Weakest lens: Security and Compliance, 37
Findings by how serious they are
18 critical403 serious158 minor
13 dimensions are left out of the score. For each one, Watchdog either couldn't measure it in this code, or found no evidence of the safeguard it looks for, such as a tested backup restore. They count neither for nor against the score, and Limitations lists each one with its reason.
This survey was produced by
Watchdog
Producer
Canine Development
Analyzer
Watchdog engine 1.0.0
Measured
23 October 2026, 15:21 UTC
A measurement, not a certificate. The Code Assurance Index records a number
together with the evidence it was worked out from, so anyone can recalculate it, but it doesn't certify or guarantee
the code. The standard was written by Canine Development, which also builds Watchdog. It is open to any tool that
implements it, and today Watchdog is the only one that does.
The score is deterministic, which means the same code always gets the same score. Watchdog works it out with tools that follow published rules, and an AI model never decides it, so anyone who applies the same rules to the same code gets the same number. How it is done is explained under Methodology ▸
63of 66 dimensions measured by tools. The other 3 are advisory notes from an AI model, which explain the code but don't count towards the score.
538of 579 findings point to an exact file and line, so you can open each one in the code. The other 41 concern the repository as a whole, such as missing documentation.
66dimensions across 7 lenses, read from 54,959 lines of product code in 13 projects.
foss42/apidash scores 51 out of 100 and is rated Adequate, while five of its seven lenses score higher still: Domain Modelling at 100 and Architecture at 98, both rated Exemplary, Performance at 78, rated Strong, and Code Health and Maturity at 70, both rated Adequate.
The score is lower than those five because the weakest lens counts most, and here that is Security and Compliance, which scores 37 and is rated Weak. Its Web-Security Posture dimension scores 0 out of 10, and until that reaches 4, Security and Compliance can't be rated higher than Adequate. The first actions are to stop accepting every TLS certificate: delete the `badCertificateCallback` / `onBadCertificate` / `validateCertificate` that returns `true` so the chain, hostname and expiry are verified, and trust a self-signed or private server by loading its CA into a `SecurityContext` — never by switching verification off and to write a diagnostic trail the user can hand back with a bug report: log through `package:logging` to a file in the app's support directory that a report can attach, and if Security and Compliance rose to 70, the score would rise from 51 to about 62.
18 findings are critical: nine in Change Coupling, five in Static Analysis (SAST), three in Knowledge Freshness and one in Web-Security Posture.
Watchdog couldn't measure 12 dimensions in this code, among them Code Coverage, Test Reliability and Internal API Consistency, so they are left out of the score. The product code is 54,959 lines, which would take an estimated 0.9 person-years, around €130,000, to rebuild.
A lens is capped at Adequate while one of its dimensions scores below 4 out of 10, however well the rest of the lens does. That way a serious problem in one place always shows in the lens's rating.
How the score is built: what each lens counts forThe lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.
Watchdog compares every finding with the previous survey's. A finding that has only moved to another line in the same file counts as the same finding, so only new findings appear here. Advisory notes from the AI model are left out, because the model words them afresh in every survey.
Fixed since the last survey: 39 findings
These 39 critical or serious findings were in the previous survey, on 9 October 2026, and are gone from this one.
Exception handling · Swallowed exception (caught, then discarded) lib/widgets/previewer_json.dart
Exception handling · Swallowed exception (caught, then discarded) lib/widgets/previewer_csv.dart
Exception handling · Swallowed exception (caught, then discarded) lib/widgets/button_copy.dart
Exception handling · Swallowed exception (caught, then discarded) packages/apidash_core/lib/import_export/postman_io.dart
Exception handling · Swallowed exception (caught, then discarded) packages/apidash_core/lib/import_export/postman_io.dart
Exception handling · Swallowed exception (caught, then discarded) packages/apidash_core/lib/import_export/postman_io.dart
Exception handling · Swallowed exception (caught, then discarded) packages/apidash_core/lib/import_export/postman_io.dart
Exception handling · Swallowed exception (caught, then discarded) packages/apidash_core/lib/import_export/insomnia_io.dart
Exception handling · Swallowed exception (caught, then discarded) packages/apidash_core/lib/import_export/insomnia_io.dart
Exception handling · Swallowed exception (caught, then discarded) packages/apidash_core/lib/import_export/har_io.dart
Exception handling · Swallowed exception (caught, then discarded) packages/apidash_core/lib/import_export/har_io.dart
Exception handling · Swallowed exception (caught, then discarded) packages/better_networking/lib/utils/http_response_utils.dart
Exception handling · Swallowed exception (caught, then discarded) packages/better_networking/lib/utils/http_request_utils.dart
Exception handling · Swallowed exception (caught, then discarded) packages/better_networking/lib/utils/content_type_utils.dart
Exception handling · Swallowed exception (caught, then discarded) packages/curl_parser/lib/models/curl.dart
Exception handling · Swallowed exception (caught, then discarded) packages/insomnia_collection/lib/models/insomnia_item.dart
Rebuild cost: about €130,000 · Estimate
Cost to rebuild
€43,000 to €210,000, for 709 to 2,250 hours of work, about 0.9 person-years for 1 to 2 engineers
Difficulty of the problem
Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor
×0.7 at a score of 51. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
Size
Medium: 54,959 lines of product code
How the estimate is made: Watchdog prices the hours a team would need to write this code again, at €60 to €95 an hour. Declarations and boilerplate are priced at a fast rate and logic at a slower one, and the logic is then multiplied by the difficulty of the problem and by the quality factor. The estimate can be about 30% off either way, and it moves most with the hourly rate and the difficulty. For this code, every line is priced as straight logic, which keeps the estimate on the low side.
Top priorities
The three actions that raise the score most for the work they take. The full ranked list is in the Roadmap.
1
Stop accepting every TLS certificate: delete the `badCertificateCallback` / `onBadCertificate` / `validateCertificate` that returns `true` so the chain, hostname and expiry are verified, and trust a self-signed or private server by loading its CA into a `SecurityContext` — never by switching verification off.
Write a diagnostic trail the user can hand back with a bug report: log through `package:logging` to a file in the app's support directory that a report can attach.
Start with the error paths that emit nothing — a discarded error is the failure the user cannot describe and you cannot reproduce.
Raises the score by about 5 points · Medium effort · Observability
3
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing.
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 €130,000 to build again, about 0.9 person-years of work. Its weakest lens is Security and Compliance, at 37 (Weak). Security and Compliance is about how well the product is protected, and how it handles personal data. Because the weakest lens counts most in the score, work on Security and Compliance also moves the score most.
Based on: the rebuild estimate · the Security and Compliance grade · how much each lens counts
What to do: Start with the Security and Compliance actions in Top priorities.
If you do one thing first · First action
Stop accepting every TLS certificate: delete the `badCertificateCallback` / `onBadCertificate` / `validateCertificate` that returns `true` so the chain, hostname and expiry are verified, and trust a self-signed or private server by loading its CA into a `SecurityContext` — never by switching verification off. Of all the actions in this report, it raises the score most for the work it takes: about 12 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 Watchdog estimates the extra work at 5% to 10% on every change. The history of the code shows how much it changes: about 15,610 lines over the last 90 days, which is about 63,307 lines a year. At that pace, the extra work comes to an estimated 7.1 to 42.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 Watchdog's 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; and an engineer changes 150 to 400 lines in a day. The result is a range for planning, not a measurement.
Based on: Cyclomatic Complexity · Cognitive Complexity · Code Duplication · Cohesion (LCOM4) · the code's change history
What to do: Start with the files listed under Churn × Complexity Hotspots, which change often and are hard to read, because that is where the extra work is paid most often.
Architecture — module dependency graph
Project dependencies, layered top-to-bottom; arrows show direction. Any dashed red edge points upward or sideways — a layering smell or cycle. A clean layered graph has none.
Architecture: which parts of the code depend on which
The code is divided into modules, groups of code that each handle one part of the product, and a module depends on another when it uses code from it. The table lists the modules both down the side and across the top, in an order where each module should only use modules listed above it. A number in a cell means the module on that row uses the module in that column, and it counts the pairs of building blocks (types) that connect them. The one thing to look for is a mark above the diagonal line. It means two or more modules use each other in a loop (a dependency cycle), so none of them can be changed, tested or released on its own.
18 modules, with 24 dependencies between them. One loop runs through 3 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.
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
5
High / Critical
A03:2025 — Software Supply Chain Failures
3
Medium
Roadmap
First, enforce strict TLS certificate validation by removing insecure callbacks and properly trusting private CAs to prevent man-in-the-middle attacks. Second, implement structured logging to capture diagnostic trails for error paths, ensuring users can provide actionable data when bugs occur. Finally, harden the build pipeline by signing artifacts, establishing build provenance, and pinning build actions to ensure supply-chain integrity.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Stop accepting every TLS certificate: delete the `badCertificateCallback` / `onBadCertificate` / `validateCertificate` that returns `true` so the chain, hostname and expiry are verified, and trust a self-signed or private server by loading its CA into a `SecurityContext` — never by switching verification off.
Write a diagnostic trail the user can hand back with a bug report: log through `package:logging` to a file in the app's support directory that a report can attach. Start with the error paths that emit nothing — a discarded error is the failure the user cannot describe and you cannot reproduce.
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.
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 — 18
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 — 403
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 — 158
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 13
Something this survey could not settle
from the outside, and which could be critical or serious. Either a control was required and no
positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves
nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean
result. These are excluded from the score rather than awarded a pass, so the number on the cover neither
rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each
one is named under Limitations.
Methodology & how to trust this report
Watchdog is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. 63 of 66 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); 3 documentation/naming judgement(s) are LLM-assisted and labelled advisory. Overall confidence is 0.9 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.
Every figure here is one of three kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact; ◐ Advisory — an LLM prose judgement. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10; ◐ Sampled · advisory marks an LLM verdict over a bounded sample — advisory, never a deterministic measurement.
What we checked — 66 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, 538 of 579 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
Is there a tool behind the number? Every score below names the method that produced it — Roslyn, git, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — not a narrative.
Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
This report answers yes to all three. That's the bar to hold any assessment to.
Tools & methods
The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.
Method
Backs
Version
Evaluator
Roslyn static analysis
Complexity, cohesion, coupling, dead code, API surface, layering
What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.
D8 Code Coverage — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: test source is present (.dart) but the built-in coverage collector has no runner for this repository's ecosystem — so this suite was never executed by it. Not scored — this is a gap in the analyzer's language coverage, not a defect in the repo. To have real coverage read, produce a coverage report in a standard format (lcov — `flutter test --coverage` (or `dart test --coverage=coverage` then `dart run coverage:format_coverage --lcov`)) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures. You can widen what we reach: optional: produce a coverage report in a standard format (lcov — `flutter test --coverage` (or `dart test --coverage=coverage` then `dart run coverage:format_coverage --lcov`)) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures — then the real number is read on the next scan.
D11 Test Reliability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.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.
D22 Internal API Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is a COLLECTOR gap, not an environment fault: it declares a published package (packages/apidash_design_system/pubspec.yaml), but no published-package marker D22 reads admitted any project here, so this ecosystem's public API has no collector, and the remedy is to write one — no change to the scan image can close it.
D27 Navigability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
AX6 Interface segregation — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
AXB1 Runtime evidence locked — no reproducible boot — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Subject: a native UI project (pubspec.yaml). The Runtime Evidence tier boots an app only via docker-compose, an Aspire AppHost, a Dockerfile, an npm dev script, a web service's own toolchain entry point (cargo, go, dotnet, Python, Spring Boot), or an Android app's own Gradle wrapper (run on an emulator); an Apple or Flutter app needs a host it lacks. None applied, so no live runtime a11y/egress/header evidence was collected. You can widen what we reach: add a docker-compose.yml (or an Aspire AppHost) that brings the app up with its dependencies. Watchdog then boots it in an isolated sandbox and gathers real runtime evidence — you change nothing in your pipeline (no CI step, no SDK).
C1 Data Protection — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 'package:hive_ce_flutter' is imported (lib/services/hive_services.dart:2), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
C3 Audit Trail — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 'package:hive_ce_flutter' is imported (lib/services/hive_services.dart:2), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
C4 Data Retention — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 'package:hive_ce_flutter' is imported (lib/services/hive_services.dart:2), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
C5 Data-Subject Rights — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 'package:hive_ce_flutter' is imported (lib/services/hive_services.dart:2), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
P1 CI/CD gates — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. A CI pipeline exists and the word "test" appears, but no explicit test-runner invocation (your stack's test command, or a test job) was matched — so either the gate runs tests through a step this pass could not recognise, or "test" is incidental here (a path, "latest", a reporter). Which of the two it is cannot be settled from this dimension's evidence; the coverage dimensions report whether a suite exists at all. You can widen what we reach: name the test runner explicitly in the pipeline step (your stack's test command, or a job named for the suite) so the gate is unambiguous to a reader and to this pass.
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.
P8 Schema migrations — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads EF Core usage in C# and the schema tooling its file scan recognises only, and no .NET project was loaded, and this repository's language is not one the scan models, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X24 Document value interpolated into markup unescaped — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Scala, Ruby and Python source only, and no C# was loaded and no JavaScript/TypeScript, Java, Scala, Ruby or Python was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X3 Exception handling — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 35 further occurrence(s) are not listed individually; the score already reflects all 75.
Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.
Limitations & what we did not check
Watchdog assesses the repository exactly as committed, and only the repository. By design it does not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.
D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
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 is judged by an LLM over a bounded sample of docs — it reads what is written, not whether the docs match the running system, and it is advisory, not a measurement. Its critique rows are drawn from a closed category vocabulary and each row means the same thing in every run, so two scans can be compared row by row; the SET that fires is still a sample, and does not repeat exactly. Measured on one frozen input, six scans at one engine SHA: 2-5 critique rows per scan, 8 distinct rows across the six, 3 of those 8 seen in only one scan. So a D19 row is evidence about the documentation, but a COUNT of D19 rows is not a quantity — never read a change in it as an improvement or a regression.
D20 ADR Quality: ADR quality is an LLM read of the decision records present — it cannot know about decisions made and never recorded, and its verdict is sampled and advisory.
D21 Naming Consistency: Naming quality is an LLM judgement over a bounded sample — it assesses clarity/consistency of the names it sees, not domain-correctness, and is advisory.
D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
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: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
The LLM boundary
LLM-set scores this run (3): D19, D21, M4 (model: Local LLM). For these, a model reads a bounded sample and sets the numeric score; each names its own sample and method on its card. They are sampled and advisory by design: they vary at the margins between runs and are never a deterministic measurement. Every other score in this report is tool-computed at confidence 1.0.
What it measures: How tangled the control flow is — methods with many branches are hard to test and change.
Method: Cyclomatic complexity per method (1 + decision points), computed exhaustively across production source; test projects separated by convention. Deterministic.
55 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was PromptBuilder.buildTaskPrompt at 116. A further 5 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being Codegen.getCode at 37 — they are counted neither in the figure above nor in this dimension's score. 4 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: lib/codegen/codegen.dart (Codegen.getCode at 37), lib/screens/home_page/editor_pane/url_card/editor_pane_request_url_card.dart (EditorPaneRequestURLCard.build at 21), lib/dashbot/services/actions/auto_fix_service.dart (AutoFixService.apply at 17), lib/screens/home_page/editor_pane/details_card/request_pane/request_pane.dart (EditRequestPane.build at 17). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
+ 50 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 1 body over 60 down to 60 or less in Cyclomatic Complexity — start with PromptBuilder.buildTaskPrompt (cyclomatic 116). — Refactoring it lifts Cyclomatic Complexity from 3.9 to about 5.2/10.
Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d1_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How hard the code is for a person to follow, beyond raw branching.
Method: Cognitive complexity per method (Sonar-style nesting-penalized score), computed exhaustively over production code, excluding test projects. Deterministic.
+ 81 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 6 bodies over 60 down to 60 or less in Cognitive Complexity — start with PromptBuilder.buildTaskPrompt (cognitive 175), CollectionStateNotifier._connectGrpc (cognitive 147), CollectionStateNotifier.sendRequest (cognitive 114). — 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 6 together lifts Cognitive Complexity from 2.0 to about 3.6/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes7.1 / 10Strong✓ Tool-verified
What it measures: Over-large classes that try to do too much ("god classes").
Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.
Resolve the 35 MethodTooLong finding(s) in God Classes — start with collection_providers.dart (4), realtime_event_stream_view.dart (2), example4.dart. — One of this dimension's main actionable groups (35 warning-level).
Resolve the 6 ClassTooLong finding(s) in God Classes — start with collection_providers.dart, prompt_builder.dart, chat_viewmodel.dart. — One of this dimension's main actionable groups (6 warning-level).
Resolve the 6 FileTooLong finding(s) in God Classes — start with collection_providers.dart, prompt_builder.dart, chat_viewmodel.dart. — One of this dimension's main actionable groups (6 warning-level).
Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Copy-pasted code that should be shared instead.
Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), density-scored per KLoC of production code. Deterministic.
107 duplicated block group(s) detected. A further 6 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted. 4 of the 113 are in trees this repository does not ship — vendored, example/demo, fixture and benchmark code — and are ranked below the shipped groups rather than excluded from them: the duplication there is real and is still counted in this dimension's score. The dimensions that publish a production-file census leave those trees out of theirs, so this count is deliberately drawn over the wider population.
+ 67 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 8 Duplicated block (10 lines × 2) finding(s) in Code Duplication — start with collection_providers.dart (2), okhttp.dart, chat_viewmodel.dart. — One of this dimension's main actionable groups (8 warning-level).
Resolve the 7 Duplicated block (11 lines × 2) finding(s) in Code Duplication — start with request_apply_service.dart, generate_ui_dialog.dart, his_request_pane.dart. — One of this dimension's main actionable groups (7 warning-level).
Resolve the 5 Duplicated block (16 lines × 2) finding(s) in Code Duplication — start with prompt_builder.dart, settings_model.dart, his_bottombar.dart. — One of this dimension's main actionable groups (5 warning-level).
Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · 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.
13 production modules (pub), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 0 module(s) off the main sequence, with abstractness counted on 12 of the 13 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
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 1 Low cohesion finding(s) in Cohesion (LCOM4) — start with collection_providers.dart. — One of this dimension's main actionable groups (1 warning-level).
Enforce Cohesion (LCOM4) in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
Detailed fixes: d6_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether dependencies are current, secure, and not bloated.
Method: Manifest scan via dotnet list package across all projects; worst-signal-per-package deduction (saturating for vulnerabilities, capped-linear for deprecation/outdated) per KLoC. Exhaustive, deterministic.
27 outdated, 0 discontinued direct pub dependencies. The direct set is read from pubspec.lock's own `dependency:` markers, so development and transitive packages are excluded by the resolver's classification rather than by inference. SDK-sourced packages (flutter and friends) are not graded: they ship with the toolchain and carry the placeholder version 0.0.0, so there is no pub.dev release for them to be behind. A newer release is reported only where this repository's OWN constraint already admits it — which for a BARE constraint it never does, because a bare pub constraint is EXACT and `dart pub upgrade` would not move it. Known CVEs in this dependency graph are D30's question.
Outdated: code_builder · ×27
What to do
Enforce Dependency Hygiene in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
Detailed fixes: d12_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 268 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 11 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 104 package(s) locked at an older version the licence read is that of the package's latest analysed release, not of the locked one. 3 of them carry no licence pub.dev recognises; that is missing data, not a violation, and none of them is charged.
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 7 Hotspot finding(s) in Churn × Complexity Hotspots — start with collection_providers.dart, his_request_pane.dart, request_pane_grpc.dart. — One of this dimension's main actionable groups (7 warning-level).
Resolve the 1 Repeated repair finding(s) in Churn × Complexity Hotspots — start with ws_recently_sent.dart. — One of this dimension's main actionable groups (1 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 Factor8.2 / 10Strong✓ Tool-verified
What it measures: Whether knowledge is concentrated in too few people (the "bus factor").
Method: Living knowledge per author via time-decayed commit attribution (6-month half-life, focus weighting) across largest source files. Deterministic, avoids blame's mechanical-refactor false positives.
41 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is lib/services/connection_manager.dart. Counted over 231 of the 536 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 · ×2
Further sole-owners (lower concentration)
What to do
Resolve the 2 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (2 recommendation-level).
Resolve the 1 Further sole-owners (lower concentration) finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d16_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Acknowledged debt left in the code — TODOs, dead code, suppressed warnings.
Method: Roslyn syntactic debt markers (suppressions/TODO/FIXME/HACK/empty-catch/commented-code/Obsolete) plus SymbolFinder dead-code analysis; weighted-debt-per-KLoC density deducted 2.0x per unit. Deterministic, exhaustive.
35 deducted task-comment markers across 54959 LoC (0.1/KLoC) → score 9.9. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
Resolve the 34 TodoComment finding(s) in Explicit Debt — start with env_manager_test.dart (3), code_pane.dart (3), his_request_test.dart (2). — One of this dimension's main actionable groups (34 warning-level).
Resolve the 1 FixmeComment finding(s) in Explicit Debt — start with ui_providers_test.dart. — One of this dimension's main actionable groups (1 warning-level).
Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the project's documentation is clear, complete, and useful.
Method: Judged by language model at low temperature (0.0-0.1) on a deterministic doc sample (READMEs plus first 25 architecture docs), with two-pass stability filtering. Advisory, sampled.
The repository's root README is clear and comprehensive (API Dash ⚡️ with a Discord invite badge, download table, a full list of supported mime-types, and an overview of the project), while its subdirectories document the doc/ directory (e.g. API Dash Docs, dev_guide, security docs) as well as packages such as better_networking, curl_parser, genai, har, insomnia_collection — each with their own READMEs that describe what they are for and how to use them. The root README is the one that needs to be judged on its own scope (overview, installation/usage/contribution), but all visible documents are well-structured and complete within their own directories. The repository is well documented: the READMEs for each package directory (e.g. packages/json_explorer/README.md) describe what the directory provides and give usage examples, while architecture/design docs are kept separate (242 markdown files). The root README covers installation, overview, features, and contribution guidance; the doc/dev_guide/adding_codegen.md is a detailed code-generation guide with an outline that all sections exist in. There is no single document missing any of the standard categories.
Documentation: no project overview · ×2README.md
✓ On the Gold path — maintain.
Detailed fixes: d19_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D20 · ADR Quality0.0 / 10Critical✓ Tool-verified
What it measures: Whether architecture decisions are recorded well (context, decision, consequences).
Method: Per-ADR judgment by language model at low temperature with two-pass stability; confidence is share of ADRs evaluated; enforcement-field presence detected deterministically. Advisory.
What it measures: Whether names — types, methods, variables — are clear and consistent.
Method: Judged by language model at low temperature (0.0-0.1) on a deterministic random symbol sample (fixed size, not exhaustive), with disclosed confidence band. Advisory, sampled.
1 of 13 build units (pub) flagged as possibly oversized/incoherent.
Projects may be oversized for their cohesion
What to do
Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d26_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.
Method: Secret scan via TWO gitleaks detect passes in an isolated checkout — the full git history, then a second --no-git pass over the working tree as it stands — merged and de-duplicated by (rule, file, line); each match flagged High. Both invocations are recorded in the audit trail. Exhaustive; when the tool is absent, or when its output cannot be parsed into the expected shape, the dimension is WITHHELD as an explicit measurement gap on our side — unscored and excluded from the lens, never a hedged middling score.
What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.
Method: Polyglot static analysis via semgrep across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.
Coverage: semgrep pattern rules over all files — exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).
5 finding(s): 0 critical, 5 high, 0 medium, 0 low. 4 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 1 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
REDACTED
REDACTED
What to do
Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
No action in Static Analysis (SAST) — all 4 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 (4 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.
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.
64 of 231 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is lib/utils/js_utils.dart. Counted over 231 of the 536 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
Resolve the 61 Orphaned file finding(s) in Knowledge Freshness — start with okhttp.dart (2), multi_trigger_autocomplete.dart, oauth2_field.dart. — One of this dimension's main actionable groups (61 recommendation-level).
Resolve the 3 Orphaned knowledge finding(s) in Knowledge Freshness — start with js_utils.dart, json_explorer.dart, json_explorer_store.dart. — One of this dimension's main actionable groups (3 issue-level).
Resolve the 1 Further orphaned files (smaller) finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d34_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.
Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.
Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling. A non-source file is never a coupling PARTICIPANT either: documentation, schemas, config and data files are dropped with the rest, so a code↔docs pair — a command and the reference page that restates it — is not reported however strongly the two co-change; nor is coupling that runs THROUGH a build step or config file.
Resolve the 9 Boundary-crossing change coupling finding(s) in Change Coupling — start with collection_pane.dart (2), collection_providers.dart (2), editor_request.dart. — One of this dimension's main actionable groups (9 issue-level).
Resolve the 11 Change coupling finding(s) in Change Coupling — start with dashbot_dashboard.dart (2), navbar.dart, api_key_auth_fields.dart. — One of this dimension's main actionable groups (11 warning-level).
Resolve the 1 Change coupling clique finding(s) in Change Coupling — start with request_form_data.dart. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d35_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the build pipeline provides supply-chain integrity — generated provenance/attestation, signed artifacts (cosign/sigstore), an SBOM, and pinned build actions. Presence of the configuration, not a runtime guarantee.
Method: Supply-chain provenance/signing read deterministically from CI/build config (.github/workflows, .gitlab-ci.yml, azure-pipelines, Jenkinsfile, .circleci) + the release surface: four signals — generated provenance/attestation (SLSA/in-toto/actions-attest), artifact signing (cosign/sigstore/gitsign), an SBOM (syft/sbom-action/*.spdx.json/*.cdx.json), and SHA-pinned build actions — scored 10·present/denom. NotApplicable without a build pipeline. Detects configuration presence, not runtime enforcement.
What it measures: Whether the repository publishes a coordinated-vulnerability-disclosure policy (SECURITY.md or security.txt) with a reporting contact, so finders know how to report a vulnerability. Presence of a policy file with a contact, not whether the policy is adequate or honoured.
Method: Vulnerability-disclosure policy read deterministically from the repo: a SECURITY.md (root/.github/docs) or .well-known/security.txt / security.txt, regex-checked for a reporting contact (email / URL / mailto). Present + contact → 10; present without a contact → 4; NotApplicable when no policy file exists (it may live off-repo). Detects the policy file's presence + contact, not its adequacy.
What it measures: Whether any dependency the repository declares is published as MALICIOUS rather than merely vulnerable — a package that is an attacker's work, in any ecosystem osv-scanner reads. Scored 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. SCORED, not informational.
What it measures: Whether anyone still ships security patches for the platform this repository RUNS ON — the runtime it pins and the framework majors its own constraints hold it to. Separate from D12 because the question differs: a current Django on an end-of-life Python is perfectly up to date and completely unsupported, and the fix is a migration rather than a version bump. What the repository says it merely SUPPORTS is never charged.
Method: End-of-life PLATFORM read from the repository's own declarations and graded against a FROZEN, dated table of vendor support dates — no network, no feed, no API, so this dimension answers identically inside a closed scan fence. Two subjects: a RUNTIME the project pins (a single or all-end-of-life TargetFramework, a .nvmrc or .python-version, a requires-python CAP) and a FRAMEWORK major a dependency constraint cannot move off (a caret, tilde or exact version; `vue@^2.7.16` pins Vue 2). A FLOOR is deliberately never charged — `requires-python = ">=3.8"` states what a package SUPPORTS, not what it runs on — and a multi-target project is charged only when EVERY target is out of support. Runtime 4.0/product capped 8.0, framework 1.5 capped 4.5. The table is safe to freeze because a statement about support that ended in the past cannot become false: it loses recall as it ages, never precision, and a test asserts every entry predates the freeze date. Disjoint from D31 (a container image's OS layer) and D29 (the toolchain a CI workflow installs). Abstains when the repository declares no platform this pass reads — never scores it clean.
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 1 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Other · Architecture — Whether any singleton service captures a scoped/transient dependency — a silent lifetime/threading bug.
Method: Roslyn scan: DI registrations parsed from AddSingleton/Scoped/Transient; each singleton checked for captured shorter-lifetime dependencies. Exhaustive, deterministic.
Other · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified. How each file's role is decided, because the split is only as good as that: a generated name or a build-output tree makes it Generated, a test project makes it Test, and otherwise the file's NAMESPACE and PATH words are matched against fixed vocabularies in a fixed ORDER — domain, then infrastructure, then application — so a file whose words hit two layers is counted under the earlier one. A production file matching none of them counts as application, so that share reads 'application or unclassified' rather than a measured application layer. Roles come from naming convention, never from what the code does. On this repository the split was taken from the source tree on disk rather than from a loaded .NET workspace, so a file's role is decided by its PATH segments alone — no declared namespace was available to add to the evidence — and generated output is excluded from the census entirely rather than counted as a generated share.
Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.
Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.
What to do
The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
Other · Architecture — Whether the project-reference graph is acyclic (cycles block independent build/deploy and signal eroding boundaries).
Method: Project reference cycles via elementary-DFS over real .csproj references, using the engine shared with D5/D7; cyclic versus acyclic. Exhaustive, deterministic.
Other · Architecture — Whether dependencies point inward (Domain ← Application ← Infrastructure/Web) — the clean-architecture dependency rule, checked across the project graph.
Method: Layer violations by name-segment inference (Domain/Core to Application to Infrastructure/Web) over the project-reference graph. Exhaustive over all projects, deterministic.
Other · Architecture — Whether read (query) handlers stay side-effect-free — a query that writes persistent state or raises events breaks CQS and makes reads unsafe to retry, cache, or route to a read replica.
Method: Roslyn scan: CQRS handlers classified query-vs-command by interface (IQueryHandler/ICommandHandler/IRequestHandler<TQuery,TResult>) and name convention (*Query/Get*/Find* vs *Command); each query handler's body checked for persistent-state writes (SaveChanges/repository Add-Update) or event publishes by resolved invocation. Deterministic, type-level, exhaustive over the detected handlers.
Coverage: Population: CQRS handlers identified by IQueryHandler/ICommandHandler/IRequestHandler interface + *Query/Get*/Find*/*Command NAME convention; query purity then checked exhaustively within that set — a query handler using neither convention is invisible, and mutation is a resolved persistence/publish CALL, not full dataflow.
Other · Domain Modelling — Whether 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.
A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something. (×9) — packages/json_explorer/test/golden/json_attribute_test.dart:40, packages/json_explorer/test/golden/json_attribute_test.dart:153, packages/json_explorer/test/golden/json_attribute_test.dart:211, …
`createSpecialText`'s body only throws an UnsupportedError or an UnimplementedError that gives its reason — sometimes a deliberate refusal, often an unfinished stub. Confirm it's intentional. — packages/json_field_editor/lib/src/json_highlight/json_highlight.dart:71
What to do
Clear the softer debt: re-enable or delete tests marked `skip:`, decide whether each empty method or UnsupportedError is deliberate (and say so in a comment), and replace `// ignore_for_file: type=lint` with targeted, justified ignores.
Maturity · Maturity — Whether the repo and its projects have a README, and whether it's substantive and current.
Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.
What to do
Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.
Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.
No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
Maturity · Maturity — Whether the README actually describes the code that exists (LLM-judged, advisory).
Method: Judged by language model at low temperature: README accuracy versus actual projects, within a disclosed tolerance. Advisory, not a measured number.
doc/dev_guide/flutter_rust_bridge_experiment.md changes into `apidash/packages/hurl/rust`, but no such folder exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — doc/dev_guide/flutter_rust_bridge_experiment.md:120
doc/security/COMMANDS.md documents the environment variable `FETCH_LICENSE`, but no code, script or configuration file names it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — doc/security/COMMANDS.md:26
doc/user_guide/gateway_proxy.md runs `node server.js`, but `server.js` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — doc/user_guide/gateway_proxy.md:52
doc/user_guide/grpc_user_guide.md links to `images/grpc/grpc_overview.png`, but `doc/user_guide/images/grpc/grpc_overview.png` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — doc/user_guide/grpc_user_guide.md:7
doc/user_guide/grpc_user_guide.md runs `docker compose -f grpc/docker-compose.yml up --build`, but `grpc/docker-compose.yml` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — doc/user_guide/grpc_user_guide.md:19
doc/user_guide/grpc_user_guide.md links to `images/grpc/grpc_quick_start.png`, but `doc/user_guide/images/grpc/grpc_quick_start.png` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — doc/user_guide/grpc_user_guide.md:37
doc/user_guide/grpc_user_guide.md links to `images/grpc/grpc_sidebar_badge.png`, but `doc/user_guide/images/grpc/grpc_sidebar_badge.png` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — doc/user_guide/grpc_user_guide.md:54
doc/user_guide/grpc_user_guide.md links to `images/grpc/grpc_request_screen.png`, but `doc/user_guide/images/grpc/grpc_request_screen.png` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — doc/user_guide/grpc_user_guide.md:108
doc/user_guide/grpc_user_guide.md links to `images/grpc/grpc_reflect.png`, but `doc/user_guide/images/grpc/grpc_reflect.png` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — doc/user_guide/grpc_user_guide.md:144
doc/user_guide/grpc_user_guide.md links to `images/grpc/grpc_proto_import.png`, but `doc/user_guide/images/grpc/grpc_proto_import.png` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — doc/user_guide/grpc_user_guide.md:158
doc/user_guide/grpc_user_guide.md links to `images/grpc/grpc_type_selector.png`, but `doc/user_guide/images/grpc/grpc_type_selector.png` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — doc/user_guide/grpc_user_guide.md:202
doc/user_guide/grpc_user_guide.md links to `images/grpc/grpc_request_message.png`, but `doc/user_guide/images/grpc/grpc_request_message.png` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — doc/user_guide/grpc_user_guide.md:226
doc/user_guide/grpc_user_guide.md links to `images/grpc/grpc_metadata.png`, but `doc/user_guide/images/grpc/grpc_metadata.png` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — doc/user_guide/grpc_user_guide.md:246
doc/user_guide/grpc_user_guide.md links to `images/grpc/grpc_auth.png`, but `doc/user_guide/images/grpc/grpc_auth.png` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — doc/user_guide/grpc_user_guide.md:274
doc/user_guide/grpc_user_guide.md links to `images/grpc/grpc_tls.png`, but `doc/user_guide/images/grpc/grpc_tls.png` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — doc/user_guide/grpc_user_guide.md:307
doc/user_guide/grpc_user_guide.md links to `images/grpc/grpc_response_stream.png`, but `doc/user_guide/images/grpc/grpc_response_stream.png` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — doc/user_guide/grpc_user_guide.md:328
doc/user_guide/grpc_user_guide.md links to `images/grpc/grpc_streaming_send.png`, but `doc/user_guide/images/grpc/grpc_streaming_send.png` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — doc/user_guide/grpc_user_guide.md:341
doc/user_guide/instructions_to_run_generated_code.md installs the package `System.Net.Http` (`dotnet add package System.Net.Http`), but no project or props file references it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — doc/user_guide/instructions_to_run_generated_code.md:234
doc/user_guide/instructions_to_run_generated_code.md installs the package `RestSharp` (`dotnet add package RestSharp`), but no project or props file references it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — doc/user_guide/instructions_to_run_generated_code.md:310
doc/user_guide/instructions_to_run_generated_code.md runs `node app.js`, but `app.js` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — doc/user_guide/instructions_to_run_generated_code.md:560
doc/gsoc/2025/udhay_adithya_j.md names `lib/services/flutter_js_service.dart`, but no file or folder `lib/services/flutter_js_service.dart` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — doc/gsoc/2025/udhay_adithya_j.md:286
doc/gsoc/2026/borgy.md documents the environment variable `APIDASH_PATH`, but no code, script or configuration file names it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — doc/gsoc/2026/borgy.md:172
doc/gsoc/2026/shashwat_pratap_singh.md names `lib/services/storage/workspace_storage.dart`, but no file or folder `lib/services/storage/workspace_storage.dart` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — doc/gsoc/2026/shashwat_pratap_singh.md:77
doc/gsoc/2026/shashwat_pratap_singh.md names `lib/services/workspace_service.dart`, but no file or folder `lib/services/workspace_service.dart` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — doc/gsoc/2026/shashwat_pratap_singh.md:78
doc/gsoc/2026/shashwat_pratap_singh.md names `lib/providers/workspace_lifecycle.dart`, but no file or folder `lib/providers/workspace_lifecycle.dart` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — doc/gsoc/2026/shashwat_pratap_singh.md:78
doc/gsoc/2026/shashwat_pratap_singh.md names `lib/workflow/`, but no file or folder `lib/workflow` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — doc/gsoc/2026/shashwat_pratap_singh.md:82
doc/gsoc/2026/shashwat_pratap_singh.md names `lib/dashboard/`, but no file or folder `lib/dashboard` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — doc/gsoc/2026/shashwat_pratap_singh.md:83
doc/gsoc/2026/shashwat_pratap_singh.md links to `../../user_guide/collaboration_guide.md`, but `doc/user_guide/collaboration_guide.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — doc/gsoc/2026/shashwat_pratap_singh.md:160
doc/gsoc/2026/shashwat_pratap_singh.md links to `../../user_guide/workflows_guide.md`, but `doc/user_guide/workflows_guide.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — doc/gsoc/2026/shashwat_pratap_singh.md:270
doc/gsoc/2026/shashwat_pratap_singh.md links to `../../user_guide/dashboard_guide.md`, but `doc/user_guide/dashboard_guide.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — doc/gsoc/2026/shashwat_pratap_singh.md:355
What to do
Reconcile the README with reality: doc/dev_guide/flutter_rust_bridge_experiment.md changes into `apidash/packages/hurl/rust`, but no such folder exists; doc/security/COMMANDS.md documents the environment variable `FETCH_LICENSE`, but no code, script or configuration file names it; doc/user_guide/gateway_proxy.md runs `node server.js`, but `server.js` does not exist; doc/user_guide/grpc_user_guide.md links to `images/grpc/grpc_overview.png`, but `doc/user_guide/images/grpc/grpc_overview.png` does not exist; doc/user_guide/grpc_user_guide.md runs `docker compose -f grpc/docker-compose.yml up --build`, but `grpc/docker-compose.yml` does not exist.
Do you agree with this assessment?
P1 · CI/CD gates8.5 / 10Strong✓ Tool-verified
Readiness · Readiness — Whether an automated pipeline builds and tests every change.
Method: Filesystem scan: CI workflow files (.github/workflows, .gitlab-ci.yml, etc.) for build and test stages. Exhaustive, deterministic.
What to do
Run the test suite in CI via an explicit runner step for your stack, and gate merges on it.
Do you agree with this assessment?
P10 · Library API & versioning6.0 / 10Adequate✓ Tool-verified
Readiness · Readiness — For a library: a deliberate (small) public API surface and explicit semantic versioning so consumers can depend on it safely.
Method: Roslyn scan: public API surface area and semantic-versioning markers (SemVer attributes, changelog entries) for libraries; off .NET, a library is the ecosystem's publication act (an npm package that is not private and names an entry point, a PyPI distribution with a build system, a Rust library crate, a Maven/Gradle module that publishes, a Go module with no package main, a gemspec, a Composer library, a SwiftPM library product, a pub.dev or Hex package), its surface is the share of types the language model records as public (Rust, Swift, Java, Kotlin, Go, Dart; not measured where the model records no type visibility or, as in TypeScript, only module-level export), and its version is read from the manifest, a semver CHANGELOG, release tooling or semver git tags. Exhaustive, deterministic.
114/118 types (97%) declared in the published library are public. For a library, every public type is a stability contract — keep implementation types off the surface and expose only the intended API.
What to do
Keep implementation types off the public surface (Dart: a `_` name, or keep it under `lib/src/` unexported) so internals can change without breaking consumers.
Do you agree with this assessment?
P2 · Observability0.0 / 10Critical✓ Tool-verified
Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.
No logging or diagnostics emission found. This repository ships a binary its users launch rather than a service you operate, so there is no operator to page — but when a run fails on a user's machine, neither they nor you have anything to read.
What to do
Write a diagnostic trail the user can hand back with a bug report: log through `package:logging` to a file in the app's support directory that a report can attach. Start with the error paths that emit nothing — a discarded error is the failure the user cannot describe and you cannot reproduce.
Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).
Method: Filesystem scan: SAST configuration, dependency-update automation, secret scanning, and a benchmark harness or benchmark step — in this repository's own ecosystem. Exhaustive, deterministic.
What to do
Dependabot is configured but does not watch `github-actions` — 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 · Performance — Whether the code is written to minimise allocations so it doesn't pressure its host's memory manager — buffer/slice views over copies, object pooling, stack or value-type allocation, and buffer writers. Reward-only: credited where present, never penalised where a simpler style is fine.
Method: Production-source scan: density (per 1k LoC) of allocation-aware APIs — in .NET Span/Memory, ArrayPool/ObjectPool, stackalloc, ValueTask, value-type structs, IBufferWriter, string.Create, SkipLocalsInit; off .NET, with comments and strings blanked, Go's sync.Pool, preallocated slices/maps, Grow, strconv.Append* and buf[:0] reuse; the JVM's NIO buffer views, MemorySegment, primitive collections, pools and literal presizes (plus Kotlin primitive arrays and value classes, Scala AnyVal and @specialized); Swift's reserveCapacity, ContiguousArray, withUnsafe* access and ~Copyable. Activated off .NET on the same floor (400 lines, and benchmarks or 8 uses); Rust and garbage-collected scripting languages are not applicable. Reward-only. Deterministic, syntax/text detection.
What to do
Raise allocation-aware density on the hot paths — currently 8 use(s) across 56,649 production line(s) (~0.1/1k). More of the idioms below on the allocation-heavy paths climbs this toward 10.
Dart: on hot paths, hold numbers in dart:typed_data lists (Int32List, Float64List …) instead of boxed List<int>/List<double>, read through views (sublistView, buffer.asInt32List, asByteData) instead of copying, make lists that never grow growable: false, compute in the SIMD types (Float32x4List …), and build bytes with BytesBuilder(copy: false).
Readiness · Performance — Whether asynchronous code stays responsive — it avoids sync-over-async blocking (a .NET .Wait()/.GetAwaiter().GetResult(), a time.sleep or blocking HTTP call inside a Python coroutine, a *Sync call inside an async JavaScript function, block_on inside a Rust async fn, runBlocking inside a Kotlin suspend function, block() inside a Reactor publisher) that stalls a thread or event loop and risks deadlock, and, where the code is a reusable library on .NET, awaits with ConfigureAwait(false) so it never captures and stalls its caller's context.
Method: Production-source scan: sync-over-async blocking counted everywhere — .Wait()/.GetAwaiter().GetResult() in .NET; off .NET, read from the language model, a blocking call inside an async function (Python, TS/JS, Rust, Kotlin, Swift, Dart) or inside a Java method returning a Reactor Mono/Flux or a Scala method returning a Future or effect — and, for a .NET library with ≥5 awaits, the share of awaits using ConfigureAwait(false). Deterministic, syntax/text detection.
Other · Security — Read from this repository's Dart source: cryptographic hygiene (weak hash or cipher, key material fixed in the source) and outbound TLS certificate validation — facts about code that hold whether or not it serves anything itself. The TLS protocol version is not read: `dart:io` leaves the protocol floor to the platform's TLS library and has no switch that admits an obsolete version. This repository serves HTTP itself (packages/better_networking/lib/services/oauth_callback_server.dart:25 — `HttpServer.bind(`), so its Dart source was also read for the server controls: TLS served or HSTS set, security response headers, cookie flags and inbound validation — each credited where its Dart spelling appears in production source, not proven on every route. Every server it binds listens on the loopback interface only, so its traffic never leaves the device and HTTPS enforcement is N/A, as it is for a native app's loopback redirect listener (RFC 8252 §7.3).
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.
`badCertificateCallback` returning `true` is set on a TLS client, so every peer certificate is accepted — including one an attacker presents. Chain, expiry, revocation and hostname are all skipped, so an attacker on the network path can present any certificate and read or rewrite the traffic — the connection is encrypted to the attacker, not to the intended host. Remove the callback so `dart:io` validates the peer. If the server presents a self-signed or privately-issued certificate, trust THAT issuer rather than every certificate: load its CA into a `SecurityContext` (`setTrustedCertificatesBytes`) and pass it as `HttpClient(context: …)` / `SecureSocket.connect(…, context: …)`, which keeps the chain and hostname checks on. A callback that must exist should compare the presented certificate with a pinned fingerprint, never return `true`. — packages/better_networking/lib/services/http_client_manager.dart:8
MD5/SHA1 is computed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ (`sha256.convert(…)` from `package:crypto`) for content integrity, or a KDF (bcrypt/Argon2/scrypt) for password storage. If it only derives a non-security identifier (a cache key, an avatar URL, an ETag), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as xxhash or murmurhash says it in code — since the algorithm alone cannot distinguish the two uses. Where a protocol this code does not own fixes the digest (a k-anonymity range query, a legacy signature format), the protocol decides; say so beside the call. — packages/better_networking/lib/utils/auth/digest_auth_utils.dart:34
None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is set on a response this repository's Dart server sends — defense in depth, even when a proxy could set them. (−2.0 on this card.) The server: packages/better_networking/lib/services/oauth_callback_server.dart:25 — `HttpServer.bind(`.
No handler of this repository's Dart server answers 400, 413 or 422 (`Response.badRequest`, `HttpStatus.badRequest`, `statusCode = 400`) and no validation package (luthor, acanthis, ez_validator, json_schema, …) is imported — nothing shows inbound requests being checked, and refused, before a handler acts on them. A check that answers its failure with 200 and an error body is not seen. (−2.0 on this card.) The server: packages/better_networking/lib/services/oauth_callback_server.dart:25 — `HttpServer.bind(`.
What to do
Stop accepting every TLS certificate: delete the `badCertificateCallback` / `onBadCertificate` / `validateCertificate` that returns `true` so the chain, hostname and expiry are verified, and trust a self-signed or private server by loading its CA into a `SecurityContext` — never by switching verification off.
Review each MD5/SHA1 use by what it protects: replace it with SHA-256+ (or a KDF for passwords) where the digest is security-relevant, and switch it to a non-cryptographic hash (xxhash, murmurhash) where it only derives an identifier such as a cache key.
Set security response headers on what the server sends — `response.headers.set('X-Content-Type-Options', 'nosniff')` in a `dart:io` handler, or a shelf middleware that adds `Content-Security-Policy`, `X-Content-Type-Options` and a frame policy to every `Response`.
Validate what the server reads from a request — path, query, headers, body size and shape — and answer what fails with 400 (413 for an oversized body) before a handler acts on it, so a client and a proxy can tell a refusal from a success.
Other · Code Health — Whether the code avoids sync-over-async (deadlock-prone blocking on tasks) and async void.
Method: Roslyn syntax scan: async methods scanned for .Wait()/.GetAwaiter().GetResult() and async-void outside event handlers. Deterministic, hard fact per invocation.
Other · Code Health — Whether any branch is dead by construction — a switch arm whose label can never equal a case-normalised subject, or an `else if` whose predicate the arm above has already swallowed.
Method: Roslyn syntax + semantics: switch labels compared against the subject's own case normaliser, and if/else-if chains checked for a literal an earlier arm's containment test already swallows. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X13 · Undrained process stream10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a child process that has BOTH standard streams redirected drains both — reading one to the end while the other is never read deadlocks once the child fills the unread pipe.
Method: Roslyn syntax + semantics: ProcessStartInfo launches with both streams redirected, checked for a drain of each stream across the enclosing type. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `spawn` imported from `child_process` whose stdout and stderr are both pipes (no options, no `stdio`, or `stdio` of `'pipe'`), bound to a local that never leaves its scope, where exactly one of the two streams is read, the other never, and the child’s `close`/`exit` (or the read stream’s end) is awaited; a shell redirect in the call’s arguments or a `kill` of the child suppresses it. The same rule reads Python’s `subprocess.Popen`, Dart’s `Process.start`, Ruby’s `Open3.popen3`, and Scala’s JDK process starts (`new ProcessBuilder(…).start()` with no `redirectErrorStream`/`redirectError`/`redirectOutput`/`inheritIO`, `Runtime.getRuntime.exec`) where one of `getInputStream`/`getErrorStream` is read and the other never while `waitFor()` is called or the read stream is read to its end. Deterministic, provable per finding. Advisory.
Other · Security — Whether a hand-rolled public/private IP check can be walked past — a method that unwraps IPv4-mapped IPv6 but returns the opposite verdict for the same host written as IPv4-compatible, 6to4 or NAT64.
Method: Roslyn syntax + semantics: methods that unwrap IPv4-mapped IPv6 and hand-roll IPv4 range carve-outs, checked for whether the IPv6 branch also accounts for the IPv4-compatible, 6to4 and NAT64 embeddings. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X15 · Unvalidated length from an untrusted reader10.0 / 10Exemplary○ Nothing flagged
Other · Security — Whether a length read out of the stream being parsed is bounded before it is allocated or read — an unchecked count taken from the input lets the input choose the allocation.
Method: Roslyn syntax + semantics: integer lengths read from a BinaryReader and spent on a bulk read or an array allocation, checked for any comparison or bounding call on the value anywhere in the method. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a loop that shortens a string until it fits a length budget has a floor — one with none grinds the value down to the empty string, or past it into a negative-length `Substring`.
Method: Roslyn syntax + semantics: while/do loops whose body's only effect on a string is to drop its last character, checked for whether anything — a direct comparison on the length, a body guard, a break — bounds that length below. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `while`/`do` loop whose body’s one assignment to a value is `x = x.slice(0, -1)` or `x = x.slice|substring|substr(0, x.length - 1)`, driven by a condition that reads `x.length` only as a term of a larger expression — never compared directly, never tested for truthiness, and with no other read of `x` — and whose body has no `break`, `return`, `throw` or `if` naming `x`. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X17 · Uncapped recursion over a caller-supplied document10.0 / 10Exemplary○ Nothing flagged
Other · Security — Whether a walk that recurses through a JSON/XML tree handed in by its caller bounds how deep it will go — an uncapped walk lets the document's nesting choose the stack depth, and the resulting StackOverflowException cannot be caught.
Method: Roslyn syntax + semantics: methods that take a JSON/XML document node and call themselves with a child of it, reachable from an externally-callable member of the same type that accepts a document, checked for any depth parameter, descent counter or threaded arithmetic anywhere in the walk. On a repository with no .NET source it reads TypeScript off the engine’s own token stream (test, vendored, generated and minified paths and `.d.ts` not) with the same rule: a function or method with a parameter typed as a document value — `unknown`, `any`, `object`, `Record<string, unknown|any>`, a JSON alias (`JsonValue`, `JSONObject`, …) or a DOM node global the file does not rebind — that calls itself (bare, or through `this` for a method, or hands itself to a call over the value as in `value.map(walk)`) with something it took out of that value and never through an ancestor accessor such as `closest()` or `parentElement`, that is exported or reached from an exported function (a public method of the same exported class) taking such a value, and that names no depth, level, nesting, recursion, remaining or budget anywhere and threads no `+`/`-` arithmetic through a self-call. Plain JavaScript is not read: with no annotation nothing tells a parsed document from a tree the code built itself. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a type's disposal matches what it OWNS — releasing what it created, leaving alone what it was handed, and not declaring a finalizer for state that has nothing unmanaged to finalize.
Method: Roslyn syntax + semantics: every assignment to a disposable field is read to decide whether the type CREATED the value or was handed it, and the type's disposal is checked against that answer — an injected interface it disposes, a value it constructed and never releases, a finalizer on a type holding nothing unmanaged, and a disposable local whose every reference is a plain member read. A value handed to a container that disposes its contents (a parent control's `Controls` collection, a component `IContainer`) is released by that container and is not reported; generated code is out of population. On a repository with no .NET source the same ownership questions are read in JavaScript/TypeScript off the engine’s own token stream (test, vendored, generated and minified paths not): a class declaring `dispose()`, `[Symbol.dispose]()` or `[Symbol.asyncDispose]()` that disposes a field it was handed through a constructor parameter typed as a repository interface or resolved by a dependency-injection container; that assigns a field only ever from `new X(…)` of a disposable class and neither releases it anywhere in the class nor names it in its disposal member or a method that member calls, nor hands it to anything else; and a `const`/`let` local built from literals only whose every reference opens a statement operating on a non-release member of it. A class is disposable when every repository declaration of its name declares or inherits a disposal member, or when it is a documented library disposable (`vscode` EventEmitter, CancellationTokenSource and Disposable; three.js geometries, materials, textures, render targets, renderers, controls and composers). The finalizer arm has no JavaScript counterpart: a class cannot declare one. Dart is read for the owned-and-never-released arm: a Flutter `State` (or a class declaring `dispose()`/`close()`) whose library-private field is written only with direct creations of a framework controller, `FocusNode`, `StreamController` or periodic `Timer` (or a `.listen(…)` into a field declared `StreamSubscription`), which nothing in the class or its library releases (`dispose`/`close`/`cancel`) and which is never handed on except as a named argument. Ruby is read for the owned-and-never-released arm and the abandoned-local arm: a class declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose instance variable is written only with a blockless core descriptor creation (`File.open`/`new`, `Tempfile`, `Dir.open`, `IO.popen`, the `socket` and `openssl` socket classes) that no method of the class closes and that is never handed on (passed, returned, stored, exposed by `attr_reader`, delegated) — a class whose superclass or mixin lies outside the repository is not judged — and a blockless creation read through and dropped (`File.open(path).read`) or held in a local that is never closed, returned, passed or stored (a `&:read` block-pass, an `autoclose: false` borrow and a `fileno` hand-over are not abandonment). PHP is read for the same two arms: a class (not a trait, and not one using a trait) declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose `private` property (or a `final` class's `protected` one) is written only with a direct core `fopen`, `tmpfile`, `popen`, `proc_open`, `fsockopen`, `stream_socket_client`/`server` or `opendir` that nothing in the class closes (`fclose`, `pclose`, `closedir`, `unset`, a reset to `null`) and that is never handed on, and a handle held in a function's local, or read through as the argument of a reader, that is never closed, returned, passed, captured or stored; a `php://` stream, `curl_init`, `SplFileObject`, `PDO` and a function the repository declares under the core name are not read. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a method that temporarily changes state belonging to the whole process — the working directory, an environment variable — puts it back on EVERY path: a restore reached only when nothing throws leaks the change to the rest of the process.
Method: Roslyn syntax + semantics: method bodies that write the process working directory or an environment variable and write it back in the same body, checked for whether that restore sits in a `finally`/`catch` or only on the straight-line path. On a repository with no .NET source the same rule reads production JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not): `process.chdir`, `process.env.NAME =`/`["NAME"] =` and `delete process.env.NAME`, and Deno’s `Deno.chdir`/`Deno.env.set`/`Deno.env.delete`, paired per function body (a nested function or arrow is its own body, and module top-level code is none), where the last write puts back a local the body captured from the same global or deletes a variable the first write set, with at least one statement between them; a write in a `catch`/`finally` of that body silences it. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether an argument guard throws the exception its own condition describes — a guard that rejects a value for being EMPTY and reports it as `NullPointerException` (Java, Kotlin, Scala), `ArgumentError.notNull` (Dart) or `ArgumentNullException` (F#'s `nullArg`) tells the caller a parameter was null when it provably was not.
Method: Roslyn syntax: `throw new ArgumentNullException(nameof(p))` statements controlled by an `if`, whose condition is read for a test that is true of a NON-null `p` — an emptiness test that dereferences it (`p.Count == 0`, `!p.Any()`) or a BCL predicate documented true of the empty value (`string.IsNullOrEmpty(p)`). Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a `when` guard is free of side effects — a guard that increments a counter or assigns while deciding whether its arm matches applies that change during PATTERN MATCHING, on an arm that may not be selected, and skips it entirely when a short-circuit to its left answers first.
Method: Roslyn syntax: `when` guards on case labels and switch-expression arms, read for a mutation (`++`/`--`/assignment) sitting in a position the guard's own `&&`/`||`/`??`/`?:`/`?.` can skip. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a method that TAKES a lock or semaphore and gives it back from a flag-guarded `finally` returns the value that flag implies — reporting success while the guard hands the primitive back admits a second caller the exclusion was there to keep out, and reporting failure while the guard keeps it leaves nothing to ever give it back.
Method: Roslyn syntax: `try` statements whose `finally` releases a synchronisation primitive under a bare local-bool guard, where the method also TOOK that same primitive before the `try`, checked for a `return` of a bool literal whose value disagrees with the flag state the method's own straight-line assignments put it in. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether the work a diagnostic log line costs is paid only when that line is wanted — C# evaluates a call's arguments BEFORE the call, so a trace/debug message joined or projected out of a collection is built in full on every pass, and then discarded by a sink the shipped configuration leaves switched off.
Method: Roslyn syntax: log calls at a diagnostic level (a `Log`-prefixed method naming Trace/Debug/Verbose, or a bare `Debug`/`Trace`/`Verbose` on a receiver named for a logger), whose argument list is read for a call whose cost scales with a sequence — a LINQ operator, a materialisation, `string.Join`, a serializer — with no enclosing level check or conditional-compilation region. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `debug`/`trace`/`verbose` call on a receiver named for a logger, or a `log`-prefixed method naming the level, whose argument calls an array operator (`map`/`filter`/`reduce`/`sort`/…), `Array.from`, `Object.keys/values/entries`, `JSON.stringify`/`util.inspect` over anything but a literal, or an array `join` — outside any arrow or function passed as an argument, which the logger calls only when the level is on — with no enclosing `if`, `&&` or `?:` whose condition names a level, a level string, or the `NODE_ENV`/`__DEV__`/`DEV` build switch. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a value the caller is invited to supply is the value the type actually uses — a constructor parameter stored in a private field that nothing ever reads while the default it was given is spelled out a second time at the site that should have read it, a keyed lookup that falls back to a different setting than the one its key names while the same type falls back to the matching one for that same key, or a culture-sensitive parse given no format provider by a type that feeds its own settable culture to the same kind of parse elsewhere, or a number an entry point writes to standard output under the host's culture while the same entry point formats with the invariant culture elsewhere. Either way, every caller who supplies a value silently gets something else.
Method: Roslyn syntax: private instance fields of a non-partial type assigned in a constructor from one of its own parameters with a `??` fallback, checked for whether anything in the type body reads the field and whether that same fallback expression is spelled out again outside the constructor; and `??` fallbacks onto a member access from a lookup call carrying exactly one string literal, grouped by that key across the type and checked for a fallback member whose folded name disagrees with the key while a sibling site for the same key agrees with it. On a repository with no .NET source the first two arms read JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `#x`, `private` or `private` parameter-property instance field filled in the constructor from a parameter (or one member of one) through `??`/`||` or a parameter default, never read anywhere in the file by name, whose constructed default is spelled again in the class body; and `lookup("key") ?? s.member` grouped by key per class, or per module outside every class. The culture arm has no JavaScript counterpart: its parses take no locale. Deterministic, provable per finding. Advisory.
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.
Method: Roslyn syntax + semantics: `foreach` statements whose body calls a structural mutator (`Add`/`Remove`/`Clear`/`Insert`/…) on the very expression the loop is enumerating. Two arms. ARM A — the source is a concrete fragile BCL collection, or a live `Keys`/`Values` view over one, and the mutator resolves to that same collection's own member; concurrent and immutable collections and arrays are outside the population by construction, since their enumerators survive a structural change. ARM B — the source is an argument-less accessor CALL on a receiver whose body is in source: the accessor must return a stored field VERBATIM and a sibling member must structurally change that same field, both read off the implementations rather than from the members' names. A mutation the loop provably exits immediately after (`break`/`return`/`throw`/`goto`), or one written inside a nested loop or a lambda, is counted and never reported. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X28 · Index access outside its own emptiness guard10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a condition that tests a value for emptiness indexes that same value only where the test holds — an `||` written one parenthesis too far to the left leaves an index access outside the guard beside it, so the empty case the guard exists to anticipate reaches the index and throws.
Method: Roslyn syntax only, no semantic model: the OUTERMOST `&&`/`||` of every boolean condition, read for a symbol the condition tests for emptiness (`string.IsNullOrEmpty`/`IsNullOrWhiteSpace`, a `Length`/`Count` comparison against a literal, `Any()`, a `Length`/`Count` pattern, or a comparison against `""`) and ALSO indexes. Each `symbol[...]` access is placed by a boolean-reachability walk from the access up to the outermost connective: an access is COVERED when some enclosing step has it in the right operand and the left operand, under the truth value that step forces, proves the symbol non-empty — a recursion over `&&`/`||` whose true- and false-directions are asymmetric. A finding needs BOTH an uncovered access and a covered one on the same symbol in the same condition, which is the agreeing twin that separates a misplaced parenthesis from an unrelated length test. Bare index accesses with no emptiness test in the condition are neither counted nor reported; a non-identifier receiver and a lambda nested inside the condition are outside the population. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X29 · Per-element action decided by a fixed element10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a decision taken once per element is taken ABOUT that element — a test inside a counted loop that reads a fixed subscript of the very collection its guarded statement indexes by the loop variable applies element zero's answer to all of them, so the elements that differ from it are all handled wrongly, and in the same direction.
Method: Roslyn syntax only, no semantic model: every `for` statement declaring exactly ONE loop variable, and every `if` inside its body that is not under a nested loop or a lambda. A site enters the population when the `if`’s condition never mentions the loop variable while the statement it guards indexes some collection by that variable ALONE (`c[i]`; `c[i + 1]` and `c[i, j]` are outside it). A finding additionally needs the AGREEING TWIN at the same-collection grain: the condition must read THAT SAME collection at a subscript that does not move — written into the condition, or reached through a local declared BEFORE the loop, so an alias bound inside the body is not followed. Both collection expressions must be simple identifiers. On a repository with no .NET source the same rule reads JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `for (let|var|const x = …; …; …)` with one declarator and a braced body, an alias followed only when it is declared before the loop in a block that encloses it and never assigned inside the loop. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether exceptions are handled rather than silently swallowed or rethrown with lost stack traces.
Method: Roslyn syntax scan: every catch clause counted; empty catches and bare rethrows flagged. Population is all catch clauses, not estimated. Deterministic, hard fact.
`catch (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. (×30) — lib/codegen/c/curl.dart:183, lib/codegen/csharp/rest_sharp.dart:181, lib/codegen/csharp/http_client.dart:158, …
`catch (_)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. (×8) — lib/dashbot/providers/chat_viewmodel.dart:46, lib/dashbot/providers/chat_viewmodel.dart:386, lib/dashbot/providers/chat_viewmodel.dart:415, …
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. (×2) — lib/dashbot/providers/chat_viewmodel.dart:444, lib/dashbot/providers/chat_viewmodel.dart:911
What to do
Swallowed exception (caught, then discarded)
Do you agree with this assessment?
X30 · Support guard that admits what it rejects10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a guard written as a NEGATED `||` says what its author meant — `!(a || b || x != k)` is `!a && !b && x == k` by De Morgan, so a bail-out that mixes capabilities the code needs with a fault it refuses turns inside out: it fires only where the capabilities are ABSENT, and lets every value the fault term names walk straight into the body that cannot handle it.
Method: Roslyn syntax only, no semantic model: every logical-not whose operand is a parenthesised `||` chain of two or more disjuncts, flattened (a left-nested `a || b || c` read once would see `(a || b)` as one disjunct). A site enters the population on that shape alone. A finding additionally needs the disjuncts to DISAGREE in polarity: at least one bare boolean read — an identifier or member access, never an invocation, which is a predicate rather than a capability flag — and at least one `x != <constant>`, the only form that negates into an exact-value pin (`== null` negates into a looser requirement and is outside the fault set). Consistently-polarised disjunctions, all-fault or all-capability, are counted and never reported; a negated `&&` is outside the population entirely. No same-receiver gate: it was measured to cost a real defect and remove no false positive. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether Dart's sound null safety is on and is not undermined by null assertions — a package whose `environment: sdk:` lower bound is 2.12 or above is null safe, so `String` cannot hold null and `String?` must be checked before use, and each postfix `!` is a run-time `Null check operator used on a null value` the author has told the analyzer cannot happen.
Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.
Do you agree with this assessment?
Reference — by lens
The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.
Unscored — 2 check(s) recorded observations but carry no score
These checks ran and found something, but they do not carry a score — either by design (an advisory check reports evidence rather than grading it) or because they could not be scored here. They are excluded from the score for that reason, not because there was nothing to see.
X10 Duplicated predicate — 15 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X7 Silent fallback defaults — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 4 control(s) we could not find positive evidence for
These checks grade a working control, and the repository shows no evidence of one. That is deliberately not scored as a zero: a repository cannot show an ops runbook, a database TTL or an infrastructure-side audit log, so absence of evidence here is not evidence the control is missing. It is also not a statement that the check is irrelevant to this codebase — the thing it grades applies; we just could not see it. Excluded from the score either way.
C3 Audit Trail — Not assessed: this repository stores data through 'package:hive_ce_flutter' (lib/services/hive_services.dart:2) but declares no persisted model this check reads (Drift tables, ObjectBox/Floor @Entity, Isar @collection and Hive @HiveType classes, Serverpod table models). Personal data may be written through raw SQL or a hosted backend, so whether its changes need an audit trail could not be established, and the trail's absence is not scored.
C4 Data Retention — Not assessed: this repository stores data through 'package:hive_ce_flutter' (lib/services/hive_services.dart:2) but declares no persisted model this check reads (Drift tables, ObjectBox/Floor @Entity, Isar @collection and Hive @HiveType classes, Serverpod table models). Personal data may be written through raw SQL or a hosted backend, so whether a retention limit applies here could not be established, and its absence is not scored.
C5 Data-Subject Rights — Not assessed: this repository stores data through 'package:hive_ce_flutter' (lib/services/hive_services.dart:2) but declares no persisted model this check reads (Drift tables, ObjectBox/Floor @Entity, Isar @collection and Hive @HiveType classes, Serverpod table models). Personal data may be written through raw SQL or a hosted backend, so whether data-subject rights apply here could not be established, and their absence is not scored.
P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 53 check(s) not relevant to this codebase
These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.
AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
AX2 Stateful singletons — Not applicable: Dart isolates share no mutable memory, so no two requests write one object at the same instant.
AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX6 Interface segregation — not assessed — interface segregation is computed over a type surface that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
AX8 Test isolation — no test/production split to check
AXB1 Runtime evidence locked — no reproducible boot — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
C1 Data Protection — Not assessed: this repository stores data through 'package:hive_ce_flutter' (lib/services/hive_services.dart:2) but declares no persisted model this check reads (Drift tables, Isar/ObjectBox/Floor/Hive entities, Serverpod table models). Personal data may be written through raw SQL or a hosted backend, so the absence of a personal-data field here is not evidence that none is stored, and encryption at rest is not scored over a subject that could not be established.
C2 Access Controls — No access-control surface detected in the analyzed source — this repository stands up no server another machine can reach (no HttpServer or shelf server bound beyond loopback, no dart_frog route, no Serverpod endpoint, no Conduit, Alfred or Angel application) and keeps no data in a hosted backend. Access control is therefore N/A here — a Flutter app or pub package is authorized by the server it calls, not by itself; hiding a screen authorizes nothing. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
D10 Test Quality — ~79939 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
D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ projects each declaring an entity of their own. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
D24 Comment Value — No inline comments to assess — comment value is not applicable here.
D25 ADR Conformance — no ADRs to check
D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.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.
D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
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
D9 Test Distribution — Test source is 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 its unit/integration/BDD/E2E split couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
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, which this analysis does not build from source alone for this language. Reported as guidance rather than measured
ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the Dart source, so there is no service whose uptime a failing dependency could take down
P8 Schema migrations — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (lcov — `flutter test --coverage` (or `dart test --coverage=coverage` then `dart run coverage:format_coverage --lcov`)) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for classes extending benchmark_harness's `BenchmarkBase`, `AsyncBenchmarkBase` or `PerfBenchmarkBase` (directly or through a base of your own), `benchmark(…)` calls under the pub `benchmark` package, Flutter's `benchmarkWidgets`, `watchPerformance` or `traceAction` in a test importing flutter_test, integration_test or flutter_driver, or benchmark_harness, benchmark or web_benchmarks in a pubspec.yaml, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
X2 Cancellation propagation — 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
X24 Document value interpolated into markup unescaped — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X26 Unsynchronised callback handoff — Not applicable: this check looks for a collection written by a callback on one thread while the body waiting on it touches it on another, and in this repository's languages no collection is reachable from two threads at once. Dart isolates share no mutable memory: a value sent to another isolate arrives as a copy, and callbacks within one isolate run one at a time on its event loop, so no collection is reachable from two threads at once. Not a gap in the analyzer and not a finding about your code.
X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
X4 Structured logging — This check asks whether log calls keep a message's values apart from its text, which needs a logger that can carry them as fields. This repository's Dart was read, and it logs through none: package:logging, package:logger, talker and dart:developer take one finished message and no template arguments or fields (as log4net does in C#), so an interpolated message there loses nothing the API could have kept. Sentry's structured logs (`Sentry.logger`) would be judged.
X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
The findings behind the scores, grouped by severity, then by dimension and kind. The high-severity issues are enumerated in full below; items per group are capped at 25 with any overflow stated explicitly per group, never silently truncated. The complete machine-readable list of every finding (all severities) is the companion findings.md in this report's bundle.
Boundary-crossing change coupling: editor_request.dart ↔ tab_label.dart lib/screens/home_page/editor_pane/editor_request.dart:1— `lib/screens/home_page/editor_pane/editor_request.dart` (context screens) and `lib/widgets/tab_label.dart` (context widgets) sit in DIFFERENT parts of the tree yet change together 73% of the time (8 of the 11 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 8 shared commits counted here, the most recent 3 are `15ad5976` feat: environment editor (at that commit the file was still `lib/widgets/tabs.dart`); `b0c4f714` wip: desktop responsiveness (at that commit the file was still `lib/widgets/tabs.dart`); `5c654ffd` wip: desktop responsiveness (at that commit the file was still `lib/widgets/tabs.dart`) — run `git show` on any of them.
Boundary-crossing change coupling: collection_pane.dart ↔ tab_label.dart lib/screens/home_page/collection_pane.dart:1— `lib/screens/home_page/collection_pane.dart` (context screens) and `lib/widgets/tab_label.dart` (context widgets) sit in DIFFERENT parts of the tree yet change together 73% of the time (8 of the 11 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 8 shared commits counted here, the most recent 3 are `b0c4f714` wip: desktop responsiveness (at that commit the file was still `lib/widgets/tabs.dart`); `5c654ffd` wip: desktop responsiveness (at that commit the file was still `lib/widgets/tabs.dart`); `6b2b2789` refactor: review changes (at that commit the file was still `lib/widgets/tabs.dart`) — run `git show` on any of them.
Boundary-crossing change coupling: settings_page.dart ↔ tab_label.dart lib/screens/settings_page.dart:1— `lib/screens/settings_page.dart` (context screens) and `lib/widgets/tab_label.dart` (context widgets) sit in DIFFERENT parts of the tree yet change together 64% of the time (7 of the 11 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `b0c4f714` wip: desktop responsiveness (at that commit the file was still `lib/widgets/tabs.dart`); `5c654ffd` wip: desktop responsiveness (at that commit the file was still `lib/widgets/tabs.dart`); `6b2b2789` refactor: review changes (at that commit the file was still `lib/widgets/tabs.dart`) — run `git show` on any of them.
Boundary-crossing change coupling: his_request_pane.dart ↔ history_utils.dart lib/screens/history/history_widgets/his_request_pane.dart:1— `lib/screens/history/history_widgets/his_request_pane.dart` (context screens) and `lib/utils/history_utils.dart` (context utils) sit in DIFFERENT parts of the tree yet 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) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `001567bd` feat: offer DashBot code generation where native codegen is missing (…; `d4a96965` add grpc support to request history; `a988a4e3` feat(mqtt): add MQTT support to request history — run `git show` on any of them.
Boundary-crossing change coupling: collection_pane.dart ↔ splitview_drawer.dart lib/screens/home_page/collection_pane.dart:1— `lib/screens/home_page/collection_pane.dart` (context screens) and `lib/widgets/splitview_drawer.dart` (context widgets) sit in DIFFERENT parts of the tree yet 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) — 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 `3c710d12` Add extensions in design system; `7fcfe4f8` feat: environment pane (at that commit the file was still `lib/widgets/splitviews.dart`); `09639cdf` fix: migrate to native drawer (at that commit the file was still `lib/widgets/splitviews.dart`) — run `git show` on any of them.
Boundary-crossing change coupling: collection_providers.dart ↔ response_body.dart lib/providers/collection_providers.dart:1— `lib/providers/collection_providers.dart` (context providers) and `lib/widgets/response_body.dart` (context widgets) sit in DIFFERENT parts of the tree yet change together 50% of the time (7 of the 14 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `7b7daa7d` Add AI request model support and improve type handling; `30075a6d` genai: Minor Refactoring and Corrections; `e06bddca` SSEDislay: SelectedModel provided via parameter & StreamingFixes — run `git show` on any of them.
Boundary-crossing change coupling: collection_providers.dart ↔ realtime_event_stream_view.dart lib/providers/collection_providers.dart:1— `lib/providers/collection_providers.dart` (context providers) and `lib/screens/home_page/editor_pane/details_card/realtime_event_stream_view.dart` (context screens) sit in DIFFERENT parts of the tree yet change together 50% of the time (5 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — 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 5 shared commits counted here, the most recent 3 are `ad7444d1` state update fix + filter topic UI fix; `e8ae5216` add gRPC provider logic and request/response UI; `a0031720` simplify websocket message view and apply heartbeat interval live — run `git show` on any of them.
Boundary-crossing change coupling: environment_page.dart ↔ card_sidebar_request.dart lib/screens/envvar/environment_page.dart:1— `lib/screens/envvar/environment_page.dart` (context screens) and `lib/widgets/card_sidebar_request.dart` (context widgets) sit in DIFFERENT parts of the tree yet change together 50% of the time (5 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — 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 5 shared commits counted here, the most recent 3 are `631b6b22` fix: ui corrections (at that commit the file was still `lib/widgets/cards.dart`); `7fcfe4f8` feat: environment pane (at that commit the file was still `lib/widgets/cards.dart`); `8228b28a` wip: environment pane (at that commit the file was still `lib/widgets/cards.dart`) — run `git show` on any of them.
Boundary-crossing change coupling: ui_utils.dart ↔ texts.dart lib/utils/ui_utils.dart:1— `lib/utils/ui_utils.dart` (context utils) and `lib/widgets/texts.dart` (context widgets) sit in DIFFERENT parts of the tree yet change together 50% of the time (5 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — 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 5 shared commits counted here, the most recent 3 are `e8ae5216` add gRPC provider logic and request/response UI; `c9f8603f` feat(ws): add WebSocket UI styles and URL card behavior; `d923996d` AIProviderSelector Impl & AI Models added to RequestModel — run `git show` on any of them.
Orphaned knowledge lib/utils/js_utils.dart:1— No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
Orphaned knowledge packages/json_explorer/lib/src/json_explorer.dart:1— No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
Orphaned knowledge packages/json_explorer/lib/src/json_explorer_store.dart:1— No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
TLS certificate validation disabled packages/better_networking/lib/services/http_client_manager.dart:8— `badCertificateCallback` returning `true` is set on a TLS client, so every peer certificate is accepted — including one an attacker presents. Chain, expiry, revocation and hostname are all skipped, so an attacker on the network path can present any certificate and read or rewrite the traffic — the connection is encrypted to the attacker, not to the intended host. Remove the callback so `dart:io` validates the peer. If the server presents a self-signed or privately-issued certificate, trust THAT issuer rather than every certificate: load its CA into a `SecurityContext` (`setTrustedCertificatesBytes`) and pass it as `HttpClient(context: …)` / `SecureSocket.connect(…, context: …)`, which keeps the chain and hostname checks on. A callback that must exist should compare the presented certificate with a pinned fingerprint, never return `true`.
Swallowed exception (caught, then discarded) lib/codegen/c/curl.dart:183— `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/codegen/csharp/rest_sharp.dart:181— `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/codegen/csharp/http_client.dart:158— `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/codegen/dart/http.dart:25— `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/codegen/dart/dio.dart:23— `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/codegen/go/http.dart:173— `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/codegen/java/unirest.dart:163— `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/codegen/java/okhttp.dart:170— `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/codegen/java/httpclient.dart:191— `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/codegen/java/async_http_client.dart:217— `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/codegen/js/fetch.dart:132— `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/codegen/js/axios.dart:121— `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/codegen/julia/http.dart:163— `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/codegen/kotlin/okhttp.dart:182— `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/codegen/others/har.dart:16— `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/codegen/others/curl.dart:71— `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/codegen/php/http_plug.dart:184— `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/codegen/php/guzzle.dart:144— `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/codegen/php/curl.dart:174— `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/codegen/python/requests.dart:197— `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/codegen/python/http_client.dart:187— `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/codegen/ruby/net_http.dart:129— `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/codegen/ruby/faraday.dart:171— `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/codegen/rust/ureq.dart:210— `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/codegen/rust/reqwest.dart:176— `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.
MethodTooLong: SDUIWidget.build doc/gsoc/2025/codes/example4.dart:22— MethodTooLong — build runs 502 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 402 over it, 5.02× 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: CollectionStateNotifier.sendRequest lib/providers/collection_providers.dart:1047— MethodTooLong — sendRequest runs 423 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 323 over it, 4.23× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: PromptBuilder.buildTaskPrompt lib/dashbot/services/agent/prompt_builder.dart:499— MethodTooLong — buildTaskPrompt runs 380 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 280 over it, 3.80× 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: _EditGrpcRequestPaneState.build lib/screens/home_page/editor_pane/details_card/request_pane/request_pane_grpc.dart:36— MethodTooLong — build runs 351 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 251 over it, 3.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: _DashbotHomePageState.build lib/dashbot/pages/dashbot_home_page.dart:23— MethodTooLong — build runs 315 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 215 over it, 3.15× 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: CollectionStateNotifier._connectGrpc lib/providers/collection_providers.dart:1839— MethodTooLong — _connectGrpc runs 257 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 157 over it, 2.57× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: _EditMQTTRequestPaneState._buildSettingsTab lib/screens/home_page/editor_pane/details_card/request_pane/mqtt/mqtt_request_pane.dart:322— MethodTooLong — _buildSettingsTab runs 255 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 155 over it, 2.55× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: SettingsPage.build lib/screens/settings_page.dart:16— 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: HistoryRequestPane.build lib/screens/history/history_widgets/his_request_pane.dart:19— MethodTooLong — build runs 219 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 119 over it, 2.19× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: DashbotTaskButtons.build lib/dashbot/widgets/dashbot_task_buttons.dart:16— MethodTooLong — build runs 192 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 92 over it, 1.92× 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: _OAuth2FieldsState.build lib/screens/common_widgets/auth/oauth2_field.dart:111— MethodTooLong — build runs 191 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 91 over it, 1.91× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: SDUIWidget.build doc/gsoc/2025/codes/example5.dart:22— MethodTooLong — build runs 177 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 77 over it, 1.77× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: ChatViewmodel.sendMessage lib/dashbot/providers/chat_viewmodel.dart:57— MethodTooLong — sendMessage runs 173 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 73 over it, 1.73× 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: CollectionStateNotifier._connectWebSocket lib/providers/collection_providers.dart:740— MethodTooLong — _connectWebSocket runs 173 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 73 over it, 1.73× 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: EditMQTTTopicsState.build lib/screens/home_page/editor_pane/details_card/request_pane/mqtt/mqtt_request_topics.dart:57— MethodTooLong — build runs 168 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 68 over it, 1.68× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: _WsMessageEditorState.build lib/screens/home_page/editor_pane/details_card/request_pane/ws/ws_message_editor.dart:123— MethodTooLong — build runs 166 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 66 over it, 1.66× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: CollectionStateNotifier.update lib/providers/collection_providers.dart:309— MethodTooLong — update runs 160 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 60 over it, 1.60× 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: _RealtimeEventStreamViewState.build lib/screens/home_page/editor_pane/details_card/realtime_event_stream_view.dart:64— MethodTooLong — build runs 155 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 55 over it, 1.55× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: DashbotWindow.build lib/dashbot/dashbot_dashboard.dart:19— MethodTooLong — build runs 147 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 47 over it, 1.47× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: EditRequestHeadersState.build lib/screens/home_page/editor_pane/details_card/request_pane/request_headers.dart:39— MethodTooLong — build runs 144 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 44 over it, 1.44× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: EditRequestURLParamsState.build lib/screens/home_page/editor_pane/details_card/request_pane/request_params.dart:39— MethodTooLong — build runs 141 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 41 over it, 1.41× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: _FormDataBodyState.build lib/screens/home_page/editor_pane/details_card/request_pane/request_form_data.dart:37— MethodTooLong — build runs 140 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 40 over it, 1.40× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: EditGrpcRequestMetadataState.build lib/screens/home_page/editor_pane/details_card/request_pane/request_metadata_grpc.dart:46— MethodTooLong — build runs 136 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 36 over it, 1.36× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: EditEnvironmentVariablesState.build lib/screens/envvar/editor_pane/variables_pane.dart:47— MethodTooLong — build runs 125 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 25 over it, 1.25× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: _JwtAuthFieldsState.build lib/screens/common_widgets/auth/jwt_auth_fields.dart:50— MethodTooLong — build runs 123 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 23 over it, 1.23× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
TodoComment integration_test/desktop/his_request_test.dart:48— /// TODO: Having overflowing number of cards causes the test to fail — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment integration_test/mobile/his_request_test.dart:62— /// TODO: Having overflowing number of cards causes the test to fail — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment integration_test/mobile/env_manager_test.dart:22— // TODO: Hover on variable doesn't work in test for long URLs — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment integration_test/mobile/env_manager_test.dart:87— // TODO: Unable to get Popover to show on mobile — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment integration_test/mobile/env_manager_test.dart:145— // TODO: Unable to get Popover to show on mobile — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment lib/consts.dart:487— // TODO: CodeField widget does not allow this hint. To be solved. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment lib/dashbot/services/openapi_import_service.dart:157— /// TODO: Remove this workaround once openapi_spec package fixes — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment lib/dashbot/services/openapi_import_service.dart:237— // TODO: Extract form field names from schema if available — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment lib/dashbot/widgets/openapi_operation_picker_dialog.dart:71— // TODO: Create a common Search field widget — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment lib/importer/import_dialog.dart:13— // TODO: The dialog must have a feature to paste contents in a text field — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment lib/screens/common_widgets/code_pane.dart:39— // TODO: Add AI Request Codegen — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment lib/screens/common_widgets/code_pane.dart:44— // TODO: Add WebSocket Codegen — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment lib/screens/common_widgets/code_pane.dart:75— // TODO: Add GraphQL Codegen — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment lib/screens/common_widgets/ai/dialog_add_ai_model.dart:40— // TODO: Add logic to add a new model — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment lib/screens/common_widgets/ai/ai_model_selector_dialog.dart:55— // TODO: Add update model logic — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment lib/screens/common_widgets/ai/ai_model_selector_dialog.dart:114— // TODO: Add update model logic — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment lib/screens/home_page/editor_pane/details_card/response_pane.dart:9— //TODO : A better way to handle the logic for showing different panes — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment lib/screens/home_page/editor_pane/url_card/url_text_field.dart:10— //TODO : A better way to use hintText for each protocol — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment lib/services/connection_manager.dart:23— /// TODO: it should also be usable for other Protocols — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment lib/utils/js_utils.dart:346— // TODO: Add helpers for request.formData if needed (similar to headers/params) — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment lib/widgets/editor_json.dart:141— // TODO: Show error message in Global Status bar — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment lib/widgets/editor_code.dart:39— // TODO: Fix numbers size — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment packages/apidash_design_system/lib/widgets/list_tile.dart:36— // TODO: Handle this case. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment packages/apidash_design_system/lib/widgets/list_tile.dart:38— // TODO: Handle this case. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment packages/better_networking/lib/utils/http_request_utils.dart:101— //TODO: TAKE A LOOK — 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.
Change coupling: navbar.dart ↔ page_base.dart lib/screens/mobile/navbar.dart:1— `lib/screens/mobile/navbar.dart` and `lib/screens/mobile/widgets/page_base.dart` change together 68% of the time (13 of the 19 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 13 shared commits counted here, the most recent 3 are `b4827dc2` Update screens UI as per the latest Material 3 colors; `126de74c` fix: bottom navbar; `09639cdf` fix: migrate to native drawer — run `git show` on any of them.
Change coupling: api_key_auth_fields.dart ↔ jwt_auth_fields.dart lib/screens/common_widgets/auth/api_key_auth_fields.dart:1— `lib/screens/common_widgets/auth/api_key_auth_fields.dart` and `lib/screens/common_widgets/auth/jwt_auth_fields.dart` change together 58% of the time (7 of the 12 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency between them. They sit in the same directory, but in this ecosystem each file is its own module — a sibling reference still needs an import — so the missing import edge is real: the coupling runs through shared behaviour, not a declared dependency. If they duplicate structure, extract the common part into one unit; otherwise the coupling is hidden and worth breaking. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `9bc2ac21` feat: replace Column with ListView in auth fields; `127b2c1e` fix: disable onChanged for read-only auth fields; `e838654b` feat: enhance authentication fields with additional info — run `git show` on any of them.
Change coupling: dashbot_chat_page.dart ↔ chat_viewmodel.dart lib/dashbot/pages/dashbot_chat_page.dart:1— `lib/dashbot/pages/dashbot_chat_page.dart` and `lib/dashbot/providers/chat_viewmodel.dart` change together 58% of the time (7 of the 12 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) 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 `b840ba44` feat: create a dedicated provider for dashbot navigation (at that commit the files were still `lib/dashbot/features/chat/view/pages/dashbot_chat_page.dart` and `lib/dashbot/features/chat/viewmodel/chat_viewmodel.dart`); `e1481e8d` feat: send a user message for each task (at that commit the files were still `lib/dashbot/features/chat/view/pages/dashbot_chat_page.dart` and `lib/dashbot/features/chat/viewmodel/chat_viewmodel.dart`); `fc6abd04` feat: add clear chat functionality (at that commit the files were still `lib/dashbot/features/chat/view/pages/dashbot_chat_page.dart` and `lib/dashbot/features/chat/viewmodel/chat_viewmodel.dart`) — run `git show` on any of them.
Change coupling: app.dart ↔ tab_label.dart lib/app.dart:1— `lib/app.dart` and `lib/widgets/tab_label.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 `b0c4f714` wip: desktop responsiveness (at that commit the file was still `lib/widgets/tabs.dart`); `5c654ffd` wip: desktop responsiveness (at that commit the file was still `lib/widgets/tabs.dart`); `6b2b2789` refactor: review changes (at that commit the file was still `lib/widgets/tabs.dart`) — run `git show` on any of them.
Change coupling: intro_message.dart ↔ tab_label.dart lib/widgets/intro_message.dart:1— `lib/widgets/intro_message.dart` and `lib/widgets/tab_label.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 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 6 shared commits counted here, the most recent 3 are `b0c4f714` wip: desktop responsiveness (at that commit the file was still `lib/widgets/tabs.dart`); `5c654ffd` wip: desktop responsiveness (at that commit the file was still `lib/widgets/tabs.dart`); `6b2b2789` refactor: review changes (at that commit the file was still `lib/widgets/tabs.dart`) — run `git show` on any of them.
Change coupling: dashbot_dashboard.dart ↔ dashbot_home_page.dart lib/dashbot/dashbot_dashboard.dart:1— `lib/dashbot/dashbot_dashboard.dart` and `lib/dashbot/pages/dashbot_home_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 `b840ba44` feat: create a dedicated provider for dashbot navigation (at that commit the file was still `lib/dashbot/features/home/view/pages/dashbot_home_page.dart`); `5149179d` feat: hide dashbot fab when dashbot is open (at that commit the file was still `lib/dashbot/features/home/view/pages/home_page.dart`); `1a26380b` feat: rearrange dashbot home buttons (at that commit the file was still `lib/dashbot/features/home/view/pages/home_page.dart`) — run `git show` on any of them.
Change coupling: environments_pane.dart ↔ dashboard.dart lib/screens/envvar/environments_pane.dart:1— `lib/screens/envvar/environments_pane.dart` and `lib/screens/mobile/dashboard.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 `3c710d12` Add extensions in design system; `dace4952` fix: ui tests; `631b6b22` fix: ui corrections — run `git show` on any of them.
Change coupling: dashbot_dashboard.dart ↔ dashbot_tab.dart lib/dashbot/dashbot_dashboard.dart:1— `lib/dashbot/dashbot_dashboard.dart` and `lib/dashbot/dashbot_tab.dart` change together 50% of the time (6 of the 12 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) 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 6 shared commits counted here, the most recent 3 are `b840ba44` feat: create a dedicated provider for dashbot navigation; `8cd99236` feat: integrate chat state management for dynamic navigation in dashbot; `e3fc474c` feat: implement reactive switching in dashbot home and default page — run `git show` on any of them.
Change coupling: request_pane_graphql.dart ↔ request_pane_rest.dart lib/screens/home_page/editor_pane/details_card/request_pane/request_pane_graphql.dart:1— `lib/screens/home_page/editor_pane/details_card/request_pane/request_pane_graphql.dart` and `lib/screens/home_page/editor_pane/details_card/request_pane/request_pane_rest.dart` change together 50% of the time (6 of the 12 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) 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 6 shared commits counted here, the most recent 3 are `8b85d469` view code button update; `6c5862cd` refactor: move authModel to HttpRequestModel; `3903277a` chore: resolve merge conflicts — run `git show` on any of them.
Change coupling: environment_page.dart ↔ navbar.dart lib/screens/envvar/environment_page.dart:1— `lib/screens/envvar/environment_page.dart` and `lib/screens/mobile/navbar.dart` change together 50% of the time (5 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 5 shared commits counted here, the most recent 3 are `dace4952` fix: ui tests; `7fcfe4f8` feat: environment pane; `8228b28a` wip: environment pane — run `git show` on any of them.
Change coupling: realtime_event_stream_view.dart ↔ request_pane_ws.dart lib/screens/home_page/editor_pane/details_card/realtime_event_stream_view.dart:1— `lib/screens/home_page/editor_pane/details_card/realtime_event_stream_view.dart` and `lib/screens/home_page/editor_pane/details_card/request_pane/request_pane_ws.dart` change together 50% of the time (5 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 5 shared commits counted here, the most recent 3 are `c952f691` address review comments; `e00db8b7` fixing state update problems; `87314849` history persistance and UI updates — run `git show` on any of them.
Duplicated block (10 lines × 2) lib/codegen/java/okhttp.dart:118— lib/codegen/java/okhttp.dart:118-127 | lib/codegen/kotlin/okhttp.dart:111-120 — `lib/codegen/java/okhttp.dart` and `lib/codegen/kotlin/okhttp.dart` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 4 separate duplicated blocks between them, totalling at least 50 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (10 lines × 2) lib/dashbot/providers/chat_viewmodel.dart:456— lib/dashbot/providers/chat_viewmodel.dart:456-465 | lib/dashbot/services/actions/request_apply_service.dart:233-242 — before extracting anything, compare `lib/dashbot/providers/chat_viewmodel.dart` and `lib/dashbot/services/actions/request_apply_service.dart` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 51 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (10 lines × 2) lib/providers/collection_providers.dart:139— lib/providers/collection_providers.dart:139-148 | lib/providers/collection_providers.dart:156-165 — 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/providers/collection_providers.dart:2137— lib/providers/collection_providers.dart:2137-2146 | lib/providers/collection_providers.dart:2187-2196 — 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/services/connection_manager.dart:342— lib/services/connection_manager.dart:342-352 | lib/services/connection_manager.dart:438-447 — 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/services/grpc_reflection_service.dart:446— lib/services/grpc_reflection_service.dart:446-455 | lib/services/grpc_reflection_service.dart:483-492 — 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/services/agentic_services/agents/intermediate_rep_gen.dart:19— lib/services/agentic_services/agents/intermediate_rep_gen.dart:19-28 | lib/services/agentic_services/agents/stac_to_flutter.dart:19-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 (10 lines × 2) lib/widgets/previewer_json.dart:392— lib/widgets/previewer_json.dart:392-401 | packages/json_explorer/example/lib/main.dart:354-363 — 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.
Hotspot: lib/providers/collection_providers.dart lib/providers/collection_providers.dart:1047— lib/providers/collection_providers.dart changed 15 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 52 in CollectionStateNotifier.sendRequest at line 1047. 5 of those changes were fix/bug commits, and the other 10 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-13..2026-10-11, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-13 00:07:16 +05:30' --until='2026-10-11 00:07:16 +05:30' --full-history --no-merges -- lib/providers/collection_providers.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/screens/history/history_widgets/his_request_pane.dart lib/screens/history/history_widgets/his_request_pane.dart:19— lib/screens/history/history_widgets/his_request_pane.dart changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 34 in HistoryRequestPane.build at line 19. 1 of those changes was a fix/bug commit, and the other 6 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-13..2026-10-11, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-13 00:07:16 +05:30' --until='2026-10-11 00:07:16 +05:30' --full-history --no-merges -- lib/screens/history/history_widgets/his_request_pane.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/screens/home_page/editor_pane/details_card/request_pane/request_pane_grpc.dart lib/screens/home_page/editor_pane/details_card/request_pane/request_pane_grpc.dart:36— lib/screens/home_page/editor_pane/details_card/request_pane/request_pane_grpc.dart changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 31 in _EditGrpcRequestPaneState.build at line 36. 1 of those changes was a fix/bug commit, and the other 6 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-13..2026-10-11, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-13 00:07:16 +05:30' --until='2026-10-11 00:07:16 +05:30' --full-history --no-merges -- lib/screens/home_page/editor_pane/details_card/request_pane/request_pane_grpc.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/screens/home_page/editor_pane/details_card/request_pane/mqtt/mqtt_request_topics.dart lib/screens/home_page/editor_pane/details_card/request_pane/mqtt/mqtt_request_topics.dart:57— lib/screens/home_page/editor_pane/details_card/request_pane/mqtt/mqtt_request_topics.dart changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 25 in EditMQTTTopicsState.build at line 57. 1 of those changes was a fix/bug commit, and the other 5 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-13..2026-10-11, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-13 00:07:16 +05:30' --until='2026-10-11 00:07:16 +05:30' --full-history --no-merges -- lib/screens/home_page/editor_pane/details_card/request_pane/mqtt/mqtt_request_topics.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/screens/home_page/editor_pane/details_card/request_pane/mqtt/mqtt_request_pane.dart lib/screens/home_page/editor_pane/details_card/request_pane/mqtt/mqtt_request_pane.dart:322— lib/screens/home_page/editor_pane/details_card/request_pane/mqtt/mqtt_request_pane.dart changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 19 in _EditMQTTRequestPaneState._buildSettingsTab at line 322. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-13..2026-10-11, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-13 00:07:16 +05:30' --until='2026-10-11 00:07:16 +05:30' --full-history --no-merges -- lib/screens/home_page/editor_pane/details_card/request_pane/mqtt/mqtt_request_pane.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/screens/settings_page.dart lib/screens/settings_page.dart:16— lib/screens/settings_page.dart changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in SettingsPage.build at line 16. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-13..2026-10-11, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-13 00:07:16 +05:30' --until='2026-10-11 00:07:16 +05:30' --full-history --no-merges -- lib/screens/settings_page.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/models/settings_model.dart lib/models/settings_model.dart:226— lib/models/settings_model.dart changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 18 in SettingsModel.== at line 226. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-13..2026-10-11, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-13 00:07:16 +05:30' --until='2026-10-11 00:07:16 +05:30' --full-history --no-merges -- lib/models/settings_model.dart`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Duplicated block (11 lines × 2) lib/dashbot/services/actions/request_apply_service.dart:114— lib/dashbot/services/actions/request_apply_service.dart:114-124 | lib/dashbot/services/actions/request_apply_service.dart:231-241 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2) lib/screens/common_widgets/agentic_ui_features/ai_ui_designer/generate_ui_dialog.dart:68— lib/screens/common_widgets/agentic_ui_features/ai_ui_designer/generate_ui_dialog.dart:68-78 | lib/screens/common_widgets/agentic_ui_features/tool_generation/generate_tool_dialog.dart:106-116 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (11 lines × 2) lib/screens/history/history_widgets/his_request_pane.dart:29— lib/screens/history/history_widgets/his_request_pane.dart:29-39 | lib/screens/history/history_widgets/his_request_pane.dart:43-53 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2) lib/screens/home_page/editor_pane/details_card/request_pane/request_headers.dart:125— lib/screens/home_page/editor_pane/details_card/request_pane/request_headers.dart:125-135 | lib/screens/home_page/editor_pane/details_card/request_pane/request_headers.dart:151-161 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2) lib/screens/home_page/editor_pane/details_card/request_pane/request_metadata_grpc.dart:119— lib/screens/home_page/editor_pane/details_card/request_pane/request_metadata_grpc.dart:119-129 | lib/screens/home_page/editor_pane/details_card/request_pane/request_metadata_grpc.dart:145-155 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2) lib/screens/home_page/editor_pane/details_card/request_pane/request_params.dart:115— lib/screens/home_page/editor_pane/details_card/request_pane/request_params.dart:115-125 | lib/screens/home_page/editor_pane/details_card/request_pane/request_params.dart:141-151 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2) lib/screens/home_page/editor_pane/url_card/editor_pane_request_url_card.dart:38— lib/screens/home_page/editor_pane/url_card/editor_pane_request_url_card.dart:38-48 | lib/screens/home_page/editor_pane/url_card/editor_pane_request_url_card.dart:56-66 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
ClassTooLong: CollectionStateNotifier lib/providers/collection_providers.dart:96— ClassTooLong — 1499 significant lines (blank, comment-only and punctuation-only lines excluded), 38 methods. The bar is 400 significant lines; this is 1099 over it, 3.75× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: PromptBuilder lib/dashbot/services/agent/prompt_builder.dart:7— ClassTooLong — 821 significant lines (blank, comment-only and punctuation-only lines excluded), 23 methods. The bar is 400 significant lines; this is 421 over it, 2.05× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: ChatViewmodel lib/dashbot/providers/chat_viewmodel.dart:24— ClassTooLong — 693 significant lines (blank, comment-only and punctuation-only lines excluded), 27 methods. The bar is 400 significant lines; this is 293 over it, 1.73× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: ConnectionManager lib/services/connection_manager.dart:23— ClassTooLong — 517 significant lines (blank, comment-only and punctuation-only lines excluded), 27 methods. The bar is 400 significant lines; this is 117 over it, 1.29× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: SDUIWidget doc/gsoc/2025/codes/example4.dart:21— ClassTooLong — 503 significant lines (blank, comment-only and punctuation-only lines excluded), 1 methods. The bar is 400 significant lines; this is 103 over it, 1.26× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: _EditMQTTRequestPaneState lib/screens/home_page/editor_pane/details_card/request_pane/mqtt/mqtt_request_pane.dart:21— ClassTooLong — 458 significant lines (blank, comment-only and punctuation-only lines excluded), 7 methods. The bar is 400 significant lines; this is 58 over it, 1.15× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
FileTooLong: providers/collection_providers.dart lib/providers/collection_providers.dart— FileTooLong — 1555 significant lines (blank, comment-only and punctuation-only lines excluded), about 96% of them inside a single declaration: CollectionStateNotifier (96-2222). The bar is 500 significant lines; this is 1055 over it, 3.11× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: agent/prompt_builder.dart lib/dashbot/services/agent/prompt_builder.dart— FileTooLong — 826 significant lines (blank, comment-only and punctuation-only lines excluded), about 99% of them inside a single declaration: PromptBuilder (7-1052). The bar is 500 significant lines; this is 326 over it, 1.65× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: providers/chat_viewmodel.dart lib/dashbot/providers/chat_viewmodel.dart— FileTooLong — 712 significant lines (blank, comment-only and punctuation-only lines excluded), about 97% of them inside a single declaration: ChatViewmodel (24-960). The bar is 500 significant lines; this is 212 over it, 1.42× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: services/connection_manager.dart lib/services/connection_manager.dart— FileTooLong — 531 significant lines (blank, comment-only and punctuation-only lines excluded), about 97% of them inside a single declaration: ConnectionManager (30-860). The bar is 500 significant lines; this is 31 over it, 1.06× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: lib/consts.dart lib/consts.dart— FileTooLong — 523 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 23 over it, 1.05× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: codes/example4.dart doc/gsoc/2025/codes/example4.dart— FileTooLong — 513 significant lines (blank, comment-only and punctuation-only lines excluded), about 98% of them inside a single declaration: SDUIWidget (21-743). The bar is 500 significant lines; this is 13 over it, 1.03× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
Duplicated block (16 lines × 2) lib/dashbot/services/agent/prompt_builder.dart:696— lib/dashbot/services/agent/prompt_builder.dart:696-711 | lib/dashbot/services/agent/prompt_builder.dart:808-823 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (16 lines × 2) lib/models/settings_model.dart:45— lib/models/settings_model.dart:45-60 | lib/providers/settings_providers.dart:29-44 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (16 lines × 2) lib/screens/history/history_widgets/his_bottombar.dart:24— lib/screens/history/history_widgets/his_bottombar.dart:24-39 | lib/screens/mobile/requests_page/request_response_page_bottombar.dart:20-35 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (16 lines × 2) lib/screens/home_page/editor_pane/details_card/request_pane/mqtt/mqtt_request_pane.dart:499— lib/screens/home_page/editor_pane/details_card/request_pane/mqtt/mqtt_request_pane.dart:499-514 | lib/screens/home_page/editor_pane/details_card/request_pane/mqtt/mqtt_request_pane.dart:561-576 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (16 lines × 2) lib/widgets/editor.dart:30— lib/widgets/editor.dart:30-45 | lib/widgets/editor_json.dart:34-49 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (12 lines × 2) lib/codegen/go/http.dart:153— lib/codegen/go/http.dart:153-164 | lib/codegen/rust/curl_rust.dart:141-152 — 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/screens/history/history_widgets/ai_history_page.dart:81— lib/screens/history/history_widgets/ai_history_page.dart:81-93 | lib/screens/home_page/editor_pane/details_card/request_pane/ai_request/aireq_authorization.dart:23-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.
Duplicated block (12 lines × 2) lib/screens/home_page/editor_pane/details_card/realtime_event_stream_view.dart:410— lib/screens/home_page/editor_pane/details_card/realtime_event_stream_view.dart:410-421 | lib/screens/home_page/editor_pane/details_card/realtime_event_stream_view.dart:440-451 — 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/services/agentic_services/agents/stacgen.dart:15— lib/services/agentic_services/agents/stacgen.dart:15-26 | lib/services/agentic_services/agents/stacmodifier.dart:15-26 — 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 (21 lines × 2) lib/providers/js_runtime_notifier.dart:122— lib/providers/js_runtime_notifier.dart:122-142 | lib/providers/js_runtime_notifier.dart:223-243 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (21 lines × 2) lib/screens/envvar/editor_pane/secrets_pane.dart:171— lib/screens/envvar/editor_pane/secrets_pane.dart:171-191 | lib/screens/envvar/editor_pane/variables_pane.dart:177-197 — 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 (21 lines × 2) lib/screens/history/history_widgets/his_request_pane.dart:266— lib/screens/history/history_widgets/his_request_pane.dart:266-286 | lib/screens/history/history_widgets/his_request_pane.dart:288-308 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (18 lines × 2) lib/screens/common_widgets/auth/jwt_auth_fields.dart:158— lib/screens/common_widgets/auth/jwt_auth_fields.dart:158-175 | lib/screens/common_widgets/auth/jwt_auth_fields.dart:197-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.
Duplicated block (18 lines × 2) lib/screens/home_page/editor_pane/details_card/request_pane/ai_request/aireq_prompt.dart:40— lib/screens/home_page/editor_pane/details_card/request_pane/ai_request/aireq_prompt.dart:40-57 | lib/screens/home_page/editor_pane/details_card/request_pane/ai_request/aireq_prompt.dart:66-83 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (18 lines × 2) lib/screens/home_page/editor_pane/details_card/request_pane/ws/ws_connection_settings.dart:69— lib/screens/home_page/editor_pane/details_card/request_pane/ws/ws_connection_settings.dart:69-86 | lib/screens/home_page/editor_pane/details_card/request_pane/ws/ws_connection_settings.dart:115-132 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (15 lines × 3) doc/gsoc/2025/codes/example5.dart:61— doc/gsoc/2025/codes/example5.dart:61-75 | doc/gsoc/2025/codes/example5.dart:77-91 | doc/gsoc/2025/codes/example5.dart:93-107 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (15 lines × 3) doc/gsoc/2025/codes/example5.dart:160— doc/gsoc/2025/codes/example5.dart:160-174 | doc/gsoc/2025/codes/example5.dart:212-226 | doc/gsoc/2025/codes/example5.dart:264-278 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (15 lines × 3) lib/screens/home_page/editor_pane/details_card/request_pane/request_headers.dart:82— lib/screens/home_page/editor_pane/details_card/request_pane/request_headers.dart:82-96 | lib/screens/home_page/editor_pane/details_card/request_pane/request_metadata_grpc.dart:76-90 | lib/screens/home_page/editor_pane/details_card/request_pane/request_params.dart:72-86 — before extracting anything, compare `lib/screens/home_page/editor_pane/details_card/request_pane/request_headers.dart` and `lib/screens/home_page/editor_pane/details_card/request_pane/request_metadata_grpc.dart` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 163 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (14 lines × 2) lib/screens/history/history_widgets/his_request_pane.dart:58— lib/screens/history/history_widgets/his_request_pane.dart:58-71 | lib/screens/history/history_widgets/his_request_pane.dart:72-85 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (14 lines × 2) lib/services/agentic_services/agents/stacgen.dart:28— lib/services/agentic_services/agents/stacgen.dart:28-41 | lib/services/agentic_services/agents/stacmodifier.dart:28-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 (14 lines × 2) packages/better_networking/example/lib/main.dart:45— packages/better_networking/example/lib/main.dart:45-58 | packages/better_networking/example/lib/main.dart:72-85 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (13 lines × 2) lib/dashbot/services/agent/prompt_builder.dart:620— lib/dashbot/services/agent/prompt_builder.dart:620-632 | lib/dashbot/services/agent/prompt_builder.dart:636-648 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (13 lines × 2) lib/screens/history/history_widgets/ai_history_page.dart:12— lib/screens/history/history_widgets/ai_history_page.dart:12-24 | lib/screens/history/history_widgets/ai_history_page.dart:75-87 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (13 lines × 2) lib/services/agentic_services/agents/apitool_bodygen.dart:19— lib/services/agentic_services/agents/apitool_bodygen.dart:19-31 | lib/services/agentic_services/agents/apitool_funcgen.dart:19-31 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (7 lines × 2) doc/gsoc/2025/codes/example4.dart:12— doc/gsoc/2025/codes/example4.dart:12-18 | doc/gsoc/2025/codes/example5.dart:12-18 — 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/codegen/java/okhttp.dart:176— lib/codegen/java/okhttp.dart:176-182 | lib/codegen/kotlin/okhttp.dart:195-201 — `lib/codegen/java/okhttp.dart` and `lib/codegen/kotlin/okhttp.dart` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 4 separate duplicated blocks between them, totalling at least 50 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (7 lines × 2) packages/apidash_core/lib/utils/string_utils.dart:12— packages/apidash_core/lib/utils/string_utils.dart:12-18 | packages/better_networking/lib/utils/string_utils.dart:15-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.
TooManyMethods: CollectionStateNotifier lib/providers/collection_providers.dart:96— TooManyMethods — 38 methods. The bar is 30 methods; this is 8 over it, 1.27× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: DashbotPrompts lib/dashbot/prompts/dashbot_prompts.dart:33— TooManyMethods — 31 methods. The bar is 30 methods; this is 1 over it, 1.03× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
D4 · Code Duplication· Members sharing a duplicated core (5 members, 50+ identical tokens) · ×2
Members sharing a duplicated core (5 members, 50+ identical tokens) lib/codegen/php/curl.dart:97— lib/codegen/php/curl.dart:97-177 | lib/codegen/php/guzzle.dart:66-147 | lib/codegen/php/http_plug.dart:79-187 | lib/codegen/python/http_client.dart:82-190 | lib/codegen/python/requests.dart:78-200 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
Members sharing a duplicated core (5 members, 50+ identical tokens) lib/screens/home_page/editor_pane/details_card/request_pane/mqtt/mqtt_request_topics.dart:57— lib/screens/home_page/editor_pane/details_card/request_pane/mqtt/mqtt_request_topics.dart:57-289 | lib/screens/home_page/editor_pane/details_card/request_pane/mqtt/mqtt_user_properties.dart:57-222 | lib/screens/home_page/editor_pane/details_card/request_pane/request_headers.dart:39-239 | lib/screens/home_page/editor_pane/details_card/request_pane/request_metadata_grpc.dart:46-233 | lib/screens/home_page/editor_pane/details_card/request_pane/request_params.dart:39-230 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
Duplicated block (18–19 lines × 2) lib/screens/common_widgets/agentic_ui_features/tool_generation/tool_requirements_selector.dart:181— lib/screens/common_widgets/agentic_ui_features/tool_generation/tool_requirements_selector.dart:181-199 | lib/screens/settings_page.dart:136-153 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (18–19 lines × 2) lib/screens/history/history_widgets/ai_history_page.dart:18— lib/screens/history/history_widgets/ai_history_page.dart:18-36 | lib/screens/home_page/editor_pane/details_card/request_pane/ai_request/aireq_prompt.dart:28-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 (17 lines × 2) lib/dashbot/services/agent/prompt_builder.dart:600— lib/dashbot/services/agent/prompt_builder.dart:600-616 | lib/dashbot/services/agent/prompt_builder.dart:827-843 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (17 lines × 2) lib/screens/common_widgets/sidebar_header.dart:45— lib/screens/common_widgets/sidebar_header.dart:45-61 | lib/screens/history/history_widgets/his_sidebar_header.dart:70-86 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (16–17 lines × 2) packages/apidash_core/lib/import_export/insomnia_io.dart:64— packages/apidash_core/lib/import_export/insomnia_io.dart:64-79 | packages/apidash_core/lib/import_export/postman_io.dart:67-83 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (16–17 lines × 2) packages/genai/lib/interface/model_providers/azureopenai.dart:31— packages/genai/lib/interface/model_providers/azureopenai.dart:31-47 | packages/genai/lib/interface/model_providers/openai.dart:27-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 (15–16 lines × 3) lib/dashbot/providers/chat_viewmodel.dart:420— lib/dashbot/providers/chat_viewmodel.dart:420-435 | lib/dashbot/services/actions/request_apply_service.dart:75-89 | lib/dashbot/services/actions/request_apply_service.dart:191-205 — before extracting anything, compare `lib/dashbot/providers/chat_viewmodel.dart` and `lib/dashbot/services/actions/request_apply_service.dart` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 51 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (15–16 lines × 3) lib/screens/home_page/editor_pane/details_card/request_pane/ai_request/request_pane_ai.dart:21— lib/screens/home_page/editor_pane/details_card/request_pane/ai_request/request_pane_ai.dart:21-36 | lib/screens/home_page/editor_pane/details_card/request_pane/request_pane_graphql.dart:42-56 | lib/screens/home_page/editor_pane/details_card/request_pane/request_pane_rest.dart:47-61 — 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 (16 lines × 3) lib/screens/home_page/editor_pane/details_card/request_pane/request_headers.dart:103— lib/screens/home_page/editor_pane/details_card/request_pane/request_headers.dart:103-118 | lib/screens/home_page/editor_pane/details_card/request_pane/request_metadata_grpc.dart:97-112 | lib/screens/home_page/editor_pane/details_card/request_pane/request_params.dart:93-108 — before extracting anything, compare `lib/screens/home_page/editor_pane/details_card/request_pane/request_headers.dart` and `lib/screens/home_page/editor_pane/details_card/request_pane/request_metadata_grpc.dart` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 163 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (16 lines × 3) lib/screens/home_page/editor_pane/details_card/request_pane/request_headers.dart:131— lib/screens/home_page/editor_pane/details_card/request_pane/request_headers.dart:131-146 | lib/screens/home_page/editor_pane/details_card/request_pane/request_metadata_grpc.dart:125-140 | lib/screens/home_page/editor_pane/details_card/request_pane/request_params.dart:121-136 — before extracting anything, compare `lib/screens/home_page/editor_pane/details_card/request_pane/request_headers.dart` and `lib/screens/home_page/editor_pane/details_card/request_pane/request_metadata_grpc.dart` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 163 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (15 lines × 2) lib/codegen/swift/alamofire.dart:115— lib/codegen/swift/alamofire.dart:115-129 | lib/codegen/swift/urlsession.dart:144-158 — 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 (15 lines × 2) lib/screens/common_widgets/auth/oauth1_fields.dart:231— lib/screens/common_widgets/auth/oauth1_fields.dart:231-245 | lib/screens/common_widgets/auth/oauth1_fields.dart:248-262 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8–9 lines × 2) lib/codegen/java/okhttp.dart:131— lib/codegen/java/okhttp.dart:131-139 | lib/codegen/kotlin/okhttp.dart:144-151 — `lib/codegen/java/okhttp.dart` and `lib/codegen/kotlin/okhttp.dart` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 4 separate duplicated blocks between them, totalling at least 50 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (8–9 lines × 2) lib/providers/collection_providers.dart:1865— lib/providers/collection_providers.dart:1865-1872 | lib/services/connection_manager.dart:745-753 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (9 lines × 2) lib/dashbot/services/agent/prompt_builder.dart:576— lib/dashbot/services/agent/prompt_builder.dart:576-584 | lib/dashbot/services/agent/prompt_builder.dart:588-596 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) lib/widgets/dropdown_content_type.dart:15— lib/widgets/dropdown_content_type.dart:15-23 | lib/widgets/dropdown_formdata.dart:15-23 — 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.
Swallowed exception (empty catch) lib/dashbot/providers/chat_viewmodel.dart:444— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) lib/dashbot/providers/chat_viewmodel.dart:911— 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.
PromptBuilder.buildTaskPrompt (cyclomatic 116) lib/dashbot/services/agent/prompt_builder.dart:499— PromptBuilder.buildTaskPrompt has cyclomatic complexity 116 (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.
CollectionStateNotifier.sendRequest (cyclomatic 52) lib/providers/collection_providers.dart:1047— CollectionStateNotifier.sendRequest has cyclomatic complexity 52 (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.
CollectionStateNotifier._connectGrpc (cyclomatic 50) lib/providers/collection_providers.dart:1839— CollectionStateNotifier._connectGrpc has cyclomatic complexity 50 (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.
Curl.parse (cyclomatic 35) packages/curl_parser/lib/models/curl.dart:88— Curl.parse has cyclomatic complexity 35 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
HistoryRequestPane.build (cyclomatic 34) lib/screens/history/history_widgets/his_request_pane.dart:19— HistoryRequestPane.build has cyclomatic complexity 34 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
ChatViewmodel.sendMessage (cyclomatic 33) lib/dashbot/providers/chat_viewmodel.dart:57— ChatViewmodel.sendMessage has cyclomatic complexity 33 (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.
DashbotActionWidgetFactory.build (cyclomatic 33) lib/dashbot/widgets/dashbot_action.dart:13— DashbotActionWidgetFactory.build has cyclomatic complexity 33 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
URLTextField.build (cyclomatic 32) lib/screens/home_page/editor_pane/url_card/url_text_field.dart:11— URLTextField.build has cyclomatic complexity 32 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
CollectionStateNotifier._connectWebSocket (cyclomatic 31) lib/providers/collection_providers.dart:740— CollectionStateNotifier._connectWebSocket 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.
_EditGrpcRequestPaneState.build (cyclomatic 31) lib/screens/home_page/editor_pane/details_card/request_pane/request_pane_grpc.dart:36— _EditGrpcRequestPaneState.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.
_RealtimeEventStreamViewState.build (cyclomatic 29) lib/screens/home_page/editor_pane/details_card/realtime_event_stream_view.dart:64— _RealtimeEventStreamViewState.build has cyclomatic complexity 29 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
GrpcUtils._decodeWithSchema (cyclomatic 26) lib/utils/grpc_utils.dart:181— GrpcUtils._decodeWithSchema has cyclomatic complexity 26 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
EditMQTTTopicsState.build (cyclomatic 25) lib/screens/home_page/editor_pane/details_card/request_pane/mqtt/mqtt_request_topics.dart:57— EditMQTTTopicsState.build has cyclomatic complexity 25 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
ConnectionManager._connectMqttV5 (cyclomatic 25) lib/services/connection_manager.dart:406— ConnectionManager._connectMqttV5 has cyclomatic complexity 25 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
GrpcReflectionService.getMethodSchema (cyclomatic 24) lib/services/grpc_reflection_service.dart:479— GrpcReflectionService.getMethodSchema 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.
NetworkDetails.build (cyclomatic 24) lib/terminal/widgets/terminal_tiles.dart:299— NetworkDetails.build has cyclomatic complexity 24 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
DartHttpCodeGen.generatedDartCode (cyclomatic 23) lib/codegen/dart/http.dart:30— DartHttpCodeGen.generatedDartCode has cyclomatic complexity 23 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
PythonHttpClientCodeGen.getCode (cyclomatic 23) lib/codegen/python/http_client.dart:82— PythonHttpClientCodeGen.getCode has cyclomatic complexity 23 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
PromptBuilder.formatWsMessageLog (cyclomatic 23) lib/dashbot/services/agent/prompt_builder.dart:433— PromptBuilder.formatWsMessageLog has cyclomatic complexity 23 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This is NOT this file's highest cyclomatic complexity: PromptBuilder.getUserMessageForTask (cyclomatic 29) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded method is counted neither in this dimension's figures nor in its score.
_OAuth2FieldsState.build (cyclomatic 23) lib/screens/common_widgets/auth/oauth2_field.dart:111— _OAuth2FieldsState.build has cyclomatic complexity 23 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
RustUreqCodeGen.getCode (cyclomatic 21) lib/codegen/rust/ureq.dart:114— RustUreqCodeGen.getCode has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
KotlinOkHttpCodeGen.getCode (cyclomatic 20) lib/codegen/kotlin/okhttp.dart:85— KotlinOkHttpCodeGen.getCode has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
PhpHttpPlugCodeGen.getCode (cyclomatic 20) lib/codegen/php/http_plug.dart:79— PhpHttpPlugCodeGen.getCode has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
PromptBuilder.buildWsConnectionHealthStats (cyclomatic 20) lib/dashbot/services/agent/prompt_builder.dart:264— PromptBuilder.buildWsConnectionHealthStats has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This is NOT this file's highest cyclomatic complexity: PromptBuilder.getUserMessageForTask (cyclomatic 29) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded method is counted neither in this dimension's figures nor in its score.
CCurlCodeGen.getCode (cyclomatic 19) lib/codegen/c/curl.dart:92— CCurlCodeGen.getCode 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.
PythonRequestsCodeGen.getCode (cyclomatic 19) lib/codegen/python/requests.dart:78— PythonRequestsCodeGen.getCode 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.
RubyFaradayCodeGen.getCode (cyclomatic 19) lib/codegen/ruby/faraday.dart:87— RubyFaradayCodeGen.getCode 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.
RustActixCodeGen.getCode (cyclomatic 19) lib/codegen/rust/actix.dart:116— RustActixCodeGen.getCode 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.
RustReqwestCodeGen.getCode (cyclomatic 19) lib/codegen/rust/reqwest.dart:87— RustReqwestCodeGen.getCode 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.
ChatViewmodel._applyOpenApi (cyclomatic 19) lib/dashbot/providers/chat_viewmodel.dart:365— ChatViewmodel._applyOpenApi 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.
ChatBubble.build (cyclomatic 19) lib/dashbot/widgets/chat_bubble.dart:25— ChatBubble.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.
CollectionStateNotifier.update (cyclomatic 19) lib/providers/collection_providers.dart:309— CollectionStateNotifier.update 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.
_EditMQTTRequestPaneState._buildSettingsTab (cyclomatic 19) lib/screens/home_page/editor_pane/details_card/request_pane/mqtt/mqtt_request_pane.dart:322— _EditMQTTRequestPaneState._buildSettingsTab 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.
APIDashRequestDescription.generateREQDATA (cyclomatic 18) lib/apitoolgen/request_consolidator.dart:24— APIDashRequestDescription.generateREQDATA has cyclomatic complexity 18 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
DartDioCodeGen.generatedDartCode (cyclomatic 18) lib/codegen/dart/dio.dart:28— DartDioCodeGen.generatedDartCode 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.
RustHyperCodeGen.getCode (cyclomatic 18) lib/codegen/rust/hyper.dart:110— RustHyperCodeGen.getCode has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
RequestApplyService.applyOpenApi (cyclomatic 18) lib/dashbot/services/actions/request_apply_service.dart:134— RequestApplyService.applyOpenApi has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
SettingsModel.== (cyclomatic 18) lib/models/settings_model.dart:226— SettingsModel.== has cyclomatic complexity 18 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
ResponsePane.build (cyclomatic 18) lib/screens/home_page/editor_pane/details_card/response_pane.dart:13— ResponsePane.build has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
GrpcReflectionService._mapTypeToString (cyclomatic 18) lib/services/grpc_reflection_service.dart:604— GrpcReflectionService._mapTypeToString 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.
GrpcUtils.paramsToJson (cyclomatic 18) lib/utils/grpc_utils.dart:442— GrpcUtils.paramsToJson has cyclomatic complexity 18 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
_PreviewerState.build (cyclomatic 18) lib/widgets/previewer.dart:49— _PreviewerState.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.
CSharpRestSharp.getCode (cyclomatic 17) lib/codegen/csharp/rest_sharp.dart:89— CSharpRestSharp.getCode has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
JavaAsyncHttpClientGen.getCode (cyclomatic 17) lib/codegen/java/async_http_client.dart:112— JavaAsyncHttpClientGen.getCode has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
JavaOkHttpCodeGen.getCode (cyclomatic 17) lib/codegen/java/okhttp.dart:91— JavaOkHttpCodeGen.getCode has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
PhpGuzzleCodeGen.getCode (cyclomatic 17) lib/codegen/php/guzzle.dart:66— PhpGuzzleCodeGen.getCode has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
_ChatScreenState.build (cyclomatic 17) lib/dashbot/pages/dashbot_chat_page.dart:56— _ChatScreenState.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.
_FormDataBodyState.build (cyclomatic 17) lib/screens/home_page/editor_pane/details_card/request_pane/request_form_data.dart:37— _FormDataBodyState.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.
AxiosCodeGen.getCode (cyclomatic 16) lib/codegen/js/axios.dart:50— AxiosCodeGen.getCode 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.
FetchCodeGen.getCode (cyclomatic 16) lib/codegen/js/fetch.dart:57— FetchCodeGen.getCode 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.
OpenApiImportService.extractSpecMeta (cyclomatic 16) lib/dashbot/services/openapi_import_service.dart:41— OpenApiImportService.extractSpecMeta 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.
_LogEntryState.build (cyclomatic 16) lib/screens/home_page/editor_pane/details_card/realtime_event_stream_view.dart:347— _LogEntryState.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.
EditRequestHeadersState.build (cyclomatic 16) lib/screens/home_page/editor_pane/details_card/request_pane/request_headers.dart:39— EditRequestHeadersState.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.
SettingsPage.build (cyclomatic 16) lib/screens/settings_page.dart:16— SettingsPage.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.
GrpcUtils.paramsToBytes (cyclomatic 16) lib/utils/grpc_utils.dart:463— GrpcUtils.paramsToBytes 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.
Repeated repair: lib/screens/home_page/editor_pane/details_card/request_pane/ws/ws_recently_sent.dart lib/screens/home_page/editor_pane/details_card/request_pane/ws/ws_recently_sent.dart:27— lib/screens/home_page/editor_pane/details_card/request_pane/ws/ws_recently_sent.dart changed 3 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 11 (its worst body is WsRecentlySent.build at line 27), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix: dedupe WebSocket Recently Sent cards and show send count (#1750)”; “fix: view full text of long Recently Sent messages (#1752)”; “fix: keep automatic heartbeat messages out of WS Recently Sent (#1751)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-13..2026-10-11, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-13 00:07:16 +05:30' --until='2026-10-11 00:07:16 +05:30' --full-history --no-merges -- lib/screens/home_page/editor_pane/details_card/request_pane/ws/ws_recently_sent.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.
FixmeComment test/providers/ui_providers_test.dart:30— // FIXME: Font file moved to design system so this must be fixed if spot screenshot is used — 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.
PromptBuilder.buildTaskPrompt (cognitive 175) lib/dashbot/services/agent/prompt_builder.dart:499— PromptBuilder.buildTaskPrompt has cognitive complexity 175 (threshold 15). Drivers by points: ternaries 80 (163 pts), if/else 5 (8 pts), boolean chains 3, match/switch 1 (nesting depth added 86). 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.
CollectionStateNotifier._connectGrpc (cognitive 147) lib/providers/collection_providers.dart:1839— CollectionStateNotifier._connectGrpc has cognitive complexity 147 (threshold 15). Drivers by points: if/else 30 (102 pts), ternaries 8 (33 pts), boolean chains 11, error handling 1 (nesting depth added 97). 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.
CollectionStateNotifier.sendRequest (cognitive 114) lib/providers/collection_providers.dart:1047— CollectionStateNotifier.sendRequest has cognitive complexity 114 (threshold 15). Drivers by points: if/else 37 (76 pts), boolean chains 15, ternaries 3 (13 pts), error handling 2 (6 pts), loops 1 (4 pts) (nesting depth added 56). 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.
GrpcReflectionService.getMethodSchema (cognitive 82) lib/services/grpc_reflection_service.dart:479— GrpcReflectionService.getMethodSchema has cognitive complexity 82 (threshold 15). Drivers by points: if/else 8 (35 pts), loops 8 (28 pts), ternaries 3 (15 pts), boolean chains 3, error handling 1 (nesting depth added 59). 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.
CollectionStateNotifier._connectWebSocket (cognitive 68) lib/providers/collection_providers.dart:740— CollectionStateNotifier._connectWebSocket has cognitive complexity 68 (threshold 15). Drivers by points: if/else 24 (57 pts), loops 2 (5 pts), boolean chains 3, error handling 2 (3 pts) (nesting depth added 37). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
GrpcUtils._decodeWithSchema (cognitive 64) lib/utils/grpc_utils.dart:181— GrpcUtils._decodeWithSchema has cognitive complexity 64 (threshold 15). Drivers by points: if/else 17 (41 pts), error handling 3 (14 pts), loops 2 (4 pts), match/switch 1 (2 pts), ternaries 1 (2 pts), boolean chains 1 (nesting depth added 39). 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.
KotlinOkHttpCodeGen.getCode (cognitive 58) lib/codegen/kotlin/okhttp.dart:85— KotlinOkHttpCodeGen.getCode has cognitive complexity 58 (threshold 15). Drivers by points: if/else 12 (36 pts), ternaries 5 (15 pts), loops 1 (4 pts), boolean chains 2, error handling 1 (nesting depth added 37). 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.
Curl.parse (cognitive 57) packages/curl_parser/lib/models/curl.dart:88— Curl.parse has cognitive complexity 57 (threshold 15). Drivers by points: if/else 22 (37 pts), boolean chains 8, loops 4 (7 pts), ternaries 3 (5 pts) (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.
URLTextField.build (cognitive 56) lib/screens/home_page/editor_pane/url_card/url_text_field.dart:11— URLTextField.build has cognitive complexity 56 (threshold 15). Drivers by points: if/else 15 (41 pts), boolean chains 6, ternaries 1 (4 pts), error handling 1 (3 pts), match/switch 2 (nesting depth added 31). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
PythonRequestsCodeGen.getCode (cognitive 55) lib/codegen/python/requests.dart:78— PythonRequestsCodeGen.getCode has cognitive complexity 55 (threshold 15). Drivers by points: if/else 16 (49 pts), loops 1 (4 pts), boolean chains 1, error handling 1 (nesting depth added 36). 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.
PythonHttpClientCodeGen.getCode (cognitive 53) lib/codegen/python/http_client.dart:82— PythonHttpClientCodeGen.getCode has cognitive complexity 53 (threshold 15). Drivers by points: if/else 12 (39 pts), boolean chains 7, ternaries 2 (6 pts), error handling 1 (nesting depth added 31). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
PhpHttpPlugCodeGen.getCode (cognitive 52) lib/codegen/php/http_plug.dart:79— PhpHttpPlugCodeGen.getCode has cognitive complexity 52 (threshold 15). Drivers by points: if/else 15 (43 pts), boolean chains 4, loops 1 (4 pts), error handling 1 (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.
RustReqwestCodeGen.getCode (cognitive 48) lib/codegen/rust/reqwest.dart:87— RustReqwestCodeGen.getCode has cognitive complexity 48 (threshold 15). Drivers by points: if/else 14 (44 pts), boolean chains 3, error handling 1 (nesting depth added 30). 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.
_RealtimeEventStreamViewState.build (cognitive 47) lib/screens/home_page/editor_pane/details_card/realtime_event_stream_view.dart:64— _RealtimeEventStreamViewState.build has cognitive complexity 47 (threshold 15). Drivers by points: if/else 17 (34 pts), ternaries 5 (7 pts), boolean chains 6 (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.
CSharpRestSharp.getCode (cognitive 46) lib/codegen/csharp/rest_sharp.dart:89— CSharpRestSharp.getCode has cognitive complexity 46 (threshold 15). Drivers by points: if/else 9 (29 pts), loops 3 (13 pts), boolean chains 3, error handling 1 (nesting depth added 30). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
RustUreqCodeGen.getCode (cognitive 46) lib/codegen/rust/ureq.dart:114— RustUreqCodeGen.getCode has cognitive complexity 46 (threshold 15). Drivers by points: if/else 16 (41 pts), boolean chains 4, error handling 1 (nesting depth added 25). 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.
RustActixCodeGen.getCode (cognitive 43) lib/codegen/rust/actix.dart:116— RustActixCodeGen.getCode has cognitive complexity 43 (threshold 15). Drivers by points: if/else 14 (38 pts), boolean chains 4, error handling 1 (nesting depth added 24). 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.
ChatViewmodel.sendMessage (cognitive 43) lib/dashbot/providers/chat_viewmodel.dart:57— ChatViewmodel.sendMessage has cognitive complexity 43 (threshold 15). Drivers by points: if/else 18 (24 pts), boolean chains 13, error handling 2 (4 pts), ternaries 2 (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.
JavaOkHttpCodeGen.getCode (cognitive 42) lib/codegen/java/okhttp.dart:91— JavaOkHttpCodeGen.getCode has cognitive complexity 42 (threshold 15). Drivers by points: if/else 9 (27 pts), ternaries 4 (12 pts), boolean chains 2, error handling 1 (nesting depth added 26). 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.
_EditGrpcRequestPaneState.build (cognitive 42) lib/screens/home_page/editor_pane/details_card/request_pane/request_pane_grpc.dart:36— _EditGrpcRequestPaneState.build has cognitive complexity 42 (threshold 15). Drivers by points: if/else 17 (25 pts), ternaries 8 (12 pts), boolean chains 5 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
JuliaHttpClientCodeGen.getCode (cognitive 39) lib/codegen/julia/http.dart:75— JuliaHttpClientCodeGen.getCode has cognitive complexity 39 (threshold 15). Drivers by points: if/else 11 (36 pts), boolean chains 2, error handling 1 (nesting depth added 25). 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.
FetchCodeGen.getCode (cognitive 38) lib/codegen/js/fetch.dart:57— FetchCodeGen.getCode has cognitive complexity 38 (threshold 15). Drivers by points: if/else 7 (18 pts), ternaries 4 (12 pts), loops 2 (6 pts), boolean chains 1, error handling 1 (nesting depth added 23). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
JavaAsyncHttpClientGen.getCode (cognitive 36) lib/codegen/java/async_http_client.dart:112— JavaAsyncHttpClientGen.getCode has cognitive complexity 36 (threshold 15). Drivers by points: if/else 12 (30 pts), loops 1 (3 pts), boolean chains 2, error handling 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.
RustHyperCodeGen.getCode (cognitive 36) lib/codegen/rust/hyper.dart:110— RustHyperCodeGen.getCode has cognitive complexity 36 (threshold 15). Drivers by points: if/else 13 (27 pts), boolean chains 5, ternaries 1 (3 pts), error handling 1 (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
GoHttpCodeGen.getCode (cognitive 35) lib/codegen/go/http.dart:91— GoHttpCodeGen.getCode has cognitive complexity 35 (threshold 15). Drivers by points: if/else 8 (23 pts), loops 1 (4 pts), ternaries 1 (4 pts), boolean chains 3, error handling 1 (nesting depth added 21). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AxiosCodeGen.getCode (cognitive 35) lib/codegen/js/axios.dart:50— AxiosCodeGen.getCode has cognitive complexity 35 (threshold 15). Drivers by points: if/else 6 (14 pts), ternaries 4 (12 pts), loops 2 (6 pts), boolean chains 2, error handling 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.
ChatViewmodel.handlePotentialCurlPaste (cognitive 35) lib/dashbot/providers/chat_viewmodel.dart:497— ChatViewmodel.handlePotentialCurlPaste has cognitive complexity 35 (threshold 15). Drivers by points: if/else 6 (20 pts), error handling 3 (8 pts), ternaries 1 (5 pts), boolean chains 2 (nesting depth added 23). 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.
_OAuth2FieldsState._loadCredentialsFromFile (cognitive 35) lib/screens/common_widgets/auth/oauth2_field.dart:69— _OAuth2FieldsState._loadCredentialsFromFile has cognitive complexity 35 (threshold 15). Drivers by points: if/else 11 (32 pts), error handling 1 (2 pts), boolean chains 1 (nesting depth added 22). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
GrpcUtils._parseLevel (cognitive 35) lib/utils/grpc_utils.dart:94— GrpcUtils._parseLevel has cognitive complexity 35 (threshold 15). Drivers by points: if/else 9 (22 pts), loops 4 (10 pts), ternaries 1 (2 pts), boolean chains 1 (nesting depth added 20). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ConnectionManager._connectMqttV5 (cognitive 34) lib/services/connection_manager.dart:406— ConnectionManager._connectMqttV5 has cognitive complexity 34 (threshold 15). Drivers by points: if/else 16 (21 pts), boolean chains 6, ternaries 2 (4 pts), error handling 2, loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PhpGuzzleCodeGen.getCode (cognitive 33) lib/codegen/php/guzzle.dart:66— PhpGuzzleCodeGen.getCode has cognitive complexity 33 (threshold 15). Drivers by points: if/else 7 (19 pts), ternaries 4 (9 pts), boolean chains 4, error handling 1 (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
APIDashRequestDescription.generateREQDATA (cognitive 32) lib/apitoolgen/request_consolidator.dart:24— APIDashRequestDescription.generateREQDATA has cognitive complexity 32 (threshold 15). Drivers by points: loops 6 (17 pts), if/else 9 (13 pts), boolean chains 1, ternaries 1 (nesting depth added 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
PHPcURLCodeGen.getCode (cognitive 32) lib/codegen/php/curl.dart:97— PHPcURLCodeGen.getCode has cognitive complexity 32 (threshold 15). Drivers by points: if/else 8 (24 pts), ternaries 1 (4 pts), boolean chains 3, 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.
CCurlCodeGen.getCode (cognitive 31) lib/codegen/c/curl.dart:92— CCurlCodeGen.getCode has cognitive complexity 31 (threshold 15). Drivers by points: if/else 10 (23 pts), boolean chains 7, error handling 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.
ChatViewmodel._applyOpenApi (cognitive 31) lib/dashbot/providers/chat_viewmodel.dart:365— ChatViewmodel._applyOpenApi has cognitive complexity 31 (threshold 15). Drivers by points: if/else 10 (14 pts), error handling 4 (8 pts), ternaries 4 (7 pts), boolean chains 2 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ChatViewmodel.handlePotentialOpenApiUrl (cognitive 31) lib/dashbot/providers/chat_viewmodel.dart:615— ChatViewmodel.handlePotentialOpenApiUrl has cognitive complexity 31 (threshold 15). Drivers by points: if/else 8 (22 pts), error handling 3 (8 pts), boolean chains 1 (nesting depth added 19). 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.
DartHttpCodeGen.generatedDartCode (cognitive 30) lib/codegen/dart/http.dart:30— DartHttpCodeGen.generatedDartCode has cognitive complexity 30 (threshold 15). Drivers by points: if/else 17 (23 pts), ternaries 4 (5 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.
RubyFaradayCodeGen.getCode (cognitive 30) lib/codegen/ruby/faraday.dart:87— RubyFaradayCodeGen.getCode has cognitive complexity 30 (threshold 15). Drivers by points: if/else 11 (22 pts), boolean chains 7, error handling 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PromptBuilder.buildWsConnectionHealthStats (cognitive 30) lib/dashbot/services/agent/prompt_builder.dart:264— PromptBuilder.buildWsConnectionHealthStats has cognitive complexity 30 (threshold 15). Drivers by points: if/else 14 (24 pts), boolean chains 2, match/switch 1 (2 pts), loops 1, ternaries 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.
ChatBubble.build (cognitive 30) lib/dashbot/widgets/chat_bubble.dart:25— ChatBubble.build has cognitive complexity 30 (threshold 15). Drivers by points: if/else 9 (18 pts), ternaries 4, boolean chains 3, loops 1 (3 pts), error handling 1 (2 pts) (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
GrpcUtils.paramsToBytes (cognitive 30) lib/utils/grpc_utils.dart:463— GrpcUtils.paramsToBytes has cognitive complexity 30 (threshold 15). Drivers by points: if/else 11 (21 pts), ternaries 1 (4 pts), boolean chains 2, match/switch 1 (2 pts), loops 1 (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
cURLCodeGen.getCode (cognitive 29) lib/codegen/others/curl.dart:21— cURLCodeGen.getCode has cognitive complexity 29 (threshold 15). Drivers by points: if/else 5 (13 pts), loops 2 (6 pts), ternaries 1 (5 pts), boolean chains 2, match/switch 1 (2 pts), error handling 1 (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
EditMQTTTopicsState.build (cognitive 29) lib/screens/home_page/editor_pane/details_card/request_pane/mqtt/mqtt_request_topics.dart:57— EditMQTTTopicsState.build has cognitive complexity 29 (threshold 15). Drivers by points: if/else 16 (19 pts), boolean chains 5, 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.
RustCurlCodeGen.getCode (cognitive 27) lib/codegen/rust/curl_rust.dart:91— RustCurlCodeGen.getCode has cognitive complexity 27 (threshold 15). Drivers by points: if/else 7 (18 pts), boolean chains 5, ternaries 1 (3 pts), error handling 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.
DashbotActionWidgetFactory.build (cognitive 27) lib/dashbot/widgets/dashbot_action.dart:13— DashbotActionWidgetFactory.build has cognitive complexity 27 (threshold 15). Drivers by points: if/else 13 (21 pts), boolean chains 5, match/switch 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.
HistoryRequestPane.build (cognitive 27) lib/screens/history/history_widgets/his_request_pane.dart:19— HistoryRequestPane.build has cognitive complexity 27 (threshold 15). Drivers by points: if/else 8 (12 pts), boolean chains 6, loops 2 (4 pts), match/switch 3, ternaries 2 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
RequestApplyService.applyOpenApi (cognitive 26) lib/dashbot/services/actions/request_apply_service.dart:134— RequestApplyService.applyOpenApi has cognitive complexity 26 (threshold 15). Drivers by points: if/else 10 (11 pts), ternaries 4 (8 pts), error handling 3 (5 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.
_OAuth2FieldsState.build (cognitive 26) lib/screens/common_widgets/auth/oauth2_field.dart:111— _OAuth2FieldsState.build has cognitive complexity 26 (threshold 15). Drivers by points: if/else 15 (17 pts), ternaries 3 (5 pts), boolean chains 4 (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
JavaHttpClientCodeGen.getCode (cognitive 25) lib/codegen/java/httpclient.dart:110— JavaHttpClientCodeGen.getCode has cognitive complexity 25 (threshold 15). Drivers by points: if/else 8 (22 pts), boolean chains 2, error handling 1 (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ChatViewmodel.handlePotentialOpenApiPaste (cognitive 25) lib/dashbot/providers/chat_viewmodel.dart:737— ChatViewmodel.handlePotentialOpenApiPaste has cognitive complexity 25 (threshold 15). Drivers by points: if/else 5 (16 pts), error handling 3 (8 pts), boolean chains 1 (nesting depth added 16). 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.
_EditMQTTRequestPaneState._buildSettingsTab (cognitive 25) lib/screens/home_page/editor_pane/details_card/request_pane/mqtt/mqtt_request_pane.dart:322— _EditMQTTRequestPaneState._buildSettingsTab has cognitive complexity 25 (threshold 15). Drivers by points: if/else 17 (21 pts), boolean chains 2, ternaries 2 (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
JavaUnirestGen.getCode (cognitive 24) lib/codegen/java/unirest.dart:65— JavaUnirestGen.getCode has cognitive complexity 24 (threshold 15). Drivers by points: if/else 8 (17 pts), boolean chains 3, loops 1 (3 pts), error handling 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PromptBuilder.formatWsMessageLog (cognitive 24) lib/dashbot/services/agent/prompt_builder.dart:433— PromptBuilder.formatWsMessageLog has cognitive complexity 24 (threshold 15). Drivers by points: if/else 5 (9 pts), boolean chains 6, ternaries 4 (5 pts), loops 2, match/switch 1 (2 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CollectionStateNotifier.update (cognitive 24) lib/providers/collection_providers.dart:309— CollectionStateNotifier.update has cognitive complexity 24 (threshold 15). Drivers by points: if/else 7 (12 pts), boolean chains 5, ternaries 2 (5 pts), match/switch 1 (2 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
NetworkDetails.build (cognitive 24) lib/terminal/widgets/terminal_tiles.dart:299— NetworkDetails.build has cognitive complexity 24 (threshold 15). Drivers by points: boolean chains 10, if/else 7 (8 pts), ternaries 5, loops 1 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
RubyNetHttpCodeGen.getCode (cognitive 23) lib/codegen/ruby/net_http.dart:54— RubyNetHttpCodeGen.getCode has cognitive complexity 23 (threshold 15). Drivers by points: if/else 7 (16 pts), boolean chains 3, loops 1 (3 pts), error handling 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
OpenApiImportService._payloadForOperation (cognitive 23) lib/dashbot/services/openapi_import_service.dart:182— OpenApiImportService._payloadForOperation has cognitive complexity 23 (threshold 15). Drivers by points: if/else 7 (14 pts), ternaries 2 (5 pts), boolean chains 3, loops 1 (nesting depth added 10). 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.
JsRuntimeNotifier.executePreRequestScript (cognitive 23) lib/providers/js_runtime_notifier.dart:86— JsRuntimeNotifier.executePreRequestScript has cognitive complexity 23 (threshold 15). Drivers by points: if/else 6 (15 pts), error handling 2 (6 pts), ternaries 1 (2 pts) (nesting depth added 14). 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. This shape REPEATS in the file: one other method here (JsRuntimeNotifier.executePostResponseScript) 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.
JsRuntimeNotifier.executePostResponseScript (cognitive 23) lib/providers/js_runtime_notifier.dart:182— JsRuntimeNotifier.executePostResponseScript has cognitive complexity 23 (threshold 15). Drivers by points: if/else 6 (15 pts), error handling 2 (6 pts), ternaries 1 (2 pts) (nesting depth added 14). 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. This shape REPEATS in the file: one other method here (JsRuntimeNotifier.executePreRequestScript) 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.
ResponsePane.build (cognitive 23) lib/screens/home_page/editor_pane/details_card/response_pane.dart:13— ResponsePane.build has cognitive complexity 23 (threshold 15). Drivers by points: if/else 9 (13 pts), boolean chains 6, ternaries 2 (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.
UrlEnvService.ensureBaseUrlEnvForOpenApi (cognitive 22) lib/dashbot/services/base/url_env_service.dart:69— UrlEnvService.ensureBaseUrlEnvForOpenApi has cognitive complexity 22 (threshold 15). Drivers by points: if/else 6 (11 pts), boolean chains 5, ternaries 2 (5 pts), error handling 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PostmanIO.postmanRequestToHttpRequestModel (cognitive 22) packages/apidash_core/lib/import_export/postman_io.dart:18— PostmanIO.postmanRequestToHttpRequestModel has cognitive complexity 22 (threshold 15). Drivers by points: error handling 3 (8 pts), if/else 3 (5 pts), loops 3 (5 pts), match/switch 1 (4 pts) (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
GrpcReflectionService.getMethodsForService (cognitive 21) lib/services/grpc_reflection_service.dart:443— GrpcReflectionService.getMethodsForService has cognitive complexity 21 (threshold 15). Drivers by points: if/else 2 (7 pts), loops 2 (7 pts), ternaries 1 (5 pts), boolean chains 1, error handling 1 (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
_PreviewerState.build (cognitive 21) lib/widgets/previewer.dart:49— _PreviewerState.build has cognitive complexity 21 (threshold 15). Drivers by points: if/else 9 (10 pts), error handling 3 (6 pts), boolean chains 5 (nesting depth added 4). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
SwiftAlamofireCodeGen.getCode (cognitive 20) lib/codegen/swift/alamofire.dart:66— SwiftAlamofireCodeGen.getCode has cognitive complexity 20 (threshold 15). Drivers by points: if/else 10 (17 pts), loops 1 (2 pts), error handling 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DashbotImportNowButton.build (cognitive 20) lib/dashbot/widgets/dashbot_action_buttons/dashbot_import_now_button.dart:16— DashbotImportNowButton.build has cognitive complexity 20 (threshold 15). Drivers by points: if/else 5 (10 pts), ternaries 2 (5 pts), boolean chains 2, loops 1 (2 pts), error handling 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ConnectionManager._connectMqttV3 (cognitive 20) lib/services/connection_manager.dart:286— ConnectionManager._connectMqttV3 has cognitive complexity 20 (threshold 15). Drivers by points: if/else 11 (14 pts), boolean chains 3, ternaries 1 (2 pts), error handling 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
GrpcUtils.paramsToJson (cognitive 20) lib/utils/grpc_utils.dart:442— GrpcUtils.paramsToJson has cognitive complexity 20 (threshold 15). Drivers by points: boolean chains 10, if/else 6 (9 pts), loops 1 (nesting depth added 3). 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.
SSEDisplay.build (cognitive 20) lib/widgets/sse_display.dart:15— SSEDisplay.build has cognitive complexity 20 (threshold 15). Drivers by points: if/else 4 (8 pts), error handling 2 (4 pts), ternaries 3 (4 pts), boolean chains 2, loops 1 (2 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SwiftURLSessionCodeGen.getCode (cognitive 19) lib/codegen/swift/urlsession.dart:109— SwiftURLSessionCodeGen.getCode has cognitive complexity 19 (threshold 15). Drivers by points: if/else 10 (16 pts), boolean chains 2, error handling 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.
InsomniaIO.insomniaResourceToHttpRequestModel (cognitive 19) packages/apidash_core/lib/import_export/insomnia_io.dart:23— InsomniaIO.insomniaResourceToHttpRequestModel has cognitive complexity 19 (threshold 15). Drivers by points: error handling 2 (5 pts), loops 3 (5 pts), if/else 3 (4 pts), match/switch 1 (4 pts), boolean chains 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
_TerminalPageState.build (cognitive 19) lib/screens/terminal/terminal_page.dart:34— _TerminalPageState.build has cognitive complexity 19 (threshold 15). Drivers by points: ternaries 5 (11 pts), if/else 4 (6 pts), boolean chains 1, match/switch 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.
OAuthCallbackServer._handleRequest (cognitive 18) packages/better_networking/lib/services/oauth_callback_server.dart:154— OAuthCallbackServer._handleRequest has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (15 pts), error handling 2 (3 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.
CSharpHttpClientCodeGen.getCode (cognitive 17) lib/codegen/csharp/http_client.dart:92— CSharpHttpClientCodeGen.getCode has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (11 pts), boolean chains 3, ternaries 1 (2 pts), error handling 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.
_DashbotTabState.build (cognitive 17) lib/dashbot/dashbot_tab.dart:27— _DashbotTabState.build has cognitive complexity 17 (threshold 15). Drivers by points: if/else 11 (16 pts), boolean chains 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
OpenApiImportService.extractSpecMeta (cognitive 17) lib/dashbot/services/openapi_import_service.dart:41— OpenApiImportService.extractSpecMeta has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (7 pts), boolean chains 5, ternaries 3, loops 2 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
SettingsModel.fromJson (cognitive 17) lib/models/settings_model.dart:107— SettingsModel.fromJson has cognitive complexity 17 (threshold 15). Drivers by points: error handling 4 (8 pts), if/else 6, boolean chains 2, ternaries 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SettingsModel.== (cognitive 17) lib/models/settings_model.dart:226— SettingsModel.== has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 17. 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.
CollectionStateNotifier.reflectGrpcServices (cognitive 17) lib/providers/collection_providers.dart:1761— CollectionStateNotifier.reflectGrpcServices has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (12 pts), boolean chains 3, ternaries 1 (2 pts) (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
_FormDataBodyState.build (cognitive 17) lib/screens/home_page/editor_pane/details_card/request_pane/request_form_data.dart:37— _FormDataBodyState.build has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8, boolean chains 5, ternaries 4. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
GrpcReflectionService._mapTypeToString (cognitive 17) lib/services/grpc_reflection_service.dart:604— GrpcReflectionService._mapTypeToString has cognitive complexity 17 (threshold 15). Drivers by points: if/else 17. 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.
DartDioCodeGen.generatedDartCode (cognitive 16) lib/codegen/dart/dio.dart:28— DartDioCodeGen.generatedDartCode has cognitive complexity 16 (threshold 15). Drivers by points: if/else 10, boolean chains 3, match/switch 1 (2 pts), ternaries 1 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
_ChatScreenState.build (cognitive 16) lib/dashbot/pages/dashbot_chat_page.dart:56— _ChatScreenState.build has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6, boolean chains 5, ternaries 5. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
RequestApplyService.applyCurl (cognitive 16) lib/dashbot/services/actions/request_apply_service.dart:33— RequestApplyService.applyCurl has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (7 pts), ternaries 3 (5 pts), error handling 2 (3 pts), boolean chains 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Curl.toCurlString (cognitive 16) packages/curl_parser/lib/models/curl.dart:271— Curl.toCurlString has cognitive complexity 16 (threshold 15). Drivers by points: if/else 10, ternaries 1 (3 pts), loops 1 (2 pts), boolean chains 1 (nesting depth added 3). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
EditRequestHeadersState.build (cognitive 16) lib/screens/home_page/editor_pane/details_card/request_pane/request_headers.dart:39— EditRequestHeadersState.build has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7, ternaries 6, boolean chains 3. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
Change coupling clique: request_form_data.dart, request_headers.dart, request_params.dart lib/screens/home_page/editor_pane/details_card/request_pane/request_form_data.dart— 3 files — `lib/screens/home_page/editor_pane/details_card/request_pane/request_form_data.dart`, `lib/screens/home_page/editor_pane/details_card/request_pane/request_headers.dart`, `lib/screens/home_page/editor_pane/details_card/request_pane/request_params.dart` — all change together with no explicit dependency: a fully-connected co-change clique, not 3 separate couplings. They share one concern (thin parallel siblings over a common abstraction), so extract the shared part into ONE unit and the whole clique's coupling clears at once — you do not need to break each pair individually.
Change-coupling hub: collection_pane.dart → environment_page.dart, environments_pane.dart, navbar.dart, page_base.dart lib/screens/home_page/collection_pane.dart— `lib/screens/home_page/collection_pane.dart` changes together with 4 other files — `lib/screens/envvar/environment_page.dart`, `lib/screens/envvar/environments_pane.dart`, `lib/screens/mobile/navbar.dart`, `lib/screens/mobile/widgets/page_base.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.
D4 · Code Duplication· Near-duplicate member family (3 members, 39 shared lines) · ×1
Near-duplicate member family (3 members, 39 shared lines) lib/dashbot/providers/chat_viewmodel.dart:365— lib/dashbot/providers/chat_viewmodel.dart:365-472 | lib/dashbot/services/actions/request_apply_service.dart:33-132 | lib/dashbot/services/actions/request_apply_service.dart:134-253 — These 3 members are variants of one another: a block of 39 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 3 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 3 times.
Near-duplicate member pair (42 shared lines) lib/codegen/java/okhttp.dart:91— lib/codegen/java/okhttp.dart:91-173 | lib/codegen/kotlin/okhttp.dart:85-185 — These two members are variants of one another: 42 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.
D4 · Code Duplication· Edited copy of a member (18 corresponding lines) · ×1
Edited copy of a member (18 corresponding lines) lib/models/settings_model.dart:44— lib/models/settings_model.dart:44-82 | lib/terminal/models/network_log_data.dart:40-74 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Members sharing a duplicated core (7 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (7 members, 50+ identical tokens) lib/screens/home_page/editor_pane/details_card/request_pane/mqtt/mqtt_request_topics.dart:57— lib/screens/home_page/editor_pane/details_card/request_pane/mqtt/mqtt_request_topics.dart:57-289 | lib/screens/home_page/editor_pane/details_card/request_pane/request_form_data.dart:37-232 | lib/screens/home_page/editor_pane/details_card/request_pane/request_headers.dart:39-239 | lib/screens/home_page/editor_pane/details_card/request_pane/request_metadata_grpc.dart:46-233 | lib/screens/home_page/editor_pane/details_card/request_pane/request_params.dart:39-230 | lib/widgets/table_request.dart:20-107 | lib/widgets/table_request_form.dart:21-118 — These 7 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 7 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 7 times.
Duplicated block (49–50 lines × 2) lib/dashbot/services/actions/request_apply_service.dart:64— lib/dashbot/services/actions/request_apply_service.dart:64-112 | lib/dashbot/services/actions/request_apply_service.dart:180-229 — 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 (46–48 lines × 2) lib/dashbot/providers/chat_viewmodel.dart:681— lib/dashbot/providers/chat_viewmodel.dart:681-726 | lib/dashbot/providers/chat_viewmodel.dart:759-806 — 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 (38–41 lines × 2) lib/widgets/table_request.dart:20— lib/widgets/table_request.dart:20-57 | lib/widgets/table_request_form.dart:21-61 — before extracting anything, compare `lib/widgets/table_request.dart` and `lib/widgets/table_request_form.dart` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 87 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (36 lines × 2) lib/widgets/editor.dart:72— lib/widgets/editor.dart:72-107 | lib/widgets/editor_json.dart:144-179 — 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 (31–32 lines × 2) lib/providers/js_runtime_notifier.dart:145— lib/providers/js_runtime_notifier.dart:145-176 | lib/providers/js_runtime_notifier.dart:247-277 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (31 lines × 2) lib/screens/home_page/editor_pane/details_card/request_pane/request_pane_graphql.dart:28— lib/screens/home_page/editor_pane/details_card/request_pane/request_pane_graphql.dart:28-58 | lib/screens/home_page/editor_pane/details_card/request_pane/request_pane_rest.dart:33-63 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (29–31 lines × 2) lib/widgets/card_sidebar_environment.dart:90— lib/widgets/card_sidebar_environment.dart:90-118 | lib/widgets/card_sidebar_request.dart:96-126 — 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 (30 lines × 3) doc/gsoc/2025/codes/example5.dart:120— doc/gsoc/2025/codes/example5.dart:120-149 | doc/gsoc/2025/codes/example5.dart:172-201 | doc/gsoc/2025/codes/example5.dart:224-253 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (27–29 lines × 2) lib/screens/history/history_widgets/his_scripts_tab.dart:22— lib/screens/history/history_widgets/his_scripts_tab.dart:22-50 | lib/screens/home_page/editor_pane/details_card/request_pane/request_scripts.dart:22-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.
Duplicated block (28 lines × 2) lib/dashbot/services/agent/prompt_builder.dart:847— lib/dashbot/services/agent/prompt_builder.dart:847-874 | lib/dashbot/services/agent/prompt_builder.dart:878-905 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (25–28 lines × 2) lib/widgets/table_request.dart:83— lib/widgets/table_request.dart:83-107 | lib/widgets/table_request_form.dart:91-118 — before extracting anything, compare `lib/widgets/table_request.dart` and `lib/widgets/table_request_form.dart` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 87 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (27 lines × 6) doc/gsoc/2025/codes/example4.dart:126— doc/gsoc/2025/codes/example4.dart:126-152 | doc/gsoc/2025/codes/example4.dart:225-251 | doc/gsoc/2025/codes/example4.dart:324-350 | doc/gsoc/2025/codes/example4.dart:423-449 | doc/gsoc/2025/codes/example4.dart:522-548 | doc/gsoc/2025/codes/example4.dart:621-647 — all 6 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (25 lines × 2) lib/screens/home_page/editor_pane/details_card/request_pane/request_headers.dart:70— lib/screens/home_page/editor_pane/details_card/request_pane/request_headers.dart:70-94 | lib/screens/home_page/editor_pane/details_card/request_pane/request_metadata_grpc.dart:64-88 — before extracting anything, compare `lib/screens/home_page/editor_pane/details_card/request_pane/request_headers.dart` and `lib/screens/home_page/editor_pane/details_card/request_pane/request_metadata_grpc.dart` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 163 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (24 lines × 2) lib/codegen/java/okhttp.dart:150— lib/codegen/java/okhttp.dart:150-173 | lib/codegen/kotlin/okhttp.dart:162-185 — `lib/codegen/java/okhttp.dart` and `lib/codegen/kotlin/okhttp.dart` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 4 separate duplicated blocks between them, totalling at least 50 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (23 lines × 2) lib/widgets/splitview_dashboard.dart:33— lib/widgets/splitview_dashboard.dart:33-55 | lib/widgets/splitview_history.dart:33-55 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (19–22 lines × 2) lib/codegen/rust/actix.dart:176— lib/codegen/rust/actix.dart:176-197 | lib/codegen/rust/ureq.dart:178-196 — 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 (17–22 lines × 2) lib/screens/envvar/environments_pane.dart:199— lib/screens/envvar/environments_pane.dart:199-215 | lib/screens/home_page/collection_pane.dart:203-224 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (21 lines × 3) lib/screens/home_page/editor_pane/details_card/request_pane/request_form_data.dart:181— lib/screens/home_page/editor_pane/details_card/request_pane/request_form_data.dart:181-201 | lib/screens/home_page/editor_pane/details_card/request_pane/request_headers.dart:187-207 | lib/screens/home_page/editor_pane/details_card/request_pane/request_metadata_grpc.dart:181-201 — before extracting anything, compare `lib/screens/home_page/editor_pane/details_card/request_pane/request_form_data.dart` and `lib/screens/home_page/editor_pane/details_card/request_pane/request_headers.dart` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 58 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (20 lines × 7) doc/gsoc/2025/codes/example4.dart:43— doc/gsoc/2025/codes/example4.dart:43-62 | doc/gsoc/2025/codes/example4.dart:142-161 | doc/gsoc/2025/codes/example4.dart:241-260 | doc/gsoc/2025/codes/example4.dart:340-359 | doc/gsoc/2025/codes/example4.dart:439-458 | doc/gsoc/2025/codes/example4.dart:538-557 | doc/gsoc/2025/codes/example4.dart:637-656 — all 7 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (20 lines × 3) lib/codegen/rust/actix.dart:144— lib/codegen/rust/actix.dart:144-163 | lib/codegen/rust/reqwest.dart:110-129 | lib/codegen/rust/ureq.dart:143-162 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once.
Duplicated block (19 lines × 5) lib/screens/home_page/editor_pane/details_card/request_pane/mqtt/mqtt_request_topics.dart:251— lib/screens/home_page/editor_pane/details_card/request_pane/mqtt/mqtt_request_topics.dart:251-269 | lib/screens/home_page/editor_pane/details_card/request_pane/request_form_data.dart:194-212 | lib/screens/home_page/editor_pane/details_card/request_pane/request_headers.dart:200-218 | lib/screens/home_page/editor_pane/details_card/request_pane/request_metadata_grpc.dart:194-212 | lib/screens/home_page/editor_pane/details_card/request_pane/request_params.dart:191-209 — before extracting anything, compare `lib/screens/home_page/editor_pane/details_card/request_pane/mqtt/mqtt_request_topics.dart` and `lib/screens/home_page/editor_pane/details_card/request_pane/request_headers.dart` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 41 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (18–19 lines × 3) lib/dashbot/providers/chat_viewmodel.dart:394— lib/dashbot/providers/chat_viewmodel.dart:394-412 | lib/dashbot/services/actions/request_apply_service.dart:51-68 | lib/dashbot/services/actions/request_apply_service.dart:167-184 — before extracting anything, compare `lib/dashbot/providers/chat_viewmodel.dart` and `lib/dashbot/services/actions/request_apply_service.dart` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 51 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (19 lines × 2) lib/providers/js_runtime_notifier.dart:295— lib/providers/js_runtime_notifier.dart:295-313 | lib/providers/js_runtime_notifier.dart:333-351 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (18 lines × 7) doc/gsoc/2025/codes/example4.dart:124— doc/gsoc/2025/codes/example4.dart:124-141 | doc/gsoc/2025/codes/example4.dart:223-240 | doc/gsoc/2025/codes/example4.dart:322-339 | doc/gsoc/2025/codes/example4.dart:421-438 | doc/gsoc/2025/codes/example4.dart:520-537 | doc/gsoc/2025/codes/example4.dart:619-636 | doc/gsoc/2025/codes/example4.dart:718-735 — all 7 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (18 lines × 6) lib/screens/home_page/editor_pane/details_card/request_pane/request_form_data.dart:190— lib/screens/home_page/editor_pane/details_card/request_pane/request_form_data.dart:190-207 | lib/screens/home_page/editor_pane/details_card/request_pane/request_headers.dart:196-213 | lib/screens/home_page/editor_pane/details_card/request_pane/request_metadata_grpc.dart:190-207 | lib/screens/home_page/editor_pane/details_card/request_pane/request_params.dart:187-204 | lib/widgets/table_request.dart:86-103 | lib/widgets/table_request_form.dart:97-114 — before extracting anything, compare `lib/screens/home_page/editor_pane/details_card/request_pane/request_form_data.dart` and `lib/screens/home_page/editor_pane/details_card/request_pane/request_headers.dart` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 58 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (14–17 lines × 2) lib/dashbot/services/actions/auto_fix_service.dart:161— lib/dashbot/services/actions/auto_fix_service.dart:161-177 | lib/dashbot/services/actions/auto_fix_service.dart:201-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.
Duplicated block (16 lines × 7) doc/gsoc/2025/codes/example4.dart:64— doc/gsoc/2025/codes/example4.dart:64-79 | doc/gsoc/2025/codes/example4.dart:163-178 | doc/gsoc/2025/codes/example4.dart:262-277 | doc/gsoc/2025/codes/example4.dart:361-376 | doc/gsoc/2025/codes/example4.dart:460-475 | doc/gsoc/2025/codes/example4.dart:559-574 | doc/gsoc/2025/codes/example4.dart:658-673 — all 7 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (13–15 lines × 2) lib/services/connection_manager.dart:297— lib/services/connection_manager.dart:297-309 | lib/services/connection_manager.dart:418-432 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (14–15 lines × 2) lib/widgets/card_sidebar_environment.dart:75— lib/widgets/card_sidebar_environment.dart:75-89 | lib/widgets/card_sidebar_request.dart:78-91 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (14 lines × 3) lib/providers/collection_providers.dart:996— lib/providers/collection_providers.dart:996-1009 | lib/providers/collection_providers.dart:1014-1027 | lib/providers/collection_providers.dart:1032-1045 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (13–14 lines × 2) lib/screens/history/history_widgets/ai_history_page.dart:43— lib/screens/history/history_widgets/ai_history_page.dart:43-56 | lib/screens/home_page/editor_pane/details_card/request_pane/ai_request/aireq_prompt.dart:59-71 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (13 lines × 28) doc/gsoc/2025/codes/example4.dart:55— doc/gsoc/2025/codes/example4.dart:55-67 | doc/gsoc/2025/codes/example4.dart:82-94 | doc/gsoc/2025/codes/example4.dart:96-108 | doc/gsoc/2025/codes/example4.dart:110-122 | doc/gsoc/2025/codes/example4.dart:154-166 | doc/gsoc/2025/codes/example4.dart:181-193 | doc/gsoc/2025/codes/example4.dart:195-207 | doc/gsoc/2025/codes/example4.dart:209-221 | doc/gsoc/2025/codes/example4.dart:253-265 | doc/gsoc/2025/codes/example4.dart:280-292 | doc/gsoc/2025/codes/example4.dart:294-306 | doc/gsoc/2025/codes/example4.dart:308-320 | doc/gsoc/2025/codes/example4.dart:352-364 | doc/gsoc/2025/codes/example4.dart:379-391 | doc/gsoc/2025/codes/example4.dart:393-405 | doc/gsoc/2025/codes/example4.dart:407-419 | doc/gsoc/2025/codes/example4.dart:451-463 | doc/gsoc/2025/codes/example4.dart:478-490 | doc/gsoc/2025/codes/example4.dart:492-504 | doc/gsoc/2025/codes/example4.dart:506-518 | doc/gsoc/2025/codes/example4.dart:550-562 | doc/gsoc/2025/codes/example4.dart:577-589 | doc/gsoc/2025/codes/example4.dart:591-603 | doc/gsoc/2025/codes/example4.dart:605-617 | doc/gsoc/2025/codes/example4.dart:649-661 | doc/gsoc/2025/codes/example4.dart:676-688 | doc/gsoc/2025/codes/example4.dart:690-702 | doc/gsoc/2025/codes/example4.dart:704-716 — all 28 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (12–13 lines × 2) packages/apidash_core/lib/import_export/har_io.dart:19— packages/apidash_core/lib/import_export/har_io.dart:19-31 | packages/apidash_core/lib/import_export/insomnia_io.dart:24-35 — 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–12 lines × 8) lib/dashbot/services/agent/prompt_builder.dart:669— lib/dashbot/services/agent/prompt_builder.dart:669-676 | lib/dashbot/services/agent/prompt_builder.dart:682-689 | lib/dashbot/services/agent/prompt_builder.dart:695-706 | lib/dashbot/services/agent/prompt_builder.dart:731-738 | lib/dashbot/services/agent/prompt_builder.dart:744-751 | lib/dashbot/services/agent/prompt_builder.dart:781-788 | lib/dashbot/services/agent/prompt_builder.dart:794-801 | lib/dashbot/services/agent/prompt_builder.dart:807-818 — all 8 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (12 lines × 4) lib/screens/home_page/editor_pane/details_card/request_pane/mqtt/mqtt_request_topics.dart:93— lib/screens/home_page/editor_pane/details_card/request_pane/mqtt/mqtt_request_topics.dart:93-104 | lib/screens/home_page/editor_pane/details_card/request_pane/request_headers.dart:102-113 | lib/screens/home_page/editor_pane/details_card/request_pane/request_metadata_grpc.dart:96-107 | lib/screens/home_page/editor_pane/details_card/request_pane/request_params.dart:92-103 — before extracting anything, compare `lib/screens/home_page/editor_pane/details_card/request_pane/mqtt/mqtt_request_topics.dart` and `lib/screens/home_page/editor_pane/details_card/request_pane/request_headers.dart` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 41 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (12 lines × 3) lib/widgets/splitview_dashboard.dart:31— lib/widgets/splitview_dashboard.dart:31-42 | lib/widgets/splitview_equal.dart:26-37 | lib/widgets/splitview_history.dart:31-42 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once.
Duplicated block (11–12 lines × 2) lib/dashbot/services/actions/request_apply_service.dart:35— lib/dashbot/services/actions/request_apply_service.dart:35-45 | lib/dashbot/services/actions/request_apply_service.dart:137-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.
Duplicated block (11 lines × 5) lib/codegen/php/curl.dart:132— lib/codegen/php/curl.dart:132-142 | lib/codegen/php/guzzle.dart:92-102 | lib/codegen/php/http_plug.dart:100-110 | lib/codegen/python/http_client.dart:107-117 | lib/codegen/python/requests.dart:104-114 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 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 5 times.
Duplicated block (11 lines × 3) lib/screens/home_page/editor_pane/details_card/request_pane/request_headers.dart:70— lib/screens/home_page/editor_pane/details_card/request_pane/request_headers.dart:70-80 | lib/screens/home_page/editor_pane/details_card/request_pane/request_metadata_grpc.dart:64-74 | lib/screens/home_page/editor_pane/details_card/request_pane/request_params.dart:60-70 — before extracting anything, compare `lib/screens/home_page/editor_pane/details_card/request_pane/request_headers.dart` and `lib/screens/home_page/editor_pane/details_card/request_pane/request_metadata_grpc.dart` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 163 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (10 lines × 5) lib/screens/home_page/editor_pane/details_card/request_pane/mqtt/mqtt_request_topics.dart:91— lib/screens/home_page/editor_pane/details_card/request_pane/mqtt/mqtt_request_topics.dart:91-100 | lib/screens/home_page/editor_pane/details_card/request_pane/mqtt/mqtt_user_properties.dart:97-106 | lib/screens/home_page/editor_pane/details_card/request_pane/request_headers.dart:100-109 | lib/screens/home_page/editor_pane/details_card/request_pane/request_metadata_grpc.dart:94-103 | lib/screens/home_page/editor_pane/details_card/request_pane/request_params.dart:90-99 — before extracting anything, compare `lib/screens/home_page/editor_pane/details_card/request_pane/mqtt/mqtt_request_topics.dart` and `lib/screens/home_page/editor_pane/details_card/request_pane/request_headers.dart` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 41 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (10 lines × 3) lib/screens/home_page/editor_pane/details_card/request_pane/ai_request/aireq_authorization.dart:31— lib/screens/home_page/editor_pane/details_card/request_pane/ai_request/aireq_authorization.dart:31-40 | lib/screens/home_page/editor_pane/details_card/request_pane/ai_request/aireq_prompt.dart:42-52 | lib/screens/home_page/editor_pane/details_card/request_pane/ai_request/aireq_prompt.dart:68-78 — 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 (9–10 lines × 2) lib/models/settings_model.dart:63— lib/models/settings_model.dart:63-71 | packages/json_explorer/lib/src/json_explorer_theme.dart:157-166 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (9 lines × 3) lib/models/settings_model.dart:73— lib/models/settings_model.dart:73-82 | lib/terminal/models/network_log_data.dart:66-74 | lib/terminal/models/terminal_entry.dart:46-54 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
Duplicated block (7–8 lines × 2) lib/terminal/widgets/terminal_tiles.dart:44— lib/terminal/widgets/terminal_tiles.dart:44-50 | lib/terminal/widgets/terminal_tiles.dart:132-139 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (6 lines × 3) lib/dashbot/providers/chat_viewmodel.dart:371— lib/dashbot/providers/chat_viewmodel.dart:371-376 | lib/dashbot/services/actions/request_apply_service.dart:41-46 | lib/dashbot/services/actions/request_apply_service.dart:144-149 — before extracting anything, compare `lib/dashbot/providers/chat_viewmodel.dart` and `lib/dashbot/services/actions/request_apply_service.dart` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 51 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (6 lines × 2) lib/widgets/previewer_json.dart:403— lib/widgets/previewer_json.dart:403-408 | packages/json_explorer/example/lib/main.dart:365-370 — 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 (32–33 lines × 2) packages/multi_trigger_autocomplete_plus/example/lib/src/options/emoji_autocomplete_options.dart:20— packages/multi_trigger_autocomplete_plus/example/lib/src/options/emoji_autocomplete_options.dart:20-52 | packages/multi_trigger_autocomplete_plus/example/lib/src/options/hashtag_autocomplete_options.dart:20-51 — before extracting anything, compare `packages/multi_trigger_autocomplete_plus/example/lib/src/options/emoji_autocomplete_options.dart` and `packages/multi_trigger_autocomplete_plus/example/lib/src/options/hashtag_autocomplete_options.dart` as WHOLE FILES: this scan already matched 3 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.
Duplicated block (22–23 lines × 3) packages/multi_trigger_autocomplete_plus/example/lib/src/options/emoji_autocomplete_options.dart:22— packages/multi_trigger_autocomplete_plus/example/lib/src/options/emoji_autocomplete_options.dart:22-44 | packages/multi_trigger_autocomplete_plus/example/lib/src/options/hashtag_autocomplete_options.dart:22-43 | packages/multi_trigger_autocomplete_plus/example/lib/src/options/mention_autocomplete_options.dart:23-45 — before extracting anything, compare `packages/multi_trigger_autocomplete_plus/example/lib/src/options/emoji_autocomplete_options.dart` and `packages/multi_trigger_autocomplete_plus/example/lib/src/options/hashtag_autocomplete_options.dart` as WHOLE FILES: this scan already matched 3 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.
Duplicated block (11–12 lines × 3) packages/multi_trigger_autocomplete_plus/example/lib/src/options/emoji_autocomplete_options.dart:46— packages/multi_trigger_autocomplete_plus/example/lib/src/options/emoji_autocomplete_options.dart:46-56 | packages/multi_trigger_autocomplete_plus/example/lib/src/options/hashtag_autocomplete_options.dart:45-55 | packages/multi_trigger_autocomplete_plus/example/lib/src/options/mention_autocomplete_options.dart:45-56 — before extracting anything, compare `packages/multi_trigger_autocomplete_plus/example/lib/src/options/emoji_autocomplete_options.dart` and `packages/multi_trigger_autocomplete_plus/example/lib/src/options/hashtag_autocomplete_options.dart` as WHOLE FILES: this scan already matched 3 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.
Low cohesion: CollectionStateNotifier (LCOM4 5) lib/providers/collection_providers.dart:96— CollectionStateNotifier'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.
No structured logging — No logging or diagnostics emission found. This repository ships a binary its users launch rather than a service you operate, so there is no operator to page — but when a run fails on a user's machine, neither they nor you have anything to read.
Weak hash algorithm packages/better_networking/lib/utils/auth/digest_auth_utils.dart:34— MD5/SHA1 is computed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ (`sha256.convert(…)` from `package:crypto`) for content integrity, or a KDF (bcrypt/Argon2/scrypt) for password storage. If it only derives a non-security identifier (a cache key, an avatar URL, an ETag), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as xxhash or murmurhash says it in code — since the algorithm alone cannot distinguish the two uses. Where a protocol this code does not own fixes the digest (a k-anonymity range query, a legacy signature format), the protocol decides; say so beside the call.
Orphaned file packages/multi_trigger_autocomplete_plus/lib/src/multi_trigger_autocomplete.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/screens/common_widgets/auth/oauth2_field.dart:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/better_networking/lib/utils/auth/oauth2_utils.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/screens/common_widgets/auth/oauth1_fields.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/screens/envvar/environments_pane.dart:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/json_explorer/lib/src/json_explorer_theme.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/screens/home_page/editor_pane/details_card/request_pane/request_form_data.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/codegen/java/httpclient.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/widgets/uint8_audio_player.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/dashbot/pages/dashbot_chat_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/codegen/rust/actix.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/providers/environment_providers.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/codegen/kotlin/okhttp.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/codegen/c/curl.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/services/hive_services.dart:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/better_networking/lib/utils/auth/digest_auth_utils.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/dashbot/widgets/openapi_operation_picker_dialog.dart:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file lib/codegen/php/http_plug.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/utils/har_utils.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/codegen/java/okhttp.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/screens/history/history_sidebar.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/codegen/ruby/faraday.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/screens/mobile/onboarding_screen.dart:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file lib/codegen/dart/dio.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/codegen/rust/reqwest.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.
README/code drift doc/dev_guide/flutter_rust_bridge_experiment.md:120— doc/dev_guide/flutter_rust_bridge_experiment.md changes into `apidash/packages/hurl/rust`, but no such folder exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift doc/security/COMMANDS.md:26— doc/security/COMMANDS.md documents the environment variable `FETCH_LICENSE`, but no code, script or configuration file names it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift doc/user_guide/gateway_proxy.md:52— doc/user_guide/gateway_proxy.md runs `node server.js`, but `server.js` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift doc/user_guide/grpc_user_guide.md:7— doc/user_guide/grpc_user_guide.md links to `images/grpc/grpc_overview.png`, but `doc/user_guide/images/grpc/grpc_overview.png` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift doc/user_guide/grpc_user_guide.md:19— doc/user_guide/grpc_user_guide.md runs `docker compose -f grpc/docker-compose.yml up --build`, but `grpc/docker-compose.yml` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift doc/user_guide/grpc_user_guide.md:37— doc/user_guide/grpc_user_guide.md links to `images/grpc/grpc_quick_start.png`, but `doc/user_guide/images/grpc/grpc_quick_start.png` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift doc/user_guide/grpc_user_guide.md:54— doc/user_guide/grpc_user_guide.md links to `images/grpc/grpc_sidebar_badge.png`, but `doc/user_guide/images/grpc/grpc_sidebar_badge.png` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift doc/user_guide/grpc_user_guide.md:108— doc/user_guide/grpc_user_guide.md links to `images/grpc/grpc_request_screen.png`, but `doc/user_guide/images/grpc/grpc_request_screen.png` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift doc/user_guide/grpc_user_guide.md:144— doc/user_guide/grpc_user_guide.md links to `images/grpc/grpc_reflect.png`, but `doc/user_guide/images/grpc/grpc_reflect.png` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift doc/user_guide/grpc_user_guide.md:158— doc/user_guide/grpc_user_guide.md links to `images/grpc/grpc_proto_import.png`, but `doc/user_guide/images/grpc/grpc_proto_import.png` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift doc/user_guide/grpc_user_guide.md:202— doc/user_guide/grpc_user_guide.md links to `images/grpc/grpc_type_selector.png`, but `doc/user_guide/images/grpc/grpc_type_selector.png` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift doc/user_guide/grpc_user_guide.md:226— doc/user_guide/grpc_user_guide.md links to `images/grpc/grpc_request_message.png`, but `doc/user_guide/images/grpc/grpc_request_message.png` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift doc/user_guide/grpc_user_guide.md:246— doc/user_guide/grpc_user_guide.md links to `images/grpc/grpc_metadata.png`, but `doc/user_guide/images/grpc/grpc_metadata.png` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift doc/user_guide/grpc_user_guide.md:274— doc/user_guide/grpc_user_guide.md links to `images/grpc/grpc_auth.png`, but `doc/user_guide/images/grpc/grpc_auth.png` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift doc/user_guide/grpc_user_guide.md:307— doc/user_guide/grpc_user_guide.md links to `images/grpc/grpc_tls.png`, but `doc/user_guide/images/grpc/grpc_tls.png` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift doc/user_guide/grpc_user_guide.md:328— doc/user_guide/grpc_user_guide.md links to `images/grpc/grpc_response_stream.png`, but `doc/user_guide/images/grpc/grpc_response_stream.png` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift doc/user_guide/grpc_user_guide.md:341— doc/user_guide/grpc_user_guide.md links to `images/grpc/grpc_streaming_send.png`, but `doc/user_guide/images/grpc/grpc_streaming_send.png` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift doc/user_guide/instructions_to_run_generated_code.md:234— doc/user_guide/instructions_to_run_generated_code.md installs the package `System.Net.Http` (`dotnet add package System.Net.Http`), but no project or props file references it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift doc/user_guide/instructions_to_run_generated_code.md:310— doc/user_guide/instructions_to_run_generated_code.md installs the package `RestSharp` (`dotnet add package RestSharp`), but no project or props file references it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift doc/user_guide/instructions_to_run_generated_code.md:560— doc/user_guide/instructions_to_run_generated_code.md runs `node app.js`, but `app.js` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift doc/gsoc/2025/udhay_adithya_j.md:286— doc/gsoc/2025/udhay_adithya_j.md names `lib/services/flutter_js_service.dart`, but no file or folder `lib/services/flutter_js_service.dart` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift doc/gsoc/2026/borgy.md:172— doc/gsoc/2026/borgy.md documents the environment variable `APIDASH_PATH`, but no code, script or configuration file names it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift doc/gsoc/2026/shashwat_pratap_singh.md:77— doc/gsoc/2026/shashwat_pratap_singh.md names `lib/services/storage/workspace_storage.dart`, but no file or folder `lib/services/storage/workspace_storage.dart` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift doc/gsoc/2026/shashwat_pratap_singh.md:78— doc/gsoc/2026/shashwat_pratap_singh.md names `lib/services/workspace_service.dart`, but no file or folder `lib/services/workspace_service.dart` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift doc/gsoc/2026/shashwat_pratap_singh.md:78— doc/gsoc/2026/shashwat_pratap_singh.md names `lib/providers/workspace_lifecycle.dart`, but no file or folder `lib/providers/workspace_lifecycle.dart` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
Duplicated predicate lib/consts.dart:31— `!kIsWeb && (Platform.isIOS || Platform.isAndroid)` appears character-identically in 2 files — lib/consts.dart, packages/better_networking/lib/utils/platform_utils.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/consts.dart:27— `!kIsWeb && (Platform.isMacOS || Platform.isWindows || Platform.isLinux)` appears character-identically in 2 files — lib/consts.dart, packages/better_networking/lib/utils/platform_utils.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/screens/home_page/editor_pane/details_card/response_pane.dart:31— `apiType == APIType.websocket || apiType == APIType.mqtt` appears character-identically in 2 files — lib/screens/home_page/editor_pane/details_card/response_pane.dart, lib/screens/home_page/editor_pane/url_card/send_request_button.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/dashbot/providers/chat_viewmodel.dart:380— `baseUrl.isNotEmpty && url.startsWith(baseUrl)` appears character-identically in 2 files — lib/dashbot/providers/chat_viewmodel.dart, lib/dashbot/services/actions/request_apply_service.dart. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate lib/providers/collection_providers.dart:1999— `grpcModel.streamingType == GrpcStreamingType.client || grpcModel.streamingType == GrpcStreamingType.bidi` appears character-identically in 2 files — lib/providers/collection_providers.dart, lib/screens/home_page/editor_pane/details_card/request_pane/request_pane_grpc.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/codegen/java/async_http_client.dart:167— `hasBody && !requestModel.hasContentTypeHeader` appears character-identically in 4 files — lib/codegen/java/async_http_client.dart, lib/codegen/java/unirest.dart, lib/codegen/python/http_client.dart, lib/utils/har_utils.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/codegen/rust/actix.dart:180— `headersList != null || hasBody || requestModel.hasFormData` appears character-identically in 2 files — lib/codegen/rust/actix.dart, lib/codegen/rust/ureq.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/codegen/go/http.dart:152— `headersList != null || requestModel.hasBody` appears character-identically in 3 files — lib/codegen/go/http.dart, lib/codegen/java/httpclient.dart, lib/codegen/rust/curl_rust.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/providers/history_providers.dart:56— `historyIds == null || historyIds.isEmpty` appears character-identically in 2 files — lib/providers/history_providers.dart, lib/services/history_service.dart. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate lib/codegen/java/okhttp.dart:132— `kMethodsWithBody.contains(method) && requestBody != null` appears character-identically in 5 files — lib/codegen/java/okhttp.dart, lib/codegen/kotlin/okhttp.dart, lib/codegen/rust/actix.dart, lib/codegen/rust/reqwest.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/screens/home_page/editor_pane/details_card/request_pane/request_form_data.dart:131— `pickedResult != null && pickedResult.path.isNotEmpty` appears character-identically in 2 files — lib/screens/home_page/editor_pane/details_card/request_pane/request_form_data.dart, lib/widgets/drag_and_drop_area.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/codegen/php/curl.dart:145— `requestModel.hasBody && !requestModel.hasContentTypeHeader` appears character-identically in 3 files — lib/codegen/php/curl.dart, lib/codegen/php/http_plug.dart, lib/codegen/ruby/faraday.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/codegen/csharp/rest_sharp.dart:135— `requestModel.hasJsonData || requestModel.hasTextData` appears character-identically in 13 files — lib/codegen/csharp/rest_sharp.dart, lib/codegen/go/http.dart, lib/codegen/java/httpclient.dart, lib/codegen/julia/http.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/codegen/c/curl.dart:135— `requestModel.hasTextData || requestModel.hasJsonData` appears character-identically in 5 files — lib/codegen/c/curl.dart, lib/codegen/go/http.dart, lib/codegen/java/async_http_client.dart, lib/codegen/java/unirest.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/screens/common_widgets/ai/ai_model_selector_dialog.dart:40— `snapshot.connectionState == ConnectionState.done && snapshot.hasData && snapshot.data != null` appears character-identically in 2 files — lib/screens/common_widgets/ai/ai_model_selector_dialog.dart, packages/genai/genai_example/lib/main.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.
Disabled test packages/json_explorer/test/golden/json_attribute_test.dart:40— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test packages/json_explorer/test/golden/json_attribute_test.dart:153— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test packages/json_explorer/test/golden/json_attribute_test.dart:211— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test packages/json_explorer/test/golden/json_attribute_test.dart:226— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test packages/json_explorer/test/golden/json_attribute_test.dart:241— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test packages/json_explorer/test/golden/json_data_explorer_test.dart:142— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test packages/json_explorer/test/golden/json_data_explorer_test.dart:207— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test packages/json_explorer/test/golden/multi_size_test.dart:67— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test test/providers/collection_providers_test.dart:54— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 27 significant file(s) lose their only recent owner: lib/services/connection_manager.dart, lib/screens/home_page/editor_pane/details_card/request_pane/mqtt/mqtt_request_pane.dart, lib/services/grpc_reflection_service.dart, lib/screens/home_page/editor_pane/details_card/request_pane/request_pane_grpc.dart, lib/screens/home_page/editor_pane/details_card/realtime_event_stream_view.dart, lib/utils/grpc_utils.dart, lib/screens/home_page/editor_pane/details_card/request_pane/ws/ws_message_editor.dart, lib/screens/home_page/editor_pane/details_card/request_pane/mqtt/mqtt_request_topics.dart (+19 more). Pair on, review, or document these before any departure.
Off-boarding risk: anonymized user #2 — If anonymized user #2 becomes unavailable, 12 significant file(s) lose their only recent owner: lib/screens/common_widgets/auth/oauth2_field.dart, lib/dashbot/services/openapi_import_service.dart, lib/dashbot/prompts/debug_api_error.dart, packages/better_networking/lib/utils/auth/oauth2_utils.dart, lib/dashbot/services/actions/request_apply_service.dart, lib/screens/common_widgets/auth/oauth1_fields.dart, lib/dashbot/pages/dashbot_chat_page.dart, lib/dashbot/widgets/openapi_operation_picker_dialog.dart (+4 more). Pair on, review, or document these before any departure.
Documentation: no project overview README.md— The opening paragraph ('API Dash is a beautiful AI powered open-source cross-platform API Client that can help you easily create & customize your API requests, visually inspect responses') describes what the project does but does not state what the repository is for or its scope. Add an overview section stating the repository's purpose (the API dash initiative) and what it provides.
Documentation: no installation or build instructions README.md— The root README has no installation, build, or setup instructions; only a 'Please support this initiative by giving this project a Star ⭐️' line. Add an install section covering how to get started (clone the repo, run flutter pub get, and any prerequisites).
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 (41 single-owned of 231 analysed files in total, counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated and example/demo trees and test files identified by path convention, largest first; 231 of the 536 production source files in this repository met that bar). They are anonymized user #3 (2 file(s)) — spread or document their files in the same way, at lower priority than the named off-boarding risks above. The files folded here: packages/genai/lib/utils/ai_request_utils.dart, packages/apidash_core/lib/utils/curl_utils.dart.
No ADRs found — No ADRs found. The recognised ADR directories in this tree were read — `doc/proposals` — and none of their files is a decision record (a README, index or template page does not count). What was searched, so you can tell an empty log from a search that missed one: every directory under the tree (build output, dependencies and VCS metadata excepted), for a document that is either any non-index page inside a recognised ADR directory, whatever its name and however deeply nested (`docs/adr/use-postgres.md`, `docs/adr/2024/0001-x.md`); or a file anywhere whose name is ADR-shaped (`0001-use-postgres.md`, `adr-012-caching.md`); or, when neither turned anything up, a document carrying the decision-record signature (an "Architecture Decision Record" heading, or Status / Context / Decision / Consequences as section headings). A decision log that clears none of these — unnumbered files outside any recognised directory, without those headings — is not seen by this check and this row is then wrong. If that is your case, say so rather than renaming anything; otherwise, consider recording architectural decisions in `docs/adr/`.
D26 · Project Cohesion· Projects may be oversized for their cohesion · ×1
Projects may be oversized for their cohesion — 1 of 13 project(s) overshoot their size bounds, lowering Project Cohesion to 8.5/10. The most over is `(repository root)` (43702 LoC, 382 module-visible types across 67 directories). Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
D34 · Knowledge Freshness· Further orphaned files (smaller) · ×1
Further orphaned files (smaller) — 61 smaller file(s) also have no living knowledge — folded into the freshness score and metrics rather than raised one row each — most significant first: packages/multi_trigger_autocomplete_plus/lib/src/multi_trigger_autocomplete.dart, lib/screens/common_widgets/auth/oauth2_field.dart, packages/better_networking/lib/utils/auth/oauth2_utils.dart, lib/screens/common_widgets/auth/oauth1_fields.dart, lib/screens/envvar/environments_pane.dart, packages/json_explorer/lib/src/json_explorer_theme.dart, lib/screens/home_page/editor_pane/details_card/request_pane/request_form_data.dart, lib/codegen/java/httpclient.dart (and 53 more) (64 orphaned of 231 analysed files in total, counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated and example/demo trees and test files identified by path convention, largest first; 231 of the 536 production source files in this repository met that bar). Attach the read to the next change that touches one of them: have a second person review that change, and leave behind a short comment or test recording what the file is for, so the knowledge comes back at the cost of a change you were making anyway.
IC1 · Incompleteness & stubs· Member throws UnsupportedError · ×1
Member throws UnsupportedError packages/json_field_editor/lib/src/json_highlight/json_highlight.dart:71— `createSpecialText`'s body only throws an UnsupportedError or an UnimplementedError that gives its reason — sometimes a deliberate refusal, often an unfinished stub. Confirm it's intentional.
No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
P10 · Library API & versioning· Large public API surface · ×1
Large public API surface — 114/118 types (97%) declared in the published library are public. For a library, every public type is a stability contract — keep implementation types off the surface and expose only the intended API.
No security response headers detected — None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is set on a response this repository's Dart server sends — defense in depth, even when a proxy could set them. (−2.0 on this card.) The server: packages/better_networking/lib/services/oauth_callback_server.dart:25 — `HttpServer.bind(`.
No inbound request validation detected — No handler of this repository's Dart server answers 400, 413 or 422 (`Response.badRequest`, `HttpStatus.badRequest`, `statusCode = 400`) and no validation package (luthor, acanthis, ez_validator, json_schema, …) is imported — nothing shows inbound requests being checked, and refused, before a handler acts on them. A check that answers its failure with 200 and an error body is not seen. (−2.0 on this card.) The server: packages/better_networking/lib/services/oauth_callback_server.dart:25 — `HttpServer.bind(`.
Silent fallback default in catch lib/utils/grpc_utils.dart:44— `parseProtoFile` turns every thrown error into `{}` — a data error becomes a silent behavior change with no trail. Log the error or rethrow it. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment at the `catch` or in the `///` doc, and the row stops firing.
Outdated: code_builder — `code_builder` is locked at 4.11.1 but 4.13.0 is the current stable release on pub.dev, and it already satisfies the `^4.11.1` constraint declared in pubspec.yaml — so the lockfile is behind this repository's own declared range. Run `dart pub upgrade code_builder` and commit the updated pubspec.lock.
Outdated: dart_style — `dart_style` is locked at 3.1.6 but 3.1.14 is the current stable release on pub.dev, and it already satisfies the `^3.1.6` constraint declared in pubspec.yaml — so the lockfile is behind this repository's own declared range. Run `dart pub upgrade dart_style` and commit the updated pubspec.lock.
Outdated: flutter_markdown_plus — `flutter_markdown_plus` is locked at 1.0.7 but 1.0.12 is the current stable release on pub.dev, and it already satisfies the `^1.0.7` constraint declared in pubspec.yaml — so the lockfile is behind this repository's own declared range. Run `dart pub upgrade flutter_markdown_plus` and commit the updated pubspec.lock.
Outdated: flutter_riverpod — `flutter_riverpod` is locked at 3.2.1 but 3.4.3 is the current stable release on pub.dev, and it already satisfies the `^3.2.1` constraint declared in pubspec.yaml — so the lockfile is behind this repository's own declared range. Run `dart pub upgrade flutter_riverpod` and commit the updated pubspec.lock.
Outdated: flutter_svg — `flutter_svg` is locked at 2.2.4 but 2.3.0 is the current stable release on pub.dev, and it already satisfies the `^2.2.4` constraint declared in pubspec.yaml — so the lockfile is behind this repository's own declared range. Run `dart pub upgrade flutter_svg` and commit the updated pubspec.lock.
Outdated: hive_ce_flutter — `hive_ce_flutter` is locked at 2.3.4 but 2.5.0 is the current stable release on pub.dev, and it already satisfies the `^2.3.4` constraint declared in pubspec.yaml — so the lockfile is behind this repository's own declared range. Run `dart pub upgrade hive_ce_flutter` and commit the updated pubspec.lock.
Outdated: hooks_riverpod — `hooks_riverpod` is locked at 3.2.1 but 3.4.3 is the current stable release on pub.dev, and it already satisfies the `^3.2.1` constraint declared in pubspec.yaml — so the lockfile is behind this repository's own declared range. Run `dart pub upgrade hooks_riverpod` and commit the updated pubspec.lock.
Outdated: intl — `intl` is locked at 0.20.2 but 0.20.3 is the current stable release on pub.dev, and it already satisfies the `^0.20.2` constraint declared in pubspec.yaml — so the lockfile is behind this repository's own declared range. Run `dart pub upgrade intl` and commit the updated pubspec.lock.
Outdated: json_annotation — `json_annotation` is locked at 4.11.0 but 4.12.0 is the current stable release on pub.dev, and it already satisfies the `^4.11.0` constraint declared in pubspec.yaml — so the lockfile is behind this repository's own declared range. Run `dart pub upgrade json_annotation` and commit the updated pubspec.lock.
Outdated: just_audio — `just_audio` is locked at 0.10.5 but 0.10.6 is the current stable release on pub.dev, and it already satisfies the `^0.10.5` constraint declared in pubspec.yaml — so the lockfile is behind this repository's own declared range. Run `dart pub upgrade just_audio` and commit the updated pubspec.lock.
Outdated: lottie — `lottie` is locked at 3.3.2 but 3.6.1 is the current stable release on pub.dev, and it already satisfies the `^3.3.2` constraint declared in pubspec.yaml — so the lockfile is behind this repository's own declared range. Run `dart pub upgrade lottie` and commit the updated pubspec.lock.
Outdated: markdown — `markdown` is locked at 7.3.0 but 7.3.1 is the current stable release on pub.dev, and it already satisfies the `^7.3.0` constraint declared in pubspec.yaml — so the lockfile is behind this repository's own declared range. Run `dart pub upgrade markdown` and commit the updated pubspec.lock.
Outdated: mime — `mime` is locked at 2.0.0 but 2.1.0 is the current stable release on pub.dev, and it already satisfies the `^2.0.0` constraint declared in pubspec.yaml — so the lockfile is behind this repository's own declared range. Run `dart pub upgrade mime` and commit the updated pubspec.lock.
Outdated: mqtt_client — `mqtt_client` is locked at 10.11.11 but 10.13.0 is the current stable release on pub.dev, and it already satisfies the `^10.11.11` constraint declared in pubspec.yaml — so the lockfile is behind this repository's own declared range. Run `dart pub upgrade mqtt_client` and commit the updated pubspec.lock.
Outdated: multi_split_view — `multi_split_view` is locked at 3.6.1 but 3.6.2 is the current stable release on pub.dev, and it already satisfies the `^3.6.1` constraint declared in pubspec.yaml — so the lockfile is behind this repository's own declared range. Run `dart pub upgrade multi_split_view` and commit the updated pubspec.lock.
Outdated: path_provider — `path_provider` is locked at 2.1.5 but 2.1.6 is the current stable release on pub.dev, and it already satisfies the `^2.1.2` constraint declared in pubspec.yaml — so the lockfile is behind this repository's own declared range. Run `dart pub upgrade path_provider` and commit the updated pubspec.lock.
Outdated: printing — `printing` is locked at 5.14.2 but 5.15.1 is the current stable release on pub.dev, and it already satisfies the `^5.13.4` constraint declared in pubspec.yaml — so the lockfile is behind this repository's own declared range. Run `dart pub upgrade printing` and commit the updated pubspec.lock.
Outdated: pub_semver — `pub_semver` is locked at 2.2.0 but 2.2.1 is the current stable release on pub.dev, and it already satisfies the `^2.1.5` constraint declared in pubspec.yaml — so the lockfile is behind this repository's own declared range. Run `dart pub upgrade pub_semver` and commit the updated pubspec.lock.
Outdated: riverpod — `riverpod` is locked at 3.2.1 but 3.4.3 is the current stable release on pub.dev, and it already satisfies the `^3.2.1` constraint declared in pubspec.yaml — so the lockfile is behind this repository's own declared range. Run `dart pub upgrade riverpod` and commit the updated pubspec.lock.
Outdated: shared_preferences — `shared_preferences` is locked at 2.5.4 but 2.5.6 is the current stable release on pub.dev, and it already satisfies the `^2.5.4` constraint declared in pubspec.yaml — so the lockfile is behind this repository's own declared range. Run `dart pub upgrade shared_preferences` and commit the updated pubspec.lock.
Outdated: stac — `stac` is locked at 1.3.1 but 1.6.0 is the current stable release on pub.dev, and it already satisfies the `^1.3.1` constraint declared in pubspec.yaml — so the lockfile is behind this repository's own declared range. Run `dart pub upgrade stac` and commit the updated pubspec.lock.
Outdated: url_launcher — `url_launcher` is locked at 6.3.2 but 6.3.3 is the current stable release on pub.dev, and it already satisfies the `^6.3.2` constraint declared in pubspec.yaml — so the lockfile is behind this repository's own declared range. Run `dart pub upgrade url_launcher` and commit the updated pubspec.lock.
Outdated: uuid — `uuid` is locked at 4.5.3 but 4.6.0 is the current stable release on pub.dev, and it already satisfies the `^4.5.3` constraint declared in pubspec.yaml — so the lockfile is behind this repository's own declared range. Run `dart pub upgrade uuid` and commit the updated pubspec.lock.
Outdated: vector_graphics_compiler — `vector_graphics_compiler` is locked at 1.2.0 but 1.3.2 is the current stable release on pub.dev, and it already satisfies the `^1.2.0` constraint declared in pubspec.yaml — so the lockfile is behind this repository's own declared range. Run `dart pub upgrade vector_graphics_compiler` and commit the updated pubspec.lock.
Outdated: video_player — `video_player` is locked at 2.11.0 but 2.14.1 is the current stable release on pub.dev, and it already satisfies the `^2.11.0` constraint declared in pubspec.yaml — so the lockfile is behind this repository's own declared range. Run `dart pub upgrade video_player` and commit the updated pubspec.lock.
+ 2 more in this group — see findings.md.
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.
trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
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 01a1695a-a03d-7aa5-9a30-47ba279cf853 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 18 · Warnings: 403 · Recommendations: 131 · Info: 27 — Appendix A · all findings · full markdown report.
Generated by Watchdog — deterministic code-health analysis. 23-10-2026 @ 15:21 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.