Public report of openci-org/openci, published 17 November 2026. It has the same score, grades and number of findings as the full report. The details of security findings (where they are in the code, which known vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive report Measured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.11.4). Assert signed this survey and filed it in the standard's public register, where anyone can look it up by its survey ID. Check this survey → Signed and filed in the standard's public register, 17 November 2026, 21:23 UTC · Survey ID cd_8456243a10724717ba2837a824d242af

openci-org/openci

Measured 17 November 2026, 21:21 UTC, at code version 84a4029

First survey, so nothing to compare with yet
CAI score 51.3out of 100 At risk

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: 40,323 lines of product code in 32 projects, tests not counted · Estimated rebuild effort: about 0.5 person-years · Weakest lens: Production Readiness, 35.0

Findings by how serious they are

56 critical 461 serious 50 minor

6 dimensions are left out of the score. For each one, we either couldn't measure it in this code, or found no evidence of the safeguard we look for, such as a tested backup restore. They count neither for nor against the score, and Limitations lists each one with its reason.

This survey was produced by

Assert small markCanine Code Analyzer
Producer
Canine Development
Analyzer
Canine Code Analyzer engine 1.0.0
Measured
17 November 2026, 21: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 the Canine Code Analyzer. It is open to any tool that implements it, and today the Canine Code Analyzer is the only one that does.

A critical security finding is open, such as a library with a known critical vulnerability or a password or key found in the code. The score itself is unchanged, but its band shows At risk until the finding is fixed. See the Security and Compliance lens.

The score is deterministic, which means the same code always gets the same score. We work it out with tools that follow published rules, and an AI model never decides it, so anyone who applies the same rules to the same code gets the same number. How it is done is explained under Methodology ▸

73of 73 dimensions measured by tools.
558of 567 findings point to an exact file and line, so you can open each one in the code. The other 9 concern the repository as a whole, such as missing documentation.
73dimensions across 8 lenses, read from 40,323 lines of product code in 32 projects.
Chapters

Executive summary

openci-org/openci is rated At risk because critical security findings are open, most of them leaked passwords or keys. Its score is held back because two passwords or keys sit in the current code and we found no working pipeline that builds or tests changes to the code. It scores 51.3 out of 100, which the At risk rating leaves unchanged.

Production Readiness, at 35.0, is the weakest lens and counts most in the score. The best first step is replacing the two exposed passwords or keys and switching the old ones off, worth about 13.4 points. Adding an automated build and test pipeline is another step, worth about 5.6 points. Raising Production Readiness to 70 would lift the score to about 64.2.

Nineteen passwords or keys in the code's history and two in the code are open to anyone who can read the repository. Twelve known security holes in the packages the code depends on can be used by attackers, and three settings leave the servers or containers unsafe. Replacing each exposed password or key, updating the vulnerable packages and correcting the unsafe settings would close these risks. Fixing the weaknesses the scanner points to would fix the two security weaknesses in the code. Giving the shared object a factory instead of the short-lived one would take care of the 14 shared objects holding on to short-lived ones.

The product code is 40,323 lines, about €75,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 for The 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.
Production Readiness 35.0 · counts for 45%Maturity 58.7 · counts for 25%Accessibility 66.5 · counts for 14%Security and Compliance 67.4 · counts for 8%Code Health 67.9 · counts for 4%Architecture 78.1 · counts for 2%Domain Modelling 100.0 · counts for 1%Performance 100.0 · counts for 1%

If Production Readiness rose from 35.0 to 70, the lowest score rated Strong, the score would rise from 51.3 to about 64.2.

Code composition: what the lines of code are
Product code 51%Tests 49%
Rebuild cost: about €75,000 · Estimate
Cost to rebuild€25,000 to €120,000, for 413 to 1,311 hours of work, about 0.5 person-years for one engineer
Difficulty of the problemStandard, 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.
SizeMedium: 40,323 lines of product code
What it is notNot a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one.

How the estimate is made: We price the hours a team would need to write this code again, at €60 to €95 an hour. Declarations and boilerplate are priced at a fast rate and logic at a slower one, and the logic is then multiplied by the difficulty of the problem and by the quality factor. The estimate can be about 30% off either way, and it moves most with the hourly rate and the difficulty. For this code, every line is priced as straight logic, which keeps the estimate on the low side.

Top priorities

The three actions that raise the score most for the work they take. The full ranked list is in the Roadmap.

1
Resolve the 2 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (2).
Raises the score by about 13.4 points · Low effort · REDACTED Scanning
2
Resolve the 1 No ADRs found finding(s) in ADR Quality — start with server.dart.
Raises the score by about 2.9 points · Low effort · ADR Quality
3
Add a CI workflow that builds and runs the test suite on every push/PR.
The repository declares its tests as `npm test --workspace=openci-website` (`apps/website/package.json`): run that.
Raises the score by about 5.6 points · Medium effort · CI/CD gates

Diagnosis: what the measurements show together

Each conclusion below combines several dimensions into one point that no single dimension shows, and lists the measurements it rests on.

Where the investment is most exposed · Value at risk
This code would cost about €75,000 to build again, about 0.5 person-years of work. Its weakest lens is Production Readiness, at 35.0 (Weak). Production Readiness is about whether the product is ready to run in production and to change without breaking. Because the weakest lens counts most in the score, work on Production Readiness also moves the score most.
Based on: the rebuild estimate · the Production Readiness grade · how much each lens counts
What to do: Start with the Production Readiness actions in Top priorities.
If you do one thing first · First action
Resolve the 2 Leaked secret finding(s) in REDACTED Scanning. Of all the actions in this report, it raises the score most for the work it takes: about 13.4 points for low effort, because it clears the 2 REDACTED Scanning findings. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
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.8 out of 10. Code at that level is slower to change than clean code, and we estimate the extra work at 3% to 7% on every change. The history of the code shows how much it changes: about 157,977 lines over the last 90 days, which is about 640,684 lines a year. At that pace, the extra work comes to an estimated 47.5 to 285.2 engineer-days a year, and it grows as more code changes.
How this is estimated: The number of changed lines is measured from the history of the code. The rest rests on two assumptions of our own: code scoring 8 out of 10 or more adds no extra work, and each point below 8 adds 2.5% to 5.6% to every change, never less than 2% to 5% and never more than 40% to 60% in all; and an engineer changes 150 to 400 lines in a day. The result is a range for planning, not a measurement.
Based on: Cyclomatic Complexity · Cognitive Complexity · Code Duplication · Cohesion (LCOM4) · the code's change history
What to do: Start with the files listed under Churn × Complexity Hotspots, which change often and are hard to read, because that is where the extra work is paid most often.

Architecture — module dependency graph

Project dependencies, layered top-to-bottom; arrows show direction. Any dashed red edge points upward or sideways, which only happens where the projects form a dependency cycle. A graph without cycles has none.

arch :app :app @openci/billing-admin billing-admin @openci/builds-admin builds-admin @openci/dispatch-admin dispatch-admin @openci/github-admin github-admin @openci/logs-admin logs-admin @openci/secrets-admin secrets-admin @openci/teams-admin teams-admin @openci/webhooks-admin webhooks-admin android android dashboard dashboard macos_updater (pub) macos_updater (pub) dashboard->macos_updater (pub) openci_shared openci_shared dashboard->openci_shared firebase-dev firebase-dev firebase-dev->@openci/billing-admin firebase-dev->@openci/builds-admin firebase-dev->@openci/dispatch-admin firebase-dev->@openci/github-admin firebase-dev->@openci/logs-admin firebase-dev->@openci/secrets-admin firebase-dev->@openci/teams-admin firebase-dev->@openci/webhooks-admin landing-page landing-page macos_updater (SwiftPM) macos_updater (SwiftPM) openci_cli_plus openci_cli_plus openci_cli_plus->openci_shared openci_dart_functions openci_dart_functions openci_dart_functions->openci_shared openci_workflow openci_workflow openci_workflows openci_workflows openci_workflows->openci_workflow __more__ +1 more projects

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.

94 modules, with 53 dependencies between them. Every module uses only modules listed above it, so there are no loops.

The table shows the 40 modules with the most connections; 54 more are left out to keep it readable.

Which modules use which. The module on each row uses the module in each column, and the number counts the pairs of types that connect them. A cell above the diagonal is part of a loop.
uses →1 apps.landing_page.lib.releases2 firebase.functions.billing.config3 firebase.functions.billing.model4 firebase.functions.billing.store5 firebase.functions.build_dispatch6 firebase.functions.cloud_run_job7 firebase.functions.executor.model8 firebase.functions.executor.orchard9 firebase.functions.github_connection.config10 firebase.functions.github_connection.vault11 firebase.functions.github_webhook12 firebase.functions.log_retention13 firebase.functions.orchard_capacity14 firebase.functions.secrets.service15 firebase.functions.skipped_checks16 repository.generated17 repository.src18 apps.landing_page.lib19 firebase.functions.billing.stripe20 firebase.functions.dispatch_store21 firebase.functions.executor.billing22 firebase.functions.executor.github23 firebase.functions.executor.logs24 firebase.functions.executor.store25 firebase.functions.github_connection26 firebase.functions.github_connection.github27 firebase.functions.secrets.store28 firebase.functions.secrets.vault29 firebase.functions.skipped_check_store30 repository.build_logs31 repository.team32 firebase.functions.billing.service33 firebase.functions.executor.execute34 firebase.functions.github_connection.service35 firebase.functions.queued_checks36 repository.cicd_log37 firebase.functions38 firebase.functions.billing39 firebase.functions.executor40 firebase.functions.github_connection.store
1 apps.landing_page.lib.releases
2 firebase.functions.billing.config
3 firebase.functions.billing.model
4 firebase.functions.billing.store
5 firebase.functions.build_dispatch
6 firebase.functions.cloud_run_job
7 firebase.functions.executor.model
8 firebase.functions.executor.orchard
9 firebase.functions.github_connection.config
10 firebase.functions.github_connection.vault
11 firebase.functions.github_webhook
12 firebase.functions.log_retention
13 firebase.functions.orchard_capacity
14 firebase.functions.secrets.service
15 firebase.functions.skipped_checks
16 repository.generated
17 repository.src
18 apps.landing_page.lib1
19 firebase.functions.billing.stripe1
20 firebase.functions.dispatch_store3
21 firebase.functions.executor.billing11
22 firebase.functions.executor.github2
23 firebase.functions.executor.logs1
24 firebase.functions.executor.store1
25 firebase.functions.github_connection1
26 firebase.functions.github_connection.github1
27 firebase.functions.secrets.store1
28 firebase.functions.secrets.vault1
29 firebase.functions.skipped_check_store1
30 repository.build_logs2
31 repository.team12
32 firebase.functions.billing.service111
33 firebase.functions.executor.execute1111
34 firebase.functions.github_connection.service112
35 firebase.functions.queued_checks1
36 repository.cicd_log71
37 firebase.functions411121111
38 firebase.functions.billing13221
39 firebase.functions.executor1112
40 firebase.functions.github_connection.store111
Uses a module listed above itPart of a loopThe module itself
1 apps.landing_page.lib.releases2 firebase.functions.billing.config3 firebase.functions.billing.model4 firebase.functions.billing.store5 firebase.functions.build_dispatch6 firebase.functions.cloud_run_job7 firebase.functions.executor.model8 firebase.functions.executor.orchard9 firebase.functions.github_connection.config10 firebase.functions.github_connection.vault11 firebase.functions.github_webhook12 firebase.functions.log_retention13 firebase.functions.orchard_capacity14 firebase.functions.secrets.service15 firebase.functions.skipped_checks16 repository.generated17 repository.src18 apps.landing_page.lib19 firebase.functions.billing.stripe20 firebase.functions.dispatch_store21 firebase.functions.executor.billing22 firebase.functions.executor.github23 firebase.functions.executor.logs24 firebase.functions.executor.store25 firebase.functions.github_connection26 firebase.functions.github_connection.github27 firebase.functions.secrets.store28 firebase.functions.secrets.vault29 firebase.functions.skipped_check_store30 repository.build_logs31 repository.team32 firebase.functions.billing.service33 firebase.functions.executor.execute34 firebase.functions.github_connection.service35 firebase.functions.queued_checks36 repository.cicd_log37 firebase.functions38 firebase.functions.billing39 firebase.functions.executor40 firebase.functions.github_connection.storeapps.landing_page.lib.releases1firebase.functions.billing.config2firebase.functions.billing.model3firebase.functions.billing.store4firebase.functions.build_dispatch5firebase.functions.cloud_run_job6firebase.functions.executor.model7firebase.functions.executor.orchard8firebase.functions.github_connection.config9firebase.functions.github_connection.vault10firebase.functions.github_webhook11firebase.functions.log_retention12firebase.functions.orchard_capacity13firebase.functions.secrets.service14firebase.functions.skipped_checks15repository.generated16repository.src17apps.landing_page.lib18firebase.functions.billing.stripe19firebase.functions.dispatch_store20firebase.functions.executor.billing21firebase.functions.executor.github22firebase.functions.executor.logs23firebase.functions.executor.store24firebase.functions.github_connection25firebase.functions.github_connection.github26firebase.functions.secrets.store27firebase.functions.secrets.vault28firebase.functions.skipped_check_store29repository.build_logs30repository.team31firebase.functions.billing.service32firebase.functions.executor.execute33firebase.functions.github_connection.service34firebase.functions.queued_checks35repository.cicd_log36firebase.functions37firebase.functions.billing38firebase.functions.executor39firebase.functions.github_connection.store4011311211111112121111111112171411121111132211112111+54 more modules (most-connected shown)

At a glance — Code Health · 67.9 · Adequate ·

At a glance — Architecture · 78.1 · Adequate · gated by AX1 ·

At a glance — Maturity · 58.7 · Adequate · gated by M2 ·

At a glance — Readiness · 35.0 · Weak · gated by D13, P1, P3 ·

At a glance — Security · 67.4 · Adequate · gated by D28 ·

At a glance — Domain Modelling · 100.0 · Exemplary ·

At a glance — Accessibility · 66.5 · Adequate · gated by AC1 ·

At a glance — Performance · 100.0 · Exemplary ·

Security & Compliance — OWASP Top-10 mapping

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 categoryFindingsSeverity
A02:2025 — Security Misconfiguration25High / Critical
A07:2025 — Authentication Failures22High / Critical
A03:2025 — Software Supply Chain Failures22High / Critical
A05:2025 — Injection6High / Critical

Roadmap

Top priorities: Resolve the 2 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (2); Add a CI workflow that builds and runs the test suite on every push/PR. The repository declares its tests as `npm test --workspace=openci-website` (`apps/website/package.json`): run that; Run what this repository's stack ships: the Dart analyzer's security lints plus `semgrep --config=auto` — locally for now, since there is no CI pipeline here yet, and as a step of the first workflow you add so a security regression fails the build instead of landing.

Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.

Do thisHelpsEffortDimension
Resolve the 2 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (2).+13.4 ptsLowREDACTED Scanning
Resolve the 1 No ADRs found finding(s) in ADR Quality — start with server.dart.+2.9 ptsLowADR Quality
Add a CI workflow that builds and runs the test suite on every push/PR. The repository declares its tests as `npm test --workspace=openci-website` (`apps/website/package.json`): run that.+5.6 ptsMediumCI/CD gates
Run what this repository's stack ships: the Dart analyzer's security lints plus `semgrep --config=auto` — locally for now, since there is no CI pipeline here yet, and as a step of the first workflow you add so a security regression fails the build instead of landing.+5.6 ptsMediumSecurity & performance tooling
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.+2.8 ptsMediumArchitecture documentation
Add a build/run (quick start) section to the root README — the first thing a newcomer needs.+2.0 ptsMediumDocumentation (README)
Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.+1.9 ptsMediumObservability
Add tests that import the unreached modules (directly or through their public entry).+0.8 ptsMediumTest Coverage

File quality

Per-file score 0–10 — a quality signature. Of 112 files carrying findings, judged against the Production bar: 4% slop · 72% mixed · 24% near-clean.

FileScoreBandWorst signal
REDACTED0.0SlopDependency Vulnerabilities: Critical vulnerability: REDACTED
REDACTED0.8SlopREDACTED Scanning: Leaked secret: REDACTED
REDACTED2.5SlopIaC & Container Security: High IaC: REDACTED
REDACTED2.7SlopIaC & Container Security: High IaC: REDACTED
REDACTED3.7SlopDependency Vulnerabilities: Critical vulnerability: REDACTED
REDACTED4.4MixedSecrets (history): REDACTED: REDACTED
REDACTED4.4MixedIaC & Container Security: High IaC: REDACTED
REDACTED4.9MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED5.7MixedStatic Analysis (SAST): High: REDACTED
REDACTED6.9MixedIaC & Container Security: Medium IaC: REDACTED
REDACTED6.9MixedIaC & Container Security: Medium IaC: REDACTED
REDACTED6.9MixedIaC & Container Security: Medium IaC: REDACTED
REDACTED6.9MixedIaC & Container Security: Medium IaC: REDACTED
apps/dashboard/lib/generated/builds/get_build_job.dart7.0MixedCyclomatic Complexity: GetBuildJobJob.== (cyclomatic 31)
apps/dashboard/lib/secret_manager/secret_manager_page.dart7.0MixedCyclomatic Complexity: _AddSecretBottomSheet.build (cyclomatic 26)
apps/dashboard/lib/team/delete_team_bottom_sheet.dart7.0MixedCyclomatic Complexity: DeleteTeamBottomSheet.build (cyclomatic 18)
firebase/functions/executor/github.ts7.0MixedCyclomatic Complexity: ExecutionGitHub.resolveCheckout::readCandidate (cyclomatic 26)
packages/openci_workflow/lib/src/shorebird/shorebird_ci.dart7.0MixedCognitive Complexity: ShorebirdCI.releaseApk (cognitive 17)
apps/dashboard/lib/auth/auth_page.dart7.0MixedCyclomatic Complexity: FirebaseFormSheet.build (cyclomatic 58)
apps/dashboard/lib/generated/secrets/commit_managed_secret.dart7.0MixedCode Duplication: Edited copy of a member (13 corresponding lines)

How the grades work

Every finding carries one of four grades. Three say how serious it is. The fourth says this survey could not settle it — and it is a grade, not a gap.

Critical — 56

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 — 461

Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.

Minor — 50

Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.

Could not be resolved — 6

Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.

Methodology & how to trust this report

This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 73 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.

Every figure here is one of two kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10.

What we checked — 73 dimensions across the health lenses
D1D2D3D4D5D6D10D13D14D15D17D19D20D24D26D28D29D30D31D34D35D43D44AC1AC2AC3AC5AC6AX1AX10AX3AX4AX6AX9DM5GD1IC1M1M2M3M4P1P10P2P3P4P5P6P8PF3R1R10R2R3R4R5R6R7R8R9S1X1X12X13X14X16X2X21X25X27X29X3X5

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
  1. 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, 558 of 567 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.)
  2. Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
  3. 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.

MethodBacksVersionEvaluator
Roslyn static analysisComplexity, cohesion, coupling, dead code, API surface, layering5.3.0✓ deterministic
Native secret scannerHardcoded secrets / credentials1.0.0✓ deterministic
Canine Code Analyzer duplication detector (in-process)Code duplication1.0.0✓ deterministic
Coverage (coverlet / dotnet-coverage)Line & branch coverage10.0.400✓ deterministic
NuGet / dotnetOutdated, vulnerable & deprecated dependencies10.0.400✓ deterministic
git / LibGit2SharpChurn hotspots, knowledge concentration, history2.43.0 · 0.31.0✓ deterministic
gitleaks · semgrep · trivy · checkovSecrets in history, SAST, CVEs, IaC & container, PII / GDPR1.86.0 · 0.69.3 · 3.2.533✓ deterministic

Every finding is locatable in findings.md. Run 01a1eb62-f1a3-700c-b491-262d82ca88b0.

The exact command behind every deep-scan dimension — tool, version, invocation and retained raw output — is in Appendix B — Reproduction & audit trail.

Run transparency — what happened this run

What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.

  • D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: this repository's production source spans .ts, .tsx, .dart, and our analyzer cannot run the .dart test suite(s) — so no coverage was collected for the repository as a whole. The JavaScript/TypeScript half did build and run, and its own line coverage came back at 81.2% — but that is a figure for one half of the product, and we do not publish a partial one as if it were complete. This is OUR limitation, not a defect in the repo — coverage is excluded from the score rather than counted as a near-zero.
  • D10 Test Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The 482 test(s) behind this row are the ones the JavaScript/TypeScript census could read, and this repository also carries at least 183 test source file(s) (.dart) that it cannot: it reads JavaScript/TypeScript test declarations off disk, so a JUnit/pytest-style suite is invisible to it. Skipped tests, zero-assertion tests and the other quality signals on this row are UNMEASURED in that suite — their absence from the counts above is a gap in this analyzer's language coverage, not a finding that those tests are sound.
  • D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability NOT SCORED: this repository's production source includes .dart, and the built-in reliability runner cannot re-run the .dart test suite(s) — so reliability was not measured for the repository as a whole. The JavaScript/TypeScript (node:test via `npm ci --ignore-scripts` in apps/website/ (1 tests); node:test via `npm ci --ignore-scripts` in firebase/ (233 tests)): measured (0 flaky) suite(s) did re-run, and came back with 0 flaky across 1 measured tier(s) — but that is a figure for one half of the product, and we do not publish a partial one as if it were complete. This is OUR limitation, not a defect in the repo — test reliability is excluded from the score rather than counted.
  • D12 Dependency Hygiene — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Not scored — 2 Maven/Gradle manifest(s) were read, stating a version for 0 dependency(ies) and leaving 0 to a parent or an imported BOM, but no build resolved the dependency graph, so the outdated signal was not established. NOT a finding that these dependencies are current or healthy.
  • D14 License Compliance — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares package.json, but the licence verdict published here was taken over its pub package dependencies. Nothing was read about its npm dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
  • D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (3 contributor(s) across 2473 commit(s) sampled, automation and bot accounts excluded). One of them holds 100% of the history; the other 2 hold 0% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
  • D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22's deterministic call-shape rules are gated per language (docs/plans/deterministic-engine.md, P5; C# and each NeutralApiArms arm pass): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
  • D24 Comment Value — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
  • D27 Navigability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
  • D31 IaC & Container Security — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Firebase/Dockerfile.executor.dockerignore carries no `FROM` instruction, so it declares no build stage and every REDACTED rule this engine owns — the runtime-hardening, key-material, mutable-clone, no-op-shim, build-context, trust-anchor, install-guard, setuid and world-writable-path rules — is outside its own premise there and returned nothing. That silence is deliberate and correct: with no base image there is no image to reason about. It is reported here because it is NOT the same fact as a clean file, and coverage is stated as 17 of 18 Infrastructure-as-Code manifest(s) fully judged rather than as 100%. The vendor scanners (trivy, checkov) do read these files and their findings above stand; only this engine's own stage-keyed rules are absent. No owner action: a build file with no FROM is a legitimate include fragment.
  • D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `apps/dashboard/android/app/build.gradle.kts`, `apps/website/src/pages/ogp/[...route].ts`, `firebase/functions/orchard_network.ts` produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
  • M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
  • R2 Cyclomatic Complexity — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 22 further occurrence(s) are not listed individually; the score already reflects all 62.
  • X24 Document value interpolated into markup unescaped — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
  • X27 Collection changed while being enumerated — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.

Repo exclusion declarations: 8 pattern(s) declared (.gitattributes linguist-generated/vendored, .editorconfig generated_code) excluded 0 source file(s) from code-quality scoring. Declarations are the repo's own visible statement that a tree is machine-written or vendored — auditable in any diff, honored by GitHub the same way.

Limitations & what we did not check

We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.

Per-dimension blind spots

For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.

  • D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
  • D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
  • D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
  • D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
  • D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
  • D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
  • D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
  • D13 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
  • D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
  • D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
  • D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
  • D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
  • D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
  • D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
  • D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
  • D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
  • D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
  • D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
  • D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
  • D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
  • D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
  • D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
  • D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
  • AC1 Text alternatives: Alt-text is detected structurally — the scan sees that an alternative EXISTS, not whether it meaningfully describes the image, and decorative-vs-missing is judged by attribute shape; runtime-injected images and a non-role=img decorative svg are out of scope. This is accessibility readiness, never a WCAG conformance claim.
  • AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
  • AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
  • AC5 ARIA correctness: ARIA correctness is checked against the static role/attribute shape — roles/attributes set dynamically aren't seen, a valid role says nothing about whether it matches the element's real behaviour, and required-state checks are suppressed when a JSX spread could supply them. The two-branch toggle check (a control whose state is conveyed only by which of two mutually exclusive branches renders) reads CONDITIONALS THAT ARE ATTRIBUTES — Vue v-if/v-else/v-show and Alpine x-if/x-show — so the same toggle written as a Svelte {#if} block or a JSX ternary is control flow the markup model never projects as a branch and is not seen at all.
  • AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
  • AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
  • AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
  • M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
  • P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
  • P5 DR & Backup: Backup/restore and disaster-recovery readiness is judged from in-repo evidence — a config that exists is not a tested restore, so the absence of positive evidence is reported as "not evidenced", never scored as present.
  • P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.

Dimensions

D1 · Cyclomatic Complexity5.9 / 10Adequate✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 5.9 / 10 · rule-coverage 100% · ceiling Prevented

64 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was FirebaseFormSheet.build at 58. A further 3 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 purchase.paidPeriod at 32 — they are counted neither in the figure above nor in this dimension's score. 1 file carries no cyclomatic complexity row at all for this reason — every one of its over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: firebase/functions/billing/stripe.ts (stripe.validatePrice at 16). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.

build-job-card-demo.BuildJobCardDemo::getJobStatus (cyclomatic 20) · ×2apps/landing_page/components/build-job-card-demo.tsx:141
FirebaseFormSheet.build (cyclomatic 58)apps/dashboard/lib/auth/auth_page.dart:522
execute.executeBuild (cyclomatic 53)firebase/functions/executor/execute.ts:86
SetupAscKeysCommand.run (cyclomatic 44)apps/openci_cli/lib/src/commands/setup/setup_asc_keys_command.dart:96
TeamSecrets.execute (cyclomatic 39)firebase/functions/secrets/service.ts:49

+ 58 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

  1. Bring the 12 bodies over 30 down to 30 or less in Cyclomatic Complexity — start with FirebaseFormSheet.build (cyclomatic 58), execute.executeBuild (cyclomatic 53), SetupAscKeysCommand.run (cyclomatic 44). — 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 12 together lifts Cyclomatic Complexity from 5.9 to about 6.9/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.

Detailed fixes: d1_recommendation.md · top locations in Appendix A, every location in findings.md.

D2 · Cognitive Complexity4.6 / 10Weak✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 4.6 / 10 · rule-coverage 100% · ceiling Prevented

83 method(s) exceeded the cognitive complexity threshold of 15; the worst was FirebaseFormSheet.build at 79.

build-job-card-demo.BuildJobCardDemo::getJobStatus (cognitive 31) · ×2apps/landing_page/components/build-job-card-demo.tsx:141
FirebaseFormSheet.build (cognitive 79)apps/dashboard/lib/auth/auth_page.dart:522
execute.executeBuild (cognitive 66)firebase/functions/executor/execute.ts:86
OctokitConnectionClient.candidates (cognitive 58)firebase/functions/github_connection/github.ts:102
FirebaseHostingClient.deploy (cognitive 55)packages/openci_workflow/lib/src/firebase_hosting/firebase_hosting_client.dart:49

+ 77 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

  1. Bring the 2 bodies over 60 down to 60 or less in Cognitive Complexity — start with FirebaseFormSheet.build (cognitive 79), execute.executeBuild (cognitive 66). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 2 together lifts Cognitive Complexity from 4.6 to about 5.2/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.

Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.

D3 · God Classes8.2 / 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.

Maturity: Documented → Verified → Prevented · effective 8.2 / 10 · rule-coverage 100% · ceiling Prevented

22 god class(es) detected.

MethodTooLong: AuthPage.build · ×14apps/dashboard/lib/auth/auth_page.dart:32
FileTooLong: secret_manager/secret_manager_page.dart · ×4apps/dashboard/lib/secret_manager/secret_manager_page.dart
FunctionTooLong: build-job-card-demo.BuildJobCardDemo · ×3apps/landing_page/components/build-job-card-demo.tsx:95
ClassTooLong: ExecutionGitHubfirebase/functions/executor/github.ts:52

What to do

  1. Resolve the 14 MethodTooLong finding(s) in God Classes — start with secret_manager_page.dart (3), auth_page.dart (2), self_hosted_setup_form.dart. — One of this dimension's main actionable groups (14 warning-level).
  2. Resolve the 4 FileTooLong finding(s) in God Classes — start with secret_manager_page.dart, site.tsx, auth_page.dart. — One of this dimension's main actionable groups (4 warning-level).
  3. Resolve the 3 FunctionTooLong finding(s) in God Classes — start with build-job-card-demo.tsx, site.tsx, REDACTED. — One of this dimension's main actionable groups (3 warning-level).

Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.

D4 · Code Duplication6.7 / 10Adequate✓ Tool-verified

What it measures: How much of the production code is copy-pasted: the share of production lines inside a reported copy (every copy of a duplicated block or of an edited member, each line once), 10 at none and 0 at a quarter of the lines.

Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), scored on the share of production lines inside a reported copy (each line once; 10 at none, 0 at a quarter). Deterministic.

Maturity: Documented → Verified → Prevented · effective 6.7 / 10 · rule-coverage 100% · ceiling Verified

66 duplicated block group(s) detected. 8.2 % of the production lines (3,305 of 40,323) are in a reported copy. A further 38 rows report members as variants of one another; the share counts each copied line once, however many rows cite it. Measured on part of this repository only: .ts (21% of production source) was not exposed to THIS dimension's token comparison and is not in this count; duplication there is measured by R10 Code Duplication, the frontend lens's card running the same clone algorithm over the JS/TS token stream.

Duplicated block (5 lines × 2) · ×5apps/dashboard/lib/generated/secrets/get_secrets.dart:144
Duplicated block (12 lines × 2) · ×4apps/dashboard/lib/secret_manager/secret_manager_page.dart:1116
Edited copy of a member (15 corresponding lines) · ×3apps/dashboard/lib/generated/builds/get_build_jobs.dart:371
Edited copy of a member (6 corresponding lines) · ×3apps/dashboard/lib/generated/teams/add_team_member.dart:178
Duplicated block (10 lines × 2) · ×3apps/dashboard/lib/generated/logs/get_build_log_state.dart:141

+ 73 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

  1. Resolve the 5 Duplicated block (5 lines × 2) finding(s) in Code Duplication — start with get_secrets.dart, get_my_teams.dart, create_build_step.dart. — One of this dimension's main actionable groups (5 warning-level).
  2. Resolve the 4 Duplicated block (12 lines × 2) finding(s) in Code Duplication — start with secret_manager_page.dart, delete_secret_command.dart, list_teams_command.dart. — One of this dimension's main actionable groups (4 warning-level).
  3. Resolve the 3 Edited copy of a member (15 corresponding lines) finding(s) in Code Duplication — start with get_build_jobs.dart, get_build_log_write_state.dart, REDACTED. — One of this dimension's main actionable groups (3 warning-level).

Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.

D5 · Coupling9.6 / 10Stronggated by 1 serious finding✓ Tool-verified

What it measures: Whether volatile projects sit underneath others that depend on them (so their churn ripples upward), and whether project dependencies form cycles. A widely-depended-on but stable shared/kernel project is healthy, not penalised.

Method: Dependency cycles via elementary-DFS over real .csproj references, plus Martin instability (afferent/efferent) per project. Exhaustive over the reference graph, deterministic.

Coverage: Exhaustive · type-level: afferent/efferent coupling + cycles computed over every production type — the population is all types, not a name convention.

Maturity: Documented → Verified → Prevented · effective 9.6 / 10 · rule-coverage 100% · ceiling Prevented

21 production modules (Gradle+npm+SwiftPM+pub), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; edges a convention plugin adds from buildSrc or build-logic are not visible there; 1 module(s) off the main sequence, with abstractness counted on 11 of the 21 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).

Off the main sequence: openci_workflow

What to do

  1. Resolve the 1 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).

Detailed fixes: d5_recommendation.md · top locations in Appendix A, every location in findings.md.

D6 · Cohesion (LCOM4)10.0 / 10Exemplary✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Verified

0 of 73 classes have LCOM4 above 3.

✓ On the Gold path — maintain.

Detailed fixes: d6_recommendation.md.

D10 · Test Quality9.9 / 10Stronggated by 2 serious findings✓ Tool-verified

What it measures: Whether the tests truly assert behaviour rather than just running the code.

Method: Per-test assertions, skips, and mock references analyzed via Roslyn; structured skip-reason tags (BUG:/ENV:) separate documented deferrals from debt. Deterministic.

Maturity: Documented → Verified → Prevented · effective 9.9 / 10 · rule-coverage 100% · ceiling Prevented

0 skipped, 2 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 482 tests. Measured on the JavaScript/TypeScript suite only — at least 183 test source file(s) (.dart) went unread, so its test quality is unmeasured and is not in these counts.

No assertions: allows a new Google user · ×2firebase/functions/test/auth_signup_policy.test.mjs:12

What to do

  1. Resolve the 2 No assertions finding(s) in Test Quality — start with auth_signup_policy.test.mjs, build_dispatch_functions.test.mjs. — One of this dimension's main actionable groups (2 warning-level).

