Public report of sws2apps/organized-app, 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, 19:34 UTC · Survey ID cd_ada4a2a8bea8441eaf229a8d4fb8a423

sws2apps/organized-app

Measured 17 November 2026, 19:31 UTC, at code version 4609bd1

First survey, so nothing to compare with yet
CAI score 44.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 large codebase: 148,385 lines of product code in 1 project, tests not counted · Estimated rebuild effort: about 1.0 person-years · Weakest lens: Code Health, 38.1

Findings by how serious they are

32 critical 718 serious 198 minor

10 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, 19:31 UTC

A measurement, not a certificate. The Code Assurance Index records a number together with the evidence it was worked out from, so anyone can recalculate it, but it doesn't certify or guarantee the code. The standard was written by Canine Development, which also builds the Canine Code Analyzer. It is open to any tool that implements it, and today the Canine Code Analyzer is the only one that does.

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 ▸

70of 70 dimensions measured by tools.
900of 948 findings point to an exact file and line, so you can open each one in the code. The other 48 concern the repository as a whole, such as missing documentation.
70dimensions across 7 lenses, read from 148,385 lines of product code in 1 project.
Chapters

Executive summary

sws2apps/organized-app is rated At risk because critical security findings are open, most of them in the packages it uses. It scores 44.3 out of 100, which the At risk rating leaves unchanged.

Code Health, at 38.1, is the weakest lens and counts most in the score. The best first step is fixing the 183 functions that are too long, worth about 4.2 points. Removing the copied code would lift Code Health itself, worth about 3.7 points. Raising Code Health to 70 would lift the score to about 49.5.

Sixteen known security holes in the packages the code depends on can be used by attackers. Three passwords or keys are open to anyone who can read the repository, and two secrets can leak from the build pipeline. Updating the vulnerable packages, replacing each exposed password or key and limiting each secret to its own step would close these risks. Setting a waiting period for automatic updates would fix the automatic dependency update that takes a new release at once. The four loops of files that import each other need breaking.

The product code is 148,385 lines, about €140,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.
Code Health 38.1 · counts for 46%Accessibility 41.0 · counts for 25%Production Readiness 48.6 · counts for 14%Maturity 58.4 · counts for 8%Security and Compliance 61.5 · counts for 4%Architecture 70.1 · counts for 2%Performance 100.0 · counts for 1%

If Code Health rose from 38.1 to 70, the lowest score rated Strong, the score would rise from 44.3 to about 49.5.

Code composition: what the lines of code are
Product code 100%Tests 0%
Rebuild cost: about €140,000 · Estimate
Cost to rebuild€48,000 to €240,000, for 794 to 2,519 hours of work, about 1.0 person-years for 1 to 2 engineers
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 44. 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.
SizeLarge: 148,385 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 183 FunctionTooLong finding(s) in God Classes — start with index.tsx (69), useConfirmImport.tsx (4), schedules.ts (4).
Raises the score by about 4.2 points · High effort · God Classes
2
Resolve the 1 Deprecated finding(s) in Dependency Hygiene — start with package.json.
Raises the score by about 1.9 points · Low effort · Dependency Hygiene
3
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.
Raises the score by about 3.7 points · Medium effort · Code Duplication

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 €140,000 to build again, about 1.0 person-years of work. Its weakest lens is Code Health, at 38.1 (Weak). Code Health is about how easy the code is to read and change safely, and code that is hard to read is slow and risky to change, so every future change costs more than it should. Because the weakest lens counts most in the score, work on Code Health also moves the score most.
Based on: the rebuild estimate · the Code Health grade · how much each lens counts
What to do: Start with the Code Health actions in Top priorities.
If you do one thing first · First action
Resolve the 183 FunctionTooLong finding(s) in God Classes. Of all the actions in this report, it raises the score most for the work it takes: about 4.2 points for high effort, because it clears the 183 God Classes 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 5.4 out of 10. Code at that level is slower to change than clean code, and we estimate the extra work at 7% to 15% on every change. The history of the code shows how much it changes: about 38,650 lines over the last 90 days, which is about 156,747 lines a year. At that pace, the extra work comes to an estimated 25.7 to 154.3 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 · the code's change history
What to do: Start with the files listed under Churn × Complexity Hotspots, which change often and are hard to read, because that is where the extra work is paid most often.

Architecture: which parts of the code depend on which

The code is divided into modules, groups of code that each handle one part of the product, and a module depends on another when it uses code from it. The table lists the modules both down the side and across the top, in an order where each module should only use modules listed above it. A number in a cell means the module on that row uses the module in that column, and it counts the pairs of building blocks (types) that connect them. The one thing to look for is a mark above the diagonal line. It means two or more modules use each other in a loop (a dependency cycle), so none of them can be changed, tested or released on its own.

605 modules, with 62 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; 565 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 components.illustrations.IllustrationMultiPlatform2 components.public_witnessing_card.public_witnessing_card_types3 components.table.index_types4 components.tabs.index_types5 definition.app6 definition.assignment7 definition.branch_report8 definition.cong_field_service_reports9 definition.meeting_attendance10 definition.notification11 definition.schedules12 definition.settings13 definition.sources14 definition.upcoming_events15 definition.user_field_service_reports16 definition.week_type17 features.congregation.app_access.user_add.person_select.index_types18 features.congregation.settings.circuit_overseer.useCircuitOverseer19 features.congregation.settings.circuit_overseer.weeks_list20 features.persons.import_export.import.index_types21 features.reports.publisher_records.export_S21.index_types22 src23 components.assignments_checklist.assignments_checklist_types24 components.illustrations25 components.info_banner.index_types26 components.public_witnessing_card27 components.public_witnessing_card.view28 components.table.useSorting29 components.tabs30 features.app_notification.notification_item31 features.color_scheme_selector32 features.congregation.app_access.join_requests.accept33 features.congregation.app_access.user_add.person_select34 features.congregation.settings.circuit_overseer35 features.congregation.settings.circuit_overseer.week_item36 features.my_profile.user_profile_details.profile_picture_selector37 features.persons.import_export.confirm_import38 services.app39 utils40 components.table
1 components.illustrations.IllustrationMultiPlatform
2 components.public_witnessing_card.public_witnessing_card_types
3 components.table.index_types
4 components.tabs.index_types
5 definition.app
6 definition.assignment
7 definition.branch_report
8 definition.cong_field_service_reports
9 definition.meeting_attendance
10 definition.notification
11 definition.schedules
12 definition.settings
13 definition.sources
14 definition.upcoming_events
15 definition.user_field_service_reports
16 definition.week_type
17 features.congregation.app_access.user_add.person_select.index_types
18 features.congregation.settings.circuit_overseer.useCircuitOverseer
19 features.congregation.settings.circuit_overseer.weeks_list
20 features.persons.import_export.import.index_types
21 features.reports.publisher_records.export_S21.index_types
22 src1
23 components.assignments_checklist.assignments_checklist_types1
24 components.illustrations1
25 components.info_banner.index_types1
26 components.public_witnessing_card2
27 components.public_witnessing_card.view2
28 components.table.useSorting1
29 components.tabs1
30 features.app_notification.notification_item1
31 features.color_scheme_selector1
32 features.congregation.app_access.join_requests.accept1
33 features.congregation.app_access.user_add.person_select1
34 features.congregation.settings.circuit_overseer1
35 features.congregation.settings.circuit_overseer.week_item1
36 features.my_profile.user_profile_details.profile_picture_selector1
37 features.persons.import_export.confirm_import1
38 services.app2511112
39 utils12
40 components.table21
Uses a module listed above itPart of a loopThe module itself
1 components.illustrations.IllustrationMultiPlatform2 components.public_witnessing_card.public_witnessing_card_types3 components.table.index_types4 components.tabs.index_types5 definition.app6 definition.assignment7 definition.branch_report8 definition.cong_field_service_reports9 definition.meeting_attendance10 definition.notification11 definition.schedules12 definition.settings13 definition.sources14 definition.upcoming_events15 definition.user_field_service_reports16 definition.week_type17 features.congregation.app_access.user_add.person_select.index_types18 features.congregation.settings.circuit_overseer.useCircuitOverseer19 features.congregation.settings.circuit_overseer.weeks_list20 features.persons.import_export.import.index_types21 features.reports.publisher_records.export_S21.index_types22 src23 components.assignments_checklist.assignments_checklist_types24 components.illustrations25 components.info_banner.index_types26 components.public_witnessing_card27 components.public_witnessing_card.view28 components.table.useSorting29 components.tabs30 features.app_notification.notification_item31 features.color_scheme_selector32 features.congregation.app_access.join_requests.accept33 features.congregation.app_access.user_add.person_select34 features.congregation.settings.circuit_overseer35 features.congregation.settings.circuit_overseer.week_item36 features.my_profile.user_profile_details.profile_picture_selector37 features.persons.import_export.confirm_import38 services.app39 utils40 components.tablecomponents.illustrations.IllustrationMultiPlatform1components.public_witnessing_card.public_witnessing_card_types2components.table.index_types3components.tabs.index_types4definition.app5definition.assignment6definition.branch_report7definition.cong_field_service_reports8definition.meeting_attendance9definition.notification10definition.schedules11definition.settings12definition.sources13definition.upcoming_events14definition.user_field_service_reports15definition.week_type16features.congregation.app_access.user_add.person_select.index_types17features.congregation.settings.circuit_overseer.useCircuitOverseer18features.congregation.settings.circuit_overseer.weeks_list19features.persons.import_export.import.index_types20features.reports.publisher_records.export_S21.index_types21src22components.assignments_checklist.assignments_checklist_types23components.illustrations24components.info_banner.index_types25components.public_witnessing_card26components.public_witnessing_card.view27components.table.useSorting28components.tabs29features.app_notification.notification_item30features.color_scheme_selector31features.congregation.app_access.join_requests.accept32features.congregation.app_access.user_add.person_select33features.congregation.settings.circuit_overseer34features.congregation.settings.circuit_overseer.week_item35features.my_profile.user_profile_details.profile_picture_selector36features.persons.import_export.confirm_import37services.app38utils39components.table40111122111111111125111121221+565 more modules (most-connected shown)

At a glance — Code Health · 38.1 · Weak · gated by R10, X5 ·

At a glance — Architecture · 70.1 · Adequate · gated by R9 ·

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

At a glance — Readiness · 48.6 · Weak · gated by R8 ·

At a glance — Security · 61.5 · Adequate · gated by D36, C1 ·

At a glance — Accessibility · 41.0 · Weak · gated by AC2, AC4 ·

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
A03:2025 — Software Supply Chain Failures29High / Critical
A05:2025 — Injection5High / Critical
A07:2025 — Authentication Failures4High / Critical
A01:2025 — Broken Access Control2Medium

Roadmap

Top priorities: Resolve the 183 FunctionTooLong finding(s) in God Classes — start with index.tsx (69), useConfirmImport.tsx (4), schedules.ts (4); 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; Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.

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

Do thisHelpsEffortDimension
Resolve the 183 FunctionTooLong finding(s) in God Classes — start with index.tsx (69), useConfirmImport.tsx (4), schedules.ts (4).+4.2 ptsHighGod Classes
Resolve the 1 Deprecated finding(s) in Dependency Hygiene — start with package.json.+1.9 ptsLowDependency Hygiene
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.+3.7 ptsMediumCode Duplication
Resolve the 1 No assertions finding(s) in Test Quality — start with spec.cy.ts.+1.8 ptsLowTest Quality
Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.+3.2 ptsMediumKeyboard semantics
Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label.+2.9 ptsMediumForms & labels
The findings name the configuration each number was taken from and, for the assertions, the files that hold them. Turn null checking on where it is off — `"strict": true` in the base tsconfig that the others extend switches `strictNullChecks` on with the rest of the family — and then resolve the assertions rather than adding to them. A `!` on a value the checker could show to be null is a promise the author cannot check from where they are standing, and each one is a `TypeError: Cannot read properties of null` waiting for the path that makes it true; where the value genuinely cannot be null, say something the checker can see instead (narrow it with a test, make the property required, drop the `?`).+2.8 ptsMediumNullable reference types
Resolve the 1 No ADRs found finding(s) in ADR Quality — start with package.json.+1.1 ptsLowADR Quality

File quality

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

FileScoreBandWorst signal
REDACTED0.0SlopDependency Vulnerabilities: Critical CVE: REDACTED
REDACTED4.6MixedStatic Analysis (SAST): Medium: REDACTED
src/services/app/assignments_with_stats.ts6.0MixedExplicit Debt: TodoComment
src/services/app/schedules.ts6.3MixedCyclomatic Complexity: schedules.schedulesMidweekInfo (cyclomatic 116)
src/features/meetings/person_selector/brother_selector/useBrotherSelector.tsx6.3MixedCyclomatic Complexity: useBrotherSelector.useBrotherSelector.options (cyclomatic 25)
REDACTED6.4MixedData Compliance (PII/GDPR): Medium: REDACTED
src/utils/dev.ts6.5MixedCyclomatic Complexity: dev.importDummyPersons (cyclomatic 86)
src/services/app/autofill.ts6.5MixedCyclomatic Complexity: autofill.getTasksArray (cyclomatic 21)
src/services/app/persons.ts6.9MixedCyclomatic Complexity: persons.applyGroupFilters (cyclomatic 50)
src/services/worker/backupUtils.ts7.0MixedCyclomatic Complexity: backupUtils.dbExportDataBackup (cyclomatic 85)
src/features/congregation/settings/import_export/confirm_import/useConfirmImport.tsx7.0MixedCyclomatic Complexity: useConfirmImport.useConfirmImport.handleImportData (cyclomatic 37)
src/components/button/index.tsx7.1MixedCyclomatic Complexity: index.Button (cyclomatic 90)
src/services/app/assignment_selection.ts7.1MixedCyclomatic Complexity: assignment_selection.sortCandidatesMultiLevel (cyclomatic 29)
src/features/persons/speakers_catalog/import_export/export/useExportSpeakers.tsx7.1MixedCyclomatic Complexity: useExportSpeakers.useExportSpeakers.getCongregationValue (cyclomatic 37)
src/features/ministry/report/form_S4/hours_credits/useHoursCredits.tsx7.1MixedCyclomatic Complexity: useHoursCredits.useHoursCredits.handleSelectPreset (cyclomatic 20)
src/features/congregation/settings/import_export/confirm_import/useImportHourglass.jsx7.2MixedCyclomatic Complexity: useImportHourglass.useHourglassImport.migrateHourglassPersons (cyclomatic 55)
src/features/meetings/midweek_editor/index.tsx7.2MixedCyclomatic Complexity: index.MidweekEditor (cyclomatic 55)
src/features/meetings/monthly_view/index.tsx7.2MixedCyclomatic Complexity: index.MonthlyView (cyclomatic 50)
src/layouts/navbar/index.tsx7.2MixedCyclomatic Complexity: index.NavBar (cyclomatic 38)
src/features/meetings/weekly_schedules/person_component/usePersonComponent.tsx7.2MixedCyclomatic Complexity: usePersonComponent.usePersonComponent.personData (cyclomatic 33)

How the grades work

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

Critical — 32

A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.

Serious — 718

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

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

Could not be resolved — 10

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 70 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 — 70 dimensions across the health lenses
D1D2D3D10D12D13D14D15D16D17D19D20D24D28D29D30D32D34D35D36D37D43D44AC1AC2AC3AC4AC5AC6AX10AX3AX5AX6AX7C1GD1IC1M1M2M3M4P1P2P3P4P5P6PF3R1R10R11R2R3R4R5R6R7R8R9S1X1X12X16X2X21X24X25X29X3X5

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, 900 of 948 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 · trivySecrets in history, SAST, CVEs, IaC & container, PII / GDPR1.86.0 · 0.69.3✓ deterministic

Every finding is locatable in findings.md. Run 01a1eafd-da6d-7562-8ece-24e0addbdf01.

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: the JavaScript/TypeScript half could not be measured — the JavaScript/TypeScript suite(s) run through a browser-driven runner the coverage collector does not drive — the repository root (cypress) — a gap in the analyzer, not something this repository is missing. Coverage is excluded from the score rather than counted as a near-zero. This is OUR limitation, not a defect in the repo.
  • D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.ts) and the reliability runner does support this ecosystem — it drives jest, vitest, mocha and egg-bin, and Cypress component specs in the analyzer image's own Cypress — but no package script here runs `cypress run --component`, so these Cypress specs run end-to-end: each one visits the application's own running server, which a scan does not start. Re-run without it, every spec would fail every time and read as a perfectly stable suite that measured nothing. the root package declares `cypress` and its `scripts.test` is `npm run cypress:test`. So flakiness couldn't be assessed. Not scored — this is a gap in the analyzer's end-to-end test support (starting the application under test), not a missing .ts runner and not a finding about this repository.
  • D22 Internal API Consistency — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. This repository's source is written only in languages whose packages are published through a manifest, and no manifest in the tree makes a publication act: either there is no package manifest of any ecosystem (no package.json, pyproject.toml, setup.py, gemspec, Cargo.toml, pom.xml, build.gradle, composer.json, pubspec.yaml or mix.exs), or every one present declares in its package manager's own terms that it is not published (an npm package marked "private": true, a Cargo package with publish = false, a pubspec with publish_to: none, a Composer "project", a Poetry project with package-mode = false, or the "Private :: Do Not Upload" classifier). With no publication act there is no intentionally-exposed surface for API consistency to be judged over.
  • D26 Project Cohesion — 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. `(repository root)` (148385 LoC, 1756 module-visible types across 666 directories) is over its size bounds, and whether one unit is a coherent whole or a grab-bag is read from its type references: the parts of it that reach the rest only through its shared core. Those are read over the C#/VB code model, which this unit's source did not supply. Its size alone is no verdict on its cohesion, so none is published.
  • AXB2 Runtime readiness — 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. The dev server kept running but no port it opened served a page in the time allowed. (rule: no-answer). The renderer reported: the dev server (`npm run dev`) kept running but served no page within 2 minutes. Likely cause (not identified): the dev server kept running but no port it opened served a page in the time allowed. Last output: "> organized@3.41.0 dev / > vite / VITE v8.0.16 ready in 645 ms / ➜ Local: http://localhost:4050/ / ➜ Network: http://172.31.7.5:4050/ / 7:32:07 PM [vite] (client) [optimizer] scanning dependencies... / 7:32:12 PM [vite] (client) [optimizer] bundling dependencies..." No runtime evidence was gathered.
  • AXR1 Runtime accessibility — 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. Render strategy: boot via DevServer (dev). the dev server (`npm run dev`) kept running but served no page within 2 minutes. Likely cause (not identified): the dev server kept running but no port it opened served a page in the time allowed. Last output: "> organized@3.41.0 dev / > vite / VITE v8.0.16 ready in 645 ms / ➜ Local: http://localhost:4050/ / ➜ Network: http://172.31.7.5:4050/ / 7:32:07 PM [vite] (client) [optimizer] scanning dependencies... / 7:32:12 PM [vite] (client) [optimizer] bundling dependencies..." No runtime evidence was gathered.
  • C2 Access Controls — 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. 'firebase/app' is imported (src/wrapper/feature_flags/useFeatureFlags.tsx:3), but this repository stands up no server and carries no migration or rules file this check reads, so who may read and write its data could not be decided.
  • P2 Observability — 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. 100 further occurrence(s) are not listed individually; the score already reflects all 140.
  • R10 Code Duplication — 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. 786 further occurrence(s) are not listed individually; the score already reflects all 826.
  • 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. 125 further occurrence(s) are not listed individually; the score already reflects all 165.
  • R7 Dead Code — 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. 160 further occurrence(s) are not listed individually; the score already reflects all 200.
  • X10 Duplicated predicate — 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. 21 further occurrence(s) are not listed individually; the score already reflects all 61.
  • X2 Cancellation propagation — 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. 25 further occurrence(s) are not listed individually; the score already reflects all 65.
  • X4 Structured logging — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Python, PHP, Dart, Ruby, Scala, Rust, Go, Swift, Erlang, F# and Visual Basic source only, and no C# was loaded, and this repository's JavaScript/TypeScript, Python and PHP log through no library that carries a message's values as fields (pino, winston, bunyan, tslog, LogTape, roarr; Python's logging, structlog; PHP's PSR-3 loggers), so its log calls cannot be judged, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X7 Silent fallback defaults — 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. 22 further occurrence(s) are not listed individually; the score already reflects all 62.

Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.

Limitations & what we did not check

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

Per-dimension blind spots

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

  • D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
  • D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
  • D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
  • D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
  • D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
  • D13 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
  • D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
  • D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
  • D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
  • D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
  • D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
  • D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
  • 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.
  • 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.
  • D32 Data Compliance (PII/GDPR): PII/GDPR signals are heuristic pattern matches in code — they flag likely handling concerns, not legal compliance, and cannot trace where data actually flows at runtime.
  • D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
  • D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
  • D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
  • D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
  • 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.
  • AC4 Keyboard semantics: Keyboard semantics are inferred from markup attributes — interactivity wired purely in script, focus managed at runtime, and component-level handlers are invisible. A clean result means "no static keyboard-trap shape", not a keyboard-operability proof.
  • 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.
  • 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

96 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was schedules.schedulesMidweekInfo at 116. A further 2 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being index.Badge at 22 — they are counted neither in the figure above nor in this dimension's score. 2 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: src/components/badge/index.tsx (index.Badge at 22), src/features/reports/field_service/selector_stats/person_filter/index.tsx (index.PersonFilter 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.

schedules.schedulesMidweekInfo (cyclomatic 116)src/services/app/schedules.ts:139
index.Button (cyclomatic 90)src/components/button/index.tsx:10
dev.importDummyPersons (cyclomatic 86)src/utils/dev.ts:67
backupUtils.dbExportDataBackup (cyclomatic 85)src/services/worker/backupUtils.ts:1757
index.WeekendEditor (cyclomatic 68)src/features/meetings/weekend_editor/index.tsx:53

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

What to do

  1. Bring the 5 bodies over 60 down to 60 or less in Cyclomatic Complexity — start with schedules.schedulesMidweekInfo (cyclomatic 116), index.Button (cyclomatic 90), dev.importDummyPersons (cyclomatic 86). — 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 5 together lifts Cyclomatic Complexity from 5.9 to about 6.5/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.

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

D2 · Cognitive Complexity4.9 / 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.9 / 10 · rule-coverage 100% · ceiling Prevented

114 method(s) exceeded the cognitive complexity threshold of 15; the worst was schedules.schedulesMidweekInfo at 283.

index.Button::getBackgroundColorClick (cognitive 34) · ×3src/components/button/index.tsx:153
schedules.schedulesMidweekInfo (cognitive 283)src/services/app/schedules.ts:139
backupUtils.dbExportDataBackup (cognitive 220)src/services/worker/backupUtils.ts:1757
dev.importDummyPersons (cognitive 164)src/utils/dev.ts:67
persons.applyGroupFilters (cognitive 90)src/services/app/persons.ts:544

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

What to do

  1. Bring the 3 bodies over 120 down to 120 or less in Cognitive Complexity — start with schedules.schedulesMidweekInfo (cognitive 283), backupUtils.dbExportDataBackup (cognitive 220), dev.importDummyPersons (cognitive 164). — 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 3 together lifts Cognitive Complexity from 4.9 to about 5.8/10, projected with the scoring formula itself and assuming each lands exactly at 120; a cleaner split scores higher.

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

D3 · God Classes4.2 / 10Weak✓ Tool-verified

What it measures: Over-large classes that try to do too much ("god classes").

Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.

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

202 god class(es) detected.

FunctionTooLong: IllustrationMultiPlatform.IllustrationMultiPlatform · ×183src/components/illustrations/IllustrationMultiPlatform.tsx:6
FileTooLong: illustrations/IllustrationMultiPlatform.tsx · ×15src/components/illustrations/IllustrationMultiPlatform.tsx
ClassTooLong: IllustrationMultiPlatform · ×4src/components/illustrations/IllustrationMultiPlatform.tsx:1

What to do

  1. Resolve the 183 FunctionTooLong finding(s) in God Classes — start with index.tsx (69), useConfirmImport.tsx (4), schedules.ts (4). — One of this dimension's main actionable groups (183 warning-level).
  2. Resolve the 15 FileTooLong finding(s) in God Classes — start with index.tsx (3), IllustrationMultiPlatform.tsx, schedules.ts. — One of this dimension's main actionable groups (15 warning-level).
  3. Resolve the 4 ClassTooLong finding(s) in God Classes — start with IllustrationMultiPlatform.tsx, IllustrationSecretary.tsx, IllustrationOtherSchedules.tsx. — One of this dimension's main actionable groups (4 warning-level).

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

D10 · Test Quality8.1 / 10Strong✓ 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 8.1 / 10 · rule-coverage 100% · ceiling Prevented

0 skipped, 1 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 4 tests.

No assertions: passescypress/e2e/spec.cy.ts:4

What to do

  1. Resolve the 1 No assertions finding(s) in Test Quality — start with spec.cy.ts. — One of this dimension's main actionable groups (1 warning-level).

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

D12 · Dependency Hygiene8.0 / 10Strong✓ Tool-verified

What it measures: Whether dependencies are current, not deprecated, and not bloated. Known vulnerabilities are D30's.

Method: Manifest scan via dotnet list package across all projects; worst-signal-per-package deduction (capped-linear for deprecation, prerelease and outdated) per KLoC. Known-vulnerable packages are D30's and are not charged here (rubric-2026.11.2). Exhaustive.

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

31 outdated direct production npm dependency(ies) of 51 graded, 0 pinning defect(s), across 1 package.json (1 of them the product) and 1 committed lockfile(s). Development dependencies are deliberately not graded for currency: that grade is about what SHIPS. 1 direct dependency(ies) — production, development or optional — are marked DEPRECATED by their publisher (the registry's per-version mark, or the lockfile's copy of it when the registry could not be asked); deprecated transitive packages are listed but not charged. Whether any is UNMAINTAINED is not graded — the registry publishes no maintenance status, and release age does not stand in for one. Whether any is UNUSED is not graded either: that is a source question, and the frontend dependency lens (R8) answers it in this same run. Known CVEs in this dependency graph are D30's question, read from the manifest there.

Deprecated: eslintpackage.json:102
Outdated (npm): @mui/icons-material · ×31

What to do

  1. Resolve the 1 Deprecated finding(s) in Dependency Hygiene — start with package.json. — One of this dimension's main actionable groups (1 warning-level).

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

D13 · REDACTED Scanning10.0 / 10Exemplary○ Nothing flagged

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 10.0 / 10 · rule-coverage 100% · ceiling Prevented

REDACTED scan ran and found no leaked secrets.

✓ On the Gold path — maintain.

Detailed fixes: d13_recommendation.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 436 shipped npm package(s) use a banned license. Licences were resolved from registry.npmjs.org over the 436 package(s) this repository's committed lockfile installs for a consumer — its 51 production, optional and peer dependency(ies), across 1 product package.json manifest(s), and everything those install in turn. Its 42 `devDependencies` declaration(s), and every package only they reach, are excluded: a consumer installs none of them. ★ Each licence is the one the registry publishes for the package's CURRENT release rather than for the pinned version, which is the same caveat the Hex and RubyGems arms carry. Third-party code that ships WITHOUT a manifest entry was read too: 0 component(s) whose licence travels in the tree (vendored or copied-in directories, licence comments preserved in committed bundles, compiled wasm modules) and 0 bundled package(s) named only by a bundle's module path, graded on the registry; 0 use a banned licence. 1 vendored, copied-in or compiled component(s) state no licence this pass can read — missing data, not charged. This repository publishes itself under MIT, which is its own choice and is not judged here.

✓ On the Gold path — maintain.

Detailed fixes: d14_recommendation.md.

D15 · Churn × Complexity Hotspots9.6 / 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.6 / 10 · rule-coverage 100% · ceiling Documented

Top hotspots: src/services/worker/backupUtils.ts (10×85=850); src/services/app/schedules.ts (7×116=812); src/components/button/index.tsx (4×90=360) Repeated repair below the complexity floor: src/components/icon_button/index.tsx (3 of 3 changes were fixes)

Hotspot: src/services/worker/backupUtils.ts · ×23src/services/worker/backupUtils.ts:1757
Repeated repair: src/components/icon_button/index.tsxsrc/components/icon_button/index.tsx:14

What to do

  1. Resolve the 23 Hotspot finding(s) in Churn × Complexity Hotspots — start with index.tsx (16), backupUtils.ts, schedules.ts. — One of this dimension's main actionable groups (23 warning-level).
  2. Resolve the 1 Repeated repair finding(s) in Churn × Complexity Hotspots — start with index.tsx. — One of this dimension's main actionable groups (1 warning-level).

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

D16 · Bus Factor9.3 / 10Exemplary✓ Tool-verified

What it measures: Whether knowledge is concentrated in too few people (the "bus factor").

Method: Living knowledge per author via time-decayed commit attribution (6-month half-life, focus weighting) across largest source files. Deterministic, avoids blame's mechanical-refactor false positives.

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

44 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is src/features/persons/speakers_catalog/import_export/confirm_import/useCSVImport.tsx. Counted over 653 of the 2172 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.

Off-boarding risk: anonymized user #1 · ×3

✓ On the Gold path — maintain.

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

D17 · Explicit Debt10.0 / 10Stronggated by 1 serious finding✓ Tool-verified

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

1 deducted task-comment markers across 147215 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.

TodoCommentsrc/services/app/assignments_with_stats.ts:606

What to do

  1. Resolve the 1 TodoComment finding(s) in Explicit Debt — start with assignments_with_stats.ts. — One of this dimension's main actionable groups (1 warning-level).

Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.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

1 of 1 documentation facets pass in full. 11 document(s) read across 1 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 foundpackage.json:12

What to do

  1. Resolve the 1 No ADRs found finding(s) in ADR Quality — start with package.json. — 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 Value6.4 6.1 / 10Adequate✓ Tool-verified

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 6.1 / 10 · rule-coverage 96% · ceiling Documented

22 of 608 judged comments only repeat the code they sit on (3.6 %). 38 comment(s) in another language or script were not judged.

redundant comment · ×14converter/css/convert.js:94
doc comments repeat the namessrc/components/badge/index.types.ts:101

What to do

  1. Resolve the 14 redundant comment finding(s) in Comment Value — start with index.tsx (3), useBrotherSelector.tsx (2), schedules.ts (2). — One of this dimension's main actionable groups (14 recommendation-level).

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

D28 · Secrets (history)7.0 / 10Adequategated by 3 critical findings✓ 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 7.0 / 10 · rule-coverage 100% · ceiling Documented

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

REDACTED
REDACTED

What to do

  1. Resolve the 3 REDACTED finding(s) in Secrets (history) — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (3 issue-level).
  2. 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)5.4 / 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 5.4 / 10 · rule-coverage 100% · ceiling Documented

5 finding(s): 0 critical, 3 high, 2 medium, 0 low. semgrep hit a parse error in 1 file(s) — `src/services/app/schedules.ts` — so no absence of findings in them is evidence of anything, and nothing in them was analysed. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 2 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.

REDACTED
REDACTED
REDACTED
REDACTED

What to do

  1. Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 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

24 finding(s): 1 critical, 15 high, 6 medium, 2 low.

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

What to do

  1. Resolve the 15 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (15). — One of this dimension's main actionable groups (15 issue-level).
  2. Resolve the 5 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (5). — One of this dimension's main actionable groups (5 warning-level).
  3. Resolve the 1 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).

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

D32 · Data Compliance (PII/GDPR)8.1 / 10Strong✓ Tool-verified

What it measures: Likely personal-data (PII / GDPR) handling concerns — logging or storing data without safeguards.

Method: Heuristic PII/GDPR LEAK scan via semgrep across the repo, using our own ruleset: personal data crossing a boundary it should not — reaching a log/console sink, a URL or query string, or unprotected browser storage. Matches map to severity and a 0-10 wide normalizer. A clean sweep is unscored rather than an unearned 10, and is a statement about the leak paths checked only — this dimension does not inventory the personal data a repository holds (the personal-data map and the C1-C5 compliance cards do that), so it never reports that a repository has no personal-data surface. Reported LOUDLY as a measurement gap if the ruleset is missing from the analyzer image. Exhaustive over the leak paths, advisory-leaning; degrades on parse failure.

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

2 finding(s): 0 critical, 0 high, 2 medium, 0 low.

REDACTED
REDACTED

What to do

  1. Resolve the 1 REDACTED finding(s) in Data Compliance (PII/GDPR) — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
  2. Resolve the 1 REDACTED finding(s) in Data Compliance (PII/GDPR) — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).

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

D34 · Knowledge Freshness9.9 / 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 9.9 / 10 · rule-coverage 100% · ceiling Documented

8 of 653 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is src/components/icons/IconDistance.tsx. Counted over 653 of the 2172 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.

Orphaned file · ×8src/components/icons/IconDistance.tsx:1
Orphaned files with no living knowledge

✓ On the Gold path — maintain.

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

D35 · Change Coupling10.0 / 10Adequategated by 1 critical finding✓ 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

Strongest change-coupling: useLanguage.tsx↔app.ts 50%

Boundary-crossing change coupling: useLanguage.tsx ↔ app.tssrc/features/language_switcher/useLanguage.tsx:1

What to do

  1. Resolve the 1 Boundary-crossing change coupling finding(s) in Change Coupling — start with useLanguage.tsx. — One of this dimension's main actionable groups (1 issue-level).

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

D36 · Supply-chain Provenance & Signing2.5 / 10Weak✓ Tool-verified

What it measures: Whether the build pipeline provides supply-chain integrity — generated provenance/attestation, signed artifacts (cosign/sigstore), an SBOM, and pinned build actions. Presence of the configuration, not a runtime guarantee.