Detailed fixes: d10_recommendation.md · top locations in Appendix A, every location in findings.md.

D13 · REDACTED Scanning0.0 / 10Critical✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 0.0 / 10 · rule-coverage 100% · ceiling Prevented

2 secret(s) detected. 1 detection(s) were excluded as holding no minted credential in material that runs: a name, reference or comparison rather than a value, a readable phrase or pattern, a value that declares itself fake, or development, test, example, mock or demo material.

REDACTED

What to do

  1. Resolve the 2 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).

Detailed fixes: d13_recommendation.md · top locations in Appendix A, every location in findings.md.

D14 · License Compliance10.0 / 10Exemplary○ Nothing flagged

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.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Verified

0 of 221 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 0 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 62 package(s) locked at an older version the licence read is that of the package's latest analysed release, not of the locked one. ★ COVERAGE OF THIS VERDICT: it grades this repository's pub package dependencies and nothing else. The repository also declares package.json, and the licences of those dependencies were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.

✓ On the Gold path — maintain.

Detailed fixes: d14_recommendation.md.

D15 · Churn × Complexity Hotspots9.8 / 10Stronggated by 24 serious findings✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 9.8 / 10 · rule-coverage 100% · ceiling Documented

Top hotspots: firebase/functions/executor/github.ts (15×49=735); apps/dashboard/lib/auth/auth_page.dart (11×58=638); apps/openci_cli/lib/src/commands/setup/setup_asc_keys_command.dart (13×44=572)

Hotspot: firebase/functions/executor/github.ts · ×24firebase/functions/executor/github.ts:231

What to do

  1. Resolve the 24 Hotspot finding(s) in Churn × Complexity Hotspots — start with github.ts (2), auth_page.dart, setup_asc_keys_command.dart. — One of this dimension's main actionable groups (24 warning-level).

Detailed fixes: d15_recommendation.md · top locations in Appendix A, every location in findings.md.

D17 · Explicit Debt10.0 / 10Exemplary○ Nothing flagged

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.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Prevented

0 deducted task-comment markers across 40323 LoC (0.0/KLoC) → score 10.0. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.

✓ On the Gold path — maintain.

Detailed fixes: d17_recommendation.md.

D19 · Documentation Quality10.0 / 10Exemplary○ Nothing flagged

What it measures: Whether the project's documentation is clear, complete, and useful.

Method: Every README, docs/ document and root guide parsed by its markup and measured in Unicode letters. Published: a runnable or packaged .NET project whose README (or a document it links, or a root guide) shows no example, and a root README naming none of three or more projects. Overview, licence, boilerplate, wall-of-text, empty-section and XML-doc rows are measured and withheld (counted in gaps) after adjudication. Deterministic, exhaustive, advisory.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

2 of 2 documentation facets pass in full. 37 document(s) read across 15 unit(s).

✓ On the Gold path — maintain.

Detailed fixes: d19_recommendation.md.

D20 · ADR Quality0.0 / 10Critical✓ Tool-verified

What it measures: Whether architecture decisions are recorded well (context, decision, consequences).

Method: Every ADR read by its section structure: nine located rules (a missing Decision, Context or Consequences section, a stale status, two records deciding the same question, a dangling supersede link, a number-only title, a single option, no named cost, no status where the log uses one, no enforcement field where the log adopted one), each a fixed deduction from 10; the score is the mean over evaluated records. Deterministic, no model. Advisory.

Maturity: Documented → Verified → Prevented · effective 0.0 / 10 · rule-coverage 100% · ceiling Documented

No architecture decision records were found.

No ADRs foundfirebase/dart_functions/bin/server.dart:26

What to do

  1. Resolve the 1 No ADRs found finding(s) in ADR Quality — start with server.dart. — One of this dimension's main actionable groups (1 recommendation-level).

Detailed fixes: d20_recommendation.md · top locations in Appendix A, every location in findings.md.

D24 · Comment Value10.0 9.8 / 10Exemplary○ Nothing flagged

What it measures: Whether comments are worth it — explaining WHY (valuable) rather than WHAT (redundant).

Method: Every inline C# comment compared word by word with the identifiers, literals and constructs of the code it annotates (taken from the syntax); a comment whose words that code already contains is redundant, as are closing-brace labels and generator template text. Comments giving a reason or a reference are kept; other scripts and languages are not judged. Deterministic, exhaustive, advisory.

Maturity: Documented → Verified → Prevented · effective 9.8 / 10 · rule-coverage 98% · ceiling Documented

0 of 150 judged comments only repeat the code they sit on (0.0 %). 4 comment(s) in another language or script were not judged.

✓ On the Gold path — maintain.

Detailed fixes: d24_recommendation.md.

D26 · Project Cohesion9.4 / 10Exemplary✓ Tool-verified

What it measures: Whether each project is a focused, coherent unit rather than an oversized grab-bag.

Method: Project size overshoot penalties (LoC / public-type count / namespace count, 2-of-3 flag) weighted by log magnitude. Exhaustive across projects, deterministic.

Maturity: Documented → Verified → Prevented · effective 9.4 / 10 · rule-coverage 100% · ceiling Documented

1 of 32 build units (Gradle, SwiftPM, Xcode, npm, pub) flagged as possibly oversized/incoherent.

Projects may be oversized for their cohesionapps/dashboard/pubspec.yaml:1

✓ On the Gold path — maintain.

Detailed fixes: d26_recommendation.md · top locations in Appendix A, every location in findings.md.

D28 · Secrets (history)0.0 / 10Critical✓ Tool-verified

What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.

Method: REDACTED scan via TWO gitleaks detect passes in an isolated checkout — the full git history, then a second --no-git pass over the working tree as it stands — merged and de-duplicated by (rule, file, line); each match flagged High. Both invocations are recorded in the audit trail. Exhaustive; when the tool is absent, or when its output cannot be parsed into the expected shape, the dimension is WITHHELD as an explicit measurement gap on our side — unscored and excluded from the lens, never a hedged middling score.

Maturity: Documented → Verified → Prevented · effective 0.0 / 10 · rule-coverage 100% · ceiling Documented

19 finding(s): 0 critical, 19 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.

REDACTED
REDACTED
REDACTED

What to do

  1. Resolve the 18 REDACTED finding(s) in Secrets (history) — start with REDACTED (12), REDACTED (2), REDACTED (2). — One of this dimension's main actionable groups (18 issue-level).
  2. Resolve the 1 High secret finding(s) in Secrets (history) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
  3. Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).

Detailed fixes: d28_recommendation.md · top locations in Appendix A, every location in findings.md.

D29 · Static Analysis (SAST)6.2 / 10Adequate✓ Tool-verified

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).

Maturity: Documented → Verified → Prevented · effective 6.2 / 10 · rule-coverage 100% · ceiling Documented

6 finding(s): 0 critical, 2 high, 2 medium, 2 low. semgrep hit a parse error in 2 file(s) — `apps/website/src/pages/ogp/[...route].ts` (line 21), `firebase/functions/orchard_network.ts` (line 13) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

What to do

  1. Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
  2. Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
  3. Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).

Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.

D30 · Dependency Vulnerabilities0.0 / 10Critical✓ Tool-verified

What it measures: Whether any dependency has a known published vulnerability (CVE), direct or transitive, in ANY ecosystem the repository declares — Dart pub, Elixir and Erlang via Hex, Go modules, Java and Kotlin via Maven/Gradle, JavaScript/npm, .NET/NuGet, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift.

Method: Dependency-CVE scan across every ecosystem the repository declares, scored ONCE. Three sources are unioned and deduplicated by advisory identity (rule id + alias closure, CVE<->GHSA) scoped to package+version, keeping the worst severity: `osv-scanner --recursive` over osv.dev for Dart pub, Elixir/Hex (and Erlang, whose `rebar.lock` syft first converts to a CycloneDX SBOM the scanner reads, with rows attributed back to the lock), Go, Java and Kotlin via Maven/Gradle (and Scala, whose sbt build's pinned direct declarations are written into a CycloneDX SBOM the scanner reads, with rows attributed back to the build file), npm, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift; `trivy fs --scanners vuln` for npm lockfiles; and `dotnet list package --vulnerable --include-transitive` for NuGet (with per-advisory collapse of the project x target-framework fan-out), plus a DECLARED-dependency arm that resolves a published gem's gemspec against rubygems.org where no Gemfile.lock is committed. `SeverityScore(c,h,m,l, normalizer 8.0)`. NotApplicable only when NO ecosystem is readable; if any applicable ecosystem could not be scanned the findings are REPORTED and the score is withheld. Supersedes the npm and OSV arms, retired 2026-09-05. Advisory since rubric-2026.11.2 (CAI decision 0006): every row is a match against a vulnerability database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.

Maturity: Documented → Verified → Prevented · effective 0.0 / 10 · rule-coverage 100% · ceiling Documented

22 finding(s): 4 critical, 8 high, 8 medium, 2 low.

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

What to do

  1. Resolve the 8 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (7), REDACTED. — One of this dimension's main actionable groups (8 issue-level).
  2. Resolve the 2 Critical vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 issue-level).
  3. Resolve the 2 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).

Detailed fixes: d30_recommendation.md · top locations in Appendix A, every location in findings.md.

D31 · IaC & Container Security7.4 7.0 / 10Adequate✓ Tool-verified

What it measures: Whether Dockerfiles / Terraform / Kubernetes config follow security best practices.

Method: IaC/container misconfiguration scan via trivy config (REDACTED/Terraform/K8s/Helm/CloudFormation); severity rules to 0-10 moderate normalizer. NotApplicable without manifests. Exhaustive, deterministic.

Maturity: Documented → Verified → Prevented · effective 7.0 / 10 · rule-coverage 94% · ceiling Documented

25 finding(s): 0 critical, 3 high, 14 medium, 8 low.

REDACTED
REDACTED
REDACTED

What to do

  1. Resolve the 3 High IaC finding(s) in IaC & Container Security — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (3 issue-level).
  2. Resolve the 14 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (3), REDACTED (2), REDACTED (2). — One of this dimension's main actionable groups (14 warning-level).
  3. Resolve the 8 Low IaC finding(s) in IaC & Container Security — start with REDACTED (4), REDACTED, REDACTED. — One of this dimension's main actionable groups (8 recommendation-level).

Detailed fixes: d31_recommendation.md · top locations in Appendix A, every location in findings.md.

D34 · Knowledge Freshness10.0 / 10Exemplary✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

Every significant source file has living knowledge — recently and meaningfully worked. Counted over 143 of the 354 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.

✓ On the Gold path — maintain.

Detailed fixes: d34_recommendation.md.

D35 · Change Coupling10.0 / 10Exemplary✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

No strong hidden change-coupling between production files.

✓ On the Gold path — maintain.

Detailed fixes: d35_recommendation.md.

D43 · Malicious Dependencies10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether any dependency the repository declares is published as MALICIOUS rather than merely vulnerable — a package that is an attacker's work, in any ecosystem osv-scanner reads. Reported apart from D30 because the answer is binary: there is no safe version to upgrade to, and the fix is to remove the package and rotate every credential it could have read.

Method: The same dependency scan D30 reads, partitioned on the scanner's own classification rather than rescanned: a row is MALICIOUS when its id is in the `MAL-` space (the ossf/malicious-packages feed) OR its `database_specific.cwe_ids` carries `CWE-506` ("Embedded Malicious Code"). Both channels are structural; the summary text is deliberately NOT read, because a malicious-package record whose summary says only "Critical severity vulnerability" is a real shape ([GHSA redacted]) and a text matcher misses it. Scored BINARY: any surviving row is 0, whatever its severity and however many CVEs sit beside it — a hostile dependency is not a quantity. Applicability and degradation are D30's: NotApplicable only when no ecosystem is readable, and an unscannable ecosystem degrades rather than reading clean. Advisory since rubric-2026.11.2 (CAI decision 0006): the malicious-package feed is a database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

No dependency in any ecosystem this repository declares is published as malicious.

✓ On the Gold path — maintain.

Detailed fixes: d43_recommendation.md.

D44 · Platform End-of-Life10.0 / 10Exemplary✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 3 platform declaration(s) and 2 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.

✓ On the Gold path — maintain.

Detailed fixes: d44_recommendation.md.

Frontend & cross-cutting dimensions

R = React/JS · M = Maturity · P = Readiness.

AC1 · Text alternatives3.5 / 10Weak✓ Tool-verified

Other · Accessibility — Whether non-text content carries a text alternative — img/area/input[type=image] have alt, a meaningful svg has a title or aria-label, video has a captions track, and object/embed/canvas have a name or fallback content. Static markup readiness, not a WCAG conformance claim.

Method: Static markup-model scan: every img/area/input[type=image] checked for alt, svg[role=img] for a title/aria-label, video for a captions <track>. Components skipped, spreads suppressed. Deterministic, hard fact per element.

Coverage: Population: image/media elements — img, area, input[type=image], svg, video, object, embed, canvas — across the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx); components, hidden subtrees and dynamic-attribute elements are skipped. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is NOT read by any producer, so it contributes no element to this population; where such a frontend is present the card discloses it as an analyzer gap rather than scoring around it.

  • Video with no captions <track> offers no captions. This player's source is set at runtime, so there is no caption file to author here: give the player a way to carry captions — accept a track/captions URL alongside the media and render a <track kind="captions"> when one is supplied — and capture that asset wherever the media enters the product (upload, import or generation). — REDACTED:164

What to do

  • Add a text alternative — alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, an aria-label or inner fallback content on canvas, and a captions <track> on video.
AC2 · Forms & labels10.0 / 10Exemplary○ Nothing flagged

Other · Accessibility — Whether form controls have a programmatic label (an associated label, aria-label or aria-labelledby), buttons have text, links have an accessible name, a click handler on a plain element names the control it declares, fieldsets have a non-empty legend, known UI-library field components carry a label prop, and a placeholder isn't used as the only label. Static markup readiness, not a WCAG conformance claim.

Method: Static markup-model scan: inputs/selects/textareas checked for an associated label[for]/wrapping label/aria-label/aria-labelledby (per document), buttons for accessible text, fieldsets for a legend; placeholder-only labelling flagged. Deterministic, hard fact per control.

Coverage: Population: form controls, buttons, links, fieldsets and known UI-library field components in the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx); components, hidden subtrees and spread/dynamic-attribute elements are skipped, so a control whose label arrives through a spread or a runtime expression is deliberately not judged. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.

AC3 · Page structure5.1 / 10Adequate✓ Tool-verified

Other · Accessibility — Whether pages declare a language (well-formed BCP-47) and a non-empty title, expose exactly one main landmark and a sane heading order with non-empty headings, keep zoom enabled, title their iframes, give data tables header cells, and avoid meta-refresh. Static markup readiness, not a WCAG conformance claim.

Method: Static markup-model scan: html lang, document <title>, a main landmark and heading order on full documents only, plus zoom-disabling viewports, untitled iframes and meta-refresh anywhere. Deterministic, per structural checkpoint.

Coverage: Population: the PARSED MARKUP documents (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx). The page-level checks — lang, title, single main landmark — fire ONCE PER FULL DOCUMENT (an <html> root) and never on a partial or component fragment, so a repo of fragments is assessed only on the per-element checks (heading order, table headers, iframe titles, meta-refresh, zoom). Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.

  • The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en"). — apps/dashboard/web/index.html:2
  • No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. (×3) — apps/dashboard/web/index.html:2, apps/landing_page/app/(en)/layout.tsx:17, apps/landing_page/app/(ja)/layout.tsx:17
  • A page with no <title> gives no name in the tab, history or screen-reader page list. Declare it the way this router does — Next App Router `export const metadata = { title }`, React Router/Remix `export function meta`, TanStack Start `head`, or a Helmet/Head component. (×3) — apps/landing_page/app/(en)/layout.tsx:17, apps/landing_page/app/(ja)/layout.tsx:17, apps/landing_page/app/(redirect)/layout.tsx:17

What to do

  • Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
AC5 · ARIA correctness10.0 / 10Exemplary○ Nothing flagged

Other · Accessibility — Whether ARIA is used correctly — valid non-abstract roles, the ARIA state a role requires, valid (non-misspelled) aria-* attribute names, in-enum values for token-typed aria-* attributes, and no aria-hidden on (or wrapping) a focusable element. Static markup readiness, not a WCAG conformance claim.

Method: Static markup-model scan: role values checked against the WAI-ARIA role set (abstract/invalid flagged), required ARIA state for a role, and aria-hidden on a focusable element. Deterministic, role/attribute level.

Coverage: Population: elements in the PARSED MARKUP files (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx) that carry a role or an aria-* attribute; roles and token values are checked against the ARIA enums exhaustively within that set. An expression-valued (dynamic) role or aria-* value is skipped rather than guessed, and markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.

AC6 · Visual & motion safety10.0 / 10Exemplary○ Nothing flagged

Other · Accessibility — Whether focus outlines aren't removed without a replacement, motion respects prefers-reduced-motion, and literal CSS colour pairs meet contrast — PARTIAL: inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS literals are read (hex/rgb/hsl/named), never computed/runtime/external-CDN colour. Static markup readiness, not a WCAG conformance claim.

Method: Static markup/CSS scan: inline outline:none/0, literal inline colour/background contrast against the 4.5:1 AA floor, and <style>-block animation without a prefers-reduced-motion guard. Deterministic but PARTIAL — only inline styles and in-repo CSS literals are visible.

Coverage: Population: styled elements in the PARSED MARKUP files (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx), plus in-repo <style> blocks, in-repo .css files and CSS-in-JS literals. Colour contrast is computed from LITERAL colour pairs only (hex/rgb/hsl/named, including var() tokens and Tailwind neutral utilities) — computed, runtime-themed and external-CDN colour is never resolved, so this is a partial read of contrast by construction. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.

AX1 · Captive dependencies2.7 / 10Weak✓ Tool-verified

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.

  • `localePreferenceProvider` is a keep-alive Riverpod provider and calls `ref.watch(sharedPreferencesProvider…)`, which is declared auto-dispose (apps/dashboard/lib/utilities/shared_preferences_provider.dart:6). The keep-alive provider listens to it for the life of the ProviderContainer, so `sharedPreferencesProvider` is never disposed — the auto-dispose lifetime it declares never happens, and whatever it holds (a socket, a controller, a stale value) is kept for every later reader. Mark `sharedPreferencesProvider` keepAlive too, make `localePreferenceProvider` auto-dispose, or read it per use outside build. — apps/dashboard/lib/app_locale_provider.dart:32
  • `githubConnectionApiProvider` is a keep-alive Riverpod provider and calls `ref.watch(currentGitHubConnectionContextProvider…)`, which is declared auto-dispose (apps/dashboard/lib/team/current_github_connection_context_provider.dart:8). The keep-alive provider listens to it for the life of the ProviderContainer, so `currentGitHubConnectionContextProvider` is never disposed — the auto-dispose lifetime it declares never happens, and whatever it holds (a socket, a controller, a stale value) is kept for every later reader. Mark `currentGitHubConnectionContextProvider` keepAlive too, make `githubConnectionApiProvider` auto-dispose, or read it per use outside build. — apps/dashboard/lib/team/github_connection_api.dart:14
  • `githubConnectionApiProvider` is a keep-alive Riverpod provider and calls `ref.watch(activeConnectionFirebaseAuthProvider…)`, which is declared auto-dispose (apps/dashboard/lib/connections/active_connection_firebase_auth.dart:11). The keep-alive provider listens to it for the life of the ProviderContainer, so `activeConnectionFirebaseAuthProvider` is never disposed — the auto-dispose lifetime it declares never happens, and whatever it holds (a socket, a controller, a stale value) is kept for every later reader. Mark `activeConnectionFirebaseAuthProvider` keepAlive too, make `githubConnectionApiProvider` auto-dispose, or read it per use outside build. — apps/dashboard/lib/team/github_connection_api.dart:16
  • `githubConnectionApiProvider` is a keep-alive Riverpod provider and calls `ref.read(currentGitHubConnectionContextProvider…)`, which is declared auto-dispose (apps/dashboard/lib/team/current_github_connection_context_provider.dart:8). Read in build, `currentGitHubConnectionContextProvider` has no listener once the read returns, so it is disposed at once — its ref.onDispose closes what it handed out — while `githubConnectionApiProvider` keeps that value for the life of the ProviderContainer. Mark `currentGitHubConnectionContextProvider` keepAlive too, make `githubConnectionApiProvider` auto-dispose, or read it per use outside build. — apps/dashboard/lib/team/github_connection_api.dart:20
  • `teamMembersApiProvider` is a keep-alive Riverpod provider and calls `ref.watch(authStateChangesProvider…)`, which is declared auto-dispose (apps/dashboard/lib/auth/auth_provider.dart:31). The keep-alive provider listens to it for the life of the ProviderContainer, so `authStateChangesProvider` is never disposed — the auto-dispose lifetime it declares never happens, and whatever it holds (a socket, a controller, a stale value) is kept for every later reader. Mark `authStateChangesProvider` keepAlive too, make `teamMembersApiProvider` auto-dispose, or read it per use outside build. — apps/dashboard/lib/team/team_members_api.dart:12
  • `teamMembersApiProvider` is a keep-alive Riverpod provider and calls `ref.watch(activeConnectionFirebaseAuthProvider…)`, which is declared auto-dispose (apps/dashboard/lib/connections/active_connection_firebase_auth.dart:11). The keep-alive provider listens to it for the life of the ProviderContainer, so `activeConnectionFirebaseAuthProvider` is never disposed — the auto-dispose lifetime it declares never happens, and whatever it holds (a socket, a controller, a stale value) is kept for every later reader. Mark `activeConnectionFirebaseAuthProvider` keepAlive too, make `teamMembersApiProvider` auto-dispose, or read it per use outside build. — apps/dashboard/lib/team/team_members_api.dart:14
  • `teamMembersApiProvider` is a keep-alive Riverpod provider and calls `ref.watch(teamsConnectorProvider…)`, which is declared auto-dispose (apps/dashboard/lib/team/teams_connector_provider.dart:11). The keep-alive provider listens to it for the life of the ProviderContainer, so `teamsConnectorProvider` is never disposed — the auto-dispose lifetime it declares never happens, and whatever it holds (a socket, a controller, a stale value) is kept for every later reader. Mark `teamsConnectorProvider` keepAlive too, make `teamMembersApiProvider` auto-dispose, or read it per use outside build. — apps/dashboard/lib/team/team_members_api.dart:15
  • `teamSecretsCallableProvider` is a keep-alive Riverpod provider and calls `ref.watch(activeConnectionFirebaseAuthProvider…)`, which is declared auto-dispose (apps/dashboard/lib/connections/active_connection_firebase_auth.dart:11). The keep-alive provider listens to it for the life of the ProviderContainer, so `activeConnectionFirebaseAuthProvider` is never disposed — the auto-dispose lifetime it declares never happens, and whatever it holds (a socket, a controller, a stale value) is kept for every later reader. Mark `activeConnectionFirebaseAuthProvider` keepAlive too, make `teamSecretsCallableProvider` auto-dispose, or read it per use outside build. — apps/dashboard/lib/secret_manager/secrets_backend.dart:30
  • `routerProvider` is a keep-alive Riverpod provider and calls `ref.listen(authStateChangesProvider…)`, which is declared auto-dispose (apps/dashboard/lib/auth/auth_provider.dart:31). The keep-alive provider listens to it for the life of the ProviderContainer, so `authStateChangesProvider` is never disposed — the auto-dispose lifetime it declares never happens, and whatever it holds (a socket, a controller, a stale value) is kept for every later reader. Mark `authStateChangesProvider` keepAlive too, make `routerProvider` auto-dispose, or read it per use outside build. — apps/dashboard/lib/router/router.dart:16
  • `routerProvider` is a keep-alive Riverpod provider and calls `ref.read(authStateChangesProvider…)`, which is declared auto-dispose (apps/dashboard/lib/auth/auth_provider.dart:31). Read in build, `authStateChangesProvider` has no listener once the read returns, so it is disposed at once — its ref.onDispose closes what it handed out — while `routerProvider` keeps that value for the life of the ProviderContainer. Mark `authStateChangesProvider` keepAlive too, make `routerProvider` auto-dispose, or read it per use outside build. — apps/dashboard/lib/router/router.dart:57
  • `connectionStoreProvider` is a keep-alive Riverpod provider and calls `ref.watch(sharedPreferencesProvider…)`, which is declared auto-dispose (apps/dashboard/lib/utilities/shared_preferences_provider.dart:6). The keep-alive provider listens to it for the life of the ProviderContainer, so `sharedPreferencesProvider` is never disposed — the auto-dispose lifetime it declares never happens, and whatever it holds (a socket, a controller, a stale value) is kept for every later reader. Mark `sharedPreferencesProvider` keepAlive too, make `connectionStoreProvider` auto-dispose, or read it per use outside build. — apps/dashboard/lib/connections/connection_store_provider.dart:14
  • `billingApiProvider` is a keep-alive Riverpod provider and calls `ref.watch(authStateChangesProvider…)`, which is declared auto-dispose (apps/dashboard/lib/auth/auth_provider.dart:31). The keep-alive provider listens to it for the life of the ProviderContainer, so `authStateChangesProvider` is never disposed — the auto-dispose lifetime it declares never happens, and whatever it holds (a socket, a controller, a stale value) is kept for every later reader. Mark `authStateChangesProvider` keepAlive too, make `billingApiProvider` auto-dispose, or read it per use outside build. — apps/dashboard/lib/billing/billing_api.dart:12
  • `billingApiProvider` is a keep-alive Riverpod provider and calls `ref.watch(activeConnectionFirebaseAuthProvider…)`, which is declared auto-dispose (apps/dashboard/lib/connections/active_connection_firebase_auth.dart:11). The keep-alive provider listens to it for the life of the ProviderContainer, so `activeConnectionFirebaseAuthProvider` is never disposed — the auto-dispose lifetime it declares never happens, and whatever it holds (a socket, a controller, a stale value) is kept for every later reader. Mark `activeConnectionFirebaseAuthProvider` keepAlive too, make `billingApiProvider` auto-dispose, or read it per use outside build. — apps/dashboard/lib/billing/billing_api.dart:14
  • `accountSetupProvider` is a keep-alive Riverpod provider and calls `ref.watch(authStateChangesProvider…)`, which is declared auto-dispose (apps/dashboard/lib/auth/auth_provider.dart:31). The keep-alive provider listens to it for the life of the ProviderContainer, so `authStateChangesProvider` is never disposed — the auto-dispose lifetime it declares never happens, and whatever it holds (a socket, a controller, a stale value) is kept for every later reader. Mark `authStateChangesProvider` keepAlive too, make `accountSetupProvider` auto-dispose, or read it per use outside build. — apps/dashboard/lib/auth/account_setup_provider.dart:8

What to do

  • Riverpod: a keepAlive provider must only watch, listen to or read in build other keepAlive providers — mark the dependency @Riverpod(keepAlive: true) (or drop .autoDispose), make the consumer auto-dispose too, or read the dependency per use from a Notifier method instead of in build (riverpod_lint: only_use_keep_alive_inside_keep_alive).
AX10 · Code composition9.9 / 10Exemplary✓ Tool-verified

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.

AX3 · Project dependency cycles10.0 / 10Exemplary✓ Tool-verified

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.

AX4 · Dependency direction10.0 / 10Exemplary✓ Tool-verified

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.

AX6 · Interface segregation10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether interfaces stay focused rather than fat — the Interface-Segregation principle (SOLID 'I').

Method: Roslyn scan: public interface declared-member counts (accessors fold into their property/event); fat-interface threshold (over 15 declared members) flagged per type. Each finding also reports the distinct-OPERATION count — members counted by name, so an overload group counts once — which decides whether it states the caller-side ISP harm or the implementer-side burden of an overload set. TypeScript: exported interfaces that declare behaviour, counted over their REQUIRED operations (method signatures and function-typed properties with no `?`, once per signature) — data-shape interfaces and ambient .d.ts declarations are outside the population; JavaScript declares no interfaces and is not applicable. Deterministic, type-level.

AX9 · CQS / query purity10.0 / 10Exemplary✓ Tool-verified

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.

DM5 · Encapsulated state10.0 / 10Exemplary✓ Tool-verified

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.

GD1 · Unfinished & placeholder code10.0 / 10Exemplary○ Nothing flagged

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.

IC1 · Incompleteness & stubs10.0 / 10Exemplary○ Nothing flagged

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. (×4) — packages/openci_workflow/test/src/dart/pub_dev_publisher_test.dart:177, packages/openci_workflow/test/src/dart/pub_dev_publisher_test.dart:203, packages/openci_workflow/test/src/dart/pub_dev_publisher_test.dart:218, …

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.
M1 · Documentation (README)6.6 / 10Adequate✓ Tool-verified

Maturity · Maturity — Whether the repository and its projects have a README, and whether it is substantive.

Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.

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.
M2 · Architecture documentation0.0 / 10Critical✓ Tool-verified

Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.

Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.

  • No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
  • No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.

What to do

  • Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
  • Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure10.0 / 10Exemplary✓ Tool-verified

Maturity · Maturity — Whether the repository is organised deliberately: production code and tests are set apart in a way its ecosystem or the repository itself declares.

Method: Filesystem scan: src/test folder separation and namespace-prefix consistency (majority RootNamespace agreement). Exhaustive across projects, deterministic.

M4 · Documentation accuracy10.0 / 10Exemplary○ Nothing flagged

Maturity · Maturity — Whether the project's current-state documentation describes the code that exists.

Method: Every current-state document's checkable claims looked up in the tree (links, versions, and artefact counts an order of magnitude off), plus two README checks: an advertised infrastructure product with no footprint, and a module the CHANGELOG records as removed. Deterministic, no model. Advisory.

P1 · CI/CD gates0.0 / 10Critical✓ Tool-verified

Readiness · Readiness — Whether an automated pipeline builds and tests every change.

Method: Filesystem scan: CI workflow files (.github/workflows, .gitlab-ci.yml, etc.) for build and test stages. Exhaustive, deterministic.

  • No CI workflow found (.github/workflows, azure-pipelines.yml, .gitlab-ci.yml, …) — changes aren't gated by an automated build/test.

What to do

  • Add a CI workflow that builds and runs the test suite on every push/PR. The repository declares its tests as `npm test --workspace=openci-website` (`apps/website/package.json`): run that.
P10 · Library API & versioning10.0 / 10Exemplary○ Nothing flagged

Readiness · Readiness — For a library: a deliberate (small) public API surface and explicit semantic versioning so consumers can depend on it safely.

Method: Roslyn scan: public API surface area and semantic-versioning markers (SemVer attributes, changelog entries) for libraries; off .NET, a library is the ecosystem's publication act (an npm package that is not private and names an entry point, a PyPI distribution with a build system, a Rust library crate, a Maven/Gradle module that publishes, a Go module with no package main, a gemspec, a Composer library, a SwiftPM library product, a pub.dev or Hex package), its surface is the share of types the language's code model records as public (Rust, Swift, Java, Kotlin, Go, Dart; not measured where the model records no type visibility or, as in TypeScript, only module-level export), and its version is read from the manifest, a semver CHANGELOG, release tooling or semver git tags. Exhaustive, deterministic.

P2 · Observability4.2 / 10Weak✓ Tool-verified

Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.

Method: Filesystem/Roslyn scan: structured-logging frameworks (Serilog, NLog), OpenTelemetry, and health-check endpoint patterns. Exhaustive, deterministic.

  • Only 1/12 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `.`, `apps/dashboard`, `apps/dashboard/ios`, `apps/dashboard/macos`, `apps/landing_page` and 6 more.

What to do

  • Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
  • Add a health-check endpoint (a /health route on your shelf router) so orchestrators and load balancers can probe liveness/readiness.
P3 · Security & performance tooling0.0 / 10Critical✓ Tool-verified

Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).

Method: Filesystem scan: SAST configuration, dependency-update automation, secret scanning, and a benchmark harness or benchmark step — in this repository's own ecosystem. Exhaustive, deterministic.

  • No static application security testing detected. For this repository's stack, add the Dart analyzer's security lints plus `semgrep --config=auto` — this repository has no CI pipeline yet, so run it locally to clear the existing findings, then make it a step of the first workflow you add so a regression fails the build. What was searched, so you can tell an absence from a miss: the 0 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
  • `package.json` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — package.json:15

What to do

  • Run what this repository's stack ships: the Dart analyzer's security lints plus `semgrep --config=auto` — locally for now, since there is no CI pipeline here yet, and as a step of the first workflow you add so a security regression fails the build instead of landing.
  • Enable Dependabot/Renovate or a dependency-review gate.
  • Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback8.0 / 10Strong✓ Tool-verified

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

  • Add an approval/environment gate (required reviewers / protection rules) before production promotion.
P5 · DR & Backup7.0 / 10Strong✓ Tool-verified

Readiness · Readiness — Whether disaster recovery is planned and codified — backups, geo-recovery, RTO/RPO, persistence guarantees — from IaC + container manifests + docs, never the live cloud.

Method: Filesystem scan: disaster recovery, backup, geo-recovery, RTO/RPO, persistence guarantees from IaC, manifests, and docs. Exhaustive, deterministic, never a live environment.

What to do

  • Document RTO/RPO and a tested restore procedure (a backup config alone isn't disaster recovery).
P6 · Release Hygiene10.0 / 10Exemplary✓ Tool-verified

Readiness · Readiness — Whether releases are traceable — a maintained changelog and explicit version stamping.

Method: Filesystem scan: changelog file presence and version tags in csproj or git tags. Exhaustive, deterministic.

P8 · Schema migrations10.0 / 10Exemplary○ Nothing flagged

Readiness · Readiness — Whether database schema changes go through versioned migrations rather than being auto-created from the model at startup.

Method: Roslyn scan: EF Core DbContext for a versioned migrations directory versus bare EnsureCreated usage; off .NET, a file scan of dependency manifests, migration histories (Flyway, Liquibase, Alembic, Django, Rails, Prisma, TypeORM, Knex/Sequelize, golang-migrate, goose, Laravel, Doctrine, Diesel/sqlx) and schema auto-create in production source or config. Exhaustive, deterministic.

PF3 · Async & latency hygiene10.0 / 10Exemplary✓ Tool-verified

Readiness · Performance — Whether asynchronous code stays responsive — it avoids sync-over-async blocking (a .NET .Wait()/.GetAwaiter().GetResult(), a time.sleep or blocking HTTP call inside a Python coroutine, a *Sync call inside an async JavaScript function, block_on inside a Rust async fn, runBlocking inside a Kotlin suspend function, block() inside a Reactor publisher) that stalls a thread or event loop and risks deadlock, and, where the code is a reusable library on .NET, awaits with ConfigureAwait(false) so it never captures and stalls its caller's context.

Method: Production-source scan: sync-over-async blocking counted everywhere — .Wait()/.GetAwaiter().GetResult() in .NET; off .NET, read from each language's code model, a blocking call inside an async function (Python, TS/JS, Rust, Kotlin, Swift, Dart) or inside a Java method returning a Reactor Mono/Flux or a Scala method returning a Future or effect — and, for a .NET library with ≥5 awaits, the share of awaits using ConfigureAwait(false). Deterministic, syntax/text detection.

R1 · Type Safety5.9 / 10Adequate✓ Tool-verified

React / JS · Code Health — How much of the frontend is typed TypeScript vs untyped JavaScript.

Method: Frontend file inventory: the share of typed TypeScript vs untyped JavaScript across the source tree. Deterministic, exhaustive over frontend files.

  • 77 typed · 54 plain JS — the untyped files are apps/dashboard/web/flutter_bootstrap.js, firebase/dataconnect/test/billing.test.mjs, firebase/dataconnect/test/build_checks.test.mjs, firebase/dataconnect/test/build_dispatch.test.mjs, firebase/dataconnect/test/build_dispatch_queue.test.mjs, firebase/dataconnect/test/build_dispatch_retry.test.mjs (+48 more).
R10 · Code Duplication7.0 / 10Adequate✓ Tool-verified

React / JS · Code Health — The share of the scored frontend lines inside a near-exact copy-pasted block of substantial extent (the D4 clone algorithm over JS/TS tokens, D-386; each line once, 10 at none and 0 at a quarter of the lines, as D4): a block is reported only where its copies still agree on most of their own identifiers and literals, or were renamed as they were pasted but kept most of their constants, and where the copies carry enough code to stand on their own or the copied extent reaches 30 lines — so a re-implementation sharing neither names nor values, and a small pasted declaration, are both found and deliberately not reported, and a clean R10 is not a claim that nothing was copied.

Method: Near-exact copy-pasted blocks of substantial extent across the frontend (the D4 clone algorithm run over JS/TS tokens). Masking finds the candidates; a block is reported when its copies still agree on most of their own identifiers and literals, or when a renamed copy still agrees on most of its constants, AND the copies carry enough code to stand on their own — or when the copied extent reaches 30 lines. So a re-implementation sharing neither names nor values, and a small pasted declaration, are deliberately not counted. Scored on the share of the scored frontend lines inside a reported copy, on the same curve as D4. Deterministic.

  • firebase/functions/executor/orchard.ts:28 · firebase/functions/orchard_capacity.ts:130 — the two spans are one implementation copied and then locally edited — 336 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — firebase/functions/executor/orchard.ts:28
  • apps/landing_page/components/build-job-card-demo.tsx:308 · apps/landing_page/components/build-job-card-demo.tsx:341 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — apps/landing_page/components/build-job-card-demo.tsx:308
  • firebase/functions/github_connection/github.ts:114 · firebase/functions/github_connection/github.ts:192 — the two spans are one implementation copied and then locally edited — 213 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — firebase/functions/github_connection/github.ts:114
  • firebase/functions/executor/github.ts:171 · firebase/functions/executor/github.ts:539 — 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. — firebase/functions/executor/github.ts:171
  • REDACTED:252 · apps/landing_page/components/site.tsx:304 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — REDACTED:252
  • firebase/functions/executor/store.ts:63 · firebase/functions/queued_checks.ts:24 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — firebase/functions/executor/store.ts:63
  • apps/landing_page/components/site.tsx:539 · apps/landing_page/components/site.tsx:569 — 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. — apps/landing_page/components/site.tsx:539
  • apps/landing_page/components/build-job-card-demo.tsx:290 · apps/landing_page/components/build-job-card-demo.tsx: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. — apps/landing_page/components/build-job-card-demo.tsx:290
  • apps/landing_page/components/site.tsx:186 · apps/landing_page/components/site.tsx:211 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — apps/landing_page/components/site.tsx:186
  • firebase/functions/secret_functions.ts:24 · firebase/functions/team_functions.ts:10 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — firebase/functions/secret_functions.ts:24
  • firebase/functions/executor/logs.ts:59 · firebase/functions/executor/logs.ts:86 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — firebase/functions/executor/logs.ts:59
  • apps/landing_page/app/(en)/layout.tsx:11 · apps/landing_page/app/(ja)/layout.tsx:11 · apps/landing_page/app/(redirect)/layout.tsx:11 — the 3 copies are spread across 3 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. There is one copy in each of 3 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete. — apps/landing_page/app/(en)/layout.tsx:11
  • firebase/functions/build_dispatch_functions.ts:61 · firebase/functions/skipped_check_functions.ts:48 — the two spans are one implementation copied and then locally edited — 53 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — firebase/functions/build_dispatch_functions.ts:61
  • firebase/functions/executor/store.ts:85 · firebase/functions/executor/store.ts:110 — the two spans are one implementation copied and then locally edited — 67 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — firebase/functions/executor/store.ts:85
  • firebase/functions/executor/github.ts:424 · firebase/functions/executor/github.ts:498 — 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. — firebase/functions/executor/github.ts:424
  • apps/landing_page/components/build-job-card-demo.tsx:144 · apps/landing_page/components/build-job-card-demo.tsx:152 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — apps/landing_page/components/build-job-card-demo.tsx:144
  • firebase/functions/executor/orchard.ts:161 · firebase/functions/orchard_capacity.ts:50 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — firebase/functions/executor/orchard.ts:161
  • REDACTED:51 · firebase/functions/github_connection_functions.ts:44 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — REDACTED:51
  • firebase/functions/executor/billing.ts:156 · firebase/functions/executor/billing.ts:183 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — firebase/functions/executor/billing.ts:156
  • firebase/functions/github_connection/github.ts:28 · firebase/functions/orchard_capacity.ts:20 — the two spans are one implementation copied and then locally edited — 68 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — firebase/functions/github_connection/github.ts:28
  • firebase/functions/executor/billing.ts:124 · firebase/functions/executor/billing.ts:155 · firebase/functions/executor/billing.ts:182 — all 3 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — firebase/functions/executor/billing.ts:124
  • firebase/functions/github_connection/service.ts:63 · firebase/functions/secrets/service.ts:46 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — firebase/functions/github_connection/service.ts:63
  • infra/deploy/prepare-core.mjs:5 · infra/deploy/prepare.mjs:6 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — infra/deploy/prepare-core.mjs:5
  • firebase/functions/billing/service.ts:109 · firebase/functions/executor/billing.ts:51 — the two spans are one implementation copied and then locally edited — 64 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — firebase/functions/billing/service.ts:109
  • firebase/functions/executor/github.ts:427 · firebase/functions/executor/github.ts:501 · REDACTED:308 — the 3 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — firebase/functions/executor/github.ts:427

What to do

  • Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract.
R2 · Cyclomatic Complexity6.0 / 10Adequate✓ Tool-verified

React / JS · Code Health — Per-function cyclomatic/cognitive complexity from the token-level function scanner (D-386) — real branching, not a regex heuristic.

Method: Per-function cyclomatic/cognitive complexity from a token-level function scanner (real branching, not a regex heuristic), computed over every frontend function. Deterministic.

  • execute has cyclomatic complexity 40 and cognitive complexity 46; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — firebase/functions/secrets/service.ts:49
  • checkWorkerMemory has cyclomatic complexity 34 and cognitive complexity 28; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — firebase/functions/executor/orchard.ts:146
  • candidates has cyclomatic complexity 33 and cognitive complexity 59; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — firebase/functions/github_connection/github.ts:102
  • sync has cyclomatic complexity 31 and cognitive complexity 29; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — firebase/functions/queued_checks.ts:79
  • hasOrchardCapacity has cyclomatic complexity 30 and cognitive complexity 38; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — firebase/functions/orchard_capacity.ts:39
  • (anonymous) has cyclomatic complexity 30 and cognitive complexity 25; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — firebase/functions/executor/github.ts:287
  • (anonymous) has cyclomatic complexity 29 and cognitive complexity 36; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — firebase/functions/build_dispatch_functions.ts:270
  • executeBuild has cyclomatic complexity 29 and cognitive complexity 32; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — firebase/functions/executor/execute.ts:86
  • execute has cyclomatic complexity 27 and cognitive complexity 23; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — firebase/functions/github_connection/service.ts:66
  • resolveCheckout has cyclomatic complexity 24 and cognitive complexity 28; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — firebase/functions/executor/github.ts:231
  • repositories has cyclomatic complexity 24 and cognitive complexity 27; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — firebase/functions/github_connection/github.ts:174
  • receiveStripeWebhook has cyclomatic complexity 24 and cognitive complexity 20; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — firebase/functions/billing/webhook.ts:23
  • reconcileCardSession has cyclomatic complexity 24 and cognitive complexity 18; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — firebase/functions/billing/card_setup.ts:34
  • request has cyclomatic complexity 23 and cognitive complexity 31; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — firebase/functions/test/pull_request_qr.test.mjs:276
  • (anonymous) has cyclomatic complexity 23 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — firebase/functions/build_dispatch_functions.ts:204
  • (anonymous) has cyclomatic complexity 22 and cognitive complexity 36; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — firebase/functions/build_dispatch_functions.ts:73
  • execute has cyclomatic complexity 22 and cognitive complexity 32; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — firebase/functions/teams/service.ts:31
  • skippedCheck has cyclomatic complexity 22 and cognitive complexity 23; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — firebase/functions/executor/github.ts:137
  • billingConfig has cyclomatic complexity 22 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — firebase/functions/billing/config.ts:12
  • observePurchase has cyclomatic complexity 21 and cognitive complexity 9; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — firebase/functions/billing/purchase.ts:76
  • (anonymous) has cyclomatic complexity 20 and cognitive complexity 31; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — apps/landing_page/components/build-job-card-demo.tsx:141
  • execute has cyclomatic complexity 20 and cognitive complexity 20; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — firebase/functions/billing/service.ts:34
  • receiveGitHubWebhook has cyclomatic complexity 19 and cognitive complexity 20; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — firebase/functions/github_webhook.ts:11
  • cleanupExecution has cyclomatic complexity 19 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — firebase/functions/executor/execute.ts:48
  • configure has cyclomatic complexity 19 and cognitive complexity 12; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — firebase/functions/executor/store.ts:82
  • close has cyclomatic complexity 18 and cognitive complexity 30; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — firebase/functions/executor/billing.ts:181
  • readPullRequestQrCodes has cyclomatic complexity 18 and cognitive complexity 27; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:126
  • (anonymous) has cyclomatic complexity 18 and cognitive complexity 20; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — firebase/dataconnect/test/build_job_planning.test.mjs:36
  • callback has cyclomatic complexity 18 and cognitive complexity 18; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — firebase/functions/github_connection/service.ts:173
  • runtime has cyclomatic complexity 18 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — firebase/functions/executor/runtime.ts:16
  • publishPullRequestQrCodes has cyclomatic complexity 17 and cognitive complexity 23; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:289
  • status has cyclomatic complexity 17 and cognitive complexity 21; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — firebase/functions/billing/service.ts:88
  • reconcile has cyclomatic complexity 16 and cognitive complexity 26; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — firebase/functions/billing/service.ts:198
  • (anonymous) has cyclomatic complexity 16 and cognitive complexity 21; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — apps/landing_page/components/build-job-card-demo.tsx:174
  • validatedQrMetadata has cyclomatic complexity 16 and cognitive complexity 15; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:75
  • cardSetupStatus has cyclomatic complexity 16 and cognitive complexity 14; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — firebase/functions/billing/card_setup.ts:165
  • admit has cyclomatic complexity 15 and cognitive complexity 23; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — firebase/functions/executor/billing.ts:68
  • retainPaidPeriod has cyclomatic complexity 15 and cognitive complexity 15; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — firebase/functions/billing/service.ts:315
  • deleteTeam has cyclomatic complexity 14 and cognitive complexity 27; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — firebase/functions/billing/service.ts:258
  • dispatchBuildJob has cyclomatic complexity 14 and cognitive complexity 25; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — firebase/functions/build_dispatch.ts:139
R3 · Large Files7.9 / 10Strong✓ Tool-verified

React / JS · Code Health — How many source files exceed the large-file threshold.

Method: Components/modules exceeding the large-file threshold, counted exhaustively across the frontend source tree. Deterministic.

  • apps/landing_page/components/site.tsx has 999 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — apps/landing_page/components/site.tsx:1
  • firebase/functions/executor/github.ts has 569 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — firebase/functions/executor/github.ts:1
  • REDACTED has 413 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — REDACTED:1
  • firebase/generated/billing-admin/index.cjs.js has 408 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — firebase/generated/billing-admin/index.cjs.js:1
  • firebase/generated/dispatch-admin/index.cjs.js has 403 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — firebase/generated/dispatch-admin/index.cjs.js:1

What to do

  • Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
R4 · Test Coverage6.2 / 10Adequate✓ Tool-verified

React / JS · Readiness — Static test reachability (D-386): the share of production files reachable from any test via the import graph — measured without running anything.

Method: Static test reachability: the share of production files reachable from any test via the import graph — measured without running anything. Deterministic.

  • No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one. (×30) — apps/landing_page/components/site.tsx:1, apps/landing_page/components/build-job-card-demo.tsx:1, REDACTED:1, …

What to do

  • Add tests that import the unreached modules (directly or through their public entry).
R5 · Dependency Freshness7.3 / 10Strong✓ Tool-verified

React / JS · Readiness — How outdated the npm dependencies are (a maturity signal). JS/npm CVEs are scored separately in D30 (JS/npm Dependency Vulnerabilities).

Method: npm dependency staleness from manifest/registry metadata (a maturity signal; JS/npm CVEs are scored separately in D30, which answers dependency vulnerabilities for every ecosystem). Deterministic.

R6 · Tooling10.0 / 10Exemplary✓ Tool-verified

React / JS · Readiness — Whether the project wires up test, lint and typecheck — detected from each package.json script's COMMAND (eslint / tsc / vitest / jest / playwright), not just its name, and corroborated against CI-workflow invocations so a tool run only in CI still counts.

Method: package.json scanned for test/lint/typecheck script wiring. Deterministic presence check.

R7 · Dead Code9.9 / 10Exemplary✓ Tool-verified

React / JS · Code Health — Files unreachable from every application/tooling/test entry point, and exports nothing imports (module-graph reachability, D-386).

Method: Dead code: files unreachable from every application/tooling/test entry point plus exports nothing imports, via module-graph reachability. Deterministic, exhaustive over the import graph.

  • Unreachable from the 48 application, 13 tooling and 36 test entry point(s) detected in this repo. Gate removals on `npm run build` — an undetected custom entry would make these reachable.
  • no import path from any entry point (48 application, 13 tooling, 36 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make (×2) — infra/orchard/check-network.mjs, firebase/functions/core.ts

What to do

  • Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
R8 · Dependency Hygiene10.0 / 10Exemplary✓ Tool-verified

React / JS · Readiness — npm dependency truthfulness (D-386): unused dependencies, imports not declared anywhere, and type-/test-only packages shipped as production deps.

Method: npm dependency truthfulness: unused dependencies, imports declared nowhere, and type-/test-only packages shipped as production deps — from the manifest + import graph. Deterministic.

R9 · Circular Imports10.0 / 10Exemplary✓ Tool-verified

React / JS · Architecture — Import cycles in the module graph (D-386) — files that can only be understood and changed together.

Method: Import cycles in the module graph, detected exhaustively over JS/TS imports (the same cycle detection as the .NET coupling dimension). Deterministic.

S1 · Web-Security Posture8.0 / 10Strong✓ Tool-verified

Other · Security — Only what this repository's own non-C# files could be read for was assessed — and because this repository commits the configuration that serves its own HTTP surface, that configuration could be read in full for the security response headers it sets. Nothing else in this dimension was assessed: the transport, cookie, input-validation and crypto controls are read from a source model that was not loaded for this repository’s language, so their absence here is not a finding about this repository.

Method: Roslyn plus filesystem scan: HSTS/security headers, secure cookies, input validation, middleware order, weak crypto (MD5/SHA1/DES); HTTPS-metadata context-aware. On a repository with no .NET source it reads JavaScript/TypeScript, Dart, Ruby, Scala, Rust or Elixir source itself (test, vendored, generated and minified paths not) for the arms that hold whether or not the code serves HTTP: a weak hash or cipher, key material fixed in the source, a TLS client that accepts any certificate, and (JavaScript/TypeScript, Ruby, Scala, Rust and Elixir) an obsolete TLS version; the server controls are not assessed there, and a Dart, Ruby, Scala, Rust or Elixir repository that serves no HTTP of its own is N/A on them. Deterministic.

  • None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is configured — defense in depth, even when a reverse proxy could set them. This is reported because `firebase.json` configures this repository's static hosting, including its response headers, so the configuration that would carry these headers is in this repository and was read in full. (−2.0 on this card.) — firebase/firebase.json:1

What to do

  • Set security response headers on the surface this repository serves: an `add_header` directive per header in the nginx/Caddy/Apache config, a `_headers` / `vercel.json` / `netlify.toml` entry for a static host, or `helmet()` in the HTTP server. `Content-Security-Policy` is the one that pays for itself first — it is what contains an injected script once one reaches the page — followed by `X-Content-Type-Options: nosniff` and a frame policy (`X-Frame-Options: DENY`, or CSP `frame-ancestors`). Where the app is served from a build container, the header configuration belongs in the image beside the built assets, so it ships with them rather than depending on where it lands.
X1 · Async correctness10.0 / 10Exemplary○ Nothing flagged

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.

X12 · Unreachable branch10.0 / 10Exemplary○ Nothing flagged

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.

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.

X14 · Bypassable address classification10.0 / 10Exemplary○ Nothing flagged

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.

X16 · Unfloored truncation loop10.0 / 10Exemplary○ Nothing flagged

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.

X2 · Cancellation propagation8.8 / 10Strong✓ Tool-verified

Other · Code Health — Whether async functions that make a cancellable request accept or pass on an AbortSignal (adoption curve).

Method: Roslyn scan: every async method (excluding framework-fixed overrides/Blazor handlers) checked for CancellationToken parameter presence. Deterministic, adoption percentage. 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 question: every named async function that itself makes a request an AbortSignal can cancel (global `fetch`, axios and its file-local instances, ky, ofetch) counts, and it is compliant when its parameters or body name a signal or it hands one of its own parameters to the request as options; signatures a framework fixes (JSX event handlers, route and lifecycle exports, request-first handlers, `override`, `'use server'` modules, TanStack `mutationFn`) are exempt unless they take a signal. Deterministic, adoption percentage.

  • Only 8/10 async functions that make a cancellable request (fetch, axios, ky, ofetch, got, undici, node:http) accept an AbortSignal or pass one on, so a request keeps running after whatever wanted it has given up — a page navigated away from, an unmounted component, a timed-out job. Take a `signal` (or an options object that carries one) and hand it to the request; where nothing could ever cancel the call, omitting it is a deliberate choice — judge against how the function is used.
  • `postPullRequestQrCodes` holds an AbortSignal but calls `client(…)` without it, so its caller's cancellation never reaches that call and it runs to its end after whatever wanted it has given up. Hand the signal on: `client(…, { signal })`. — firebase/functions/executor/github.ts:112
  • `resolveCheckout` holds an AbortSignal but calls `client(…)` without it, so its caller's cancellation never reaches that call and it runs to its end after whatever wanted it has given up. Hand the signal on: `client(…, { signal })`. — firebase/functions/executor/github.ts:231

What to do

  • Thread an AbortSignal through async functions that make requests, so the work stops when its caller gives up.
X21 · Side-effecting pattern guard10.0 / 10Exemplary○ Nothing flagged

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.

X25 · Inert configuration knob10.0 / 10Exemplary○ Nothing flagged

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.

X27 · Collection changed while being enumerated10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a `for` loop leaves the `dict`, `set` or `deque` it is walking alone — CPython's iterators over those check that the collection has not changed size since the loop began, so a body that removes from (or empties) the very collection the loop is walking makes the next step raise `RuntimeError: dictionary changed size during iteration` and the remaining items are never seen. Whether a `for … in` loop leaves the `List`, `Map` or `Set` it is walking alone — Dart's collection iterators check that the collection has not changed since the loop began, so a body that adds to or removes from the very collection the loop is walking (or the map whose `keys`, `values` or `entries` it walks) makes the next step throw `ConcurrentModificationError` and the remaining elements are never seen. Whether a `for (x in c)` or `c.forEach { … }` leaves the collection it is walking alone — a `mutableListOf`/`ArrayList`, `mutableMapOf`/`HashMap` or `mutableSetOf`/`HashSet` is a `java.util` collection on the JVM and is walked by its own fail-fast iterator, so a body that adds to or removes from the very collection the loop is walking makes the next step throw `ConcurrentModificationException` and the remaining elements are never seen.

Method: Roslyn syntax + semantics: `foreach` statements whose body calls a structural mutator (`Add`/`Remove`/`Clear`/`Insert`/…) on the very expression the loop is enumerating. Two arms. ARM A — the source is a concrete fragile BCL collection, or a live `Keys`/`Values` view over one, and the mutator resolves to that same collection's own member; concurrent and immutable collections and arrays are outside the population by construction, since their enumerators survive a structural change. ARM B — the source is an argument-less accessor CALL on a receiver whose body is in source: the accessor must return a stored field VERBATIM and a sibling member must structurally change that same field, both read off the implementations rather than from the members' names. A mutation the loop provably exits immediately after (`break`/`return`/`throw`/`goto`), or one written inside a nested loop or a lambda, is counted and never reported. Deterministic, provable per finding. Advisory.

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.

X3 · Exception handling6.6 / 10Adequate✓ Tool-verified

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(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it. (×2) — firebase/functions/github_connection/vault.ts:53, firebase/functions/executor/logs.ts:201
  • `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, or keep only the failure you expect and rethrow the rest (`catch (e) { if (!(e instanceof SyntaxError)) throw e; … }`, or test `e.name`), because a JavaScript catch takes every exception, programming errors included. (×2) — firebase/functions/executor/billing.ts:94, firebase/functions/executor/billing.ts:220
  • 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. (×14) — firebase/functions/executor/billing.ts:116, firebase/functions/executor/billing.ts:146, firebase/functions/executor/billing.ts:174, …
  • `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. — firebase/dart_functions/lib/src/open_ci_parser.dart:96

What to do

  • Swallowed exception (empty catch)
X5 · Nullable reference types9.0 / 10Exemplary✓ Tool-verified

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.

WCAG coverage — what static analysis assessed

Statically assessed 13 of 55 WCAG 2.2 Level A/AA success criteria (24%; ≈26% of the 50 WCAG 2.1 AA criteria for EN 301 549). The other 42 require runtime or manual evaluation. Partial signal only (a clean result is necessary, not sufficient; static analysis fully verifies none). This is accessibility readiness, not a conformance claim — a WCAG conformance claim requires manual evaluation (WCAG-EM 1.0).

DimensionWCAG 2.2 A/AA criteriaCoverage
AC1 · Text alternatives1.1.1, 1.2.2, 1.2.5Partial signal
AC2 · Forms & labels1.3.1, 3.3.2, 4.1.2Partial signal
AC3 · Page structure1.4.4, 2.2.1, 2.4.1, 2.4.2, 3.1.1, 4.1.2Partial signal
AC5 · ARIA correctness4.1.2Partial signal
AC6 · Visual & motion safety1.4.3, 2.4.7Partial — literal CSS only

Not statically assessed — these 42 Level A/AA criteria need runtime or manual evaluation (WCAG-EM): 1.2.1, 1.2.3, 1.2.4, 1.3.2, 1.3.3, 1.3.4, 1.3.5, 1.4.1, 1.4.2, 1.4.5, 1.4.10, 1.4.11, 1.4.12, 1.4.13, 2.1.1, 2.1.2, 2.1.4, 2.2.2, 2.3.1, 2.4.3, 2.4.4, 2.4.5, 2.4.6, 2.4.11, 2.5.1, 2.5.2, 2.5.3, 2.5.4, 2.5.7, 2.5.8, 3.1.2, 3.2.1, 3.2.2, 3.2.3, 3.2.4, 3.2.6, 3.3.1, 3.3.3, 3.3.4, 3.3.7, 3.3.8, 4.1.3.

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.

LensScoreRatingImpact
Code Health67.9AdequateAcceptable, with room to improve.
Architecture78.1Adequate — gated by AX1Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Maturity58.7Adequate — gated by M2Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Readiness35.0Weak — gated by D13, P1, P3Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security67.4Adequate — gated by D28Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Domain Modelling100.0ExemplaryStrongest area.
Accessibility66.5Adequate — gated by AC1Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Performance100.0ExemplarySolid.
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.

  • SC1 Supply-chain hygiene — 8 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
  • X10 Duplicated predicate — 24 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not included — 61 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.

  • AC4 Keyboard semantics — No interactive element found in the parsed markup — AC4 not applicable here.
  • AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No class in this Kotlin code is a Spring, JSR-330 or CDI singleton bean. No function in this Python code is served by a threaded web framework (a Flask, Bottle or FastAPI route, a Django or Pyramid view), so no module is shared between request threads. No Swift request handler (a Vapor, Hummingbird, Kitura, Swifter or Perfect route handler, as a method or a registered closure) is declared, so no state is shared between request threads. Dart isolates share no mutable memory, so no two requests write one object at the same instant. TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
  • AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • AX7 Slice cohesion — not applicable — not a vertical-slice architecture
  • AX8 Test isolation — no test/production split to check
  • AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • AXR1 Runtime accessibility — compose up failed (exit 17 — an image could not be built) — failed to solve: process "/bin/sh -c npm install --global firebase-tools@15.25.0 && firebase setup:emulators:ui && npm cache clean --force" did not complete successfully: exit code: 1; likely cause (the repository): a RUN step of the repository's REDACTED exited with code 1 (`/bin/sh -c npm install --global firebase-tools@15.25.0 && firebase setup:emulators:ui && npm cache clean --force`): the build's own command failed, for example a compile or test error; runtime evidence skipped The cause is in the repository, not in our sandbox: a RUN step of the repository's REDACTED exited with code 1 (`/bin/sh -c npm install --global firebase-tools@15.25.0 && firebase setup:emulators:ui && npm cache clean --force`): the build's own command failed, for example a compile or test error. Nothing here says the surface is inaccessible, only that it was never rendered.
  • C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Drift table, an Isar, ObjectBox, Floor or Hive entity, or a Serverpod table model — and no database or data-store client (sqflite, Drift, Isar, Hive, Realm, Firestore, Supabase, postgres, …) in the source either, so this repository keeps no data at rest for these controls to protect.
  • C2 Access Controls — No access-control surface detected in the analyzed source — this repository stands up no server another machine can reach (no HttpServer or shelf server bound beyond loopback, no dart_frog route, no Serverpod endpoint, no Conduit, Alfred or Angel application) and keeps no data in a hosted backend. Access control is therefore N/A here — a Flutter app or pub package is authorized by the server it calls, not by itself; hiding a screen authorizes nothing. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
  • C3 Audit Trail — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Drift table, an ObjectBox/Floor @Entity, an Isar @collection, a Hive @HiveType or a Serverpod table model — and no database or data-store client (sqflite, Firestore, Supabase, postgres, …) imported either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a hosted backend configured outside this repository, for instance), the trail belongs to wherever that data is stored.
  • C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Drift table, an ObjectBox/Floor @Entity, an Isar @collection, a Hive @HiveType or a Serverpod table model — and no database or data-store client (sqflite, Firestore, Supabase, postgres, …) imported either, so this repository keeps no personal data whose lifetime a retention limit would bound.
  • C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Drift table, an ObjectBox/Floor @Entity, an Isar @collection, a Hive @HiveType or a Serverpod table model — and no database or data-store client (sqflite, Firestore, Supabase, postgres, …) imported either, so this repository keeps no personal data for a data subject to erase, export or consent over.
  • D11 Test Reliability — Test reliability not scored — polyglot repository, one half has no runner
  • D12 Dependency Hygiene — Not scored — 2 Maven/Gradle manifest(s) were read, stating a version for 0 dependency(ies) and leaving 0 to a parent or an imported BOM, but no build resolved the dependency graph, so the outdated signal was not established. NOT a finding that these dependencies are current or healthy.
  • D16 Bus Factor — single-maintainer repository — bus factor is not applicable
  • D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
  • D21 Naming Consistency — N/A — too few peers to establish a naming convention (6479 declarations, no unit with a dominant convention).
  • D22 Internal API Consistency — API consistency is measured on C#, TypeScript, Go only; the exposed JavaScript, Swift surface was not measured.
  • D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
  • 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.
  • D32 Data Compliance (PII/GDPR) — 3 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
  • D36 Supply-chain Provenance & Signing — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for.
  • D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
  • D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
  • D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
  • D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
  • D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
  • D8 Code Coverage — Coverage not measured — polyglot repository, one half has no runner
  • DM1 Aggregate boundaries — not scored for Dart: aggregate-vs-value-object classification cannot be told apart in source (every class-holding-class reads alike), and a child COLLECTION (legitimate membership) vs a single embedded aggregate is indistinguishable — reported as guidance rather than measured
  • DM2 Strongly-typed ids — no in-repo typed-id idiom — primitive-obsession recorded as advisory DM8, DM2 not gated
  • DM3 Integration-event coupling — not scored for Dart: a cross-package domain leak cannot be told apart in source from a legitimate shared-kernel package, and most repositories ship a single package — reported as guidance rather than measured
  • DM4 Rich vs anemic domain model — this Dart repository declares no domain-layer entity carrying stored data (every type is a typed-id wrapper, DTO/config, ORM row or presentation container), so DM4's rich-vs-anemic read has no population to be taken over
  • DM6 Domain ↔ infrastructure boundary — this Dart repository maps no type to a persistence framework (drift/floor/isar/objectbox/hive), so DM6's domain↔infrastructure fusion read has no population to be taken over
  • DM7 Repository granularity — not scored for Dart: 'a repository per CHILD entity' needs the aggregate-root structure, which is not source-resolvable — reported as guidance rather than measured
  • ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and this analysis resolves a call's owner only where the receiver's type is written down in the source. Reported as guidance rather than measured
  • ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, which this analysis does not build from source alone for this language. Reported as guidance rather than measured
  • ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
  • ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
  • P12 CI test-gate honesty — no CI workflow found
  • P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the Dart, JVM, JavaScript/TypeScript, Python, Swift source, so there is no service whose uptime a failing dependency could take down
  • P9 Domain vs controller coverage — coverage data present for 78 file(s), but no domain-layer files were identified: no covered file's path contains any of the markers this check keys on (/domain/, /aggregates/, /valueobjects/, /domainmodel/, .domain/, /entities/), which are matched case-insensitively anywhere in the path. With no domain partition there is nothing to compare the web/controller layer against — if this repository keeps its business rules under a folder named none of those, that naming is what the check cannot see, not the domain logic.
  • PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for classes extending benchmark_harness's `BenchmarkBase`, `AsyncBenchmarkBase` or `PerfBenchmarkBase` (directly or through a base of your own), `benchmark(…)` calls under the pub `benchmark` package, Flutter's `benchmarkWidgets`, `watchPerformance` or `traceAction` in a test importing flutter_test, integration_test or flutter_driver, or benchmark_harness, benchmark or web_benchmarks in a pubspec.yaml, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
  • PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
  • R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
  • X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X18 Disposal-pattern correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X20 Mistyped argument guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X24 Document value interpolated into markup unescaped — X24 reached only 31% of this repository's production lines — dart (29,828 lines), swift (224 lines), kotlin (3 lines), c (1 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
  • X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
  • X4 Structured logging — This check asks whether log calls keep a message's values apart from its text, which needs a logger that can carry them as fields. This repository's Dart was read, and it logs through none: package:logging, package:logger, talker and dart:developer take one finished message and no template arguments or fields (as log4net does in C#), so an interpolated message there loses nothing the API could have kept. Sentry's structured logs (`Sentry.logger`) would be judged.
  • X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.

Appendix A — Findings (grouped)

The findings behind the scores, grouped by severity, then by dimension and kind. The high-severity issues are enumerated in full below; items per group are capped at 25 with any overflow stated explicitly per group, never silently truncated. The complete machine-readable list of every finding (all severities) is the companion findings.md in this report's bundle.

Critical — 56 finding(s)
D28 · Secrets (history) · REDACTED · ×18
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
AX1 · Captive dependencies · Captive dependency · ×14
  • Captive dependency: keepAlive provider localePreferenceProvider captures autoDispose sharedPreferencesProvider apps/dashboard/lib/app_locale_provider.dart:32 — `localePreferenceProvider` is a keep-alive Riverpod provider and calls `ref.watch(sharedPreferencesProvider…)`, which is declared auto-dispose (apps/dashboard/lib/utilities/shared_preferences_provider.dart:6). The keep-alive provider listens to it for the life of the ProviderContainer, so `sharedPreferencesProvider` is never disposed — the auto-dispose lifetime it declares never happens, and whatever it holds (a socket, a controller, a stale value) is kept for every later reader. Mark `sharedPreferencesProvider` keepAlive too, make `localePreferenceProvider` auto-dispose, or read it per use outside build.
  • Captive dependency: keepAlive provider githubConnectionApiProvider captures autoDispose currentGitHubConnectionContextProvider apps/dashboard/lib/team/github_connection_api.dart:14 — `githubConnectionApiProvider` is a keep-alive Riverpod provider and calls `ref.watch(currentGitHubConnectionContextProvider…)`, which is declared auto-dispose (apps/dashboard/lib/team/current_github_connection_context_provider.dart:8). The keep-alive provider listens to it for the life of the ProviderContainer, so `currentGitHubConnectionContextProvider` is never disposed — the auto-dispose lifetime it declares never happens, and whatever it holds (a socket, a controller, a stale value) is kept for every later reader. Mark `currentGitHubConnectionContextProvider` keepAlive too, make `githubConnectionApiProvider` auto-dispose, or read it per use outside build.
  • Captive dependency: keepAlive provider githubConnectionApiProvider captures autoDispose activeConnectionFirebaseAuthProvider apps/dashboard/lib/team/github_connection_api.dart:16 — `githubConnectionApiProvider` is a keep-alive Riverpod provider and calls `ref.watch(activeConnectionFirebaseAuthProvider…)`, which is declared auto-dispose (apps/dashboard/lib/connections/active_connection_firebase_auth.dart:11). The keep-alive provider listens to it for the life of the ProviderContainer, so `activeConnectionFirebaseAuthProvider` is never disposed — the auto-dispose lifetime it declares never happens, and whatever it holds (a socket, a controller, a stale value) is kept for every later reader. Mark `activeConnectionFirebaseAuthProvider` keepAlive too, make `githubConnectionApiProvider` auto-dispose, or read it per use outside build.
  • Captive dependency: keepAlive provider githubConnectionApiProvider captures autoDispose currentGitHubConnectionContextProvider apps/dashboard/lib/team/github_connection_api.dart:20 — `githubConnectionApiProvider` is a keep-alive Riverpod provider and calls `ref.read(currentGitHubConnectionContextProvider…)`, which is declared auto-dispose (apps/dashboard/lib/team/current_github_connection_context_provider.dart:8). Read in build, `currentGitHubConnectionContextProvider` has no listener once the read returns, so it is disposed at once — its ref.onDispose closes what it handed out — while `githubConnectionApiProvider` keeps that value for the life of the ProviderContainer. Mark `currentGitHubConnectionContextProvider` keepAlive too, make `githubConnectionApiProvider` auto-dispose, or read it per use outside build.
  • Captive dependency: keepAlive provider teamMembersApiProvider captures autoDispose authStateChangesProvider apps/dashboard/lib/team/team_members_api.dart:12 — `teamMembersApiProvider` is a keep-alive Riverpod provider and calls `ref.watch(authStateChangesProvider…)`, which is declared auto-dispose (apps/dashboard/lib/auth/auth_provider.dart:31). The keep-alive provider listens to it for the life of the ProviderContainer, so `authStateChangesProvider` is never disposed — the auto-dispose lifetime it declares never happens, and whatever it holds (a socket, a controller, a stale value) is kept for every later reader. Mark `authStateChangesProvider` keepAlive too, make `teamMembersApiProvider` auto-dispose, or read it per use outside build.
  • Captive dependency: keepAlive provider teamMembersApiProvider captures autoDispose activeConnectionFirebaseAuthProvider apps/dashboard/lib/team/team_members_api.dart:14 — `teamMembersApiProvider` is a keep-alive Riverpod provider and calls `ref.watch(activeConnectionFirebaseAuthProvider…)`, which is declared auto-dispose (apps/dashboard/lib/connections/active_connection_firebase_auth.dart:11). The keep-alive provider listens to it for the life of the ProviderContainer, so `activeConnectionFirebaseAuthProvider` is never disposed — the auto-dispose lifetime it declares never happens, and whatever it holds (a socket, a controller, a stale value) is kept for every later reader. Mark `activeConnectionFirebaseAuthProvider` keepAlive too, make `teamMembersApiProvider` auto-dispose, or read it per use outside build.
  • Captive dependency: keepAlive provider teamMembersApiProvider captures autoDispose teamsConnectorProvider apps/dashboard/lib/team/team_members_api.dart:15 — `teamMembersApiProvider` is a keep-alive Riverpod provider and calls `ref.watch(teamsConnectorProvider…)`, which is declared auto-dispose (apps/dashboard/lib/team/teams_connector_provider.dart:11). The keep-alive provider listens to it for the life of the ProviderContainer, so `teamsConnectorProvider` is never disposed — the auto-dispose lifetime it declares never happens, and whatever it holds (a socket, a controller, a stale value) is kept for every later reader. Mark `teamsConnectorProvider` keepAlive too, make `teamMembersApiProvider` auto-dispose, or read it per use outside build.
  • Captive dependency: keepAlive provider teamSecretsCallableProvider captures autoDispose activeConnectionFirebaseAuthProvider apps/dashboard/lib/secret_manager/secrets_backend.dart:30 — `teamSecretsCallableProvider` is a keep-alive Riverpod provider and calls `ref.watch(activeConnectionFirebaseAuthProvider…)`, which is declared auto-dispose (apps/dashboard/lib/connections/active_connection_firebase_auth.dart:11). The keep-alive provider listens to it for the life of the ProviderContainer, so `activeConnectionFirebaseAuthProvider` is never disposed — the auto-dispose lifetime it declares never happens, and whatever it holds (a socket, a controller, a stale value) is kept for every later reader. Mark `activeConnectionFirebaseAuthProvider` keepAlive too, make `teamSecretsCallableProvider` auto-dispose, or read it per use outside build.
  • Captive dependency: keepAlive provider routerProvider captures autoDispose authStateChangesProvider apps/dashboard/lib/router/router.dart:16 — `routerProvider` is a keep-alive Riverpod provider and calls `ref.listen(authStateChangesProvider…)`, which is declared auto-dispose (apps/dashboard/lib/auth/auth_provider.dart:31). The keep-alive provider listens to it for the life of the ProviderContainer, so `authStateChangesProvider` is never disposed — the auto-dispose lifetime it declares never happens, and whatever it holds (a socket, a controller, a stale value) is kept for every later reader. Mark `authStateChangesProvider` keepAlive too, make `routerProvider` auto-dispose, or read it per use outside build.
  • Captive dependency: keepAlive provider routerProvider captures autoDispose authStateChangesProvider apps/dashboard/lib/router/router.dart:57 — `routerProvider` is a keep-alive Riverpod provider and calls `ref.read(authStateChangesProvider…)`, which is declared auto-dispose (apps/dashboard/lib/auth/auth_provider.dart:31). Read in build, `authStateChangesProvider` has no listener once the read returns, so it is disposed at once — its ref.onDispose closes what it handed out — while `routerProvider` keeps that value for the life of the ProviderContainer. Mark `authStateChangesProvider` keepAlive too, make `routerProvider` auto-dispose, or read it per use outside build.
  • Captive dependency: keepAlive provider connectionStoreProvider captures autoDispose sharedPreferencesProvider apps/dashboard/lib/connections/connection_store_provider.dart:14 — `connectionStoreProvider` is a keep-alive Riverpod provider and calls `ref.watch(sharedPreferencesProvider…)`, which is declared auto-dispose (apps/dashboard/lib/utilities/shared_preferences_provider.dart:6). The keep-alive provider listens to it for the life of the ProviderContainer, so `sharedPreferencesProvider` is never disposed — the auto-dispose lifetime it declares never happens, and whatever it holds (a socket, a controller, a stale value) is kept for every later reader. Mark `sharedPreferencesProvider` keepAlive too, make `connectionStoreProvider` auto-dispose, or read it per use outside build.
  • Captive dependency: keepAlive provider billingApiProvider captures autoDispose authStateChangesProvider apps/dashboard/lib/billing/billing_api.dart:12 — `billingApiProvider` is a keep-alive Riverpod provider and calls `ref.watch(authStateChangesProvider…)`, which is declared auto-dispose (apps/dashboard/lib/auth/auth_provider.dart:31). The keep-alive provider listens to it for the life of the ProviderContainer, so `authStateChangesProvider` is never disposed — the auto-dispose lifetime it declares never happens, and whatever it holds (a socket, a controller, a stale value) is kept for every later reader. Mark `authStateChangesProvider` keepAlive too, make `billingApiProvider` auto-dispose, or read it per use outside build.
  • Captive dependency: keepAlive provider billingApiProvider captures autoDispose activeConnectionFirebaseAuthProvider apps/dashboard/lib/billing/billing_api.dart:14 — `billingApiProvider` is a keep-alive Riverpod provider and calls `ref.watch(activeConnectionFirebaseAuthProvider…)`, which is declared auto-dispose (apps/dashboard/lib/connections/active_connection_firebase_auth.dart:11). The keep-alive provider listens to it for the life of the ProviderContainer, so `activeConnectionFirebaseAuthProvider` is never disposed — the auto-dispose lifetime it declares never happens, and whatever it holds (a socket, a controller, a stale value) is kept for every later reader. Mark `activeConnectionFirebaseAuthProvider` keepAlive too, make `billingApiProvider` auto-dispose, or read it per use outside build.
  • Captive dependency: keepAlive provider accountSetupProvider captures autoDispose authStateChangesProvider apps/dashboard/lib/auth/account_setup_provider.dart:8 — `accountSetupProvider` is a keep-alive Riverpod provider and calls `ref.watch(authStateChangesProvider…)`, which is declared auto-dispose (apps/dashboard/lib/auth/auth_provider.dart:31). The keep-alive provider listens to it for the life of the ProviderContainer, so `authStateChangesProvider` is never disposed — the auto-dispose lifetime it declares never happens, and whatever it holds (a socket, a controller, a stale value) is kept for every later reader. Mark `authStateChangesProvider` keepAlive too, make `accountSetupProvider` auto-dispose, or read it per use outside build.
D30 · Dependency Vulnerabilities · High CVE · ×8
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
AC3 · Page structure · Document without a <title> · ×3
  • Document without a <title> apps/landing_page/app/(en)/layout.tsx:17 — A page with no <title> gives no name in the tab, history or screen-reader page list. Declare it the way this router does — Next App Router `export const metadata = { title }`, React Router/Remix `export function meta`, TanStack Start `head`, or a Helmet/Head component.
  • Document without a <title> apps/landing_page/app/(ja)/layout.tsx:17 — A page with no <title> gives no name in the tab, history or screen-reader page list. Declare it the way this router does — Next App Router `export const metadata = { title }`, React Router/Remix `export function meta`, TanStack Start `head`, or a Helmet/Head component.
  • Document without a <title> apps/landing_page/app/(redirect)/layout.tsx:17 — A page with no <title> gives no name in the tab, history or screen-reader page list. Declare it the way this router does — Next App Router `export const metadata = { title }`, React Router/Remix `export function meta`, TanStack Start `head`, or a Helmet/Head component.
D31 · IaC & Container Security · High IaC · ×3
  • REDACTED
  • REDACTED
  • REDACTED
D13 · REDACTED Scanning · Leaked secret · ×2
  • REDACTED
  • REDACTED
D30 · Dependency Vulnerabilities · Critical vulnerability · ×2
  • REDACTED
  • REDACTED
D30 · Dependency Vulnerabilities · Critical CVE · ×2
  • REDACTED
  • REDACTED
AC3 · Page structure · <html> without a lang · ×1
  • <html> without a lang apps/dashboard/web/index.html:2 — The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
D28 · Secrets (history) · High secret · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
Serious — 461 finding(s)
R4 · Test Coverage · No test reaches this file · ×30
  • No test reaches this file apps/landing_page/components/site.tsx:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file apps/landing_page/components/build-job-card-demo.tsx:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file REDACTED:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file apps/landing_page/lib/releases.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file firebase/functions/executor/runtime.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file infra/deploy/prepare.mjs:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file firebase/functions/index.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file firebase/functions/skipped_check_functions.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file firebase/functions/secret_functions.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file apps/landing_page/lib/seo.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file infra/orchard/check-network.mjs:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file firebase/functions/executor/main.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file apps/landing_page/app/(ja)/ja/releases/[slug]/page.tsx:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file apps/landing_page/app/(redirect)/page.tsx:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file infra/deploy/prepare-core.mjs:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file firebase/functions/secrets/store.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file firebase/functions/build_recovery_functions.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file apps/dashboard/web/flutter_bootstrap.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file firebase/functions/log_retention_functions.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file apps/landing_page/app/(en)/layout.tsx:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file apps/landing_page/app/(ja)/layout.tsx:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file apps/landing_page/app/(redirect)/layout.tsx:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file apps/landing_page/app/(en)/en/page.tsx:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file apps/landing_page/app/(ja)/ja/page.tsx:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file apps/landing_page/app/(ja)/ja/releases/page.tsx:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • + 5 more in this group — see findings.md.
D15 · Churn × Complexity Hotspots · Hotspot · ×24
  • Hotspot: firebase/functions/executor/github.ts firebase/functions/executor/github.ts:231 — firebase/functions/executor/github.ts changed 15 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 49 in ExecutionGitHub.resolveCheckout at line 231. 8 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-20..2026-11-18, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-20 01:07:43 +09:00' --until='2026-11-18 01:07:43 +09:00' --full-history --no-merges -- firebase/functions/executor/github.ts`: 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: apps/dashboard/lib/auth/auth_page.dart apps/dashboard/lib/auth/auth_page.dart:522 — apps/dashboard/lib/auth/auth_page.dart changed 11 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 58 in FirebaseFormSheet.build at line 522. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-20..2026-11-18, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-20 01:07:43 +09:00' --until='2026-11-18 01:07:43 +09:00' --full-history --no-merges -- apps/dashboard/lib/auth/auth_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: apps/openci_cli/lib/src/commands/setup/setup_asc_keys_command.dart apps/openci_cli/lib/src/commands/setup/setup_asc_keys_command.dart:96 — apps/openci_cli/lib/src/commands/setup/setup_asc_keys_command.dart changed 13 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 44 in SetupAscKeysCommand.run at line 96. 1 of those changes was a fix/bug commit, and the other 12 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-20..2026-11-18, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-20 01:07:43 +09:00' --until='2026-11-18 01:07:43 +09:00' --full-history --no-merges -- apps/openci_cli/lib/src/commands/setup/setup_asc_keys_command.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: firebase/functions/executor/execute.ts firebase/functions/executor/execute.ts:86 — firebase/functions/executor/execute.ts changed 10 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 53 in execute.executeBuild at line 86. 4 of those changes were fix/bug commits, 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-08-20..2026-11-18, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-20 01:07:43 +09:00' --until='2026-11-18 01:07:43 +09:00' --full-history --no-merges -- firebase/functions/executor/execute.ts`: 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: firebase/functions/build_dispatch_functions.ts firebase/functions/build_dispatch_functions.ts:270 — firebase/functions/build_dispatch_functions.ts changed 12 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 28 in build_dispatch_functions.dispatchBuildJob at line 270. 6 of those changes were fix/bug commits, 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-08-20..2026-11-18, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-20 01:07:43 +09:00' --until='2026-11-18 01:07:43 +09:00' --full-history --no-merges -- firebase/functions/build_dispatch_functions.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: REDACTED REDACTED:289 — REDACTED changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 38 in pull_request_qr.publishPullRequestQrCodes at line 289. 1 of those changes was a fix/bug commit, and the other 4 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-20..2026-11-18, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-20 01:07:43 +09:00' --until='2026-11-18 01:07:43 +09:00' --full-history --no-merges -- REDACTED`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: apps/dashboard/lib/billing/billing_view.dart apps/dashboard/lib/billing/billing_view.dart:27 — apps/dashboard/lib/billing/billing_view.dart changed 9 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 17 in BillingView.build at line 27. 2 of those changes were fix/bug commits, and the other 7 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-20..2026-11-18, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-20 01:07:43 +09:00' --until='2026-11-18 01:07:43 +09:00' --full-history --no-merges -- apps/dashboard/lib/billing/billing_view.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: apps/dashboard/lib/billing/billing_actions.dart apps/dashboard/lib/billing/billing_actions.dart:29 — apps/dashboard/lib/billing/billing_actions.dart changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 27 in BillingActions._create at line 29. 2 of those changes were fix/bug commits, and the other 3 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-20..2026-11-18, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-20 01:07:43 +09:00' --until='2026-11-18 01:07:43 +09:00' --full-history --no-merges -- apps/dashboard/lib/billing/billing_actions.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: firebase/dart_functions/lib/src/create_build_jobs.dart firebase/dart_functions/lib/src/create_build_jobs.dart:38 — firebase/dart_functions/lib/src/create_build_jobs.dart changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 22 in BuildJobPlanner._processOnce at line 38. 3 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-20..2026-11-18, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-20 01:07:43 +09:00' --until='2026-11-18 01:07:43 +09:00' --full-history --no-merges -- firebase/dart_functions/lib/src/create_build_jobs.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: apps/dashboard/lib/secret_manager/secret_manager_page.dart apps/dashboard/lib/secret_manager/secret_manager_page.dart:980 — apps/dashboard/lib/secret_manager/secret_manager_page.dart changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 26 in _AddSecretBottomSheet.build at line 980. 1 of those changes was a fix/bug commit, and the other 3 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-20..2026-11-18, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-20 01:07:43 +09:00' --until='2026-11-18 01:07:43 +09:00' --full-history --no-merges -- apps/dashboard/lib/secret_manager/secret_manager_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: firebase/dart_functions/lib/src/planning_event.dart firebase/dart_functions/lib/src/planning_event.dart:30 — firebase/dart_functions/lib/src/planning_event.dart changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 29 in PlanningEvent.parse at line 30. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-20..2026-11-18, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-20 01:07:43 +09:00' --until='2026-11-18 01:07:43 +09:00' --full-history --no-merges -- firebase/dart_functions/lib/src/planning_event.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: firebase/functions/queued_checks.ts firebase/functions/queued_checks.ts:79 — firebase/functions/queued_checks.ts changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 28 in QueuedChecks.sync at line 79. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-20..2026-11-18, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-20 01:07:43 +09:00' --until='2026-11-18 01:07:43 +09:00' --full-history --no-merges -- firebase/functions/queued_checks.ts`: 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: firebase/functions/billing/service.ts firebase/functions/billing/service.ts:34 — firebase/functions/billing/service.ts changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 20 in Billing.execute at line 34. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-20..2026-11-18, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-20 01:07:43 +09:00' --until='2026-11-18 01:07:43 +09:00' --full-history --no-merges -- firebase/functions/billing/service.ts`: 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: apps/dashboard/lib/secret_manager/secret_manager_provider.dart apps/dashboard/lib/secret_manager/secret_manager_provider.dart:49 — apps/dashboard/lib/secret_manager/secret_manager_provider.dart changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 17 in SecretManager._call at line 49. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-20..2026-11-18, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-20 01:07:43 +09:00' --until='2026-11-18 01:07:43 +09:00' --full-history --no-merges -- apps/dashboard/lib/secret_manager/secret_manager_provider.dart`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: firebase/dart_functions/lib/src/github_workflows.dart firebase/dart_functions/lib/src/github_workflows.dart:76 — firebase/dart_functions/lib/src/github_workflows.dart changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 22 in GitHubWorkflows.observePullRequest at line 76. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-20..2026-11-18, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-20 01:07:43 +09:00' --until='2026-11-18 01:07:43 +09:00' --full-history --no-merges -- firebase/dart_functions/lib/src/github_workflows.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: apps/dashboard/lib/cicd_log/detail/ci_cd_log_detail_page.dart apps/dashboard/lib/cicd_log/detail/ci_cd_log_detail_page.dart:62 — apps/dashboard/lib/cicd_log/detail/ci_cd_log_detail_page.dart changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in CicdLogDetailPage.build at line 62. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-20..2026-11-18, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-20 01:07:43 +09:00' --until='2026-11-18 01:07:43 +09:00' --full-history --no-merges -- apps/dashboard/lib/cicd_log/detail/ci_cd_log_detail_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: apps/dashboard/lib/generated/builds/get_build_jobs.dart apps/dashboard/lib/generated/builds/get_build_jobs.dart:149 — apps/dashboard/lib/generated/builds/get_build_jobs.dart changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 31 in GetBuildJobsBuildJobs.== at line 149. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-20..2026-11-18, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-20 01:07:43 +09:00' --until='2026-11-18 01:07:43 +09:00' --full-history --no-merges -- apps/dashboard/lib/generated/builds/get_build_jobs.dart`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: packages/openci_workflow/lib/src/pull_request_ci.dart packages/openci_workflow/lib/src/pull_request_ci.dart:56 — packages/openci_workflow/lib/src/pull_request_ci.dart changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 20 in PullRequestCI.postQrCode at line 56. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-20..2026-11-18, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-20 01:07:43 +09:00' --until='2026-11-18 01:07:43 +09:00' --full-history --no-merges -- packages/openci_workflow/lib/src/pull_request_ci.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: firebase/functions/billing/webhook.ts firebase/functions/billing/webhook.ts:23 — firebase/functions/billing/webhook.ts changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 24 in webhook.receiveStripeWebhook at line 23. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-20..2026-11-18, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-20 01:07:43 +09:00' --until='2026-11-18 01:07:43 +09:00' --full-history --no-merges -- firebase/functions/billing/webhook.ts`: 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: firebase/functions/github_connection/github.ts firebase/functions/github_connection/github.ts:174 — firebase/functions/github_connection/github.ts changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 23 in OctokitConnectionClient.repositories at line 174. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-20..2026-11-18, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-20 01:07:43 +09:00' --until='2026-11-18 01:07:43 +09:00' --full-history --no-merges -- firebase/functions/github_connection/github.ts`: 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: firebase/functions/github_webhook.ts firebase/functions/github_webhook.ts:11 — firebase/functions/github_webhook.ts changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 23 in github_webhook.receiveGitHubWebhook at line 11. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-20..2026-11-18, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-20 01:07:43 +09:00' --until='2026-11-18 01:07:43 +09:00' --full-history --no-merges -- firebase/functions/github_webhook.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: packages/openci_workflow/lib/src/flutter/firebase_app_distribution/firebase_app_distribution_client.dart packages/openci_workflow/lib/src/flutter/firebase_app_distribution/firebase_app_distribution_client.dart:33 — packages/openci_workflow/lib/src/flutter/firebase_app_distribution/firebase_app_distribution_client.dart changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 20 in FirebaseAppDistributionClient.upload at line 33. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-20..2026-11-18, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-20 01:07:43 +09:00' --until='2026-11-18 01:07:43 +09:00' --full-history --no-merges -- packages/openci_workflow/lib/src/flutter/firebase_app_distribution/firebase_app_distribution_client.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: apps/dashboard/lib/team/delete_team_bottom_sheet.dart apps/dashboard/lib/team/delete_team_bottom_sheet.dart:14 — apps/dashboard/lib/team/delete_team_bottom_sheet.dart changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 18 in DeleteTeamBottomSheet.build at line 14. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-20..2026-11-18, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-20 01:07:43 +09:00' --until='2026-11-18 01:07:43 +09:00' --full-history --no-merges -- apps/dashboard/lib/team/delete_team_bottom_sheet.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: firebase/functions/billing/config.ts firebase/functions/billing/config.ts:12 — firebase/functions/billing/config.ts changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 17 in config.billingConfig at line 12. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-20..2026-11-18, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-20 01:07:43 +09:00' --until='2026-11-18 01:07:43 +09:00' --full-history --no-merges -- firebase/functions/billing/config.ts`: 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.
X3 · Exception handling · Swallowed exception (empty catch) · ×16
  • Swallowed exception (empty catch) firebase/functions/github_connection/vault.ts:53 — `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
  • Swallowed exception (empty catch) firebase/functions/executor/billing.ts:116 — 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) firebase/functions/executor/billing.ts:146 — 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) firebase/functions/executor/billing.ts:174 — 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) firebase/functions/executor/billing.ts:243 — 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) firebase/functions/executor/logs.ts:201 — `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
  • Swallowed exception (empty catch) firebase/functions/executor/orchard.ts:127 — 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) firebase/functions/executor/store.ts:115 — 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) firebase/functions/billing/card_setup.ts:158 — 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) firebase/functions/billing/service.ts:158 — 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) firebase/functions/billing/service.ts:171 — 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) firebase/functions/billing/service.ts:216 — 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) firebase/functions/billing/service.ts:248 — 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) firebase/functions/billing/service.ts:296 — 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) firebase/functions/billing/store.ts:88 — 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) apps/openci_cli/lib/src/extensions/file_extensions.dart:46 — 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.