Method: Supply-chain provenance/signing read deterministically from CI/build config (.github/workflows, .gitlab-ci.yml, azure-pipelines, Jenkinsfile, .circleci) + the release surface: four signals — generated provenance/attestation (SLSA/in-toto/actions-attest), artifact signing (cosign/sigstore/gitsign), an SBOM (syft/sbom-action/*.spdx.json/*.cdx.json), and SHA-pinned build actions — scored 10·present/denom. NotApplicable without a build pipeline. Detects configuration presence, not runtime enforcement.

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

1/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

What to do

  1. Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
  2. Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
  3. Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).

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

D37 · Vulnerability-disclosure Policy10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether the repository publishes a coordinated-vulnerability-disclosure policy (SECURITY.md or security.txt) with a reporting contact, so finders know how to report a vulnerability. Presence of a policy file with a contact, not whether the policy is adequate or honoured.

Method: Vulnerability-disclosure policy read deterministically from the repo: a SECURITY.md (root/.github/docs) or .well-known/security.txt / security.txt, regex-checked for a reporting contact (email / URL / mailto). Present + contact → 10; present without a contact → 4; NotApplicable when no policy file exists (it may live off-repo). Detects the policy file's presence + contact, not its adequacy.

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

A vulnerability-disclosure policy (SECURITY.md) is published with a reporting contact.

✓ On the Gold path — maintain.

Detailed fixes: d37_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 1 platform declaration(s) and 51 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 alternatives10.0 / 10Exemplary○ Nothing flagged

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.

AC2 · Forms & labels1.6 / 10Critical✓ Tool-verified

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.

  • This UI-library field component has no label / aria-label / aria-labelledby / id at this call site, and nothing written inside it here carries one either (a name prop is the form-submission key, not a label; an id, even one the component sets on what it renders, names nothing until a label points at it) — so it likely renders an unlabelled control. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed. (×27) — src/components/switch_with_label/index.tsx:16, src/components/theme_switch/index.tsx:50, src/features/app_start/vip/email_sent/index.tsx:96, …
  • This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed. (×5) — src/components/timefield/index.tsx:10, src/features/congregation/settings/congregation_privacy/delete_congregation/index.tsx:33, src/features/ministry/report/form_S4/comments/index.tsx:12, …
  • This UI-library field component has no label / aria-label / aria-labelledby / id, and nothing written inside it here carries one either (a name prop is the form-submission key, not a label; an id alone, wherever it is set, names nothing until a label points at it). The text inside it does not stand in for one: these compound APIs render a trigger with role="combobox" (or role="button"), and those roles take their name from the AUTHOR, not from their content — so the words on screen never reach the accessibility tree as a name. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed. (×3) — src/features/language_group_selector/index.tsx:27, src/features/meetings/weekend_editor/song_selector/index.tsx:54, src/features/reports/field_service/selector_stats/person_filter/index.tsx:22

What to do

  • Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label.
AC3 · Page structure4.3 / 10Weak✓ Tool-verified

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

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

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

  • No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. — index.html:2
  • user-scalable=no/0 or a maximum-scale below 2 stops low-vision users zooming to 200%. Remove the zoom restriction from the viewport meta. — index.html:16

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.
AC4 · Keyboard semantics1.0 / 10Critical✓ Tool-verified

Other · Accessibility — Whether interactive behaviour is keyboard-reachable — no click handler on a non-interactive element lacking a role, tabindex and key handler, no element the repo's own CSS styles `cursor: pointer` without giving it any of the three, no unfocusable element whose only binding is a mouse enter/leave pair or a double-click, no positive tabindex, no href-less anchor, no placeholder-href (#/javascript) link acting as a button. Static markup readiness, not a WCAG conformance claim.

Method: Static markup-model scan: click handlers on non-interactive elements lacking role+tabindex+key handler, positive tabindex values, and href-less anchors. Components skipped, spreads suppressed. Deterministic, hard fact per element.

Coverage: Population: elements that pose a keyboard-semantics question, in the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx) — a non-natively-interactive element carrying a click handler, a double-click or hover enter/leave binding, a pointer-only gesture on a tabindex="0" element, or `cursor: pointer` from the repo's own CSS; an href-less or placeholder-href (#, javascript:) anchor; and any element with a positive tabindex. Natively interactive elements used correctly (<button>, <a href>, form controls) are NOT in the population — there is nothing to judge — so a page of nothing but correct controls gives AC4 nothing to measure. Keyboard reachability is judged from the markup, never from a rendered page. ★ An interactive element declared in a tagged-template (html`…`) or hyperscript frontend is NOT in this population — no producer reads either — so an empty population is reported as an analyzer gap, never as "this repository has no interactive elements".

  • A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler. — src/components/time_picker_slider/TimeUnit.tsx:27

What to do

  • Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
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 safety7.8 / 10Strong✓ Tool-verified

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.

  • `noscript .variant-main` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — index.html:415
  • `current.animate()` moves (`Web Animations API keyframes`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — src/features/reports/meeting_attendance/monthly_record/clicker_mode/animated_count/index.tsx:181

What to do

  • Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
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.

AX5 · Architecture & structure10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether the codebase has a recognisable, scale-appropriate structure (a named architectural style, or modular enough for its size) rather than being an ad-hoc ball of mud.

Method: Roslyn plus csproj analysis: architecture style detection (DDD, clean, vertical-slice, CQRS) and structure fitness for repo size. 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.

AX7 · Slice cohesion6.5 / 10Adequate✓ Tool-verified

Other · Architecture — Whether feature slices stay independent (no direct cross-slice references) — the discipline that makes vertical-slice architecture pay off.

Method: Roslyn scan (vertical-slice gated): feature slices resolved from namespaces (.Features.*, .Slices.*) or project names; cross-slice type references detected. Deterministic, traceable.

  • `useBasicInfo` (slice 'persons') depends on `UsersOption` from slice 'congregation'. — src/features/persons/basic_info/useBasicInfo.tsx:33

What to do

  • Keep slices independent: share cross-slice needs via an explicit contract/shared-kernel, not direct references between slices.
C1 · Data Protection3.5 / 10Weak✓ Tool-verified

Other · Security — Whether sensitive data is encrypted at rest and in transit and keys are vaulted.

Method: Roslyn plus filesystem scan: encryption presence (EF ColumnEncryption, key-vault references, HTTPS enforcement) and key-derivation KDF detection. Deterministic.

What to do

  • Strengthen data-at-rest protection: vault your keys (AWS KMS / Secrets Manager, Azure Key Vault, GCP KMS / REDACTED Manager, HashiCorp Vault) and encrypt the most sensitive columns (typeorm-encrypted, prisma-field-encryption, mongoose-field-encryption or MongoDB CSFLE) — partial coverage still leaves gaps.
  • Enforce HTTPS (serve through https.createServer / NestJS httpsOptions, or redirect plain HTTP with express-sslify behind your TLS terminator) so data in transit is always encrypted.
GD1 · Unfinished & placeholder code10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Unreviewed-generation residue in this repository's JavaScript/TypeScript: functions whose whole body still throws a "not implemented" error, and placeholder text (lorem ipsum, changeme/replace_me…) left in strings and JSX 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 & stubs9.0 / 10Strong✓ Tool-verified

Other · Code Health — Unfinished work detected by code SHAPE, not keywords, in this repository's JavaScript/TypeScript: functions that only throw a "not implemented" error, functions that take inputs and return a constant or do nothing, async functions that never await, 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.

  • The guard above `return true;` also returns `true`, so no input can make it matter. Implement the distinction that was intended, or delete the guard. — src/features/reports/publisher_records_details/month_item/useMonthItem.tsx:188

What to do

  • Remove the dead code that looks live: delete dead if(false) branches, which read as logic that runs, and either do the real async work or drop the async keyword from fake-async functions, which promise work they never wait for.
M1 · Documentation (README)6.7 / 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

  • 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 gates10.0 / 10Exemplary○ Nothing flagged

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.

P2 · Observability7.0 / 10Strong✓ 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.

  • `unused-i18n-keys.ts` reports through `console.*` at line 47 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — unused-i18n-keys.ts:47
  • `src/views/meetings/weekend/outgoing_speakers_schedule/index.tsx` reports through `console.*` at line 15 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — src/views/meetings/weekend/outgoing_speakers_schedule/index.tsx:15
  • `src/utils/dev.ts` reports through `console.*` at line 713 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — src/utils/dev.ts:713
  • `src/utils/privileges.ts` reports through `console.*` at line 32 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — src/utils/privileges.ts:32
  • `src/utils/privileges.ts` reports through `console.*` at line 50 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — src/utils/privileges.ts:50
  • `src/utils/privileges.ts` reports through `console.*` at line 55 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — src/utils/privileges.ts:55
  • `src/utils/spiritual_status.ts` reports through `console.*` at line 78 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — src/utils/spiritual_status.ts:78
  • `src/utils/spiritual_status.ts` reports through `console.*` at line 238 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — src/utils/spiritual_status.ts:238
  • `src/services/worker/backupAction.ts` reports through `console.*` at line 166 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — src/services/worker/backupAction.ts:166
  • `src/services/worker/backupUtils.ts` reports through `console.*` at line 2399 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — src/services/worker/backupUtils.ts:2399
  • `src/services/dexie/cong_field_service_reports.ts` reports through `console.*` at line 225 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — src/services/dexie/cong_field_service_reports.ts:225
  • `src/services/dexie/metadata.ts` reports through `console.*` at line 34 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — src/services/dexie/metadata.ts:34
  • `src/services/dexie/metadata.ts` reports through `console.*` at line 79 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — src/services/dexie/metadata.ts:79
  • `src/services/dexie/visiting_speakers.ts` reports through `console.*` at line 88 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — src/services/dexie/visiting_speakers.ts:88
  • `src/services/dexie/visiting_speakers.ts` reports through `console.*` at line 114 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — src/services/dexie/visiting_speakers.ts:114
  • `src/services/dexie/visiting_speakers.ts` reports through `console.*` at line 152 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — src/services/dexie/visiting_speakers.ts:152
  • `src/services/dexie/visiting_speakers.ts` reports through `console.*` at line 176 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — src/services/dexie/visiting_speakers.ts:176
  • `src/services/app/meeting_attendance.ts` reports through `console.*` at line 128 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — src/services/app/meeting_attendance.ts:128
  • `src/pages/dashboard/meeting_materials/useMeetingMaterials.tsx` reports through `console.*` at line 43 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — src/pages/dashboard/meeting_materials/useMeetingMaterials.tsx:43
  • `src/pages/activities/upcoming_events/useUpcomingEvents.tsx` reports through `console.*` at line 66 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — src/pages/activities/upcoming_events/useUpcomingEvents.tsx:66
  • `src/hooks/useConsoleWarning.tsx` reports through `console.*` at line 23 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — src/hooks/useConsoleWarning.tsx:23
  • `src/hooks/useConsoleWarning.tsx` reports through `console.*` at line 24 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — src/hooks/useConsoleWarning.tsx:24
  • `src/hooks/useFirebaseAuth.tsx` reports through `console.*` at line 51 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — src/hooks/useFirebaseAuth.tsx:51
  • `src/hooks/useUserAutoLogin.tsx` reports through `console.*` at line 215 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — src/hooks/useUserAutoLogin.tsx:215
  • `src/hooks/useUserAutoLogin.tsx` reports through `console.*` at line 300 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — src/hooks/useUserAutoLogin.tsx:300
  • `src/features/reports/publisher_records_details/report_details/useReportDetails.tsx` reports through `console.*` at line 140 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — src/features/reports/publisher_records_details/report_details/useReportDetails.tsx:140
  • `src/features/reports/publisher_records_details/export_S21/useExportS21.tsx` reports through `console.*` at line 59 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — src/features/reports/publisher_records_details/export_S21/useExportS21.tsx:59
  • `src/features/reports/meeting_attendance/export_S88/useExportS88.tsx` reports through `console.*` at line 202 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — src/features/reports/meeting_attendance/export_S88/useExportS88.tsx:202
  • `src/features/reports/hooks/useReportMonthly.tsx` reports through `console.*` at line 28 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — src/features/reports/hooks/useReportMonthly.tsx:28
  • `src/features/reports/hooks/useReportYearly.tsx` reports through `console.*` at line 24 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — src/features/reports/hooks/useReportYearly.tsx:24
  • `src/features/reports/field_service/report_details/useReportDetails.tsx` reports through `console.*` at line 165 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — src/features/reports/field_service/report_details/useReportDetails.tsx:165
  • `src/features/reports/field_service/report_details/useReportDetails.tsx` reports through `console.*` at line 183 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — src/features/reports/field_service/report_details/useReportDetails.tsx:183
  • `src/features/reports/field_service/report_details/useReportDetails.tsx` reports through `console.*` at line 225 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — src/features/reports/field_service/report_details/useReportDetails.tsx:225
  • `src/features/reports/field_service/report_details/useReportDetails.tsx` reports through `console.*` at line 243 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — src/features/reports/field_service/report_details/useReportDetails.tsx:243
  • `src/features/reports/field_service/report_details/late_report/useLateReport.tsx` reports through `console.*` at line 89 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — src/features/reports/field_service/report_details/late_report/useLateReport.tsx:89
  • `src/features/reports/branch_office/withdraw_report/useWithdrawReport.tsx` reports through `console.*` at line 79 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — src/features/reports/branch_office/withdraw_report/useWithdrawReport.tsx:79
  • `src/features/reports/branch_office/submit_report/useSubmitReport.tsx` reports through `console.*` at line 136 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — src/features/reports/branch_office/submit_report/useSubmitReport.tsx:136
  • `src/features/reports/branch_office/report_section/useReportSection.tsx` reports through `console.*` at line 237 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — src/features/reports/branch_office/report_section/useReportSection.tsx:237
  • `src/features/persons/speakers_catalog/speaker_row_edit/useSpeakerRowEdit.tsx` reports through `console.*` at line 40 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — src/features/persons/speakers_catalog/speaker_row_edit/useSpeakerRowEdit.tsx:40
  • `src/features/persons/speakers_catalog/speaker_edit_popup/useSpeakerEditPopup.tsx` reports through `console.*` at line 444 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — src/features/persons/speakers_catalog/speaker_edit_popup/useSpeakerEditPopup.tsx:444

What to do

  • Route service-code `console.*` output through the module's structured logger (with named fields), so delivery outcomes and failures reach the log pipeline with a level.
  • Add a health-check endpoint (@godaddy/terminus or a /health route) so orchestrators and load balancers can probe liveness/readiness.
P3 · Security & performance tooling7.0 / 10Strong✓ 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.

What to do

  • Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback10.0 / 10Exemplary✓ 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.

P5 · DR & Backup4.0 / 10Weak✓ 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.

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 Safety10.0 / 10Exemplary✓ 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.

R10 · Code Duplication0.0 / 10Critical✓ 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.

  • 268 duplicated blocks under src/features/ have copies in at least two of the sibling directories about, activities, app_feedback, app_notification, app_start, color_scheme_selector (+15 more sibling(s) not listed) — 137 of them are reported below, and 131 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 268 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 268 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 268 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — src/features/persons/spiritual_status/first_report/useFirstReport.tsx:21
  • 114 duplicated blocks under src/ have copies in at least two of the sibling directories components, features, hooks, layouts, pages, services (+4 more sibling(s) not listed) — 70 of them are reported below, and 44 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 114 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 114 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 114 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — src/features/activities/upcoming_events/decorations_for_event.tsx:19
  • 47 duplicated blocks under src/features/meetings/ have copies in at least two of the sibling directories assignments_delete, assignments_history, assignments_week_delete, event_editor, meeting_part, midweek_editor (+18 more sibling(s) not listed) — 28 of them are reported below, and 19 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 47 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 47 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 47 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — src/features/meetings/schedule_range_selector/useScheduleRangeSelector.tsx:21
  • 46 duplicated blocks under src/features/persons/ have copies in at least two of the sibling directories app_user_profile, applications, assignments, assignments_history, basic_info, button_actions (+15 more sibling(s) not listed) — 32 of them are reported below, and 14 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 46 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 46 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 46 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — src/features/persons/import_export/confirm_import/index.tsx:1
  • 20 duplicated blocks under src/features/congregation/settings/ have copies in at least two of the sibling directories circuit_overseer, congregation_basic, congregation_privacy, first_day_week, import_export, language_groups (+2 more sibling(s) not listed) — 8 of them are reported below, and 12 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 20 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 20 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 20 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — src/features/congregation/settings/first_day_week/useFirstDayWeek.ts:12
  • 20 duplicated blocks under src/features/reports/ have copies in at least two of the sibling directories branch_office, field_service, hooks, meeting_attendance, publisher_records, publisher_records_details (+1 more sibling(s) not listed) — 9 of them are reported below, and 11 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 20 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 20 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 20 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — src/features/reports/field_service/report_details/useReportDetails.tsx:41
  • 15 duplicated blocks under src/pages/ have copies in at least two of the sibling directories activities, congregation, meeting_materials, meetings, ministry, my_profile (+2 more sibling(s) not listed) — 12 of them are reported below, and 3 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 15 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 15 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 15 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — src/pages/activities/upcoming_events/index.tsx:18
  • 14 duplicated blocks under src/features/app_start/vip/ have copies in at least two of the sibling directories congregation_create, congregation_encryption, email_link_authentication, email_sent, hooks, oauth (+3 more sibling(s) not listed) — 9 of them are reported below, and 5 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 14 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 14 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 14 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — src/features/app_start/vip/email_link_authentication/useEmailLinkAuth.tsx:41
  • 13 duplicated blocks under src/features/meetings/person_selector/ have copies in at least two of the sibling directories brother_selector, circuit_overseer, outgoing_speaker, stream_speaker, student_selector, visiting_speaker — 12 of them are reported below, and 1 is counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 13 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 13 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 13 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — src/features/meetings/person_selector/brother_selector/index.tsx:48
  • 11 duplicated blocks under src/features/congregation/ have copies in at least two of the sibling directories app_access, field_service_groups, settings — 5 of them are reported below, and 6 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 11 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 11 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 11 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — src/features/congregation/app_access/join_requests/item/useJoinRequest.tsx:94
  • 11 of the duplicated blocks reported below have copies in at least two of the sibling directories bible_studies, comments, hours_credits, hours_fields, ministry_shared, submit_report (+1 more sibling(s) not listed) under src/features/ministry/report/form_S4/. That concentration is one structural fact, not 11 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 11 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — src/features/ministry/report/form_S4/hours_credits/useHoursCredits.tsx:36
  • 10 duplicated blocks under src/features/congregation/app_access/user_details/ have copies in at least two of the sibling directories delete_user, invitation_code, profile_settings, user_additional_rights, user_main_roles, user_rights (+1 more sibling(s) not listed) — 7 of them are reported below, and 3 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 10 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 10 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 10 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — src/features/congregation/app_access/user_details/user_additional_rights/useUserAdditionalRights.tsx:120
  • 10 duplicated blocks under src/features/meetings/weekly_schedules/ have copies in at least two of the sibling directories midweek_container, midweek_meeting, outgoing_talks, weekend_container, weekend_meeting — 9 of them are reported below, and 1 is counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 10 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 10 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 10 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — src/features/meetings/weekly_schedules/midweek_meeting/useMidweekMeeting.tsx:58
  • 9 duplicated blocks under src/features/persons/speakers_catalog/ have copies in at least two of the sibling directories my_congregation, other_congregations, speaker_details, speaker_edit_popup, speaker_row_edit, speaker_row_view — 5 of them are reported below, and 4 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 9 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 9 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 9 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — src/features/persons/speakers_catalog/my_congregation/speakers_local/useSpeakersLocal.tsx:33
  • 8 duplicated blocks under src/features/reports/publisher_records_details/report_details/ have copies in at least two of the sibling directories bible_studies, comments, credit_field, hours_field, late_report, ministry_shared — 6 of them are reported below, and 2 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 8 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 8 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 8 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — src/features/reports/publisher_records_details/report_details/comments/useComments.tsx:6
  • 8 duplicated blocks under src/services/ have copies in at least two of the sibling directories api, app, dexie, encryption, worker — 6 of them are reported below, and 2 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 8 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 8 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 8 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — src/services/app/persons.ts:866
  • 6 duplicated blocks under src/components/ have copies in at least two of the sibling directories autocomplete, autocomplete_multiple, date_picker, minus_button, plus_button, scrollable_tabs (+2 more sibling(s) not listed) — 3 of them are reported below, and 3 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 6 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 6 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 6 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — src/components/minus_button/index.tsx:19
  • 6 of the duplicated blocks reported below have copies in at least two of the sibling directories congregation_access_code, congregation_details, congregation_master_key under src/features/app_start/vip/congregation_create/. That concentration is one structural fact, not 6 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 6 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — src/features/app_start/vip/congregation_create/congregation_access_code/index.tsx:68
  • 6 duplicated blocks under src/features/congregation/settings/congregation_privacy/ have copies in at least two of the sibling directories access_code_change, access_code_view, data_sharing, master_key_change, master_key_view, time_away_visibility — 4 of them are reported below, and 2 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 6 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 6 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 6 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — src/features/congregation/settings/congregation_privacy/access_code_change/useAccessCodeChange.tsx:14
  • 6 duplicated blocks under src/features/congregation/settings/meeting_settings/ have copies in at least two of the sibling directories midweek, weekend — 4 of them are reported below, and 2 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 6 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 6 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 6 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — src/features/congregation/settings/meeting_settings/midweek/day_time/useDayTime.tsx:13
  • 6 of the duplicated blocks reported below have copies in at least two of the sibling directories living_part, ministry_part, treasures_part under src/features/meetings/weekly_schedules/midweek_meeting/. That concentration is one structural fact, not 6 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 6 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — src/features/meetings/weekly_schedules/midweek_meeting/ministry_part/part_row/usePartRow.tsx:49
  • 5 duplicated blocks under src/features/congregation/settings/meeting_forms/ have copies in at least two of the sibling directories date_format, display_name, midweek_exact_date, name_format, songs_weekend — 0 of them are reported below, and 5 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 5 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 5 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 5 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — src/features/congregation/settings/meeting_forms/date_format/useDateFormat.tsx:30
  • 5 duplicated blocks under src/features/my_profile/ have copies in at least two of the sibling directories app_settings, ministry_preferences, security, sessions, user_profile_details — 4 of them are reported below, and 1 is counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 5 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 5 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 5 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — src/features/my_profile/security/mfaDisable/useMFADisable.tsx:26
  • 5 of the duplicated blocks reported below have copies in at least two of the sibling directories baptized_publisher, history, midweek_meeting_student, unbaptized_publisher under src/features/persons/spiritual_status/. That concentration is one structural fact, not 5 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 5 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — src/features/persons/spiritual_status/baptized_publisher/useBaptizedPublisher.tsx:17
  • 5 duplicated blocks under src/views/meetings/midweek/S140/ have copies in at least two of the sibling directories app_normal, default — 4 of them are reported below, and 1 is counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 5 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 5 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 5 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — src/views/meetings/midweek/S140/app_normal/S140AYF.tsx:13
  • src/utils/dev.ts:154 · src/utils/dev.ts:364 — the two spans are one implementation copied and then locally edited — 779 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. — src/utils/dev.ts:154
  • src/features/persons/spiritual_status/baptized_publisher/useBaptizedPublisher.tsx:17 · src/features/persons/spiritual_status/unbaptized_publisher/useUnbaptizedPublisher.tsx:15 — the two spans are one implementation copied and then locally edited — 888 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. — src/features/persons/spiritual_status/baptized_publisher/useBaptizedPublisher.tsx:17
  • src/features/reports/hooks/useReportMonthly.tsx:16 · src/features/reports/hooks/useReportYearly.tsx:12 — the two spans are one implementation copied and then locally edited — 638 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. — src/features/reports/hooks/useReportMonthly.tsx:16
  • src/features/ministry/report/form_S4/hours_credits/useHoursCredits.tsx:36 · src/features/ministry/report/form_S4/hours_fields/useHoursFields.tsx:67 — the two spans are one implementation copied and then locally edited — 771 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. — src/features/ministry/report/form_S4/hours_credits/useHoursCredits.tsx:36
  • src/features/meetings/person_selector/brother_selector/index.tsx:48 · src/features/meetings/person_selector/student_selector/index.tsx:65 — the two spans are one implementation copied and then locally edited — 527 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. — src/features/meetings/person_selector/brother_selector/index.tsx:48
  • src/features/app_start/vip/congregation_create/congregation_access_code/index.tsx:68 · src/features/app_start/vip/congregation_create/congregation_master_key/index.tsx:82 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — src/features/app_start/vip/congregation_create/congregation_access_code/index.tsx:68
  • src/features/persons/import_export/confirm_import/index.tsx:1 · src/features/persons/speakers_catalog/import_export/confirm_import/index.tsx:2 — these 2 files are line-for-line copies of one another — 104 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — src/features/persons/import_export/confirm_import/index.tsx:1
  • src/features/persons/assignments/useAssignments.tsx:106 · src/features/persons/filter/useFilter.tsx:26 — the 2 copies are spread across 2 files, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases. — src/features/persons/assignments/useAssignments.tsx:106
  • src/features/app_start/vip/congregation_encryption/congregation_access_code/index.tsx:12 · src/features/app_start/vip/congregation_encryption/congregation_master_key/index.tsx:12 — 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. — src/features/app_start/vip/congregation_encryption/congregation_access_code/index.tsx:12
  • src/features/persons/import_export/confirm_import/useConfirmImport.tsx:46 · src/features/persons/speakers_catalog/import_export/confirm_import/useConfirmImport.tsx:67 — the two spans are one implementation copied and then locally edited — 656 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. — src/features/persons/import_export/confirm_import/useConfirmImport.tsx:46
  • src/features/congregation/settings/congregation_privacy/access_code_change/useAccessCodeChange.tsx:14 · src/features/congregation/settings/congregation_privacy/master_key_change/useMasterKeyChange.tsx:14 — 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. — src/features/congregation/settings/congregation_privacy/access_code_change/useAccessCodeChange.tsx:14
  • src/features/meetings/person_selector/brother_selector/useBrotherSelector.tsx:281 · src/features/meetings/person_selector/student_selector/useStudentSelector.tsx:288 — the two spans are one implementation copied and then locally edited — 469 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. — src/features/meetings/person_selector/brother_selector/useBrotherSelector.tsx:281
  • src/features/persons/import_export/index.tsx:59 · src/features/persons/speakers_catalog/import_export/index.tsx:53 — 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. — src/features/persons/import_export/index.tsx:59
  • src/features/meetings/person_selector/outgoing_speaker/index.tsx:26 · src/features/meetings/person_selector/visiting_speaker/index.tsx:39 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — src/features/meetings/person_selector/outgoing_speaker/index.tsx:26
  • src/features/persons/speakers_catalog/other_congregations/congregation_info/view/index.tsx:142 · src/features/persons/speakers_catalog/other_congregations/congregation_info/view/index.tsx:218 — 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. — src/features/persons/speakers_catalog/other_congregations/congregation_info/view/index.tsx:142

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.
R11 · Import Boundaries9.9 / 10Exemplary✓ Tool-verified

React / JS · Architecture — Conformance to the detected frontend architecture layout (feature-sliced / layered src) plus cross-package deep-import rules (D-386).

Method: Conformance to the detected frontend layout (feature-sliced / layered src) plus cross-package deep-import rules, over the module graph. Deterministic.

  • src/components/date_picker/index.styles.ts:7 imports @mui/x-date-pickers/internals, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — src/components/date_picker/index.styles.ts:7
  • src/services/validator/index.ts:1 imports validator/lib/isEmail, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — src/services/validator/index.ts:1

What to do

  • Fix the listed violations: import through public entries (package exports / slice index), never reach into another layer or package's internals.
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.

  • schedulesMidweekInfo has cyclomatic complexity 121 and cognitive complexity 289; 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. — src/services/app/schedules.ts:139
  • importDummyPersons has cyclomatic complexity 89 and cognitive complexity 171; 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. — src/utils/dev.ts:67
  • dbExportDataBackup has cyclomatic complexity 86 and cognitive complexity 221; 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. — src/services/worker/backupUtils.ts:1757
  • WeekendEditor has cyclomatic complexity 68 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 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. — src/features/meetings/weekend_editor/index.tsx:53
  • schedulesMidweekData has cyclomatic complexity 55 and cognitive complexity 92; 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. — src/services/app/schedules.ts:2047
  • MidweekEditor has cyclomatic complexity 55 and cognitive complexity 52; 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. — src/features/meetings/midweek_editor/index.tsx:58
  • applyGroupFilters has cyclomatic complexity 50 and cognitive complexity 90; 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. — src/services/app/persons.ts:544
  • (anonymous) has cyclomatic complexity 50 and cognitive complexity 58; 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. — src/features/congregation/settings/import_export/confirm_import/useImportHourglass.jsx:28
  • TextField has cyclomatic complexity 46 and cognitive complexity 43; 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. — src/components/textfield/index.tsx:16
  • Button has cyclomatic complexity 42 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 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. — src/components/button/index.tsx:10
  • schedulesGetHistoryDetails has cyclomatic complexity 41 and cognitive complexity 58; 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. — src/services/app/schedules.ts:854
  • (anonymous) has cyclomatic complexity 39 and cognitive complexity 75; 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. — src/features/meetings/meeting_part/useMeetingPart.tsx:189
  • NavBar has cyclomatic complexity 38 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 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. — src/layouts/navbar/index.tsx:60
  • schedulesWeekendData has cyclomatic complexity 37 and cognitive complexity 54; 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. — src/services/app/schedules.ts:2497
  • handleImportData has cyclomatic complexity 37 and cognitive complexity 39; 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. — src/features/congregation/settings/import_export/confirm_import/useConfirmImport.tsx:520
  • (anonymous) has cyclomatic complexity 37 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. — src/features/persons/speakers_catalog/import_export/export/useExportSpeakers.tsx:142
  • schedulesWeekendInfo has cyclomatic complexity 36 and cognitive complexity 56; 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. — src/services/app/schedules.ts:602
  • (anonymous) has cyclomatic complexity 32 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. — src/features/meetings/weekly_schedules/person_component/usePersonComponent.tsx:62
  • (anonymous) has cyclomatic complexity 32 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. — src/features/app_start/vip/startup/useStartup.tsx:72
  • getBadges has cyclomatic complexity 28 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. — src/features/persons/hooks/usePerson.tsx:195
  • EditUpcomingEvent has cyclomatic complexity 27 and cognitive complexity 24; 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. — src/features/activities/upcoming_events/edit_upcoming_event/index.tsx:24
  • MidweekMeeting has cyclomatic complexity 26 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. — src/features/meetings/weekly_schedules/midweek_meeting/index.tsx:27
  • (anonymous) has cyclomatic complexity 25 and cognitive complexity 62; 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. — src/services/worker/backupUtils.ts:161
  • runBackup has cyclomatic complexity 25 and cognitive complexity 47; 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. — src/services/worker/backupAction.ts:36
  • (anonymous) has cyclomatic complexity 25 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. — src/features/persons/list/person_card/usePersonCard.tsx:36
  • (anonymous) has cyclomatic complexity 24 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. (×2) — src/features/congregation/settings/import_export/confirm_import/useConfirmImport.tsx:351, src/views/meetings/midweek/S140/app_normal/index.tsx:37
  • (anonymous) has cyclomatic complexity 23 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. — src/features/meetings/person_selector/brother_selector/useBrotherSelector.tsx:311
  • dbGetMetadata has cyclomatic complexity 23 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 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. — src/services/worker/backupUtils.ts:332
  • Badge has cyclomatic complexity 22 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 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. — src/components/badge/index.tsx:109
  • (anonymous) has cyclomatic complexity 22 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. — src/views/meetings/midweek/S140/default/index.tsx:36
  • RootLayout 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. — src/layouts/root_layout/index.tsx:32
  • schedulesS89Data has cyclomatic complexity 21 and cognitive complexity 43; 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. — src/services/app/schedules.ts:1791
  • handleLoginData has cyclomatic complexity 21 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. — src/hooks/useUserAutoLogin.tsx:98
  • dbRestoreSettings has cyclomatic complexity 21 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. — src/services/worker/backupUtils.ts:663
  • sourcesPartTiming has cyclomatic complexity 21 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:493
  • LivingPart has cyclomatic complexity 21 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. — src/features/meetings/weekly_schedules/midweek_meeting/living_part/index.tsx:23
  • Checkbox has cyclomatic complexity 21 and cognitive complexity 19; 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. — src/components/checkbox/index.tsx:19
  • Dialog has cyclomatic complexity 21 and cognitive complexity 19; 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. — src/components/dialog/index.tsx:78
  • (anonymous) has cyclomatic complexity 20 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. — src/utils/common.ts:104
R3 · Large Files9.4 / 10Exemplary✓ 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.

  • src/services/app/schedules.ts has 2492 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/services/app/schedules.ts:1
  • src/components/illustrations/IllustrationMultiPlatform.tsx has 2296 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/components/illustrations/IllustrationMultiPlatform.tsx:1
  • src/services/worker/backupUtils.ts has 1945 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/services/worker/backupUtils.ts:1
  • src/services/app/autofill.ts has 1798 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/services/app/autofill.ts:1
  • src/components/illustrations/IllustrationSecretary.tsx has 1513 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/components/illustrations/IllustrationSecretary.tsx:1
  • src/features/meetings/monthly_view/index.tsx has 1307 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/features/meetings/monthly_view/index.tsx:1
  • src/utils/dev.ts has 1289 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/utils/dev.ts:1
  • src/components/illustrations/IllustrationOtherSchedules.tsx has 1077 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/components/illustrations/IllustrationOtherSchedules.tsx:1
  • src/services/app/assignment_selection.ts has 1077 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/services/app/assignment_selection.ts:1
  • src/constants/index.ts has 1070 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/constants/index.ts:1
  • src/services/app/assignments_with_stats.ts has 1032 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/services/app/assignments_with_stats.ts:1
  • src/services/app/persons.ts has 859 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/services/app/persons.ts:1
  • src/features/persons/speakers_catalog/import_export/confirm_import/useCSVImport.tsx has 723 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/features/persons/speakers_catalog/import_export/confirm_import/useCSVImport.tsx:1
  • REDACTED has 703 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
  • src/features/congregation/settings/import_export/confirm_import/useConfirmImport.tsx has 641 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/features/congregation/settings/import_export/confirm_import/useConfirmImport.tsx:1
  • src/services/dexie/visiting_speakers.ts has 635 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/services/dexie/visiting_speakers.ts:1
  • src/layouts/navbar/index.tsx has 615 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/layouts/navbar/index.tsx:1
  • src/features/meetings/midweek_editor/index.tsx has 592 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/features/meetings/midweek_editor/index.tsx:1
  • REDACTED has 560 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
  • src/features/congregation/settings/import_export/confirm_import/useImportHourglass.jsx has 558 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/features/congregation/settings/import_export/confirm_import/useImportHourglass.jsx:1
  • src/states/settings.ts has 526 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/states/settings.ts:1
  • src/features/meetings/person_selector/brother_selector/useBrotherSelector.tsx has 520 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/features/meetings/person_selector/brother_selector/useBrotherSelector.tsx:1
  • src/services/dexie/assignment.ts has 504 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/services/dexie/assignment.ts:1
  • src/features/persons/speakers_catalog/import_export/export/useExportSpeakers.tsx has 501 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/features/persons/speakers_catalog/import_export/export/useExportSpeakers.tsx:1
  • src/features/meetings/weekend_editor/index.tsx has 497 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/features/meetings/weekend_editor/index.tsx:1
  • src/features/meetings/person_selector/student_selector/useStudentSelector.tsx has 462 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/features/meetings/person_selector/student_selector/useStudentSelector.tsx:1
  • src/features/meetings/monthly_view/useMonthlyView.tsx has 441 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/features/meetings/monthly_view/useMonthlyView.tsx:1
  • src/utils/date.ts has 422 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/utils/date.ts:1
  • src/features/persons/speakers_catalog/speaker_edit_popup/useSpeakerEditPopup.tsx has 410 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/features/persons/speakers_catalog/speaker_edit_popup/useSpeakerEditPopup.tsx:1
  • src/services/api/user.ts has 404 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/services/api/user.ts:1

What to do

  • Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
R4 · Test Coverage9.8 / 10Exemplary✓ 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. (×31) — src/utils/dev.ts:1, converter/svg/convert.js:1, src/components/multi_select/styled.tsx:1, …

What to do

  • Add tests that import the unreached modules (directly or through their public entry).
R5 · Dependency Freshness4.9 / 10Weak✓ 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.

  • 51 outdated package(s); JS/npm CVEs scored in D30
R6 · Tooling6.7 / 10Adequate✓ 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.

  • test ✓ · lint ✓ · typecheck ✗ — read from this repository's package.json scripts and corroborated against its CI workflows. A script counts when its name or command matches the step: `test` for the suite, `lint` or `prettier` for linting, `typecheck`/`type-check`/`tsc` for type checking. ✗ therefore means no script or CI step under those names was found, NOT that the step is absent from your pipeline — a task invoked by a runner this check does not read, or named something else entirely, is not seen and is worth confirming before acting on a cross. A ✓ means the wiring is DECLARED — a script or CI step under those names exists. It is not a statement that the step passes, or that it runs at all: nothing here installs a dependency or executes a suite.
  • the root package is TypeScript, but a type error in it cannot fail anything this repository runs: its `build` script (`vite build && tsx workbox.config.ts`) compiles TypeScript with a transpile-only tool that strips types without checking them, and no script, config or CI step of the package runs `tsc --noEmit` or another type checker over it. Add a type check that can fail — a `typecheck` script running `tsc --noEmit` (or `vue-tsc`/`svelte-check`) that CI or the workspace pipeline runs, or a build step that checks before it bundles. — package.json:13

What to do

  • Add `tsc --noEmit` as package.json scripts and run them in CI.
R7 · Dead Code7.7 / 10Strong✓ 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 129 application, 9 tooling and 5 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 (129 application, 9 tooling, 5 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/components/multi_select/index.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it (×2) — src/components/multi_select/styled.tsx, src/components/multi_select/types.ts
  • no import path from any entry point (129 application, 9 tooling, 5 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 (×20) — src/features/congregation/settings/public_links/index.tsx, src/features/meetings/schedule_range_selector/index.tsx, src/components/info_tip/index.tsx, …
  • no import path from any entry point (129 application, 9 tooling, 5 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/features/meetings/schedule_range_selector/index.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — src/features/meetings/schedule_range_selector/useScheduleRangeSelector.tsx
  • no import path from any entry point (129 application, 9 tooling, 5 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/features/meetings/switch_checkbox/index.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — src/features/meetings/switch_checkbox/useSwitchCheckbox.tsx
  • no import path from any entry point (129 application, 9 tooling, 5 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/components/info_tip/index.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — src/components/info_tip/types.ts
  • no import path from any entry point (129 application, 9 tooling, 5 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/components/member_account_item/index.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it (×2) — src/components/member_account_item/member_account_item.styled.tsx, src/components/member_account_item/member_account_item.types.tsx
  • no import path from any entry point (129 application, 9 tooling, 5 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/components/feature_flag/index.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — src/components/feature_flag/useFeatureFlag.tsx
  • no import path from any entry point (129 application, 9 tooling, 5 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/features/meetings/no_schedule/index.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — src/features/meetings/no_schedule/useNoSchedule.tsx
  • no import path from any entry point (129 application, 9 tooling, 5 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (src/features/meetings/schedule_range_selector/index.tsx, src/features/meetings/schedule_range_selector/useScheduleRangeSelector.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — src/features/meetings/schedule_range_selector/index.types.ts
  • no import path from any entry point (129 application, 9 tooling, 5 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (src/components/feature_flag/index.tsx, src/components/feature_flag/useFeatureFlag.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — src/components/feature_flag/index.types.ts
  • no import path from any entry point (129 application, 9 tooling, 5 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (src/features/meetings/switch_checkbox/index.tsx, src/features/meetings/switch_checkbox/useSwitchCheckbox.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — src/features/meetings/switch_checkbox/index.types.ts
  • Nothing ultimately consumes this binding: its only referrer is the re-export in src/components/index.ts, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in src/components/index.ts in the same commit, or the barrel will import a name that no longer exists. (×2) — src/components/card_header/index.tsx:51, src/components/dark_overlay/index.tsx:24
  • Nothing imports this binding — it is safe to review for removal. — src/components/date_picker/index.styles.ts:148
  • Nothing ultimately consumes this binding: its only referrer is the re-export in src/components/icons/index.ts, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in src/components/icons/index.ts in the same commit, or the barrel will import a name that no longer exists. (×4) — src/components/icons/IconAddPin.tsx:52, src/components/icons/IconAirportShuttle.tsx:52, src/components/icons/IconAssign.tsx:56, …

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 Hygiene1.0 / 10Critical✓ 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.

  • Imported but not declared in any reachable package.json — installs work only by hoisting accident. (×3) — src/App.tsx:18, src/views/meetings/midweek/S140/app_normal/index.styles.ts:1, unused-i18n-keys.ts:2
  • Declared in the root package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it. (×6) — package.json:84, package.json:85, package.json:35, …

What to do

  • Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
R9 · Circular Imports2.4 / 10Critical✓ 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.

  • src/features/persons/hooks/usePerson.tsx → src/hooks/index.ts → src/hooks/useCurrentUser.tsx → src/features/persons/hooks/usePerson.tsx (one verified cycle inside a mutually-dependent group of 4 files) — src/features/persons/hooks/usePerson.tsx:3
  • src/services/app/assignments_with_stats.ts → src/services/app/autofill.ts → src/services/app/assignments_with_stats.ts — src/services/app/assignments_with_stats.ts:18
  • src/services/app/field_service_groups.ts → src/services/states/persons.ts → src/states/persons.ts → src/services/app/persons.ts → src/states/field_service_groups.ts → src/services/app/field_service_groups.ts — src/services/app/field_service_groups.ts:2
  • src/services/app/index.ts → src/services/dexie/assignment.ts → src/services/app/index.ts (one verified cycle inside a mutually-dependent group of 5 files) — src/services/app/index.ts:24

What to do

  • Break each cycle by extracting the shared piece into a module both sides can import.
S1 · Web-Security Posture9.5 / 10Exemplary✓ Tool-verified

Other · Security — Read from this repository's JavaScript/TypeScript source: cryptographic hygiene (weak hash or cipher, key material fixed in the source) and outbound TLS (certificate validation, protocol version) — facts about code that hold whether or not it serves anything itself. This repository commits the configuration that serves its own HTTP surface, so that configuration was read in full for the security response headers it sets. Of the server controls, two are read where the source shows them: every session or sign-in cookie the code sets is read for HttpOnly, Secure and SameSite at the line that sets it (a raw `Set-Cookie` header, Express, Fastify, Hono, Koa, Next.js, `cookie.serialize`, express-session and cookie-session), and every Node listener for HTTPS enforcement. HSTS, security response headers and input validation are NOT assessed for JavaScript/TypeScript: each is scored as an absence, an absence is only reportable over the production HTTP server, and in this ecosystem the file that opens the port is build output or a framework launcher rather than a file in the source tree. 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.

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.

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 propagation4.0 / 10Weak✓ 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 0/64 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.
  • `apiGetCongregationBackup` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — src/services/worker/backupApi.ts:3
  • `apiGetPocketBackup` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — src/services/worker/backupApi.ts:60
  • `apiSendPocketBackup` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — src/services/worker/backupApi.ts:88
  • `apiSendCongregationBackupChunk` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — src/services/worker/backupApi.ts:111
  • `apiFeatureFlagsGet` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — src/services/api/app.ts:3
  • `apiFetchCountries` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — REDACTED:10
  • `apiFetchCongregations` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — REDACTED:36
  • `apiCreateCongregation` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — REDACTED:67
  • `apiFetchCongregationUsers` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — REDACTED:105
  • `apiSetCongregationMasterKey` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — REDACTED:132
  • `apiSetCongregationAccessCode` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — REDACTED:164
  • `apiGetCongregationMasterKey` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — REDACTED:197
  • `apiGetCongregationAccessCode` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — REDACTED:224
  • `apiPocketUserCreate` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — REDACTED:250
  • `apiCongregationUsersGet` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — REDACTED:304
  • `apiCongregationUserUpdate` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — REDACTED:338
  • `apiAdminRevokeUserSession` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — REDACTED:397
  • `apiAdminDeletePocketCode` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — REDACTED:436
  • `apiAdminGlobalSearchUser` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — REDACTED:471
  • `apiCreateUser` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — REDACTED:498
  • `apiCongregationUserDelete` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — REDACTED:552
  • `apiCongregationSaveApplication` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — REDACTED:587
  • `apiCongregationDeleteApplication` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — REDACTED:625
  • `apiSetUserUid` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — REDACTED:660
  • `apiCongregationDelete` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — REDACTED:692
  • `apiCongregationJoinRequestDecline` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — REDACTED:722
  • `apiCongregationJoinRequestAccept` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — REDACTED:758
  • `apiFetchNotifications` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — src/services/api/notification.ts:4
  • `apiPocketSignup` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — src/services/api/pocket.ts:9
  • `apiPocketValidateMe` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — src/services/api/pocket.ts:28
  • `apiGetPocketSessions` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — src/services/api/pocket.ts:47
  • `apiRevokePocketSession` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — src/services/api/pocket.ts:68
  • `apiPocketFieldServiceReportPost` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — src/services/api/pocket.ts:87
  • `apiGetPocketApplications` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — src/services/api/pocket.ts:117
  • `apiPocketSubmitApplication` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — src/services/api/pocket.ts:139
  • `apiPocketDelete` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — src/services/api/pocket.ts:171
  • `apiFetchSchedule` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — src/services/api/schedule.ts:10
  • `apiPublicScheduleGet` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — src/services/api/schedule.ts:56
  • `apiPublishSchedule` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — src/services/api/schedule.ts:89

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.

X24 · Document value interpolated into markup unescaped10.0 / 10Exemplary○ Nothing flagged

Other · Security — Whether text read out of the document being converted is escaped before it is written into generated markup — a value the document's author chose, interpolated into an attribute the surrounding literal delimits, can close that attribute and open another.

Method: Roslyn semantic model over the whole compilation: a string-typed `Value`/`InnerText`/`InnerXml`/`Text` member declared inside `DocumentFormat.OpenXml` or `System.Xml` is a taint SOURCE, propagated through assignments, returns, arguments, tuple elements and string composition to its transitive closure, then read at interpolated-string holes that sit in a markup position the surrounding literal itself delimits. Escaper/encoder calls and enclosing validator conditions cut the flow. Flow- and container-insensitive by construction. A second arm needs no provenance at all and reports a type that CONTRADICTS ITSELF — the same expression escaped at one delimited markup hole and interpolated raw at another hole in the same markup position of the same type, which the type's own escaping proves is a defect without knowing where the value came from. On a repository with no .NET source it reads JavaScript/TypeScript off the token stream with the same rule: a DOM read of raw document text (`getAttribute`, `textContent`, `innerText`, `nodeValue`) is the source, propagated through local bindings and string composition, and judged at template-literal and concatenation holes in the same two delimited markup positions; escapers and validating conditions cut it, and documentation-site, test, vendored and minified scripts are not read. Deterministic, provable per finding. Advisory.

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.

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 handling7.4 / 10Strong✓ 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.

  • 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. (×3) — src/services/haptics/index.ts:16, src/hooks/usePwaInstall.tsx:24, converter/svg/convert.js:166
  • `.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) — src/services/app/index.ts:140, src/services/app/index.ts:142

What to do

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

Other · Code Health — Whether strict null checking is enabled and not undermined by heavy `!` assertion — TypeScript's `strictNullChecks` (which `strict` turns on) is what makes `string` exclude `null` and `undefined`, and the postfix `!` is the operator that silences it.

Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.

  • 0/1 of this repository's type-checking configuration(s) turn on strict null checking (`"strict": true`, or `"strictNullChecks": true`). A configuration that states neither is counted as OFF, because off is tsc's own default; a solution-style one whose `"files"` is empty and whose `"references"` point at other projects is in neither number, because it checks no source itself. Where it is off, `string` admits `null` and `undefined`: passing a value that is null compiles silently and throws on the first property access.
  • ~0.4 `!` null assertions per 1k TypeScript source lines — 66 assertion(s) across the 170513 source line(s) of the 2161 TypeScript file(s) read, which is the only code the operator asserts anything in (a `!` in a `.js` file is not this operator and was not counted, and one in a file whose null checking is off silences nothing). Densest: src/services/app/schedules.ts (15), src/services/app/assignment_selection.ts (11), src/states/app.ts (5). Each one tells the compiler to trust the author about null, suppressing the very diagnostic `strictNullChecks` exists to produce. Many are correct: each is a claim the checker could not verify, and it is wrong only where the value can in fact be missing, so review the densest places first.

What to do

  • The findings name the configuration each number was taken from and, for the assertions, the files that hold them. Turn null checking on where it is off — `"strict": true` in the base tsconfig that the others extend switches `strictNullChecks` on with the rest of the family — and then resolve the assertions rather than adding to them. A `!` on a value the checker could show to be null is a promise the author cannot check from where they are standing, and each one is a `TypeError: Cannot read properties of null` waiting for the path that makes it true; where the value genuinely cannot be null, say something the checker can see instead (narrow it with a test, make the property required, drop the `?`).

WCAG coverage — what static analysis assessed

Statically assessed 15 of 55 WCAG 2.2 Level A/AA success criteria (27%; ≈30% of the 50 WCAG 2.1 AA criteria for EN 301 549). The other 40 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
AC4 · Keyboard semantics2.1.1, 2.4.3Partial signal
AC5 · ARIA correctness4.1.2Partial signal
AC6 · Visual & motion safety1.4.3, 2.4.7Partial — literal CSS only

Not statically assessed — these 40 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.2, 2.1.4, 2.2.2, 2.3.1, 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 Health38.1Weak — gated by R10, X5Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Architecture70.1Adequate — gated by R9Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Maturity58.4Adequate — gated by M2Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Readiness48.6Weak — gated by R8Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security61.5Adequate — gated by D36, C1Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Accessibility41.0Weak — gated by AC2, AC4Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Performance100.0ExemplaryStrongest area.
Unscored — 2 check(s) recorded observations but carry no score

These checks ran and found something, but they do not carry a score — either by design (an advisory check reports evidence rather than grading it) or because they could not be scored here. They are excluded from the score for that reason, not because there was nothing to see.

  • X10 Duplicated predicate — 40 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
  • X7 Silent fallback defaults — 40 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 3 control(s) we could not find positive evidence for

These checks grade a working control, and the repository shows no evidence of one. That is deliberately not scored as a zero: a repository cannot show an ops runbook, a database TTL or an infrastructure-side audit log, so absence of evidence here is not evidence the control is missing. It is also not a statement that the check is irrelevant to this codebase — the thing it grades applies; we just could not see it. Excluded from the score either way.

  • C3 Audit Trail — Repo shows no audit-logging mechanism (an audit-log table or model, an ORM write hook that records changes — a TypeORM/MikroORM subscriber, a Sequelize or Mongoose hook, Prisma middleware — or a change-history plugin such as mongoose-history or sequelize-paper-trail) for sensitive changes — absence of evidence is not evidence of a working control. Record an audit trail in code (or document where it lives) so this dimension can be scored.
  • C4 Data Retention — Repo shows no data-retention / TTL / cleanup mechanism for personal data — absence of evidence is not evidence of a working control. Define retention periods and a purge/cleanup job (or TTL) in code, or document where retention is enforced, so this dimension can be scored.
  • C5 Data-Subject Rights — Repo shows no corroborated data-subject-rights mechanism (erasure / export-portability / consent) tied to a subject id or GDPR vocabulary — absence of evidence is not evidence of a working control. A delete/anonymise identifier was seen but did not co-occur with GDPR vocabulary or a subject-id shape, so it was not credited (e.g. a save-slot DeleteAccount()). Implement erasure, data export/portability and consent tracking over the subject's records.
Not included — 53 check(s) not relevant to this codebase

These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.

  • AX1 Captive dependencies — Not applicable: this repository's JavaScript imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; this repository's TypeScript imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
  • AX2 Stateful singletons — Not applicable: 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).
  • AX4 Dependency direction — not applicable to a vertical-slice architecture (the inward-dependency rule is for layered/clean styles)
  • AX8 Test isolation — no test/production split to check
  • AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
  • AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • AXR1 Runtime accessibility — the dev server (`npm run dev`) kept running but served no page within 2 minutes. Likely cause (not identified): the dev server kept running but no port it opened served a page in the time allowed. Last output: "> organized@3.41.0 dev / > vite / VITE v8.0.16 ready in 645 ms / ➜ Local: http://localhost:4050/ / ➜ Network: http://172.31.7.5:4050/ / 7:32:07 PM [vite] (client) [optimizer] scanning dependencies... / 7:32:12 PM [vite] (client) [optimizer] bundling dependencies..." No runtime evidence was gathered. This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
  • C2 Access Controls — Not assessed: this is a browser application whose data is served by a hosted backend ('firebase/app', src/wrapper/feature_flags/useFeatureFlags.tsx:3). Its access control is that backend's configuration — Supabase row-level security, Firebase security rules, Appwrite permissions — and this repository carries none of it that this check reads (no Supabase migration, no server code). A client-side route guard hides a page; it authorizes nothing. Whether access is authorized by default could not be established, and its absence is not scored.
  • D11 Test Reliability — Test reliability not included — Cypress end-to-end specs need the application running, which a scan does not start (cypress-e2e)
  • 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 (5006 declarations, no unit with a dominant convention).
  • D22 Internal API Consistency — No intentionally-exposed public API to evaluate for consistency.
  • D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
  • D25 ADR Conformance — no ADRs to check
  • D26 Project Cohesion — D26 could not read how the parts of this repository's one build unit reference each other, so its cohesion was not measured. Not scored: this is a gap in the analyzer, not a verdict about this repository.
  • D27 Navigability — symbol resolution incomplete — navigability not assessed
  • D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
  • D4 Code Duplication — This repository's production source (.ts, .tsx) is not read by D4's token comparison, which compares .NET source: duplication in it is measured by R10 Code Duplication, the frontend lens's card running the same clone algorithm over the JS/TS token stream. Not scored here — read the R10 card for this repository's duplication.
  • 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.
  • D5 Coupling — Not applicable — this npm build ships 1 production module(s), so there is no coupling BETWEEN modules to measure. (Its test and non-production modules are not part of the shipped graph.)
  • D6 Cohesion (LCOM4) — Cohesion (LCOM4) was not measured: of the 2 type(s) found, none both holds instance state and has two or more methods whose shared use of it could be read (2 with fewer than two methods), so LCOM4 is undefined for every type in this repository. Not scored — the metric does not apply here, and this is not a finding about this repository.
  • 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 — JavaScript/TypeScript suite
  • DM1 Domain Modelling — not scored — this repository shows none of the 3 signals this lens looks for
  • ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
  • ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
  • ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
  • P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
  • P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JavaScript/TypeScript source, so there is no service whose uptime a failing dependency could take down
  • P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
  • P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
  • PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for tinybench, mitata, benchmark.js, benny or vitest `bench(...)` calls in files that import them (or `*.bench.*` files), or one of those in a package.json, 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.
  • SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • 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 — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
  • 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
  • X26 Unsynchronised callback handoff — Not applicable: this check looks for a collection written by a callback on one thread while the body waiting on it touches it on another, and in this repository's languages no collection is reachable from two threads at once. TypeScript/JavaScript runs every callback on the one thread that owns its objects: a callback runs only when the body waiting on it has yielded, never alongside it, and a worker thread receives a COPY of what it is sent. A SharedArrayBuffer carries raw bytes, never an Array, Map or Set, so no collection is reachable from two threads at once. Not a gap in the analyzer and not a finding about your code.
  • X27 Collection changed while being enumerated — Not applicable: this check looks for a loop whose body adds to or removes from the very collection the loop is walking, invalidating the enumerator it holds, and in this repository's languages that cannot happen. JavaScript and TypeScript have no iterator that a change can invalidate: an `Array` is walked by index against its live length, and a `Map` or `Set` by the ECMAScript specification's live entry list, so a body that adds to, removes from or empties what it walks raises nothing — every loop form (`for…of`, `for…in`, `forEach`, `map`, `filter`, `reduce`, `entries()`) on every built-in collection (`Array`, `Map`, `Set`, plain objects, `URLSearchParams`, `Headers`, `FormData`) runs to completion. Such a loop can still skip an element or never end, which is a different defect and not the one this check asks about. Not a gap in the analyzer and not a finding about your code.
  • 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 — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.

Appendix A — Findings (grouped)

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

Critical — 32 finding(s)
D30 · Dependency Vulnerabilities · High CVE · ×15
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D28 · Secrets (history) · REDACTED · ×3
  • REDACTED
  • REDACTED
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
R9 · Circular Imports · Import cycle (2 files) · ×2
  • Import cycle (2 files) src/services/app/assignments_with_stats.ts:18 — src/services/app/assignments_with_stats.ts → src/services/app/autofill.ts → src/services/app/assignments_with_stats.ts
  • Import cycle (2 files) src/services/app/index.ts:24 — src/services/app/index.ts → src/services/dexie/assignment.ts → src/services/app/index.ts (one verified cycle inside a mutually-dependent group of 5 files)
AC3 · Page structure · Viewport restricts zoom · ×1
  • Viewport restricts zoom index.html:16 — user-scalable=no/0 or a maximum-scale below 2 stops low-vision users zooming to 200%. Remove the zoom restriction from the viewport meta.
AC4 · Keyboard semantics · Click handler on a non-interactive <div> · ×1
  • Click handler on a non-interactive <div> src/components/time_picker_slider/TimeUnit.tsx:27 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D30 · Dependency Vulnerabilities · Critical CVE · ×1
  • REDACTED
D35 · Change Coupling · Boundary-crossing change coupling · ×1
  • Boundary-crossing change coupling: useLanguage.tsx ↔ app.ts src/features/language_switcher/useLanguage.tsx:1 — `src/features/language_switcher/useLanguage.tsx` (context features) and `src/states/app.ts` (context states) sit in DIFFERENT parts of the tree yet change together 50% of the time (6 of the 12 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `85bbe5ea` feat(locales): add hebrew language; `4fc50258` fix(components): localize date shown in toolbar for date picker; `51bea3b5` feat(app): localize date picker — run `git show` on any of them.
R8 · Dependency Hygiene · Unlisted import '@emotion/cache' · ×1
  • Unlisted import '@emotion/cache' src/App.tsx:18 — Imported but not declared in any reachable package.json — installs work only by hoisting accident.
R8 · Dependency Hygiene · Unlisted import '@react-pdf/types' · ×1
  • Unlisted import '@react-pdf/types' src/views/meetings/midweek/S140/app_normal/index.styles.ts:1 — Imported but not declared in any reachable package.json — installs work only by hoisting accident.
R8 · Dependency Hygiene · Unlisted import 'glob' · ×1
  • Unlisted import 'glob' unused-i18n-keys.ts:2 — Imported but not declared in any reachable package.json — installs work only by hoisting accident.
R9 · Circular Imports · Import cycle (3 files) · ×1
  • Import cycle (3 files) src/features/persons/hooks/usePerson.tsx:3 — src/features/persons/hooks/usePerson.tsx → src/hooks/index.ts → src/hooks/useCurrentUser.tsx → src/features/persons/hooks/usePerson.tsx (one verified cycle inside a mutually-dependent group of 4 files)
R9 · Circular Imports · Import cycle (5 files) · ×1
  • Import cycle (5 files) src/services/app/field_service_groups.ts:2 — src/services/app/field_service_groups.ts → src/services/states/persons.ts → src/states/persons.ts → src/services/app/persons.ts → src/states/field_service_groups.ts → src/services/app/field_service_groups.ts
Serious — 718 finding(s)
D3 · God Classes · FunctionTooLong · ×183
  • FunctionTooLong: IllustrationMultiPlatform.IllustrationMultiPlatform src/components/illustrations/IllustrationMultiPlatform.tsx:6 — FunctionTooLong — IllustrationMultiPlatform runs 2290 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 2190 over it, 22.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: IllustrationSecretary.IllustrationSecretary src/components/illustrations/IllustrationSecretary.tsx:4 — FunctionTooLong — IllustrationSecretary runs 1508 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 1408 over it, 15.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.
  • FunctionTooLong: index.MonthlyView src/features/meetings/monthly_view/index.tsx:26 — FunctionTooLong — MonthlyView runs 1133 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 1033 over it, 11.33× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: IllustrationOtherSchedules.IllustrationOtherSchedules src/components/illustrations/IllustrationOtherSchedules.tsx:4 — FunctionTooLong — IllustrationOtherSchedules runs 1072 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 972 over it, 10.72× 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: index.MidweekEditor src/features/meetings/midweek_editor/index.tsx:58 — FunctionTooLong — MidweekEditor runs 486 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 386 over it, 4.86× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: index.NavBar src/layouts/navbar/index.tsx:60 — FunctionTooLong — NavBar runs 482 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 382 over it, 4.82× 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: useConfirmImport.useConfirmImport src/features/congregation/settings/import_export/confirm_import/useConfirmImport.tsx:58 — FunctionTooLong — useConfirmImport runs 462 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 362 over it, 4.62× 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: dev.importDummyPersons src/utils/dev.ts:67 — FunctionTooLong — importDummyPersons runs 454 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 354 over it, 4.54× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: useImportHourglass.useHourglassImport src/features/congregation/settings/import_export/confirm_import/useImportHourglass.jsx:20 — FunctionTooLong — useHourglassImport runs 415 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 315 over it, 4.15× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: index.WeekendEditor src/features/meetings/weekend_editor/index.tsx:53 — FunctionTooLong — WeekendEditor runs 404 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 304 over it, 4.04× 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: assignment.dbAssignmentUpdate src/services/dexie/assignment.ts:6 — FunctionTooLong — dbAssignmentUpdate runs 398 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 298 over it, 3.98× 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: backupUtils.dbExportDataBackup src/services/worker/backupUtils.ts:1757 — FunctionTooLong — dbExportDataBackup runs 387 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 287 over it, 3.87× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: useCSVImport.useCSVImport src/features/persons/speakers_catalog/import_export/confirm_import/useCSVImport.tsx:59 — FunctionTooLong — useCSVImport runs 378 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 278 over it, 3.78× 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: IllustrationMinistryAssignments.IllustrationMinistryAssignments src/components/illustrations/IllustrationMinistryAssignments.tsx:4 — FunctionTooLong — IllustrationMinistryAssignments runs 369 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 269 over it, 3.69× 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: useBrotherSelector.useBrotherSelector src/features/meetings/person_selector/brother_selector/useBrotherSelector.tsx:50 — FunctionTooLong — useBrotherSelector runs 364 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 264 over it, 3.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.
  • FunctionTooLong: IllustrationMeetingSchedules.IllustrationMeetingSchedules src/components/illustrations/IllustrationMeetingSchedules.tsx:4 — FunctionTooLong — IllustrationMeetingSchedules runs 343 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 243 over it, 3.43× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: useStudentSelector.useStudentSelector src/features/meetings/person_selector/student_selector/useStudentSelector.tsx:47 — FunctionTooLong — useStudentSelector runs 343 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 243 over it, 3.43× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: index.TemplateS140AppNormal src/views/meetings/midweek/S140/app_normal/index.tsx:25 — FunctionTooLong — TemplateS140AppNormal runs 323 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 223 over it, 3.23× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: schedules.schedulesMidweekData src/services/app/schedules.ts:2047 — FunctionTooLong — schedulesMidweekData runs 310 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 210 over it, 3.10× 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: visiting_speakers.dbVisitingSpeakersDummy src/services/dexie/visiting_speakers.ts:249 — FunctionTooLong — dbVisitingSpeakersDummy runs 310 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 210 over it, 3.10× 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: index.ScheduleS140 src/views/meetings/midweek/S140/default/index.tsx:23 — FunctionTooLong — ScheduleS140 runs 296 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 196 over it, 2.96× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: useMinistryYearlyRecord.useMinistryYearlyRecord src/features/ministry/hooks/useMinistryYearlyRecord.tsx:10 — FunctionTooLong — useMinistryYearlyRecord runs 279 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 179 over it, 2.79× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: useContainer.useContainer src/features/app_notification/container/useContainer.tsx:42 — FunctionTooLong — useContainer runs 276 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 176 over it, 2.76× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: index.StudentSelector src/features/meetings/person_selector/student_selector/index.tsx:32 — FunctionTooLong — StudentSelector runs 275 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 175 over it, 2.75× 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: useSpeakerEditPopup.useSpeakerEditPopup src/features/persons/speakers_catalog/speaker_edit_popup/useSpeakerEditPopup.tsx:81 — FunctionTooLong — useSpeakerEditPopup runs 264 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 164 over it, 2.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.
  • + 158 more in this group — see findings.md.
X2 · Cancellation propagation · Async function without AbortSignal · ×39
  • Async function without AbortSignal: apiGetCongregationBackup src/services/worker/backupApi.ts:3 — `apiGetCongregationBackup` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
  • Async function without AbortSignal: apiGetPocketBackup src/services/worker/backupApi.ts:60 — `apiGetPocketBackup` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
  • Async function without AbortSignal: apiSendPocketBackup src/services/worker/backupApi.ts:88 — `apiSendPocketBackup` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
  • Async function without AbortSignal: apiSendCongregationBackupChunk src/services/worker/backupApi.ts:111 — `apiSendCongregationBackupChunk` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
  • Async function without AbortSignal: apiFeatureFlagsGet src/services/api/app.ts:3 — `apiFeatureFlagsGet` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
  • Async function without AbortSignal: apiFetchCountries REDACTED:10 — `apiFetchCountries` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
  • Async function without AbortSignal: apiFetchCongregations REDACTED:36 — `apiFetchCongregations` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
  • Async function without AbortSignal: apiCreateCongregation REDACTED:67 — `apiCreateCongregation` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
  • Async function without AbortSignal: apiFetchCongregationUsers REDACTED:105 — `apiFetchCongregationUsers` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
  • Async function without AbortSignal: apiSetCongregationMasterKey REDACTED:132 — `apiSetCongregationMasterKey` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
  • Async function without AbortSignal: apiSetCongregationAccessCode REDACTED:164 — `apiSetCongregationAccessCode` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
  • Async function without AbortSignal: apiGetCongregationMasterKey REDACTED:197 — `apiGetCongregationMasterKey` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
  • Async function without AbortSignal: apiGetCongregationAccessCode REDACTED:224 — `apiGetCongregationAccessCode` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
  • Async function without AbortSignal: apiPocketUserCreate REDACTED:250 — `apiPocketUserCreate` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
  • Async function without AbortSignal: apiCongregationUsersGet REDACTED:304 — `apiCongregationUsersGet` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
  • Async function without AbortSignal: apiCongregationUserUpdate REDACTED:338 — `apiCongregationUserUpdate` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
  • Async function without AbortSignal: apiAdminRevokeUserSession REDACTED:397 — `apiAdminRevokeUserSession` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
  • Async function without AbortSignal: apiAdminDeletePocketCode REDACTED:436 — `apiAdminDeletePocketCode` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
  • Async function without AbortSignal: apiAdminGlobalSearchUser REDACTED:471 — `apiAdminGlobalSearchUser` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
  • Async function without AbortSignal: apiCreateUser REDACTED:498 — `apiCreateUser` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
  • Async function without AbortSignal: apiCongregationUserDelete REDACTED:552 — `apiCongregationUserDelete` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
  • Async function without AbortSignal: apiCongregationSaveApplication REDACTED:587 — `apiCongregationSaveApplication` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
  • Async function without AbortSignal: apiCongregationDeleteApplication REDACTED:625 — `apiCongregationDeleteApplication` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
  • Async function without AbortSignal: apiSetUserUid REDACTED:660 — `apiSetUserUid` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
  • Async function without AbortSignal: apiCongregationDelete REDACTED:692 — `apiCongregationDelete` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
  • + 14 more in this group — see findings.md.
R4 · Test Coverage · No test reaches this file · ×31
  • No test reaches this file src/utils/dev.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 converter/svg/convert.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 src/components/multi_select/styled.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 src/constants/person_mock.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 src/features/congregation/settings/public_links/index.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 src/features/meetings/schedule_range_selector/useScheduleRangeSelector.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 src/features/meetings/schedule_range_selector/index.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 src/components/info_tip/index.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 src/features/meetings/switch_checkbox/useSwitchCheckbox.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 src/features/meetings/no_schedule/index.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 src/components/multi_select/index.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 src/states/utils.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 unused-i18n-keys.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 src/components/member_account_item/index.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 src/components/table/table.styles.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 src/features/ministry/report/form_S4/bible_studies/bible_studies_list/bible_study_item/useBibleStudyItem.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 src/components/member_account_item/member_account_item.styled.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 src/features/meetings/switch_checkbox/index.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 src/utils/scroll.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 src/features/ministry/application_form/footer/index.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 src/views/reports/S21/1in1/index.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 src/services/react/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 src/components/feature_flag/useFeatureFlag.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 src/components/feature_flag/index.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 src/features/meetings/no_schedule/useNoSchedule.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.
  • + 6 more in this group — see findings.md.
D15 · Churn × Complexity Hotspots · Hotspot · ×23
  • Hotspot: src/services/worker/backupUtils.ts src/services/worker/backupUtils.ts:1757 — src/services/worker/backupUtils.ts changed 10 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 85 in backupUtils.dbExportDataBackup at line 1757. 6 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-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 23:08:15 +00:00' --until='2026-11-16 23:08:15 +00:00' --full-history --no-merges -- src/services/worker/backupUtils.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: src/services/app/schedules.ts src/services/app/schedules.ts:139 — src/services/app/schedules.ts changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 116 in schedules.schedulesMidweekInfo at line 139. 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-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 23:08:15 +00:00' --until='2026-11-16 23:08:15 +00:00' --full-history --no-merges -- src/services/app/schedules.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: src/components/button/index.tsx src/components/button/index.tsx:10 — src/components/button/index.tsx changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 90 in index.Button at line 10. 2 of those changes were fix/bug commits, and the other 2 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-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 23:08:15 +00:00' --until='2026-11-16 23:08:15 +00:00' --full-history --no-merges -- src/components/button/index.tsx`: 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: src/layouts/navbar/index.tsx src/layouts/navbar/index.tsx:60 — src/layouts/navbar/index.tsx changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 38 in index.NavBar at line 60. 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-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 23:08:15 +00:00' --until='2026-11-16 23:08:15 +00:00' --full-history --no-merges -- src/layouts/navbar/index.tsx`: 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: src/features/meetings/monthly_view/index.tsx src/features/meetings/monthly_view/index.tsx:26 — src/features/meetings/monthly_view/index.tsx changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 50 in index.MonthlyView at line 26. 1 of those changes was a fix/bug commit, and the other 2 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-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 23:08:15 +00:00' --until='2026-11-16 23:08:15 +00:00' --full-history --no-merges -- src/features/meetings/monthly_view/index.tsx`: 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: src/features/meetings/person_selector/student_selector/useStudentSelector.tsx src/features/meetings/person_selector/student_selector/useStudentSelector.tsx:199 — src/features/meetings/person_selector/student_selector/useStudentSelector.tsx changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 29 in useStudentSelector.useStudentSelector.options at line 199. 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-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 23:08:15 +00:00' --until='2026-11-16 23:08:15 +00:00' --full-history --no-merges -- src/features/meetings/person_selector/student_selector/useStudentSelector.tsx`: 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: src/features/meetings/midweek_editor/index.tsx src/features/meetings/midweek_editor/index.tsx:58 — src/features/meetings/midweek_editor/index.tsx changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 55 in index.MidweekEditor at line 58. 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-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 23:08:15 +00:00' --until='2026-11-16 23:08:15 +00:00' --full-history --no-merges -- src/features/meetings/midweek_editor/index.tsx`: 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: src/features/meetings/person_selector/student_selector/index.tsx src/features/meetings/person_selector/student_selector/index.tsx:32 — src/features/meetings/person_selector/student_selector/index.tsx changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 24 in index.StudentSelector at line 32. 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-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 23:08:15 +00:00' --until='2026-11-16 23:08:15 +00:00' --full-history --no-merges -- src/features/meetings/person_selector/student_selector/index.tsx`: 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: src/components/textfield/index.tsx src/components/textfield/index.tsx:16 — src/components/textfield/index.tsx changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 44 in index.TextField at line 16. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 23:08:15 +00:00' --until='2026-11-16 23:08:15 +00:00' --full-history --no-merges -- src/components/textfield/index.tsx`: 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: src/features/reports/meeting_attendance/monthly_record/week_box/useWeekBox.tsx src/features/reports/meeting_attendance/monthly_record/week_box/useWeekBox.tsx:51 — src/features/reports/meeting_attendance/monthly_record/week_box/useWeekBox.tsx changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 20 in useWeekBox.useWeekBox at line 51. 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-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 23:08:15 +00:00' --until='2026-11-16 23:08:15 +00:00' --full-history --no-merges -- src/features/reports/meeting_attendance/monthly_record/week_box/useWeekBox.tsx`: 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: src/features/meetings/weekly_schedules/midweek_meeting/index.tsx src/features/meetings/weekly_schedules/midweek_meeting/index.tsx:27 — src/features/meetings/weekly_schedules/midweek_meeting/index.tsx changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 26 in index.MidweekMeeting at line 27. 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-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 23:08:15 +00:00' --until='2026-11-16 23:08:15 +00:00' --full-history --no-merges -- src/features/meetings/weekly_schedules/midweek_meeting/index.tsx`: 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: src/components/dialog/index.tsx src/components/dialog/index.tsx:78 — src/components/dialog/index.tsx changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 23 in index.Dialog at line 78. 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-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 23:08:15 +00:00' --until='2026-11-16 23:08:15 +00:00' --full-history --no-merges -- src/components/dialog/index.tsx`: 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: src/features/meetings/weekly_schedules/midweek_meeting/living_part/index.tsx src/features/meetings/weekly_schedules/midweek_meeting/living_part/index.tsx:23 — src/features/meetings/weekly_schedules/midweek_meeting/living_part/index.tsx changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 21 in index.LivingPart 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-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 23:08:15 +00:00' --until='2026-11-16 23:08:15 +00:00' --full-history --no-merges -- src/features/meetings/weekly_schedules/midweek_meeting/living_part/index.tsx`: 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: src/features/persons/hooks/usePerson.tsx src/features/persons/hooks/usePerson.tsx:195 — src/features/persons/hooks/usePerson.tsx changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 28 in usePerson.usePerson.getBadges at line 195. 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-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 23:08:15 +00:00' --until='2026-11-16 23:08:15 +00:00' --full-history --no-merges -- src/features/persons/hooks/usePerson.tsx`: 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: src/features/meetings/weekend_editor/public_talk_selector/index.tsx src/features/meetings/weekend_editor/public_talk_selector/index.tsx:12 — src/features/meetings/weekend_editor/public_talk_selector/index.tsx changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 18 in index.PublicTalkSelector 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-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 23:08:15 +00:00' --until='2026-11-16 23:08:15 +00:00' --full-history --no-merges -- src/features/meetings/weekend_editor/public_talk_selector/index.tsx`: 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: src/features/meetings/person_selector/brother_selector/index.tsx src/features/meetings/person_selector/brother_selector/index.tsx:16 — src/features/meetings/person_selector/brother_selector/index.tsx changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 17 in index.BrotherSelector at line 16. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 23:08:15 +00:00' --until='2026-11-16 23:08:15 +00:00' --full-history --no-merges -- src/features/meetings/person_selector/brother_selector/index.tsx`: 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: src/features/activities/upcoming_events/edit_upcoming_event/index.tsx src/features/activities/upcoming_events/edit_upcoming_event/index.tsx:24 — src/features/activities/upcoming_events/edit_upcoming_event/index.tsx changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 25 in index.EditUpcomingEvent at line 24. 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-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 23:08:15 +00:00' --until='2026-11-16 23:08:15 +00:00' --full-history --no-merges -- src/features/activities/upcoming_events/edit_upcoming_event/index.tsx`: 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: src/views/meetings/midweek/S140/default/index.tsx src/views/meetings/midweek/S140/default/index.tsx:23 — src/views/meetings/midweek/S140/default/index.tsx changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 23 in index.ScheduleS140 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-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 23:08:15 +00:00' --until='2026-11-16 23:08:15 +00:00' --full-history --no-merges -- src/views/meetings/midweek/S140/default/index.tsx`: 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: src/features/congregation/settings/language_groups/group_delete/useGroupDelete.tsx src/features/congregation/settings/language_groups/group_delete/useGroupDelete.tsx:39 — src/features/congregation/settings/language_groups/group_delete/useGroupDelete.tsx changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 20 in useGroupDelete.useGroupDelete.handleDelete at line 39. 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-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 23:08:15 +00:00' --until='2026-11-16 23:08:15 +00:00' --full-history --no-merges -- src/features/congregation/settings/language_groups/group_delete/useGroupDelete.tsx`: 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: src/features/activities/upcoming_events/upcoming_event/index.tsx src/features/activities/upcoming_events/upcoming_event/index.tsx:21 — src/features/activities/upcoming_events/upcoming_event/index.tsx changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 18 in index.UpcomingEvent at line 21. 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-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 23:08:15 +00:00' --until='2026-11-16 23:08:15 +00:00' --full-history --no-merges -- src/features/activities/upcoming_events/upcoming_event/index.tsx`: 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: src/features/persons/speakers_catalog/my_congregation/header/index.tsx src/features/persons/speakers_catalog/my_congregation/header/index.tsx:20 — src/features/persons/speakers_catalog/my_congregation/header/index.tsx changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 18 in index.OutgoingSpeakersHeader at line 20. 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-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 23:08:15 +00:00' --until='2026-11-16 23:08:15 +00:00' --full-history --no-merges -- src/features/persons/speakers_catalog/my_congregation/header/index.tsx`: 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: src/features/persons/speakers_catalog/other_congregations/speakers_list/index.tsx src/features/persons/speakers_catalog/other_congregations/speakers_list/index.tsx:12 — src/features/persons/speakers_catalog/other_congregations/speakers_list/index.tsx changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 17 in index.SpeakersList 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-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 23:08:15 +00:00' --until='2026-11-16 23:08:15 +00:00' --full-history --no-merges -- src/features/persons/speakers_catalog/other_congregations/speakers_list/index.tsx`: 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: src/features/meetings/monthly_view/useMonthlyView.tsx src/features/meetings/monthly_view/useMonthlyView.tsx:30 — src/features/meetings/monthly_view/useMonthlyView.tsx changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 17 in useMonthlyView.useMonthlyView 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-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 23:08:15 +00:00' --until='2026-11-16 23:08:15 +00:00' --full-history --no-merges -- src/features/meetings/monthly_view/useMonthlyView.tsx`: 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.
D3 · God Classes · FileTooLong · ×15
  • FileTooLong: illustrations/IllustrationMultiPlatform.tsx src/components/illustrations/IllustrationMultiPlatform.tsx — FileTooLong — 2294 significant lines (blank, comment-only and punctuation-only lines excluded), about 100% of them inside a single declaration: IllustrationMultiPlatform (6-2297). The bar is 500 significant lines; this is 1794 over it, 4.59× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
  • FileTooLong: app/schedules.ts src/services/app/schedules.ts — FileTooLong — 1977 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 1477 over it, 3.95× 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: illustrations/IllustrationSecretary.tsx src/components/illustrations/IllustrationSecretary.tsx — FileTooLong — 1511 significant lines (blank, comment-only and punctuation-only lines excluded), about 100% of them inside a single declaration: IllustrationSecretary (4-1513). The bar is 500 significant lines; this is 1011 over it, 3.02× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
  • FileTooLong: worker/backupUtils.ts src/services/worker/backupUtils.ts — FileTooLong — 1477 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 977 over it, 2.95× 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: monthly_view/index.tsx src/features/meetings/monthly_view/index.tsx — FileTooLong — 1158 significant lines (blank, comment-only and punctuation-only lines excluded), about 98% of them inside a single declaration: MonthlyView (26-1310). The bar is 500 significant lines; this is 658 over it, 2.32× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
  • FileTooLong: illustrations/IllustrationOtherSchedules.tsx src/components/illustrations/IllustrationOtherSchedules.tsx — FileTooLong — 1075 significant lines (blank, comment-only and punctuation-only lines excluded), about 100% of them inside a single declaration: IllustrationOtherSchedules (4-1077). The bar is 500 significant lines; this is 575 over it, 2.15× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
  • FileTooLong: app/autofill.ts src/services/app/autofill.ts — FileTooLong — 1019 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 519 over it, 2.04× 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: utils/dev.ts src/utils/dev.ts — FileTooLong — 1012 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 512 over it, 2.02× 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: constants/index.ts src/constants/index.ts — FileTooLong — 809 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 309 over it, 1.62× 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: app/persons.ts src/services/app/persons.ts — FileTooLong — 659 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 159 over it, 1.32× 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: REDACTED REDACTED — FileTooLong — 564 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 64 over it, 1.13× 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: app/assignment_selection.ts src/services/app/assignment_selection.ts — FileTooLong — 562 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 62 over it, 1.12× 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: midweek_editor/index.tsx src/features/meetings/midweek_editor/index.tsx — FileTooLong — 543 significant lines (blank, comment-only and punctuation-only lines excluded), about 90% of them inside a single declaration: MidweekEditor (58-624). The bar is 500 significant lines; this is 43 over it, 1.09× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
  • FileTooLong: navbar/index.tsx src/layouts/navbar/index.tsx — FileTooLong — 534 significant lines (blank, comment-only and punctuation-only lines excluded), about 90% of them inside a single declaration: NavBar (60-635). The bar is 500 significant lines; this is 34 over it, 1.07× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
  • FileTooLong: confirm_import/useConfirmImport.tsx src/features/congregation/settings/import_export/confirm_import/useConfirmImport.tsx — FileTooLong — 519 significant lines (blank, comment-only and punctuation-only lines excluded), about 89% of them inside a single declaration: useConfirmImport (58-775). The bar is 500 significant lines; this is 19 over it, 1.04× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
AC2 · Forms & labels · <Switch> field component without a label · ×10
  • <Switch> field component without a label src/components/switch_with_label/index.tsx:16 — This UI-library field component has no label / aria-label / aria-labelledby / id at this call site, and nothing written inside it here carries one either (a name prop is the form-submission key, not a label; an id, even one the component sets on what it renders, names nothing until a label points at it) — so it likely renders an unlabelled control. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
  • <Switch> field component without a label src/components/theme_switch/index.tsx:50 — This UI-library field component has no label / aria-label / aria-labelledby / id at this call site, and nothing written inside it here carries one either (a name prop is the form-submission key, not a label; an id, even one the component sets on what it renders, names nothing until a label points at it) — so it likely renders an unlabelled control. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
  • <Switch> field component without a label src/features/my_profile/app_settings/index.tsx:39 — This UI-library field component has no label / aria-label / aria-labelledby / id at this call site, and nothing written inside it here carries one either (a name prop is the form-submission key, not a label; an id, even one the component sets on what it renders, names nothing until a label points at it) — so it likely renders an unlabelled control. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
  • <Switch> field component without a label src/features/my_profile/app_settings/index.tsx:89 — This UI-library field component has no label / aria-label / aria-labelledby / id at this call site, and nothing written inside it here carries one either (a name prop is the form-submission key, not a label; an id, even one the component sets on what it renders, names nothing until a label points at it) — so it likely renders an unlabelled control. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
  • <Switch> field component without a label src/features/my_profile/app_settings/index.tsx:150 — This UI-library field component has no label / aria-label / aria-labelledby / id at this call site, and nothing written inside it here carries one either (a name prop is the form-submission key, not a label; an id, even one the component sets on what it renders, names nothing until a label points at it) — so it likely renders an unlabelled control. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
  • <Switch> field component without a label src/features/my_profile/ministry_preferences/index.tsx:19 — This UI-library field component has no label / aria-label / aria-labelledby / id at this call site, and nothing written inside it here carries one either (a name prop is the form-submission key, not a label; an id, even one the component sets on what it renders, names nothing until a label points at it) — so it likely renders an unlabelled control. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
  • <Switch> field component without a label src/features/my_profile/security/index.tsx:53 — This UI-library field component has no label / aria-label / aria-labelledby / id at this call site, and nothing written inside it here carries one either (a name prop is the form-submission key, not a label; an id, even one the component sets on what it renders, names nothing until a label points at it) — so it likely renders an unlabelled control. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
  • <Switch> field component without a label src/features/persons/family_members/index.tsx:74 — This UI-library field component has no label / aria-label / aria-labelledby / id at this call site, and nothing written inside it here carries one either (a name prop is the form-submission key, not a label; an id, even one the component sets on what it renders, names nothing until a label points at it) — so it likely renders an unlabelled control. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
  • <Switch> field component without a label src/features/persons/speakers_catalog/my_congregation/visibility_toggle/index.tsx:38 — This UI-library field component has no label / aria-label / aria-labelledby / id at this call site, and nothing written inside it here carries one either (a name prop is the form-submission key, not a label; an id, even one the component sets on what it renders, names nothing until a label points at it) — so it likely renders an unlabelled control. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
  • <Switch> field component without a label src/features/persons/spiritual_status/title/index.tsx:27 — This UI-library field component has no label / aria-label / aria-labelledby / id at this call site, and nothing written inside it here carries one either (a name prop is the form-submission key, not a label; an id, even one the component sets on what it renders, names nothing until a label points at it) — so it likely renders an unlabelled control. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
AC2 · Forms & labels · <RadioGroup> field component without a label · ×9
  • <RadioGroup> field component without a label src/features/congregation/app_access/user_add/person_select/index.tsx:48 — This UI-library field component has no label / aria-label / aria-labelledby / id at this call site, and nothing written inside it here carries one either (a name prop is the form-submission key, not a label; an id, even one the component sets on what it renders, names nothing until a label points at it) — so it likely renders an unlabelled control. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
  • <RadioGroup> field component without a label src/features/congregation/field_service_groups/export_groups/ExportGroupsDialog.tsx:67 — This UI-library field component has no label / aria-label / aria-labelledby / id at this call site, and nothing written inside it here carries one either (a name prop is the form-submission key, not a label; an id, even one the component sets on what it renders, names nothing until a label points at it) — so it likely renders an unlabelled control. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
  • <RadioGroup> field component without a label src/features/congregation/field_service_groups/export_groups/ExportGroupsDialog.tsx:96 — This UI-library field component has no label / aria-label / aria-labelledby / id at this call site, and nothing written inside it here carries one either (a name prop is the form-submission key, not a label; an id, even one the component sets on what it renders, names nothing until a label points at it) — so it likely renders an unlabelled control. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
  • <RadioGroup> field component without a label src/features/meetings/weekend_editor/public_talk_type_selector/index.tsx:23 — This UI-library field component has no label / aria-label / aria-labelledby / id at this call site, and nothing written inside it here carries one either (a name prop is the form-submission key, not a label; an id, even one the component sets on what it renders, names nothing until a label points at it) — so it likely renders an unlabelled control. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
  • <RadioGroup> field component without a label src/features/meetings/weekend_editor/song_selector/index.tsx:54 — This UI-library field component has no label / aria-label / aria-labelledby / id, and nothing written inside it here carries one either (a name prop is the form-submission key, not a label; an id alone, wherever it is set, names nothing until a label points at it). The text inside it does not stand in for one: these compound APIs render a trigger with role="combobox" (or role="button"), and those roles take their name from the AUTHOR, not from their content — so the words on screen never reach the accessibility tree as a name. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
  • <RadioGroup> field component without a label src/features/persons/basic_info/index.tsx:165 — This UI-library field component has no label / aria-label / aria-labelledby / id at this call site, and nothing written inside it here carries one either (a name prop is the form-submission key, not a label; an id, even one the component sets on what it renders, names nothing until a label points at it) — so it likely renders an unlabelled control. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
  • <RadioGroup> field component without a label src/features/persons/speakers_catalog/speaker_edit_popup/info_tab/index.tsx:92 — This UI-library field component has no label / aria-label / aria-labelledby / id at this call site, and nothing written inside it here carries one either (a name prop is the form-submission key, not a label; an id, even one the component sets on what it renders, names nothing until a label points at it) — so it likely renders an unlabelled control. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
  • <RadioGroup> field component without a label src/features/persons/spiritual_status/baptized_publisher/index.tsx:78 — This UI-library field component has no label / aria-label / aria-labelledby / id at this call site, and nothing written inside it here carries one either (a name prop is the form-submission key, not a label; an id, even one the component sets on what it renders, names nothing until a label points at it) — so it likely renders an unlabelled control. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
  • <RadioGroup> field component without a label src/features/reports/publisher_records/export_S21/all_records/index.tsx:33 — This UI-library field component has no label / aria-label / aria-labelledby / id at this call site, and nothing written inside it here carries one either (a name prop is the form-submission key, not a label; an id, even one the component sets on what it renders, names nothing until a label points at it) — so it likely renders an unlabelled control. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
AC2 · Forms & labels · <TextField> field component without a label · ×7
  • <TextField> field component without a label src/components/timefield/index.tsx:10 — This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
  • <TextField> field component without a label src/features/congregation/settings/congregation_privacy/access_code_view/index.tsx:23 — This UI-library field component has no label / aria-label / aria-labelledby / id at this call site, and nothing written inside it here carries one either (a name prop is the form-submission key, not a label; an id, even one the component sets on what it renders, names nothing until a label points at it) — so it likely renders an unlabelled control. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
  • <TextField> field component without a label src/features/congregation/settings/congregation_privacy/delete_congregation/index.tsx:33 — This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
  • <TextField> field component without a label src/features/congregation/settings/congregation_privacy/master_key_view/index.tsx:23 — This UI-library field component has no label / aria-label / aria-labelledby / id at this call site, and nothing written inside it here carries one either (a name prop is the form-submission key, not a label; an id, even one the component sets on what it renders, names nothing until a label points at it) — so it likely renders an unlabelled control. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
  • <TextField> field component without a label src/features/ministry/report/form_S4/comments/index.tsx:12 — This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
  • <TextField> field component without a label src/features/my_profile/security/delete_account/index.tsx:37 — This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
  • <TextField> field component without a label src/features/reports/publisher_records_details/report_details/comments/index.tsx:11 — This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
D30 · Dependency Vulnerabilities · Medium CVE · ×5
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
X3 · Exception handling · Swallowed exception (empty catch) · ×5
  • Swallowed exception (empty catch) src/services/haptics/index.ts:16 — 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) src/services/app/index.ts:140 — `.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) src/services/app/index.ts:142 — `.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) src/hooks/usePwaInstall.tsx:24 — 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) converter/svg/convert.js:166 — 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 · ClassTooLong · ×4
  • ClassTooLong: IllustrationMultiPlatform src/components/illustrations/IllustrationMultiPlatform.tsx:1 — ClassTooLong — 2290 significant lines (blank, comment-only and punctuation-only lines excluded), 1 methods. The bar is 400 significant lines; this is 1890 over it, 5.73× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: IllustrationSecretary src/components/illustrations/IllustrationSecretary.tsx:1 — ClassTooLong — 1508 significant lines (blank, comment-only and punctuation-only lines excluded), 1 methods. The bar is 400 significant lines; this is 1108 over it, 3.77× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: IllustrationOtherSchedules src/components/illustrations/IllustrationOtherSchedules.tsx:1 — ClassTooLong — 1072 significant lines (blank, comment-only and punctuation-only lines excluded), 1 methods. The bar is 400 significant lines; this is 672 over it, 2.68× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: useConfirmImport src/features/congregation/settings/import_export/confirm_import/useConfirmImport.tsx:1 — ClassTooLong — 462 significant lines (blank, comment-only and punctuation-only lines excluded), 17 methods. The bar is 400 significant lines; this is 62 over it, 1.16× 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.
R7 · Dead Code · Dead file (~0 LoC) · ×4
  • Dead file (~0 LoC) src/services/app/field_service_reports.ts — no import path from any entry point (129 application, 9 tooling, 5 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
  • Dead file (~0 LoC) src/services/app/public_talks.ts — no import path from any entry point (129 application, 9 tooling, 5 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
  • Dead file (~0 LoC) src/services/app/updater.ts — no import path from any entry point (129 application, 9 tooling, 5 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
  • Dead file (~0 LoC) src/services/dexie/announcements.ts — no import path from any entry point (129 application, 9 tooling, 5 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
AC2 · Forms & labels · <OTPInput> field component without a label · ×3
  • <OTPInput> field component without a label src/features/app_start/vip/email_sent/index.tsx:96 — This UI-library field component has no label / aria-label / aria-labelledby / id at this call site, and nothing written inside it here carries one either (a name prop is the form-submission key, not a label; an id, even one the component sets on what it renders, names nothing until a label points at it) — so it likely renders an unlabelled control. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
  • <OTPInput> field component without a label src/features/app_start/vip/verify_mfa/index.tsx:43 — This UI-library field component has no label / aria-label / aria-labelledby / id at this call site, and nothing written inside it here carries one either (a name prop is the form-submission key, not a label; an id, even one the component sets on what it renders, names nothing until a label points at it) — so it likely renders an unlabelled control. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
  • <OTPInput> field component without a label src/features/my_profile/security/mfaEnable/index.tsx:177 — This UI-library field component has no label / aria-label / aria-labelledby / id at this call site, and nothing written inside it here carries one either (a name prop is the form-submission key, not a label; an id, even one the component sets on what it renders, names nothing until a label points at it) — so it likely renders an unlabelled control. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
D2 · Cognitive Complexity · index.Button · ×3
  • index.Button::getBackgroundColorClick (cognitive 34) src/components/button/index.tsx:153 — index.Button::getBackgroundColorClick has cognitive complexity 34 (threshold 15). Drivers by points: if/else 12 (34 pts) (nesting depth added 22). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function. This shape REPEATS in the file: 3 other methods here (index.Button, index.Button::getBackgroundColorHover, index.Button::getSvgColor) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 4 times rather than 4 independent problems. Splitting this body alone leaves the other 3 exactly as they are. Where these are variations on one operation, the change that clears all 4 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.
  • index.Button::getSvgColor (cognitive 21) src/components/button/index.tsx:197 — index.Button::getSvgColor has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (20 pts), boolean chains 1 (nesting depth added 12). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function. This shape REPEATS in the file: 3 other methods here (index.Button, index.Button::getBackgroundColorHover, index.Button::getBackgroundColorClick) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 4 times rather than 4 independent problems. Splitting this body alone leaves the other 3 exactly as they are. Where these are variations on one operation, the change that clears all 4 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.
  • index.Button::getBackgroundColorHover (cognitive 18) src/components/button/index.tsx:121 — index.Button::getBackgroundColorHover has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (18 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. This shape REPEATS in the file: 3 other methods here (index.Button, index.Button::getBackgroundColorClick, index.Button::getSvgColor) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 4 times rather than 4 independent problems. Splitting this body alone leaves the other 3 exactly as they are. Where these are variations on one operation, the change that clears all 4 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.
R7 · Dead Code · Dead file (~9 LoC) · ×3
  • Dead file (~9 LoC) src/features/meetings/no_schedule/useNoSchedule.tsx — no import path from any entry point (129 application, 9 tooling, 5 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/features/meetings/no_schedule/index.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
  • Dead file (~9 LoC) src/features/meetings/schedule_range_selector/index.types.ts — no import path from any entry point (129 application, 9 tooling, 5 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (src/features/meetings/schedule_range_selector/index.tsx, src/features/meetings/schedule_range_selector/useScheduleRangeSelector.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
  • Dead file (~9 LoC) src/services/states/user_field_service_reports.ts — no import path from any entry point (129 application, 9 tooling, 5 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
AC2 · Forms & labels · <Select> field component without a label · ×2
  • <Select> field component without a label src/features/language_group_selector/index.tsx:27 — This UI-library field component has no label / aria-label / aria-labelledby / id, and nothing written inside it here carries one either (a name prop is the form-submission key, not a label; an id alone, wherever it is set, names nothing until a label points at it). The text inside it does not stand in for one: these compound APIs render a trigger with role="combobox" (or role="button"), and those roles take their name from the AUTHOR, not from their content — so the words on screen never reach the accessibility tree as a name. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
  • <Select> field component without a label src/features/reports/field_service/selector_stats/person_filter/index.tsx:22 — This UI-library field component has no label / aria-label / aria-labelledby / id, and nothing written inside it here carries one either (a name prop is the form-submission key, not a label; an id alone, wherever it is set, names nothing until a label points at it). The text inside it does not stand in for one: these compound APIs render a trigger with role="combobox" (or role="button"), and those roles take their name from the AUTHOR, not from their content — so the words on screen never reach the accessibility tree as a name. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
AC2 · Forms & labels · <DatePicker> field component without a label · ×2
  • <DatePicker> field component without a label src/features/ministry/application_form/body/index.tsx:100 — This UI-library field component has no label / aria-label / aria-labelledby / id at this call site, and nothing written inside it here carries one either (a name prop is the form-submission key, not a label; an id, even one the component sets on what it renders, names nothing until a label points at it) — so it likely renders an unlabelled control. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
  • <DatePicker> field component without a label src/features/ministry/report/report_form_dialog/service_time/index.tsx:89 — This UI-library field component has no label / aria-label / aria-labelledby / id at this call site, and nothing written inside it here carries one either (a name prop is the form-submission key, not a label; an id, even one the component sets on what it renders, names nothing until a label points at it) — so it likely renders an unlabelled control. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
R10 · Code Duplication · Duplication concentrated across 3 sibling directories (6 clone groups) · ×2
  • Duplication concentrated across 3 sibling directories (6 clone groups) src/features/app_start/vip/congregation_create/congregation_access_code/index.tsx:68 — 6 of the duplicated blocks reported below have copies in at least two of the sibling directories congregation_access_code, congregation_details, congregation_master_key under src/features/app_start/vip/congregation_create/. That concentration is one structural fact, not 6 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 6 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
  • Duplication concentrated across 3 sibling directories (6 clone groups) src/features/meetings/weekly_schedules/midweek_meeting/ministry_part/part_row/usePartRow.tsx:49 — 6 of the duplicated blocks reported below have copies in at least two of the sibling directories living_part, ministry_part, treasures_part under src/features/meetings/weekly_schedules/midweek_meeting/. That concentration is one structural fact, not 6 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 6 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
R10 · Code Duplication · Duplication concentrated across 5 sibling directories (5 clone groups) · ×2
  • Duplication concentrated across 5 sibling directories (5 clone groups) src/features/congregation/settings/meeting_forms/date_format/useDateFormat.tsx:30 — 5 duplicated blocks under src/features/congregation/settings/meeting_forms/ have copies in at least two of the sibling directories date_format, display_name, midweek_exact_date, name_format, songs_weekend — 0 of them are reported below, and 5 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 5 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 5 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 5 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
  • Duplication concentrated across 5 sibling directories (5 clone groups) src/features/my_profile/security/mfaDisable/useMFADisable.tsx:26 — 5 duplicated blocks under src/features/my_profile/ have copies in at least two of the sibling directories app_settings, ministry_preferences, security, sessions, user_profile_details — 4 of them are reported below, and 1 is counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 5 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 5 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 5 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
R11 · Import Boundaries · Boundary violation [package · ×2
  • Boundary violation [package:third-party-deep-import] src/components/date_picker/index.styles.ts:7 — src/components/date_picker/index.styles.ts:7 imports @mui/x-date-pickers/internals, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
  • Boundary violation [package:third-party-deep-import] src/services/validator/index.ts:1 — src/services/validator/index.ts:1 imports validator/lib/isEmail, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 24, cognitive 23) · ×2
  • Complex function (anonymous) (cyclomatic 24, cognitive 23) src/features/congregation/settings/import_export/confirm_import/useConfirmImport.tsx:351 — (anonymous) has cyclomatic complexity 24 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.
  • Complex function (anonymous) (cyclomatic 24, cognitive 23) src/views/meetings/midweek/S140/app_normal/index.tsx:37 — (anonymous) has cyclomatic complexity 24 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.
R7 · Dead Code · Dead file (~20 LoC) · ×2
  • Dead file (~20 LoC) src/features/ministry/application_form/footer/index.tsx — no import path from any entry point (129 application, 9 tooling, 5 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
  • Dead file (~20 LoC) src/views/reports/S21/1in1/index.tsx — no import path from any entry point (129 application, 9 tooling, 5 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 (~5 LoC) · ×2
  • Dead file (~5 LoC) src/components/feature_flag/index.types.ts — no import path from any entry point (129 application, 9 tooling, 5 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (src/components/feature_flag/index.tsx, src/components/feature_flag/useFeatureFlag.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
  • Dead file (~5 LoC) src/features/reports/publisher_records_details/report_details/credit_field/index.types.ts — no import path from any entry point (129 application, 9 tooling, 5 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
AC2 · Forms & labels · <TimeField> field component without a label · ×1
  • <TimeField> field component without a label src/features/ministry/report/hours_editor/index.tsx:22 — This UI-library field component has no label / aria-label / aria-labelledby / id at this call site, and nothing written inside it here carries one either (a name prop is the form-submission key, not a label; an id, even one the component sets on what it renders, names nothing until a label points at it) — so it likely renders an unlabelled control. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
AC2 · Forms & labels · <TimePicker> field component without a label · ×1
  • <TimePicker> field component without a label src/features/persons/speakers_catalog/other_congregations/meeting_time/index.tsx:40 — This UI-library field component has no label / aria-label / aria-labelledby / id at this call site, and nothing written inside it here carries one either (a name prop is the form-submission key, not a label; an id, even one the component sets on what it renders, names nothing until a label points at it) — so it likely renders an unlabelled control. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
AC3 · Page structure · Page without a main landmark · ×1
  • Page without a main landmark 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>.
AC6 · Visual & motion safety · Focus outline removed in CSS without a · ×1
  • Focus outline removed in CSS without a :focus replacement index.html:415 — `noscript .variant-main` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
AC6 · Visual & motion safety · Animation without a prefers-reduced-motion guard · ×1
  • Animation without a prefers-reduced-motion guard src/features/reports/meeting_attendance/monthly_record/clicker_mode/animated_count/index.tsx:181 — `current.animate()` moves (`Web Animations API keyframes`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
AX7 · Slice cohesion · Cross-slice coupling · ×1
  • Cross-slice coupling: persons → congregation src/features/persons/basic_info/useBasicInfo.tsx:33 — `useBasicInfo` (slice 'persons') depends on `UsersOption` from slice 'congregation'.
D1 · Cyclomatic Complexity · schedules.schedulesMidweekInfo (cyclomatic 116) · ×1
  • schedules.schedulesMidweekInfo (cyclomatic 116) src/services/app/schedules.ts:139 — schedules.schedulesMidweekInfo has cyclomatic complexity 116 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · index.Button (cyclomatic 90) · ×1
  • index.Button (cyclomatic 90) src/components/button/index.tsx:10 — index.Button has cyclomatic complexity 90 (threshold 15). Of this number, 42 points are the body's own statements and 48 belong to 7 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 · dev.importDummyPersons (cyclomatic 86) · ×1
  • dev.importDummyPersons (cyclomatic 86) src/utils/dev.ts:67 — dev.importDummyPersons has cyclomatic complexity 86 (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 · backupUtils.dbExportDataBackup (cyclomatic 85) · ×1
  • backupUtils.dbExportDataBackup (cyclomatic 85) src/services/worker/backupUtils.ts:1757 — backupUtils.dbExportDataBackup has cyclomatic complexity 85 (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 · index.WeekendEditor (cyclomatic 68) · ×1
  • index.WeekendEditor (cyclomatic 68) src/features/meetings/weekend_editor/index.tsx:53 — index.WeekendEditor has cyclomatic complexity 68 (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 · useImportHourglass.useHourglassImport.migrateHourglassPersons (cyclomatic 55) · ×1
  • useImportHourglass.useHourglassImport.migrateHourglassPersons (cyclomatic 55) src/features/congregation/settings/import_export/confirm_import/useImportHourglass.jsx:21 — useImportHourglass.useHourglassImport.migrateHourglassPersons has cyclomatic complexity 55 (threshold 15). Most of this is not in the body itself: 2 of the 55 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 28, 327). 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 · index.MidweekEditor (cyclomatic 55) · ×1
  • index.MidweekEditor (cyclomatic 55) src/features/meetings/midweek_editor/index.tsx:58 — index.MidweekEditor has cyclomatic complexity 55 (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 · index.MonthlyView (cyclomatic 50) · ×1
  • index.MonthlyView (cyclomatic 50) src/features/meetings/monthly_view/index.tsx:26 — index.MonthlyView has cyclomatic complexity 50 (threshold 15). Of this number, 19 points are the body's own statements and 31 belong to 16 function literals inside it that branch. 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 · persons.applyGroupFilters (cyclomatic 50) · ×1
  • persons.applyGroupFilters (cyclomatic 50) src/services/app/persons.ts:544 — persons.applyGroupFilters has cyclomatic complexity 50 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · schedules.schedulesMidweekData (cyclomatic 50) · ×1
  • schedules.schedulesMidweekData (cyclomatic 50) src/services/app/schedules.ts:2047 — schedules.schedulesMidweekData has cyclomatic complexity 50 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · useUserAutoLogin.useUserAutoLogin (cyclomatic 44) · ×1
  • useUserAutoLogin.useUserAutoLogin (cyclomatic 44) src/hooks/useUserAutoLogin.tsx:33 — useUserAutoLogin.useUserAutoLogin has cyclomatic complexity 44 (threshold 15). Most of this is not in the body itself: 1 of the 44 points is its own statement and the rest belongs to 6 function literals inside it that branch (lines 98, 239, 52, …). 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 · index.TextField (cyclomatic 44) · ×1
  • index.TextField (cyclomatic 44) src/components/textfield/index.tsx:16 — index.TextField has cyclomatic complexity 44 (threshold 15). Of this number, 42 points are the body's own statements and 2 belong to one function literal inside it that branches. 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 · useMeetingPart.useMeetingPart (cyclomatic 39) · ×1
  • useMeetingPart.useMeetingPart (cyclomatic 39) src/features/meetings/meeting_part/useMeetingPart.tsx:9 — useMeetingPart.useMeetingPart has cyclomatic complexity 39 (threshold 15). Most of this is not in the body itself: 1 of the 39 points is its own statement and the rest belongs to one function literal inside it that branches (line 189). The decisions are inside the literal, 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 literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
D1 · Cyclomatic Complexity · schedules.schedulesGetHistoryDetails (cyclomatic 39) · ×1
  • schedules.schedulesGetHistoryDetails (cyclomatic 39) src/services/app/schedules.ts:854 — schedules.schedulesGetHistoryDetails 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 · index.NavBar (cyclomatic 38) · ×1
  • index.NavBar (cyclomatic 38) src/layouts/navbar/index.tsx:60 — index.NavBar has cyclomatic complexity 38 (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 · useConfirmImport.useConfirmImport.handleImportData (cyclomatic 37) · ×1
  • useConfirmImport.useConfirmImport.handleImportData (cyclomatic 37) src/features/congregation/settings/import_export/confirm_import/useConfirmImport.tsx:520 — useConfirmImport.useConfirmImport.handleImportData has cyclomatic complexity 37 (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 · useExportSpeakers.useExportSpeakers.getCongregationValue (cyclomatic 37) · ×1
  • useExportSpeakers.useExportSpeakers.getCongregationValue (cyclomatic 37) src/features/persons/speakers_catalog/import_export/export/useExportSpeakers.tsx:137 — useExportSpeakers.useExportSpeakers.getCongregationValue has cyclomatic complexity 37 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
D1 · Cyclomatic Complexity · schedules.schedulesWeekendInfo (cyclomatic 36) · ×1
  • schedules.schedulesWeekendInfo (cyclomatic 36) src/services/app/schedules.ts:602 — schedules.schedulesWeekendInfo has cyclomatic complexity 36 (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 · useStartup.useStartup (cyclomatic 35) · ×1
  • useStartup.useStartup (cyclomatic 35) src/features/app_start/vip/startup/useStartup.tsx:37 — useStartup.useStartup has cyclomatic complexity 35 (threshold 15). Most of this is not in the body itself: 1 of the 35 points is its own statement and the rest belongs to 2 function literals inside it that branch (lines 72, 221). 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 · usePersonComponent.usePersonComponent.personData (cyclomatic 33) · ×1
  • usePersonComponent.usePersonComponent.personData (cyclomatic 33) src/features/meetings/weekly_schedules/person_component/usePersonComponent.tsx:62 — usePersonComponent.usePersonComponent.personData has cyclomatic complexity 33 (threshold 15). Of this number, 32 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 · schedules.schedulesWeekendData (cyclomatic 33) · ×1
  • schedules.schedulesWeekendData (cyclomatic 33) src/services/app/schedules.ts:2497 — schedules.schedulesWeekendData 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 · backupUtils.syncFromRemote (cyclomatic 30) · ×1
  • backupUtils.syncFromRemote (cyclomatic 30) src/services/worker/backupUtils.ts:161 — backupUtils.syncFromRemote has cyclomatic complexity 30 (threshold 15). Of this number, 25 points are the body's own statements and 5 belong to 3 function literals 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 · index.DatePicker (cyclomatic 29) · ×1
  • index.DatePicker (cyclomatic 29) src/components/date_picker/index.tsx:23 — index.DatePicker has cyclomatic complexity 29 (threshold 15). Most of this is not in the body itself: 7 of the 29 points are its own statements and the rest belongs to 7 function items inside it that branch (handleValueChange, a function literal at line 111, handleKeyDown, …). 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 · useStudentSelector.useStudentSelector.options (cyclomatic 29) · ×1
  • useStudentSelector.useStudentSelector.options (cyclomatic 29) src/features/meetings/person_selector/student_selector/useStudentSelector.tsx:199 — useStudentSelector.useStudentSelector.options has cyclomatic complexity 29 (threshold 15). Most of this is not in the body itself: 2 of the 29 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 202, 263, 237). 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 · assignment_selection.sortCandidatesMultiLevel (cyclomatic 29) · ×1
  • assignment_selection.sortCandidatesMultiLevel (cyclomatic 29) src/services/app/assignment_selection.ts:812 — assignment_selection.sortCandidatesMultiLevel has cyclomatic complexity 29 (threshold 15). Most of this is not in the body itself: 10 of the 29 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 831, 959). 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 · usePerson.usePerson.getBadges (cyclomatic 28) · ×1
  • usePerson.usePerson.getBadges (cyclomatic 28) src/features/persons/hooks/usePerson.tsx:195 — usePerson.usePerson.getBadges 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 · index.ExportSpeakers (cyclomatic 28) · ×1
  • index.ExportSpeakers (cyclomatic 28) src/features/persons/speakers_catalog/import_export/export/index.tsx:18 — index.ExportSpeakers has cyclomatic complexity 28 (threshold 15). Of this number, 14 points are the body's own statements and 14 belong to 7 function items inside it that branch. 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 · index.MidweekMeeting (cyclomatic 26) · ×1
  • index.MidweekMeeting (cyclomatic 26) src/features/meetings/weekly_schedules/midweek_meeting/index.tsx:27 — index.MidweekMeeting 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.
D1 · Cyclomatic Complexity · index.EditUpcomingEvent (cyclomatic 25) · ×1
  • index.EditUpcomingEvent (cyclomatic 25) src/features/activities/upcoming_events/edit_upcoming_event/index.tsx:24 — index.EditUpcomingEvent has cyclomatic complexity 25 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · useBrotherSelector.useBrotherSelector.options (cyclomatic 25) · ×1
  • useBrotherSelector.useBrotherSelector.options (cyclomatic 25) src/features/meetings/person_selector/brother_selector/useBrotherSelector.tsx:157 — useBrotherSelector.useBrotherSelector.options has cyclomatic complexity 25 (threshold 15). Most of this is not in the body itself: 1 of the 25 points is its own statement and the rest belongs to 5 function literals inside it that branch (lines 158, 273, 160, …). 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 · index.InfoMessage (cyclomatic 24) · ×1
  • index.InfoMessage (cyclomatic 24) src/components/info-message/index.tsx:14 — index.InfoMessage has cyclomatic complexity 24 (threshold 15). Of this number, 18 points are the body's own statements and 6 belong to 2 function items inside it that branch. 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 · useConfirmImport.useConfirmImport.selectedAll (cyclomatic 24) · ×1
  • useConfirmImport.useConfirmImport.selectedAll (cyclomatic 24) src/features/congregation/settings/import_export/confirm_import/useConfirmImport.tsx:351 — useConfirmImport.useConfirmImport.selectedAll 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 · index.StudentSelector (cyclomatic 24) · ×1
  • index.StudentSelector (cyclomatic 24) src/features/meetings/person_selector/student_selector/index.tsx:32 — index.StudentSelector has cyclomatic complexity 24 (threshold 15). Of this number, 19 points are the body's own statements and 5 belong 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 · usePersonCard.usePersonCard.getPersonBadge (cyclomatic 24) · ×1
  • usePersonCard.usePersonCard.getPersonBadge (cyclomatic 24) src/features/persons/list/person_card/usePersonCard.tsx:36 — usePersonCard.usePersonCard.getPersonBadge has cyclomatic complexity 24 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · index.TemplateS140AppNormal (cyclomatic 24) · ×1
  • index.TemplateS140AppNormal (cyclomatic 24) src/views/meetings/midweek/S140/app_normal/index.tsx:25 — index.TemplateS140AppNormal has cyclomatic complexity 24 (threshold 15). Most of this is not in the body itself: 1 of the 24 points is its own statement and the rest belongs to one function literal inside it that branches (line 37). The decisions are inside the literal, 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 literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
D1 · Cyclomatic Complexity · index.Dialog (cyclomatic 23) · ×1
  • index.Dialog (cyclomatic 23) src/components/dialog/index.tsx:78 — index.Dialog has cyclomatic complexity 23 (threshold 15). Of this number, 19 points are the body's own statements and 4 belong to 2 function items inside it that branch. 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 · backupUtils.dbGetMetadata (cyclomatic 23) · ×1
  • backupUtils.dbGetMetadata (cyclomatic 23) src/services/worker/backupUtils.ts:332 — backupUtils.dbGetMetadata 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 · backupAction.runBackup (cyclomatic 23) · ×1
  • backupAction.runBackup (cyclomatic 23) src/services/worker/backupAction.ts:36 — backupAction.runBackup 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 · common.updateObject (cyclomatic 23) · ×1
  • common.updateObject (cyclomatic 23) src/utils/common.ts:104 — common.updateObject has cyclomatic complexity 23 (threshold 15). Of this number, 20 points are the body's own statements and 3 belong to 2 function literals 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 · index.ScheduleS140 (cyclomatic 23) · ×1
  • index.ScheduleS140 (cyclomatic 23) src/views/meetings/midweek/S140/default/index.tsx:23 — index.ScheduleS140 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, 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 · useWebWorker.useWebWorker (cyclomatic 23) · ×1
  • useWebWorker.useWebWorker (cyclomatic 23) src/wrapper/web_worker/useWebWorker.tsx:32 — useWebWorker.useWebWorker has cyclomatic complexity 23 (threshold 15). Most of this is not in the body itself: 4 of the 23 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 130, 58, 102, …). 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 · useBrotherSelector.useBrotherSelector.value (cyclomatic 22) · ×1
  • useBrotherSelector.useBrotherSelector.value (cyclomatic 22) src/features/meetings/person_selector/brother_selector/useBrotherSelector.tsx:311 — useBrotherSelector.useBrotherSelector.value has cyclomatic complexity 22 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · useSubmitReport.useSubmitReport.handleSubmit (cyclomatic 22) · ×1
  • useSubmitReport.useSubmitReport.handleSubmit (cyclomatic 22) src/features/ministry/report/form_S4/submit_report/useSubmitReport.tsx:250 — useSubmitReport.useSubmitReport.handleSubmit has cyclomatic complexity 22 (threshold 15). Of this number, 14 points are the body's own statements and 8 belong to 4 function literals 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 · index.RootLayout (cyclomatic 22) · ×1
  • index.RootLayout (cyclomatic 22) src/layouts/root_layout/index.tsx:32 — index.RootLayout has cyclomatic complexity 22 (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 · index.LivingPart (cyclomatic 21) · ×1
  • index.LivingPart (cyclomatic 21) src/features/meetings/weekly_schedules/midweek_meeting/living_part/index.tsx:23 — index.LivingPart 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 · useSpeakerEditPopup.useSpeakerEditPopup.handleSave (cyclomatic 21) · ×1
  • useSpeakerEditPopup.useSpeakerEditPopup.handleSave (cyclomatic 21) src/features/persons/speakers_catalog/speaker_edit_popup/useSpeakerEditPopup.tsx:343 — useSpeakerEditPopup.useSpeakerEditPopup.handleSave has cyclomatic complexity 21 (threshold 15). Of this number, 20 points are the body's own statements and 1 belongs to one function item 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 · sources.sourcesPartTiming (cyclomatic 21) · ×1
  • sources.sourcesPartTiming (cyclomatic 21) REDACTED:493 — sources.sourcesPartTiming 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.
D1 · Cyclomatic Complexity · autofill.getTasksArray (cyclomatic 21) · ×1
  • autofill.getTasksArray (cyclomatic 21) src/services/app/autofill.ts:743 — autofill.getTasksArray has cyclomatic complexity 21 (threshold 15). Most of this is not in the body itself: 2 of the 21 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 805, 766, 777, …). 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 · persons.dbPersonsSave (cyclomatic 21) · ×1
  • persons.dbPersonsSave (cyclomatic 21) src/services/dexie/persons.ts:21 — persons.dbPersonsSave has cyclomatic complexity 21 (threshold 15). Of this number, 15 points are the body's own statements and 6 belong to 6 function literals 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 · index.Checkbox (cyclomatic 20) · ×1
  • index.Checkbox (cyclomatic 20) src/components/checkbox/index.tsx:19 — index.Checkbox 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 · useGroupDelete.useGroupDelete.handleDelete (cyclomatic 20) · ×1
  • useGroupDelete.useGroupDelete.handleDelete (cyclomatic 20) src/features/congregation/settings/language_groups/group_delete/useGroupDelete.tsx:39 — useGroupDelete.useGroupDelete.handleDelete 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 · useHoursCredits.useHoursCredits.handleSelectPreset (cyclomatic 20) · ×1
  • useHoursCredits.useHoursCredits.handleSelectPreset (cyclomatic 20) src/features/ministry/report/form_S4/hours_credits/useHoursCredits.tsx:185 — useHoursCredits.useHoursCredits.handleSelectPreset has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · index.MonthItem (cyclomatic 20) · ×1
  • index.MonthItem (cyclomatic 20) src/features/ministry/service_year/monthly_stats/month_item/index.tsx:9 — index.MonthItem 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 · useWeekBox.useWeekBox (cyclomatic 20) · ×1
  • useWeekBox.useWeekBox (cyclomatic 20) src/features/reports/meeting_attendance/monthly_record/week_box/useWeekBox.tsx:51 — useWeekBox.useWeekBox has cyclomatic complexity 20 (threshold 15). Of this number, 19 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 · backupUtils.dbRestoreSettings (cyclomatic 20) · ×1
  • backupUtils.dbRestoreSettings (cyclomatic 20) src/services/worker/backupUtils.ts:663 — backupUtils.dbRestoreSettings has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · backupUtils.dbRestoreSchedules (cyclomatic 20) · ×1
  • backupUtils.dbRestoreSchedules (cyclomatic 20) src/services/worker/backupUtils.ts:1507 — backupUtils.dbRestoreSchedules has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · index.AssignmentCheckList (cyclomatic 19) · ×1
  • index.AssignmentCheckList (cyclomatic 19) src/components/assignments_checklist/index.tsx:25 — index.AssignmentCheckList has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 6 of the 19 points are its own statements and the rest belongs to 7 function items inside it that branch (a function literal at line 87, a function literal at line 47, a function literal at line 65, …). 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 · index.ScheduleItem (cyclomatic 19) · ×1
  • index.ScheduleItem (cyclomatic 19) src/features/meetings/outgoing_talks/schedule_item/index.tsx:28 — index.ScheduleItem 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 · index.CommitteeMember (cyclomatic 19) · ×1
  • index.CommitteeMember (cyclomatic 19) src/features/ministry/application_form/sc_member/index.tsx:13 — index.CommitteeMember 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 · useExportSpeakers.useExportSpeakers.handleExport (cyclomatic 19) · ×1
  • useExportSpeakers.useExportSpeakers.handleExport (cyclomatic 19) src/features/persons/speakers_catalog/import_export/export/useExportSpeakers.tsx:304 — useExportSpeakers.useExportSpeakers.handleExport has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 5 of the 19 points are its own statements and the rest belongs to 6 function items inside it that branch (a function literal at line 345, a function literal at line 380, a function literal at line 318, …). 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 · useSpiritualStatus.useSpiritualStatus.handleToggleBaptizedPublisher (cyclomatic 19) · ×1
  • useSpiritualStatus.useSpiritualStatus.handleToggleBaptizedPublisher (cyclomatic 19) src/features/persons/spiritual_status/useSpiritualStatus.tsx:209 — useSpiritualStatus.useSpiritualStatus.handleToggleBaptizedPublisher has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · index.MonthItem (cyclomatic 19) · ×1
  • index.MonthItem (cyclomatic 19) src/features/reports/publisher_records_details/month_item/index.tsx:18 — index.MonthItem 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 · schedules.schedulesS89Data (cyclomatic 19) · ×1
  • schedules.schedulesS89Data (cyclomatic 19) src/services/app/schedules.ts:1791 — schedules.schedulesS89Data has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · index.TimePicker (cyclomatic 18) · ×1
  • index.TimePicker (cyclomatic 18) src/components/time_picker/index.tsx:20 — index.TimePicker has cyclomatic complexity 18 (threshold 15). Of this number, 17 points are the body's own statements and 1 belongs to one function item inside it that branches. 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 · index.UpcomingEvent (cyclomatic 18) · ×1
  • index.UpcomingEvent (cyclomatic 18) src/features/activities/upcoming_events/upcoming_event/index.tsx:21 — index.UpcomingEvent has cyclomatic complexity 18 (threshold 15). Of this number, 16 points are the body's own statements and 2 belong 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 · index.PersonSelect (cyclomatic 18) · ×1
  • index.PersonSelect (cyclomatic 18) src/features/congregation/app_access/user_add/person_select/index.tsx:14 — index.PersonSelect 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 · usePartDuration.usePartDuration.handleChangeDuration (cyclomatic 18) · ×1
  • usePartDuration.usePartDuration.handleChangeDuration (cyclomatic 18) src/features/meetings/part_duration/usePartDuration.tsx:19 — usePartDuration.usePartDuration.handleChangeDuration 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 · usePublicTalkSelector.usePublicTalkSelector.talks (cyclomatic 18) · ×1
  • usePublicTalkSelector.usePublicTalkSelector.talks (cyclomatic 18) src/features/meetings/weekend_editor/public_talk_selector/usePublicTalkSelector.tsx:37 — usePublicTalkSelector.usePublicTalkSelector.talks has cyclomatic complexity 18 (threshold 15). Of this number, 16 points are the body's own statements and 2 belong to 2 function literals 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 · index.PublicTalkSelector (cyclomatic 18) · ×1
  • index.PublicTalkSelector (cyclomatic 18) src/features/meetings/weekend_editor/public_talk_selector/index.tsx:12 — index.PublicTalkSelector has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 6 of the 18 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 62, 48). 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 · useBibleStudies.useBibleStudies.handleBibleStudyChange (cyclomatic 18) · ×1
  • useBibleStudies.useBibleStudies.handleBibleStudyChange (cyclomatic 18) src/features/ministry/report/form_S4/bible_studies/useBibleStudies.tsx:115 — useBibleStudies.useBibleStudies.handleBibleStudyChange 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 · useApplicationPerson.useApplicationPerson.handleApprovalChange (cyclomatic 18) · ×1
  • useApplicationPerson.useApplicationPerson.handleApprovalChange (cyclomatic 18) src/features/persons/application_person/useApplicationPerson.tsx:168 — useApplicationPerson.useApplicationPerson.handleApprovalChange 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 · useAssignmentGroup.useAssignmentGroup.checkAssignmentDisabled (cyclomatic 18) · ×1
  • useAssignmentGroup.useAssignmentGroup.checkAssignmentDisabled (cyclomatic 18) src/features/persons/assignment_group/useAssignmentGroup.tsx:42 — useAssignmentGroup.useAssignmentGroup.checkAssignmentDisabled 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 · index.OutgoingSpeakersHeader (cyclomatic 18) · ×1
  • index.OutgoingSpeakersHeader (cyclomatic 18) src/features/persons/speakers_catalog/my_congregation/header/index.tsx:20 — index.OutgoingSpeakersHeader 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 · usePersonsList.usePersonsList.handleAddRandomData (cyclomatic 18) · ×1
  • usePersonsList.usePersonsList.handleAddRandomData (cyclomatic 18) src/features/reports/field_service/persons_list/usePersonsList.tsx:307 — usePersonsList.usePersonsList.handleAddRandomData has cyclomatic complexity 18 (threshold 15). Of this number, 17 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 · autofill.processAssignmentSettings (cyclomatic 18) · ×1
  • autofill.processAssignmentSettings (cyclomatic 18) src/services/app/autofill.ts:228 — autofill.processAssignmentSettings has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 3 of the 18 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 274, 239, 305). 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 · assignment_selection.hasAssignmentConflict (cyclomatic 18) · ×1
  • assignment_selection.hasAssignmentConflict (cyclomatic 18) src/services/app/assignment_selection.ts:1129 — assignment_selection.hasAssignmentConflict has cyclomatic complexity 18 (threshold 15). Of this number, 15 points are the body's own statements and 3 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 · assignments.checkAssignmentUnappliable (cyclomatic 18) · ×1
  • assignments.checkAssignmentUnappliable (cyclomatic 18) src/utils/assignments.ts:53 — assignments.checkAssignmentUnappliable 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 · dev.dbReportsFillRandom (cyclomatic 18) · ×1
  • dev.dbReportsFillRandom (cyclomatic 18) src/utils/dev.ts:982 — dev.dbReportsFillRandom 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 · useTimeField.useTimeField.handleArrowWheel (cyclomatic 17) · ×1
  • useTimeField.useTimeField.handleArrowWheel (cyclomatic 17) src/components/timefield/useTimeField.tsx:104 — useTimeField.useTimeField.handleArrowWheel 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 · useConfirmImport.useConfirmImport.handleSelectAll (cyclomatic 17) · ×1
  • useConfirmImport.useConfirmImport.handleSelectAll (cyclomatic 17) src/features/congregation/settings/import_export/confirm_import/useConfirmImport.tsx:425 — useConfirmImport.useConfirmImport.handleSelectAll has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 5 of the 17 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 439, 427). 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 · index.BrotherSelector (cyclomatic 17) · ×1
  • index.BrotherSelector (cyclomatic 17) src/features/meetings/person_selector/brother_selector/index.tsx:16 — index.BrotherSelector has cyclomatic complexity 17 (threshold 15). Of this number, 16 points are the body's own statements and 1 belongs to one function literal inside it that branches. 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 · useMonthlyView.useMonthlyView (cyclomatic 17) · ×1
  • useMonthlyView.useMonthlyView (cyclomatic 17) src/features/meetings/monthly_view/useMonthlyView.tsx:30 — useMonthlyView.useMonthlyView has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 1 of the 17 points is its own statement and the rest belongs to 6 function literals inside it that branch (lines 330, 368, 234, …). 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 · index.WeekendMeeting (cyclomatic 17) · ×1
  • index.WeekendMeeting (cyclomatic 17) src/features/meetings/weekly_schedules/weekend_meeting/index.tsx:21 — index.WeekendMeeting 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 · useHoursCredits.useHoursCredits.handleHoursChange (cyclomatic 17) · ×1
  • useHoursCredits.useHoursCredits.handleHoursChange (cyclomatic 17) src/features/ministry/report/form_S4/hours_credits/useHoursCredits.tsx:80 — useHoursCredits.useHoursCredits.handleHoursChange 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 · useWithdrawReport.useWithdrawReport.handleWithdrawal (cyclomatic 17) · ×1
  • useWithdrawReport.useWithdrawReport.handleWithdrawal (cyclomatic 17) src/features/ministry/report/form_S4/withdraw_report/useWithdrawReport.tsx:87 — useWithdrawReport.useWithdrawReport.handleWithdrawal 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 · index.SpeakersList (cyclomatic 17) · ×1
  • index.SpeakersList (cyclomatic 17) src/features/persons/speakers_catalog/other_congregations/speakers_list/index.tsx:12 — index.SpeakersList has cyclomatic complexity 17 (threshold 15). Of this number, 16 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 · cong_field_service_reports.dbHandleIncomingReports (cyclomatic 17) · ×1
  • cong_field_service_reports.dbHandleIncomingReports (cyclomatic 17) src/services/dexie/cong_field_service_reports.ts:33 — cong_field_service_reports.dbHandleIncomingReports has cyclomatic complexity 17 (threshold 15). Of this number, 15 points are the body's own statements and 2 belong to 2 function literals 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 · index.DateNavigator (cyclomatic 16) · ×1
  • index.DateNavigator (cyclomatic 16) src/components/date_navigator/index.tsx:55 — index.DateNavigator has cyclomatic complexity 16 (threshold 15). Of this number, 10 points are the body's own statements and 6 belong to 4 function items inside it that branch. 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 · index.VipStartup (cyclomatic 16) · ×1
  • index.VipStartup (cyclomatic 16) src/features/app_start/vip/startup/index.tsx:12 — index.VipStartup has cyclomatic complexity 16 (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 · useUserDetails.useUserDetails.handleSaveDetails (cyclomatic 16) · ×1
  • useUserDetails.useUserDetails.handleSaveDetails (cyclomatic 16) src/features/congregation/app_access/user_details/useUserDetails.tsx:34 — useUserDetails.useUserDetails.handleSaveDetails has cyclomatic complexity 16 (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 · useHoursFields.useHoursFields.handleHoursChange (cyclomatic 16) · ×1
  • useHoursFields.useHoursFields.handleHoursChange (cyclomatic 16) src/features/ministry/report/form_S4/hours_fields/useHoursFields.tsx:111 — useHoursFields.useHoursFields.handleHoursChange 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 · usePioneerStats.usePioneerStats.hours_balance (cyclomatic 16) · ×1
  • usePioneerStats.usePioneerStats.hours_balance (cyclomatic 16) src/features/ministry/service_year/yearly_stats/pioneer_stats/usePioneerStats.tsx:112 — usePioneerStats.usePioneerStats.hours_balance 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 · useNavbar.useNavbar.markLastNavBarButton (cyclomatic 16) · ×1
  • useNavbar.useNavbar.markLastNavBarButton (cyclomatic 16) src/layouts/navbar/useNavbar.tsx:174 — useNavbar.useNavbar.markLastNavBarButton has cyclomatic complexity 16 (threshold 15). Of this number, 8 points are the body's own statements and 8 belong to 2 function literals 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 · autofill.getSortedTasks (cyclomatic 16) · ×1
  • autofill.getSortedTasks (cyclomatic 16) src/services/app/autofill.ts:962 — autofill.getSortedTasks has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 1 of the 16 points is its own statement and the rest belongs to 3 function items inside it that branch (a function literal at line 994, getBaseKey, a function literal at line 980). 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 · user_field_service_reports.refreshSharedMinistry (cyclomatic 16) · ×1
  • user_field_service_reports.refreshSharedMinistry (cyclomatic 16) src/services/app/user_field_service_reports.ts:98 — user_field_service_reports.refreshSharedMinistry 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 · MeetingPart.MeetingPart (cyclomatic 16) · ×1
  • MeetingPart.MeetingPart (cyclomatic 16) src/views/meetings/weekend/MeetingPart.tsx:7 — MeetingPart.MeetingPart has cyclomatic complexity 16 (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.
D10 · Test Quality · No assertions · ×1
  • No assertions: passes cypress/e2e/spec.cy.ts:4 — 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.
D12 · Dependency Hygiene · Deprecated · ×1
  • Deprecated: eslint package.json:102 — eslint 9.39.2, declared in package.json, is marked deprecated by its publisher: "This version is no longer supported. Please see https://eslint.org/version-support for other options.". Replace it with the package or version that message names, or record why this one must stay.
D15 · Churn × Complexity Hotspots · Repeated repair · ×1
  • Repeated repair: src/components/icon_button/index.tsx src/components/icon_button/index.tsx:14 — src/components/icon_button/index.tsx changed 3 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 5 (its worst body is index.IconButton at line 14), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(ui): align the button hover and pressed states (#5517)”; “fix(ui): keep icon buttons round when a caller passes sx (#5500)”; “fix(ui): use accent colors for keyboard focus in menus and dropdowns (#5483)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 23:08:15 +00:00' --until='2026-11-16 23:08:15 +00:00' --full-history --no-merges -- src/components/icon_button/index.tsx`: 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.
D17 · Explicit Debt · TodoComment · ×1
  • TodoComment src/services/app/assignments_with_stats.ts:606 — // TODO(follow-up PR): `undefined` doubles as "not a variable part". — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
D2 · Cognitive Complexity · schedules.schedulesMidweekInfo (cognitive 283) · ×1
  • schedules.schedulesMidweekInfo (cognitive 283) src/services/app/schedules.ts:139 — schedules.schedulesMidweekInfo has cognitive complexity 283 (threshold 15). Drivers by points: if/else 75 (243 pts), boolean chains 30, ternaries 2 (6 pts), loops 2 (4 pts) (nesting depth added 174). 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 · backupUtils.dbExportDataBackup (cognitive 220) · ×1
  • backupUtils.dbExportDataBackup (cognitive 220) src/services/worker/backupUtils.ts:1757 — backupUtils.dbExportDataBackup has cognitive complexity 220 (threshold 15). Drivers by points: if/else 53 (184 pts), boolean chains 20, ternaries 2 (11 pts), loops 1 (4 pts), error handling 1 (nesting depth added 143). 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 · dev.importDummyPersons (cognitive 164) · ×1
  • dev.importDummyPersons (cognitive 164) src/utils/dev.ts:67 — dev.importDummyPersons has cognitive complexity 164 (threshold 15). Drivers by points: if/else 40 (131 pts), boolean chains 24, loops 4 (8 pts), error handling 1 (nesting depth added 95). To reduce it, split the body into named stages: move each independent 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 · persons.applyGroupFilters (cognitive 90) · ×1
  • persons.applyGroupFilters (cognitive 90) src/services/app/persons.ts:544 — persons.applyGroupFilters has cognitive complexity 90 (threshold 15). Drivers by points: if/else 23 (65 pts), boolean chains 23, loops 1 (2 pts) (nesting depth added 43). To reduce it, split the body into named stages: move each independent 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 · useMeetingPart.useMeetingPart (cognitive 75) · ×1
  • useMeetingPart.useMeetingPart (cognitive 75) src/features/meetings/meeting_part/useMeetingPart.tsx:9 — useMeetingPart.useMeetingPart has cognitive complexity 75 (threshold 15). Drivers by points: ternaries 13 (39 pts), if/else 12 (23 pts), boolean chains 13 (nesting depth added 37). None of this is in the body itself: all 75 points belong to one function literal inside it that branches (line 189). The decisions are inside the literal, 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 literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · schedules.schedulesMidweekData (cognitive 72) · ×1
  • schedules.schedulesMidweekData (cognitive 72) src/services/app/schedules.ts:2047 — schedules.schedulesMidweekData has cognitive complexity 72 (threshold 15). Drivers by points: if/else 33 (58 pts), boolean chains 9, ternaries 1 (3 pts), loops 2 (nesting depth added 27). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · backupUtils.syncFromRemote (cognitive 63) · ×1
  • backupUtils.syncFromRemote (cognitive 63) src/services/worker/backupUtils.ts:161 — backupUtils.syncFromRemote has cognitive complexity 63 (threshold 15). Drivers by points: if/else 14 (47 pts), boolean chains 8, loops 5 (8 pts) (nesting depth added 36). Of this number, 60 points are the body's own statements and 3 belong to 3 function literals inside it that branch. 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 · usePersonComponent.usePersonComponent.personData (cognitive 60) · ×1
  • usePersonComponent.usePersonComponent.personData (cognitive 60) src/features/meetings/weekly_schedules/person_component/usePersonComponent.tsx:62 — usePersonComponent.usePersonComponent.personData has cognitive complexity 60 (threshold 15). Drivers by points: if/else 20 (48 pts), boolean chains 9, ternaries 1 (3 pts) (nesting depth added 30). Of this number, 59 points are the body's own statements and 1 belongs to one function literal inside it that branches. 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 · common.updateObject (cognitive 60) · ×1
  • common.updateObject (cognitive 60) src/utils/common.ts:104 — common.updateObject has cognitive complexity 60 (threshold 15). Drivers by points: if/else 15 (49 pts), loops 5 (8 pts), boolean chains 3 (nesting depth added 37). Of this number, 58 points are the body's own statements and 2 belong to 2 function literals inside it that branch. 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 · schedules.schedulesWeekendInfo (cognitive 56) · ×1
  • schedules.schedulesWeekendInfo (cognitive 56) src/services/app/schedules.ts:602 — schedules.schedulesWeekendInfo has cognitive complexity 56 (threshold 15). Drivers by points: if/else 21 (41 pts), boolean chains 14, ternaries 1 (nesting depth added 20). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · schedules.schedulesGetHistoryDetails (cognitive 56) · ×1
  • schedules.schedulesGetHistoryDetails (cognitive 56) src/services/app/schedules.ts:854 — schedules.schedulesGetHistoryDetails has cognitive complexity 56 (threshold 15). Drivers by points: if/else 32 (43 pts), ternaries 2 (8 pts), boolean chains 5 (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 · schedules.schedulesWeekendData (cognitive 50) · ×1
  • schedules.schedulesWeekendData (cognitive 50) src/services/app/schedules.ts:2497 — schedules.schedulesWeekendData has cognitive complexity 50 (threshold 15). Drivers by points: if/else 26 (44 pts), boolean chains 6 (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 · useImportHourglass.useHourglassImport.migrateHourglassPersons (cognitive 49) · ×1
  • useImportHourglass.useHourglassImport.migrateHourglassPersons (cognitive 49) src/features/congregation/settings/import_export/confirm_import/useImportHourglass.jsx:21 — useImportHourglass.useHourglassImport.migrateHourglassPersons has cognitive complexity 49 (threshold 15). Drivers by points: if/else 27 (33 pts), ternaries 9, boolean chains 6, loops 1 (nesting depth added 6). Most of this is not in the body itself: 1 of the 49 points is its own statement and the rest belongs to 2 function literals inside it that branch (lines 28, 327). 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 · useUserAutoLogin.useUserAutoLogin (cognitive 47) · ×1
  • useUserAutoLogin.useUserAutoLogin (cognitive 47) src/hooks/useUserAutoLogin.tsx:33 — useUserAutoLogin.useUserAutoLogin has cognitive complexity 47 (threshold 15). Drivers by points: if/else 22 (34 pts), boolean chains 11, error handling 2 (nesting depth added 12). None of this is in the body itself: all 47 points belong to 6 function literals inside it that branch (lines 98, 239, 52, …). 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 · index.TextField (cognitive 45) · ×1
  • index.TextField (cognitive 45) src/components/textfield/index.tsx:16 — index.TextField has cognitive complexity 45 (threshold 15). Drivers by points: ternaries 27 (32 pts), boolean chains 9, if/else 4 (nesting depth added 5). Of this number, 43 points are the body's own statements and 2 belong 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 · useSpiritualStatus.useSpiritualStatus.handleToggleBaptizedPublisher (cognitive 44) · ×1
  • useSpiritualStatus.useSpiritualStatus.handleToggleBaptizedPublisher (cognitive 44) src/features/persons/spiritual_status/useSpiritualStatus.tsx:209 — useSpiritualStatus.useSpiritualStatus.handleToggleBaptizedPublisher has cognitive complexity 44 (threshold 15). Drivers by points: if/else 16 (42 pts), boolean chains 2 (nesting depth added 26). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
D2 · Cognitive Complexity · backupUtils.dbRestoreSchedules (cognitive 44) · ×1
  • backupUtils.dbRestoreSchedules (cognitive 44) src/services/worker/backupUtils.ts:1507 — backupUtils.dbRestoreSchedules has cognitive complexity 44 (threshold 15). Drivers by points: if/else 17 (42 pts), error handling 1, loops 1 (nesting depth added 25). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · backupAction.runBackup (cognitive 43) · ×1
  • backupAction.runBackup (cognitive 43) src/services/worker/backupAction.ts:36 — backupAction.runBackup has cognitive complexity 43 (threshold 15). Drivers by points: if/else 13 (33 pts), boolean chains 5, loops 2 (4 pts), error handling 1 (nesting depth added 22). To reduce it, split the body into named stages: move each independent 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 · schedules.schedulesS89Data (cognitive 41) · ×1
  • schedules.schedulesS89Data (cognitive 41) src/services/app/schedules.ts:1791 — schedules.schedulesS89Data has cognitive complexity 41 (threshold 15). Drivers by points: if/else 14 (38 pts), boolean chains 2, loops 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 · index.MonthlyView (cognitive 40) · ×1
  • index.MonthlyView (cognitive 40) src/features/meetings/monthly_view/index.tsx:26 — index.MonthlyView has cognitive complexity 40 (threshold 15). Drivers by points: boolean chains 23, ternaries 13 (17 pts) (nesting depth added 4). Of this number, 18 points are the body's own statements and 22 belong to 16 function literals inside it that branch. 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 · useConfirmImport.useConfirmImport.handleImportData (cognitive 39) · ×1
  • useConfirmImport.useConfirmImport.handleImportData (cognitive 39) src/features/congregation/settings/import_export/confirm_import/useConfirmImport.tsx:520 — useConfirmImport.useConfirmImport.handleImportData has cognitive complexity 39 (threshold 15). Drivers by points: if/else 32 (36 pts), boolean chains 2, error handling 1 (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
D2 · Cognitive Complexity · useTimeField.useTimeField.handleArrowWheel (cognitive 38) · ×1
  • useTimeField.useTimeField.handleArrowWheel (cognitive 38) src/components/timefield/useTimeField.tsx:104 — useTimeField.useTimeField.handleArrowWheel has cognitive complexity 38 (threshold 15). Drivers by points: if/else 14 (34 pts), ternaries 1 (3 pts), boolean chains 1 (nesting depth added 22). To reduce it, split the body into named stages: move each independent 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 · useSubmitReport.useSubmitReport.handleSubmit (cognitive 38) · ×1
  • useSubmitReport.useSubmitReport.handleSubmit (cognitive 38) src/features/ministry/report/form_S4/submit_report/useSubmitReport.tsx:250 — useSubmitReport.useSubmitReport.handleSubmit has cognitive complexity 38 (threshold 15). Drivers by points: if/else 17 (36 pts), boolean chains 2 (nesting depth added 19). Of this number, 18 points are the body's own statements and 20 belong to 4 function literals 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 · index.Button (cognitive 37) · ×1
  • index.Button (cognitive 37) src/components/button/index.tsx:10 — index.Button has cognitive complexity 37 (threshold 15). Drivers by points: if/else 50 (108 pts), boolean chains 20, ternaries 15 (nesting depth added 58). To reduce it, split the body into named stages: move each independent 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: 3 other methods here (index.Button::getBackgroundColorHover, index.Button::getBackgroundColorClick, index.Button::getSvgColor) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 4 times rather than 4 independent problems. Splitting this body alone leaves the other 3 exactly as they are. Where these are variations on one operation, the change that clears all 4 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 · useAssignments.useAssignments.handleToggleAssignment (cognitive 37) · ×1
  • useAssignments.useAssignments.handleToggleAssignment (cognitive 37) src/features/persons/assignments/useAssignments.tsx:326 — useAssignments.useAssignments.handleToggleAssignment has cognitive complexity 37 (threshold 15). Drivers by points: if/else 13 (33 pts), boolean chains 2, loops 1 (2 pts) (nesting depth added 21). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · persons.dbPersonsSave (cognitive 37) · ×1
  • persons.dbPersonsSave (cognitive 37) src/services/dexie/persons.ts:21 — persons.dbPersonsSave has cognitive complexity 37 (threshold 15). Drivers by points: if/else 14 (31 pts), boolean chains 6 (nesting depth added 17). Of this number, 31 points are the body's own statements and 6 belong to 6 function literals 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 · dev.dbReportsFillRandom (cognitive 37) · ×1
  • dev.dbReportsFillRandom (cognitive 37) src/utils/dev.ts:982 — dev.dbReportsFillRandom has cognitive complexity 37 (threshold 15). Drivers by points: if/else 9 (31 pts), boolean chains 3, loops 2 (3 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 · useStartup.useStartup (cognitive 35) · ×1
  • useStartup.useStartup (cognitive 35) src/features/app_start/vip/startup/useStartup.tsx:37 — useStartup.useStartup has cognitive complexity 35 (threshold 15). Drivers by points: if/else 15 (18 pts), boolean chains 16, error handling 1 (nesting depth added 3). None of this is in the body itself: all 35 points belong to 2 function literals inside it that branch (lines 72, 221). 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 · useBibleStudies.useBibleStudies.handleBibleStudyChange (cognitive 35) · ×1
  • useBibleStudies.useBibleStudies.handleBibleStudyChange (cognitive 35) src/features/ministry/report/form_S4/bible_studies/useBibleStudies.tsx:115 — useBibleStudies.useBibleStudies.handleBibleStudyChange has cognitive complexity 35 (threshold 15). Drivers by points: if/else 13 (31 pts), boolean chains 3, error handling 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 · useHoursCredits.useHoursCredits.handleHoursChange (cognitive 34) · ×1
  • useHoursCredits.useHoursCredits.handleHoursChange (cognitive 34) src/features/ministry/report/form_S4/hours_credits/useHoursCredits.tsx:80 — useHoursCredits.useHoursCredits.handleHoursChange has cognitive complexity 34 (threshold 15). Drivers by points: if/else 13 (31 pts), boolean chains 2, error handling 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 · index.NavBar (cognitive 34) · ×1
  • index.NavBar (cognitive 34) src/layouts/navbar/index.tsx:60 — index.NavBar has cognitive complexity 34 (threshold 15). Drivers by points: boolean chains 23, ternaries 6 (11 pts) (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 · useBrotherSelector.useBrotherSelector.options (cognitive 33) · ×1
  • useBrotherSelector.useBrotherSelector.options (cognitive 33) src/features/meetings/person_selector/brother_selector/useBrotherSelector.tsx:157 — useBrotherSelector.useBrotherSelector.options has cognitive complexity 33 (threshold 15). Drivers by points: if/else 12 (18 pts), ternaries 3 (9 pts), boolean chains 6 (nesting depth added 12). None of this is in the body itself: all 33 points belong to 5 function literals inside it that branch (lines 158, 273, 244, …). 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 · useHoursFields.useHoursFields.handleHoursChange (cognitive 33) · ×1
  • useHoursFields.useHoursFields.handleHoursChange (cognitive 33) src/features/ministry/report/form_S4/hours_fields/useHoursFields.tsx:111 — useHoursFields.useHoursFields.handleHoursChange has cognitive complexity 33 (threshold 15). Drivers by points: if/else 13 (31 pts), boolean chains 1, error handling 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 · useStudentSelector.useStudentSelector.options (cognitive 32) · ×1
  • useStudentSelector.useStudentSelector.options (cognitive 32) src/features/meetings/person_selector/student_selector/useStudentSelector.tsx:199 — useStudentSelector.useStudentSelector.options has cognitive complexity 32 (threshold 15). Drivers by points: if/else 14 (19 pts), boolean chains 13 (nesting depth added 5). Most of this is not in the body itself: 1 of the 32 points is its own statement and the rest belongs to 3 function literals inside it that branch (lines 202, 263, 237). 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 · useAssignments.useAssignments.handleToggleGroup (cognitive 32) · ×1
  • useAssignments.useAssignments.handleToggleGroup (cognitive 32) src/features/persons/assignments/useAssignments.tsx:247 — useAssignments.useAssignments.handleToggleGroup has cognitive complexity 32 (threshold 15). Drivers by points: if/else 10 (24 pts), loops 3 (7 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 · useExportS21.useExportS21.handleExportAll (cognitive 32) · ×1
  • useExportS21.useExportS21.handleExportAll (cognitive 32) src/features/reports/publisher_records/export_S21/useExportS21.tsx:91 — useExportS21.useExportS21.handleExportAll has cognitive complexity 32 (threshold 15). Drivers by points: if/else 7 (17 pts), loops 5 (15 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 · index.DatePicker (cognitive 30) · ×1
  • index.DatePicker (cognitive 30) src/components/date_picker/index.tsx:23 — index.DatePicker has cognitive complexity 30 (threshold 15). Drivers by points: if/else 16 (17 pts), boolean chains 9, ternaries 4 (nesting depth added 1). Most of this is not in the body itself: 6 of the 30 points are its own statements and the rest belongs to 7 function items inside it that branch (handleValueChange, a function literal at line 98, handleKeyDown, …). 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.
D2 · Cognitive Complexity · useHoursCredits.useHoursCredits.handleSelectPreset (cognitive 30) · ×1
  • useHoursCredits.useHoursCredits.handleSelectPreset (cognitive 30) src/features/ministry/report/form_S4/hours_credits/useHoursCredits.tsx:185 — useHoursCredits.useHoursCredits.handleSelectPreset has cognitive complexity 30 (threshold 15). Drivers by points: if/else 11 (25 pts), boolean chains 4, error handling 1 (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · usePerson.usePerson.getBadges (cognitive 30) · ×1
  • usePerson.usePerson.getBadges (cognitive 30) src/features/persons/hooks/usePerson.tsx:195 — usePerson.usePerson.getBadges has cognitive complexity 30 (threshold 15). Drivers by points: if/else 14 (24 pts), boolean chains 6 (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 · index.ExportSpeakers (cognitive 30) · ×1
  • index.ExportSpeakers (cognitive 30) src/features/persons/speakers_catalog/import_export/export/index.tsx:18 — index.ExportSpeakers has cognitive complexity 30 (threshold 15). Drivers by points: ternaries 11 (14 pts), if/else 9, boolean chains 6, error handling 1 (nesting depth added 3). Of this number, 16 points are the body's own statements and 14 belong to 7 function items inside it that branch. 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 · index.MidweekEditor (cognitive 29) · ×1
  • index.MidweekEditor (cognitive 29) src/features/meetings/midweek_editor/index.tsx:58 — index.MidweekEditor has cognitive complexity 29 (threshold 15). Drivers by points: boolean chains 29. 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 · useSpeakerEditPopup.useSpeakerEditPopup.handleSave (cognitive 29) · ×1
  • useSpeakerEditPopup.useSpeakerEditPopup.handleSave (cognitive 29) src/features/persons/speakers_catalog/speaker_edit_popup/useSpeakerEditPopup.tsx:343 — useSpeakerEditPopup.useSpeakerEditPopup.handleSave has cognitive complexity 29 (threshold 15). Drivers by points: if/else 15 (24 pts), boolean chains 4, error handling 1 (nesting depth added 9). Of this number, 28 points are the body's own statements and 1 belongs to one function item 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 · schedules.schedulesMidweekGetTiming (cognitive 29) · ×1
  • schedules.schedulesMidweekGetTiming (cognitive 29) src/services/app/schedules.ts:1923 — schedules.schedulesMidweekGetTiming has cognitive complexity 29 (threshold 15). Drivers by points: if/else 22 (27 pts), boolean chains 2 (nesting depth added 5). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · useConfirmImport.useConfirmImport.handleSelectAll (cognitive 28) · ×1
  • useConfirmImport.useConfirmImport.handleSelectAll (cognitive 28) src/features/congregation/settings/import_export/confirm_import/useConfirmImport.tsx:425 — useConfirmImport.useConfirmImport.handleSelectAll has cognitive complexity 28 (threshold 15). Drivers by points: if/else 13 (24 pts), boolean chains 2, loops 1 (2 pts) (nesting depth added 12). Most of this is not in the body itself: 4 of the 28 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 439, 427). 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 · usePublicTalkSelector.usePublicTalkSelector.talks (cognitive 28) · ×1
  • usePublicTalkSelector.usePublicTalkSelector.talks (cognitive 28) src/features/meetings/weekend_editor/public_talk_selector/usePublicTalkSelector.tsx:37 — usePublicTalkSelector.usePublicTalkSelector.talks has cognitive complexity 28 (threshold 15). Drivers by points: if/else 7 (16 pts), boolean chains 6, loops 2 (4 pts), ternaries 1 (2 pts) (nesting depth added 12). Of this number, 26 points are the body's own statements and 2 belong to 2 function literals 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 · usePersonsList.usePersonsList.handleAddRandomData (cognitive 28) · ×1
  • usePersonsList.usePersonsList.handleAddRandomData (cognitive 28) src/features/reports/field_service/persons_list/usePersonsList.tsx:307 — usePersonsList.usePersonsList.handleAddRandomData has cognitive complexity 28 (threshold 15). Drivers by points: if/else 10 (24 pts), boolean chains 3, loops 1 (nesting depth added 14). 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, split the body into named stages: move each independent 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 · autofill.processAssignmentSettings (cognitive 28) · ×1
  • autofill.processAssignmentSettings (cognitive 28) src/services/app/autofill.ts:228 — autofill.processAssignmentSettings has cognitive complexity 28 (threshold 15). Drivers by points: if/else 13 (24 pts), boolean chains 4 (nesting depth added 11). Most of this is not in the body itself: 2 of the 28 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 274, 239, 305). 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 · cong_field_service_reports.dbHandleIncomingReports (cognitive 28) · ×1
  • cong_field_service_reports.dbHandleIncomingReports (cognitive 28) src/services/dexie/cong_field_service_reports.ts:33 — cong_field_service_reports.dbHandleIncomingReports has cognitive complexity 28 (threshold 15). Drivers by points: if/else 10 (22 pts), boolean chains 5, loops 1 (nesting depth added 12). Of this number, 26 points are the body's own statements and 2 belong to 2 function literals 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 · sources.sourcesPartTiming (cognitive 27) · ×1
  • sources.sourcesPartTiming (cognitive 27) REDACTED:493 — sources.sourcesPartTiming has cognitive complexity 27 (threshold 15). Drivers by points: ternaries 7 (14 pts), if/else 7, boolean chains 6 (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 · backupUtils.dbRestoreSettings (cognitive 27) · ×1
  • backupUtils.dbRestoreSettings (cognitive 27) src/services/worker/backupUtils.ts:663 — backupUtils.dbRestoreSettings has cognitive complexity 27 (threshold 15). Drivers by points: if/else 12 (18 pts), boolean chains 4, loops 2 (4 pts), error handling 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · dev.dbBranchS1ReportsFill (cognitive 27) · ×1
  • dev.dbBranchS1ReportsFill (cognitive 27) src/utils/dev.ts:1149 — dev.dbBranchS1ReportsFill has cognitive complexity 27 (threshold 15). Drivers by points: if/else 6 (18 pts), loops 3 (5 pts), boolean chains 2, ternaries 1 (2 pts) (nesting depth added 15). Of this number, 23 points are the body's own statements and 4 belong to 2 function literals 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 · usePersonCard.usePersonCard.getPersonBadge (cognitive 26) · ×1
  • usePersonCard.usePersonCard.getPersonBadge (cognitive 26) src/features/persons/list/person_card/usePersonCard.tsx:36 — usePersonCard.usePersonCard.getPersonBadge has cognitive complexity 26 (threshold 15). Drivers by points: if/else 14 (23 pts), boolean chains 3 (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 · assignment_selection.sortCandidatesMultiLevel (cognitive 26) · ×1
  • assignment_selection.sortCandidatesMultiLevel (cognitive 26) src/services/app/assignment_selection.ts:812 — assignment_selection.sortCandidatesMultiLevel has cognitive complexity 26 (threshold 15). Drivers by points: if/else 7 (12 pts), boolean chains 9, ternaries 5 (nesting depth added 5). Most of this is not in the body itself: 5 of the 26 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 831, 959). 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 · usePioneerStats.usePioneerStats.hours_balance (cognitive 25) · ×1
  • usePioneerStats.usePioneerStats.hours_balance (cognitive 25) src/features/ministry/service_year/yearly_stats/pioneer_stats/usePioneerStats.tsx:112 — usePioneerStats.usePioneerStats.hours_balance has cognitive complexity 25 (threshold 15). Drivers by points: if/else 10 (20 pts), boolean chains 2, loops 2, ternaries 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 · useSpiritualStatus.useSpiritualStatus.handleToggleUnbaptizedPublisher (cognitive 25) · ×1
  • useSpiritualStatus.useSpiritualStatus.handleToggleUnbaptizedPublisher (cognitive 25) src/features/persons/spiritual_status/useSpiritualStatus.tsx:131 — useSpiritualStatus.useSpiritualStatus.handleToggleUnbaptizedPublisher has cognitive complexity 25 (threshold 15). Drivers by points: if/else 10 (23 pts), boolean chains 2 (nesting depth added 13). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
D2 · Cognitive Complexity · index.AssignmentCheckList (cognitive 24) · ×1
  • index.AssignmentCheckList (cognitive 24) src/components/assignments_checklist/index.tsx:25 — index.AssignmentCheckList has cognitive complexity 24 (threshold 15). Drivers by points: if/else 8 (11 pts), ternaries 5 (7 pts), boolean chains 6 (nesting depth added 5). Most of this is not in the body itself: 5 of the 24 points are its own statements and the rest belongs to 7 function items inside it that branch (a function literal at line 87, calculateWidthForStyledContentBox, a function literal at line 47, …). 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.
D2 · Cognitive Complexity · useBrotherSelector.useBrotherSelector.value (cognitive 24) · ×1
  • useBrotherSelector.useBrotherSelector.value (cognitive 24) src/features/meetings/person_selector/brother_selector/useBrotherSelector.tsx:311 — useBrotherSelector.useBrotherSelector.value has cognitive complexity 24 (threshold 15). Drivers by points: if/else 13 (16 pts), boolean chains 8 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · index.WeekendEditor (cognitive 24) · ×1
  • index.WeekendEditor (cognitive 24) src/features/meetings/weekend_editor/index.tsx:53 — index.WeekendEditor has cognitive complexity 24 (threshold 15). Drivers by points: boolean chains 24. 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 · useAssignmentGroup.useAssignmentGroup.checkAssignmentDisabled (cognitive 24) · ×1
  • useAssignmentGroup.useAssignmentGroup.checkAssignmentDisabled (cognitive 24) src/features/persons/assignment_group/useAssignmentGroup.tsx:42 — useAssignmentGroup.useAssignmentGroup.checkAssignmentDisabled has cognitive complexity 24 (threshold 15). Drivers by points: if/else 12 (19 pts), boolean chains 5 (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 · persons.assignFamilyMembersToHead (cognitive 24) · ×1
  • persons.assignFamilyMembersToHead (cognitive 24) src/services/dexie/persons.ts:194 — persons.assignFamilyMembersToHead has cognitive complexity 24 (threshold 15). Drivers by points: if/else 10 (21 pts), loops 2 (3 pts) (nesting depth added 12). Most of this is not in the body itself: 9 of the 24 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 226, 206). 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 · assignments.checkAssignmentUnappliable (cognitive 24) · ×1
  • assignments.checkAssignmentUnappliable (cognitive 24) src/utils/assignments.ts:53 — assignments.checkAssignmentUnappliable has cognitive complexity 24 (threshold 15). Drivers by points: if/else 12 (19 pts), boolean chains 5 (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 · dev.dbMeetingAttendanceFill (cognitive 24) · ×1
  • dev.dbMeetingAttendanceFill (cognitive 24) src/utils/dev.ts:1064 — dev.dbMeetingAttendanceFill has cognitive complexity 24 (threshold 15). Drivers by points: if/else 6 (18 pts), loops 3 (6 pts) (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · useConfirmImport.useConfirmImport.selectedAll (cognitive 23) · ×1
  • useConfirmImport.useConfirmImport.selectedAll (cognitive 23) src/features/congregation/settings/import_export/confirm_import/useConfirmImport.tsx:351 — useConfirmImport.useConfirmImport.selectedAll has cognitive complexity 23 (threshold 15). Drivers by points: if/else 12, boolean chains 11. 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 · useComments.useComments.handleCommentsChange (cognitive 23) · ×1
  • useComments.useComments.handleCommentsChange (cognitive 23) src/features/ministry/report/form_S4/comments/useComments.tsx:39 — useComments.useComments.handleCommentsChange has cognitive complexity 23 (threshold 15). Drivers by points: if/else 10 (22 pts), 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 · useMinistryShared.useMinistryShared.handleToggleChecked (cognitive 23) · ×1
  • useMinistryShared.useMinistryShared.handleToggleChecked (cognitive 23) src/features/ministry/report/form_S4/ministry_shared/useMinistryShared.tsx:40 — useMinistryShared.useMinistryShared.handleToggleChecked has cognitive complexity 23 (threshold 15). Drivers by points: if/else 10 (22 pts), 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 · schedules.schedulesBuildHistoryList (cognitive 23) · ×1
  • schedules.schedulesBuildHistoryList (cognitive 23) src/services/app/schedules.ts:1138 — schedules.schedulesBuildHistoryList has cognitive complexity 23 (threshold 15). Drivers by points: if/else 4 (14 pts), loops 3 (6 pts), ternaries 1 (3 pts) (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · index.InfoMessage (cognitive 22) · ×1
  • index.InfoMessage (cognitive 22) src/components/info-message/index.tsx:14 — index.InfoMessage has cognitive complexity 22 (threshold 15). Drivers by points: boolean chains 9, ternaries 6 (7 pts), if/else 6 (nesting depth added 1). Of this number, 16 points are the body's own statements and 6 belong to 2 function items inside it that branch. 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 · usePublisherDetails.usePublisherDetails.handleChangeFirstReport (cognitive 22) · ×1
  • usePublisherDetails.usePublisherDetails.handleChangeFirstReport (cognitive 22) src/features/reports/publisher_records_details/publisher_details/usePublisherDetails.tsx:95 — usePublisherDetails.usePublisherDetails.handleChangeFirstReport has cognitive complexity 22 (threshold 15). Drivers by points: if/else 9 (19 pts), boolean chains 2, error handling 1 (nesting depth added 10). Of this number, 20 points are the body's own statements and 2 belong to 2 function literals 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 · schedules.schedulesUpdateHistory (cognitive 22) · ×1
  • schedules.schedulesUpdateHistory (cognitive 22) src/services/app/schedules.ts:1192 — schedules.schedulesUpdateHistory has cognitive complexity 22 (threshold 15). Drivers by points: if/else 10 (19 pts), boolean chains 2, loops 1 (nesting depth added 9). 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 into named stages: move each independent 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 · autofill.getTasksArray (cognitive 22) · ×1
  • autofill.getTasksArray (cognitive 22) src/services/app/autofill.ts:743 — autofill.getTasksArray has cognitive complexity 22 (threshold 15). Drivers by points: if/else 10 (16 pts), boolean chains 5, ternaries 1 (nesting depth added 6). Most of this is not in the body itself: 1 of the 22 points is its own statement and the rest belongs to 4 function literals inside it that branch (lines 805, 766, 777, …). 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 · assignments_with_stats.getCorrectionCounts (cognitive 22) · ×1
  • assignments_with_stats.getCorrectionCounts (cognitive 22) src/services/app/assignments_with_stats.ts:278 — assignments_with_stats.getCorrectionCounts has cognitive complexity 22 (threshold 15). Drivers by points: if/else 5 (12 pts), boolean chains 5, ternaries 2 (4 pts), loops 1 (nesting depth added 9). Of this number, 14 points are the body's own statements and 8 belong to 2 function literals 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 · useWebWorker.useWebWorker (cognitive 22) · ×1
  • useWebWorker.useWebWorker (cognitive 22) src/wrapper/web_worker/useWebWorker.tsx:32 — useWebWorker.useWebWorker has cognitive complexity 22 (threshold 15). Drivers by points: if/else 10 (16 pts), boolean chains 6 (nesting depth added 6). Most of this is not in the body itself: 2 of the 22 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 130, 102, 56, …). 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 · useFirstReport.useFirstReport.handleChangeFirstReport (cognitive 21) · ×1
  • useFirstReport.useFirstReport.handleChangeFirstReport (cognitive 21) src/features/persons/spiritual_status/first_report/useFirstReport.tsx:16 — useFirstReport.useFirstReport.handleChangeFirstReport has cognitive complexity 21 (threshold 15). Drivers by points: if/else 9 (19 pts), boolean chains 2 (nesting depth added 10). Of this number, 19 points are the body's own statements and 2 belong to 2 function literals 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 · assignment_selection.hasAssignmentConflict (cognitive 21) · ×1
  • assignment_selection.hasAssignmentConflict (cognitive 21) src/services/app/assignment_selection.ts:1129 — assignment_selection.hasAssignmentConflict has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (13 pts), boolean chains 7, loops 1 (nesting depth added 5). Of this number, 19 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 · schedules.dbSchedAuxClassUpdate (cognitive 21) · ×1
  • schedules.dbSchedAuxClassUpdate (cognitive 21) src/services/dexie/schedules.ts:53 — schedules.dbSchedAuxClassUpdate has cognitive complexity 21 (threshold 15). Drivers by points: if/else 10 (20 pts), loops 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · backupUtils.dbGetMetadata (cognitive 21) · ×1
  • backupUtils.dbGetMetadata (cognitive 21) src/services/worker/backupUtils.ts:332 — backupUtils.dbGetMetadata has cognitive complexity 21 (threshold 15). Drivers by points: boolean chains 10, if/else 10, loops 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 · index.TemplateS140AppNormal (cognitive 21) · ×1
  • index.TemplateS140AppNormal (cognitive 21) src/views/meetings/midweek/S140/app_normal/index.tsx:25 — index.TemplateS140AppNormal has cognitive complexity 21 (threshold 15). Drivers by points: boolean chains 21. None of this is in the body itself: all 21 points belong to one function literal inside it that branches (line 37). The decisions are inside the literal, 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 literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · useContainer.useContainer.handleRejectedRequests (cognitive 20) · ×1
  • useContainer.useContainer.handleRejectedRequests (cognitive 20) src/features/app_notification/container/useContainer.tsx:208 — useContainer.useContainer.handleRejectedRequests has cognitive complexity 20 (threshold 15). Drivers by points: if/else 5 (12 pts), loops 2 (5 pts), boolean chains 2, error handling 1 (nesting depth added 10). Of this number, 18 points are the body's own statements and 2 belong to 2 function literals 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 · useExportSpeakers.useExportSpeakers.handleExport (cognitive 20) · ×1
  • useExportSpeakers.useExportSpeakers.handleExport (cognitive 20) src/features/persons/speakers_catalog/import_export/export/useExportSpeakers.tsx:304 — useExportSpeakers.useExportSpeakers.handleExport has cognitive complexity 20 (threshold 15). Drivers by points: if/else 11 (12 pts), boolean chains 6, error handling 1, ternaries 1 (nesting depth added 1). Most of this is not in the body itself: 7 of the 20 points are its own statements and the rest belongs to 6 function items inside it that branch (a function literal at line 345, a function literal at line 380, a function literal at line 334, …). 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.
D2 · Cognitive Complexity · useWeekBox.useWeekBox (cognitive 20) · ×1
  • useWeekBox.useWeekBox (cognitive 20) src/features/reports/meeting_attendance/monthly_record/week_box/useWeekBox.tsx:51 — useWeekBox.useWeekBox has cognitive complexity 20 (threshold 15). Drivers by points: boolean chains 13, ternaries 5 (6 pts), if/else 1 (nesting depth added 1). Of this number, 19 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.
D2 · Cognitive Complexity · useNavbar.useNavbar.markLastNavBarButton (cognitive 20) · ×1
  • useNavbar.useNavbar.markLastNavBarButton (cognitive 20) src/layouts/navbar/useNavbar.tsx:174 — useNavbar.useNavbar.markLastNavBarButton has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (12 pts), boolean chains 3, loops 2 (3 pts), ternaries 1 (2 pts) (nesting depth added 6). Of this number, 12 points are the body's own statements and 8 belong to 2 function literals 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 · autofill.getSortedTasks (cognitive 20) · ×1
  • autofill.getSortedTasks (cognitive 20) src/services/app/autofill.ts:962 — autofill.getSortedTasks has cognitive complexity 20 (threshold 15). Drivers by points: if/else 10, ternaries 4 (8 pts), boolean chains 2 (nesting depth added 4). None of this is in the body itself: all 20 points belong to 3 function items inside it that branch (a function literal at line 994, getBaseKey, a function literal at line 980). 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.
D2 · Cognitive Complexity · spiritual_status.toggleActive (cognitive 20) · ×1
  • spiritual_status.toggleActive (cognitive 20) src/utils/spiritual_status.ts:212 — spiritual_status.toggleActive has cognitive complexity 20 (threshold 15). Drivers by points: if/else 9 (18 pts), boolean chains 1, ternaries 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · useAuth.useAuth.updateUserSettings (cognitive 19) · ×1
  • useAuth.useAuth.updateUserSettings (cognitive 19) src/features/app_start/vip/hooks/useAuth.tsx:96 — useAuth.useAuth.updateUserSettings has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9 (14 pts), loops 2 (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 · useGroupDelete.useGroupDelete.handleDelete (cognitive 19) · ×1
  • useGroupDelete.useGroupDelete.handleDelete (cognitive 19) src/features/congregation/settings/language_groups/group_delete/useGroupDelete.tsx:39 — useGroupDelete.useGroupDelete.handleDelete has cognitive complexity 19 (threshold 15). Drivers by points: if/else 14, boolean chains 4, error handling 1. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · useWithdrawReport.useWithdrawReport.handleWithdrawal (cognitive 19) · ×1
  • useWithdrawReport.useWithdrawReport.handleWithdrawal (cognitive 19) src/features/ministry/report/form_S4/withdraw_report/useWithdrawReport.tsx:87 — useWithdrawReport.useWithdrawReport.handleWithdrawal has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9 (14 pts), boolean chains 4, 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 · useCSVImport.useCSVImport.parseCsvToPersonsAndGroups (cognitive 19) · ×1
  • useCSVImport.useCSVImport.parseCsvToPersonsAndGroups (cognitive 19) src/features/persons/import_export/confirm_import/useCSVImport.tsx:39 — useCSVImport.useCSVImport.parseCsvToPersonsAndGroups has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (11 pts), boolean chains 3, error handling 2 (3 pts), loops 1, ternaries 1 (nesting depth added 6). Most of this is not in the body itself: 5 of the 19 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 87, 80). 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 · assignments_with_stats.calculateOpportunityScore (cognitive 19) · ×1
  • assignments_with_stats.calculateOpportunityScore (cognitive 19) src/services/app/assignments_with_stats.ts:949 — assignments_with_stats.calculateOpportunityScore has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (12 pts), boolean chains 4, ternaries 1 (2 pts), loops 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · index.decryptObject (cognitive 19) · ×1
  • index.decryptObject (cognitive 19) src/services/encryption/index.ts:89 — index.decryptObject has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (15 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 · backupUtils.dbRestoreSources (cognitive 19) · ×1
  • backupUtils.dbRestoreSources (cognitive 19) src/services/worker/backupUtils.ts:1405 — backupUtils.dbRestoreSources has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9 (15 pts), boolean chains 2, error handling 1, loops 1 (nesting depth added 6). Of this number, 15 points are the body's own statements and 4 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 · index.Checkbox (cognitive 18) · ×1
  • index.Checkbox (cognitive 18) src/components/checkbox/index.tsx:19 — index.Checkbox has cognitive complexity 18 (threshold 15). Drivers by points: boolean chains 11, ternaries 7. 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 · index.NavBarButton (cognitive 18) · ×1
  • index.NavBarButton (cognitive 18) src/components/nav_bar_button/index.tsx:16 — index.NavBarButton has cognitive complexity 18 (threshold 15). Drivers by points: ternaries 6 (10 pts), boolean chains 6, if/else 1 (2 pts) (nesting depth added 5). Of this number, 14 points are the body's own statements and 4 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 · index.EditUpcomingEvent (cognitive 18) · ×1
  • index.EditUpcomingEvent (cognitive 18) src/features/activities/upcoming_events/edit_upcoming_event/index.tsx:24 — index.EditUpcomingEvent has cognitive complexity 18 (threshold 15). Drivers by points: boolean chains 9, ternaries 8 (9 pts) (nesting depth added 1). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · useImport.useImport (cognitive 18) · ×1
  • useImport.useImport (cognitive 18) src/features/congregation/settings/import_export/import/useImport.tsx:14 — useImport.useImport has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (14 pts), boolean chains 3, error handling 1 (nesting depth added 5). None of this is in the body itself: all 18 points belong to one function literal inside it that branches (line 24). The decisions are inside the literal, 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 literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · usePartDuration.usePartDuration.handleChangeDuration (cognitive 18) · ×1
  • usePartDuration.usePartDuration.handleChangeDuration (cognitive 18) src/features/meetings/part_duration/usePartDuration.tsx:19 — usePartDuration.usePartDuration.handleChangeDuration has cognitive complexity 18 (threshold 15). Drivers by points: if/else 12 (18 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 · useSongSource.useSongSource.initialValue (cognitive 18) · ×1
  • useSongSource.useSongSource.initialValue (cognitive 18) src/features/meetings/song_source/useSongSource.tsx:59 — useSongSource.useSongSource.initialValue has cognitive complexity 18 (threshold 15). Drivers by points: if/else 10 (17 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 · usePublisherCard.usePublisherCard.getReportData (cognitive 18) · ×1
  • usePublisherCard.usePublisherCard.getReportData (cognitive 18) src/features/reports/hooks/usePublisherCard.tsx:94 — usePublisherCard.usePublisherCard.getReportData has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (16 pts), boolean chains 1, loops 1 (nesting depth added 11). Of this number, 17 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 · schedules.schedulesSaveAssignment (cognitive 18) · ×1
  • schedules.schedulesSaveAssignment (cognitive 18) src/services/app/schedules.ts:1304 — schedules.schedulesSaveAssignment has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (13 pts), ternaries 2 (5 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 · index.TimePicker (cognitive 17) · ×1
  • index.TimePicker (cognitive 17) src/components/time_picker/index.tsx:20 — index.TimePicker has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 15, boolean chains 1, if/else 1. Of this number, 16 points are the body's own statements and 1 belongs to one function item inside it that branches. 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 · useTimeField.useTimeField.handleDigitsTyped (cognitive 17) · ×1
  • useTimeField.useTimeField.handleDigitsTyped (cognitive 17) src/components/timefield/useTimeField.tsx:44 — useTimeField.useTimeField.handleDigitsTyped has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (16 pts), boolean chains 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · index.StudentSelector (cognitive 17) · ×1
  • index.StudentSelector (cognitive 17) src/features/meetings/person_selector/student_selector/index.tsx:32 — index.StudentSelector has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 14, ternaries 3. Of this number, 14 points are the body's own statements and 3 belong 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.
D2 · Cognitive Complexity · useMainForm.useMainForm (cognitive 17) · ×1
  • useMainForm.useMainForm (cognitive 17) src/features/ministry/ap_application/main_form/useMainForm.tsx:21 — useMainForm.useMainForm has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (16 pts), boolean chains 1 (nesting depth added 7). None of this is in the body itself: all 17 points belong to 2 function literals inside it that branch (lines 83, 63). 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 · useCSVImport.useCSVImport.processRowData (cognitive 17) · ×1
  • useCSVImport.useCSVImport.processRowData (cognitive 17) src/features/persons/speakers_catalog/import_export/confirm_import/useCSVImport.tsx:225 — useCSVImport.useCSVImport.processRowData has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 2 (6 pts), if/else 3 (5 pts), boolean chains 3, error handling 1 (2 pts), loops 1 (nesting depth added 7). Of this number, 16 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 · assignments.toggleAssignment (cognitive 17) · ×1
  • assignments.toggleAssignment (cognitive 17) src/utils/assignments.ts:110 — assignments.toggleAssignment has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (14 pts), boolean chains 1, loops 1, 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 · index.ScheduleS140 (cognitive 17) · ×1
  • index.ScheduleS140 (cognitive 17) src/views/meetings/midweek/S140/default/index.tsx:23 — index.ScheduleS140 has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 17. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · useFeatureFlags.useFeatureFlags (cognitive 17) · ×1
  • useFeatureFlags.useFeatureFlags (cognitive 17) src/wrapper/feature_flags/useFeatureFlags.tsx:12 — useFeatureFlags.useFeatureFlags has cognitive complexity 17 (threshold 15). Drivers by points: if/else 11 (13 pts), boolean chains 2, error handling 1, loops 1 (nesting depth added 2). None of this is in the body itself: all 17 points belong to 6 function literals inside it that branch (lines 49, 75, 74, …). 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 · index.Dialog (cognitive 16) · ×1
  • index.Dialog (cognitive 16) src/components/dialog/index.tsx:78 — index.Dialog has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 11, if/else 3, ternaries 2. Of this number, 13 points are the body's own statements and 3 belong to 2 function items inside it that branch. 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 · useMonthlyView.useMonthlyView (cognitive 16) · ×1
  • useMonthlyView.useMonthlyView (cognitive 16) src/features/meetings/monthly_view/useMonthlyView.tsx:30 — useMonthlyView.useMonthlyView has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9, boolean chains 5, ternaries 2. None of this is in the body itself: all 16 points belong to 6 function literals inside it that branch (lines 330, 368, 234, …). 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 · usePersonFilter.usePersonFilter.filters (cognitive 16) · ×1
  • usePersonFilter.usePersonFilter.filters (cognitive 16) src/features/reports/field_service/selector_stats/person_filter/usePersonFilter.tsx:35 — usePersonFilter.usePersonFilter.filters has cognitive complexity 16 (threshold 15). Drivers by points: if/else 10 (13 pts), boolean chains 3 (nesting depth added 3). Of this number, 14 points are the body's own statements and 2 belong 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 · index.RootLayout (cognitive 16) · ×1
  • index.RootLayout (cognitive 16) src/layouts/root_layout/index.tsx:32 — index.RootLayout has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 16. 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 · date.buildServiceYearsList (cognitive 16) · ×1
  • date.buildServiceYearsList (cognitive 16) src/utils/date.ts:234 — date.buildServiceYearsList has cognitive complexity 16 (threshold 15). Drivers by points: if/else 3 (6 pts), ternaries 2 (6 pts), loops 3 (4 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D30 · Dependency Vulnerabilities · Medium vulnerability · ×1
  • REDACTED
D32 · Data Compliance (PII/GDPR) · REDACTED · ×1
  • REDACTED
D32 · Data Compliance (PII/GDPR) · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
IC1 · Incompleteness & stubs · Guard cannot change the result · ×1
  • Guard cannot change the result — returns what the code already falls through to src/features/reports/publisher_records_details/month_item/useMonthItem.tsx:188 — The guard above `return true;` also returns `true`, so no input can make it matter. Implement the distinction that was intended, or delete the guard.
R10 · Code Duplication · Duplication concentrated across 21 sibling directories (268 clone groups) · ×1
  • Duplication concentrated across 21 sibling directories (268 clone groups) src/features/persons/spiritual_status/first_report/useFirstReport.tsx:21 — 268 duplicated blocks under src/features/ have copies in at least two of the sibling directories about, activities, app_feedback, app_notification, app_start, color_scheme_selector (+15 more sibling(s) not listed) — 137 of them are reported below, and 131 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 268 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 268 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 268 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
R10 · Code Duplication · Duplication concentrated across 10 sibling directories (114 clone groups) · ×1
  • Duplication concentrated across 10 sibling directories (114 clone groups) src/features/activities/upcoming_events/decorations_for_event.tsx:19 — 114 duplicated blocks under src/ have copies in at least two of the sibling directories components, features, hooks, layouts, pages, services (+4 more sibling(s) not listed) — 70 of them are reported below, and 44 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 114 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 114 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 114 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
R10 · Code Duplication · Duplication concentrated across 24 sibling directories (47 clone groups) · ×1
  • Duplication concentrated across 24 sibling directories (47 clone groups) src/features/meetings/schedule_range_selector/useScheduleRangeSelector.tsx:21 — 47 duplicated blocks under src/features/meetings/ have copies in at least two of the sibling directories assignments_delete, assignments_history, assignments_week_delete, event_editor, meeting_part, midweek_editor (+18 more sibling(s) not listed) — 28 of them are reported below, and 19 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 47 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 47 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 47 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
R10 · Code Duplication · Duplication concentrated across 21 sibling directories (46 clone groups) · ×1
  • Duplication concentrated across 21 sibling directories (46 clone groups) src/features/persons/import_export/confirm_import/index.tsx:1 — 46 duplicated blocks under src/features/persons/ have copies in at least two of the sibling directories app_user_profile, applications, assignments, assignments_history, basic_info, button_actions (+15 more sibling(s) not listed) — 32 of them are reported below, and 14 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 46 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 46 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 46 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
R10 · Code Duplication · Duplication concentrated across 8 sibling directories (20 clone groups) · ×1
  • Duplication concentrated across 8 sibling directories (20 clone groups) src/features/congregation/settings/first_day_week/useFirstDayWeek.ts:12 — 20 duplicated blocks under src/features/congregation/settings/ have copies in at least two of the sibling directories circuit_overseer, congregation_basic, congregation_privacy, first_day_week, import_export, language_groups (+2 more sibling(s) not listed) — 8 of them are reported below, and 12 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 20 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 20 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 20 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
R10 · Code Duplication · Duplication concentrated across 7 sibling directories (20 clone groups) · ×1
  • Duplication concentrated across 7 sibling directories (20 clone groups) src/features/reports/field_service/report_details/useReportDetails.tsx:41 — 20 duplicated blocks under src/features/reports/ have copies in at least two of the sibling directories branch_office, field_service, hooks, meeting_attendance, publisher_records, publisher_records_details (+1 more sibling(s) not listed) — 9 of them are reported below, and 11 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 20 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 20 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 20 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
R10 · Code Duplication · Duplication concentrated across 8 sibling directories (15 clone groups) · ×1
  • Duplication concentrated across 8 sibling directories (15 clone groups) src/pages/activities/upcoming_events/index.tsx:18 — 15 duplicated blocks under src/pages/ have copies in at least two of the sibling directories activities, congregation, meeting_materials, meetings, ministry, my_profile (+2 more sibling(s) not listed) — 12 of them are reported below, and 3 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 15 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 15 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 15 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
R10 · Code Duplication · Duplication concentrated across 9 sibling directories (14 clone groups) · ×1
  • Duplication concentrated across 9 sibling directories (14 clone groups) src/features/app_start/vip/email_link_authentication/useEmailLinkAuth.tsx:41 — 14 duplicated blocks under src/features/app_start/vip/ have copies in at least two of the sibling directories congregation_create, congregation_encryption, email_link_authentication, email_sent, hooks, oauth (+3 more sibling(s) not listed) — 9 of them are reported below, and 5 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 14 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 14 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 14 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
R10 · Code Duplication · Duplication concentrated across 6 sibling directories (13 clone groups) · ×1
  • Duplication concentrated across 6 sibling directories (13 clone groups) src/features/meetings/person_selector/brother_selector/index.tsx:48 — 13 duplicated blocks under src/features/meetings/person_selector/ have copies in at least two of the sibling directories brother_selector, circuit_overseer, outgoing_speaker, stream_speaker, student_selector, visiting_speaker — 12 of them are reported below, and 1 is counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 13 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 13 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 13 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
R10 · Code Duplication · Duplication concentrated across 3 sibling directories (11 clone groups) · ×1
  • Duplication concentrated across 3 sibling directories (11 clone groups) src/features/congregation/app_access/join_requests/item/useJoinRequest.tsx:94 — 11 duplicated blocks under src/features/congregation/ have copies in at least two of the sibling directories app_access, field_service_groups, settings — 5 of them are reported below, and 6 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 11 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 11 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 11 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
R10 · Code Duplication · Duplication concentrated across 7 sibling directories (11 clone groups) · ×1
  • Duplication concentrated across 7 sibling directories (11 clone groups) src/features/ministry/report/form_S4/hours_credits/useHoursCredits.tsx:36 — 11 of the duplicated blocks reported below have copies in at least two of the sibling directories bible_studies, comments, hours_credits, hours_fields, ministry_shared, submit_report (+1 more sibling(s) not listed) under src/features/ministry/report/form_S4/. That concentration is one structural fact, not 11 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 11 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
R10 · Code Duplication · Duplication concentrated across 7 sibling directories (10 clone groups) · ×1
  • Duplication concentrated across 7 sibling directories (10 clone groups) src/features/congregation/app_access/user_details/user_additional_rights/useUserAdditionalRights.tsx:120 — 10 duplicated blocks under src/features/congregation/app_access/user_details/ have copies in at least two of the sibling directories delete_user, invitation_code, profile_settings, user_additional_rights, user_main_roles, user_rights (+1 more sibling(s) not listed) — 7 of them are reported below, and 3 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 10 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 10 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 10 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
R10 · Code Duplication · Duplication concentrated across 5 sibling directories (10 clone groups) · ×1
  • Duplication concentrated across 5 sibling directories (10 clone groups) src/features/meetings/weekly_schedules/midweek_meeting/useMidweekMeeting.tsx:58 — 10 duplicated blocks under src/features/meetings/weekly_schedules/ have copies in at least two of the sibling directories midweek_container, midweek_meeting, outgoing_talks, weekend_container, weekend_meeting — 9 of them are reported below, and 1 is counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 10 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 10 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 10 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
R10 · Code Duplication · Duplication concentrated across 6 sibling directories (9 clone groups) · ×1
  • Duplication concentrated across 6 sibling directories (9 clone groups) src/features/persons/speakers_catalog/my_congregation/speakers_local/useSpeakersLocal.tsx:33 — 9 duplicated blocks under src/features/persons/speakers_catalog/ have copies in at least two of the sibling directories my_congregation, other_congregations, speaker_details, speaker_edit_popup, speaker_row_edit, speaker_row_view — 5 of them are reported below, and 4 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 9 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 9 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 9 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
R10 · Code Duplication · Duplication concentrated across 6 sibling directories (8 clone groups) · ×1
  • Duplication concentrated across 6 sibling directories (8 clone groups) src/features/reports/publisher_records_details/report_details/comments/useComments.tsx:6 — 8 duplicated blocks under src/features/reports/publisher_records_details/report_details/ have copies in at least two of the sibling directories bible_studies, comments, credit_field, hours_field, late_report, ministry_shared — 6 of them are reported below, and 2 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 8 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 8 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 8 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
R10 · Code Duplication · Duplication concentrated across 5 sibling directories (8 clone groups) · ×1
  • Duplication concentrated across 5 sibling directories (8 clone groups) src/services/app/persons.ts:866 — 8 duplicated blocks under src/services/ have copies in at least two of the sibling directories api, app, dexie, encryption, worker — 6 of them are reported below, and 2 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 8 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 8 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 8 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
R10 · Code Duplication · Duplication concentrated across 8 sibling directories (6 clone groups) · ×1
  • Duplication concentrated across 8 sibling directories (6 clone groups) src/components/minus_button/index.tsx:19 — 6 duplicated blocks under src/components/ have copies in at least two of the sibling directories autocomplete, autocomplete_multiple, date_picker, minus_button, plus_button, scrollable_tabs (+2 more sibling(s) not listed) — 3 of them are reported below, and 3 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 6 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 6 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 6 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
R10 · Code Duplication · Duplication concentrated across 6 sibling directories (6 clone groups) · ×1
  • Duplication concentrated across 6 sibling directories (6 clone groups) src/features/congregation/settings/congregation_privacy/access_code_change/useAccessCodeChange.tsx:14 — 6 duplicated blocks under src/features/congregation/settings/congregation_privacy/ have copies in at least two of the sibling directories access_code_change, access_code_view, data_sharing, master_key_change, master_key_view, time_away_visibility — 4 of them are reported below, and 2 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 6 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 6 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 6 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
R10 · Code Duplication · Duplication concentrated across 2 sibling directories (6 clone groups) · ×1
  • Duplication concentrated across 2 sibling directories (6 clone groups) src/features/congregation/settings/meeting_settings/midweek/day_time/useDayTime.tsx:13 — 6 duplicated blocks under src/features/congregation/settings/meeting_settings/ have copies in at least two of the sibling directories midweek, weekend — 4 of them are reported below, and 2 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 6 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 6 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 6 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
R10 · Code Duplication · Duplication concentrated across 4 sibling directories (5 clone groups) · ×1
  • Duplication concentrated across 4 sibling directories (5 clone groups) src/features/persons/spiritual_status/baptized_publisher/useBaptizedPublisher.tsx:17 — 5 of the duplicated blocks reported below have copies in at least two of the sibling directories baptized_publisher, history, midweek_meeting_student, unbaptized_publisher under src/features/persons/spiritual_status/. That concentration is one structural fact, not 5 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 5 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
R10 · Code Duplication · Duplication concentrated across 2 sibling directories (5 clone groups) · ×1
  • Duplication concentrated across 2 sibling directories (5 clone groups) src/views/meetings/midweek/S140/app_normal/S140AYF.tsx:13 — 5 duplicated blocks under src/views/meetings/midweek/S140/ have copies in at least two of the sibling directories app_normal, default — 4 of them are reported below, and 1 is counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 5 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 5 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 5 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
R10 · Code Duplication · Duplicated block with local edits (150 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (150 matched lines × 2 locations) src/utils/dev.ts:154 — src/utils/dev.ts:154 · src/utils/dev.ts:364 — the two spans are one implementation copied and then locally edited — 779 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 with local edits (125 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (125 matched lines × 2 locations) src/features/persons/spiritual_status/baptized_publisher/useBaptizedPublisher.tsx:17 — src/features/persons/spiritual_status/baptized_publisher/useBaptizedPublisher.tsx:17 · src/features/persons/spiritual_status/unbaptized_publisher/useUnbaptizedPublisher.tsx:15 — the two spans are one implementation copied and then locally edited — 888 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 with local edits (122 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (122 matched lines × 2 locations) src/features/reports/hooks/useReportMonthly.tsx:16 — src/features/reports/hooks/useReportMonthly.tsx:16 · src/features/reports/hooks/useReportYearly.tsx:12 — the two spans are one implementation copied and then locally edited — 638 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 with local edits (115 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (115 matched lines × 2 locations) src/features/ministry/report/form_S4/hours_credits/useHoursCredits.tsx:36 — src/features/ministry/report/form_S4/hours_credits/useHoursCredits.tsx:36 · src/features/ministry/report/form_S4/hours_fields/useHoursFields.tsx:67 — the two spans are one implementation copied and then locally edited — 771 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 with local edits (113 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (113 matched lines × 2 locations) src/features/meetings/person_selector/brother_selector/index.tsx:48 — src/features/meetings/person_selector/brother_selector/index.tsx:48 · src/features/meetings/person_selector/student_selector/index.tsx:65 — the two spans are one implementation copied and then locally edited — 527 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 (104 lines × 2 locations) · ×1
  • Duplicated block (104 lines × 2 locations) src/features/app_start/vip/congregation_create/congregation_access_code/index.tsx:68 — src/features/app_start/vip/congregation_create/congregation_access_code/index.tsx:68 · src/features/app_start/vip/congregation_create/congregation_master_key/index.tsx:82 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
R10 · Code Duplication · Wholesale file copy (104 identical lines × 2 files) · ×1
  • Wholesale file copy (104 identical lines × 2 files) src/features/persons/import_export/confirm_import/index.tsx:1 — src/features/persons/import_export/confirm_import/index.tsx:1 · src/features/persons/speakers_catalog/import_export/confirm_import/index.tsx:2 — these 2 files are line-for-line copies of one another — 104 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
R10 · Code Duplication · Duplicated block (101 lines × 2 locations) · ×1
  • Duplicated block (101 lines × 2 locations) src/features/persons/assignments/useAssignments.tsx:106 — src/features/persons/assignments/useAssignments.tsx:106 · src/features/persons/filter/useFilter.tsx:26 — the 2 copies are spread across 2 files, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases.
R10 · Code Duplication · Duplicated block (98 lines × 2 locations) · ×1
  • Duplicated block (98 lines × 2 locations) src/features/app_start/vip/congregation_encryption/congregation_access_code/index.tsx:12 — src/features/app_start/vip/congregation_encryption/congregation_access_code/index.tsx:12 · src/features/app_start/vip/congregation_encryption/congregation_master_key/index.tsx:12 — 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.
R10 · Code Duplication · Duplicated block with local edits (98 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (98 matched lines × 2 locations) src/features/persons/import_export/confirm_import/useConfirmImport.tsx:46 — src/features/persons/import_export/confirm_import/useConfirmImport.tsx:46 · src/features/persons/speakers_catalog/import_export/confirm_import/useConfirmImport.tsx:67 — the two spans are one implementation copied and then locally edited — 656 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 (92 lines × 2 locations) · ×1
  • Duplicated block (92 lines × 2 locations) src/features/congregation/settings/congregation_privacy/access_code_change/useAccessCodeChange.tsx:14 — src/features/congregation/settings/congregation_privacy/access_code_change/useAccessCodeChange.tsx:14 · src/features/congregation/settings/congregation_privacy/master_key_change/useMasterKeyChange.tsx:14 — 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 with local edits (77 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (77 matched lines × 2 locations) src/features/meetings/person_selector/brother_selector/useBrotherSelector.tsx:281 — src/features/meetings/person_selector/brother_selector/useBrotherSelector.tsx:281 · src/features/meetings/person_selector/student_selector/useStudentSelector.tsx:288 — the two spans are one implementation copied and then locally edited — 469 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 (76 lines × 2 locations) · ×1
  • Duplicated block (76 lines × 2 locations) src/features/persons/import_export/index.tsx:59 — src/features/persons/import_export/index.tsx:59 · src/features/persons/speakers_catalog/import_export/index.tsx:53 — 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.
R10 · Code Duplication · Duplicated block (72 lines × 2 locations) · ×1
  • Duplicated block (72 lines × 2 locations) src/features/meetings/person_selector/outgoing_speaker/index.tsx:26 — src/features/meetings/person_selector/outgoing_speaker/index.tsx:26 · src/features/meetings/person_selector/visiting_speaker/index.tsx:39 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
R10 · Code Duplication · Duplicated block (70 lines × 2 locations) · ×1
  • Duplicated block (70 lines × 2 locations) src/features/persons/speakers_catalog/other_congregations/congregation_info/view/index.tsx:142 — src/features/persons/speakers_catalog/other_congregations/congregation_info/view/index.tsx:142 · src/features/persons/speakers_catalog/other_congregations/congregation_info/view/index.tsx:218 — 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.
R2 · Cyclomatic Complexity · Complex function schedulesMidweekInfo (cyclomatic 121, cognitive 289) · ×1
  • Complex function schedulesMidweekInfo (cyclomatic 121, cognitive 289) src/services/app/schedules.ts:139 — schedulesMidweekInfo has cyclomatic complexity 121 and cognitive complexity 289; 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 importDummyPersons (cyclomatic 89, cognitive 171) · ×1
  • Complex function importDummyPersons (cyclomatic 89, cognitive 171) src/utils/dev.ts:67 — importDummyPersons has cyclomatic complexity 89 and cognitive complexity 171; 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 dbExportDataBackup (cyclomatic 86, cognitive 221) · ×1
  • Complex function dbExportDataBackup (cyclomatic 86, cognitive 221) src/services/worker/backupUtils.ts:1757 — dbExportDataBackup has cyclomatic complexity 86 and cognitive complexity 221; 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 WeekendEditor (cyclomatic 68, cognitive 59) · ×1
  • Complex function WeekendEditor (cyclomatic 68, cognitive 59) src/features/meetings/weekend_editor/index.tsx:53 — WeekendEditor has cyclomatic complexity 68 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 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 schedulesMidweekData (cyclomatic 55, cognitive 92) · ×1
  • Complex function schedulesMidweekData (cyclomatic 55, cognitive 92) src/services/app/schedules.ts:2047 — schedulesMidweekData has cyclomatic complexity 55 and cognitive complexity 92; 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 MidweekEditor (cyclomatic 55, cognitive 52) · ×1
  • Complex function MidweekEditor (cyclomatic 55, cognitive 52) src/features/meetings/midweek_editor/index.tsx:58 — MidweekEditor has cyclomatic complexity 55 and cognitive complexity 52; 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 applyGroupFilters (cyclomatic 50, cognitive 90) · ×1
  • Complex function applyGroupFilters (cyclomatic 50, cognitive 90) src/services/app/persons.ts:544 — applyGroupFilters has cyclomatic complexity 50 and cognitive complexity 90; 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 50, cognitive 58) · ×1
  • Complex function (anonymous) (cyclomatic 50, cognitive 58) src/features/congregation/settings/import_export/confirm_import/useImportHourglass.jsx:28 — (anonymous) has cyclomatic complexity 50 and cognitive complexity 58; 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 TextField (cyclomatic 46, cognitive 43) · ×1
  • Complex function TextField (cyclomatic 46, cognitive 43) src/components/textfield/index.tsx:16 — TextField has cyclomatic complexity 46 and cognitive complexity 43; 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 Button (cyclomatic 42, cognitive 38) · ×1
  • Complex function Button (cyclomatic 42, cognitive 38) src/components/button/index.tsx:10 — Button has cyclomatic complexity 42 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 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 schedulesGetHistoryDetails (cyclomatic 41, cognitive 58) · ×1
  • Complex function schedulesGetHistoryDetails (cyclomatic 41, cognitive 58) src/services/app/schedules.ts:854 — schedulesGetHistoryDetails has cyclomatic complexity 41 and cognitive complexity 58; 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 39, cognitive 75) · ×1
  • Complex function (anonymous) (cyclomatic 39, cognitive 75) src/features/meetings/meeting_part/useMeetingPart.tsx:189 — (anonymous) has cyclomatic complexity 39 and cognitive complexity 75; 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 NavBar (cyclomatic 38, cognitive 30) · ×1
  • Complex function NavBar (cyclomatic 38, cognitive 30) src/layouts/navbar/index.tsx:60 — NavBar has cyclomatic complexity 38 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 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 schedulesWeekendData (cyclomatic 37, cognitive 54) · ×1
  • Complex function schedulesWeekendData (cyclomatic 37, cognitive 54) src/services/app/schedules.ts:2497 — schedulesWeekendData has cyclomatic complexity 37 and cognitive complexity 54; 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 handleImportData (cyclomatic 37, cognitive 39) · ×1
  • Complex function handleImportData (cyclomatic 37, cognitive 39) src/features/congregation/settings/import_export/confirm_import/useConfirmImport.tsx:520 — handleImportData has cyclomatic complexity 37 and cognitive complexity 39; 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 37, cognitive 12) · ×1
  • Complex function (anonymous) (cyclomatic 37, cognitive 12) src/features/persons/speakers_catalog/import_export/export/useExportSpeakers.tsx:142 — (anonymous) has cyclomatic complexity 37 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 schedulesWeekendInfo (cyclomatic 36, cognitive 56) · ×1
  • Complex function schedulesWeekendInfo (cyclomatic 36, cognitive 56) src/services/app/schedules.ts:602 — schedulesWeekendInfo has cyclomatic complexity 36 and cognitive complexity 56; 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 32, cognitive 59) · ×1
  • Complex function (anonymous) (cyclomatic 32, cognitive 59) src/features/meetings/weekly_schedules/person_component/usePersonComponent.tsx:62 — (anonymous) has cyclomatic complexity 32 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 (anonymous) (cyclomatic 32, cognitive 32) · ×1
  • Complex function (anonymous) (cyclomatic 32, cognitive 32) src/features/app_start/vip/startup/useStartup.tsx:72 — (anonymous) has cyclomatic complexity 32 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 getBadges (cyclomatic 28, cognitive 30) · ×1
  • Complex function getBadges (cyclomatic 28, cognitive 30) src/features/persons/hooks/usePerson.tsx:195 — getBadges has cyclomatic complexity 28 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 EditUpcomingEvent (cyclomatic 27, cognitive 24) · ×1
  • Complex function EditUpcomingEvent (cyclomatic 27, cognitive 24) src/features/activities/upcoming_events/edit_upcoming_event/index.tsx:24 — EditUpcomingEvent has cyclomatic complexity 27 and cognitive complexity 24; 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 MidweekMeeting (cyclomatic 26, cognitive 23) · ×1
  • Complex function MidweekMeeting (cyclomatic 26, cognitive 23) src/features/meetings/weekly_schedules/midweek_meeting/index.tsx:27 — MidweekMeeting has cyclomatic complexity 26 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 (anonymous) (cyclomatic 25, cognitive 62) · ×1
  • Complex function (anonymous) (cyclomatic 25, cognitive 62) src/services/worker/backupUtils.ts:161 — (anonymous) has cyclomatic complexity 25 and cognitive complexity 62; 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 runBackup (cyclomatic 25, cognitive 47) · ×1
  • Complex function runBackup (cyclomatic 25, cognitive 47) src/services/worker/backupAction.ts:36 — runBackup has cyclomatic complexity 25 and cognitive complexity 47; 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 25, cognitive 27) · ×1
  • Complex function (anonymous) (cyclomatic 25, cognitive 27) src/features/persons/list/person_card/usePersonCard.tsx:36 — (anonymous) has cyclomatic complexity 25 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 23, cognitive 25) · ×1
  • Complex function (anonymous) (cyclomatic 23, cognitive 25) src/features/meetings/person_selector/brother_selector/useBrotherSelector.tsx:311 — (anonymous) has cyclomatic complexity 23 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.
R2 · Cyclomatic Complexity · Complex function dbGetMetadata (cyclomatic 23, cognitive 21) · ×1
  • Complex function dbGetMetadata (cyclomatic 23, cognitive 21) src/services/worker/backupUtils.ts:332 — dbGetMetadata has cyclomatic complexity 23 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 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 Badge (cyclomatic 22, cognitive 21) · ×1
  • Complex function Badge (cyclomatic 22, cognitive 21) src/components/badge/index.tsx:109 — Badge has cyclomatic complexity 22 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 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 18) · ×1
  • Complex function (anonymous) (cyclomatic 22, cognitive 18) src/views/meetings/midweek/S140/default/index.tsx:36 — (anonymous) has cyclomatic complexity 22 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 RootLayout (cyclomatic 22, cognitive 17) · ×1
  • Complex function RootLayout (cyclomatic 22, cognitive 17) src/layouts/root_layout/index.tsx:32 — RootLayout 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 schedulesS89Data (cyclomatic 21, cognitive 43) · ×1
  • Complex function schedulesS89Data (cyclomatic 21, cognitive 43) src/services/app/schedules.ts:1791 — schedulesS89Data has cyclomatic complexity 21 and cognitive complexity 43; 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 handleLoginData (cyclomatic 21, cognitive 28) · ×1
  • Complex function handleLoginData (cyclomatic 21, cognitive 28) src/hooks/useUserAutoLogin.tsx:98 — handleLoginData has cyclomatic complexity 21 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 dbRestoreSettings (cyclomatic 21, cognitive 28) · ×1
  • Complex function dbRestoreSettings (cyclomatic 21, cognitive 28) src/services/worker/backupUtils.ts:663 — dbRestoreSettings has cyclomatic complexity 21 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 sourcesPartTiming (cyclomatic 21, cognitive 27) · ×1
  • Complex function sourcesPartTiming (cyclomatic 21, cognitive 27) REDACTED:493 — sourcesPartTiming has cyclomatic complexity 21 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 LivingPart (cyclomatic 21, cognitive 20) · ×1
  • Complex function LivingPart (cyclomatic 21, cognitive 20) src/features/meetings/weekly_schedules/midweek_meeting/living_part/index.tsx:23 — LivingPart has cyclomatic complexity 21 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 Checkbox (cyclomatic 21, cognitive 19) · ×1
  • Complex function Checkbox (cyclomatic 21, cognitive 19) src/components/checkbox/index.tsx:19 — Checkbox has cyclomatic complexity 21 and cognitive complexity 19; 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 Dialog (cyclomatic 21, cognitive 19) · ×1
  • Complex function Dialog (cyclomatic 21, cognitive 19) src/components/dialog/index.tsx:78 — Dialog has cyclomatic complexity 21 and cognitive complexity 19; 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 59) · ×1
  • Complex function (anonymous) (cyclomatic 20, cognitive 59) src/utils/common.ts:104 — (anonymous) has cyclomatic complexity 20 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.
R3 · Large Files · src/services/app/schedules.ts · ×1
  • src/services/app/schedules.ts: 2492 lines of code src/services/app/schedules.ts:1 — src/services/app/schedules.ts has 2492 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 · src/components/illustrations/IllustrationMultiPlatform.tsx · ×1
  • src/components/illustrations/IllustrationMultiPlatform.tsx: 2296 lines of code src/components/illustrations/IllustrationMultiPlatform.tsx:1 — src/components/illustrations/IllustrationMultiPlatform.tsx has 2296 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 · src/services/worker/backupUtils.ts · ×1
  • src/services/worker/backupUtils.ts: 1945 lines of code src/services/worker/backupUtils.ts:1 — src/services/worker/backupUtils.ts has 1945 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 · src/services/app/autofill.ts · ×1
  • src/services/app/autofill.ts: 1798 lines of code src/services/app/autofill.ts:1 — src/services/app/autofill.ts has 1798 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 · src/components/illustrations/IllustrationSecretary.tsx · ×1
  • src/components/illustrations/IllustrationSecretary.tsx: 1513 lines of code src/components/illustrations/IllustrationSecretary.tsx:1 — src/components/illustrations/IllustrationSecretary.tsx has 1513 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 · src/features/meetings/monthly_view/index.tsx · ×1
  • src/features/meetings/monthly_view/index.tsx: 1307 lines of code src/features/meetings/monthly_view/index.tsx:1 — src/features/meetings/monthly_view/index.tsx has 1307 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 · src/utils/dev.ts · ×1
  • src/utils/dev.ts: 1289 lines of code src/utils/dev.ts:1 — src/utils/dev.ts has 1289 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 · src/components/illustrations/IllustrationOtherSchedules.tsx · ×1
  • src/components/illustrations/IllustrationOtherSchedules.tsx: 1077 lines of code src/components/illustrations/IllustrationOtherSchedules.tsx:1 — src/components/illustrations/IllustrationOtherSchedules.tsx has 1077 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 · src/services/app/assignment_selection.ts · ×1
  • src/services/app/assignment_selection.ts: 1077 lines of code src/services/app/assignment_selection.ts:1 — src/services/app/assignment_selection.ts has 1077 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 · src/constants/index.ts · ×1
  • src/constants/index.ts: 1070 lines of code src/constants/index.ts:1 — src/constants/index.ts has 1070 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 · src/services/app/assignments_with_stats.ts · ×1
  • src/services/app/assignments_with_stats.ts: 1032 lines of code src/services/app/assignments_with_stats.ts:1 — src/services/app/assignments_with_stats.ts has 1032 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 · src/services/app/persons.ts · ×1
  • src/services/app/persons.ts: 859 lines of code src/services/app/persons.ts:1 — src/services/app/persons.ts has 859 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 · src/features/persons/speakers_catalog/import_export/confirm_import/useCSVImport.tsx · ×1
  • src/features/persons/speakers_catalog/import_export/confirm_import/useCSVImport.tsx: 723 lines of code src/features/persons/speakers_catalog/import_export/confirm_import/useCSVImport.tsx:1 — src/features/persons/speakers_catalog/import_export/confirm_import/useCSVImport.tsx has 723 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: 703 lines of code REDACTED:1 — REDACTED has 703 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 · src/features/congregation/settings/import_export/confirm_import/useConfirmImport.tsx · ×1
  • src/features/congregation/settings/import_export/confirm_import/useConfirmImport.tsx: 641 lines of code src/features/congregation/settings/import_export/confirm_import/useConfirmImport.tsx:1 — src/features/congregation/settings/import_export/confirm_import/useConfirmImport.tsx has 641 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 · src/services/dexie/visiting_speakers.ts · ×1
  • src/services/dexie/visiting_speakers.ts: 635 lines of code src/services/dexie/visiting_speakers.ts:1 — src/services/dexie/visiting_speakers.ts has 635 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 · src/layouts/navbar/index.tsx · ×1
  • src/layouts/navbar/index.tsx: 615 lines of code src/layouts/navbar/index.tsx:1 — src/layouts/navbar/index.tsx has 615 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 · src/features/meetings/midweek_editor/index.tsx · ×1
  • src/features/meetings/midweek_editor/index.tsx: 592 lines of code src/features/meetings/midweek_editor/index.tsx:1 — src/features/meetings/midweek_editor/index.tsx has 592 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: 560 lines of code REDACTED:1 — REDACTED has 560 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 · src/features/congregation/settings/import_export/confirm_import/useImportHourglass.jsx · ×1
  • src/features/congregation/settings/import_export/confirm_import/useImportHourglass.jsx: 558 lines of code src/features/congregation/settings/import_export/confirm_import/useImportHourglass.jsx:1 — src/features/congregation/settings/import_export/confirm_import/useImportHourglass.jsx has 558 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 · src/states/settings.ts · ×1
  • src/states/settings.ts: 526 lines of code src/states/settings.ts:1 — src/states/settings.ts has 526 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 · src/features/meetings/person_selector/brother_selector/useBrotherSelector.tsx · ×1
  • src/features/meetings/person_selector/brother_selector/useBrotherSelector.tsx: 520 lines of code src/features/meetings/person_selector/brother_selector/useBrotherSelector.tsx:1 — src/features/meetings/person_selector/brother_selector/useBrotherSelector.tsx has 520 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 · src/services/dexie/assignment.ts · ×1
  • src/services/dexie/assignment.ts: 504 lines of code src/services/dexie/assignment.ts:1 — src/services/dexie/assignment.ts has 504 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 · src/features/persons/speakers_catalog/import_export/export/useExportSpeakers.tsx · ×1
  • src/features/persons/speakers_catalog/import_export/export/useExportSpeakers.tsx: 501 lines of code src/features/persons/speakers_catalog/import_export/export/useExportSpeakers.tsx:1 — src/features/persons/speakers_catalog/import_export/export/useExportSpeakers.tsx has 501 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 · src/features/meetings/weekend_editor/index.tsx · ×1
  • src/features/meetings/weekend_editor/index.tsx: 497 lines of code src/features/meetings/weekend_editor/index.tsx:1 — src/features/meetings/weekend_editor/index.tsx has 497 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 · src/features/meetings/person_selector/student_selector/useStudentSelector.tsx · ×1
  • src/features/meetings/person_selector/student_selector/useStudentSelector.tsx: 462 lines of code src/features/meetings/person_selector/student_selector/useStudentSelector.tsx:1 — src/features/meetings/person_selector/student_selector/useStudentSelector.tsx has 462 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 · src/features/meetings/monthly_view/useMonthlyView.tsx · ×1
  • src/features/meetings/monthly_view/useMonthlyView.tsx: 441 lines of code src/features/meetings/monthly_view/useMonthlyView.tsx:1 — src/features/meetings/monthly_view/useMonthlyView.tsx has 441 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 · src/utils/date.ts · ×1
  • src/utils/date.ts: 422 lines of code src/utils/date.ts:1 — src/utils/date.ts has 422 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 · src/features/persons/speakers_catalog/speaker_edit_popup/useSpeakerEditPopup.tsx · ×1
  • src/features/persons/speakers_catalog/speaker_edit_popup/useSpeakerEditPopup.tsx: 410 lines of code src/features/persons/speakers_catalog/speaker_edit_popup/useSpeakerEditPopup.tsx:1 — src/features/persons/speakers_catalog/speaker_edit_popup/useSpeakerEditPopup.tsx has 410 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 · src/services/api/user.ts · ×1
  • src/services/api/user.ts: 404 lines of code src/services/api/user.ts:1 — src/services/api/user.ts has 404 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R5 · Dependency Freshness · Dependency Freshness · ×1
  • Dependency Freshness — 51 outdated package(s); JS/npm CVEs scored in D30
R6 · Tooling · No typecheck script · ×1
  • No typecheck script — test ✓ · lint ✓ · typecheck ✗ — read from this repository's package.json scripts and corroborated against its CI workflows. A script counts when its name or command matches the step: `test` for the suite, `lint` or `prettier` for linting, `typecheck`/`type-check`/`tsc` for type checking. ✗ therefore means no script or CI step under those names was found, NOT that the step is absent from your pipeline — a task invoked by a runner this check does not read, or named something else entirely, is not seen and is worth confirming before acting on a cross. A ✓ means the wiring is DECLARED — a script or CI step under those names exists. It is not a statement that the step passes, or that it runs at all: nothing here installs a dependency or executes a suite.
R6 · Tooling · Type errors in this package cannot fail any build or CI step · ×1
  • Type errors in this package cannot fail any build or CI step package.json:13 — the root package is TypeScript, but a type error in it cannot fail anything this repository runs: its `build` script (`vite build && tsx workbox.config.ts`) compiles TypeScript with a transpile-only tool that strips types without checking them, and no script, config or CI step of the package runs `tsc --noEmit` or another type checker over it. Add a type check that can fail — a `typecheck` script running `tsc --noEmit` (or `vue-tsc`/`svelte-check`) that CI or the workspace pipeline runs, or a build step that checks before it bundles.
R7 · Dead Code · Dead file (~150 LoC) · ×1
  • Dead file (~150 LoC) src/components/multi_select/styled.tsx — no import path from any entry point (129 application, 9 tooling, 5 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/components/multi_select/index.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~125 LoC) · ×1
  • Dead file (~125 LoC) src/features/congregation/settings/public_links/index.tsx — no import path from any entry point (129 application, 9 tooling, 5 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 (~122 LoC) · ×1
  • Dead file (~122 LoC) src/features/meetings/schedule_range_selector/useScheduleRangeSelector.tsx — no import path from any entry point (129 application, 9 tooling, 5 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/features/meetings/schedule_range_selector/index.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~113 LoC) · ×1
  • Dead file (~113 LoC) src/features/meetings/schedule_range_selector/index.tsx — no import path from any entry point (129 application, 9 tooling, 5 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 (~84 LoC) · ×1
  • Dead file (~84 LoC) src/components/info_tip/index.tsx — no import path from any entry point (129 application, 9 tooling, 5 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 (~72 LoC) · ×1
  • Dead file (~72 LoC) src/features/meetings/switch_checkbox/useSwitchCheckbox.tsx — no import path from any entry point (129 application, 9 tooling, 5 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/features/meetings/switch_checkbox/index.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~67 LoC) · ×1
  • Dead file (~67 LoC) src/features/meetings/no_schedule/index.tsx — no import path from any entry point (129 application, 9 tooling, 5 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 (~63 LoC) · ×1
  • Dead file (~63 LoC) src/components/multi_select/index.tsx — no import path from any entry point (129 application, 9 tooling, 5 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 (~34 LoC) · ×1
  • Dead file (~34 LoC) src/components/member_account_item/index.tsx — no import path from any entry point (129 application, 9 tooling, 5 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 (~33 LoC) · ×1
  • Dead file (~33 LoC) src/components/info_tip/types.ts — no import path from any entry point (129 application, 9 tooling, 5 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/components/info_tip/index.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~30 LoC) · ×1
  • Dead file (~30 LoC) src/components/table/table.styles.tsx — no import path from any entry point (129 application, 9 tooling, 5 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 (~29 LoC) · ×1
  • Dead file (~29 LoC) src/features/ministry/report/form_S4/bible_studies/bible_studies_list/bible_study_item/useBibleStudyItem.tsx — no import path from any entry point (129 application, 9 tooling, 5 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 (~25 LoC) · ×1
  • Dead file (~25 LoC) src/components/multi_select/types.ts — no import path from any entry point (129 application, 9 tooling, 5 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/components/multi_select/index.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~24 LoC) · ×1
  • Dead file (~24 LoC) src/components/member_account_item/member_account_item.styled.tsx — no import path from any entry point (129 application, 9 tooling, 5 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/components/member_account_item/index.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~23 LoC) · ×1
  • Dead file (~23 LoC) src/features/meetings/switch_checkbox/index.tsx — no import path from any entry point (129 application, 9 tooling, 5 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 (~17 LoC) · ×1
  • Dead file (~17 LoC) src/services/react/index.ts — no import path from any entry point (129 application, 9 tooling, 5 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 (~16 LoC) · ×1
  • Dead file (~16 LoC) src/components/feature_flag/useFeatureFlag.tsx — no import path from any entry point (129 application, 9 tooling, 5 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/components/feature_flag/index.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~14 LoC) · ×1
  • Dead file (~14 LoC) src/components/member_account_item/member_account_item.types.tsx — no import path from any entry point (129 application, 9 tooling, 5 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/components/member_account_item/index.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~12 LoC) · ×1
  • Dead file (~12 LoC) src/components/feature_flag/index.tsx — no import path from any entry point (129 application, 9 tooling, 5 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 (~7 LoC) · ×1
  • Dead file (~7 LoC) src/services/states/songs.ts — no import path from any entry point (129 application, 9 tooling, 5 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 (~4 LoC) · ×1
  • Dead file (~4 LoC) src/features/meetings/switch_checkbox/index.types.ts — no import path from any entry point (129 application, 9 tooling, 5 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (src/features/meetings/switch_checkbox/index.tsx, src/features/meetings/switch_checkbox/useSwitchCheckbox.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R8 · Dependency Hygiene · Unused dependency '@eslint/compat' · ×1
  • Unused dependency '@eslint/compat' package.json:84 — Declared in the root package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
R8 · Dependency Hygiene · Unused dependency '@eslint/eslintrc' · ×1
  • Unused dependency '@eslint/eslintrc' package.json:85 — Declared in the root package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
R8 · Dependency Hygiene · Unused dependency '@mui/styled-engine-sc' · ×1
  • Unused dependency '@mui/styled-engine-sc' package.json:35 — Declared in the root package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
R8 · Dependency Hygiene · Unused dependency '@svgr/plugin-prettier' · ×1
  • Unused dependency '@svgr/plugin-prettier' package.json:89 — Declared in the root package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
R8 · Dependency Hygiene · Unused dependency 'conventional-changelog-conventionalcommits' · ×1
  • Unused dependency 'conventional-changelog-conventionalcommits' package.json:100 — Declared in the root package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
R8 · Dependency Hygiene · Unused dependency 'node-html-parser' · ×1
  • Unused dependency 'node-html-parser' package.json:61 — Declared in the root package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Minor — 166 finding(s)
P2 · Observability · Console output used as the logging channel · ×40
  • Console output used as the logging channel unused-i18n-keys.ts:47 — `unused-i18n-keys.ts` reports through `console.*` at line 47 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
  • Console output used as the logging channel src/views/meetings/weekend/outgoing_speakers_schedule/index.tsx:15 — `src/views/meetings/weekend/outgoing_speakers_schedule/index.tsx` reports through `console.*` at line 15 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
  • Console output used as the logging channel src/utils/dev.ts:713 — `src/utils/dev.ts` reports through `console.*` at line 713 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
  • Console output used as the logging channel src/utils/privileges.ts:32 — `src/utils/privileges.ts` reports through `console.*` at line 32 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
  • Console output used as the logging channel src/utils/privileges.ts:50 — `src/utils/privileges.ts` reports through `console.*` at line 50 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
  • Console output used as the logging channel src/utils/privileges.ts:55 — `src/utils/privileges.ts` reports through `console.*` at line 55 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
  • Console output used as the logging channel src/utils/spiritual_status.ts:78 — `src/utils/spiritual_status.ts` reports through `console.*` at line 78 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
  • Console output used as the logging channel src/utils/spiritual_status.ts:238 — `src/utils/spiritual_status.ts` reports through `console.*` at line 238 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
  • Console output used as the logging channel src/services/worker/backupAction.ts:166 — `src/services/worker/backupAction.ts` reports through `console.*` at line 166 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
  • Console output used as the logging channel src/services/worker/backupUtils.ts:2399 — `src/services/worker/backupUtils.ts` reports through `console.*` at line 2399 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
  • Console output used as the logging channel src/services/dexie/cong_field_service_reports.ts:225 — `src/services/dexie/cong_field_service_reports.ts` reports through `console.*` at line 225 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
  • Console output used as the logging channel src/services/dexie/metadata.ts:34 — `src/services/dexie/metadata.ts` reports through `console.*` at line 34 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
  • Console output used as the logging channel src/services/dexie/metadata.ts:79 — `src/services/dexie/metadata.ts` reports through `console.*` at line 79 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
  • Console output used as the logging channel src/services/dexie/visiting_speakers.ts:88 — `src/services/dexie/visiting_speakers.ts` reports through `console.*` at line 88 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
  • Console output used as the logging channel src/services/dexie/visiting_speakers.ts:114 — `src/services/dexie/visiting_speakers.ts` reports through `console.*` at line 114 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
  • Console output used as the logging channel src/services/dexie/visiting_speakers.ts:152 — `src/services/dexie/visiting_speakers.ts` reports through `console.*` at line 152 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
  • Console output used as the logging channel src/services/dexie/visiting_speakers.ts:176 — `src/services/dexie/visiting_speakers.ts` reports through `console.*` at line 176 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
  • Console output used as the logging channel src/services/app/meeting_attendance.ts:128 — `src/services/app/meeting_attendance.ts` reports through `console.*` at line 128 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
  • Console output used as the logging channel src/pages/dashboard/meeting_materials/useMeetingMaterials.tsx:43 — `src/pages/dashboard/meeting_materials/useMeetingMaterials.tsx` reports through `console.*` at line 43 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
  • Console output used as the logging channel src/pages/activities/upcoming_events/useUpcomingEvents.tsx:66 — `src/pages/activities/upcoming_events/useUpcomingEvents.tsx` reports through `console.*` at line 66 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
  • Console output used as the logging channel src/hooks/useConsoleWarning.tsx:23 — `src/hooks/useConsoleWarning.tsx` reports through `console.*` at line 23 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
  • Console output used as the logging channel src/hooks/useConsoleWarning.tsx:24 — `src/hooks/useConsoleWarning.tsx` reports through `console.*` at line 24 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
  • Console output used as the logging channel src/hooks/useFirebaseAuth.tsx:51 — `src/hooks/useFirebaseAuth.tsx` reports through `console.*` at line 51 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
  • Console output used as the logging channel src/hooks/useUserAutoLogin.tsx:215 — `src/hooks/useUserAutoLogin.tsx` reports through `console.*` at line 215 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
  • Console output used as the logging channel src/hooks/useUserAutoLogin.tsx:300 — `src/hooks/useUserAutoLogin.tsx` reports through `console.*` at line 300 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
  • + 15 more in this group — see findings.md.
X10 · Duplicated predicate · Duplicated predicate · ×40
  • Duplicated predicate src/features/reports/field_service/persons_list/usePersonsList.tsx:365 — `!isFMF && !isFS && !isFR && !isAP && isBaptized` appears character-identically in 2 files — src/features/reports/field_service/persons_list/usePersonsList.tsx, src/utils/dev.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 src/features/app_start/vip/congregation_create/congregation_access_code/useCongregationAccessCode.tsx:32 — `!isLengthPassed || !isNumberPassed || !isLowerCasePassed || !isUpperCasePassed || !isSpecialSymbolPassed || !isMatch` appears character-identically in 2 files — src/features/app_start/vip/congregation_create/congregation_access_code/useCongregationAccessCode.tsx, src/features/app_start/vip/congregation_create/congregation_master_key/useCongregationMasterKey.tsx. 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 src/features/congregation/settings/first_day_week/index.tsx:21 — `!isMidweekEditor && !isWeekendEditor && !isPublicTalkCoordinator` appears character-identically in 6 files — src/features/congregation/settings/first_day_week/index.tsx, src/features/congregation/settings/meeting_forms/date_format/index.tsx, src/features/congregation/settings/meeting_forms/display_name/index.tsx, src/features/congregation/settings/meeting_forms/index.tsx. 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 src/features/ministry/report/form_S4/submit_report/useSubmitReport.tsx:256 — `!isSecretary && !isGroupOverseer && !isLanguageGroupOverseer` appears character-identically in 2 files — src/features/ministry/report/form_S4/submit_report/useSubmitReport.tsx, src/features/ministry/report/form_S4/withdraw_report/useWithdrawReport.tsx. 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 src/features/congregation/settings/meeting_forms/songs_weekend/index.tsx:17 — `!isWeekendEditor && !isPublicTalkCoordinator` appears character-identically in 2 files — src/features/congregation/settings/meeting_forms/songs_weekend/index.tsx, src/features/congregation/settings/meeting_settings/weekend/monthly_warning/index.tsx. 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 src/features/congregation/field_service_groups/unassigned_publishers/publisher_item/usePublisherItem.tsx:41 — `!member.isOverseer && !member.isAssistant` appears character-identically in 3 files — src/features/congregation/field_service_groups/unassigned_publishers/publisher_item/usePublisherItem.tsx, src/features/congregation/settings/language_groups/group_members/useGroupMembers.tsx, src/services/app/field_service_groups.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 src/features/persons/spiritual_status/baptized_publisher/useBaptizedPublisher.tsx:244 — `!record._deleted && record.start_date !== null` appears character-identically in 4 files — src/features/persons/spiritual_status/baptized_publisher/useBaptizedPublisher.tsx, src/features/persons/spiritual_status/first_report/useFirstReport.tsx, src/features/reports/publisher_records_details/publisher_details/usePublisherDetails.tsx, src/utils/spiritual_status.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 src/features/persons/hooks/usePerson.tsx:179 — `!record._deleted && record.start_date?.length > 0` appears character-identically in 5 files — src/features/persons/hooks/usePerson.tsx, src/features/persons/hooks/usePersons.tsx, src/features/reports/publisher_records_details/month_item/useMonthItem.tsx, src/features/reports/publisher_records_details/publisher_details/usePublisherDetails.tsx. 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 src/features/congregation/field_service_groups/export_groups/useExportGroups.tsx:103 — `!record.isOverseer && !record.isAssistant` appears character-identically in 3 files — src/features/congregation/field_service_groups/export_groups/useExportGroups.tsx, src/features/congregation/field_service_groups/group_members/useGroupMembers.tsx, src/features/congregation/settings/language_groups/group_members/useGroupMembers.tsx. 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 src/features/ministry/ap_application/form_header/useFormHeader.tsx:42 — `!record.status || record.status === 'waiting'` appears character-identically in 2 files — src/features/ministry/ap_application/form_header/useFormHeader.tsx, src/states/persons.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 src/features/persons/assignment_group/useAssignmentGroup.tsx:72 — `(code >= AssignmentCode.MM_StartingConversation && code <= AssignmentCode.MM_Discussion) || code === AssignmentCode.MM_Talk` appears character-identically in 2 files — src/features/persons/assignment_group/useAssignmentGroup.tsx, src/utils/assignments.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 src/features/meetings/person_selector/brother_selector/useBrotherSelector.tsx:275 — `a.weekOf.length === 0 && b.weekOf.length === 0` appears character-identically in 2 files — src/features/meetings/person_selector/brother_selector/useBrotherSelector.tsx, src/features/meetings/person_selector/student_selector/useStudentSelector.tsx. 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 src/features/meetings/weekly_schedules/midweek_meeting/useMidweekMeeting.tsx:127 — `assigned?.value.length > 0 && assigned?.value === userUID` appears character-identically in 2 files — src/features/meetings/weekly_schedules/midweek_meeting/useMidweekMeeting.tsx, src/features/meetings/weekly_schedules/weekend_meeting/useWeekendMeeting.tsx. 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 src/features/meetings/midweek_editor/ministry_part/useMinistryPart.tsx:57 — `classCount === 2 && weekType !== Week.CO_VISIT && !MIDWEEK_WITH_STUDENTS_LANGUAGE_GROUP.includes(languageWeekType)` appears character-identically in 5 files — src/features/meetings/midweek_editor/ministry_part/useMinistryPart.tsx, src/features/meetings/midweek_editor/useMidweekEditor.tsx, src/features/meetings/weekly_schedules/midweek_meeting/ministry_part/part_row/usePartRow.tsx, src/features/meetings/weekly_schedules/midweek_meeting/treasures_part/useTreasuresPart.tsx. 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 src/features/app_start/vip/congregation_encryption/congregation_access_code/useCongregationAccessCode.tsx:83 — `congID.length > 0 && result.cong_id !== congID` appears character-identically in 3 files — src/features/app_start/vip/congregation_encryption/congregation_access_code/useCongregationAccessCode.tsx, src/features/app_start/vip/congregation_encryption/congregation_master_key/useCongregationMasterKey.tsx, src/features/app_start/vip/startup/useStartup.tsx. 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 src/features/reports/publisher_records_details/report_details/bible_studies/useBibleStudies.tsx:21 — `currentReport?.report_data.late.value && currentReport?.report_data.late.submitted.length === 0` appears character-identically in 5 files — src/features/reports/publisher_records_details/report_details/bible_studies/useBibleStudies.tsx, src/features/reports/publisher_records_details/report_details/comments/useComments.tsx, src/features/reports/publisher_records_details/report_details/credit_field/useCreditField.tsx, src/features/reports/publisher_records_details/report_details/hours_field/useHoursField.tsx. 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 src/features/meetings/weekly_schedules/midweek_meeting/living_part/useLivingPart.tsx:75 — `dataView === 'main' && weekType === Week.CO_VISIT` appears character-identically in 2 files — src/features/meetings/weekly_schedules/midweek_meeting/living_part/useLivingPart.tsx, src/features/meetings/weekly_schedules/weekend_meeting/watchtower_study/useWatchtowerStudy.tsx. 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 src/features/persons/hooks/usePerson.tsx:140 — `enrollmentMatches(record.enrollment, enrollment) && record.end_date === null && record._deleted === false` appears character-identically in 2 files — src/features/persons/hooks/usePerson.tsx, src/services/app/persons.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 src/features/meetings/weekly_schedules/midweek_container/useMidweekContainer.tsx:52 — `filteredSources.at(value)?.weekOf || null` appears character-identically in 2 files — src/features/meetings/weekly_schedules/midweek_container/useMidweekContainer.tsx, src/features/meetings/weekly_schedules/weekend_container/useWeekendContainer.tsx. 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 src/views/meetings/midweek/S140/default/S140SourceComplex.tsx:28 — `fontSize.source[lang] || fontSize.source.default` appears character-identically in 3 files — src/views/meetings/midweek/S140/default/S140SourceComplex.tsx, src/views/meetings/midweek/S140/default/S140SourceExtended.tsx, src/views/meetings/midweek/S140/default/S140SourceSimple.tsx. 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 src/views/meetings/midweek/S140/default/S140SourceComplex.tsx:32 — `fontSize.time[lang] || fontSize.time.default` appears character-identically in 2 files — src/views/meetings/midweek/S140/default/S140SourceComplex.tsx, src/views/meetings/midweek/S140/default/S140SourceExtended.tsx. 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 src/features/persons/spiritual_status/baptized_publisher/useBaptizedPublisher.tsx:249 — `histories.length === 0 && value && firstReport.length === 0` appears character-identically in 2 files — src/features/persons/spiritual_status/baptized_publisher/useBaptizedPublisher.tsx, src/utils/spiritual_status.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 src/components/public_witnessing_card/view/day.tsx:51 — `isContent && witnesses.length < needWitnesses` appears character-identically in 2 files — src/components/public_witnessing_card/view/day.tsx, src/components/public_witnessing_card/view/default.tsx. 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 src/features/dashboard/skeleton_loader/useSkeletonLoader.tsx:19 — `isElder || isAttendanceEditor || isGroupOverseer || isLanguageGroupOverseer` appears character-identically in 2 files — src/features/dashboard/skeleton_loader/useSkeletonLoader.tsx, src/pages/dashboard/index.tsx. 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 src/features/ministry/report/form_S4/submit_report/useSubmitReport.tsx:252 — `isSecretary || isGroupOverseer || isLanguageGroupOverseer` appears character-identically in 3 files — src/features/ministry/report/form_S4/submit_report/useSubmitReport.tsx, src/features/ministry/report/form_S4/withdraw_report/useWithdrawReport.tsx, src/pages/dashboard/reports/index.tsx. 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.
  • + 15 more in this group — see findings.md.
X7 · Silent fallback defaults · Pending state with no failure state · ×40
  • Pending state with no failure state src/wrapper/feature_flags/index.tsx:8 — The view draws `<WaitingLoader type="lottie"/>` under `isLoading`, but `isLoading` is settled by a load that can fail and the component draws no failure state, so a failed load is shown as "not yet" for ever, or as the loaded state over its initial value. Give the component a failure state and draw it.
  • Pending state with no failure state src/layouts/root_layout/index.tsx:94 — The view draws `<DashboardSkeletonLoader/>` under `isDashboard`, but `isDashboard` is settled by a load that can fail and the component draws no failure state, so a failed load is shown as "not yet" for ever, or as the loaded state over its initial value. Give the component a failure state and draw it.
  • Pending state with no failure state src/layouts/root_layout/index.tsx:96 — The view draws `<WaitingLoader type="lottie"/>` under `isDashboard`, but `isDashboard` is settled by a load that can fail and the component draws no failure state, so a failed load is shown as "not yet" for ever, or as the loaded state over its initial value. Give the component a failure state and draw it.
  • Pending state with no failure state src/features/whats_new/index.tsx:45 — The view draws `<WaitingLoader size= variant="standard"/>` under `isLoading`, but `isLoading` is settled by a load that can fail and the component draws no failure state, so a failed load is shown as "not yet" for ever, or as the loaded state over its initial value. Give the component a failure state and draw it.
  • Pending state with no failure state src/features/reports/publisher_records_details/export_S21/index.tsx:18 — The view draws `<IconLoading/>` under `isProcessing`, but `isProcessing` is settled by a load that can fail and the component draws no failure state, so a failed load is shown as "not yet" for ever, or as the loaded state over its initial value. Give the component a failure state and draw it.
  • Pending state with no failure state src/features/reports/publisher_records/export_S21/specific_records/inactive_publishers/index.tsx:62 — The view draws `<IconLoading color="var(--white)"/>` under `isProcessing`, but `isProcessing` is settled by a load that can fail and the component draws no failure state, so a failed load is shown as "not yet" for ever, or as the loaded state over its initial value. Give the component a failure state and draw it.
  • Pending state with no failure state src/features/reports/publisher_records/export_S21/specific_records/field_service_groups/index.tsx:58 — The view draws `<IconLoading color="var(--white)"/>` under `isProcessing`, but `isProcessing` is settled by a load that can fail and the component draws no failure state, so a failed load is shown as "not yet" for ever, or as the loaded state over its initial value. Give the component a failure state and draw it.
  • Pending state with no failure state src/features/reports/publisher_records/export_S21/specific_records/active_publishers/index.tsx:58 — The view draws `<IconLoading color="var(--white)"/>` under `isProcessing`, but `isProcessing` is settled by a load that can fail and the component draws no failure state, so a failed load is shown as "not yet" for ever, or as the loaded state over its initial value. Give the component a failure state and draw it.
  • Pending state with no failure state src/features/reports/publisher_records/export_S21/all_records/index.tsx:58 — The view draws `<IconLoading/>` under `isProcessing`, but `isProcessing` is settled by a load that can fail and the component draws no failure state, so a failed load is shown as "not yet" for ever, or as the loaded state over its initial value. Give the component a failure state and draw it.
  • Pending state with no failure state src/features/reports/meeting_attendance/export_S88/index.tsx:17 — The view draws `<IconLoading/>` under `isProcessing`, but `isProcessing` is settled by a load that can fail and the component draws no failure state, so a failed load is shown as "not yet" for ever, or as the loaded state over its initial value. Give the component a failure state and draw it.
  • Pending state with no failure state src/features/persons/speakers_catalog/my_congregation/congregations_access/index.tsx:33 — The view draws `<WaitingLoader size= variant="standard"/>` under `isPending`, but `isPending` is settled by a load that can fail and the component draws no failure state, so a failed load is shown as "not yet" for ever, or as the loaded state over its initial value. Give the component a failure state and draw it.
  • Pending state with no failure state src/features/persons/speakers_catalog/import_export/import/index.tsx:70 — The view draws `<WaitingLoader variant="standard" size= />` under `isProcessing`, but `isProcessing` is settled by a load that can fail and the component draws no failure state, so a failed load is shown as "not yet" for ever, or as the loaded state over its initial value. Give the component a failure state and draw it.
  • Pending state with no failure state src/features/persons/speakers_catalog/import_export/export/index.tsx:242 — The view draws `<IconLoading/>` under `isProcessing`, but `isProcessing` is settled by a load that can fail and the component draws no failure state, so a failed load is shown as "not yet" for ever, or as the loaded state over its initial value. Give the component a failure state and draw it.
  • Pending state with no failure state src/features/persons/speakers_catalog/import_export/confirm_import/index.tsx:198 — The view draws `<IconLoading/>` under `isProcessing`, but `isProcessing` is settled by a load that can fail and the component draws no failure state, so a failed load is shown as "not yet" for ever, or as the loaded state over its initial value. Give the component a failure state and draw it.
  • Pending state with no failure state src/features/persons/import_export/import/index.tsx:69 — The view draws `<WaitingLoader variant="standard" size= />` under `isProcessing`, but `isProcessing` is settled by a load that can fail and the component draws no failure state, so a failed load is shown as "not yet" for ever, or as the loaded state over its initial value. Give the component a failure state and draw it.
  • Pending state with no failure state src/features/persons/import_export/export/index.tsx:51 — The view draws `<IconLoading/>` under `isProcessing`, but `isProcessing` is settled by a load that can fail and the component draws no failure state, so a failed load is shown as "not yet" for ever, or as the loaded state over its initial value. Give the component a failure state and draw it.
  • Pending state with no failure state src/features/persons/import_export/confirm_import/index.tsx:198 — The view draws `<IconLoading/>` under `isProcessing`, but `isProcessing` is settled by a load that can fail and the component draws no failure state, so a failed load is shown as "not yet" for ever, or as the loaded state over its initial value. Give the component a failure state and draw it.
  • Pending state with no failure state src/features/my_profile/sessions/session_item/index.tsx:167 — The view draws `<IconLoading/>` under `isProcessing`, but `isProcessing` is settled by a load that can fail and the component draws no failure state, so a failed load is shown as "not yet" for ever, or as the loaded state over its initial value. Give the component a failure state and draw it.
  • Pending state with no failure state src/features/my_profile/security/mfaDisable/index.tsx:35 — The view draws `<IconLoading width= height= color="var(--black)"/>` under `isProcessing`, but `isProcessing` is settled by a load that can fail and the component draws no failure state, so a failed load is shown as "not yet" for ever, or as the loaded state over its initial value. Give the component a failure state and draw it.
  • Pending state with no failure state src/features/my_profile/security/delete_account/index.tsx:34 — The view draws `<WaitingLoader variant="standard" size= />` under `isLoading`, but `isLoading` is settled by a load that can fail and the component draws no failure state, so a failed load is shown as "not yet" for ever, or as the loaded state over its initial value. Give the component a failure state and draw it.
  • Pending state with no failure state src/features/my_profile/security/delete_account/index.tsx:65 — The view draws `<IconLoading color="var(--black)"/>` under `isProcessing`, but `isProcessing` is settled by a load that can fail and the component draws no failure state, so a failed load is shown as "not yet" for ever, or as the loaded state over its initial value. Give the component a failure state and draw it.
  • Pending state with no failure state src/features/ministry/report/form_S4/withdraw_report/index.tsx:33 — The view draws `<IconLoading/>` under `isProcessing`, but `isProcessing` is settled by a load that can fail and the component draws no failure state, so a failed load is shown as "not yet" for ever, or as the loaded state over its initial value. Give the component a failure state and draw it.
  • Pending state with no failure state src/features/ministry/report/form_S4/submit_report/index.tsx:53 — The view draws `<IconLoading/>` under `isProcessing`, but `isProcessing` is settled by a load that can fail and the component draws no failure state, so a failed load is shown as "not yet" for ever, or as the loaded state over its initial value. Give the component a failure state and draw it.
  • Pending state with no failure state src/features/ministry/application_form/sc_member/action_buttons/index.tsx:25 — The view draws `<IconLoading/>` under `isRejectProcessing`, but `isRejectProcessing` is settled by a load that can fail and the component draws no failure state, so a failed load is shown as "not yet" for ever, or as the loaded state over its initial value. Give the component a failure state and draw it.
  • Pending state with no failure state src/features/ministry/application_form/sc_member/action_buttons/index.tsx:38 — The view draws `<IconLoading/>` under `isApproveProcessing`, but `isApproveProcessing` is settled by a load that can fail and the component draws no failure state, so a failed load is shown as "not yet" for ever, or as the loaded state over its initial value. Give the component a failure state and draw it.
  • + 15 more in this group — see findings.md.
D24 · Comment Value · redundant comment · ×14
  • redundant comment converter/css/convert.js:94 — 5 comments in this file only repeat the code they sit on (lines 94, 100, 110, 116, 290), for example "meeting colors variables". Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment public/firebase-messaging-sw.js:62 — "Initialize Firebase app" repeats the code it sits on: 3 of its 3 words (initialize, firebase, app) are already in `firebase.initializeApp(defaultConfig);`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment src/components/assignments_checklist/index.tsx:85 — "set default values" repeats the code it sits on: 3 of its 3 words (set, default, values) are already in `const defaultValues = {};`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment src/components/public_witnessing_card/public_witnessing_card.types.ts:47 — 5 comments in this file only repeat the code they sit on (lines 47, 77, 86, 102, 114), for example "Props for the PublicWitnessingPlaceCard component.". Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment src/components/text_markup/index.tsx:71 — "Check if the tag has a class name assigned in the props" repeats the code it sits on: 5 of its 6 words (check, tag, class, name, props) are already in `if (props.tagClassNames && props.tagClassNames[tagName])`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment src/features/meetings/person_selector/brother_selector/useBrotherSelector.tsx:471 — "check monthly assignments" repeats the code it sits on: 3 of its 3 words (check, monthly, assignments) are already in `if (assignment.startsWith('WM_') && wmShowMonthlyWarning)`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment src/features/meetings/person_selector/brother_selector/useBrotherSelector.tsx:485 — "check if part is linked to another part" repeats the code it sits on: 3 of its 3 words (check, part, linked) are already in `if (isLinkedPart)`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment src/features/persons/import_export/confirm_import/index.tsx:38 — "Grouping the fields by groups" repeats the code it sits on: 3 of its 3 words (grouping, fields, groups) are already in `const groupedFields = PERSON_FIELD_META.reduce(`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment src/features/reports/publisher_records/publisher_tabs/list_by_groups/useListByGroups.tsx:60 — "sort members by name" repeats the code it sits on: 3 of its 3 words (sort, members, name) are already in `const valid_members = fieldGroupsSortMembersByName(`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment src/services/app/autofill.ts:550 — "CHECK: Elders only?" repeats the code it sits on: 3 of its 3 words (check, elders, only) are already in `elderOnly = sourcesCheckLCElderAssignment(title, desc, sourceLocale);`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment src/services/app/persons.ts:791 — "person is a member — find the head and include them in the returned set" repeats the code it sits on: 7 of its 7 words (person, member, find, head, include, returned, set) are already in `const headPerson = persons.find(`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment src/services/app/schedules.ts:384 — "student main hall" repeats the code it sits on: 3 of its 3 words (student, main, hall) are already in `assignment = schedule.midweek_meeting[`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment src/services/app/schedules.ts:392 — "assistant main hall" repeats the code it sits on: 3 of its 3 words (assistant, main, hall) are already in `assignment = schedule.midweek_meeting[`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment src/utils/dev.ts:856 — "assign language group" repeats the code it sits on: 3 of its 3 words (assign, language, group) are already in `const languageGroup = groups.at(4);`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
D34 · Knowledge Freshness · Orphaned file · ×8
  • Orphaned file src/components/icons/IconDistance.tsx:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/features/congregation/settings/circuit_overseer/weeks_list/useWeeksList.tsx:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/components/icons/IconVoiceSelection.tsx:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/components/icons/IconAirportShuttle.tsx:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/components/icons/IconLocalLibrary.tsx:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/components/icons/IconVacuum.tsx:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/components/icons/IconAirplaneTicket.tsx:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/components/icons/IconCalendarClock.tsx:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
R7 · Dead Code · Unused export 'default' · ×6
  • Unused export 'default' src/components/card_header/index.tsx:51 — Nothing ultimately consumes this binding: its only referrer is the re-export in src/components/index.ts, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in src/components/index.ts in the same commit, or the barrel will import a name that no longer exists.
  • Unused export 'default' src/components/dark_overlay/index.tsx:24 — Nothing ultimately consumes this binding: its only referrer is the re-export in src/components/index.ts, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in src/components/index.ts in the same commit, or the barrel will import a name that no longer exists.
  • Unused export 'default' src/components/icons/IconAddPin.tsx:52 — Nothing ultimately consumes this binding: its only referrer is the re-export in src/components/icons/index.ts, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in src/components/icons/index.ts in the same commit, or the barrel will import a name that no longer exists.
  • Unused export 'default' src/components/icons/IconAirportShuttle.tsx:52 — Nothing ultimately consumes this binding: its only referrer is the re-export in src/components/icons/index.ts, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in src/components/icons/index.ts in the same commit, or the barrel will import a name that no longer exists.
  • Unused export 'default' src/components/icons/IconAssign.tsx:56 — Nothing ultimately consumes this binding: its only referrer is the re-export in src/components/icons/index.ts, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in src/components/icons/index.ts in the same commit, or the barrel will import a name that no longer exists.
  • Unused export 'default' src/components/icons/IconAssigned.tsx:52 — Nothing ultimately consumes this binding: its only referrer is the re-export in src/components/icons/index.ts, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in src/components/icons/index.ts in the same commit, or the barrel will import a name that no longer exists.
D16 · Bus Factor · Off-boarding risk · ×3
  • Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 24 significant file(s) lose their only recent owner: src/features/app_notification/container/useContainer.tsx, src/features/ministry/hooks/useMinistryMonthlyRecord.tsx, src/App.tsx, src/services/dexie/settings.ts, src/hooks/useUserAutoLogin.tsx, src/hooks/useCurrentUser.tsx, src/features/reports/publisher_records_details/month_item/useMonthItem.tsx, src/features/meetings/weekly_schedules/weekend_meeting/useWeekendMeeting.tsx (+16 more). Pair on, review, or document these before any departure.
  • Off-boarding risk: anonymized user #2 — If anonymized user #2 becomes unavailable, 15 significant file(s) lose their only recent owner: src/components/button/index.tsx, src/features/my_profile/user_profile_details/profile_picture_selector/index.tsx, src/components/date_navigator/index.tsx, src/components/time_picker_slider/useLoopedScroll.ts, src/features/my_profile/sessions/session_item/index.tsx, src/views/activities/upcoming_events/UpcomingEvent.tsx, src/components/pane_switcher/index.tsx, src/components/snackbar/index.tsx (+7 more). Pair on, review, or document these before any departure.
  • Off-boarding risk: anonymized user #3 — If anonymized user #3 becomes unavailable, 5 significant file(s) lose their only recent owner: src/features/persons/speakers_catalog/import_export/confirm_import/useCSVImport.tsx, src/utils/speakers.ts, src/utils/congregations.ts, src/definition/assignment.ts, src/services/states/settings.ts. Pair on, review, or document these before any departure.
D30 · Dependency Vulnerabilities · Low CVE · ×2
  • REDACTED
  • REDACTED
D20 · ADR Quality · No ADRs found · ×1
  • No ADRs found package.json:12 — 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 `package.json` makes this repository a deployable product (line 12).
D28 · Secrets (history) · Rotate the exposed credentials · ×1
  • REDACTED
D34 · Knowledge Freshness · Orphaned files with no living knowledge · ×1
  • Orphaned files with no living knowledge — 8 of 653 analysed file(s) have no living knowledge left — their last meaningful change has decayed away, so if one breaks, no one currently understands it (counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated, example/demo and scaffolding-template trees and test files identified by path convention, largest first; 653 of the 2172 production source files in this repository met that bar). None is large enough to earn a read-through of its own, so this row stands in for the per-file rows rather than raising one each — most significant first: src/components/icons/IconDistance.tsx, src/features/congregation/settings/circuit_overseer/weeks_list/useWeeksList.tsx, src/components/icons/IconVoiceSelection.tsx, src/components/icons/IconAirportShuttle.tsx, src/components/icons/IconLocalLibrary.tsx, src/components/icons/IconVacuum.tsx, src/components/icons/IconAirplaneTicket.tsx, src/components/icons/IconCalendarClock.tsx. Attach the read to the next change that touches one of them: have a second person review that change, and leave behind a short comment or test recording what the file is for, so the knowledge comes back at the cost of a change you were making anyway.
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×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.
R7 · Dead Code · Unused export 'StyledIconWrapper' · ×1
  • Unused export 'StyledIconWrapper' src/components/date_picker/index.styles.ts:148 — Nothing imports this binding — it is safe to review for removal.
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 0/64 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.
X5 · Nullable reference types · Strict null checking is not enabled everywhere the repository type-checks · ×1
  • Strict null checking is not enabled everywhere the repository type-checks — 0/1 of this repository's type-checking configuration(s) turn on strict null checking (`"strict": true`, or `"strictNullChecks": true`). A configuration that states neither is counted as OFF, because off is tsc's own default; a solution-style one whose `"files"` is empty and whose `"references"` point at other projects is in neither number, because it checks no source itself. Where it is off, `string` admits `null` and `undefined`: passing a value that is null compiles silently and throws on the first property access.
X5 · Nullable reference types · Null assertions (`!`) override strict null checking · ×1
  • Null assertions (`!`) override strict null checking — ~0.4 `!` null assertions per 1k TypeScript source lines — 66 assertion(s) across the 170513 source line(s) of the 2161 TypeScript file(s) read, which is the only code the operator asserts anything in (a `!` in a `.js` file is not this operator and was not counted, and one in a file whose null checking is off silences nothing). Densest: src/services/app/schedules.ts (15), src/services/app/assignment_selection.ts (11), src/states/app.ts (5). Each one tells the compiler to trust the author about null, suppressing the very diagnostic `strictNullChecks` exists to produce. Many are correct: each is a claim the checker could not verify, and it is wrong only where the value can in fact be missing, so review the densest places first.
Minor — 32 finding(s)
D12 · Dependency Hygiene · Outdated (npm) · ×31
  • Outdated (npm): @mui/icons-material — @mui/icons-material is pinned at 9.4.0; registry.npmjs.org publishes 9.5.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): @mui/lab — @mui/lab is pinned at 9.0.0-beta.9; registry.npmjs.org publishes 9.0.0-beta.10 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): @mui/material — @mui/material is pinned at 9.4.0; registry.npmjs.org publishes 9.5.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): @mui/styled-engine-sc — @mui/styled-engine-sc is pinned at 9.4.0; registry.npmjs.org publishes 9.5.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): @mui/stylis-plugin-rtl — @mui/stylis-plugin-rtl is pinned at 9.4.0; registry.npmjs.org publishes 9.5.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): @mui/system — @mui/system is pinned at 9.4.0; registry.npmjs.org publishes 9.5.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): @mui/utils — @mui/utils is pinned at 9.4.0; registry.npmjs.org publishes 9.5.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): @mui/x-date-pickers — @mui/x-date-pickers is pinned at 9.14.0; registry.npmjs.org publishes 9.18.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): @mui/x-tree-view — @mui/x-tree-view is pinned at 9.14.0; registry.npmjs.org publishes 9.18.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): @react-pdf/renderer — @react-pdf/renderer is pinned at 4.3.2; registry.npmjs.org publishes 4.9.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): @sentry/react — @sentry/react is pinned at 10.74.0; registry.npmjs.org publishes 11.14.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): @tanstack/react-query — @tanstack/react-query is pinned at 5.99.2; registry.npmjs.org publishes 5.108.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): date-fns — date-fns is pinned at 4.1.0; registry.npmjs.org publishes 4.4.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): dexie — dexie is pinned at 4.3.0; registry.npmjs.org publishes 4.4.7 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): firebase — firebase is pinned at 12.19.0; registry.npmjs.org publishes 13.4.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): i18next — i18next is pinned at 26.4.2; registry.npmjs.org publishes 27.1.5 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): ics — ics is pinned at 3.8.1; registry.npmjs.org publishes 3.12.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): jotai — jotai is pinned at 3.0.0; registry.npmjs.org publishes 3.0.2 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): jszip — jszip is pinned at 3.10.1; registry.npmjs.org publishes 3.10.2 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): meeting-schedules-parser — meeting-schedules-parser is pinned at 4.5.0; registry.npmjs.org publishes 4.6.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): nanoid — nanoid is pinned at 5.1.16; registry.npmjs.org publishes 6.0.2 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): node-html-parser — node-html-parser is pinned at 7.1.0; registry.npmjs.org publishes 9.0.7 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): papaparse — papaparse is pinned at 5.7.0; registry.npmjs.org publishes 5.7.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): react — react is pinned at 19.3.0; registry.npmjs.org publishes 19.3.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): react-dom — react-dom is pinned at 19.3.0; registry.npmjs.org publishes 19.3.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • + 6 more in this group — see findings.md.
D24 · Comment Value · doc comments repeat the names · ×1
  • doc comments repeat the names src/components/badge/index.types.ts:101 — 4 of 429 documented parameters and 2 of 549 summaries in `organized` only repeat the member or parameter name (e.g. "Height of the icon." for `iconHeight`). Delete the restating tags, or add what the name does not say.

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-3eba8eb211cc4ed994acf10f78a07577/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-3eba8eb211cc4ed994acf10f78a07577/history-1.json --exit-code 0 --source .0artifacts/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=3200" --report-format json --report-path /tmp/watchdog-gitleaks-3eba8eb211cc4ed994acf10f78a07577/history-2.json --exit-code 0 --source .0artifacts/raw/gitleaks-history-2.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=4200 --max-count=1524" --report-format json --report-path /tmp/watchdog-gitleaks-3eba8eb211cc4ed994acf10f78a07577/history-3.json --exit-code 0 --source .3artifacts/raw/gitleaks-history-3.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-3eba8eb211cc4ed994acf10f78a07577/tree.json --exit-code 0 --source .0artifacts/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 .5artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilitiestrivy—trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** .24artifacts/raw/trivy-fs.json
D31 · IaC & Container Securitytrivy—trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.0—
D32 · Data Compliance (PII/GDPR)semgrep—semgrep --config /opt/semgrep-rules/gdpr.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 .2artifacts/raw/semgrep-gdpr.json
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 01a1eafd-da6d-7562-8ece-24e0addbdf01 · 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