D3 · God Classes · MethodTooLong · ×14
  • MethodTooLong: AuthPage.build apps/dashboard/lib/auth/auth_page.dart:32 — MethodTooLong — build runs 346 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 246 over it, 3.46× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: FirebaseFormSheet.build apps/dashboard/lib/auth/auth_page.dart:522 — MethodTooLong — build runs 328 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 228 over it, 3.28× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: _EditSecretBottomSheet.build apps/dashboard/lib/secret_manager/secret_manager_page.dart:1495 — MethodTooLong — build runs 266 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 166 over it, 2.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: SelfHostedSetupForm.build apps/dashboard/lib/auth/self_hosted_setup_form.dart:31 — MethodTooLong — build 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: _AddSecretBottomSheet.build apps/dashboard/lib/secret_manager/secret_manager_page.dart:980 — MethodTooLong — build runs 248 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 148 over it, 2.48× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: InviteTeamMemberBottomSheet.build apps/dashboard/lib/team/invite_team_member_bottom_sheet.dart:19 — MethodTooLong — build runs 201 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 101 over it, 2.01× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: TeamMembersBottomSheet.build apps/dashboard/lib/team/team_members_bottom_sheet.dart:46 — MethodTooLong — build runs 194 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 94 over it, 1.94× 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: EditTeamBottomSheet.build apps/dashboard/lib/team/edit_team_bottom_sheet.dart:12 — MethodTooLong — build 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: DeleteTeamBottomSheet.build apps/dashboard/lib/team/delete_team_bottom_sheet.dart:14 — 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: _SecretValueDialog.build apps/dashboard/lib/secret_manager/secret_manager_page.dart:600 — MethodTooLong — build runs 164 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 64 over it, 1.64× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: ExecutionGitHub.resolveCheckout firebase/functions/executor/github.ts:231 — MethodTooLong — resolveCheckout runs 145 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 45 over it, 1.45× 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: FirebaseHostingConfig.load packages/openci_workflow/lib/src/firebase_hosting/firebase_hosting_config.dart:16 — MethodTooLong — load runs 134 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 34 over it, 1.34× 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: SetupAscKeysCommand.run apps/openci_cli/lib/src/commands/setup/setup_asc_keys_command.dart:96 — MethodTooLong — run runs 116 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 16 over it, 1.16× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: ShorebirdCI.releaseIos packages/openci_workflow/lib/src/shorebird/shorebird_ci.dart:220 — MethodTooLong — releaseIos runs 108 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 8 over it, 1.08× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
D31 · IaC & Container Security · Medium IaC · ×14
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D30 · Dependency Vulnerabilities · Medium CVE · ×8
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
SC1 · Supply-chain hygiene · JavaScript dependencies are not locked · ×8
  • JavaScript dependencies are not locked firebase/generated/billing-admin/package.json:19 — firebase/generated/billing-admin/package.json declares dependencies that no committed lockfile resolves — there is no REDACTED / yarn.lock / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
  • JavaScript dependencies are not locked firebase/generated/builds-admin/package.json:19 — firebase/generated/builds-admin/package.json declares dependencies that no committed lockfile resolves — there is no REDACTED / yarn.lock / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
  • JavaScript dependencies are not locked firebase/generated/dispatch-admin/package.json:19 — firebase/generated/dispatch-admin/package.json declares dependencies that no committed lockfile resolves — there is no REDACTED / yarn.lock / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
  • JavaScript dependencies are not locked firebase/generated/github-admin/package.json:19 — firebase/generated/github-admin/package.json declares dependencies that no committed lockfile resolves — there is no REDACTED / yarn.lock / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
  • JavaScript dependencies are not locked firebase/generated/logs-admin/package.json:19 — firebase/generated/logs-admin/package.json declares dependencies that no committed lockfile resolves — there is no REDACTED / yarn.lock / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
  • JavaScript dependencies are not locked firebase/generated/secrets-admin/package.json:19 — firebase/generated/secrets-admin/package.json declares dependencies that no committed lockfile resolves — there is no REDACTED / yarn.lock / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
  • JavaScript dependencies are not locked firebase/generated/teams-admin/package.json:19 — firebase/generated/teams-admin/package.json declares dependencies that no committed lockfile resolves — there is no REDACTED / yarn.lock / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
  • JavaScript dependencies are not locked firebase/generated/webhooks-admin/package.json:19 — firebase/generated/webhooks-admin/package.json declares dependencies that no committed lockfile resolves — there is no REDACTED / yarn.lock / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
D4 · Code Duplication · Duplicated block (5 lines × 2) · ×5
  • Duplicated block (5 lines × 2) apps/dashboard/lib/generated/secrets/get_secrets.dart:144 — apps/dashboard/lib/generated/secrets/get_secrets.dart:144-148 | apps/dashboard/lib/generated/teams/get_team_members.dart:159-163 — before extracting anything, compare `apps/dashboard/lib/generated/secrets/get_secrets.dart` and `apps/dashboard/lib/generated/teams/get_team_members.dart` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 31 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (5 lines × 2) apps/dashboard/lib/generated/teams/get_my_teams.dart:112 — apps/dashboard/lib/generated/teams/get_my_teams.dart:112-116 | apps/dashboard/lib/generated/teams/get_team_members.dart:88-92 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (5 lines × 2) apps/dashboard/lib/generated/logs/create_build_step.dart:105 — apps/dashboard/lib/generated/logs/create_build_step.dart:105-109 | apps/dashboard/lib/generated/secrets/queue_secret_version_cleanup.dart:101-105 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (5 lines × 2) apps/dashboard/lib/generated/logs/delete_expired_build_logs.dart:61 — apps/dashboard/lib/generated/logs/delete_expired_build_logs.dart:61-65 | apps/dashboard/lib/generated/logs/update_build_step.dart:66-70 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (5 lines × 2) apps/dashboard/lib/generated/logs/get_expired_build_logs.dart:11 — apps/dashboard/lib/generated/logs/get_expired_build_logs.dart:11-15 | apps/dashboard/lib/generated/secrets/get_due_secret_versions.dart:11-15 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D3 · God Classes · FileTooLong · ×4
  • FileTooLong: secret_manager/secret_manager_page.dart apps/dashboard/lib/secret_manager/secret_manager_page.dart — FileTooLong — 1402 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 902 over it, 2.80× 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: components/site.tsx apps/landing_page/components/site.tsx — FileTooLong — 894 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 394 over it, 1.79× 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: auth/auth_page.dart apps/dashboard/lib/auth/auth_page.dart — FileTooLong — 705 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 205 over it, 1.41× 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: settings/settings_page.dart apps/dashboard/lib/settings/settings_page.dart — FileTooLong — 504 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 4 over it, 1.01× 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.
D4 · Code Duplication · Duplicated block (12 lines × 2) · ×4
  • Duplicated block (12 lines × 2) apps/dashboard/lib/secret_manager/secret_manager_page.dart:1116 — apps/dashboard/lib/secret_manager/secret_manager_page.dart:1116-1127 | apps/dashboard/lib/team/invite_team_member_bottom_sheet.dart:188-199 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `apps/dashboard/lib/secret_manager/secret_manager_page.dart:1116` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (12 lines × 2) apps/openci_cli/lib/src/commands/delete/delete_secret_command.dart:83 — apps/openci_cli/lib/src/commands/delete/delete_secret_command.dart:83-94 | apps/openci_cli/lib/src/commands/list/list_secrets_command.dart:74-85 — before extracting anything, compare `apps/openci_cli/lib/src/commands/delete/delete_secret_command.dart` and `apps/openci_cli/lib/src/commands/list/list_secrets_command.dart` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 40 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `apps/openci_cli/lib/src/commands/delete/delete_secret_command.dart:83` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (12 lines × 2) apps/openci_cli/lib/src/commands/list/list_teams_command.dart:73 — apps/openci_cli/lib/src/commands/list/list_teams_command.dart:73-84 | apps/openci_cli/lib/src/commands/switch/switch_team_command.dart:133-144 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `apps/openci_cli/lib/src/commands/list/list_teams_command.dart:73` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (12 lines × 2) packages/openci_workflow/lib/src/flutter/flutter_ci.dart:61 — packages/openci_workflow/lib/src/flutter/flutter_ci.dart:61-72 | packages/openci_workflow/lib/src/flutter/flutter_ci.dart:75-86 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `packages/openci_workflow/lib/src/flutter/flutter_ci.dart:61` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
AC3 · Page structure · Page without a main landmark · ×3
  • Page without a main landmark apps/dashboard/web/index.html:2 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
  • Page without a main landmark apps/landing_page/app/(en)/layout.tsx:17 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
  • Page without a main landmark apps/landing_page/app/(ja)/layout.tsx:17 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
D3 · God Classes · FunctionTooLong · ×3
  • FunctionTooLong: build-job-card-demo.BuildJobCardDemo apps/landing_page/components/build-job-card-demo.tsx:95 — FunctionTooLong — BuildJobCardDemo runs 290 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 190 over it, 2.90× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: site.CicdPage apps/landing_page/components/site.tsx:149 — FunctionTooLong — CicdPage 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.
  • FunctionTooLong: pull_request_qr.publishPullRequestQrCodes REDACTED:289 — FunctionTooLong — publishPullRequestQrCodes runs 105 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 5 over it, 1.05× 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.
D4 · Code Duplication · Edited copy of a member (15 corresponding lines) · ×3
  • Edited copy of a member (15 corresponding lines) apps/dashboard/lib/generated/builds/get_build_jobs.dart:371 — apps/dashboard/lib/generated/builds/get_build_jobs.dart:371-385 | apps/dashboard/lib/generated/logs/get_build_logs.dart:233-248 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (15 corresponding lines) apps/dashboard/lib/generated/logs/get_build_log_write_state.dart:54 — apps/dashboard/lib/generated/logs/get_build_log_write_state.dart:54-69 | apps/dashboard/lib/generated/logs/get_build_logs.dart:69-83 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (15 corresponding lines) REDACTED:22 — REDACTED:22-43 | REDACTED:45-59 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (6 corresponding lines) · ×3
  • Edited copy of a member (6 corresponding lines) apps/dashboard/lib/generated/teams/add_team_member.dart:178 — apps/dashboard/lib/generated/teams/add_team_member.dart:178-184 | apps/dashboard/lib/generated/secrets/get_managed_secret_context.dart:195-200 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (6 corresponding lines) apps/dashboard/lib/generated/builds/retry_build_job.dart:205 — apps/dashboard/lib/generated/builds/retry_build_job.dart:205-210 | apps/dashboard/lib/generated/teams/create_team.dart:166-171 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (6 corresponding lines) apps/dashboard/lib/generated/builds/retry_build_job.dart:162 — apps/dashboard/lib/generated/builds/retry_build_job.dart:162-169 | apps/dashboard/lib/generated/logs/append_build_log.dart:128-133 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Duplicated block (10 lines × 2) · ×3
  • Duplicated block (10 lines × 2) apps/dashboard/lib/generated/logs/get_build_log_state.dart:141 — apps/dashboard/lib/generated/logs/get_build_log_state.dart:141-150 | apps/dashboard/lib/generated/logs/get_build_step_write_state.dart:117-126 — before extracting anything, compare `apps/dashboard/lib/generated/logs/get_build_log_state.dart` and `apps/dashboard/lib/generated/logs/get_build_step_write_state.dart` as WHOLE FILES: this scan already matched 4 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. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (10 lines × 2) apps/dashboard/lib/generated/logs/logs.dart:59 — apps/dashboard/lib/generated/logs/logs.dart:59-68 | apps/dashboard/lib/generated/secrets/secrets.dart:34-43 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (10 lines × 2) apps/dashboard/macos/Runner/MainFlutterWindow.swift:5 — apps/dashboard/macos/Runner/MainFlutterWindow.swift:5-14 | packages/macos_updater/example/macos/Runner/MainFlutterWindow.swift:5-14 — before extracting anything, compare `apps/dashboard/macos/Runner/MainFlutterWindow.swift` and `packages/macos_updater/example/macos/Runner/MainFlutterWindow.swift` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
R10 · Code Duplication · Duplicated block (14 lines × 2 locations) · ×3
  • Duplicated block (14 lines × 2 locations) apps/landing_page/components/build-job-card-demo.tsx:290 — apps/landing_page/components/build-job-card-demo.tsx:290 · apps/landing_page/components/build-job-card-demo.tsx: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 (14 lines × 2 locations) apps/landing_page/components/site.tsx:186 — apps/landing_page/components/site.tsx:186 · apps/landing_page/components/site.tsx:211 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (14 lines × 2 locations) firebase/functions/secret_functions.ts:24 — firebase/functions/secret_functions.ts:24 · firebase/functions/team_functions.ts:10 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
X3 · Exception handling · Swallowed exception (caught, then discarded) · ×3
  • Swallowed exception (caught, then discarded) firebase/functions/executor/billing.ts:94 — `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, or keep only the failure you expect and rethrow the rest (`catch (e) { if (!(e instanceof SyntaxError)) throw e; … }`, or test `e.name`), because a JavaScript catch takes every exception, programming errors included.
  • Swallowed exception (caught, then discarded) firebase/functions/executor/billing.ts:220 — `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, or keep only the failure you expect and rethrow the rest (`catch (e) { if (!(e instanceof SyntaxError)) throw e; … }`, or test `e.name`), because a JavaScript catch takes every exception, programming errors included.
  • Swallowed exception (caught, then discarded) firebase/dart_functions/lib/src/open_ci_parser.dart:96 — `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.
D1 · Cyclomatic Complexity · build-job-card-demo.BuildJobCardDemo · ×2
  • build-job-card-demo.BuildJobCardDemo::getJobStatus (cyclomatic 20) apps/landing_page/components/build-job-card-demo.tsx:141 — build-job-card-demo.BuildJobCardDemo::getJobStatus has cyclomatic complexity 20 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages. This shape REPEATS in the file: one other method here (build-job-card-demo.BuildJobCardDemo::getJobDuration) 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.
  • build-job-card-demo.BuildJobCardDemo::getJobDuration (cyclomatic 16) apps/landing_page/components/build-job-card-demo.tsx:174 — build-job-card-demo.BuildJobCardDemo::getJobDuration has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This shape REPEATS in the file: one other method here (build-job-card-demo.BuildJobCardDemo::getJobStatus) 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.
D10 · Test Quality · No assertions · ×2
  • No assertions: allows a new Google user firebase/functions/test/auth_signup_policy.test.mjs:12 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: malformed task payloads are acknowledged without accessing configured services firebase/functions/test/build_dispatch_functions.test.mjs:422 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
D2 · Cognitive Complexity · build-job-card-demo.BuildJobCardDemo · ×2
  • build-job-card-demo.BuildJobCardDemo::getJobStatus (cognitive 31) apps/landing_page/components/build-job-card-demo.tsx:141 — build-job-card-demo.BuildJobCardDemo::getJobStatus has cognitive complexity 31 (threshold 15). Drivers by points: if/else 24 (30 pts), boolean chains 1 (nesting depth added 6). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level. This shape REPEATS in the file: 2 other methods here (build-job-card-demo.BuildJobCardDemo, build-job-card-demo.BuildJobCardDemo::getJobDuration) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
  • build-job-card-demo.BuildJobCardDemo::getJobDuration (cognitive 21) apps/landing_page/components/build-job-card-demo.tsx:174 — build-job-card-demo.BuildJobCardDemo::getJobDuration has cognitive complexity 21 (threshold 15). Drivers by points: if/else 14 (20 pts), boolean chains 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: 2 other methods here (build-job-card-demo.BuildJobCardDemo, build-job-card-demo.BuildJobCardDemo::getJobStatus) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D4 · Code Duplication · Edited copy of a member (40 corresponding lines) · ×2
  • Edited copy of a member (40 corresponding lines) apps/openci_cli/lib/src/commands/list/list_secrets_command.dart:27 — apps/openci_cli/lib/src/commands/list/list_secrets_command.dart:27-66 | apps/openci_cli/lib/src/commands/list/list_teams_command.dart:27-70 — These two members are one piece of code written twice and then edited apart: 40 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (40 corresponding lines) apps/dashboard/lib/generated/builds/get_build_job.dart:135 — apps/dashboard/lib/generated/builds/get_build_job.dart:135-174 | apps/dashboard/lib/generated/builds/get_build_jobs.dart:149-188 — These two members are one piece of code written twice and then edited apart: 40 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (11 corresponding lines) · ×2
  • Edited copy of a member (11 corresponding lines) apps/dashboard/lib/generated/secrets/commit_managed_secret.dart:214 — apps/dashboard/lib/generated/secrets/commit_managed_secret.dart:214-224 | apps/dashboard/lib/generated/secrets/rename_managed_secret.dart:269-280 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (11 corresponding lines) apps/dashboard/lib/generated/builds/get_build_jobs.dart:405 — apps/dashboard/lib/generated/builds/get_build_jobs.dart:405-415 | apps/dashboard/lib/generated/logs/get_build_logs.dart:273-284 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 8+ corresponding lines) · ×2
  • Edited copies of one member (3 members, 8+ corresponding lines) apps/dashboard/lib/build_logs/chips/job_status.dart:12 — apps/dashboard/lib/build_logs/chips/job_status.dart:12-19 | apps/dashboard/lib/build_logs/chips/job_status.dart:21-28 | apps/dashboard/lib/build_logs/chips/job_status.dart:30-37 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 8+ corresponding lines) apps/dashboard/lib/generated/secrets/delete_managed_secret.dart:162 — apps/dashboard/lib/generated/secrets/delete_managed_secret.dart:162-169 | apps/dashboard/lib/generated/secrets/get_managed_secret_context.dart:108-115 | apps/dashboard/lib/generated/secrets/get_secrets.dart:69-76 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (7 corresponding lines) · ×2
  • Edited copy of a member (7 corresponding lines) apps/dashboard/lib/generated/secrets/delete_managed_secret.dart:106 — apps/dashboard/lib/generated/secrets/delete_managed_secret.dart:106-115 | apps/dashboard/lib/generated/teams/rename_team.dart:90-96 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (7 corresponding lines) apps/dashboard/lib/generated/logs/get_build_log_write_state.dart:71 — apps/dashboard/lib/generated/logs/get_build_log_write_state.dart:71-77 | apps/dashboard/lib/generated/logs/get_build_logs.dart:85-91 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Duplicated block (20–21 lines × 2) · ×2
  • Duplicated block (20–21 lines × 2) apps/dashboard/lib/team/delete_team_bottom_sheet.dart:53 — apps/dashboard/lib/team/delete_team_bottom_sheet.dart:53-73 | apps/dashboard/lib/team/invite_team_member_bottom_sheet.dart:78-97 — before extracting anything, compare `apps/dashboard/lib/team/delete_team_bottom_sheet.dart` and `apps/dashboard/lib/team/invite_team_member_bottom_sheet.dart` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 68 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `apps/dashboard/lib/team/delete_team_bottom_sheet.dart:53` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (20–21 lines × 2) apps/dashboard/lib/team/team_members_bottom_sheet.dart:60 — apps/dashboard/lib/team/team_members_bottom_sheet.dart:60-79 | apps/dashboard/lib/team/team_members_bottom_sheet.dart:166-186 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `apps/dashboard/lib/team/team_members_bottom_sheet.dart:60` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (18 lines × 2) · ×2
  • Duplicated block (18 lines × 2) apps/dashboard/lib/team/delete_team_bottom_sheet.dart:228 — apps/dashboard/lib/team/delete_team_bottom_sheet.dart:228-245 | apps/dashboard/lib/team/edit_team_bottom_sheet.dart:230-247 — before extracting anything, compare `apps/dashboard/lib/team/delete_team_bottom_sheet.dart` and `apps/dashboard/lib/team/edit_team_bottom_sheet.dart` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 60 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `apps/dashboard/lib/team/delete_team_bottom_sheet.dart:228` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (18 lines × 2) packages/openci_workflow/lib/src/shorebird/shorebird_ci.dart:27 — packages/openci_workflow/lib/src/shorebird/shorebird_ci.dart:27-44 | packages/openci_workflow/lib/src/shorebird/shorebird_ci.dart:240-257 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `packages/openci_workflow/lib/src/shorebird/shorebird_ci.dart:27` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (15–16 lines × 2) · ×2
  • Duplicated block (15–16 lines × 2) apps/dashboard/lib/secret_manager/secret_manager_page.dart:262 — apps/dashboard/lib/secret_manager/secret_manager_page.dart:262-276 | apps/dashboard/lib/secret_manager/secret_manager_page.dart:308-323 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `apps/dashboard/lib/secret_manager/secret_manager_page.dart:262` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `apps/dashboard/lib/secret_manager/secret_manager_page.dart:324` calls `SizedBox` and `apps/dashboard/lib/secret_manager/secret_manager_page.dart:277` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (15–16 lines × 2) apps/dashboard/lib/settings/settings_page.dart:265 — apps/dashboard/lib/settings/settings_page.dart:265-279 | apps/dashboard/lib/team/switch_team_bottom_sheet.dart:461-476 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `apps/dashboard/lib/settings/settings_page.dart:265` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (15 lines × 2) · ×2
  • Duplicated block (15 lines × 2) apps/dashboard/lib/secret_manager/secret_manager_page.dart:614 — apps/dashboard/lib/secret_manager/secret_manager_page.dart:614-628 | apps/dashboard/lib/secret_manager/secret_manager_page.dart:895-909 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `apps/dashboard/lib/secret_manager/secret_manager_page.dart:614` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (15 lines × 2) apps/dashboard/lib/secret_manager/secret_manager_page.dart:1628 — apps/dashboard/lib/secret_manager/secret_manager_page.dart:1628-1642 | apps/dashboard/lib/team/edit_team_bottom_sheet.dart:150-164 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `apps/dashboard/lib/secret_manager/secret_manager_page.dart:1628` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (14 lines × 2) · ×2
  • Duplicated block (14 lines × 2) apps/dashboard/lib/generated/logs/get_build_log_write_state.dart:152 — apps/dashboard/lib/generated/logs/get_build_log_write_state.dart:152-165 | apps/dashboard/lib/generated/logs/get_build_logs.dart:166-179 — before extracting anything, compare `apps/dashboard/lib/generated/logs/get_build_log_write_state.dart` and `apps/dashboard/lib/generated/logs/get_build_logs.dart` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 52 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (14 lines × 2) apps/dashboard/lib/team/delete_team_bottom_sheet.dart:94 — apps/dashboard/lib/team/delete_team_bottom_sheet.dart:94-107 | apps/dashboard/lib/team/invite_team_member_bottom_sheet.dart:119-132 — before extracting anything, compare `apps/dashboard/lib/team/delete_team_bottom_sheet.dart` and `apps/dashboard/lib/team/invite_team_member_bottom_sheet.dart` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 68 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `apps/dashboard/lib/team/delete_team_bottom_sheet.dart:94` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (13–14 lines × 2) · ×2
  • Duplicated block (13–14 lines × 2) apps/dashboard/lib/secret_manager/secret_manager_page.dart:995 — apps/dashboard/lib/secret_manager/secret_manager_page.dart:995-1008 | apps/dashboard/lib/secret_manager/secret_manager_page.dart:1510-1522 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `apps/dashboard/lib/secret_manager/secret_manager_page.dart:995` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
  • Duplicated block (13–14 lines × 2) apps/dashboard/lib/secret_manager/secret_manager_page.dart:1516 — apps/dashboard/lib/secret_manager/secret_manager_page.dart:1516-1529 | apps/dashboard/lib/secret_manager/secret_manager_page.dart:1611-1623 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `apps/dashboard/lib/secret_manager/secret_manager_page.dart:1516` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (11 lines × 2) · ×2
  • Duplicated block (11 lines × 2) apps/dashboard/lib/generated/logs/get_build_log_state.dart:152 — apps/dashboard/lib/generated/logs/get_build_log_state.dart:152-162 | apps/dashboard/lib/generated/logs/get_build_step_write_state.dart:128-138 — before extracting anything, compare `apps/dashboard/lib/generated/logs/get_build_log_state.dart` and `apps/dashboard/lib/generated/logs/get_build_step_write_state.dart` as WHOLE FILES: this scan already matched 4 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. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (11 lines × 2) apps/dashboard/lib/generated/logs/get_build_log_write_state.dart:140 — apps/dashboard/lib/generated/logs/get_build_log_write_state.dart:140-150 | apps/dashboard/lib/generated/logs/get_build_logs.dart:154-164 — before extracting anything, compare `apps/dashboard/lib/generated/logs/get_build_log_write_state.dart` and `apps/dashboard/lib/generated/logs/get_build_logs.dart` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 52 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (7 lines × 2) · ×2
  • Duplicated block (7 lines × 2) apps/dashboard/lib/generated/logs/get_build_log_write_state.dart:79 — apps/dashboard/lib/generated/logs/get_build_log_write_state.dart:79-85 | apps/dashboard/lib/generated/logs/get_build_logs.dart:93-99 — before extracting anything, compare `apps/dashboard/lib/generated/logs/get_build_log_write_state.dart` and `apps/dashboard/lib/generated/logs/get_build_logs.dart` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 52 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `apps/dashboard/lib/generated/logs/get_build_log_write_state.dart:79` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (7 lines × 2) apps/dashboard/lib/generated/builds/get_build_job.dart:339 — apps/dashboard/lib/generated/builds/get_build_job.dart:339-345 | apps/dashboard/lib/generated/builds/retry_build_job.dart:58-64 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (5 lines × 3) · ×2
  • Duplicated block (5 lines × 3) apps/dashboard/lib/generated/logs/create_build_step.dart:159 — apps/dashboard/lib/generated/logs/create_build_step.dart:159-163 | apps/dashboard/lib/generated/logs/get_build_step_write_state.dart:220-224 | apps/dashboard/lib/generated/logs/update_build_step.dart:120-124 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `apps/dashboard/lib/generated/logs/create_build_step.dart:159` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `apps/dashboard/lib/generated/logs/update_build_step.dart:126` calls `bigIntToJson` and `apps/dashboard/lib/generated/logs/get_build_step_write_state.dart:225` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (5 lines × 3) apps/dashboard/lib/generated/secrets/commit_managed_secret.dart:214 — apps/dashboard/lib/generated/secrets/commit_managed_secret.dart:214-218 | apps/dashboard/lib/generated/secrets/delete_managed_secret.dart:162-166 | apps/dashboard/lib/generated/secrets/rename_managed_secret.dart:269-273 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `apps/dashboard/lib/generated/secrets/commit_managed_secret.dart:214` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `apps/dashboard/lib/generated/secrets/commit_managed_secret.dart:220` calls `toJson` and `apps/dashboard/lib/generated/secrets/delete_managed_secret.dart:167` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
R10 · Code Duplication · Duplicated block with local edits (11 matched lines × 2 locations) · ×2
  • Duplicated block with local edits (11 matched lines × 2 locations) firebase/functions/build_dispatch_functions.ts:61 — firebase/functions/build_dispatch_functions.ts:61 · firebase/functions/skipped_check_functions.ts:48 — the two spans are one implementation copied and then locally edited — 53 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
  • Duplicated block with local edits (11 matched lines × 2 locations) firebase/functions/executor/store.ts:85 — firebase/functions/executor/store.ts:85 · firebase/functions/executor/store.ts:110 — the two spans are one implementation copied and then locally edited — 67 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication · Duplicated block (8 lines × 2 locations) · ×2
  • Duplicated block (8 lines × 2 locations) apps/landing_page/components/build-job-card-demo.tsx:144 — apps/landing_page/components/build-job-card-demo.tsx:144 · apps/landing_page/components/build-job-card-demo.tsx:152 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
  • Duplicated block (8 lines × 2 locations) firebase/functions/executor/orchard.ts:161 — firebase/functions/executor/orchard.ts:161 · firebase/functions/orchard_capacity.ts:50 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
R10 · Code Duplication · Duplicated block (7 lines × 2 locations) · ×2
  • Duplicated block (7 lines × 2 locations) REDACTED:51 — REDACTED:51 · firebase/functions/github_connection_functions.ts:44 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
  • Duplicated block (7 lines × 2 locations) firebase/functions/executor/billing.ts:156 — firebase/functions/executor/billing.ts:156 · firebase/functions/executor/billing.ts:183 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication · Duplicated block (6 lines × 2 locations) · ×2
  • Duplicated block (6 lines × 2 locations) firebase/functions/github_connection/service.ts:63 — firebase/functions/github_connection/service.ts:63 · firebase/functions/secrets/service.ts:46 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
  • Duplicated block (6 lines × 2 locations) infra/deploy/prepare-core.mjs:5 — infra/deploy/prepare-core.mjs:5 · infra/deploy/prepare.mjs:6 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it.
X2 · Cancellation propagation · Async function without AbortSignal · ×2
  • Async function without AbortSignal: postPullRequestQrCodes firebase/functions/executor/github.ts:112 — `postPullRequestQrCodes` holds an AbortSignal but calls `client(…)` without it, so its caller's cancellation never reaches that call and it runs to its end after whatever wanted it has given up. Hand the signal on: `client(…, { signal })`.
  • Async function without AbortSignal: resolveCheckout firebase/functions/executor/github.ts:231 — `resolveCheckout` holds an AbortSignal but calls `client(…)` without it, so its caller's cancellation never reaches that call and it runs to its end after whatever wanted it has given up. Hand the signal on: `client(…, { signal })`.
AC1 · Text alternatives · <video> without a captions track · ×1
  • <video> without a captions track REDACTED:164 — Video with no captions <track> offers no captions. This player's source is set at runtime, so there is no caption file to author here: give the player a way to carry captions — accept a track/captions URL alongside the media and render a <track kind="captions"> when one is supplied — and capture that asset wherever the media enters the product (upload, import or generation).
D1 · Cyclomatic Complexity · FirebaseFormSheet.build (cyclomatic 58) · ×1
  • FirebaseFormSheet.build (cyclomatic 58) apps/dashboard/lib/auth/auth_page.dart:522 — FirebaseFormSheet.build has cyclomatic complexity 58 (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.
D1 · Cyclomatic Complexity · execute.executeBuild (cyclomatic 53) · ×1
  • execute.executeBuild (cyclomatic 53) firebase/functions/executor/execute.ts:86 — execute.executeBuild has cyclomatic complexity 53 (threshold 15). Of this number, 29 points are the body's own statements and 24 belong to 6 function items inside it that branch. 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.
D1 · Cyclomatic Complexity · SetupAscKeysCommand.run (cyclomatic 44) · ×1
  • SetupAscKeysCommand.run (cyclomatic 44) apps/openci_cli/lib/src/commands/setup/setup_asc_keys_command.dart:96 — SetupAscKeysCommand.run has cyclomatic complexity 44 (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.
D1 · Cyclomatic Complexity · TeamSecrets.execute (cyclomatic 39) · ×1
  • TeamSecrets.execute (cyclomatic 39) firebase/functions/secrets/service.ts:49 — TeamSecrets.execute has cyclomatic complexity 39 (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.
D1 · Cyclomatic Complexity · pull_request_qr.publishPullRequestQrCodes (cyclomatic 38) · ×1
  • pull_request_qr.publishPullRequestQrCodes (cyclomatic 38) REDACTED:289 — pull_request_qr.publishPullRequestQrCodes has cyclomatic complexity 38 (threshold 15). Most of this is not in the body itself: 15 of the 38 points are its own statements and the rest belongs to 4 function items inside it that branch (a function literal at line 390, findComment, current, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · FirebaseHostingConfig.load (cyclomatic 35) · ×1
  • FirebaseHostingConfig.load (cyclomatic 35) packages/openci_workflow/lib/src/firebase_hosting/firebase_hosting_config.dart:16 — FirebaseHostingConfig.load 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.
D1 · Cyclomatic Complexity · SelfHostedSetupForm.build (cyclomatic 34) · ×1
  • SelfHostedSetupForm.build (cyclomatic 34) apps/dashboard/lib/auth/self_hosted_setup_form.dart:31 — SelfHostedSetupForm.build has cyclomatic complexity 34 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · AuthPage.build (cyclomatic 33) · ×1
  • AuthPage.build (cyclomatic 33) apps/dashboard/lib/auth/auth_page.dart:32 — AuthPage.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.
D1 · Cyclomatic Complexity · OctokitConnectionClient.candidates (cyclomatic 32) · ×1
  • OctokitConnectionClient.candidates (cyclomatic 32) firebase/functions/github_connection/github.ts:102 — OctokitConnectionClient.candidates 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.
D1 · Cyclomatic Complexity · GetBuildJobJob.== (cyclomatic 31) · ×1
  • GetBuildJobJob.== (cyclomatic 31) apps/dashboard/lib/generated/builds/get_build_job.dart:135 — GetBuildJobJob.== has cyclomatic complexity 31 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · GetBuildJobsBuildJobs.== (cyclomatic 31) · ×1
  • GetBuildJobsBuildJobs.== (cyclomatic 31) apps/dashboard/lib/generated/builds/get_build_jobs.dart:149 — GetBuildJobsBuildJobs.== has cyclomatic complexity 31 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · _FilePicker.handle (cyclomatic 31) · ×1
  • _FilePicker.handle (cyclomatic 31) apps/openci_cli/lib/src/commands/register/select_secret_file.dart:51 — _FilePicker.handle 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.
D1 · Cyclomatic Complexity · OpenCICompletionCommand.run (cyclomatic 29) · ×1
  • OpenCICompletionCommand.run (cyclomatic 29) apps/openci_cli/lib/src/completion/openci_completion_command.dart:14 — OpenCICompletionCommand.run 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.
D1 · Cyclomatic Complexity · PlanningEvent.parse (cyclomatic 29) · ×1
  • PlanningEvent.parse (cyclomatic 29) firebase/dart_functions/lib/src/planning_event.dart:30 — PlanningEvent.parse 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.
D1 · Cyclomatic Complexity · FirebaseHostingClient.deploy (cyclomatic 29) · ×1
  • FirebaseHostingClient.deploy (cyclomatic 29) packages/openci_workflow/lib/src/firebase_hosting/firebase_hosting_client.dart:49 — FirebaseHostingClient.deploy 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.
D1 · Cyclomatic Complexity · orchard_capacity.hasOrchardCapacity (cyclomatic 29) · ×1
  • orchard_capacity.hasOrchardCapacity (cyclomatic 29) firebase/functions/orchard_capacity.ts:39 — orchard_capacity.hasOrchardCapacity has cyclomatic complexity 29 (threshold 15). Of this number, 24 points are the body's own statements and 5 belong to 4 function items inside it that branch. 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.
D1 · Cyclomatic Complexity · OrchardExecutor.checkWorkerMemory (cyclomatic 29) · ×1
  • OrchardExecutor.checkWorkerMemory (cyclomatic 29) firebase/functions/executor/orchard.ts:146 — OrchardExecutor.checkWorkerMemory has cyclomatic complexity 29 (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.
D1 · Cyclomatic Complexity · QueuedChecks.sync (cyclomatic 28) · ×1
  • QueuedChecks.sync (cyclomatic 28) firebase/functions/queued_checks.ts:79 — QueuedChecks.sync has cyclomatic complexity 28 (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.
D1 · Cyclomatic Complexity · build_dispatch_functions.dispatchBuildJob (cyclomatic 28) · ×1
  • build_dispatch_functions.dispatchBuildJob (cyclomatic 28) firebase/functions/build_dispatch_functions.ts:270 — build_dispatch_functions.dispatchBuildJob has cyclomatic complexity 28 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · GitHubConnections.execute (cyclomatic 28) · ×1
  • GitHubConnections.execute (cyclomatic 28) firebase/functions/github_connection/service.ts:66 — GitHubConnections.execute has cyclomatic complexity 28 (threshold 15). Of this number, 27 points are the body's own statements and 1 belongs to one function literal inside it that branches. 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.
D1 · Cyclomatic Complexity · BillingActions._create (cyclomatic 27) · ×1
  • BillingActions._create (cyclomatic 27) apps/dashboard/lib/billing/billing_actions.dart:29 — BillingActions._create has cyclomatic complexity 27 (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.
D1 · Cyclomatic Complexity · _AddSecretBottomSheet.build (cyclomatic 26) · ×1
  • _AddSecretBottomSheet.build (cyclomatic 26) apps/dashboard/lib/secret_manager/secret_manager_page.dart:980 — _AddSecretBottomSheet.build 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.
D1 · Cyclomatic Complexity · ExecutionGitHub.resolveCheckout · ×1
  • ExecutionGitHub.resolveCheckout::readCandidate (cyclomatic 26) firebase/functions/executor/github.ts:287 — ExecutionGitHub.resolveCheckout::readCandidate has cyclomatic complexity 26 (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. This shape REPEATS in the file: one other method here (ExecutionGitHub.resolveCheckout) 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.
D1 · Cyclomatic Complexity · GitHubWorkflows.fetch (cyclomatic 24) · ×1
  • GitHubWorkflows.fetch (cyclomatic 24) firebase/dart_functions/lib/src/github_workflows.dart:170 — GitHubWorkflows.fetch has cyclomatic complexity 24 (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.
D1 · Cyclomatic Complexity · webhook.receiveStripeWebhook (cyclomatic 24) · ×1
  • webhook.receiveStripeWebhook (cyclomatic 24) firebase/functions/billing/webhook.ts:23 — webhook.receiveStripeWebhook 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.
D1 · Cyclomatic Complexity · _EditSecretBottomSheet.build (cyclomatic 23) · ×1
  • _EditSecretBottomSheet.build (cyclomatic 23) apps/dashboard/lib/secret_manager/secret_manager_page.dart:1495 — _EditSecretBottomSheet.build has cyclomatic complexity 23 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · _VerificationActions.build (cyclomatic 23) · ×1
  • _VerificationActions.build (cyclomatic 23) apps/dashboard/lib/settings/email_verification_settings.dart:52 — _VerificationActions.build has cyclomatic complexity 23 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · card_setup.reconcileCardSession (cyclomatic 23) · ×1
  • card_setup.reconcileCardSession (cyclomatic 23) firebase/functions/billing/card_setup.ts:34 — card_setup.reconcileCardSession has cyclomatic complexity 23 (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.
D1 · Cyclomatic Complexity · OctokitConnectionClient.repositories (cyclomatic 23) · ×1
  • OctokitConnectionClient.repositories (cyclomatic 23) firebase/functions/github_connection/github.ts:174 — OctokitConnectionClient.repositories 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.
D1 · Cyclomatic Complexity · github_webhook.receiveGitHubWebhook (cyclomatic 23) · ×1
  • github_webhook.receiveGitHubWebhook (cyclomatic 23) firebase/functions/github_webhook.ts:11 — github_webhook.receiveGitHubWebhook has cyclomatic complexity 23 (threshold 15). Of this number, 18 points are the body's own statements and 5 belong to one function literal inside it that branches. 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.
D1 · Cyclomatic Complexity · BuildJobPlanner._processOnce (cyclomatic 22) · ×1
  • BuildJobPlanner._processOnce (cyclomatic 22) firebase/dart_functions/lib/src/create_build_jobs.dart:38 — BuildJobPlanner._processOnce has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · GitHubWorkflows.observePullRequest (cyclomatic 22) · ×1
  • GitHubWorkflows.observePullRequest (cyclomatic 22) firebase/dart_functions/lib/src/github_workflows.dart:76 — GitHubWorkflows.observePullRequest has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · InviteTeamMemberBottomSheet.build (cyclomatic 22) · ×1
  • InviteTeamMemberBottomSheet.build (cyclomatic 22) apps/dashboard/lib/team/invite_team_member_bottom_sheet.dart:19 — InviteTeamMemberBottomSheet.build has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · OrchardExecutor.exec (cyclomatic 22) · ×1
  • OrchardExecutor.exec (cyclomatic 22) firebase/functions/executor/orchard.ts:239 — OrchardExecutor.exec has cyclomatic complexity 22 (threshold 15). Most of this is not in the body itself: 3 of the 22 points are its own statements and the rest belongs to 6 function literals inside it that branch (lines 294, 246, 267, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D1 · Cyclomatic Complexity · ExecutionGitHub.skippedCheck (cyclomatic 22) · ×1
  • ExecutionGitHub.skippedCheck (cyclomatic 22) firebase/functions/executor/github.ts:137 — ExecutionGitHub.skippedCheck has cyclomatic complexity 22 (threshold 15). Of this number, 21 points are the body's own statements and 1 belongs to one function literal inside it that branches. 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.
D1 · Cyclomatic Complexity · build_dispatch_functions.queueBuildJobs (cyclomatic 22) · ×1
  • build_dispatch_functions.queueBuildJobs (cyclomatic 22) firebase/functions/build_dispatch_functions.ts:73 — build_dispatch_functions.queueBuildJobs has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This is NOT this file's highest cyclomatic complexity: build_dispatch_functions.queueRetriedBuildJob (cyclomatic 23) 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.
D1 · Cyclomatic Complexity · TeamManagement.execute (cyclomatic 22) · ×1
  • TeamManagement.execute (cyclomatic 22) firebase/functions/teams/service.ts:31 — TeamManagement.execute has cyclomatic complexity 22 (threshold 15). Of this number, 21 points are the body's own statements and 1 belongs to one function literal inside it that branches. 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.
D1 · Cyclomatic Complexity · GetBuildJobJob.toJson (cyclomatic 21) · ×1
  • GetBuildJobJob.toJson (cyclomatic 21) apps/dashboard/lib/generated/builds/get_build_job.dart:209 — GetBuildJobJob.toJson has cyclomatic complexity 21 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · GetBuildJobsBuildJobs.toJson (cyclomatic 21) · ×1
  • GetBuildJobsBuildJobs.toJson (cyclomatic 21) apps/dashboard/lib/generated/builds/get_build_jobs.dart:223 — GetBuildJobsBuildJobs.toJson has cyclomatic complexity 21 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · purchase.observePurchase (cyclomatic 21) · ×1
  • purchase.observePurchase (cyclomatic 21) firebase/functions/billing/purchase.ts:76 — purchase.observePurchase has cyclomatic complexity 21 (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. This is NOT this file's highest cyclomatic complexity: purchase.paidPeriod (cyclomatic 32) 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.
D1 · Cyclomatic Complexity · ExecutionGitHub.resolveCheckout (cyclomatic 21) · ×1
  • ExecutionGitHub.resolveCheckout (cyclomatic 21) firebase/functions/executor/github.ts:231 — ExecutionGitHub.resolveCheckout 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. This shape REPEATS in the file: one other method here (ExecutionGitHub.resolveCheckout::readCandidate) 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.
D1 · Cyclomatic Complexity · FirebaseAppDistributionClient.upload (cyclomatic 20) · ×1
  • FirebaseAppDistributionClient.upload (cyclomatic 20) packages/openci_workflow/lib/src/flutter/firebase_app_distribution/firebase_app_distribution_client.dart:33 — FirebaseAppDistributionClient.upload has cyclomatic complexity 20 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · PullRequestCI.postQrCode (cyclomatic 20) · ×1
  • PullRequestCI.postQrCode (cyclomatic 20) packages/openci_workflow/lib/src/pull_request_ci.dart:56 — PullRequestCI.postQrCode has cyclomatic complexity 20 (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.
D1 · Cyclomatic Complexity · Billing.execute (cyclomatic 20) · ×1
  • Billing.execute (cyclomatic 20) firebase/functions/billing/service.ts:34 — Billing.execute has cyclomatic complexity 20 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · pull_request_qr.readPullRequestQrCodes (cyclomatic 20) · ×1
  • pull_request_qr.readPullRequestQrCodes (cyclomatic 20) REDACTED:126 — pull_request_qr.readPullRequestQrCodes has cyclomatic complexity 20 (threshold 15). Of this number, 18 points are the body's own statements and 2 belong to one function literal inside it that branches. 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.
D1 · Cyclomatic Complexity · LocalDevelopmentConnection.parse (cyclomatic 19) · ×1
  • LocalDevelopmentConnection.parse (cyclomatic 19) apps/dashboard/lib/connections/local_development_connection.dart:63 — LocalDevelopmentConnection.parse has cyclomatic complexity 19 (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.
D1 · Cyclomatic Complexity · WorkflowContext.fromEnvironment (cyclomatic 19) · ×1
  • WorkflowContext.fromEnvironment (cyclomatic 19) packages/openci_workflow/lib/src/workflow_context.dart:13 — WorkflowContext.fromEnvironment has cyclomatic complexity 19 (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.
D1 · Cyclomatic Complexity · ExecutionStore.configure (cyclomatic 19) · ×1
  • ExecutionStore.configure (cyclomatic 19) firebase/functions/executor/store.ts:82 — ExecutionStore.configure has cyclomatic complexity 19 (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.
D1 · Cyclomatic Complexity · execute.cleanupExecution (cyclomatic 19) · ×1
  • execute.cleanupExecution (cyclomatic 19) firebase/functions/executor/execute.ts:48 — execute.cleanupExecution has cyclomatic complexity 19 (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.
D1 · Cyclomatic Complexity · DataConnectPlanningStore._execute (cyclomatic 18) · ×1
  • DataConnectPlanningStore._execute (cyclomatic 18) firebase/dart_functions/lib/src/data_connect.dart:74 — DataConnectPlanningStore._execute 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.
D1 · Cyclomatic Complexity · DeleteTeamBottomSheet.build (cyclomatic 18) · ×1
  • DeleteTeamBottomSheet.build (cyclomatic 18) apps/dashboard/lib/team/delete_team_bottom_sheet.dart:14 — DeleteTeamBottomSheet.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.
D1 · Cyclomatic Complexity · ExecutionBilling.close (cyclomatic 18) · ×1
  • ExecutionBilling.close (cyclomatic 18) firebase/functions/executor/billing.ts:181 — ExecutionBilling.close 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.
D1 · Cyclomatic Complexity · GitHubConnections.callback (cyclomatic 18) · ×1
  • GitHubConnections.callback (cyclomatic 18) firebase/functions/github_connection/service.ts:173 — GitHubConnections.callback 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.
D1 · Cyclomatic Complexity · BillingView.build (cyclomatic 17) · ×1
  • BillingView.build (cyclomatic 17) apps/dashboard/lib/billing/billing_view.dart:27 — BillingView.build 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.
D1 · Cyclomatic Complexity · SecretManager._call (cyclomatic 17) · ×1
  • SecretManager._call (cyclomatic 17) apps/dashboard/lib/secret_manager/secret_manager_provider.dart:49 — SecretManager._call has cyclomatic complexity 17 (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.
D1 · Cyclomatic Complexity · config.billingConfig (cyclomatic 17) · ×1
  • config.billingConfig (cyclomatic 17) firebase/functions/billing/config.ts:12 — config.billingConfig has cyclomatic complexity 17 (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.
D1 · Cyclomatic Complexity · Billing.status (cyclomatic 17) · ×1
  • Billing.status (cyclomatic 17) firebase/functions/billing/service.ts:88 — Billing.status 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.
D1 · Cyclomatic Complexity · pull_request_qr.validatedQrMetadata (cyclomatic 17) · ×1
  • pull_request_qr.validatedQrMetadata (cyclomatic 17) REDACTED:75 — pull_request_qr.validatedQrMetadata has cyclomatic complexity 17 (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.
D1 · Cyclomatic Complexity · CicdLogDetailPage.build (cyclomatic 16) · ×1
  • CicdLogDetailPage.build (cyclomatic 16) apps/dashboard/lib/cicd_log/detail/ci_cd_log_detail_page.dart:62 — CicdLogDetailPage.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.
D1 · Cyclomatic Complexity · EditTeamBottomSheet.build (cyclomatic 16) · ×1
  • EditTeamBottomSheet.build (cyclomatic 16) apps/dashboard/lib/team/edit_team_bottom_sheet.dart:12 — EditTeamBottomSheet.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.
D1 · Cyclomatic Complexity · card_setup.cardSetupStatus (cyclomatic 16) · ×1
  • card_setup.cardSetupStatus (cyclomatic 16) firebase/functions/billing/card_setup.ts:165 — card_setup.cardSetupStatus 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.
D1 · Cyclomatic Complexity · Billing.reconcile (cyclomatic 16) · ×1
  • Billing.reconcile (cyclomatic 16) firebase/functions/billing/service.ts:198 — Billing.reconcile 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.
D2 · Cognitive Complexity · FirebaseFormSheet.build (cognitive 79) · ×1
  • FirebaseFormSheet.build (cognitive 79) apps/dashboard/lib/auth/auth_page.dart:522 — FirebaseFormSheet.build has cognitive complexity 79 (threshold 15). Drivers by points: if/else 25 (38 pts), boolean chains 23, ternaries 7 (12 pts), error handling 3 (4 pts), loops 1 (2 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.
D2 · Cognitive Complexity · execute.executeBuild (cognitive 66) · ×1
  • execute.executeBuild (cognitive 66) firebase/functions/executor/execute.ts:86 — execute.executeBuild has cognitive complexity 66 (threshold 15). Drivers by points: if/else 30 (39 pts), ternaries 5 (11 pts), boolean chains 9, error handling 4 (6 pts), loops 1 (nesting depth added 17). Of this number, 28 points are the body's own statements and 38 belong to 6 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · OctokitConnectionClient.candidates (cognitive 58) · ×1
  • OctokitConnectionClient.candidates (cognitive 58) firebase/functions/github_connection/github.ts:102 — OctokitConnectionClient.candidates has cognitive complexity 58 (threshold 15). Drivers by points: if/else 14 (41 pts), boolean chains 7, loops 3 (6 pts), error handling 2 (4 pts) (nesting depth added 32). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · FirebaseHostingClient.deploy (cognitive 55) · ×1
  • FirebaseHostingClient.deploy (cognitive 55) packages/openci_workflow/lib/src/firebase_hosting/firebase_hosting_client.dart:49 — FirebaseHostingClient.deploy has cognitive complexity 55 (threshold 15). Drivers by points: if/else 9 (22 pts), loops 5 (14 pts), boolean chains 8, ternaries 4 (7 pts), error handling 2 (4 pts) (nesting depth added 27). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · pull_request_qr.publishPullRequestQrCodes (cognitive 54) · ×1
  • pull_request_qr.publishPullRequestQrCodes (cognitive 54) REDACTED:289 — pull_request_qr.publishPullRequestQrCodes has cognitive complexity 54 (threshold 15). Drivers by points: if/else 17 (36 pts), boolean chains 8, loops 5 (7 pts), error handling 2 (3 pts) (nesting depth added 22). Of this number, 20 points are the body's own statements and 34 belong to 4 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · SetupAscKeysCommand.run (cognitive 53) · ×1
  • SetupAscKeysCommand.run (cognitive 53) apps/openci_cli/lib/src/commands/setup/setup_asc_keys_command.dart:96 — SetupAscKeysCommand.run has cognitive complexity 53 (threshold 15). Drivers by points: if/else 15 (26 pts), error handling 10 (11 pts), match/switch 5 (11 pts), ternaries 1 (3 pts), boolean chains 2 (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.
D2 · Cognitive Complexity · SelfHostedSetupForm.build (cognitive 52) · ×1
  • SelfHostedSetupForm.build (cognitive 52) apps/dashboard/lib/auth/self_hosted_setup_form.dart:31 — SelfHostedSetupForm.build has cognitive complexity 52 (threshold 15). Drivers by points: if/else 16 (27 pts), ternaries 7 (13 pts), boolean chains 11, 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.
D2 · Cognitive Complexity · OpenCICompletionCommand.run (cognitive 52) · ×1
  • OpenCICompletionCommand.run (cognitive 52) apps/openci_cli/lib/src/completion/openci_completion_command.dart:14 — OpenCICompletionCommand.run has cognitive complexity 52 (threshold 15). Drivers by points: if/else 11 (26 pts), loops 5 (12 pts), boolean chains 9, ternaries 2 (4 pts), error handling 1 (nesting depth added 24). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · PlanningEvent.parse (cognitive 52) · ×1
  • PlanningEvent.parse (cognitive 52) firebase/dart_functions/lib/src/planning_event.dart:30 — PlanningEvent.parse has cognitive complexity 52 (threshold 15). Drivers by points: if/else 12 (30 pts), boolean chains 11, ternaries 3 (7 pts), error handling 2, loops 1 (2 pts) (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.
D2 · Cognitive Complexity · BuildJobPlanner._processOnce (cognitive 51) · ×1
  • BuildJobPlanner._processOnce (cognitive 51) firebase/dart_functions/lib/src/create_build_jobs.dart:38 — BuildJobPlanner._processOnce has cognitive complexity 51 (threshold 15). Drivers by points: if/else 13 (37 pts), ternaries 2 (8 pts), boolean chains 3, error handling 3 (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.
D2 · Cognitive Complexity · FirebaseHostingConfig.load (cognitive 51) · ×1
  • FirebaseHostingConfig.load (cognitive 51) packages/openci_workflow/lib/src/firebase_hosting/firebase_hosting_config.dart:16 — FirebaseHostingConfig.load has cognitive complexity 51 (threshold 15). Drivers by points: if/else 18 (29 pts), boolean chains 7, ternaries 5 (7 pts), loops 4 (6 pts), error handling 2 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · AuthPage.build (cognitive 45) · ×1
  • AuthPage.build (cognitive 45) apps/dashboard/lib/auth/auth_page.dart:32 — AuthPage.build has cognitive complexity 45 (threshold 15). Drivers by points: if/else 16 (26 pts), boolean chains 10, ternaries 5 (6 pts), error handling 2 (3 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.
D2 · Cognitive Complexity · TeamSecrets.execute (cognitive 45) · ×1
  • TeamSecrets.execute (cognitive 45) firebase/functions/secrets/service.ts:49 — TeamSecrets.execute has cognitive complexity 45 (threshold 15). Drivers by points: if/else 21 (30 pts), boolean chains 12, ternaries 2, 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.
D2 · Cognitive Complexity · _AddSecretBottomSheet.build (cognitive 40) · ×1
  • _AddSecretBottomSheet.build (cognitive 40) apps/dashboard/lib/secret_manager/secret_manager_page.dart:980 — _AddSecretBottomSheet.build has cognitive complexity 40 (threshold 15). Drivers by points: if/else 14 (22 pts), ternaries 7 (12 pts), boolean chains 5, 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.
D2 · Cognitive Complexity · BillingView.build (cognitive 37) · ×1
  • BillingView.build (cognitive 37) apps/dashboard/lib/billing/billing_view.dart:27 — BillingView.build has cognitive complexity 37 (threshold 15). Drivers by points: if/else 12 (18 pts), ternaries 6 (18 pts), boolean chains 1 (nesting depth added 18). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · _EditSecretBottomSheet.build (cognitive 36) · ×1
  • _EditSecretBottomSheet.build (cognitive 36) apps/dashboard/lib/secret_manager/secret_manager_page.dart:1495 — _EditSecretBottomSheet.build has cognitive complexity 36 (threshold 15). Drivers by points: if/else 14 (21 pts), ternaries 7 (12 pts), boolean chains 2, error handling 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · _VerificationActions.build (cognitive 36) · ×1
  • _VerificationActions.build (cognitive 36) apps/dashboard/lib/settings/email_verification_settings.dart:52 — _VerificationActions.build has cognitive complexity 36 (threshold 15). Drivers by points: if/else 12 (21 pts), ternaries 3 (7 pts), boolean chains 3, match/switch 1 (3 pts), error handling 2 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · DeleteTeamBottomSheet.build (cognitive 35) · ×1
  • DeleteTeamBottomSheet.build (cognitive 35) apps/dashboard/lib/team/delete_team_bottom_sheet.dart:14 — DeleteTeamBottomSheet.build has cognitive complexity 35 (threshold 15). Drivers by points: if/else 7 (16 pts), ternaries 8 (16 pts), error handling 1 (2 pts), loops 1 (nesting depth added 18). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · orchard_capacity.hasOrchardCapacity (cognitive 35) · ×1
  • orchard_capacity.hasOrchardCapacity (cognitive 35) firebase/functions/orchard_capacity.ts:39 — orchard_capacity.hasOrchardCapacity has cognitive complexity 35 (threshold 15). Drivers by points: if/else 12 (21 pts), boolean chains 11, loops 3 (nesting depth added 9). Of this number, 31 points are the body's own statements and 4 belong to 4 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · build_dispatch_functions.dispatchBuildJob (cognitive 34) · ×1
  • build_dispatch_functions.dispatchBuildJob (cognitive 34) firebase/functions/build_dispatch_functions.ts:270 — build_dispatch_functions.dispatchBuildJob has cognitive complexity 34 (threshold 15). Drivers by points: if/else 13 (19 pts), boolean chains 8, error handling 4 (6 pts), ternaries 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.
D2 · Cognitive Complexity · build_dispatch_functions.queueBuildJobs (cognitive 33) · ×1
  • build_dispatch_functions.queueBuildJobs (cognitive 33) firebase/functions/build_dispatch_functions.ts:73 — build_dispatch_functions.queueBuildJobs has cognitive complexity 33 (threshold 15). Drivers by points: if/else 8 (18 pts), loops 3 (8 pts), boolean chains 4, error handling 2 (3 pts) (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · _FilePicker.handle (cognitive 32) · ×1
  • _FilePicker.handle (cognitive 32) apps/openci_cli/lib/src/commands/register/select_secret_file.dart:51 — _FilePicker.handle has cognitive complexity 32 (threshold 15). Drivers by points: if/else 9 (17 pts), ternaries 4 (12 pts), error handling 1 (2 pts), match/switch 1 (nesting depth added 17). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
D2 · Cognitive Complexity · TeamManagement.execute (cognitive 31) · ×1
  • TeamManagement.execute (cognitive 31) firebase/functions/teams/service.ts:31 — TeamManagement.execute has cognitive complexity 31 (threshold 15). Drivers by points: if/else 10 (15 pts), ternaries 3 (9 pts), boolean chains 4, loops 2 (3 pts) (nesting depth added 12). Of this number, 29 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · BillingActions._create (cognitive 30) · ×1
  • BillingActions._create (cognitive 30) apps/dashboard/lib/billing/billing_actions.dart:29 — BillingActions._create has cognitive complexity 30 (threshold 15). Drivers by points: boolean chains 13, ternaries 4 (8 pts), if/else 4 (6 pts), error handling 2, match/switch 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.
D2 · Cognitive Complexity · GetBuildJobJob.== (cognitive 30) · ×1
  • GetBuildJobJob.== (cognitive 30) apps/dashboard/lib/generated/builds/get_build_job.dart:135 — GetBuildJobJob.== has cognitive complexity 30 (threshold 15). Drivers by points: boolean chains 28, if/else 2. 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.
D2 · Cognitive Complexity · GetBuildJobsBuildJobs.== (cognitive 30) · ×1
  • GetBuildJobsBuildJobs.== (cognitive 30) apps/dashboard/lib/generated/builds/get_build_jobs.dart:149 — GetBuildJobsBuildJobs.== has cognitive complexity 30 (threshold 15). Drivers by points: boolean chains 28, if/else 2. 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.
D2 · Cognitive Complexity · InviteTeamMemberBottomSheet.build (cognitive 30) · ×1
  • InviteTeamMemberBottomSheet.build (cognitive 30) apps/dashboard/lib/team/invite_team_member_bottom_sheet.dart:19 — InviteTeamMemberBottomSheet.build has cognitive complexity 30 (threshold 15). Drivers by points: ternaries 11 (16 pts), if/else 6 (10 pts), boolean chains 2, error handling 1, loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · pull_request_qr.readPullRequestQrCodes (cognitive 30) · ×1
  • pull_request_qr.readPullRequestQrCodes (cognitive 30) REDACTED:126 — pull_request_qr.readPullRequestQrCodes has cognitive complexity 30 (threshold 15). Drivers by points: if/else 12 (19 pts), ternaries 2 (5 pts), loops 3 (4 pts), boolean chains 2 (nesting depth added 11). Of this number, 28 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ExecutionBilling.close (cognitive 30) · ×1
  • ExecutionBilling.close (cognitive 30) firebase/functions/executor/billing.ts:181 — ExecutionBilling.close has cognitive complexity 30 (threshold 15). Drivers by points: if/else 6 (13 pts), ternaries 2 (7 pts), error handling 2 (5 pts), boolean chains 4, loops 1 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · GitHubWorkflows.observePullRequest (cognitive 29) · ×1
  • GitHubWorkflows.observePullRequest (cognitive 29) firebase/dart_functions/lib/src/github_workflows.dart:76 — GitHubWorkflows.observePullRequest has cognitive complexity 29 (threshold 15). Drivers by points: if/else 9 (16 pts), boolean chains 11, ternaries 1 (2 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · GitHubWorkflows.fetch (cognitive 28) · ×1
  • GitHubWorkflows.fetch (cognitive 28) firebase/dart_functions/lib/src/github_workflows.dart:170 — GitHubWorkflows.fetch has cognitive complexity 28 (threshold 15). Drivers by points: boolean chains 13, if/else 8 (12 pts), error handling 1 (2 pts), loops 1 (nesting depth added 5). 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.
D2 · Cognitive Complexity · Billing.deleteTeam (cognitive 27) · ×1
  • Billing.deleteTeam (cognitive 27) firebase/functions/billing/service.ts:258 — Billing.deleteTeam has cognitive complexity 27 (threshold 15). Drivers by points: if/else 9 (21 pts), error handling 2 (5 pts), boolean chains 1 (nesting depth added 15). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
D2 · Cognitive Complexity · Billing.reconcile (cognitive 26) · ×1
  • Billing.reconcile (cognitive 26) firebase/functions/billing/service.ts:198 — Billing.reconcile has cognitive complexity 26 (threshold 15). Drivers by points: if/else 7 (15 pts), error handling 3 (7 pts), boolean chains 3, loops 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · CicdLogDetailPage.build (cognitive 24) · ×1
  • CicdLogDetailPage.build (cognitive 24) apps/dashboard/lib/cicd_log/detail/ci_cd_log_detail_page.dart:62 — CicdLogDetailPage.build has cognitive complexity 24 (threshold 15). Drivers by points: if/else 9 (16 pts), ternaries 3 (5 pts), boolean chains 2, 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.
D2 · Cognitive Complexity · EditTeamBottomSheet.build (cognitive 24) · ×1
  • EditTeamBottomSheet.build (cognitive 24) apps/dashboard/lib/team/edit_team_bottom_sheet.dart:12 — EditTeamBottomSheet.build has cognitive complexity 24 (threshold 15). Drivers by points: if/else 6 (12 pts), ternaries 7 (9 pts), error handling 1 (2 pts), boolean chains 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · OctokitConnectionClient.repositories (cognitive 24) · ×1
  • OctokitConnectionClient.repositories (cognitive 24) firebase/functions/github_connection/github.ts:174 — OctokitConnectionClient.repositories has cognitive complexity 24 (threshold 15). Drivers by points: if/else 6 (15 pts), boolean chains 6, loops 2 (3 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · build_dispatch.dispatchBuildJob (cognitive 24) · ×1
  • build_dispatch.dispatchBuildJob (cognitive 24) firebase/functions/build_dispatch.ts:139 — build_dispatch.dispatchBuildJob has cognitive complexity 24 (threshold 15). Drivers by points: if/else 10 (20 pts), error handling 1 (3 pts), boolean chains 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ExecutionGitHub.resolveCheckout (cognitive 24) · ×1
  • ExecutionGitHub.resolveCheckout (cognitive 24) firebase/functions/executor/github.ts:231 — ExecutionGitHub.resolveCheckout has cognitive complexity 24 (threshold 15). Drivers by points: if/else 22 (33 pts), boolean chains 11, error handling 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. This shape REPEATS in the file: one other method here (ExecutionGitHub.resolveCheckout::readCandidate) 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.
D2 · Cognitive Complexity · HostingFiles.prepare (cognitive 23) · ×1
  • HostingFiles.prepare (cognitive 23) packages/openci_workflow/lib/src/firebase_hosting/hosting_files.dart:22 — HostingFiles.prepare has cognitive complexity 23 (threshold 15). Drivers by points: if/else 7 (15 pts), boolean chains 4, error handling 2, loops 1 (2 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · WorkflowContext.fromEnvironment (cognitive 23) · ×1
  • WorkflowContext.fromEnvironment (cognitive 23) packages/openci_workflow/lib/src/workflow_context.dart:13 — WorkflowContext.fromEnvironment has cognitive complexity 23 (threshold 15). Drivers by points: if/else 5 (10 pts), boolean chains 7, error handling 2, loops 1 (2 pts), match/switch 1 (2 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · QueuedChecks.sync (cognitive 23) · ×1
  • QueuedChecks.sync (cognitive 23) firebase/functions/queued_checks.ts:79 — QueuedChecks.sync has cognitive complexity 23 (threshold 15). Drivers by points: if/else 10 (13 pts), boolean chains 8, error handling 1, ternaries 1 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
D2 · Cognitive Complexity · ExecutionBilling.admit (cognitive 23) · ×1
  • ExecutionBilling.admit (cognitive 23) firebase/functions/executor/billing.ts:68 — ExecutionBilling.admit has cognitive complexity 23 (threshold 15). Drivers by points: if/else 6 (15 pts), error handling 2 (5 pts), boolean chains 2, loops 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · FirebaseAppDistributionClient.upload (cognitive 22) · ×1
  • FirebaseAppDistributionClient.upload (cognitive 22) packages/openci_workflow/lib/src/flutter/firebase_app_distribution/firebase_app_distribution_client.dart:33 — FirebaseAppDistributionClient.upload has cognitive complexity 22 (threshold 15). Drivers by points: if/else 8 (10 pts), boolean chains 6, ternaries 4 (5 pts), loops 1 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
D2 · Cognitive Complexity · GitHubConnections.execute (cognitive 22) · ×1
  • GitHubConnections.execute (cognitive 22) firebase/functions/github_connection/service.ts:66 — GitHubConnections.execute has cognitive complexity 22 (threshold 15). Drivers by points: if/else 11 (12 pts), boolean chains 8, ternaries 1 (2 pts) (nesting depth added 2). Of this number, 21 points are the body's own statements and 1 belongs to one function literal inside it that branches. 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.
D2 · Cognitive Complexity · github_webhook.receiveGitHubWebhook (cognitive 22) · ×1
  • github_webhook.receiveGitHubWebhook (cognitive 22) firebase/functions/github_webhook.ts:11 — github_webhook.receiveGitHubWebhook has cognitive complexity 22 (threshold 15). Drivers by points: if/else 9 (11 pts), boolean chains 4, ternaries 2 (4 pts), error handling 3 (nesting depth added 4). Of this number, 17 points are the body's own statements and 5 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · _OpenCIInitVisitor._extractFromInitArgs (cognitive 21) · ×1
  • _OpenCIInitVisitor._extractFromInitArgs (cognitive 21) firebase/dart_functions/lib/src/open_ci_parser.dart:122 — _OpenCIInitVisitor._extractFromInitArgs has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (17 pts), boolean chains 3, loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · SwitchTeamBottomSheet.build (cognitive 21) · ×1
  • SwitchTeamBottomSheet.build (cognitive 21) apps/dashboard/lib/team/switch_team_bottom_sheet.dart:35 — SwitchTeamBottomSheet.build has cognitive complexity 21 (threshold 15). Drivers by points: if/else 7 (14 pts), error handling 2 (3 pts), ternaries 2 (3 pts), loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ExecutionGitHub.skippedCheck (cognitive 21) · ×1
  • ExecutionGitHub.skippedCheck (cognitive 21) firebase/functions/executor/github.ts:137 — ExecutionGitHub.skippedCheck has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (14 pts), boolean chains 4, loops 1 (2 pts), ternaries 1 (nesting depth added 7). Of this number, 20 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · LocalDevelopmentConnection.parse (cognitive 20) · ×1
  • LocalDevelopmentConnection.parse (cognitive 20) apps/dashboard/lib/connections/local_development_connection.dart:63 — LocalDevelopmentConnection.parse has cognitive complexity 20 (threshold 15). Drivers by points: boolean chains 12, if/else 6 (8 pts) (nesting depth added 2). 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.
D2 · Cognitive Complexity · GetBuildJobJob.toJson (cognitive 20) · ×1
  • GetBuildJobJob.toJson (cognitive 20) apps/dashboard/lib/generated/builds/get_build_job.dart:209 — GetBuildJobJob.toJson has cognitive complexity 20 (threshold 15). Drivers by points: if/else 20. 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.
D2 · Cognitive Complexity · GetBuildJobsBuildJobs.toJson (cognitive 20) · ×1
  • GetBuildJobsBuildJobs.toJson (cognitive 20) apps/dashboard/lib/generated/builds/get_build_jobs.dart:223 — GetBuildJobsBuildJobs.toJson has cognitive complexity 20 (threshold 15). Drivers by points: if/else 20. 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.
D2 · Cognitive Complexity · FirebaseAuthClient._send (cognitive 20) · ×1
  • FirebaseAuthClient._send (cognitive 20) REDACTED:85 — FirebaseAuthClient._send has cognitive complexity 20 (threshold 15). Drivers by points: ternaries 4 (8 pts), if/else 3 (6 pts), boolean chains 5, error handling 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ListTeamsCommand.run (cognitive 20) · ×1
  • ListTeamsCommand.run (cognitive 20) apps/openci_cli/lib/src/commands/list/list_teams_command.dart:27 — ListTeamsCommand.run has cognitive complexity 20 (threshold 15). Drivers by points: ternaries 3 (8 pts), if/else 4 (5 pts), loops 1 (3 pts), boolean chains 2, error handling 2 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · OpenCICompletionCommand._loginValues (cognitive 20) · ×1
  • OpenCICompletionCommand._loginValues (cognitive 20) apps/openci_cli/lib/src/completion/openci_completion_command.dart:124 — OpenCICompletionCommand._loginValues has cognitive complexity 20 (threshold 15). Drivers by points: if/else 6 (16 pts), loops 1 (2 pts), boolean chains 1, error handling 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · webhook.receiveStripeWebhook (cognitive 20) · ×1
  • webhook.receiveStripeWebhook (cognitive 20) firebase/functions/billing/webhook.ts:23 — webhook.receiveStripeWebhook has cognitive complexity 20 (threshold 15). Drivers by points: if/else 12 (14 pts), boolean chains 4, error handling 1, ternaries 1 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
D2 · Cognitive Complexity · OrchardExecutor.checkWorkerMemory (cognitive 20) · ×1
  • OrchardExecutor.checkWorkerMemory (cognitive 20) firebase/functions/executor/orchard.ts:146 — OrchardExecutor.checkWorkerMemory has cognitive complexity 20 (threshold 15). Drivers by points: if/else 6 (10 pts), boolean chains 6, loops 2, ternaries 1 (2 pts) (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · _TeamBillingPageState._openStripe (cognitive 19) · ×1
  • _TeamBillingPageState._openStripe (cognitive 19) apps/dashboard/lib/billing/billing_page.dart:183 — _TeamBillingPageState._openStripe has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (12 pts), boolean chains 6, error handling 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · StatusCommand.run (cognitive 19) · ×1
  • StatusCommand.run (cognitive 19) apps/openci_cli/lib/src/commands/status_command.dart:27 — StatusCommand.run has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (7 pts), ternaries 3 (7 pts), error handling 3, boolean chains 2 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · _OpenCIInitVisitor._extractTrigger (cognitive 19) · ×1
  • _OpenCIInitVisitor._extractTrigger (cognitive 19) firebase/dart_functions/lib/src/open_ci_parser.dart:184 — _OpenCIInitVisitor._extractTrigger has cognitive complexity 19 (threshold 15). Drivers by points: if/else 11 (15 pts), boolean chains 3, loops 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.
D2 · Cognitive Complexity · FirebaseHostingCI._deploy (cognitive 19) · ×1
  • FirebaseHostingCI._deploy (cognitive 19) packages/openci_workflow/lib/src/firebase_hosting/firebase_hosting_ci.dart:107 — FirebaseHostingCI._deploy has cognitive complexity 19 (threshold 15). Drivers by points: if/else 5 (7 pts), ternaries 4 (6 pts), boolean chains 3, error handling 2 (3 pts) (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · FirebaseHostingClient._preview (cognitive 19) · ×1
  • FirebaseHostingClient._preview (cognitive 19) packages/openci_workflow/lib/src/firebase_hosting/firebase_hosting_client.dart:167 — FirebaseHostingClient._preview has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (11 pts), boolean chains 4, error handling 1 (2 pts), loops 2 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · PullRequestCI.postQrCode (cognitive 19) · ×1
  • PullRequestCI.postQrCode (cognitive 19) packages/openci_workflow/lib/src/pull_request_ci.dart:56 — PullRequestCI.postQrCode has cognitive complexity 19 (threshold 15). Drivers by points: boolean chains 13, if/else 6. 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.
D2 · Cognitive Complexity · billing_functions.cleanDeletedTeamCredentials (cognitive 19) · ×1
  • billing_functions.cleanDeletedTeamCredentials (cognitive 19) REDACTED:127 — billing_functions.cleanDeletedTeamCredentials has cognitive complexity 19 (threshold 15). Drivers by points: if/else 4 (11 pts), loops 3 (5 pts), error handling 1 (2 pts), boolean chains 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · OrchardExecutor.exec (cognitive 19) · ×1
  • OrchardExecutor.exec (cognitive 19) firebase/functions/executor/orchard.ts:239 — OrchardExecutor.exec has cognitive complexity 19 (threshold 15). Drivers by points: if/else 10 (11 pts), boolean chains 6, error handling 1, loops 1 (nesting depth added 1). Most of this is not in the body itself: 1 of the 19 points is its own statement and the rest belongs to 6 function literals inside it that branch (lines 294, 267, 246, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · pull_request_qr.saveImages (cognitive 19) · ×1
  • pull_request_qr.saveImages (cognitive 19) REDACTED:226 — pull_request_qr.saveImages has cognitive complexity 19 (threshold 15). Drivers by points: if/else 5 (10 pts), ternaries 2 (4 pts), boolean chains 2, error handling 1 (2 pts), loops 1 (nesting depth added 8). Of this number, 17 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · FilePathCompleter.complete (cognitive 18) · ×1
  • FilePathCompleter.complete (cognitive 18) apps/openci_cli/lib/src/commands/register/file_path_completer.dart:24 — FilePathCompleter.complete has cognitive complexity 18 (threshold 15). Drivers by points: if/else 4 (6 pts), ternaries 4 (6 pts), boolean chains 5, loops 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.
D2 · Cognitive Complexity · ExecutionGitHub.resolveCheckout · ×1
  • ExecutionGitHub.resolveCheckout::readCandidate (cognitive 18) firebase/functions/executor/github.ts:287 — ExecutionGitHub.resolveCheckout::readCandidate has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (12 pts), boolean chains 6 (nesting depth added 3). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (ExecutionGitHub.resolveCheckout) 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.
D2 · Cognitive Complexity · _FilePicker.render (cognitive 17) · ×1
  • _FilePicker.render (cognitive 17) apps/openci_cli/lib/src/commands/register/select_secret_file.dart:140 — _FilePicker.render has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (7 pts), loops 3 (5 pts), ternaries 2 (5 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.
D2 · Cognitive Complexity · AscKeyRegistration.save (cognitive 17) · ×1
  • AscKeyRegistration.save (cognitive 17) apps/openci_cli/lib/src/commands/setup/asc_key_registration.dart:97 — AscKeyRegistration.save has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (9 pts), boolean chains 4, error handling 2, loops 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.
D2 · Cognitive Complexity · DataConnectPlanningStore._execute (cognitive 17) · ×1
  • DataConnectPlanningStore._execute (cognitive 17) firebase/dart_functions/lib/src/data_connect.dart:74 — DataConnectPlanningStore._execute has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 12, if/else 4, ternaries 1. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · FirebaseHostingClient._channels (cognitive 17) · ×1
  • FirebaseHostingClient._channels (cognitive 17) packages/openci_workflow/lib/src/firebase_hosting/firebase_hosting_client.dart:243 — FirebaseHostingClient._channels has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (9 pts), boolean chains 5, loops 2 (3 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ShorebirdCI.releaseApk (cognitive 17) · ×1
  • ShorebirdCI.releaseApk (cognitive 17) packages/openci_workflow/lib/src/shorebird/shorebird_ci.dart:18 — ShorebirdCI.releaseApk has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (11 pts), loops 2 (3 pts), ternaries 1 (2 pts), boolean chains 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (ShorebirdCI.releaseAab) 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.
D2 · Cognitive Complexity · ShorebirdCI.releaseAab (cognitive 17) · ×1
  • ShorebirdCI.releaseAab (cognitive 17) packages/openci_workflow/lib/src/shorebird/shorebird_ci.dart:120 — ShorebirdCI.releaseAab has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (11 pts), loops 2 (3 pts), ternaries 1 (2 pts), boolean chains 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (ShorebirdCI.releaseApk) 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.
D2 · Cognitive Complexity · card_setup.startCardSetup (cognitive 17) · ×1
  • card_setup.startCardSetup (cognitive 17) firebase/functions/billing/card_setup.ts:109 — card_setup.startCardSetup has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (12 pts), boolean chains 2, error handling 1 (2 pts), loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Billing.execute (cognitive 17) · ×1
  • Billing.execute (cognitive 17) firebase/functions/billing/service.ts:34 — Billing.execute has cognitive complexity 17 (threshold 15). Drivers by points: if/else 11 (13 pts), boolean chains 4 (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.
D2 · Cognitive Complexity · SecretManager._call (cognitive 16) · ×1
  • SecretManager._call (cognitive 16) apps/dashboard/lib/secret_manager/secret_manager_provider.dart:49 — SecretManager._call has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 12, if/else 4. 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.
D2 · Cognitive Complexity · AscKeyRegistration.prepare (cognitive 16) · ×1
  • AscKeyRegistration.prepare (cognitive 16) apps/openci_cli/lib/src/commands/setup/asc_key_registration.dart:38 — AscKeyRegistration.prepare has cognitive complexity 16 (threshold 15). Drivers by points: if/else 3 (6 pts), ternaries 2 (4 pts), error handling 3, loops 1 (2 pts), boolean chains 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · _OpenCIInitVisitor._extractPaths (cognitive 16) · ×1
  • _OpenCIInitVisitor._extractPaths (cognitive 16) firebase/dart_functions/lib/src/open_ci_parser.dart:231 — _OpenCIInitVisitor._extractPaths has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (8 pts), boolean chains 5, error handling 1 (2 pts), loops 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.
D2 · Cognitive Complexity · build-job-card-demo.BuildJobCardDemo (cognitive 16) · ×1
  • build-job-card-demo.BuildJobCardDemo (cognitive 16) apps/landing_page/components/build-job-card-demo.tsx:95 — build-job-card-demo.BuildJobCardDemo has cognitive complexity 16 (threshold 15). Drivers by points: if/else 41 (53 pts), ternaries 8 (16 pts), boolean chains 2 (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. This shape REPEATS in the file: 2 other methods here (build-job-card-demo.BuildJobCardDemo::getJobStatus, build-job-card-demo.BuildJobCardDemo::getJobDuration) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D2 · Cognitive Complexity · execute.recoverExecutions (cognitive 16) · ×1
  • execute.recoverExecutions (cognitive 16) firebase/functions/executor/execute.ts:335 — execute.recoverExecutions has cognitive complexity 16 (threshold 15). Drivers by points: error handling 3 (6 pts), if/else 2 (5 pts), loops 3 (4 pts), boolean chains 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · GitHubConnections.callback (cognitive 16) · ×1
  • GitHubConnections.callback (cognitive 16) firebase/functions/github_connection/service.ts:173 — GitHubConnections.callback has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 5, if/else 3 (4 pts), ternaries 2 (4 pts), error handling 3 (nesting depth added 3). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D3 · God Classes · ClassTooLong · ×1
  • ClassTooLong: ExecutionGitHub firebase/functions/executor/github.ts:52 — ClassTooLong — 414 significant lines (blank, comment-only and punctuation-only lines excluded), 9 methods. The bar is 400 significant lines; this is 14 over it, 1.04× 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 · Near-duplicate member pair (216 shared lines) · ×1
  • Near-duplicate member pair (216 shared lines) apps/dashboard/lib/secret_manager/secret_manager_page.dart:980 — apps/dashboard/lib/secret_manager/secret_manager_page.dart:980-1311 | apps/dashboard/lib/secret_manager/secret_manager_page.dart:1495-1855 — These two members are variants of one another: 216 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 · Near-duplicate member pair (59 shared lines) · ×1
  • Near-duplicate member pair (59 shared lines) apps/dashboard/lib/team/delete_team_bottom_sheet.dart:14 — apps/dashboard/lib/team/delete_team_bottom_sheet.dart:14-245 | apps/dashboard/lib/team/edit_team_bottom_sheet.dart:12-247 — These two members are variants of one another: 59 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.
D4 · Code Duplication · Edited copy of a member (99 corresponding lines) · ×1
  • Edited copy of a member (99 corresponding lines) packages/openci_workflow/lib/src/shorebird/shorebird_ci.dart:18 — packages/openci_workflow/lib/src/shorebird/shorebird_ci.dart:18-118 | packages/openci_workflow/lib/src/shorebird/shorebird_ci.dart:120-218 — These two members are one piece of code written twice and then edited apart: 99 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (49 corresponding lines) · ×1
  • Edited copy of a member (49 corresponding lines) apps/dashboard/lib/settings/settings_page.dart:265 — apps/dashboard/lib/settings/settings_page.dart:265-324 | apps/dashboard/lib/settings/settings_page.dart:338-386 — These two members are one piece of code written twice and then edited apart: 49 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (22 corresponding lines) · ×1
  • Edited copy of a member (22 corresponding lines) apps/dashboard/lib/billing/billing_view.dart:133 — apps/dashboard/lib/billing/billing_view.dart:133-154 | apps/dashboard/lib/settings/settings_page.dart:656-686 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (30 corresponding lines) · ×1
  • Edited copy of a member (30 corresponding lines) apps/dashboard/lib/secret_manager/secret_manager_page.dart:213 — apps/dashboard/lib/secret_manager/secret_manager_page.dart:213-250 | apps/dashboard/lib/secret_manager/secret_manager_page.dart:559-588 — These two members are one piece of code written twice and then edited apart: 30 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (5 members, 18+ corresponding lines) · ×1
  • Edited copies of one member (5 members, 18+ corresponding lines) apps/openci_cli/lib/src/commands/delete/delete_secret_command.dart:77 — apps/openci_cli/lib/src/commands/delete/delete_secret_command.dart:77-97 | apps/openci_cli/lib/src/commands/list/list_secrets_command.dart:68-88 | apps/openci_cli/lib/src/commands/list/list_teams_command.dart:72-92 | apps/openci_cli/lib/src/commands/register/secret_registration.dart:19-40 | apps/openci_cli/lib/src/commands/sync/sync_secrets.dart:54-71 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 18 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (13 corresponding lines) · ×1
  • Edited copy of a member (13 corresponding lines) apps/dashboard/lib/generated/secrets/commit_managed_secret.dart:174 — apps/dashboard/lib/generated/secrets/commit_managed_secret.dart:174-186 | apps/dashboard/lib/generated/secrets/rename_managed_secret.dart:226-239 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (19 corresponding lines) · ×1
  • Edited copy of a member (19 corresponding lines) apps/dashboard/lib/generated/logs/get_build_log_state.dart:121 — apps/dashboard/lib/generated/logs/get_build_log_state.dart:121-139 | apps/dashboard/lib/generated/logs/get_build_step_write_state.dart:97-115 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 20+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 20+ corresponding lines) apps/dashboard/lib/generated/logs/append_build_log.dart:171 — apps/dashboard/lib/generated/logs/append_build_log.dart:171-191 | apps/dashboard/lib/generated/logs/get_build_log_write_state.dart:119-138 | apps/dashboard/lib/generated/logs/get_build_logs.dart:133-152 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 20 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 10+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 10+ corresponding lines) apps/dashboard/lib/generated/logs/get_build_log_state.dart:83 — apps/dashboard/lib/generated/logs/get_build_log_state.dart:83-93 | apps/dashboard/lib/generated/logs/get_build_log_write_state.dart:79-88 | apps/dashboard/lib/generated/logs/get_build_logs.dart:93-102 | apps/dashboard/lib/generated/teams/get_my_teams.dart:70-79 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 10 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (17 corresponding lines) · ×1
  • Edited copy of a member (17 corresponding lines) apps/dashboard/lib/generated/logs/create_build_step.dart:132 — apps/dashboard/lib/generated/logs/create_build_step.dart:132-148 | apps/dashboard/lib/generated/logs/update_build_step.dart:93-109 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 16+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 16+ corresponding lines) apps/dashboard/lib/generated/secrets/commit_managed_secret.dart:187 — apps/dashboard/lib/generated/secrets/commit_managed_secret.dart:187-203 | apps/dashboard/lib/generated/secrets/delete_managed_secret.dart:137-152 | apps/dashboard/lib/generated/secrets/rename_managed_secret.dart:240-257 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 16 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 7+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 7+ corresponding lines) apps/dashboard/lib/generated/logs/create_build_step.dart:159 — apps/dashboard/lib/generated/logs/create_build_step.dart:159-167 | apps/dashboard/lib/generated/logs/get_build_log_write_state.dart:250-256 | apps/dashboard/lib/generated/logs/get_build_step_write_state.dart:220-226 | apps/dashboard/lib/generated/logs/update_build_step.dart:120-128 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 7 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (10 corresponding lines) · ×1
  • Edited copy of a member (10 corresponding lines) apps/dashboard/lib/generated/secrets/rename_managed_secret.dart:199 — apps/dashboard/lib/generated/secrets/rename_managed_secret.dart:199-209 | apps/dashboard/lib/generated/teams/remove_team_member.dart:133-142 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 6+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 6+ corresponding lines) apps/dashboard/lib/generated/logs/get_build_step_write_state.dart:67 — apps/dashboard/lib/generated/logs/get_build_step_write_state.dart:67-72 | apps/dashboard/lib/generated/logs/get_expired_build_logs.dart:52-57 | apps/dashboard/lib/generated/secrets/get_managed_secret_context.dart:153-160 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 6 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 10+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 10+ corresponding lines) packages/openci_workflow/lib/src/flutter/firebase_app_distribution/deploy_aab_to_firebase_app_distribution.dart:241 — packages/openci_workflow/lib/src/flutter/firebase_app_distribution/deploy_aab_to_firebase_app_distribution.dart:241-250 | packages/openci_workflow/lib/src/flutter/firebase_app_distribution/deploy_apk_to_firebase_app_distribution.dart:229-238 | packages/openci_workflow/lib/src/flutter/firebase_app_distribution/firebase_app_distribution_client.dart:190-199 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 10 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (16 corresponding lines) · ×1
  • Edited copy of a member (16 corresponding lines) apps/dashboard/lib/generated/logs/logs.dart:126 — apps/dashboard/lib/generated/logs/logs.dart:126-141 | apps/dashboard/lib/generated/secrets/secrets.dart:60-75 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (14 corresponding lines) · ×1
  • Edited copy of a member (14 corresponding lines) apps/dashboard/lib/generated/logs/logs.dart:143 — apps/dashboard/lib/generated/logs/logs.dart:143-158 | apps/dashboard/lib/generated/secrets/secrets.dart:45-58 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (12 corresponding lines) · ×1
  • Edited copy of a member (12 corresponding lines) apps/dashboard/lib/generated/teams/add_team_member.dart:23 — apps/dashboard/lib/generated/teams/add_team_member.dart:23-35 | apps/dashboard/lib/generated/teams/remove_team_member.dart:22-33 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (8 corresponding lines) · ×1
  • Edited copy of a member (8 corresponding lines) apps/dashboard/lib/generated/logs/create_build_step.dart:150 — apps/dashboard/lib/generated/logs/create_build_step.dart:150-157 | apps/dashboard/lib/generated/logs/update_build_step.dart:111-118 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 4+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 4+ corresponding lines) apps/dashboard/lib/generated/logs/get_build_log_write_state.dart:19 — apps/dashboard/lib/generated/logs/get_build_log_write_state.dart:19-22 | apps/dashboard/lib/generated/logs/get_build_step_write_state.dart:19-24 | apps/dashboard/lib/generated/secrets/get_managed_secret_context.dart:17-22 | apps/dashboard/lib/generated/secrets/get_secret_version_references.dart:16-24 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 4 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 7+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 7+ corresponding lines) apps/dashboard/lib/generated/secrets/commit_managed_secret.dart:205 — apps/dashboard/lib/generated/secrets/commit_managed_secret.dart:205-212 | apps/dashboard/lib/generated/secrets/delete_managed_secret.dart:154-160 | apps/dashboard/lib/generated/secrets/rename_managed_secret.dart:259-267 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 7 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (4 corresponding lines) · ×1
  • Edited copy of a member (4 corresponding lines) openci/lib/macos_release_publisher.dart:291 — openci/lib/macos_release_publisher.dart:291-294 | packages/openci_workflow/lib/src/flutter/play_console/deploy_aab_to_play_console.dart:276-279 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Duplicated block (118 lines × 2) · ×1
  • Duplicated block (118 lines × 2) apps/dashboard/lib/secret_manager/secret_manager_page.dart:1146 — apps/dashboard/lib/secret_manager/secret_manager_page.dart:1146-1263 | apps/dashboard/lib/secret_manager/secret_manager_page.dart:1667-1784 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `apps/dashboard/lib/secret_manager/secret_manager_page.dart:1146` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (75 lines × 2) · ×1
  • Duplicated block (75 lines × 2) apps/dashboard/lib/generated/builds/get_build_job.dart:209 — apps/dashboard/lib/generated/builds/get_build_job.dart:209-283 | apps/dashboard/lib/generated/builds/get_build_jobs.dart:223-297 — before extracting anything, compare `apps/dashboard/lib/generated/builds/get_build_job.dart` and `apps/dashboard/lib/generated/builds/get_build_jobs.dart` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 142 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (48–50 lines × 2) · ×1
  • Duplicated block (48–50 lines × 2) apps/dashboard/lib/secret_manager/secret_manager_page.dart:1010 — apps/dashboard/lib/secret_manager/secret_manager_page.dart:1010-1059 | apps/dashboard/lib/secret_manager/secret_manager_page.dart:1524-1571 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `apps/dashboard/lib/secret_manager/secret_manager_page.dart:1010` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (42 lines × 2) · ×1
  • Duplicated block (42 lines × 2) packages/openci_workflow/lib/src/shorebird/shorebird_ci.dart:50 — packages/openci_workflow/lib/src/shorebird/shorebird_ci.dart:50-91 | packages/openci_workflow/lib/src/shorebird/shorebird_ci.dart:149-190 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `packages/openci_workflow/lib/src/shorebird/shorebird_ci.dart:50` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
D4 · Code Duplication · Duplicated block (40 lines × 2) · ×1
  • Duplicated block (40 lines × 2) apps/dashboard/lib/settings/settings_page.dart:274 — apps/dashboard/lib/settings/settings_page.dart:274-313 | apps/dashboard/lib/settings/settings_page.dart:343-382 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `apps/dashboard/lib/settings/settings_page.dart:274` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (37–38 lines × 2) · ×1
  • Duplicated block (37–38 lines × 2) apps/dashboard/lib/secret_manager/secret_manager_page.dart:1061 — apps/dashboard/lib/secret_manager/secret_manager_page.dart:1061-1098 | apps/dashboard/lib/secret_manager/secret_manager_page.dart:1573-1609 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `apps/dashboard/lib/secret_manager/secret_manager_page.dart:1061` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `apps/dashboard/lib/secret_manager/secret_manager_page.dart:1610` calls `Column` and `apps/dashboard/lib/secret_manager/secret_manager_page.dart:1099` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (32 lines × 2) · ×1
  • Duplicated block (32 lines × 2) apps/dashboard/lib/generated/builds/get_build_job.dart:176 — apps/dashboard/lib/generated/builds/get_build_job.dart:176-207 | apps/dashboard/lib/generated/builds/get_build_jobs.dart:190-221 — before extracting anything, compare `apps/dashboard/lib/generated/builds/get_build_job.dart` and `apps/dashboard/lib/generated/builds/get_build_jobs.dart` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 142 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.
D4 · Code Duplication · Duplicated block (30 lines × 2) · ×1
  • Duplicated block (30 lines × 2) apps/dashboard/lib/generated/builds/get_build_job.dart:145 — apps/dashboard/lib/generated/builds/get_build_job.dart:145-174 | apps/dashboard/lib/generated/builds/get_build_jobs.dart:159-188 — before extracting anything, compare `apps/dashboard/lib/generated/builds/get_build_job.dart` and `apps/dashboard/lib/generated/builds/get_build_jobs.dart` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 142 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `apps/dashboard/lib/generated/builds/get_build_job.dart:145` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (23 lines × 2) · ×1
  • Duplicated block (23 lines × 2) apps/dashboard/lib/team/delete_team_bottom_sheet.dart:17 — apps/dashboard/lib/team/delete_team_bottom_sheet.dart:17-39 | apps/dashboard/lib/team/edit_team_bottom_sheet.dart:17-39 — before extracting anything, compare `apps/dashboard/lib/team/delete_team_bottom_sheet.dart` and `apps/dashboard/lib/team/edit_team_bottom_sheet.dart` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 60 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `apps/dashboard/lib/team/delete_team_bottom_sheet.dart:17` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `apps/dashboard/lib/team/edit_team_bottom_sheet.dart:15` calls `useTextEditingController`, `useMemoized` and `apps/dashboard/lib/team/delete_team_bottom_sheet.dart:16` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (21–22 lines × 2) · ×1
  • Duplicated block (21–22 lines × 2) apps/dashboard/lib/team/team_members_bottom_sheet.dart:87 — apps/dashboard/lib/team/team_members_bottom_sheet.dart:87-107 | apps/dashboard/lib/team/team_members_bottom_sheet.dart:205-226 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `apps/dashboard/lib/team/team_members_bottom_sheet.dart:87` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (22 lines × 2) · ×1
  • Duplicated block (22 lines × 2) packages/openci_workflow/lib/src/shorebird/shorebird_ci.dart:19 — packages/openci_workflow/lib/src/shorebird/shorebird_ci.dart:19-40 | packages/openci_workflow/lib/src/shorebird/shorebird_ci.dart:121-142 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `packages/openci_workflow/lib/src/shorebird/shorebird_ci.dart:19` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
D4 · Code Duplication · Duplicated block (18–19 lines × 3) · ×1
  • Duplicated block (18–19 lines × 3) apps/dashboard/lib/team/delete_team_bottom_sheet.dart:55 — apps/dashboard/lib/team/delete_team_bottom_sheet.dart:55-72 | apps/dashboard/lib/team/edit_team_bottom_sheet.dart:57-75 | apps/dashboard/lib/team/invite_team_member_bottom_sheet.dart:79-96 — before extracting anything, compare `apps/dashboard/lib/team/delete_team_bottom_sheet.dart` and `apps/dashboard/lib/team/edit_team_bottom_sheet.dart` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 60 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `apps/dashboard/lib/team/delete_team_bottom_sheet.dart:55` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (17–19 lines × 2) · ×1
  • Duplicated block (17–19 lines × 2) apps/dashboard/lib/secret_manager/secret_manager_page.dart:395 — apps/dashboard/lib/secret_manager/secret_manager_page.dart:395-413 | apps/dashboard/lib/secret_manager/secret_manager_page.dart:900-916 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `apps/dashboard/lib/secret_manager/secret_manager_page.dart:395` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (19 lines × 2) · ×1
  • Duplicated block (19 lines × 2) apps/dashboard/lib/team/delete_team_bottom_sheet.dart:31 — apps/dashboard/lib/team/delete_team_bottom_sheet.dart:31-49 | apps/dashboard/lib/team/switch_team_bottom_sheet.dart:54-72 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `apps/dashboard/lib/team/delete_team_bottom_sheet.dart:31` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `apps/dashboard/lib/team/delete_team_bottom_sheet.dart:29` calls `SizedBox` and `apps/dashboard/lib/team/switch_team_bottom_sheet.dart:53` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (18–19 lines × 2) · ×1
  • Duplicated block (18–19 lines × 2) packages/openci_workflow/lib/src/flutter/firebase_app_distribution/firebase_app_distribution_client.dart:153 — packages/openci_workflow/lib/src/flutter/firebase_app_distribution/firebase_app_distribution_client.dart:153-170 | packages/openci_workflow/lib/src/flutter/testflight/app_store_connect_client.dart:79-97 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `packages/openci_workflow/lib/src/flutter/testflight/app_store_connect_client.dart:79` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (17 lines × 3) · ×1
  • Duplicated block (17 lines × 3) packages/openci_workflow/lib/src/shorebird/shorebird_ci.dart:26 — packages/openci_workflow/lib/src/shorebird/shorebird_ci.dart:26-42 | packages/openci_workflow/lib/src/shorebird/shorebird_ci.dart:128-144 | packages/openci_workflow/lib/src/shorebird/shorebird_ci.dart:239-255 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `packages/openci_workflow/lib/src/shorebird/shorebird_ci.dart:26` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (16–17 lines × 2) · ×1
  • Duplicated block (16–17 lines × 2) apps/dashboard/lib/secret_manager/secret_manager_page.dart:1784 — apps/dashboard/lib/secret_manager/secret_manager_page.dart:1784-1800 | apps/dashboard/lib/secret_manager/secret_manager_page.dart:1912-1927 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `apps/dashboard/lib/secret_manager/secret_manager_page.dart:1784` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `apps/dashboard/lib/secret_manager/secret_manager_page.dart:1783` calls `_SecretFormError`, `SizedBox` and `apps/dashboard/lib/secret_manager/secret_manager_page.dart:1912` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (12–14 lines × 2) · ×1
  • Duplicated block (12–14 lines × 2) apps/dashboard/lib/team/delete_team_bottom_sheet.dart:75 — apps/dashboard/lib/team/delete_team_bottom_sheet.dart:75-86 | apps/dashboard/lib/team/invite_team_member_bottom_sheet.dart:100-113 — before extracting anything, compare `apps/dashboard/lib/team/delete_team_bottom_sheet.dart` and `apps/dashboard/lib/team/invite_team_member_bottom_sheet.dart` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 68 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `apps/dashboard/lib/team/delete_team_bottom_sheet.dart:75` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (12 lines × 3) · ×1
  • Duplicated block (12 lines × 3) apps/dashboard/lib/settings/settings_page.dart:273 — apps/dashboard/lib/settings/settings_page.dart:273-284 | apps/dashboard/lib/settings/settings_page.dart:342-353 | apps/dashboard/lib/settings/settings_page.dart:456-467 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `apps/dashboard/lib/settings/settings_page.dart:273` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (11 lines × 3) · ×1
  • Duplicated block (11 lines × 3) apps/openci_cli/lib/src/commands/delete/delete_secret_command.dart:84 — apps/openci_cli/lib/src/commands/delete/delete_secret_command.dart:84-94 | apps/openci_cli/lib/src/commands/list/list_secrets_command.dart:75-85 | apps/openci_cli/lib/src/commands/list/list_teams_command.dart:79-89 — before extracting anything, compare `apps/openci_cli/lib/src/commands/delete/delete_secret_command.dart` and `apps/openci_cli/lib/src/commands/list/list_secrets_command.dart` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 40 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `apps/openci_cli/lib/src/commands/delete/delete_secret_command.dart:84` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (9 lines × 3) · ×1
  • Duplicated block (9 lines × 3) apps/openci_cli/lib/src/commands/delete/delete_secret_command.dart:81 — apps/openci_cli/lib/src/commands/delete/delete_secret_command.dart:81-89 | apps/openci_cli/lib/src/commands/list/list_secrets_command.dart:72-80 | apps/openci_cli/lib/src/commands/register/secret_registration.dart:23-31 — before extracting anything, compare `apps/openci_cli/lib/src/commands/delete/delete_secret_command.dart` and `apps/openci_cli/lib/src/commands/list/list_secrets_command.dart` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 40 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `apps/openci_cli/lib/src/commands/delete/delete_secret_command.dart:81` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `apps/openci_cli/lib/src/commands/register/secret_registration.dart:32` calls `secretFunctionEndpoint` and `apps/openci_cli/lib/src/commands/delete/delete_secret_command.dart:90` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (9 lines × 2) · ×1
  • Duplicated block (9 lines × 2) packages/openci_workflow/lib/src/shorebird/shorebird_ci.dart:202 — packages/openci_workflow/lib/src/shorebird/shorebird_ci.dart:202-210 | packages/openci_workflow/lib/src/shorebird/shorebird_ci.dart:356-364 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `packages/openci_workflow/lib/src/shorebird/shorebird_ci.dart:202` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (8 lines × 4) · ×1
  • Duplicated block (8 lines × 4) apps/openci_cli/lib/src/commands/delete/delete_secret_command.dart:78 — apps/openci_cli/lib/src/commands/delete/delete_secret_command.dart:78-85 | apps/openci_cli/lib/src/commands/list/list_secrets_command.dart:69-76 | apps/openci_cli/lib/src/commands/register/secret_registration.dart:20-27 | apps/openci_cli/lib/src/commands/sync/sync_secrets.dart:55-62 — before extracting anything, compare `apps/openci_cli/lib/src/commands/delete/delete_secret_command.dart` and `apps/openci_cli/lib/src/commands/list/list_secrets_command.dart` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 40 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `apps/openci_cli/lib/src/commands/delete/delete_secret_command.dart:78` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (7 lines × 3) · ×1
  • Duplicated block (7 lines × 3) apps/dashboard/lib/build_logs/chips/job_status.dart:13 — apps/dashboard/lib/build_logs/chips/job_status.dart:13-19 | apps/dashboard/lib/build_logs/chips/job_status.dart:22-28 | apps/dashboard/lib/build_logs/chips/job_status.dart:31-37 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (5 lines × 8) · ×1
  • Duplicated block (5 lines × 8) apps/dashboard/lib/generated/builds/get_build_job.dart:376 — apps/dashboard/lib/generated/builds/get_build_job.dart:376-380 | apps/dashboard/lib/generated/secrets/commit_managed_secret.dart:74-78 | apps/dashboard/lib/generated/secrets/delete_managed_secret.dart:64-68 | apps/dashboard/lib/generated/secrets/rename_managed_secret.dart:74-78 | apps/dashboard/lib/generated/teams/add_team_member.dart:59-63 | apps/dashboard/lib/generated/teams/create_team.dart:56-60 | apps/dashboard/lib/generated/teams/remove_team_member.dart:58-62 | apps/dashboard/lib/generated/teams/rename_team.dart:56-60 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 8 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 8 times. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (7 lines × 4) · ×1
  • Duplicated block (7 lines × 4) apps/dashboard/lib/generated/logs/get_build_log_state.dart:198 — apps/dashboard/lib/generated/logs/get_build_log_state.dart:198-204 | apps/dashboard/lib/generated/logs/get_build_log_write_state.dart:203-209 | apps/dashboard/lib/generated/logs/get_build_logs.dart:214-220 | apps/dashboard/lib/generated/logs/get_build_step_write_state.dart:175-181 — before extracting anything, compare `apps/dashboard/lib/generated/logs/get_build_log_state.dart` and `apps/dashboard/lib/generated/logs/get_build_step_write_state.dart` as WHOLE FILES: this scan already matched 4 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. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (6 lines × 4) · ×1
  • Duplicated block (6 lines × 4) apps/dashboard/lib/generated/secrets/commit_managed_secret.dart:109 — apps/dashboard/lib/generated/secrets/commit_managed_secret.dart:109-114 | apps/dashboard/lib/generated/secrets/rename_managed_secret.dart:109-114 | apps/dashboard/lib/generated/secrets/rename_managed_secret.dart:146-151 | apps/dashboard/lib/generated/teams/rename_team.dart:129-134 — there are 4 copies across 3 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 4 sites; resolving a subset leaves the remainder to drift apart. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (5 lines × 6) · ×1
  • Duplicated block (5 lines × 6) apps/dashboard/lib/generated/secrets/complete_secret_version_cleanup.dart:66 — apps/dashboard/lib/generated/secrets/complete_secret_version_cleanup.dart:66-70 | apps/dashboard/lib/generated/secrets/complete_secret_version_cleanup.dart:144-148 | apps/dashboard/lib/generated/secrets/get_due_secret_versions.dart:49-53 | apps/dashboard/lib/generated/secrets/get_secret_version_references.dart:134-138 | apps/dashboard/lib/generated/secrets/queue_secret_version_cleanup.dart:63-67 | apps/dashboard/lib/generated/secrets/queue_secret_version_cleanup.dart:137-141 — there are 6 copies across 4 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 6 sites; resolving a subset leaves the remainder to drift apart. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (5 lines × 4) · ×1
  • Duplicated block (5 lines × 4) apps/dashboard/lib/generated/secrets/get_managed_secret_context.dart:61 — apps/dashboard/lib/generated/secrets/get_managed_secret_context.dart:61-65 | apps/dashboard/lib/generated/teams/add_team_member.dart:92-96 | apps/dashboard/lib/generated/teams/create_team.dart:89-93 | apps/dashboard/lib/generated/teams/remove_team_member.dart:91-95 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (6 lines × 3) · ×1
  • Duplicated block (6 lines × 3) packages/openci_workflow/lib/src/flutter/firebase_app_distribution/deploy_aab_to_firebase_app_distribution.dart:266 — packages/openci_workflow/lib/src/flutter/firebase_app_distribution/deploy_aab_to_firebase_app_distribution.dart:266-271 | packages/openci_workflow/lib/src/flutter/firebase_app_distribution/deploy_apk_to_firebase_app_distribution.dart:254-259 | packages/openci_workflow/lib/src/flutter/play_console/deploy_aab_to_play_console.dart:295-300 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (16 lines × 3) · ×1
  • Duplicated block (16 lines × 3) apps/dashboard/lib/generated/builds/builds.dart:58 — apps/dashboard/lib/generated/builds/builds.dart:58-73 | apps/dashboard/lib/generated/logs/logs.dart:167-182 | apps/dashboard/lib/generated/secrets/secrets.dart:141-156 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (5 lines × 5) · ×1
  • Duplicated block (5 lines × 5) apps/dashboard/lib/generated/builds/get_build_job.dart:15 — apps/dashboard/lib/generated/builds/get_build_job.dart:15-19 | apps/dashboard/lib/generated/builds/get_build_jobs.dart:27-31 | apps/dashboard/lib/generated/logs/get_build_log_state.dart:19-23 | apps/dashboard/lib/generated/logs/get_build_logs.dart:32-36 | apps/dashboard/lib/generated/secrets/get_secrets.dart:15-19 — before extracting anything, compare `apps/dashboard/lib/generated/builds/get_build_job.dart` and `apps/dashboard/lib/generated/builds/get_build_jobs.dart` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 142 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (11 lines × 4) · ×1
  • Duplicated block (11 lines × 4) apps/dashboard/lib/generated/builds/get_build_job.dart:21 — apps/dashboard/lib/generated/builds/get_build_job.dart:21-31 | apps/dashboard/lib/generated/secrets/get_secret_version_references.dart:26-38 | apps/dashboard/lib/generated/secrets/get_secrets.dart:21-31 | apps/dashboard/lib/generated/teams/get_team_members.dart:19-29 — before extracting anything, compare `apps/dashboard/lib/generated/builds/get_build_job.dart` and `apps/dashboard/lib/generated/secrets/get_secrets.dart` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 31 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (12 lines × 19) · ×1
  • Duplicated block (12 lines × 19) apps/dashboard/lib/generated/builds/get_build_job.dart:323 — apps/dashboard/lib/generated/builds/get_build_job.dart:323-334 | apps/dashboard/lib/generated/builds/get_build_job.dart:360-371 | apps/dashboard/lib/generated/logs/get_build_log_state.dart:182-193 | apps/dashboard/lib/generated/logs/get_build_log_write_state.dart:186-198 | apps/dashboard/lib/generated/logs/get_build_logs.dart:198-209 | apps/dashboard/lib/generated/logs/get_build_step_write_state.dart:158-170 | apps/dashboard/lib/generated/logs/get_expired_build_logs.dart:70-82 | apps/dashboard/lib/generated/secrets/get_due_secret_versions.dart:32-44 | apps/dashboard/lib/generated/secrets/get_managed_secret_context.dart:44-56 | apps/dashboard/lib/generated/secrets/get_secret_version_references.dart:46-58 | apps/dashboard/lib/generated/secrets/get_secret_version_references.dart:117-129 | apps/dashboard/lib/generated/secrets/get_secrets.dart:93-104 | apps/dashboard/lib/generated/secrets/get_secrets.dart:128-139 | apps/dashboard/lib/generated/teams/get_my_teams.dart:96-107 | apps/dashboard/lib/generated/teams/get_my_teams.dart:130-141 | apps/dashboard/lib/generated/teams/get_team_members.dart:39-50 | apps/dashboard/lib/generated/teams/get_team_members.dart:71-83 | apps/dashboard/lib/generated/teams/get_team_members.dart:106-117 | apps/dashboard/lib/generated/teams/get_team_members.dart:143-154 — before extracting anything, compare `apps/dashboard/lib/generated/builds/get_build_job.dart` and `apps/dashboard/lib/generated/secrets/get_secrets.dart` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 31 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (6 lines × 2) · ×1
  • Duplicated block (6 lines × 2) apps/dashboard/lib/generated/logs/append_build_log.dart:88 — apps/dashboard/lib/generated/logs/append_build_log.dart:88-93 | apps/dashboard/lib/generated/logs/delete_expired_build_logs.dart:101-106 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (8 lines × 2) · ×1
  • Duplicated block (8 lines × 2) apps/dashboard/lib/generated/secrets/commit_managed_secret.dart:152 — apps/dashboard/lib/generated/secrets/commit_managed_secret.dart:152-159 | apps/dashboard/lib/generated/teams/add_team_member.dart:132-139 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D5 · Coupling · Off the main sequence · ×1
  • Off the main sequence: openci_workflow — openci_workflow: abstractness 0.13, instability 0.00, distance 0.87 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
P1 · CI/CD gates · No CI pipeline · ×1
  • No CI pipeline — No CI workflow found (.github/workflows, azure-pipelines.yml, .gitlab-ci.yml, …) — changes aren't gated by an automated build/test.
R1 · Type Safety · Type Safety · ×1
  • Type Safety — 77 typed · 54 plain JS — the untyped files are apps/dashboard/web/flutter_bootstrap.js, firebase/dataconnect/test/billing.test.mjs, firebase/dataconnect/test/build_checks.test.mjs, firebase/dataconnect/test/build_dispatch.test.mjs, firebase/dataconnect/test/build_dispatch_queue.test.mjs, firebase/dataconnect/test/build_dispatch_retry.test.mjs (+48 more).
R10 · Code Duplication · Duplicated block with local edits (51 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (51 matched lines × 2 locations) firebase/functions/executor/orchard.ts:28 — firebase/functions/executor/orchard.ts:28 · firebase/functions/orchard_capacity.ts:130 — the two spans are one implementation copied and then locally edited — 336 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication · Duplicated block (30 lines × 2 locations) · ×1
  • Duplicated block (30 lines × 2 locations) apps/landing_page/components/build-job-card-demo.tsx:308 — apps/landing_page/components/build-job-card-demo.tsx:308 · apps/landing_page/components/build-job-card-demo.tsx:341 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
R10 · Code Duplication · Duplicated block with local edits (30 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (30 matched lines × 2 locations) firebase/functions/github_connection/github.ts:114 — firebase/functions/github_connection/github.ts:114 · firebase/functions/github_connection/github.ts:192 — the two spans are one implementation copied and then locally edited — 213 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication · Duplicated block (25 lines × 2 locations) · ×1
  • Duplicated block (25 lines × 2 locations) firebase/functions/executor/github.ts:171 — firebase/functions/executor/github.ts:171 · firebase/functions/executor/github.ts:539 — 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.
R10 · Code Duplication · Duplicated block (22 lines × 2 locations) · ×1
  • Duplicated block (22 lines × 2 locations) REDACTED:252 — REDACTED:252 · apps/landing_page/components/site.tsx:304 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it.
R10 · Code Duplication · Duplicated block (19 lines × 2 locations) · ×1
  • Duplicated block (19 lines × 2 locations) firebase/functions/executor/store.ts:63 — firebase/functions/executor/store.ts:63 · firebase/functions/queued_checks.ts:24 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
R10 · Code Duplication · Duplicated block (18 lines × 2 locations) · ×1
  • Duplicated block (18 lines × 2 locations) apps/landing_page/components/site.tsx:539 — apps/landing_page/components/site.tsx:539 · apps/landing_page/components/site.tsx:569 — 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.
R10 · Code Duplication · Duplicated block (12 lines × 2 locations) · ×1
  • Duplicated block (12 lines × 2 locations) firebase/functions/executor/logs.ts:59 — firebase/functions/executor/logs.ts:59 · firebase/functions/executor/logs.ts:86 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication · Duplicated block (11 lines × 3 locations) · ×1
  • Duplicated block (11 lines × 3 locations) apps/landing_page/app/(en)/layout.tsx:11 — apps/landing_page/app/(en)/layout.tsx:11 · apps/landing_page/app/(ja)/layout.tsx:11 · apps/landing_page/app/(redirect)/layout.tsx:11 — the 3 copies are spread across 3 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. There is one copy in each of 3 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete.
R10 · Code Duplication · Duplicated block (10 lines × 2 locations) · ×1
  • Duplicated block (10 lines × 2 locations) firebase/functions/executor/github.ts:424 — firebase/functions/executor/github.ts:424 · firebase/functions/executor/github.ts:498 — 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.
R10 · Code Duplication · Duplicated block with local edits (7 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (7 matched lines × 2 locations) firebase/functions/github_connection/github.ts:28 — firebase/functions/github_connection/github.ts:28 · firebase/functions/orchard_capacity.ts:20 — the two spans are one implementation copied and then locally edited — 68 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication · Duplicated block (6 lines × 3 locations) · ×1
  • Duplicated block (6 lines × 3 locations) firebase/functions/executor/billing.ts:124 — firebase/functions/executor/billing.ts:124 · firebase/functions/executor/billing.ts:155 · firebase/functions/executor/billing.ts:182 — all 3 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication · Duplicated block with local edits (5 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (5 matched lines × 2 locations) firebase/functions/billing/service.ts:109 — firebase/functions/billing/service.ts:109 · firebase/functions/executor/billing.ts:51 — the two spans are one implementation copied and then locally edited — 64 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication · Duplicated block (5 lines × 3 locations) · ×1
  • Duplicated block (5 lines × 3 locations) firebase/functions/executor/github.ts:427 — firebase/functions/executor/github.ts:427 · firebase/functions/executor/github.ts:501 · REDACTED:308 — the 3 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R2 · Cyclomatic Complexity · Complex function execute (cyclomatic 40, cognitive 46) · ×1
  • Complex function execute (cyclomatic 40, cognitive 46) firebase/functions/secrets/service.ts:49 — execute has cyclomatic complexity 40 and cognitive complexity 46; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function checkWorkerMemory (cyclomatic 34, cognitive 28) · ×1
  • Complex function checkWorkerMemory (cyclomatic 34, cognitive 28) firebase/functions/executor/orchard.ts:146 — checkWorkerMemory has cyclomatic complexity 34 and cognitive complexity 28; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function candidates (cyclomatic 33, cognitive 59) · ×1
  • Complex function candidates (cyclomatic 33, cognitive 59) firebase/functions/github_connection/github.ts:102 — candidates has cyclomatic complexity 33 and cognitive complexity 59; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function sync (cyclomatic 31, cognitive 29) · ×1
  • Complex function sync (cyclomatic 31, cognitive 29) firebase/functions/queued_checks.ts:79 — sync has cyclomatic complexity 31 and cognitive complexity 29; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function hasOrchardCapacity (cyclomatic 30, cognitive 38) · ×1
  • Complex function hasOrchardCapacity (cyclomatic 30, cognitive 38) firebase/functions/orchard_capacity.ts:39 — hasOrchardCapacity has cyclomatic complexity 30 and cognitive complexity 38; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 30, cognitive 25) · ×1
  • Complex function (anonymous) (cyclomatic 30, cognitive 25) firebase/functions/executor/github.ts:287 — (anonymous) has cyclomatic complexity 30 and cognitive complexity 25; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 29, cognitive 36) · ×1
  • Complex function (anonymous) (cyclomatic 29, cognitive 36) firebase/functions/build_dispatch_functions.ts:270 — (anonymous) has cyclomatic complexity 29 and cognitive complexity 36; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function executeBuild (cyclomatic 29, cognitive 32) · ×1
  • Complex function executeBuild (cyclomatic 29, cognitive 32) firebase/functions/executor/execute.ts:86 — executeBuild has cyclomatic complexity 29 and cognitive complexity 32; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function execute (cyclomatic 27, cognitive 23) · ×1
  • Complex function execute (cyclomatic 27, cognitive 23) firebase/functions/github_connection/service.ts:66 — execute has cyclomatic complexity 27 and cognitive complexity 23; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function resolveCheckout (cyclomatic 24, cognitive 28) · ×1
  • Complex function resolveCheckout (cyclomatic 24, cognitive 28) firebase/functions/executor/github.ts:231 — resolveCheckout has cyclomatic complexity 24 and cognitive complexity 28; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function repositories (cyclomatic 24, cognitive 27) · ×1
  • Complex function repositories (cyclomatic 24, cognitive 27) firebase/functions/github_connection/github.ts:174 — repositories has cyclomatic complexity 24 and cognitive complexity 27; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function receiveStripeWebhook (cyclomatic 24, cognitive 20) · ×1
  • Complex function receiveStripeWebhook (cyclomatic 24, cognitive 20) firebase/functions/billing/webhook.ts:23 — receiveStripeWebhook has cyclomatic complexity 24 and cognitive complexity 20; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function reconcileCardSession (cyclomatic 24, cognitive 18) · ×1
  • Complex function reconcileCardSession (cyclomatic 24, cognitive 18) firebase/functions/billing/card_setup.ts:34 — reconcileCardSession has cyclomatic complexity 24 and cognitive complexity 18; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function request (cyclomatic 23, cognitive 31) · ×1
  • Complex function request (cyclomatic 23, cognitive 31) firebase/functions/test/pull_request_qr.test.mjs:276 — request has cyclomatic complexity 23 and cognitive complexity 31; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 23, cognitive 16) · ×1
  • Complex function (anonymous) (cyclomatic 23, cognitive 16) firebase/functions/build_dispatch_functions.ts:204 — (anonymous) has cyclomatic complexity 23 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 22, cognitive 36) · ×1
  • Complex function (anonymous) (cyclomatic 22, cognitive 36) firebase/functions/build_dispatch_functions.ts:73 — (anonymous) has cyclomatic complexity 22 and cognitive complexity 36; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function execute (cyclomatic 22, cognitive 32) · ×1
  • Complex function execute (cyclomatic 22, cognitive 32) firebase/functions/teams/service.ts:31 — execute has cyclomatic complexity 22 and cognitive complexity 32; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function skippedCheck (cyclomatic 22, cognitive 23) · ×1
  • Complex function skippedCheck (cyclomatic 22, cognitive 23) firebase/functions/executor/github.ts:137 — skippedCheck has cyclomatic complexity 22 and cognitive complexity 23; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function billingConfig (cyclomatic 22, cognitive 17) · ×1
  • Complex function billingConfig (cyclomatic 22, cognitive 17) firebase/functions/billing/config.ts:12 — billingConfig has cyclomatic complexity 22 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function observePurchase (cyclomatic 21, cognitive 9) · ×1
  • Complex function observePurchase (cyclomatic 21, cognitive 9) firebase/functions/billing/purchase.ts:76 — observePurchase has cyclomatic complexity 21 and cognitive complexity 9; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 20, cognitive 31) · ×1
  • Complex function (anonymous) (cyclomatic 20, cognitive 31) apps/landing_page/components/build-job-card-demo.tsx:141 — (anonymous) has cyclomatic complexity 20 and cognitive complexity 31; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function execute (cyclomatic 20, cognitive 20) · ×1
  • Complex function execute (cyclomatic 20, cognitive 20) firebase/functions/billing/service.ts:34 — execute has cyclomatic complexity 20 and cognitive complexity 20; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function receiveGitHubWebhook (cyclomatic 19, cognitive 20) · ×1
  • Complex function receiveGitHubWebhook (cyclomatic 19, cognitive 20) firebase/functions/github_webhook.ts:11 — receiveGitHubWebhook has cyclomatic complexity 19 and cognitive complexity 20; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function cleanupExecution (cyclomatic 19, cognitive 16) · ×1
  • Complex function cleanupExecution (cyclomatic 19, cognitive 16) firebase/functions/executor/execute.ts:48 — cleanupExecution has cyclomatic complexity 19 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function configure (cyclomatic 19, cognitive 12) · ×1
  • Complex function configure (cyclomatic 19, cognitive 12) firebase/functions/executor/store.ts:82 — configure has cyclomatic complexity 19 and cognitive complexity 12; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function close (cyclomatic 18, cognitive 30) · ×1
  • Complex function close (cyclomatic 18, cognitive 30) firebase/functions/executor/billing.ts:181 — close has cyclomatic complexity 18 and cognitive complexity 30; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function readPullRequestQrCodes (cyclomatic 18, cognitive 27) · ×1
  • Complex function readPullRequestQrCodes (cyclomatic 18, cognitive 27) REDACTED:126 — readPullRequestQrCodes has cyclomatic complexity 18 and cognitive complexity 27; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 18, cognitive 20) · ×1
  • Complex function (anonymous) (cyclomatic 18, cognitive 20) firebase/dataconnect/test/build_job_planning.test.mjs:36 — (anonymous) has cyclomatic complexity 18 and cognitive complexity 20; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function callback (cyclomatic 18, cognitive 18) · ×1
  • Complex function callback (cyclomatic 18, cognitive 18) firebase/functions/github_connection/service.ts:173 — callback has cyclomatic complexity 18 and cognitive complexity 18; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function runtime (cyclomatic 18, cognitive 16) · ×1
  • Complex function runtime (cyclomatic 18, cognitive 16) firebase/functions/executor/runtime.ts:16 — runtime has cyclomatic complexity 18 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function publishPullRequestQrCodes (cyclomatic 17, cognitive 23) · ×1
  • Complex function publishPullRequestQrCodes (cyclomatic 17, cognitive 23) REDACTED:289 — publishPullRequestQrCodes has cyclomatic complexity 17 and cognitive complexity 23; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function status (cyclomatic 17, cognitive 21) · ×1
  • Complex function status (cyclomatic 17, cognitive 21) firebase/functions/billing/service.ts:88 — status has cyclomatic complexity 17 and cognitive complexity 21; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function reconcile (cyclomatic 16, cognitive 26) · ×1
  • Complex function reconcile (cyclomatic 16, cognitive 26) firebase/functions/billing/service.ts:198 — reconcile has cyclomatic complexity 16 and cognitive complexity 26; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 16, cognitive 21) · ×1
  • Complex function (anonymous) (cyclomatic 16, cognitive 21) apps/landing_page/components/build-job-card-demo.tsx:174 — (anonymous) has cyclomatic complexity 16 and cognitive complexity 21; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function validatedQrMetadata (cyclomatic 16, cognitive 15) · ×1
  • Complex function validatedQrMetadata (cyclomatic 16, cognitive 15) REDACTED:75 — validatedQrMetadata has cyclomatic complexity 16 and cognitive complexity 15; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function cardSetupStatus (cyclomatic 16, cognitive 14) · ×1
  • Complex function cardSetupStatus (cyclomatic 16, cognitive 14) firebase/functions/billing/card_setup.ts:165 — cardSetupStatus has cyclomatic complexity 16 and cognitive complexity 14; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function admit (cyclomatic 15, cognitive 23) · ×1
  • Complex function admit (cyclomatic 15, cognitive 23) firebase/functions/executor/billing.ts:68 — admit has cyclomatic complexity 15 and cognitive complexity 23; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function retainPaidPeriod (cyclomatic 15, cognitive 15) · ×1
  • Complex function retainPaidPeriod (cyclomatic 15, cognitive 15) firebase/functions/billing/service.ts:315 — retainPaidPeriod has cyclomatic complexity 15 and cognitive complexity 15; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function deleteTeam (cyclomatic 14, cognitive 27) · ×1
  • Complex function deleteTeam (cyclomatic 14, cognitive 27) firebase/functions/billing/service.ts:258 — deleteTeam has cyclomatic complexity 14 and cognitive complexity 27; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function dispatchBuildJob (cyclomatic 14, cognitive 25) · ×1
  • Complex function dispatchBuildJob (cyclomatic 14, cognitive 25) firebase/functions/build_dispatch.ts:139 — dispatchBuildJob has cyclomatic complexity 14 and cognitive complexity 25; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R3 · Large Files · apps/landing_page/components/site.tsx · ×1
  • apps/landing_page/components/site.tsx: 999 lines of code apps/landing_page/components/site.tsx:1 — apps/landing_page/components/site.tsx has 999 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · firebase/functions/executor/github.ts · ×1
  • firebase/functions/executor/github.ts: 569 lines of code firebase/functions/executor/github.ts:1 — firebase/functions/executor/github.ts has 569 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · REDACTED · ×1
  • REDACTED: 413 lines of code REDACTED:1 — REDACTED has 413 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · firebase/generated/billing-admin/index.cjs.js · ×1
  • firebase/generated/billing-admin/index.cjs.js: 408 lines of code firebase/generated/billing-admin/index.cjs.js:1 — firebase/generated/billing-admin/index.cjs.js has 408 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · firebase/generated/dispatch-admin/index.cjs.js · ×1
  • firebase/generated/dispatch-admin/index.cjs.js: 403 lines of code firebase/generated/dispatch-admin/index.cjs.js:1 — firebase/generated/dispatch-admin/index.cjs.js has 403 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R7 · Dead Code · Dead file (~54 LoC) · ×1
  • Dead file (~54 LoC) infra/orchard/check-network.mjs — no import path from any entry point (48 application, 13 tooling, 36 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~9 LoC) · ×1
  • Dead file (~9 LoC) firebase/functions/core.ts — no import path from any entry point (48 application, 13 tooling, 36 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Minor — 50 finding(s)
X10 · Duplicated predicate · Duplicated predicate · ×24
  • Duplicated predicate apps/dashboard/lib/auth/auth_page.dart:573 — `!context.mounted || result == null || result.files.isEmpty` appears character-identically in 2 files — apps/dashboard/lib/auth/auth_page.dart, apps/dashboard/lib/auth/self_hosted_setup_form.dart. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate apps/openci_cli/lib/src/asc/check_asc_authentication.dart:43 — `!outputTooLarge && bytes.length + chunk.length <= 16 * 1024` appears character-identically in 2 files — apps/openci_cli/lib/src/asc/check_asc_authentication.dart, apps/openci_cli/lib/src/asc/create_asc_api_key.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 apps/openci_cli/lib/src/commands/setup/confirm_asc_key_creation.dart:27 — `!terminal.hasTerminal || !prompt.hasTerminal` appears character-identically in 2 files — apps/openci_cli/lib/src/commands/setup/confirm_asc_key_creation.dart, apps/openci_cli/lib/src/commands/setup/read_apple_id.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 apps/dashboard/lib/cicd_log/widgets/build_job_status_to_chip_status.dart:6 — `BuildJobStatus.FAILURE || BuildJobStatus.CANCELLED || BuildJobStatus.TIMED_OUT` appears character-identically in 3 files — apps/dashboard/lib/cicd_log/widgets/build_job_status_to_chip_status.dart, apps/dashboard/lib/cicd_log/widgets/cicd_job_status.dart, apps/dashboard/lib/cicd_log/widgets/workflow_overview.dart. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate packages/openci_workflow/lib/src/flutter/firebase_app_distribution/deploy_aab_to_firebase_app_distribution.dart:19 — `aabPath.trim().isEmpty || !aabPath.endsWith('.aab')` appears character-identically in 2 files — packages/openci_workflow/lib/src/flutter/firebase_app_distribution/deploy_aab_to_firebase_app_distribution.dart, packages/openci_workflow/lib/src/flutter/play_console/deploy_aab_to_play_console.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 apps/openci_cli/lib/src/commands/list/list_teams_command.dart:62 — `error is FormatException || error is TypeError` appears character-identically in 3 files — apps/openci_cli/lib/src/commands/list/list_teams_command.dart, apps/openci_cli/lib/src/commands/status_command.dart, apps/openci_cli/lib/src/commands/switch/switch_team_command.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 apps/openci_cli/lib/src/commands/list/list_secrets_command.dart:55 — `error.statusCode == HttpStatus.unauthorized || error.statusCode == HttpStatus.forbidden` appears character-identically in 7 files — apps/openci_cli/lib/src/commands/list/list_secrets_command.dart, apps/openci_cli/lib/src/commands/list/list_teams_command.dart, apps/openci_cli/lib/src/commands/setup/asc_key_registration.dart, apps/openci_cli/lib/src/commands/setup/ensure_ios_certificate_key.dart. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate packages/openci_workflow/lib/src/flutter/firebase_app_distribution/deploy_ipa_to_firebase_app_distribution.dart:22 — `ipaPath.trim().isEmpty || !ipaPath.endsWith('.ipa')` appears character-identically in 2 files — packages/openci_workflow/lib/src/flutter/firebase_app_distribution/deploy_ipa_to_firebase_app_distribution.dart, packages/openci_workflow/lib/src/flutter/testflight/deploy_ipa_to_testflight.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 apps/dashboard/lib/generated/logs/get_build_log_write_state.dart:130 — `logId == otherTyped.logId && sequence == otherTyped.sequence && stepId == otherTyped.stepId && source == otherTyped.source && stream == othe…` appears character-identically in 2 files — apps/dashboard/lib/generated/logs/get_build_log_write_state.dart, apps/dashboard/lib/generated/logs/get_build_logs.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 apps/openci_cli/lib/src/commands/list/list_teams_command.dart:76 — `profile != null && profile.authType == 'firebase' && profile.token.trim().isNotEmpty && server != null && (server.scheme == 'http' || server…` appears character-identically in 2 files — apps/openci_cli/lib/src/commands/list/list_teams_command.dart, apps/openci_cli/lib/src/commands/switch/switch_team_command.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 apps/openci_cli/lib/src/commands/delete/delete_secret_command.dart:81 — `profile != null && profile.token.trim().isNotEmpty && profile.teamId.trim().isNotEmpty && server != null && (server.scheme == 'http' || serv…` appears character-identically in 3 files — apps/openci_cli/lib/src/commands/delete/delete_secret_command.dart, apps/openci_cli/lib/src/commands/list/list_secrets_command.dart, apps/openci_cli/lib/src/commands/register/secret_registration.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 apps/dashboard/lib/billing/billing_api.dart:16 — `ref.mounted && auth.currentUser?.uid == user.uid` appears character-identically in 2 files — apps/dashboard/lib/billing/billing_api.dart, apps/dashboard/lib/team/team_members_api.dart. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate packages/openci_workflow/lib/src/flutter/firebase_app_distribution/deploy_aab_to_firebase_app_distribution.dart:196 — `releaseName is! String || !RegExp( '^${RegExp.escape(appName)}/releases/[a-zA-Z0-9_-]+\$', ).hasMatch(releaseName)` appears character-identically in 3 files — packages/openci_workflow/lib/src/flutter/firebase_app_distribution/deploy_aab_to_firebase_app_distribution.dart, packages/openci_workflow/lib/src/flutter/firebase_app_distribution/deploy_apk_to_firebase_app_distribution.dart, packages/openci_workflow/lib/src/flutter/firebase_app_distribution/firebase_app_distribution_client.dart. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate apps/openci_cli/lib/src/functions/callable_api.dart:40 — `response.statusCode < 200 || response.statusCode >= 300` appears character-identically in 7 files — apps/openci_cli/lib/src/functions/callable_api.dart, openci/lib/macos_release_publisher.dart, packages/openci_workflow/lib/src/flutter/firebase_app_distribution/deploy_aab_to_firebase_app_distribution.dart, packages/openci_workflow/lib/src/flutter/firebase_app_distribution/deploy_apk_to_firebase_app_distribution.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 apps/dashboard/lib/generated/logs/get_build_log_state.dart:132 — `stepId == otherTyped.stepId && name == otherTyped.name && status == otherTyped.status && stepOrder == otherTyped.stepOrder && durationMs == …` appears character-identically in 2 files — apps/dashboard/lib/generated/logs/get_build_log_state.dart, apps/dashboard/lib/generated/logs/get_build_step_write_state.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 apps/dashboard/lib/generated/builds/get_build_job.dart:145 — `teamId == otherTyped.teamId && id == otherTyped.id && status == otherTyped.status && owner == otherTyped.owner && repo == otherTyped.repo &&…` appears character-identically in 2 files — apps/dashboard/lib/generated/builds/get_build_job.dart, apps/dashboard/lib/generated/builds/get_build_jobs.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 apps/dashboard/lib/generated/secrets/commit_managed_secret.dart:103 — `teamId == otherTyped.teamId && name == otherTyped.name` appears character-identically in 3 files — apps/dashboard/lib/generated/secrets/commit_managed_secret.dart, apps/dashboard/lib/generated/secrets/rename_managed_secret.dart, apps/dashboard/lib/generated/teams/rename_team.dart. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate packages/openci_workflow/lib/src/flutter/firebase_app_distribution/deploy_apk_to_firebase_app_distribution.dart:179 — `uri == null || uri.scheme != 'https' || uri.authority != 'appdistribution.firebase.google.com' || uri.path != path` appears character-identically in 2 files — packages/openci_workflow/lib/src/flutter/firebase_app_distribution/deploy_apk_to_firebase_app_distribution.dart, packages/openci_workflow/lib/src/flutter/firebase_app_distribution/firebase_app_distribution_client.dart. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate firebase/functions/billing/service.ts:35 — `!input || typeof input !== "object" || Array.isArray(input)` appears character-identically in 3 files — firebase/functions/billing/service.ts, firebase/functions/secrets/service.ts, firebase/functions/teams/service.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate REDACTED:53 — `!request.auth || request.auth.token.firebase?.sign_in_provider === "anonymous"` appears character-identically in 4 files — REDACTED, firebase/functions/github_connection_functions.ts, firebase/functions/secret_functions.ts, firebase/functions/team_functions.ts. 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 firebase/functions/executor/orchard.ts:20 — `!value || typeof value !== "object" || Array.isArray(value)` appears character-identically in 4 files — firebase/functions/executor/orchard.ts, firebase/functions/github_connection/github.ts, firebase/functions/github_connection/service.ts, firebase/functions/orchard_capacity.ts. 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 firebase/functions/build_dispatch.ts:60 — `"code" in failure && typeof failure.code === "string" && codes.has(failure.code)` appears character-identically in 2 files — firebase/functions/build_dispatch.ts, firebase/functions/build_queue_error.ts. 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 firebase/functions/executor/orchard.ts:35 — `(!local && this.base.protocol !== "https:") || this.base.username || this.base.password || this.base.search || this.base.hash || !options.ac…` appears character-identically in 2 files — firebase/functions/executor/orchard.ts, firebase/functions/orchard_capacity.ts. 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 firebase/functions/executor/orchard.ts:31 — `options.allowLocalHttp && this.base.protocol === "http:" && ["localhost", "127.0.0.1"].includes(this.base.hostname)` appears character-identically in 2 files — firebase/functions/executor/orchard.ts, firebase/functions/orchard_capacity.ts. 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.
D31 · IaC & Container Security · Low IaC · ×8
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
IC1 · Incompleteness & stubs · Disabled test · ×4
  • Disabled test packages/openci_workflow/test/src/dart/pub_dev_publisher_test.dart:177 — 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/openci_workflow/test/src/dart/pub_dev_publisher_test.dart:203 — 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/openci_workflow/test/src/dart/pub_dev_publisher_test.dart:218 — 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/openci_workflow/test/src/dart/pub_dev_publisher_test.dart:357 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
D30 · Dependency Vulnerabilities · Low CVE · ×2
  • REDACTED
  • REDACTED
D20 · ADR Quality · No ADRs found · ×1
  • No ADRs found firebase/dart_functions/bin/server.dart:26 — No ADRs found. No recognised ADR directory (`docs/adr/`, `docs/decisions/`, `adr/`, `docs/rfcs/`, an `ADR0001/` folder, or their siblings) exists anywhere in this tree. What was searched, so you can tell an empty log from a search that missed one: every directory under the tree (build output, dependencies and VCS metadata excepted), for a document that is either any non-index page inside a recognised ADR directory, whatever its name and however deeply nested (`docs/adr/use-postgres.md`, `docs/adr/2024/0001-x.md`); or a file anywhere whose name is ADR-shaped (`0001-use-postgres.md`, `adr-012-caching.md`); or, when neither turned anything up, a document carrying the decision-record signature (an "Architecture Decision Record" heading, or Status / Context / Decision / Consequences as section headings). A decision log that clears none of these — unnumbered files outside any recognised directory, without those headings — is not seen by this check and this row is then wrong. If that is your case, say so rather than renaming anything; otherwise, consider recording architectural decisions in `docs/adr/`. ADRs are expected here because `firebase/dart_functions/bin/server.dart` makes this repository a deployable product (line 26).
D26 · Project Cohesion · Projects may be oversized for their cohesion · ×1
  • Projects may be oversized for their cohesion apps/dashboard/pubspec.yaml:1 — `apps/dashboard` (16571 LoC, 193 module-visible types across 22 directories) overshoots its size bounds. 1 of 32 build unit(s) (Gradle, SwiftPM, Xcode, npm, pub) overshoot their size bounds, lowering Project Cohesion to 9.4/10. Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
D28 · Secrets (history) · Rotate the exposed credentials · ×1
  • REDACTED
M2 · Architecture documentation · No ADRs · ×1
  • No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
M2 · Architecture documentation · No architecture diagram/doc · ×1
  • No architecture diagram/doc — No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
P2 · Observability · Logging is not universal · ×1
  • Logging is not universal — Only 1/12 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `.`, `apps/dashboard`, `apps/dashboard/ios`, `apps/dashboard/macos`, `apps/landing_page` and 6 more.
P3 · Security & performance tooling · No SAST · ×1
  • No SAST — No static application security testing detected. For this repository's stack, add the Dart analyzer's security lints plus `semgrep --config=auto` — this repository has no CI pipeline yet, so run it locally to clear the existing findings, then make it a step of the first workflow you add so a regression fails the build. What was searched, so you can tell an absence from a miss: the 0 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
P3 · Security & performance tooling · No dependency-update automation · ×1
  • No dependency-update automation package.json:15 — `package.json` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`.
S1 · Web-Security Posture · No security response headers detected · ×1
  • No security response headers detected firebase/firebase.json:1 — None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is configured — defense in depth, even when a reverse proxy could set them. This is reported because `firebase.json` configures this repository's static hosting, including its response headers, so the configuration that would carry these headers is in this repository and was read in full. (−2.0 on this card.)
X2 · Cancellation propagation · Not all async functions that make a request accept an AbortSignal · ×1
  • Not all async functions that make a request accept an AbortSignal — Only 8/10 async functions that make a cancellable request (fetch, axios, ky, ofetch, got, undici, node:http) accept an AbortSignal or pass one on, so a request keeps running after whatever wanted it has given up — a page navigated away from, an unmounted component, a timed-out job. Take a `signal` (or an options object that carries one) and hand it to the request; where nothing could ever cancel the call, omitting it is a deliberate choice — judge against how the function is used.

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.

DimensionToolVersionCommandFindingsRaw output
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=0 --max-count=200" --report-format json --report-path /tmp/watchdog-gitleaks-c1224321fed74a43b2b8d73dcdae37bf/history.json --exit-code 0 --source .0artifacts/raw/gitleaks-history.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=200 --max-count=800" --report-format json --report-path /tmp/watchdog-gitleaks-c1224321fed74a43b2b8d73dcdae37bf/history-1.json --exit-code 0 --source .1artifacts/raw/gitleaks-history-1.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=1000 --max-count=1473" --report-format json --report-path /tmp/watchdog-gitleaks-c1224321fed74a43b2b8d73dcdae37bf/history-2.json --exit-code 0 --source .79artifacts/raw/gitleaks-history-2.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-c1224321fed74a43b2b8d73dcdae37bf/tree.json --exit-code 0 --source .1artifacts/raw/gitleaks-tree.json
D29 · Static Analysis (SAST)semgrep—semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt --exclude apps/openci_cli/lib/src/gen --exclude apps/website/content --exclude openci/generated --exclude packages/macos_updater/lib/src .6artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilitiestrivy—trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** .22artifacts/raw/trivy-fs.json
D31 · IaC & Container Securitytrivy—trivy config --format json --quiet .25artifacts/raw/trivy-config.json
D32 · Data Compliance (PII/GDPR)semgrep—semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 3 file(s) — `apps/dashboard/android/app/build.gradle.kts`, `apps/website/src/pages/ogp/[...route].ts`, `firebase/functions/orchard_network.ts` — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.0—
D36 · Supply-chain Provenance & Signingprovenance—provenance: not applicable — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for.0—
D37 · Vulnerability-disclosure Policydisclosure—disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.0—
D40 · Network Egress Confinementruntime-hardening—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.0—
D41 · Kernel & Syscall Confinementruntime-hardening—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.0—
D42 · Runtime Threat Enforcementruntime-hardening—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.0—
D43 · Malicious Dependenciestrivy—trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** .0artifacts/raw/trivy-fs.json

Run 01a1eb62-f1a3-700c-b491-262d82ca88b0 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.

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.

⬇ Findings, MITRE CWE-tagged .sarif⬇ Health changelog .md