Public report of saeloun/miru-web, 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, 09:48 UTC · Survey ID cd_490294074cbf4d109ea330a98ddcc970

saeloun/miru-web

Measured 17 November 2026, 09:47 UTC, at code version 5b688e8

First survey, so nothing to compare with yet Test reliability: not measured

Test reliability is not measured: The suite could not be re-run, but the repository declares tests of its own unreliable.

CAI score 40.7out of 100 Weak
CriticalWeakAdequateStrongExemplary

The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.

A large codebase: 236,101 lines of product code in 4 projects, tests not counted · Estimated rebuild effort: about 2.0 person-years · Weakest lens: Production Readiness, 29.4

Findings by how serious they are

173 critical 1364 serious 236 minor

11 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, 09:47 UTC

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

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

82of 82 dimensions measured by tools.
1761of 1773 findings point to an exact file and line, so you can open each one in the code. The other 12 concern the repository as a whole, such as missing documentation.
82dimensions across 8 lenses, read from 236,101 lines of product code in 4 projects.
Chapters

Executive summary

saeloun/miru-web falls short of our standard for production, in part because two passwords or keys sit in the current code. It scores 40.7 out of 100 and is rated Weak, and 39 of its 173 critical findings are security problems.

Production Readiness, at 29.4, is the weakest lens and counts most in the score. The best first step is replacing the two exposed passwords or keys and switching the old ones off, worth about 9.3 points. Replacing the three packages under a banned licence comes next, worth about 8.3 points. Raising Production Readiness to 70 would lift the score to about 49.7.

Twenty-three weaknesses in the code could be used by an attacker. Ten passwords or keys in the code's history and two in the code are open to anyone who can read the repository, and forty controls can't be used without a mouse. Fixing the weaknesses the scanner points to, replacing each exposed password or key and making the controls work with a keyboard would close these risks. Setting a waiting period for automatic updates would fix the automatic dependency update that takes a new release at once, and the three unsafe settings in infrastructure or container files need changing to safe values. The 25 pieces of business logic tied to the database or web code need separating from the database and web code.

The product code is 236,101 lines, about €290,000 to rebuild.

A lens is capped at Adequate while one of its dimensions scores below 4 out of 10, however well the rest of the lens does. That way a serious problem in one place always shows in the lens's rating.

How the score is built: what each lens counts for The lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.
Production Readiness 29.4 · counts for 45%Accessibility 43.1 · counts for 25%Code Health 47.0 · counts for 14%Domain Modelling 50.4 · counts for 8%Security and Compliance 66.3 · counts for 4%Maturity 76.7 · counts for 2%Architecture 89.1 · counts for 1%Performance 100.0 · counts for 1%

If Production Readiness rose from 29.4 to 70, the lowest score rated Strong, the score would rise from 40.7 to about 49.7.

Code composition: what the lines of code are
Product code 69%Tests 31%
Rebuild cost: about €290,000 · Estimate
Cost to rebuild€97,000 to €490,000, for 1,612 to 5,115 hours of work, about 2.0 person-years for 1 to 4 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 41. 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: 236,101 lines of product code
What it is notNot a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one.

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

Top priorities

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

1
Resolve the 2 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (2).
Raises the score by about 9.3 points · Low effort · REDACTED Scanning
2
Resolve the 3 Banned license finding(s) in License Compliance.
Raises the score by about 8.3 points · Low effort · License Compliance
3
Resolve the 2 No assertions finding(s) in Test Quality — start with analyze-time-tracking.spec.ts, time-tracking.spec.ts.
Raises the score by about 6.4 points · Low effort · Test Quality

Diagnosis: what the measurements show together

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

Where the investment is most exposed · Value at risk
This code would cost about €290,000 to build again, about 2.0 person-years of work. Its weakest lens is Production Readiness, at 29.4 (Weak). Production Readiness is about whether the product is ready to run in production and to change without breaking. Because the weakest lens counts most in the score, work on Production Readiness also moves the score most.
Based on: the rebuild estimate · the Production Readiness grade · how much each lens counts
What to do: Start with the Production Readiness actions in Top priorities.
If you do one thing first · First action
Resolve the 2 Leaked secret finding(s) in REDACTED Scanning. Of all the actions in this report, it raises the score most for the work it takes: about 9.3 points for low effort, because it clears the 2 REDACTED Scanning findings. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
What hard-to-read code costs each year · Cost
Four dimensions measure how easy the code is to work in: two measure how tangled its logic is, one how much of it is copied, and one how well each part sticks to a single job. In this codebase they average 5.7 out of 10. Code at that level is slower to change than clean code, and we estimate the extra work at 6% to 13% on every change. The history of the code shows how much it changes: about 173,854 lines over the last 90 days, which is about 705,075 lines a year. At that pace, the extra work comes to an estimated 102.5 to 614.7 engineer-days a year, and it grows as more code changes.
How this is estimated: The number of changed lines is measured from the history of the code. The rest rests on two assumptions of our own: code scoring 8 out of 10 or more adds no extra work, and each point below 8 adds 2.5% to 5.6% to every change, never less than 2% to 5% and never more than 40% to 60% in all; and an engineer changes 150 to 400 lines in a day. The result is a range for planning, not a measurement.
Based on: Cyclomatic Complexity · Cognitive Complexity · Code Duplication · Cohesion (LCOM4) · the code's change history
What to do: Start with the files listed under Churn × Complexity Hotspots, which change often and are hard to read, because that is where the extra work is paid most often.

Architecture: which parts of the code depend on which

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

495 modules, with 178 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; 455 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 (global)2 Hiring.Intake3 app.javascript.src.StyledComponents.Modal4 app.javascript.src.common.DeleteEntryModal5 app.javascript.src.components.Authentication.ForgotPassword.PasswordResetLinkSentMsg6 app.javascript.src.components.Clients.ClientForm7 app.javascript.src.components.Payroll.api8 app.javascript.src.components.Profile.Organization.Details.MobileHeader9 app.javascript.src.components.Profile.Organization.Payment.MobileView10 app.javascript.src.components.Reports.AccountsAgingReport.ReportMobileRow11 app.javascript.src.components.Reports.GroupedTimeEntryResults12 app.javascript.src.components.payments.interfaces13 app.javascript.src.components.ui14 app.javascript.src.hooks15 app.javascript.src.mapper16 app.javascript.src.types.invoice17 Api.V118 PdfGeneration19 Reports20 app.javascript.src.StyledComponents21 app.javascript.src.components.Clients.Modals22 app.javascript.src.components.Dashboard23 app.javascript.src.components.InvoiceEmail.Header24 app.javascript.src.components.Payroll.MercuryPayments25 app.javascript.src.components.Profile.Organization.Payment26 app.javascript.src.components.Reports27 app.javascript.src.components.Reports.AccountsAgingReport28 app.javascript.src.components.Reports.OutstandingInvoiceReport29 app.javascript.src.components.Reports.PaymentReport30 app.javascript.src.components.payments31 Analytics.Exports32 Api.V1.Desktop33 Api.V1.Hiring34 Api.V1.Users35 Reports.AccountsAging36 Reports.ClientRevenues37 Reports.OutstandingOverdueInvoices38 Reports.TimeEntries39 app.javascript.src.components.Payroll40 Api.V1.Mobile
1 (global)
2 Hiring.Intake
3 app.javascript.src.StyledComponents.Modal
4 app.javascript.src.common.DeleteEntryModal
5 app.javascript.src.components.Authentication.ForgotPassword.PasswordResetLinkSentMsg
6 app.javascript.src.components.Clients.ClientForm
7 app.javascript.src.components.Payroll.api
8 app.javascript.src.components.Profile.Organization.Details.MobileHeader
9 app.javascript.src.components.Profile.Organization.Payment.MobileView
10 app.javascript.src.components.Reports.AccountsAgingReport.ReportMobileRow
11 app.javascript.src.components.Reports.GroupedTimeEntryResults
12 app.javascript.src.components.payments.interfaces
13 app.javascript.src.components.ui
14 app.javascript.src.hooks
15 app.javascript.src.mapper
16 app.javascript.src.types.invoice
17 Api.V114
18 PdfGeneration1
19 Reports3
20 app.javascript.src.StyledComponents1
21 app.javascript.src.components.Clients.Modals1
22 app.javascript.src.components.Dashboard1
23 app.javascript.src.components.InvoiceEmail.Header1
24 app.javascript.src.components.Payroll.MercuryPayments1
25 app.javascript.src.components.Profile.Organization.Payment1
26 app.javascript.src.components.Reports11
27 app.javascript.src.components.Reports.AccountsAgingReport11
28 app.javascript.src.components.Reports.OutstandingInvoiceReport111
29 app.javascript.src.components.Reports.PaymentReport11
30 app.javascript.src.components.payments3
31 Analytics.Exports11
32 Api.V1.Desktop1
33 Api.V1.Hiring21
34 Api.V1.Users205
35 Reports.AccountsAging11
36 Reports.ClientRevenues11
37 Reports.OutstandingOverdueInvoices11
38 Reports.TimeEntries21
39 app.javascript.src.components.Payroll111
40 Api.V1.Mobile331
Uses a module listed above itPart of a loopThe module itself
1 (global)2 Hiring.Intake3 app.javascript.src.StyledComponents.Modal4 app.javascript.src.common.DeleteEntryModal5 app.javascript.src.components.Authentication.ForgotPassword.PasswordResetLinkSentMsg6 app.javascript.src.components.Clients.ClientForm7 app.javascript.src.components.Payroll.api8 app.javascript.src.components.Profile.Organization.Details.MobileHeader9 app.javascript.src.components.Profile.Organization.Payment.MobileView10 app.javascript.src.components.Reports.AccountsAgingReport.ReportMobileRow11 app.javascript.src.components.Reports.GroupedTimeEntryResults12 app.javascript.src.components.payments.interfaces13 app.javascript.src.components.ui14 app.javascript.src.hooks15 app.javascript.src.mapper16 app.javascript.src.types.invoice17 Api.V118 PdfGeneration19 Reports20 app.javascript.src.StyledComponents21 app.javascript.src.components.Clients.Modals22 app.javascript.src.components.Dashboard23 app.javascript.src.components.InvoiceEmail.Header24 app.javascript.src.components.Payroll.MercuryPayments25 app.javascript.src.components.Profile.Organization.Payment26 app.javascript.src.components.Reports27 app.javascript.src.components.Reports.AccountsAgingReport28 app.javascript.src.components.Reports.OutstandingInvoiceReport29 app.javascript.src.components.Reports.PaymentReport30 app.javascript.src.components.payments31 Analytics.Exports32 Api.V1.Desktop33 Api.V1.Hiring34 Api.V1.Users35 Reports.AccountsAging36 Reports.ClientRevenues37 Reports.OutstandingOverdueInvoices38 Reports.TimeEntries39 app.javascript.src.components.Payroll40 Api.V1.Mobile(global)1Hiring.Intake2app.javascript.src.StyledComponents.Modal3app.javascript.src.common.DeleteEntryModal4app.javascript.src.components.Authentication.ForgotPassword.PasswordResetLinkSentMsg5app.javascript.src.components.Clients.ClientForm6app.javascript.src.components.Payroll.api7app.javascript.src.components.Profile.Organization.Details.MobileHeader8app.javascript.src.components.Profile.Organization.Payment.MobileView9app.javascript.src.components.Reports.AccountsAgingReport.ReportMobileRow10app.javascript.src.components.Reports.GroupedTimeEntryResults11app.javascript.src.components.payments.interfaces12app.javascript.src.components.ui13app.javascript.src.hooks14app.javascript.src.mapper15app.javascript.src.types.invoice16Api.V117PdfGeneration18Reports19app.javascript.src.StyledComponents20app.javascript.src.components.Clients.Modals21app.javascript.src.components.Dashboard22app.javascript.src.components.InvoiceEmail.Header23app.javascript.src.components.Payroll.MercuryPayments24app.javascript.src.components.Profile.Organization.Payment25app.javascript.src.components.Reports26app.javascript.src.components.Reports.AccountsAgingReport27app.javascript.src.components.Reports.OutstandingInvoiceReport28app.javascript.src.components.Reports.PaymentReport29app.javascript.src.components.payments30Analytics.Exports31Api.V1.Desktop32Api.V1.Hiring33Api.V1.Users34Reports.AccountsAging35Reports.ClientRevenues36Reports.OutstandingOverdueInvoices37Reports.TimeEntries38app.javascript.src.components.Payroll39Api.V1.Mobile40141311111111111111131112120511111121111331+455 more modules (most-connected shown)

At a glance — Code Health · 47.0 · Weak · gated by R10, R7 ·

At a glance — Architecture · 89.1 · Strong ·

At a glance — Maturity · 76.7 · Strong ·

At a glance — Readiness · 29.4 · Weak · gated by D13, R4, R8, P7 ·

At a glance — Security · 66.3 · Adequate · gated by D28, D29 ·

At a glance — Domain Modelling · 50.4 · Adequate ·

At a glance — Accessibility · 43.1 · Weak · gated by 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
A05:2025 — Injection38High / Critical
A02:2025 — Security Misconfiguration26High / Critical
A07:2025 — Authentication Failures13High / Critical
A03:2025 — Software Supply Chain Failures5Medium
A01:2025 — Broken Access Control3Medium

Roadmap

Top priorities: Resolve the 2 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (2); Resolve the 3 Banned license finding(s) in License Compliance; Resolve the 2 No assertions finding(s) in Test Quality — start with analyze-time-tracking.spec.ts, time-tracking.spec.ts.

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

Do thisHelpsEffortDimension
Resolve the 2 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (2).+9.3 ptsLowREDACTED Scanning
Resolve the 3 Banned license finding(s) in License Compliance.+8.3 ptsLowLicense Compliance
Resolve the 2 No assertions finding(s) in Test Quality — start with analyze-time-tracking.spec.ts, time-tracking.spec.ts.+6.4 ptsLowTest Quality
Add tests that import the unreached modules (directly or through their public entry).+4.7 ptsMediumTest Coverage
Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.+4.1 ptsMediumDependency Hygiene
Set `open_timeout` and `read_timeout` explicitly on every client (Net::HTTP, Faraday `request: { timeout: }`, HTTParty `timeout:`), add Faraday's `:retry` middleware (faraday-retry) or `retriable`, and a breaker (`circuitbox`, `stoplight`) around dependencies that fail.+2.2 ptsMediumOutbound HTTP resilience
Keep the ORM/table mapping on a boundary data-model + mapper; leave the domain entity framework-free (map row↔domain through a repository).+2.1 ptsMediumDomain ↔ infrastructure boundary
Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.+2.0 ptsMediumKeyboard semantics

File quality

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

FileScoreBandWorst signal
REDACTED3.0SlopSecrets (history): High secret: REDACTED
REDACTED3.5SlopIaC & Container Security: High IaC: REDACTED
REDACTED3.5SlopIaC & Container Security: High IaC: REDACTED
REDACTED3.5SlopIaC & Container Security: High IaC: REDACTED
REDACTED3.6SlopSecrets (history): REDACTED: REDACTED
REDACTED3.7SlopREDACTED Scanning: Leaked secret: REDACTED
REDACTED4.0MixedData Compliance (PII/GDPR): Medium: REDACTED
REDACTED5.0MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED5.1MixedStatic Analysis (SAST): High: REDACTED
REDACTED5.1MixedStatic Analysis (SAST): High: REDACTED
REDACTED5.3MixedData Compliance (PII/GDPR): Medium: REDACTED
app/javascript/src/services/invoiceApi.ts5.6MixedCyclomatic Complexity: InvoiceApiService.transformApiInvoice (cyclomatic 85)
REDACTED5.6MixedIaC & Container Security: Medium IaC: REDACTED
REDACTED5.7MixedStatic Analysis (SAST): Medium: REDACTED
app/javascript/src/components/Profile/Personal/User/Edit/MobileProfileEditor.tsx5.7MixedCyclomatic Complexity: MobileProfileEditor.MobileProfileEditor (cyclomatic 54)
REDACTED5.7MixedStatic Analysis (SAST): High: REDACTED
REDACTED5.7MixedStatic Analysis (SAST): High: REDACTED
REDACTED5.8MixedSecrets (history): High secret: REDACTED
REDACTED5.8MixedSecrets (history): REDACTED: REDACTED
REDACTED5.8MixedStatic Analysis (SAST): High: REDACTED

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

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

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

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

Could not be resolved — 11

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 82 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 — 82 dimensions across the health lenses
D1D2D3D4D5D6D7D10D12D13D14D15D16D17D19D20D21D24D26D27D28D29D30D31D32D34D35D36D37D43D44AC1AC2AC3AC4AC5AC6AX10AX2AX3AX4AX6DM6GD1IC1M1M2M3M4P1P2P3P4P5P6P7P8PF3R1R10R11R2R3R4R6R7R8R9S1X1X12X16X17X18X2X21X24X25X29X3X30X5

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, 1761 of 1773 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
  2. Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
  3. Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.

This report answers yes to all three. That's the bar to hold any assessment to.

Tools & methods

The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.

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

Every finding is locatable in findings.md. Run 01a1e8e7-66be-72a5-9a0d-504de39316f0.

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

Run transparency — what happened this run

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

  • D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: this repository's production source spans .go, .tsx, .ts, .rb, and our analyzer cannot run the .tsx, .ts, .rb test suite(s) — so no coverage was collected for the repository as a whole. The Go half did build and run, and its own line coverage came back at 31.7% — but that is a figure for one half of the product, and we do not publish a partial one as if it were complete. This is OUR limitation, not a defect in the repo — coverage is excluded from the score rather than counted as a near-zero.
  • D10 Test Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The 21 test(s) behind this row are the ones the JavaScript/TypeScript census could read, and this repository also carries at least 913 test source file(s) (.rb) that it cannot: it reads JavaScript/TypeScript test declarations off disk, so a JUnit/pytest-style suite is invisible to it. Skipped tests, zero-assertion tests and the other quality signals on this row are UNMEASURED in that suite — their absence from the counts above is a gap in this analyzer's language coverage, not a finding that those tests are sound.
  • D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This repository declares 2 of its own test(s) unreliable. The built-in reliability runner does not support this repository's ecosystem (.rb, .ts), so the suite was not re-run and no reliability score is given — these are the repository's own declarations, not our measurement.
  • D14 License Compliance — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares package.json, but the licence verdict published here was taken over its gem dependencies. Nothing was read about its npm dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
  • D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
  • D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
  • D21 Naming Consistency — 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. D21's naming rules read C# through Roslyn and every other language through its sidecar model; these languages are left out (PHP's reading is its own change, a Roslyn-loaded VB or F# project has no population builder yet). Their declarations carry no naming verdict this run — this says nothing about whether their names are consistent.
  • D21 Naming Consistency — 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. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
  • D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is a COLLECTOR gap, not an environment fault: no published-package marker D22 reads admitted any project here, so this ecosystem's public API has no collector, and the remedy is to write one — no change to the scan image can close it.
  • D24 Comment Value — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
  • D27 Navigability — 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. Tracing effort is measured over resolved call sites, and all 1476 sampled here came from .js/.ts/.tsx files. This repository's .rb source is a material share of its production lines and contributed none, so the score above is a verdict about the part that was read. Not a finding that the unread half navigates well — it is unmeasured.
  • D32 Data Compliance (PII/GDPR) — 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. `app/javascript/src/types/invoice.ts`, `apps/mobile/App.tsx`, `apps/mobile/src/api.ts` produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
  • AC2 Forms & labels — 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. 255 further occurrence(s) are not listed individually; the score already reflects all 295.
  • AC4 Keyboard semantics — 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. 76 further occurrence(s) are not listed individually; the score already reflects all 116.
  • AC6 Visual & motion safety — 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. 9 further occurrence(s) are not listed individually; the score already reflects all 49.
  • 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 image build failed, and its output does not match a cause we recognise. (rule: unrecognised-build-failure). The renderer reported: compose up failed (exit 17 — an image could not be built) — resolve : lstat .devcontainer: no such file or directory; likely cause (not identified): the image build failed, and its output does not match a cause we recognise; runtime evidence skipped.
  • 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 DockerCompose (REDACTED). compose up failed (exit 17 — an image could not be built) — resolve : lstat .devcontainer: no such file or directory; likely cause (not identified): the image build failed, and its output does not match a cause we recognise; runtime evidence skipped.
  • C1 Data Protection — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
  • 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. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
  • C3 Audit Trail — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
  • C4 Data Retention — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
  • M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
  • 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. 509 further occurrence(s) are not listed individually; the score already reflects all 549.
  • 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. 176 further occurrence(s) are not listed individually; the score already reflects all 216.
  • R3 Large Files — 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. 53 further occurrence(s) are not listed individually; the score already reflects all 93.
  • R4 Test Coverage — 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. 741 further occurrence(s) are not listed individually; the score already reflects all 781.
  • 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. 180 further occurrence(s) are not listed individually; the score already reflects all 220.
  • 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. 87 further occurrence(s) are not listed individually; the score already reflects all 127.
  • X27 Collection changed while being enumerated — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
  • 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.

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

Limitations & what we did not check

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

Per-dimension blind spots

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

  • D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
  • D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
  • D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
  • D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
  • D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
  • D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
  • D7 Architectural Integrity: Layering is checked against detected/declared rules — an architecture whose boundaries live in convention or in code review, not in a rule a scanner can read, is not enforced here.
  • 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.
  • D21 Naming Consistency: Naming consistency compares each name with the convention its structural peers follow in this repository: it cannot tell whether a consistently used name is a good one, and languages other than C# and TypeScript are not measured.
  • D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
  • D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
  • D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
  • D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
  • D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
  • D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
  • D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
  • D32 Data Compliance (PII/GDPR): PII/GDPR signals are heuristic pattern matches in code — they flag likely handling concerns, not legal compliance, and cannot trace where data actually flows at runtime.
  • D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
  • D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
  • D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
  • D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (REDACTED, 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.
  • DM6 Domain ↔ infrastructure boundary: Infrastructure reached through a hand-rolled wrapper, a domain-named facade, reflection, or a string-keyed service locator resolves to a non-infra type and isn't seen; the body scan is symbol resolution over syntax, not full dataflow. A clean result means "no resolved infra reference in a domain body", not a proof of purity.
  • M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
  • P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
  • P5 DR & Backup: Backup/restore and disaster-recovery readiness is judged from in-repo evidence — a config that exists is not a tested restore, so the absence of positive evidence is reported as "not evidenced", never scored as present.
  • P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.

Dimensions

D1 · Cyclomatic Complexity4.4 / 10Weak✓ 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 4.4 / 10 · rule-coverage 100% · ceiling Prevented

242 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was index.InvoiceEditor at 167. 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 ConsultantReview.process at 24 — 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: app/services/payroll/consultant_review.rb (ConsultantReview.process at 24), REDACTED (UsersController.me at 19). 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.

WeeklyEntriesCard.WeeklyEntriesCard (cyclomatic 30) · ×2app/javascript/src/components/TimeTracking/WeeklyEntriesCard.tsx:16
index.TimeTracking::TimeTrackingContent (cyclomatic 25) · ×2app/javascript/src/components/TimeTracking/index.tsx:815
Header.Header (cyclomatic 22) · ×2app/javascript/src/components/ClientInvoices/Details/Header.tsx:15
index.InvoiceEditor (cyclomatic 167)app/javascript/src/components/Invoices/InvoiceEditor/index.tsx:62
Page.OrganizationPaymentSettingsPage (cyclomatic 139)app/javascript/src/components/Profile/Organization/Payment/Page.tsx:63

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

What to do

  1. Bring the 2 bodies over 120 down to 120 or less in Cyclomatic Complexity — start with index.InvoiceEditor (cyclomatic 167), Page.OrganizationPaymentSettingsPage (cyclomatic 139). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 2 together lifts Cyclomatic Complexity from 4.4 to about 4.9/10, projected with the scoring formula itself and assuming each lands exactly at 120; a cleaner split scores higher.

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

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

What it measures: How hard the code is for a person to follow, beyond raw branching.

Method: Cognitive complexity per method (Sonar-style nesting-penalized score), computed exhaustively over production code, excluding test projects. Deterministic.

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

220 method(s) exceeded the cognitive complexity threshold of 15; the worst was Page.OrganizationPaymentSettingsPage at 183.

index.Workspace (cognitive 24) · ×2app/javascript/src/components/Agreements/index.tsx:232
index.Holidays::handleDatePicker (cognitive 22) · ×2app/javascript/src/components/Profile/Organization/Holidays/index.tsx:196
Header.Header (cognitive 16) · ×2app/javascript/src/components/ClientInvoices/Header.tsx:13
Page.OrganizationPaymentSettingsPage (cognitive 183)app/javascript/src/components/Profile/Organization/Payment/Page.tsx:63
index.InvoiceEditor (cognitive 136)app/javascript/src/components/Invoices/InvoiceEditor/index.tsx:62

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

What to do

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

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

D3 · God Classes4.8 / 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.8 / 10 · rule-coverage 100% · ceiling Prevented

309 god class(es) detected.

FunctionTooLong: ExpensesTable.ExpensesTable · ×225app/javascript/src/components/Expenses/ExpensesTable.tsx:199
FileTooLong: Payment/Page.tsx · ×44app/javascript/src/components/Profile/Organization/Payment/Page.tsx
ClassTooLong: ExpensesTable · ×21app/javascript/src/components/Expenses/ExpensesTable.tsx:1
TooManyMethods: RazorpayOauthConnection · ×18app/services/payment_providers/razorpay_oauth_connection.rb:6
MethodTooLong: InvoiceApiService.transformApiInvoiceapp/javascript/src/services/invoiceApi.ts:435

What to do

  1. Resolve the 225 FunctionTooLong finding(s) in God Classes — start with index.tsx (67), Header.tsx (6), Page.tsx (4). — One of this dimension's main actionable groups (225 warning-level).
  2. Resolve the 44 FileTooLong finding(s) in God Classes — start with index.tsx (14), Editor.tsx (2), Page.tsx. — One of this dimension's main actionable groups (44 warning-level).
  3. Resolve the 21 ClassTooLong finding(s) in God Classes — start with ExpensesTable.tsx, TeamTable.tsx, OrgEditForm.tsx. — One of this dimension's main actionable groups (21 warning-level).

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

D4 · Code Duplication9.7 / 10Stronggated by 97 serious findings✓ Tool-verified

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

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

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

25 duplicated block group(s) detected. 0.7 % of the production lines (1,651 of 236,101) are in a reported copy. A further 72 rows report members as variants of one another; the share counts each copied line once, however many rows cite it. 9 of the 97 are in trees this repository does not ship — vendored, example/demo, project-template, fixture and benchmark code — and are ranked below the shipped groups rather than excluded from them: the duplication there is real and is still counted in this dimension's score. The dimensions that publish a production-file census leave those trees out of theirs, so this count is deliberately drawn over the wider population. Measured on part of this repository only: .tsx (62% of production source) was not exposed to THIS dimension's token comparison and is not in this count; duplication there is measured by R10 Code Duplication, the frontend lens's card running the same clone algorithm over the JS/TS token stream.

Edited copy of a member (4 corresponding lines) · ×9app/controllers/api/v1/hiring/assignment_reviews_controller.rb:31
Duplicated block (5 lines × 2) · ×7app/controllers/api/v1/employee_records_controller.rb:85
Edited copy of a member (3 corresponding lines) · ×6app/services/hiring/interviews.rb:194
Edited copy of a member (14 corresponding lines) · ×5db/migrate/20261108201000_create_payroll_pto_notifications.rb:5
Edited copy of a member (6 corresponding lines) · ×5app/controllers/api/v1/agreement_templates_controller.rb:62

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

What to do

  1. Resolve the 9 Edited copy of a member (4 corresponding lines) finding(s) in Code Duplication — start with device_policy.rb (2), assignment_reviews_controller.rb, payroll_bank_change_recovery_job.rb. — One of this dimension's main actionable groups (9 warning-level).
  2. Resolve the 7 Duplicated block (5 lines × 2) finding(s) in Code Duplication — start with consultant_billing_identities_controller.rb (2), employee_records_controller.rb, paypal_controller.rb. — One of this dimension's main actionable groups (7 warning-level).
  3. Resolve the 6 Edited copy of a member (3 corresponding lines) finding(s) in Code Duplication — start with analytics_controller.rb (2), interviews.rb, values.rb. — One of this dimension's main actionable groups (6 warning-level).

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

D5 · Coupling10.0 / 10Exemplary✓ Tool-verified

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

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

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

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

4 production modules (npm+Go+RubyGems), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 0 module(s) off the main sequence, with abstractness counted on 3 of the 4 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).

✓ On the Gold path — maintain.

Detailed fixes: d5_recommendation.md.

D6 · Cohesion (LCOM4)4.0 / 10Weak✓ Tool-verified

What it measures: Whether a class's methods are focused on a single responsibility.

Method: LCOM4 cohesion per production class with at least two methods: connected components of methods sharing state or calls, computed syntactically. Deterministic, not a proxy.

Coverage: Exhaustive · type-level: LCOM4 cohesion computed over every production class — the population is all types, not a name convention.

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

1 of 2 classes have LCOM4 above 3.

Low cohesion: InvoiceApiService (LCOM4 7)app/javascript/src/services/invoiceApi.ts:120

What to do

  1. Resolve the 1 Low cohesion finding(s) in Cohesion (LCOM4) — start with invoiceApi.ts. — One of this dimension's main actionable groups (1 warning-level).

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

D7 · Architectural Integrity6.0 / 10Adequate✓ Tool-verified

What it measures: Whether the code respects its intended layering / architecture rules.

Method: Enforcement rung (Prevented/Verified/Documented) per checkable ADR via Roslyn, plus dependency cycles via the engine shared with D5/AX3. Deterministic, exact.

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

No mechanizable ADR was identified, so enforcement is not measured. Dependency cycles not checked (no project-reference graph; where this repository's language has an import-cycle lens, cycles are reported there).

Detailed fixes: d7_recommendation.md.

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

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

No assertions: analyze weekly and monthly views · ×2analyze-time-tracking.spec.ts:4

What to do

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

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

D12 · Dependency Hygiene10.0 / 10Exemplary✓ 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 10.0 / 10 · rule-coverage 100% · ceiling Verified

1 outdated, 0 author-deprecated direct Go module(s), 0 pinning or checksum defect(s). Whether any of these modules is UNMAINTAINED is not graded — proxy.golang.org 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, not a registry one. Known CVEs in this module graph are D30's question, read from REDACTED and go.sum there.

Outdated: golang.org/x/term

✓ On the Gold path — maintain.

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

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

What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.

Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.

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

2 secret(s) detected.

REDACTED

What to do

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

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

D14 · License Compliance4.0 / 10Weak✓ Tool-verified

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

3 of 263 shipped gem(s) use a banned license. Licences were resolved from rubygems.org over the 263 gem(s) a consumer installs — this repository's runtime declarations closed transitively over its committed Gemfile.lock. Development-group and `add_development_dependency` gems are excluded: they are not distributed with this repository. 2 of them publish no licence on rubygems.org; that is missing data, not a violation, and none of them is charged. ★ COVERAGE OF THIS VERDICT: it grades this repository's gem dependencies and nothing else. The repository also declares package.json, and the licences of those dependencies were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.

Banned license: bundler-audit · ×3

What to do

  1. Resolve the 3 Banned license finding(s) in License Compliance. — One of this dimension's main actionable groups (3 issue-level).

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

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

Top hotspots: app/javascript/src/components/Expenses/ExpensesTable.tsx (5×118=590); app/javascript/src/components/Profile/EmployeeRecords/index.tsx (7×80=560); app/javascript/src/components/DocumentSignatures/DeliveryPanel.tsx (5×101=505) Repeated repair below the complexity floor: app/javascript/src/components/Payroll/paymentLabels.ts (7 of 10 changes were fixes); app/services/payroll/split_arrangements.rb (6 of 6 changes were fixes); app/services/payroll/pto_ledger.rb (4 of 7 changes were fixes)

Hotspot: app/javascript/src/components/Expenses/ExpensesTable.tsx · ×49app/javascript/src/components/Expenses/ExpensesTable.tsx:199
Repeated repair: app/javascript/src/components/Payroll/paymentLabels.ts · ×22app/javascript/src/components/Payroll/paymentLabels.ts:206

What to do

  1. Resolve the 49 Hotspot finding(s) in Churn × Complexity Hotspots — start with index.tsx (12), Editor.tsx (2), Review.tsx (2). — One of this dimension's main actionable groups (49 warning-level).
  2. Resolve the 22 Repeated repair finding(s) in Churn × Complexity Hotspots — start with paymentLabels.ts, split_arrangements.rb, pto_ledger.rb. — One of this dimension's main actionable groups (22 warning-level).

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

D16 · Bus Factor7.3 / 10Strong✓ Tool-verified

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

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

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

199 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is app/javascript/src/i18n/locales/ta.ts. Counted over 724 of the 1959 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

What to do

  1. Resolve the 1 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).

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

D17 · Explicit Debt10.0 / 10Stronggated by 7 serious findings✓ 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

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

TodoComment · ×7spec/models/client_search_spec.rb:135

What to do

  1. Resolve the 7 TodoComment finding(s) in Explicit Debt — start with client_search_spec.rb (3), pg_searchable_spec.rb, WorkspaceView.tsx. — One of this dimension's main actionable groups (7 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

2 of 2 documentation facets pass in full. 183 document(s) read across 5 unit(s).

✓ On the Gold path — maintain.

Detailed fixes: d19_recommendation.md.

D20 · ADR Quality10.0 / 10Exemplary○ Nothing flagged

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

0 of 1 evaluated ADRs have a defect readable from the log itself (a missing or empty section, no title, a single option, consequences with no cost, no status, a missing enforcement field, a status the log contradicts, a dangling link, an unlinked second decision on one question, a date that is no calendar day). How well each record argues its case is not measured.

✓ On the Gold path — maintain.

Detailed fixes: d20_recommendation.md.

D21 · Naming Consistency6.2 / 10Adequate✓ Tool-verified

What it measures: Whether names — types, methods, variables — are clear and consistent.

Method: Seven vocabulary-free rules (N1-N7) mine each naming convention from the repository and flag a name that breaks a convention its structural peers in the same unit follow; production C# and TypeScript, each its own population. Deterministic, no model, no sample. Advisory.

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

1 naming inconsistencies among 26 declarations measured against a convention their peers follow.

`{ title, description, ctaLabel = "View invoices", ctaPath = Paths.INVOICES.replace("/*", ""), }` spells `INVOICES` where 25 names in the project spell it `Invoices`app/javascript/src/components/Analytics/components/AnalyticsStates.tsx:62

What to do

  1. Resolve the 1 `{ title, description, ctaLabel = "View invoices", ctaPath =… finding(s) in Naming Consistency — start with AnalyticsStates.tsx. — One of this dimension's main actionable groups (1 recommendation-level).

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

D24 · Comment Value3.6 3.6 / 10Weak✓ 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 3.6 / 10 · rule-coverage 99% · ceiling Documented

17 of 267 judged comments only repeat the code they sit on (6.4 %). 6 comment(s) in another language or script were not judged.

redundant comment · ×10REDACTED:593

What to do

  1. Resolve the 10 redundant comment finding(s) in Comment Value — start with REDACTED (4), Sidebar.tsx (2), time-tracking.spec.ts (2). — One of this dimension's main actionable groups (10 recommendation-level).

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

D26 · Project Cohesion5.0 / 10Adequate✓ Tool-verified

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

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

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

1 of 4 build units (Go, npm) flagged as possibly oversized/incoherent.

Projects may be oversized for their cohesionpackage.json:1

What to do

  1. Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion — start with package.json. — One of this dimension's main actionable groups (1 recommendation-level).

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

D27 · Navigability10.0 / 10Exemplary✓ Tool-verified

What it measures: How far you must trace to follow a call — low indirection and co-located slices read easier.

Method: Call indirection (interface hops, cross-namespace calls, slice-locality scaled) over a sampled set of method invocations, size-aware baseline. Sampled; confidence discounted by symbol-resolution gaps. C# also names each pass-through layer (a class whose every public method only forwards its own parameters to one collaborator) as a located finding; the score is not affected.

Coverage: Slice locality from the first namespace segments, SAMPLED (≤400 methods) — not exhaustive.

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

15 % of calls cross a namespace and 0 % go through an interface, but 100 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: small — navigation cost is tolerated. Measured over the .js/.ts/.tsx source only — this repository's .rb was not sampled for call sites, so this score covers part of the tree, not all of it.

Pass-through layerapp/javascript/src/components/ui/toastr.tsx:3

✓ On the Gold path — maintain.

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

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

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

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

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

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

REDACTED
REDACTED
REDACTED

What to do

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

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

D29 · Static Analysis (SAST)0.1 / 10Critical✓ 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 0.1 / 10 · rule-coverage 100% · ceiling Documented

38 finding(s): 0 critical, 24 high, 14 medium, 0 low. semgrep hit a parse error in 28 file(s) — `app/javascript/src/components/Expenses/ExpensesTable.tsx`, `app/javascript/src/components/Profile/Organization/Payment/Page.tsx`, `app/javascript/src/types/invoice.ts` (line 24, line 25, line 26, …), `apps/mobile/App.tsx` (line 220), `apps/mobile/src/api.ts` (line 80), … (+23 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 2 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

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

What to do

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

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

D30 · Dependency Vulnerabilities9.6 / 10Stronggated by 3 serious findings✓ 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 9.6 / 10 · rule-coverage 100% · ceiling Documented

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

REDACTED

What to do

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

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

D31 · IaC & Container Security6.8 / 10Adequate✓ Tool-verified

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

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

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

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

REDACTED
REDACTED
REDACTED

What to do

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

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

D32 · Data Compliance (PII/GDPR)7.3 / 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 7.3 / 10 · rule-coverage 100% · ceiling Documented

3 finding(s): 0 critical, 0 high, 3 medium, 0 low. semgrep could not parse 3 file(s) — `app/javascript/src/types/invoice.ts`, `apps/mobile/App.tsx`, `apps/mobile/src/api.ts` — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.

REDACTED
REDACTED

What to do

  1. Resolve the 2 REDACTED finding(s) in Data Compliance (PII/GDPR) — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 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 Freshness8.5 / 10Adequategated by 2 critical findings✓ 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 8.5 / 10 · rule-coverage 100% · ceiling Documented

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

Orphaned knowledge · ×2app/javascript/src/components/TimesheetEntries/index.tsx:1
Orphaned file · ×108app/javascript/src/components/TimesheetEntries/TimeEntryForm/MobileEntryForm.tsx:1
Further orphaned files (smaller)

What to do

  1. Resolve the 2 Orphaned knowledge finding(s) in Knowledge Freshness — start with index.tsx, PrivacyPolicyModal.tsx. — One of this dimension's main actionable groups (2 issue-level).
  2. Resolve the 108 Orphaned file finding(s) in Knowledge Freshness — start with index.tsx (36), TableRow.tsx (5), MobileEntryForm.tsx. — One of this dimension's main actionable groups (108 recommendation-level).
  3. Resolve the 1 Further orphaned files (smaller) finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).

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

D35 · Change Coupling9.9 / 10Adequategated by 2 critical findings✓ 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 9.9 / 10 · rule-coverage 100% · ceiling Documented

Strongest change-coupling: MobileProfileEditor.tsx↔ProfileEditor.tsx 85%; ClientEditor.tsx↔MobileClientEditor.tsx 79%; CreateClientModal.tsx↔EditClientModal.tsx 76%

Boundary-crossing change coupling: client.rb ↔ client_policy.rb · ×2app/models/client.rb:1
Change coupling: MobileProfileEditor.tsx ↔ ProfileEditor.tsx · ×14app/javascript/src/components/Profile/Personal/User/Edit/MobileProfileEditor.tsx:1

What to do

  1. Resolve the 2 Boundary-crossing change coupling finding(s) in Change Coupling — start with client.rb, company.rb. — One of this dimension's main actionable groups (2 issue-level).
  2. Resolve the 14 Change coupling finding(s) in Change Coupling — start with index.tsx (3), InvoiceListHeader.tsx (2), MobileProfileEditor.tsx. — One of this dimension's main actionable groups (14 warning-level).

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

D36 · Supply-chain Provenance & Signing5.0 / 10Adequate✓ 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 5.0 / 10 · rule-coverage 100% · ceiling Documented

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

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 recommendation-level).
  2. 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 5 platform declaration(s) and 197 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 alternatives4.7 / 10Weak✓ Tool-verified

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

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

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

  • An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative. (×21) — app/javascript/src/common/EmptyStates/index.tsx:36, app/javascript/src/common/EmptyStates/index.tsx:38, app/javascript/src/common/Error/index.tsx:25, …

What to do

  • Add a text alternative — alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, an aria-label or inner fallback content on canvas, and a captions <track> on video.
AC2 · Forms & labels4.4 / 10Weak✓ 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.

  • A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one). (×12) — app/javascript/src/StyledComponents/Pagination/index.tsx:52, app/javascript/src/StyledComponents/Pagination/index.tsx:87, app/javascript/src/common/ChartBar/index.tsx:36, …
  • This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it. (×3) — app/javascript/src/StyledComponents/Pagination/index.tsx:105, app/javascript/src/common/CustomYearPicker/index.tsx:69, app/javascript/src/components/Clients/ClientsTable.tsx:313
  • This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label htmlFor>, a wrapping <label>, or aria-label. (×8) — app/javascript/src/StyledComponents/TimeInput/index.tsx:69, app/javascript/src/common/CustomDateRangeWIthInput/index.tsx:224, app/javascript/src/common/CustomDateRangeWIthInput/index.tsx:246, …
  • 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. — app/javascript/src/common/CustomAsyncSelect/index.tsx:35
  • 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. (×4) — app/javascript/src/common/CustomDatePicker/index.tsx:71, app/javascript/src/common/CustomDateRangePicker/index.tsx:198, app/javascript/src/common/CustomDateRangeWIthInput/index.tsx:270, …
  • This select is named only by the placeholder of its value part. Nothing is typed into a select, so the placeholder does not vanish on input: it is shown as the trigger's text until a value is chosen, and then the chosen value replaces it — so at no point does the control state what the choice is for, and the trigger's role (combobox) takes its name from the author, not from that text. Name it: an aria-label on the trigger, or an id on the trigger with a <label htmlFor> pointing at it. (×6) — app/javascript/src/common/SearchTimeEntries.tsx:49, app/javascript/src/components/Analytics/components/AnalyticsFilters.tsx:65, app/javascript/src/components/Clients/ClientForm/ClientEditor.tsx:259, …
  • This <label> has no htmlFor and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label htmlFor="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id. (×6) — app/javascript/src/common/SearchTimeEntries.tsx:77, app/javascript/src/components/Analytics/components/AnalyticsFilters.tsx:64, app/javascript/src/components/Analytics/components/AnalyticsFilters.tsx:80, …

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 structure6.8 / 10Adequate✓ Tool-verified

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

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

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

  • A <table> with data cells but no <th> gives assistive technology no way to associate cells with their headers. Mark the header row/column cells as <th> (with a scope). (×6) — app/javascript/src/components/ClientInvoices/Details/InvoiceTotalSummary.tsx:18, app/javascript/src/components/InvoiceEmail/InvoiceTotalSummary.tsx:18, app/javascript/src/components/Invoices/Invoice/InvoiceTotalSummary.tsx:18, …
  • A <tr> may hold only <td>/<th> cells. Text or a value written between the cells is moved out of the table by the browser, so it is read detached from its row. Wrap it in a <td>. — app/javascript/src/components/Invoices/List/Table/TableRow.tsx:109
  • Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one. (×6) — app/javascript/src/components/Invoices/List/Table/TableRow.tsx:158, app/javascript/src/components/Profile/EmployeeRecords/index.tsx:273, app/javascript/src/components/Subscriptions/PlanSelection/index.tsx:52, …
  • The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en"). (×7) — app/views/layouts/pdf.html.erb:2, app/views/pdfs/analytics_export.html.erb:2, app/views/pdfs/client_revenues.html.erb:2, …
  • A page with no <title> gives no name in the tab, history or screen-reader page list. Add a descriptive <title> in <head>. (×2) — app/views/layouts/pdf.html.erb:2, app/views/payroll_india_mailer/report.html.erb:2
  • No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. (×7) — app/views/layouts/pdf.html.erb:2, app/views/pdfs/analytics_export.html.erb:2, app/views/pdfs/client_revenues.html.erb:2, …

What to do

  • Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
AC4 · Keyboard semantics1.5 / 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. (×37) — app/javascript/src/StyledComponents/SummaryDashboard.tsx:32, app/javascript/src/common/CustomAdvanceInput/index.tsx:57, app/javascript/src/common/CustomAdvanceInput/index.tsx:62, …
  • This <div> binds mouse-enter and mouse-leave and nothing else — no click, no key handler, no focus handler, and no tabIndex={0}, so it cannot even take focus. A keyboard user cannot hover, so whatever the pair reveals or highlights is reachable with a mouse only. Bind the same state to focus/blur as well, and add tabIndex={0}="0" so the element can receive that focus. (×2) — app/javascript/src/StyledComponents/Tooltip.tsx:43, app/javascript/src/components/Invoices/List/BulkActionsWrapper/BulkActions.tsx:36
  • A click handler on a plain element with no role and no tabindex: even where another element's key handler can reach it, assistive tech can neither focus it nor announce what it is. Use a <button>, or add role + tabIndex={0}. — app/javascript/src/components/Expenses/Modals/ExpenseForm.tsx:182

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 safety5.0 / 10Adequate✓ 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.

  • <input> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2). (×3) — app/javascript/src/common/LocaleSelector/LocaleDropdown.tsx:103, app/javascript/src/components/Clients/Modals/AddProject.tsx:77, app/javascript/src/components/payments/PaymentSearch/index.tsx:94
  • <select> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2). (×5) — app/javascript/src/components/Clients/Details/TotalHoursChart.tsx:35, app/javascript/src/components/Clients/Modals/AddProject.tsx:58, app/javascript/src/components/Clients/TotalHoursChart.tsx:60, …
  • <button> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2). (×4) — app/javascript/src/components/Clients/Modals/AddProject.tsx:132, app/javascript/src/components/Profile/Organization/Details/MobileHeader.tsx:19, app/javascript/src/components/Profile/Organization/Details/MobileHeader.tsx:31, …
  • This element's Tailwind text/background colour utilities fall below the 4.5:1 WCAG AA minimum for normal text. Pick a darker or lighter shade. (×3) — app/javascript/src/components/Dashboard/DashboardTimerControl.tsx:252, app/javascript/src/components/Dashboard/DashboardTimerControl.tsx:327, app/javascript/src/components/payments/Success/index.tsx:53
  • <div> moves — its `animate-spin` utility runs with no motion-safe:/motion-reduce: variant — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:. (×4) — app/javascript/src/components/Dashboard/MonochromeCharts.tsx:61, app/javascript/src/components/Dashboard/MonochromeCharts.tsx:214, app/javascript/src/components/Invoices/List/RecentlyUpdated/InfiniteScrollRecentlyUpdated.tsx:222, …
  • <div> moves — its inline style sets `animation: slideIn 1s ease-out` — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:. — app/javascript/src/components/Dashboard/MonochromeCharts.tsx:240
  • <span> moves — its `animate-ping` utility runs with no motion-safe:/motion-reduce: variant — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:. — app/javascript/src/components/TimeTracking/WeekDaySelector.tsx:66
  • `button, .button` sets color: white on background-color: #a78bfa — 2.7:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — app/views/reports/compensation_profitability/show.html.erb:20
  • `button[type=submit],.button` sets color: white on background-color: #a78bfa — 2.7:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — app/views/reports/profitability_scenarios/_styles.html.erb:8
  • The inline foreground/background colours fall below the 4.5:1 WCAG AA minimum for normal text. Darken/lighten one of them. — app/views/subscription_mailer/trial_pro_features.html.erb:31
  • `.sidebar` moves (`transition: transform 0.3s ease`) 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. — public/test-mobile-nav.html:88
  • `.focus-ring` 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. — app/javascript/stylesheets/application.scss:290
  • `.sidebar__reset` 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. — app/javascript/stylesheets/application.scss:323
  • `.sidebar__apply` 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. — app/javascript/stylesheets/application.scss:327
  • `.header__searchInput` 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. — app/javascript/stylesheets/application.scss:394
  • `.header__button` 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. — app/javascript/stylesheets/application.scss:398
  • `.form__textarea` 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. — app/javascript/stylesheets/application.scss:438
  • `.form__input_submit` 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. — app/javascript/stylesheets/application.scss:442
  • `.form__input` 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. — app/javascript/stylesheets/application.scss:446
  • `.form__button` 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. — app/javascript/stylesheets/application.scss:458
  • `.form__button_outline` 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. — app/javascript/stylesheets/application.scss:462
  • `.form__save` 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. — app/javascript/stylesheets/application.scss:474
  • `.form__cancel` 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. — app/javascript/stylesheets/application.scss:478
  • `.button` 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. — app/javascript/stylesheets/application.scss:487
  • `.page-content__search-input` 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. — app/javascript/stylesheets/application.scss:530
  • `.page-content__new-user-button` 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. — app/javascript/stylesheets/application.scss:546

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.1 / 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.

AX2 · Stateful singletons10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether singleton services avoid mutable shared instance state that concurrent callers would race on.

Method: Roslyn scan: singleton field mutations unguarded by lock or Interlocked, per type; syntax-based guard detection. Deterministic, traceable per field.

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

Other · Architecture — Whether the project-reference graph is acyclic (cycles block independent build/deploy and signal eroding boundaries).

Method: Project reference cycles via elementary-DFS over real .csproj references, using the engine shared with D5/D7; cyclic versus acyclic. Exhaustive, deterministic.

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

Other · Architecture — Whether dependencies point inward (Domain ← Application ← Infrastructure/Web) — the clean-architecture dependency rule, checked across the project graph.

Method: Layer violations by name-segment inference (Domain/Core to Application to Infrastructure/Web) over the project-reference graph. Exhaustive over all projects, deterministic.

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

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

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

DM6 · Domain ↔ infrastructure boundary5.0 / 10Adequate✓ Tool-verified

Other · Domain Modelling — Whether the domain layer stays free of infrastructure dependencies — a domain aggregate fused to a persistence ORM (ActiveRecord/Sequel/ROM) on its own declaration (active-record) couples the domain to infrastructure. The clean-architecture dependency rule.

Method: Roslyn (DDD-gated): domain-layer types scanned for infrastructure usage in member SIGNATURES and inside method/accessor BODIES — resolved calls and object-creations into EF/Marten/HTTP/Mongo/Redis/message-bus types (not just a namespace allowlist). Deterministic, symbol-resolved, exhaustive over domain-layer bodies, DDD-native.

Coverage: Domain layer identified by NAMESPACE heuristic; infrastructure then resolved by symbol in member SIGNATURES and method/accessor BODIES — rename the layer and the check evaporates.

  • `AgentKey` is a domain concept fused to persistence ON ITS OWN DECLARATION (Rails ActiveRecord — `ApplicationRecord`) — the domain entity IS the ActiveRecord row (active-record), and it carries domain behaviour on the persistence type. A schema/persistence change ripples straight into the domain. Keep the ORM/table mapping on a boundary data-model + a mapper, and the domain entity framework-free (map row↔domain through a repository). — app/models/agent_key.rb:3
  • `CliSession` is a domain concept fused to persistence ON ITS OWN DECLARATION (Rails ActiveRecord — `ApplicationRecord`) — the domain entity IS the ActiveRecord row (active-record), and it carries domain behaviour on the persistence type. A schema/persistence change ripples straight into the domain. Keep the ORM/table mapping on a boundary data-model + a mapper, and the domain entity framework-free (map row↔domain through a repository). — app/models/cli_session.rb:3
  • `Client` is a domain concept fused to persistence ON ITS OWN DECLARATION (Rails ActiveRecord — `ApplicationRecord`) — the domain entity IS the ActiveRecord row (active-record), and it carries domain behaviour on the persistence type. A schema/persistence change ripples straight into the domain. Keep the ORM/table mapping on a boundary data-model + a mapper, and the domain entity framework-free (map row↔domain through a repository). — app/models/client.rb:3
  • `Company` is a domain concept fused to persistence ON ITS OWN DECLARATION (Rails ActiveRecord — `ApplicationRecord`) — the domain entity IS the ActiveRecord row (active-record), and it carries domain behaviour on the persistence type. A schema/persistence change ripples straight into the domain. Keep the ORM/table mapping on a boundary data-model + a mapper, and the domain entity framework-free (map row↔domain through a repository). — app/models/company.rb:3
  • `Employment` is a domain concept fused to persistence ON ITS OWN DECLARATION (Rails ActiveRecord — `ApplicationRecord`) — the domain entity IS the ActiveRecord row (active-record), and it carries domain behaviour on the persistence type. A schema/persistence change ripples straight into the domain. Keep the ORM/table mapping on a boundary data-model + a mapper, and the domain entity framework-free (map row↔domain through a repository). — app/models/employment.rb:3
  • `Expense` is a domain concept fused to persistence ON ITS OWN DECLARATION (Rails ActiveRecord — `ApplicationRecord`) — the domain entity IS the ActiveRecord row (active-record), and it carries domain behaviour on the persistence type. A schema/persistence change ripples straight into the domain. Keep the ORM/table mapping on a boundary data-model + a mapper, and the domain entity framework-free (map row↔domain through a repository). — app/models/expense.rb:3
  • `HiringAssignment` is a domain concept fused to persistence ON ITS OWN DECLARATION (Rails ActiveRecord — `ApplicationRecord`) — the domain entity IS the ActiveRecord row (active-record), and it carries domain behaviour on the persistence type. A schema/persistence change ripples straight into the domain. Keep the ORM/table mapping on a boundary data-model + a mapper, and the domain entity framework-free (map row↔domain through a repository). — app/models/hiring_assignment.rb:3
  • `HiringInterview` is a domain concept fused to persistence ON ITS OWN DECLARATION (Rails ActiveRecord — `ApplicationRecord`) — the domain entity IS the ActiveRecord row (active-record), and it carries domain behaviour on the persistence type. A schema/persistence change ripples straight into the domain. Keep the ORM/table mapping on a boundary data-model + a mapper, and the domain entity framework-free (map row↔domain through a repository). — app/models/hiring_interview.rb:3
  • `HiringInterviewBooking` is a domain concept fused to persistence ON ITS OWN DECLARATION (Rails ActiveRecord — `ApplicationRecord`) — the domain entity IS the ActiveRecord row (active-record), and it carries domain behaviour on the persistence type. A schema/persistence change ripples straight into the domain. Keep the ORM/table mapping on a boundary data-model + a mapper, and the domain entity framework-free (map row↔domain through a repository). — app/models/hiring_interview_booking.rb:3
  • `HiringMessage` is a domain concept fused to persistence ON ITS OWN DECLARATION (Rails ActiveRecord — `ApplicationRecord`) — the domain entity IS the ActiveRecord row (active-record), and it carries domain behaviour on the persistence type. A schema/persistence change ripples straight into the domain. Keep the ORM/table mapping on a boundary data-model + a mapper, and the domain entity framework-free (map row↔domain through a repository). — app/models/hiring_message.rb:3
  • `HiringOffer` is a domain concept fused to persistence ON ITS OWN DECLARATION (Rails ActiveRecord — `ApplicationRecord`) — the domain entity IS the ActiveRecord row (active-record), and it carries domain behaviour on the persistence type. A schema/persistence change ripples straight into the domain. Keep the ORM/table mapping on a boundary data-model + a mapper, and the domain entity framework-free (map row↔domain through a repository). — app/models/hiring_offer.rb:3
  • `Invoice` is a domain concept fused to persistence ON ITS OWN DECLARATION (Rails ActiveRecord — `ApplicationRecord`) — the domain entity IS the ActiveRecord row (active-record), and it carries domain behaviour on the persistence type. A schema/persistence change ripples straight into the domain. Keep the ORM/table mapping on a boundary data-model + a mapper, and the domain entity framework-free (map row↔domain through a repository). — app/models/invoice.rb:3
  • `InvoiceTax` is a domain concept fused to persistence ON ITS OWN DECLARATION (Rails ActiveRecord — `ApplicationRecord`) — the domain entity IS the ActiveRecord row (active-record), and it carries domain behaviour on the persistence type. A schema/persistence change ripples straight into the domain. Keep the ORM/table mapping on a boundary data-model + a mapper, and the domain entity framework-free (map row↔domain through a repository). — app/models/invoice_tax.rb:3
  • `Metric` is a domain concept fused to persistence ON ITS OWN DECLARATION (Rails ActiveRecord — `ApplicationRecord`) — the domain entity IS the ActiveRecord row (active-record), and it carries domain behaviour on the persistence type. A schema/persistence change ripples straight into the domain. Keep the ORM/table mapping on a boundary data-model + a mapper, and the domain entity framework-free (map row↔domain through a repository). — app/models/metric.rb:3
  • `NativeGoogleAuthRequest` is a domain concept fused to persistence ON ITS OWN DECLARATION (Rails ActiveRecord — `ApplicationRecord`) — the domain entity IS the ActiveRecord row (active-record), and it carries domain behaviour on the persistence type. A schema/persistence change ripples straight into the domain. Keep the ORM/table mapping on a boundary data-model + a mapper, and the domain entity framework-free (map row↔domain through a repository). — app/models/native_google_auth_request.rb:3
  • `NotificationPreference` is a domain concept fused to persistence ON ITS OWN DECLARATION (Rails ActiveRecord — `ApplicationRecord`) — the domain entity IS the ActiveRecord row (active-record), and it carries domain behaviour on the persistence type. A schema/persistence change ripples straight into the domain. Keep the ORM/table mapping on a boundary data-model + a mapper, and the domain entity framework-free (map row↔domain through a repository). — app/models/notification_preference.rb:3
  • `QuickbooksConnection` is a domain concept fused to persistence ON ITS OWN DECLARATION (Rails ActiveRecord — `ApplicationRecord`) — the domain entity IS the ActiveRecord row (active-record), and it carries domain behaviour on the persistence type. A schema/persistence change ripples straight into the domain. Keep the ORM/table mapping on a boundary data-model + a mapper, and the domain entity framework-free (map row↔domain through a repository). — app/models/quickbooks_connection.rb:3
  • `SalarySlip` is a domain concept fused to persistence ON ITS OWN DECLARATION (Rails ActiveRecord — `ApplicationRecord`) — the domain entity IS the ActiveRecord row (active-record), and it carries domain behaviour on the persistence type. A schema/persistence change ripples straight into the domain. Keep the ORM/table mapping on a boundary data-model + a mapper, and the domain entity framework-free (map row↔domain through a repository). — app/models/salary_slip.rb:3
  • `SignatureCallback` is a domain concept fused to persistence ON ITS OWN DECLARATION (Rails ActiveRecord — `ApplicationRecord`) — the domain entity IS the ActiveRecord row (active-record), and it carries domain behaviour on the persistence type. A schema/persistence change ripples straight into the domain. Keep the ORM/table mapping on a boundary data-model + a mapper, and the domain entity framework-free (map row↔domain through a repository). — app/models/signature_callback.rb:3
  • `SignatureConnection` is a domain concept fused to persistence ON ITS OWN DECLARATION (Rails ActiveRecord — `ApplicationRecord`) — the domain entity IS the ActiveRecord row (active-record), and it carries domain behaviour on the persistence type. A schema/persistence change ripples straight into the domain. Keep the ORM/table mapping on a boundary data-model + a mapper, and the domain entity framework-free (map row↔domain through a repository). — app/models/signature_connection.rb:3
  • `SignatureRequest` is a domain concept fused to persistence ON ITS OWN DECLARATION (Rails ActiveRecord — `ApplicationRecord`) — the domain entity IS the ActiveRecord row (active-record), and it carries domain behaviour on the persistence type. A schema/persistence change ripples straight into the domain. Keep the ORM/table mapping on a boundary data-model + a mapper, and the domain entity framework-free (map row↔domain through a repository). — app/models/signature_request.rb:3
  • `SignatureReviewInvitation` is a domain concept fused to persistence ON ITS OWN DECLARATION (Rails ActiveRecord — `ApplicationRecord`) — the domain entity IS the ActiveRecord row (active-record), and it carries domain behaviour on the persistence type. A schema/persistence change ripples straight into the domain. Keep the ORM/table mapping on a boundary data-model + a mapper, and the domain entity framework-free (map row↔domain through a repository). — app/models/signature_review_invitation.rb:3
  • `SubscriptionPurchaseEvent` is a domain concept fused to persistence ON ITS OWN DECLARATION (Rails ActiveRecord — `ApplicationRecord`) — the domain entity IS the ActiveRecord row (active-record), and it carries domain behaviour on the persistence type. A schema/persistence change ripples straight into the domain. Keep the ORM/table mapping on a boundary data-model + a mapper, and the domain entity framework-free (map row↔domain through a repository). — app/models/subscription_purchase_event.rb:3
  • `TaxDeclaration` is a domain concept fused to persistence ON ITS OWN DECLARATION (Rails ActiveRecord — `ApplicationRecord`) — the domain entity IS the ActiveRecord row (active-record), and it carries domain behaviour on the persistence type. A schema/persistence change ripples straight into the domain. Keep the ORM/table mapping on a boundary data-model + a mapper, and the domain entity framework-free (map row↔domain through a repository). — app/models/tax_declaration.rb:3
  • `User` is a domain concept fused to persistence ON ITS OWN DECLARATION (Rails ActiveRecord — `ApplicationRecord`) — the domain entity IS the ActiveRecord row (active-record), and it carries domain behaviour on the persistence type. A schema/persistence change ripples straight into the domain. Keep the ORM/table mapping on a boundary data-model + a mapper, and the domain entity framework-free (map row↔domain through a repository). — app/models/user.rb:3

What to do

  • Keep the ORM/table mapping on a boundary data-model + mapper; leave the domain entity framework-free (map row↔domain through a repository).
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 & stubs6.7 / 10Adequate✓ 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.

  • `onSelect` is wired to an arrow whose body is empty — the markup attaches a listener that does nothing. Implement the handler, or remove the attribute that wires it. (×2) — app/javascript/src/components/Clients/Header/index.tsx:58, app/javascript/src/components/Team/List/Header.tsx:45
  • `onChange` is wired to an arrow whose body is empty — the markup attaches a listener that does nothing. Implement the handler, or remove the attribute that wires it. (×5) — app/javascript/src/components/Expenses/Modals/ExpenseForm.tsx:194, app/javascript/src/components/Invoices/Invoice/MarkInvoicePaidModal.tsx:127, app/javascript/src/components/Invoices/Invoice/MarkInvoicePaidModal.tsx:149, …
  • Both arms of this conditional expression are the same, so no input can make the condition matter. Implement the distinction that was intended, or drop the condition. (×2) — app/javascript/src/components/Invoices/InvoiceSummary/index.tsx:61, app/javascript/src/components/TimesheetEntries/TimeEntryForm/MobileEntryForm.tsx:407
  • The `if` and its `else` contain the same statements, so no input can make the condition matter. Implement the distinction that was intended, or drop the branch and keep the body. (×2) — app/javascript/src/components/Reports/Filters/index.tsx:75, app/javascript/src/components/Reports/OutstandingInvoiceReport/Filters/index.tsx:42
  • `handleRemoveSingleFilter` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it. (×3) — app/javascript/src/components/Reports/context/RevenueByClientContext.tsx:21, app/javascript/src/components/Reports/context/TimeEntryReportContext.tsx:24, app/javascript/src/components/Reports/context/outstandingOverdueInvoiceContext.tsx:21
  • 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. — app/javascript/src/components/TimeTracking/EntryCard.tsx:60
  • A bare `eslint-disable` or `@ts-nocheck` with no rule list switches every lint rule or the whole type checker off for the rest of the file — hidden debt. Disable the specific rule on the specific line, with a justification, instead. (×6) — app/javascript/src/common/Mobile/HOC/withLayout/index.tsx:1, app/javascript/src/components/TimeTracking/Header.tsx:1, app/javascript/src/components/TimesheetEntries/Header/CalendarNavigator/index.tsx:1, …

What to do

  • Finish or delete the unfinished stubs (functions that throw "not implemented", or whose body is empty or a bare constant) — they are dead surface that looks live.
  • Clear the softer debt: re-enable or delete skipped tests, decide whether each empty function is a deliberate no-op (and say so in a comment), and replace blanket `eslint-disable` / `@ts-nocheck` with targeted, justified suppressions.
M1 · Documentation (README)10.0 / 10Exemplary✓ 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.

M2 · Architecture documentation7.0 / 10Strong✓ 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.

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 accuracy6.0 / 10Adequate✓ Tool-verified

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.

  • docs/README.md names React 18, but the manifest declares `react` 19.1.10. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/README.md:76
  • docs/intro.md names React 18, but the manifest declares `react` 19.1.10. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/intro.md:90

What to do

  • Reconcile the README with reality: docs/README.md names React 18, but the manifest declares `react` 19.1.10; docs/intro.md names React 18, but the manifest declares `react` 19.1.10.
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 · Observability10.0 / 10Exemplary○ Nothing flagged

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.

  • `app/javascript/src/hooks/useDashboard.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. — app/javascript/src/hooks/useDashboard.ts:50
  • `app/javascript/src/hooks/useDashboard.ts` reports through `console.*` at line 76 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — app/javascript/src/hooks/useDashboard.ts:76
  • `app/javascript/src/hooks/useDashboard.ts` reports through `console.*` at line 111 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — app/javascript/src/hooks/useDashboard.ts:111
  • `app/javascript/src/hooks/useDashboard.ts` reports through `console.*` at line 129 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — app/javascript/src/hooks/useDashboard.ts:129
  • `app/javascript/src/components/payments/Header.tsx` reports through `console.*` at line 52 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — app/javascript/src/components/payments/Header.tsx:52
  • `app/javascript/src/components/TimesheetEntries/FloatingTimer.tsx` reports through `console.*` at line 143 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — app/javascript/src/components/TimesheetEntries/FloatingTimer.tsx:143
  • `app/javascript/src/components/TimeTracking/WeeklyEntries.tsx` reports through `console.*` at line 144 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — app/javascript/src/components/TimeTracking/WeeklyEntries.tsx:144
  • `app/javascript/src/components/Team/List/Header.tsx` reports through `console.*` at line 33 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — app/javascript/src/components/Team/List/Header.tsx:33
  • `app/javascript/src/components/Settings/Preferences/index.tsx` reports through `console.*` at line 144 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — app/javascript/src/components/Settings/Preferences/index.tsx:144
  • `app/javascript/src/components/Settings/Preferences/index.tsx` reports through `console.*` at line 182 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — app/javascript/src/components/Settings/Preferences/index.tsx:182
  • `app/javascript/src/components/Profile/Personal/User/index.tsx` reports through `console.*` at line 62 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — app/javascript/src/components/Profile/Personal/User/index.tsx:62
  • `app/javascript/src/components/Profile/Personal/User/Edit/index.tsx` reports through `console.*` at line 125 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — app/javascript/src/components/Profile/Personal/User/Edit/index.tsx:125
  • `app/javascript/src/components/Profile/Personal/Employment/index.tsx` reports through `console.*` at line 52 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — app/javascript/src/components/Profile/Personal/Employment/index.tsx:52
  • `app/javascript/src/components/Profile/Personal/Employment/Edit/index.tsx` reports through `console.*` at line 122 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — app/javascript/src/components/Profile/Personal/Employment/Edit/index.tsx:122
  • `app/javascript/src/components/Profile/Organization/Details/Page.tsx` reports through `console.*` at line 119 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — app/javascript/src/components/Profile/Organization/Details/Page.tsx:119
  • `app/javascript/src/components/Invoices/usePaginatedInvoices.ts` reports through `console.*` at line 84 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — app/javascript/src/components/Invoices/usePaginatedInvoices.ts:84
  • `app/javascript/src/components/Invoices/MonthlyRevenueChart/index.tsx` reports through `console.*` at line 142 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — app/javascript/src/components/Invoices/MonthlyRevenueChart/index.tsx:142
  • `app/javascript/src/components/Invoices/List/RecentlyUpdated/InfiniteScrollRecentlyUpdated.tsx` reports through `console.*` at line 101 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — app/javascript/src/components/Invoices/List/RecentlyUpdated/InfiniteScrollRecentlyUpdated.tsx:101
  • `app/javascript/src/components/Invoices/Invoice/PaymentDetails.tsx` reports through `console.*` at line 35 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — app/javascript/src/components/Invoices/Invoice/PaymentDetails.tsx:35
  • `app/javascript/src/components/Invoices/Invoice/ViewHistory/index.tsx` reports through `console.*` at line 22 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — app/javascript/src/components/Invoices/Invoice/ViewHistory/index.tsx:22
  • `app/javascript/src/components/Clients/ClientsTable.tsx` 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. — app/javascript/src/components/Clients/ClientsTable.tsx:128

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.
P3 · Security & performance tooling4.0 / 10Weak✓ 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.

  • `package.json` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — package.json:4

What to do

  • Enable Dependabot/Renovate or a dependency-review gate.
  • Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback8.0 / 10Strong✓ Tool-verified

Readiness · Readiness — Whether releases are automated and safely reversible (probes, rolling updates, approval gates) — from manifests/pipeline files, not the live environment.

Method: Filesystem scan: deployment manifests/IaC (K8s YAML, Helm, Terraform) for rolling updates, probes, approval gates, migration hooks. Exhaustive, deterministic.

  • Deployment is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever reaches the release trigger goes to production unreviewed, so a mistaken merge or tag is live before anyone can stop it. — .github/workflows/docker-build.yml:70

What to do

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

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

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

What to do

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

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

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

P7 · Outbound HTTP resilience3.0 / 10Weak✓ Tool-verified

Readiness · Readiness — Whether outbound HTTP calls are wrapped in resilience (retry/timeout/circuit-breaker) so a failing dependency doesn't cascade.

Method: Source scan: outbound HTTP clients and what bounds them — resilience handlers (Polly, AddStandardResilienceHandler) on .NET; on Go, the JVM, Python, JavaScript/TypeScript, Ruby, PHP, Rust, Elixir, Swift, Dart and Erlang, a timeout, deadline, retry or breaker beside each call, or a process-wide client default (a framework-wide deadline such as Drupal core's, Laravel's or actix's awc counts). Exhaustive, deterministic.

  • `HTTParty` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. (×2) — app/services/hubspot_integration_service.rb:4, app/services/payment_providers/razorpay_client.rb:125
  • `HTTParty.post` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. — app/services/hubspot_integration_service.rb:34
  • `Net::HTTP.start` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. — app/services/mobile_otp/delivery.rb:41
  • `Faraday.new` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. (×2) — app/services/quick_books/client.rb:41, app/services/quick_books/oauth_client.rb:68

What to do

  • Set `open_timeout` and `read_timeout` explicitly on every client (Net::HTTP, Faraday `request: { timeout: }`, HTTParty `timeout:`), add Faraday's `:retry` middleware (faraday-retry) or `retriable`, and a breaker (`circuitbox`, `stoplight`) around dependencies that fail.
P8 · Schema migrations10.0 / 10Exemplary○ Nothing flagged

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

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

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

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

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

R1 · Type Safety9.8 / 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 Duplication3.2 / 10Weak✓ 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.

  • 293 duplicated blocks under app/javascript/src/components/ have copies in at least two of the sibling directories Agreements, Analytics, Authentication, ClientInvoices, Clients, ConsultantPayroll (+26 more sibling(s) not listed) — 142 of them are reported below, and 151 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 293 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 293 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 293 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. — app/javascript/src/components/TimeTracking/MobileView/MobileEntryForm.tsx:56
  • 42 duplicated blocks under app/javascript/src/components/Reports/ have copies in at least two of the sibling directories AccountsAgingReport, Container, Filters, List, OutstandingInvoiceReport, PaymentReport (+2 more sibling(s) not listed) — 29 of them are reported below, and 13 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 42 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 42 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 42 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. — app/javascript/src/components/Reports/PaymentReport/index.tsx:98
  • 16 duplicated blocks under app/javascript/src/components/Invoices/ have copies in at least two of the sibling directories AdminDashboard, ChartWithSummary, CompactInvoiceSummary, Invoice, InvoiceEditor, InvoicePreview (+6 more sibling(s) not listed) — 10 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 16 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 16 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 16 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. — app/javascript/src/components/Invoices/List/FilterSideBar/filterOptions.ts:1
  • 15 duplicated blocks under app/javascript/src/components/Profile/ have copies in at least two of the sibling directories BillingIdentity, EmployeeRecords, InvoiceAuthorization, Organization, Personal — 7 of them are reported below, and 8 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. — app/javascript/src/components/Profile/Organization/Edit/Page.tsx:50
  • 13 duplicated blocks under app/javascript/src/ have copies in at least two of the sibling directories StyledComponents, common, components, constants, context, services — 5 of them are reported below, and 8 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 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. — app/javascript/src/StyledComponents/TimeInput/index.tsx:22
  • 10 duplicated blocks under app/javascript/src/components/Profile/Personal/ have copies in at least two of the sibling directories Automation, Devices, Employment, User — 5 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 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. — app/javascript/src/components/Profile/Personal/Employment/Edit/MobileEmploymentEditor.tsx:14
  • 7 duplicated blocks under app/javascript/src/common/ have copies in at least two of the sibling directories AppErrorBoundary, CustomCreatableSelect, CustomDatePicker, CustomDateRangePicker, CustomDateRangeWIthInput, CustomReactSelect (+2 more sibling(s) not listed) — 6 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 7 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 7 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 7 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. — app/javascript/src/common/CustomDateRangePicker/index.tsx:24
  • 5 of the duplicated blocks reported below have copies in at least two of the sibling directories EmailVerification, ForgotPassword, ResetPassword, SignIn, SignUp under app/javascript/src/components/Authentication/. 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. — REDACTED:27
  • app/javascript/src/components/TimeTracking/MobileView/MobileEntryForm.tsx:56 · app/javascript/src/components/TimesheetEntries/TimeEntryForm/MobileEntryForm.tsx:51 — the two spans are one implementation copied and then locally edited — 1880 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. — app/javascript/src/components/TimeTracking/MobileView/MobileEntryForm.tsx:56
  • app/javascript/src/components/Hiring/ApplicationDecisions.tsx:92 · app/javascript/src/components/Hiring/ApplicationOffers.tsx:92 — the two spans are one implementation copied and then locally edited — 1587 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. — app/javascript/src/components/Hiring/ApplicationDecisions.tsx:92
  • app/javascript/src/components/Invoices/List/FilterSideBar/index.tsx:47 · app/javascript/src/components/Reports/RevenueByClientReport/Filters/index.tsx:65 — the two spans are one implementation copied and then locally edited — 1450 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. — app/javascript/src/components/Invoices/List/FilterSideBar/index.tsx:47
  • app/javascript/src/components/Profile/Personal/User/Edit/MobileProfileEditor.tsx:128 · app/javascript/src/components/Profile/Personal/User/Edit/ProfileEditor.tsx:133 — the two spans are one implementation copied and then locally edited — 1052 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. — app/javascript/src/components/Profile/Personal/User/Edit/MobileProfileEditor.tsx:128
  • app/javascript/src/components/Analytics/ClientInsightsPage.tsx:52 · app/javascript/src/components/Analytics/ExpenseTrendsPage.tsx:54 — the two spans are one implementation copied and then locally edited — 1169 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. — app/javascript/src/components/Analytics/ClientInsightsPage.tsx:52
  • app/javascript/src/common/CustomDateRangePicker/index.tsx:24 · app/javascript/src/common/CustomDateRangeWIthInput/index.tsx:44 — the two spans are one implementation copied and then locally edited — 1209 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. — app/javascript/src/common/CustomDateRangePicker/index.tsx:24
  • app/javascript/src/components/Clients/ClientsTable.tsx:102 · app/javascript/src/components/Projects/ProjectsTable.tsx:86 — the two spans are one implementation copied and then locally edited — 1229 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. — app/javascript/src/components/Clients/ClientsTable.tsx:102
  • app/javascript/src/components/TimeoffEntries/TimeoffForm/MobileTimeoffForm.tsx:62 · app/javascript/src/components/TimesheetEntries/TimeEntryForm/MobileEntryForm.tsx:167 — the two spans are one implementation copied and then locally edited — 839 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. — app/javascript/src/components/TimeoffEntries/TimeoffForm/MobileTimeoffForm.tsx:62
  • app/javascript/src/components/Projects/ProjectsTable.tsx:161 · app/javascript/src/components/Team/TeamTable.tsx:377 — the two spans are one implementation copied and then locally edited — 1145 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. — app/javascript/src/components/Projects/ProjectsTable.tsx:161
  • app/javascript/src/components/TimeTracking/WeeklyEntriesCard.tsx:31 · app/javascript/src/components/TimesheetEntries/WeekView/WeeklyEntriesCard.tsx:34 — the two spans are one implementation copied and then locally edited — 1105 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. — app/javascript/src/components/TimeTracking/WeeklyEntriesCard.tsx:31
  • app/javascript/src/components/Reports/Filters/FilterSideBar.tsx:28 · app/javascript/src/components/Reports/Filters/Sidebar.tsx:39 — the two spans are one implementation copied and then locally edited — 1187 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. — app/javascript/src/components/Reports/Filters/FilterSideBar.tsx:28
  • app/javascript/src/components/OrganizationSetup/FinancialDetailsForm/MobileFinancialDetailForm.tsx:25 · app/javascript/src/components/OrganizationSetup/FinancialDetailsForm/index.tsx:25 — the two spans are one implementation copied and then locally edited — 777 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. — app/javascript/src/components/OrganizationSetup/FinancialDetailsForm/MobileFinancialDetailForm.tsx:25
  • app/javascript/src/components/Profile/Personal/Employment/Edit/EmploymentEditor.tsx:1 · app/javascript/src/components/Profile/Personal/Employment/Edit/MobileEmploymentEditor.tsx:1 — these 2 files are line-for-line copies of one another — 172 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. — app/javascript/src/components/Profile/Personal/Employment/Edit/EmploymentEditor.tsx:1
  • app/javascript/src/components/Analytics/ExpenseTrendsPage.tsx:134 · app/javascript/src/components/Analytics/TeamAnalyticsPage.tsx:104 — the two spans are one implementation copied and then locally edited — 806 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. — app/javascript/src/components/Analytics/ExpenseTrendsPage.tsx:134
  • REDACTED:27 · REDACTED:26 — the two spans are one implementation copied and then locally edited — 761 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. — REDACTED:27
  • app/javascript/src/components/Clients/Modals/PaymentReminder/MobileView/index.tsx:17 · app/javascript/src/components/Clients/Modals/PaymentReminder/index.tsx:18 — the two spans are one implementation copied and then locally edited — 666 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. — app/javascript/src/components/Clients/Modals/PaymentReminder/MobileView/index.tsx:17
  • app/javascript/src/components/Projects/ProjectsTable.tsx:181 · app/javascript/src/components/payments/PaymentsTable.tsx:447 — the two spans are one implementation copied and then locally edited — 663 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. — app/javascript/src/components/Projects/ProjectsTable.tsx:181
  • app/javascript/src/components/Agreements/index.tsx:299 · app/javascript/src/components/DocumentSignatures/index.tsx:280 — the two spans are one implementation copied and then locally edited — 565 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. — app/javascript/src/components/Agreements/index.tsx:299
  • app/javascript/src/components/Hiring/ApplicationInterviews.tsx:103 · app/javascript/src/components/Hiring/InterviewPanel.tsx:62 — the two spans are one implementation copied and then locally edited — 574 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. — app/javascript/src/components/Hiring/ApplicationInterviews.tsx:103
  • app/javascript/src/components/Expenses/ExpensesTable.tsx:1161 · app/javascript/src/components/Expenses/ExpensesTable.tsx:1429 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — app/javascript/src/components/Expenses/ExpensesTable.tsx:1161
  • app/javascript/src/components/Reports/PaymentReport/index.tsx:98 · app/javascript/src/components/Reports/RevenueByClientReport/index.tsx:118 — the two spans are one implementation copied and then locally edited — 675 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. — app/javascript/src/components/Reports/PaymentReport/index.tsx:98
  • app/javascript/src/components/Hiring/InterviewFeedback.tsx:413 · app/javascript/src/components/Hiring/InterviewReviews.tsx:310 — the two spans are one implementation copied and then locally edited — 354 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. — app/javascript/src/components/Hiring/InterviewFeedback.tsx:413
  • app/javascript/src/components/Hiring/ReceiptDetail.tsx:40 · app/javascript/src/components/Hiring/Settings.tsx:35 — the two spans are one implementation copied and then locally edited — 433 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. — app/javascript/src/components/Hiring/ReceiptDetail.tsx:40
  • app/javascript/src/components/Clients/Contacts/AddContacts.tsx:1 · app/javascript/src/components/Clients/Contacts/EditContact.tsx:1 — these 2 files are line-for-line copies of one another — 84 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. — app/javascript/src/components/Clients/Contacts/AddContacts.tsx:1
  • app/javascript/src/components/Hiring/AssignmentLibrary.tsx:47 · app/javascript/src/components/Hiring/Roles.tsx:100 — the two spans are one implementation copied and then locally edited — 410 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. — app/javascript/src/components/Hiring/AssignmentLibrary.tsx:47
  • app/javascript/src/components/ui/dialog.tsx:8 · app/javascript/src/components/ui/sheet.tsx:7 — the two spans are one implementation copied and then locally edited — 438 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. — app/javascript/src/components/ui/dialog.tsx:8
  • app/javascript/src/components/Authentication/ForgotPassword/index.tsx:48 · app/javascript/src/components/Authentication/ResetPassword/index.tsx:51 — the two spans are one implementation copied and then locally edited — 352 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. — app/javascript/src/components/Authentication/ForgotPassword/index.tsx:48
  • app/javascript/src/components/Hiring/AssessmentPortal.tsx:29 · app/javascript/src/components/Hiring/Portal.tsx:19 — 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. — app/javascript/src/components/Hiring/AssessmentPortal.tsx:29
  • app/javascript/src/components/TaxDeclarations/index.tsx:265 · app/javascript/src/components/TaxDeclarations/index.tsx:417 — the two spans are one implementation copied and then locally edited — 339 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. — app/javascript/src/components/TaxDeclarations/index.tsx:265
  • app/javascript/src/common/CustomCreatableSelect/index.tsx:1 · app/javascript/src/common/CustomReactSelect/index.tsx:1 — these 2 files are line-for-line copies of one another — 76 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. — app/javascript/src/common/CustomCreatableSelect/index.tsx:1
  • app/javascript/src/components/Reports/PaymentReport/index.tsx:814 · app/javascript/src/components/Reports/RevenueByClientReport/index.tsx:748 — 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. — app/javascript/src/components/Reports/PaymentReport/index.tsx:814
  • app/javascript/src/components/ClientInvoices/Details/InvoiceTotalSummary.tsx:1 · app/javascript/src/components/InvoiceEmail/InvoiceTotalSummary.tsx:1 — these 2 files are line-for-line copies of one another — 73 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. — app/javascript/src/components/ClientInvoices/Details/InvoiceTotalSummary.tsx:1

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

  • app/javascript/src/components/DocumentSignatures/PdfPages.tsx:9 imports pdfjs-dist/build/pdf.worker.min.mjs?url, 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. — app/javascript/src/components/DocumentSignatures/PdfPages.tsx:9
  • app/javascript/src/components/DocumentSignatures/pdfResources.ts:3 reaches into another package with a relative path (../../../../../node_modules/pdfjs-dist/{cmaps/*,standard_fonts/*,wasm/*,LICENSE}) — import the package by name instead. — app/javascript/src/components/DocumentSignatures/pdfResources.ts:3

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.

  • InvoiceEditor has cyclomatic complexity 74 and cognitive complexity 55; 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. — app/javascript/src/components/Invoices/InvoiceEditor/index.tsx:62
  • Billing has cyclomatic complexity 62 and cognitive complexity 41; 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. — app/javascript/src/components/Profile/Organization/Billing/index.tsx:61
  • transformApiInvoice has cyclomatic complexity 55 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. — app/javascript/src/services/invoiceApi.ts:435
  • DeliveryPanel has cyclomatic complexity 54 and cognitive complexity 41; 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. — app/javascript/src/components/DocumentSignatures/DeliveryPanel.tsx:35
  • ApplicationAssignments has cyclomatic complexity 54 and cognitive complexity 41; 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. — app/javascript/src/components/Hiring/ApplicationAssignments.tsx:63
  • InvoicesPage has cyclomatic complexity 54 and cognitive complexity 40; 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. — app/javascript/src/components/Invoices/index.tsx:38
  • OrganizationPaymentSettingsPage has cyclomatic complexity 53 and cognitive complexity 48; 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. — app/javascript/src/components/Profile/Organization/Payment/Page.tsx:63
  • MobileProfileEditor has cyclomatic complexity 52 and cognitive complexity 51; 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. — app/javascript/src/components/Profile/Personal/User/Edit/MobileProfileEditor.tsx:30
  • InvoicePreview has cyclomatic complexity 52 and cognitive complexity 45; 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. — app/javascript/src/components/Invoices/InvoicePreview/index.tsx:90
  • BillingIdentityPanel has cyclomatic complexity 51 and cognitive complexity 41; 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. — app/javascript/src/components/Profile/BillingIdentity/index.tsx:61
  • (anonymous) has cyclomatic complexity 51 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. — app/javascript/src/components/Clients/ClientForm/ClientEditor.tsx:108
  • ExpensesTable has cyclomatic complexity 50 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. — app/javascript/src/components/Expenses/ExpensesTable.tsx:199
  • ProfileEditor has cyclomatic complexity 43 and cognitive complexity 42; 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. — app/javascript/src/components/Profile/Personal/User/Edit/ProfileEditor.tsx:32
  • CandidateMessages has cyclomatic complexity 41 and cognitive complexity 36; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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. — app/javascript/src/components/Hiring/CandidateMessages.tsx:49
  • PayrollWorkspace has cyclomatic complexity 40 and cognitive complexity 35; 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. — app/javascript/src/components/ConsultantPayroll/index.tsx:108
  • Onboarding has cyclomatic complexity 40 and cognitive complexity 33; 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. — app/javascript/src/components/Hiring/Onboarding.tsx:61
  • DeclarationWorkspace has cyclomatic complexity 39 and cognitive complexity 34; 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. — app/javascript/src/components/TaxDeclarations/index.tsx:66
  • InterviewBookings has cyclomatic complexity 38 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 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. — app/javascript/src/components/Hiring/InterviewBookings.tsx:41
  • OrgEditForm has cyclomatic complexity 37 and cognitive complexity 36; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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. — app/javascript/src/components/Profile/Organization/Edit/OrgEditForm.tsx:127
  • Editor has cyclomatic complexity 37 and cognitive complexity 34; 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. — app/javascript/src/components/DocumentSignatures/Editor.tsx:30
  • PaymentReport has cyclomatic complexity 37 and cognitive complexity 33; 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. — app/javascript/src/components/Reports/PaymentReport/index.tsx:149
  • ReceiptDetail has cyclomatic complexity 37 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. — app/javascript/src/components/Hiring/ReceiptDetail.tsx:21
  • Leg has cyclomatic complexity 35 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 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. — app/javascript/src/components/Payroll/MercuryPayments.tsx:540
  • ExpenseTrendsPage has cyclomatic complexity 34 and cognitive complexity 28; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — app/javascript/src/components/Analytics/ExpenseTrendsPage.tsx:54
  • (anonymous) has cyclomatic complexity 33 and cognitive complexity 31; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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. — app/javascript/src/components/OrganizationSetup/CompanyDetailsForm/index.tsx:219
  • ClientInsightsPage has cyclomatic complexity 33 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 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. — app/javascript/src/components/Analytics/ClientInsightsPage.tsx:52
  • Settings has cyclomatic complexity 33 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. — app/javascript/src/components/Hiring/Settings.tsx:25
  • (anonymous) has cyclomatic complexity 32 and cognitive complexity 35; 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:321
  • RazorpayConnection has cyclomatic complexity 32 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. — app/javascript/src/components/Profile/Organization/Payment/RazorpayConnection.tsx:104
  • OutstandingInvoicesWorkspaceView has cyclomatic complexity 31 and cognitive complexity 29; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — app/javascript/src/components/Reports/OutstandingInvoiceReport/WorkspaceView.tsx:191
  • TeamTable has cyclomatic complexity 31 and cognitive complexity 26; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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. — app/javascript/src/components/Team/TeamTable.tsx:102
  • App has cyclomatic complexity 31 and cognitive complexity 26; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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. — apps/mobile/App.tsx:239
  • PortalField has cyclomatic complexity 30 and cognitive complexity 28; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — app/javascript/src/components/Hiring/PortalField.tsx:19
  • Records has cyclomatic complexity 30 and cognitive complexity 28; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — app/javascript/src/components/Profile/EmployeeRecords/index.tsx:44
  • OrganizationHolidaysEditor has cyclomatic complexity 30 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 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. — app/javascript/src/components/Profile/Organization/Holidays/Editor.tsx:85
  • TimeEntryReport has cyclomatic complexity 29 and cognitive complexity 25; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — app/javascript/src/components/Reports/TimeEntryReport/index.tsx:258
  • Workspace has cyclomatic complexity 29 and cognitive complexity 22; 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. — app/javascript/src/components/Hiring/index.tsx:304
  • InvoiceAuthorizationPanel has cyclomatic complexity 29 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. — app/javascript/src/components/Profile/InvoiceAuthorization/index.tsx:20
  • InvoiceList has cyclomatic complexity 29 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. — app/javascript/src/components/Invoices/InvoiceList.tsx:78
  • ConsultantRow has cyclomatic complexity 28 and cognitive complexity 25; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — app/javascript/src/components/Payroll/RunPreparation.tsx:289
R3 · Large Files4.4 / 10Weak✓ 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.

  • app/javascript/src/components/Profile/Organization/Payment/Page.tsx has 2121 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — app/javascript/src/components/Profile/Organization/Payment/Page.tsx:1
  • app/javascript/src/components/Expenses/ExpensesTable.tsx has 1594 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — app/javascript/src/components/Expenses/ExpensesTable.tsx:1
  • apps/mobile/App.tsx has 1164 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — apps/mobile/App.tsx:1
  • app/javascript/src/components/Payroll/MercuryPayments.tsx has 1056 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — app/javascript/src/components/Payroll/MercuryPayments.tsx:1
  • app/javascript/src/components/Team/TeamTable.tsx has 1052 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — app/javascript/src/components/Team/TeamTable.tsx:1
  • app/javascript/src/components/Invoices/InvoiceEditor/index.tsx has 1039 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — app/javascript/src/components/Invoices/InvoiceEditor/index.tsx:1
  • app/javascript/src/components/ConsultantPayroll/index.tsx has 995 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — app/javascript/src/components/ConsultantPayroll/index.tsx:1
  • app/javascript/src/components/Profile/BillingIdentity/index.tsx has 988 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — app/javascript/src/components/Profile/BillingIdentity/index.tsx:1
  • app/javascript/src/components/Profile/Organization/Edit/OrgEditForm.tsx has 964 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — app/javascript/src/components/Profile/Organization/Edit/OrgEditForm.tsx:1
  • app/javascript/src/components/Profile/Organization/Billing/index.tsx has 962 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — app/javascript/src/components/Profile/Organization/Billing/index.tsx:1
  • app/javascript/src/components/Payroll/PtoPanel.tsx has 960 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — app/javascript/src/components/Payroll/PtoPanel.tsx:1
  • app/javascript/src/components/TimeTracking/index.tsx has 951 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — app/javascript/src/components/TimeTracking/index.tsx:1
  • app/javascript/src/components/Reports/TimeEntryReport/index.tsx has 918 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — app/javascript/src/components/Reports/TimeEntryReport/index.tsx:1
  • app/javascript/src/components/TimesheetEntries/FloatingTimer.tsx 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. — app/javascript/src/components/TimesheetEntries/FloatingTimer.tsx:1
  • app/javascript/src/components/Profile/Organization/Holidays/Editor.tsx has 839 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — app/javascript/src/components/Profile/Organization/Holidays/Editor.tsx:1
  • app/javascript/src/components/Reports/PaymentReport/index.tsx has 829 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — app/javascript/src/components/Reports/PaymentReport/index.tsx:1
  • REDACTED has 802 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
  • app/javascript/src/components/Invoices/index.tsx has 794 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — app/javascript/src/components/Invoices/index.tsx:1
  • app/javascript/src/components/Invoices/InvoicePreview/index.tsx has 788 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — app/javascript/src/components/Invoices/InvoicePreview/index.tsx:1
  • app/javascript/src/components/Profile/Personal/User/Edit/ProfileEditor.tsx has 778 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — app/javascript/src/components/Profile/Personal/User/Edit/ProfileEditor.tsx:1
  • app/javascript/src/components/Payroll/Review.tsx has 774 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — app/javascript/src/components/Payroll/Review.tsx:1
  • app/javascript/src/components/Reports/RevenueByClientReport/index.tsx has 774 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — app/javascript/src/components/Reports/RevenueByClientReport/index.tsx:1
  • app/javascript/src/components/TaxDeclarations/index.tsx has 772 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — app/javascript/src/components/TaxDeclarations/index.tsx:1
  • app/javascript/src/components/Reports/OutstandingInvoiceReport/WorkspaceView.tsx has 757 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — app/javascript/src/components/Reports/OutstandingInvoiceReport/WorkspaceView.tsx:1
  • app/javascript/src/components/Payroll/RunPreparation.tsx has 752 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — app/javascript/src/components/Payroll/RunPreparation.tsx:1
  • app/javascript/src/components/Profile/Organization/Payment/RazorpayConnection.tsx has 751 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — app/javascript/src/components/Profile/Organization/Payment/RazorpayConnection.tsx:1
  • app/javascript/src/components/Profile/EmployeeRecords/index.tsx has 743 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — app/javascript/src/components/Profile/EmployeeRecords/index.tsx:1
  • app/javascript/src/components/payments/PaymentsTable.tsx has 717 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — app/javascript/src/components/payments/PaymentsTable.tsx:1
  • REDACTED has 716 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
  • app/javascript/src/components/TimeTracking/EntryForm.tsx has 691 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — app/javascript/src/components/TimeTracking/EntryForm.tsx:1
  • app/javascript/src/components/TimesheetEntries/index.tsx has 682 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — app/javascript/src/components/TimesheetEntries/index.tsx:1
  • app/javascript/src/components/Reports/AccountsAgingReport/index.tsx has 667 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — app/javascript/src/components/Reports/AccountsAgingReport/index.tsx:1
  • app/javascript/src/components/Agreements/Editor.tsx has 665 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — app/javascript/src/components/Agreements/Editor.tsx:1
  • app/javascript/src/components/Profile/Personal/User/Edit/MobileProfileEditor.tsx has 647 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — app/javascript/src/components/Profile/Personal/User/Edit/MobileProfileEditor.tsx:1
  • app/javascript/src/components/Hiring/ApplicationAssignments.tsx has 644 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — app/javascript/src/components/Hiring/ApplicationAssignments.tsx:1
  • app/javascript/src/components/Hiring/ReceiptDetail.tsx has 629 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — app/javascript/src/components/Hiring/ReceiptDetail.tsx:1
  • app/javascript/src/components/Hiring/InterviewBookings.tsx has 619 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — app/javascript/src/components/Hiring/InterviewBookings.tsx:1
  • app/javascript/src/components/Navbar/Sidebar.tsx has 617 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — app/javascript/src/components/Navbar/Sidebar.tsx:1
  • app/javascript/src/components/Hiring/ApplicationInterviews.tsx has 614 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — app/javascript/src/components/Hiring/ApplicationInterviews.tsx:1
  • app/javascript/src/components/Invoices/InvoiceList.tsx has 612 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — app/javascript/src/components/Invoices/InvoiceList.tsx:1

What to do

  • Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
R4 · Test Coverage0.0 / 10Critical✓ 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. (×40) — app/javascript/src/i18n/locales/en.ts:1, app/javascript/src/i18n/locales/hi.ts:1, app/javascript/src/i18n/locales/ta.ts:1, …

What to do

  • Add tests that import the unreached modules (directly or through their public entry).
R6 · Tooling10.0 / 10Exemplary✓ Tool-verified

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

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

  • The package in `docs` declares the lint script `lint` (`eslint "src/**/*.{js,jsx,ts,tsx}" --fix`), but no step of this repository's CI runs it, by name, through another script, a Makefile target or a workspace runner, and no CI step runs the linter over the package itself. The rules it sets are enforced nowhere a pull request can fail. Run it in CI: a step that runs `npm run lint` in `docs` (or the workspace's task runner). — docs/package.json:22
R7 · Dead Code4.0 / 10Weak✓ 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 128 application, 14 tooling and 6 test entry point(s) detected in this repo. Gate removals on `pnpm run mobile:typecheck` — an undetected custom entry would make these reachable.
  • no import path from any entry point (128 application, 14 tooling, 6 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 (×15) — app/javascript/src/components/TimesheetEntries/index.tsx, app/javascript/src/components/Navbar/Sidebar.tsx, app/javascript/src/components/Reports/RevenueByClientReport/WorkspaceView.tsx, …
  • no import path from any entry point (128 application, 14 tooling, 6 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (app/javascript/src/components/TimesheetEntries/TimeEntryForm/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) — app/javascript/src/components/TimesheetEntries/TimeEntryForm/MobileEntryForm.tsx, app/javascript/src/components/TimesheetEntries/TimeEntryForm/DesktopTimeEntryForm.tsx
  • no import path from any entry point (128 application, 14 tooling, 6 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (app/javascript/src/components/Reports/TimeEntryReport/Page.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 — app/javascript/src/components/Reports/Filters/FilterSideBar.tsx
  • no import path from any entry point (128 application, 14 tooling, 6 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (app/javascript/entrypoints/hiring_assignment.ts) — 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 — app/javascript/src/components/Hiring/AssessmentPortal.tsx
  • no import path from any entry point (128 application, 14 tooling, 6 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (app/javascript/src/components/TimesheetEntries/WeekView/WeeklyEntries.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 — app/javascript/src/components/TimesheetEntries/WeekView/WeeklyEntriesCard.tsx
  • no import path from any entry point (128 application, 14 tooling, 6 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (scripts/ci/authentication_e2e.mjs) — 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 — scripts/ci/authentication_flow.mjs
  • no import path from any entry point (128 application, 14 tooling, 6 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (app/javascript/src/components/Invoices/AdminDashboard/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 — app/javascript/src/components/Invoices/MonthlyRevenueChart/index.tsx
  • no import path from any entry point (128 application, 14 tooling, 6 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (app/javascript/entrypoints/document_review.ts) — 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 — app/javascript/src/components/DocumentSignatures/Review.tsx
  • no import path from any entry point (128 application, 14 tooling, 6 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (app/javascript/src/components/Reports/Filters/DateRangeFilter.tsx, app/javascript/src/components/Reports/Filters/SidebarDateRangeFilter.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 — app/javascript/src/common/CustomDateRangeWIthInput/index.tsx
  • no import path from any entry point (128 application, 14 tooling, 6 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (app/javascript/entrypoints/hiring_form.ts) — 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 — app/javascript/src/components/Hiring/Portal.tsx
  • no import path from any entry point (128 application, 14 tooling, 6 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (app/javascript/src/components/Team/modals/Modals.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 — app/javascript/src/components/Team/modals/AddEditMember.tsx
  • no import path from any entry point (128 application, 14 tooling, 6 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (app/javascript/src/components/Invoices/AdminDashboard/index.tsx, app/javascript/src/components/Invoices/List/InvoiceListContent.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 — app/javascript/src/components/Invoices/List/RecentlyUpdated/InfiniteScrollRecentlyUpdated.tsx
  • no import path from any entry point (128 application, 14 tooling, 6 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (app/javascript/src/components/Invoices/List/Table/InvoiceListTable.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 — app/javascript/src/components/Invoices/List/Table/TableRow.tsx
  • no import path from any entry point (128 application, 14 tooling, 6 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (app/javascript/src/components/Invoices/List/Table/TableRow.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) — app/javascript/src/components/Invoices/List/MoreOptions.tsx, app/javascript/src/components/Invoices/common/SendInvoiceContainer/index.tsx
  • no import path from any entry point (128 application, 14 tooling, 6 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (app/javascript/src/components/Profile/Organization/Import/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 — app/javascript/src/components/Profile/Organization/Import/importModal.tsx
  • no import path from any entry point (128 application, 14 tooling, 6 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (app/javascript/src/components/TimesheetEntries/TimeEntryManager/index.tsx, app/javascript/src/components/TimesheetEntries/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 — app/javascript/src/components/TimesheetEntries/TimeEntryForm/index.tsx
  • no import path from any entry point (128 application, 14 tooling, 6 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (app/javascript/entrypoints/hiring_offer.ts) — 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 — app/javascript/src/components/Hiring/OfferPortal.tsx
  • no import path from any entry point (128 application, 14 tooling, 6 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (app/javascript/src/components/Hiring/AssessmentPortal.tsx, app/javascript/src/components/Hiring/Portal.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 — app/javascript/src/components/Hiring/PortalField.tsx
  • no import path from any entry point (128 application, 14 tooling, 6 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (app/javascript/src/components/Reports/Filters/Sidebar.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) — app/javascript/src/components/Reports/Filters/SidebarGroupByFilter.tsx, app/javascript/src/components/Reports/Filters/SidebarTeamMembersFilter.tsx
  • no import path from any entry point (128 application, 14 tooling, 6 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (app/javascript/src/components/Team/modals/AddEditMember.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 — app/javascript/src/components/Team/modals/TeamForm.tsx
  • no import path from any entry point (128 application, 14 tooling, 6 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (app/javascript/src/components/TimeoffEntries/TimeoffEntryManager/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 — app/javascript/src/components/TimeoffEntries/EntryCard/index.tsx
  • no import path from any entry point (128 application, 14 tooling, 6 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (app/javascript/src/components/Invoices/common/InvoiceDetails/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 — app/javascript/src/components/Invoices/common/InvoiceDetails/ClientSelection.tsx

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 Hygiene0.5 / 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. — eslint.config.mjs: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. (×14) — package.json:5, package.json:6, package.json:9, …
  • Declared in apps/mobile/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. — apps/mobile/package.json:22

What to do

  • Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
R9 · Circular Imports10.0 / 10Exemplary✓ Tool-verified

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

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

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

Other · Security — Read from this repository's Ruby 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. The server controls — HTTPS enforcement, HSTS, cookie flags, input validation — are NOT assessed for Ruby: this reading covers the code's own cryptography and the TLS connections it opens as a client, and a Rails, Rack or Sinatra application's transport, header and validation settings are not modelled. 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.

  • MD5/SHA1 is computed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ (`Digest::SHA256` or `OpenSSL::Digest.new("SHA256")`) for content integrity, or a KDF (bcrypt/Argon2/scrypt) for password storage. If it only derives a non-security identifier (a cache key, an avatar URL, an ETag), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as xxhash or murmurhash says it in code — since the algorithm alone cannot distinguish the two uses. Where a protocol this code does not own fixes the digest (a k-anonymity range query, a legacy signature format), the protocol decides; say so beside the call. (×5) — app/controllers/hiring_portal_controller.rb:139, app/services/hiring/assignments.rb:194, REDACTED:59, …

What to do

  • Review each MD5/SHA1 use by what it protects: replace it with SHA-256+ (or a KDF for passwords) where the digest is security-relevant, and switch it to a non-cryptographic hash (xxhash, murmurhash) where it only derives an identifier such as a cache key. This repository constructs a collision-broken hash (MD5/SHA1) at 5 sites, not one: `app/controllers/hiring_portal_controller.rb:139` (Digest::MD5.file), `app/services/hiring/assignments.rb:194` (Digest::MD5.file), `REDACTED:59` (Digest::MD5.base64digest), `REDACTED:65` (OpenSSL::Digest::SHA1.hexdigest), `app/services/signatures/upload.rb:31` (Digest::MD5.file). Each is a separate decision — fixing only the line this row cites leaves the others in place.
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.

X17 · Uncapped recursion over a caller-supplied document2.7 / 10Weak✓ Tool-verified

Other · Security — Whether a walk that recurses through a JSON/XML tree handed in by its caller bounds how deep it will go — an uncapped walk lets the document's nesting choose the stack depth, and the resulting StackOverflowException cannot be caught.

Method: Roslyn syntax + semantics: methods that take a JSON/XML document node and call themselves with a child of it, reachable from an externally-callable member of the same type that accepts a document, checked for any depth parameter, descent counter or threaded arithmetic anywhere in the walk. On a repository with no .NET source it reads TypeScript off the engine’s own token stream (test, vendored, generated and minified paths and `.d.ts` not) with the same rule: a function or method with a parameter typed as a document value — `unknown`, `any`, `object`, `Record<string, unknown|any>`, a JSON alias (`JsonValue`, `JSONObject`, …) or a DOM node global the file does not rebind — that calls itself (bare, or through `this` for a method, or hands itself to a call over the value as in `value.map(walk)`) with something it took out of that value and never through an ancestor accessor such as `closest()` or `parentElement`, that is exported or reached from an exported function (a public method of the same exported class) taking such a value, and that names no depth, level, nesting, recursion, remaining or budget anywhere and threads no `+`/`-` arithmetic through a self-call. Plain JavaScript is not read: with no annotation nothing tells a parsed document from a tree the code built itself. Deterministic, provable per finding. Advisory.

  • `immutable` is public and takes `value` — which it walks as a `Hash` — from its caller, and it calls itself at line 39 (`self.immutable`) with a piece of `value` (and at line 40) — and nowhere in `immutable` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends stack per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. A walk like this one raises `SystemStackError` past about 3,800 levels on the main thread and about 1,000 on a `Thread` — where Puma serves requests and Sidekiq runs jobs (MRI 3.3 and 4.0). `JSON.parse` stops at 100 levels by default, but the other parsers a caller may use do not: `YAML.safe_load` builds 1,400 levels from 2.8 KB, `Oj.load` 100,000, REXML 200,000, and `JSON.load` on json 2.7 (Ruby 3.3's default) or `JSON.parse(…, max_nesting: false)` 58,000. `SystemStackError` is not a `StandardError`: a bare `rescue` or `rescue => e` around the call does not stop it. Thread a depth argument through `immutable` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — app/services/payroll_calculation/values.rb:39
  • `line_digest` is public, takes a document from its caller (line 7) and hands it to `canonical`, which walks `value` as a `Hash` and calls itself at line 20 (`self.canonical`) with a piece of `value` (and at line 21) — and nowhere in `canonical` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends stack per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. A walk like this one raises `SystemStackError` past about 3,800 levels on the main thread and about 1,000 on a `Thread` — where Puma serves requests and Sidekiq runs jobs (MRI 3.3 and 4.0). `JSON.parse` stops at 100 levels by default, but the other parsers a caller may use do not: `YAML.safe_load` builds 1,400 levels from 2.8 KB, `Oj.load` 100,000, REXML 200,000, and `JSON.load` on json 2.7 (Ruby 3.3's default) or `JSON.parse(…, max_nesting: false)` 58,000. `SystemStackError` is not a `StandardError`: a bare `rescue` or `rescue => e` around the call does not stop it. Thread a depth argument through `canonical` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — app/services/payroll/india_handoff.rb:20

What to do

  • Each finding names the externally-callable member that accepts the document and the self-call that descends, and states that no depth parameter or counter exists anywhere in the walk. Confirm from the two, then thread a depth argument through the walk and reject documents past a fixed maximum, or rewrite it with an explicit stack.
X18 · Disposal-pattern correctness10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a type's disposal matches what it OWNS — releasing what it created, leaving alone what it was handed, and not declaring a finalizer for state that has nothing unmanaged to finalize.

Method: Roslyn syntax + semantics: every assignment to a disposable field is read to decide whether the type CREATED the value or was handed it, and the type's disposal is checked against that answer — an injected interface it disposes, a value it constructed and never releases, a finalizer on a type holding nothing unmanaged, and a disposable local whose every reference is a plain member read. A value handed to a container that disposes its contents (a parent control's `Controls` collection, a component `IContainer`) is released by that container and is not reported; generated code is out of population. On a repository with no .NET source the same ownership questions are read in JavaScript/TypeScript off the engine’s own token stream (test, vendored, generated and minified paths not): a class declaring `dispose()`, `[Symbol.dispose]()` or `[Symbol.asyncDispose]()` that disposes a field it was handed through a constructor parameter typed as a repository interface or resolved by a dependency-injection container; that assigns a field only ever from `new X(…)` of a disposable class and neither releases it anywhere in the class nor names it in its disposal member or a method that member calls, nor hands it to anything else; and a `const`/`let` local built from literals only whose every reference opens a statement operating on a non-release member of it. A class is disposable when every repository declaration of its name declares or inherits a disposal member, or when it is a documented library disposable (`vscode` EventEmitter, CancellationTokenSource and Disposable; three.js geometries, materials, textures, render targets, renderers, controls and composers). The finalizer arm has no JavaScript counterpart: a class cannot declare one. Dart is read for the owned-and-never-released arm: a Flutter `State` (or a class declaring `dispose()`/`close()`) whose library-private field is written only with direct creations of a framework controller, `FocusNode`, `StreamController` or periodic `Timer` (or a `.listen(…)` into a field declared `StreamSubscription`), which nothing in the class or its library releases (`dispose`/`close`/`cancel`) and which is never handed on except as a named argument. Ruby is read for the owned-and-never-released arm and the abandoned-local arm: a class declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose instance variable is written only with a blockless core descriptor creation (`File.open`/`new`, `Tempfile`, `Dir.open`, `IO.popen`, the `socket` and `openssl` socket classes) that no method of the class closes and that is never handed on (passed, returned, stored, exposed by `attr_reader`, delegated) — a class whose superclass or mixin lies outside the repository is not judged — and a blockless creation read through and dropped (`File.open(path).read`) or held in a local that is never closed, returned, passed or stored (a `&:read` block-pass, an `autoclose: false` borrow and a `fileno` hand-over are not abandonment). PHP is read for the same two arms: a class (not a trait, and not one using a trait) declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose `private` property (or a `final` class's `protected` one) is written only with a direct core `fopen`, `tmpfile`, `popen`, `proc_open`, `fsockopen`, `stream_socket_client`/`server` or `opendir` that nothing in the class closes (`fclose`, `pclose`, `closedir`, `unset`, a reset to `null`) and that is never handed on, and a handle held in a function's local, or read through as the argument of a reader, that is never closed, returned, passed, captured or stored; a `php://` stream, `curl_init`, `SplFileObject`, `PDO` and a function the repository declares under the core name are not read. Deterministic, provable per finding. Advisory.

X2 · Cancellation propagation4.5 / 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 2/26 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.
  • `request` 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 })`. — apps/mobile/src/api.ts:19
  • `getInvoices` awaits `axios.get(…)` 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: `axios.get(url, { signal })`. — app/javascript/src/services/invoiceApi.ts:193
  • `getInvoice` awaits `axios.get(…)` 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: `axios.get(url, { signal })`. — app/javascript/src/services/invoiceApi.ts:243
  • `createInvoice` awaits `axios.post(…)` 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: `axios.post(url, { signal })`. — app/javascript/src/services/invoiceApi.ts:249
  • `updateInvoice` awaits `axios.patch(…)` 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: `axios.patch(url, { signal })`. — app/javascript/src/services/invoiceApi.ts:261
  • `deleteInvoice` awaits `axios.delete(…)` 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: `axios.delete(url, { signal })`. — app/javascript/src/services/invoiceApi.ts:276
  • `sendInvoice` awaits `axios.post(…)` 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: `axios.post(url, { signal })`. — app/javascript/src/services/invoiceApi.ts:280
  • `sendReminder` awaits `axios.post(…)` 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: `axios.post(url, { signal })`. — app/javascript/src/services/invoiceApi.ts:299
  • `waiveInvoice` awaits `axios.patch(…)` 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: `axios.patch(url, { signal })`. — app/javascript/src/services/invoiceApi.ts:318
  • `downloadInvoice` awaits `axios.get(…)` 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: `axios.get(url, { signal })`. — app/javascript/src/services/invoiceApi.ts:324
  • `getClients` awaits `axios.get(…)` 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: `axios.get(url, { signal })`. — app/javascript/src/services/invoiceApi.ts:332
  • `getTaxConfigurations` awaits `axios.get(…)` 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: `axios.get(url, { signal })`. — app/javascript/src/services/invoiceApi.ts:354
  • `fetchCurrentUser` 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 })`. — app/javascript/src/hooks/useCurrentUser.ts:38
  • `fetchUserDetails` 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 })`. — app/javascript/src/components/AppWithUserData.tsx:148
  • `queryFn` awaits `axios.get(…)` 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: `axios.get(url, { signal })`. (×5) — app/javascript/src/components/TimesheetEntries/FloatingTimer.tsx:123, app/javascript/src/components/Reports/TimeEntryReport/index.tsx:334, app/javascript/src/components/Reports/RevenueByClientReport/index.tsx:185, …
  • `fetchBlobs` 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 })`. — app/javascript/src/components/Expenses/utils.jsx:157
  • `fetch` 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 })`. — app/javascript/src/components/DocumentSignatures/pdfResources.ts:11
  • `isSessionStillUnauthorized` 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:157
  • `googleAuth` 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:225
  • `preview` 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 })`. — app/javascript/entrypoints/profitability_planning.ts:24

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 unescaped4.3 / 10Weak✓ Tool-verified

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.

  • `Object.entries(THEMES).map(([theme,prefix])=>` ${prefix} [data-chart=${id}] { ${colorConfig.map(([key,itemConfig])=>{…` is text this program did not author, and it is written into the text of an element through `dangerouslySetInnerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — REDACTED:79

What to do

  • Each finding names the expression, the attribute it lands in and the line. Confirm the value's origin from the read this analyzer traced, then escape it at the sink or validate it against the shape the attribute accepts before interpolating.
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.3 / 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. (×10) — script/launch_matrix/verify.mjs:85, script/launch_matrix/verify.mjs:97, app/javascript/src/utils/runtimeRecovery.ts:92, …
  • `… rescue nil` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. — config/environments/production.rb:7
  • `rescue StandardError` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. (×8) — app/services/currency_conversion_service.rb:93, app/services/pdf_generation/invoice_service.rb:83, app/mcp/pro_access_checker.rb:15, …
  • `… rescue Encoding::UTF_8` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. — app/services/hiring/email_content.rb:142
  • `rescue` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. — app/models/concerns/pg_searchable.rb:116
  • `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, or keep only the failure you expect and rethrow the rest (`catch (e) { if (!(e instanceof SyntaxError)) throw e; … }`, or test `e.name`), because a JavaScript catch takes every exception, programming errors included. — app/javascript/src/i18n/index.ts:146

What to do

  • Swallowed exception (empty catch)
X30 · Support guard that admits what it rejects10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a guard written as a NEGATED `||` says what its author meant — `!(a || b || x != k)` is `!a && !b && x == k` by De Morgan, so a bail-out that mixes capabilities the code needs with a fault it refuses turns inside out: it fires only where the capabilities are ABSENT, and lets every value the fault term names walk straight into the body that cannot handle it.

Method: Roslyn syntax only, no semantic model: every logical-not whose operand is a parenthesised `||` chain of two or more disjuncts, flattened (a left-nested `a || b || c` read once would see `(a || b)` as one disjunct). A site enters the population on that shape alone. A finding additionally needs the disjuncts to DISAGREE in polarity: at least one bare boolean read — an identifier or member access, never an invocation, which is a predicate rather than a capability flag — and at least one `x != <constant>`, the only form that negates into an exact-value pin (`== null` negates into a looser requirement and is outside the fault set). Consistently-polarised disjunctions, all-fault or all-capability, are counted and never reported; a negated `&&` is outside the population entirely. No same-receiver gate: it was measured to cost a real defect and remove no false positive. Deterministic, provable per finding. Advisory.

X5 · Nullable reference types6.0 / 10Adequate✓ 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.

  • 1/2 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.2 `!` null assertions per 1k TypeScript source lines — 30 assertion(s) across the 185352 source line(s) of the 806 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: app/javascript/entrypoints/profitability_planning.ts (15), app/javascript/src/components/Hiring/ApplicationAssignments.tsx (3), app/javascript/src/components/Hiring/InterviewReviews.tsx (3). 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 Health47.0Weak — gated by R10, R7Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Architecture89.1StrongSolid.
Maturity76.7StrongSolid.
Readiness29.4Weak — gated by D13, R4, R8, P7Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security66.3Adequate — gated by D28, D29Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Domain Modelling50.4AdequateAcceptable, with room to improve.
Accessibility43.1Weak — gated by AC4Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Performance100.0ExemplaryStrongest area.
Unscored — 3 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.

  • D11 Test Reliability — 2 observation(s) recorded · This repository declares 2 of its own test(s) unreliable. The built-in reliability runner does not support this repository's ecosystem (.rb, .ts), so the suite was not re-run and no reliability score is given — these are the repository's own declarations, not our measurement.
  • X10 Duplicated predicate — 40 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
  • X7 Silent fallback defaults — 33 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 — C3 reached only 24% of this repository's production lines — typescript (175,477 lines), javascript (1,882 lines), go (1,381 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
  • C4 Data Retention — C4 reached only 24% of this repository's production lines — typescript (175,477 lines), javascript (1,882 lines), go (1,381 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
  • 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. Implement erasure, data export/portability and consent tracking over the subject's records.
Not included — 40 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 Ruby 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.
  • AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • AX7 Slice cohesion — not applicable — not a vertical-slice architecture
  • AX8 Test isolation — no test/production split to check
  • 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 — compose up failed (exit 17 — an image could not be built) — resolve : lstat .devcontainer: no such file or directory; likely cause (not identified): the image build failed, and its output does not match a cause we recognise; runtime evidence skipped 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.
  • C1 Data Protection — C1 reached only 24% of this repository's production lines — typescript (175,477 lines), javascript (1,882 lines), go (1,381 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
  • C2 Access Controls — C2 reached only 24% of this repository's production lines — typescript (175,477 lines), javascript (1,882 lines), go (1,381 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
  • D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
  • D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
  • D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ 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 — None of 0 binding record(s) states a rule in checkable form (a backticked element with a prohibition, or an `adr-rules` block), so conformance cannot be read from the code. Write the rule as an `adr-rules` block (`forbid:` a symbol, a package or a dependency) to make it checkable.
  • D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
  • D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
  • D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
  • D8 Code Coverage — Coverage not measured — polyglot repository, one half has no runner
  • 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'.
  • P9 Domain vs controller coverage — coverage data present for 1 file(s), but no domain-layer files were identified: no covered file's path contains any of the markers this check keys on (/domain/, /aggregates/, /valueobjects/, /domainmodel/, .domain/, /entities/), which are matched case-insensitively anywhere in the path. With no domain partition there is nothing to compare the web/controller layer against — if this repository keeps its business rules under a folder named none of those, that naming is what the check cannot see, not the domain logic.
  • PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `x.report(…)` entries in a `Benchmark.ips`/`bm`/`bmbm`/`benchmark`/`memory` block, `benchmark:` entries in a benchmark-driver YAML under a bench* directory, rspec-benchmark `perform_*` expectations where the gem is installed, or benchmark-ips, benchmark-memory, rspec-benchmark or benchmark-driver in a Gemfile or gemspec, 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.
  • R5 Dependency Freshness — uses a pnpm lockfile — dependency freshness not measured here; JS/npm CVEs are scored in D30 (Dependency Vulnerabilities), which answers every ecosystem
  • 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
  • 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 — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X27 Collection changed while being enumerated — X27 reached only 25% of this repository's production lines — typescript (175,477 lines), javascript (1,882 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
  • 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
  • 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 — 173 finding(s)
DM6 · Domain ↔ infrastructure boundary · Domain fused to persistence infrastructure · ×25
  • Domain fused to persistence infrastructure: AgentKey app/models/agent_key.rb:3 — `AgentKey` is a domain concept fused to persistence ON ITS OWN DECLARATION (Rails ActiveRecord — `ApplicationRecord`) — the domain entity IS the ActiveRecord row (active-record), and it carries domain behaviour on the persistence type. A schema/persistence change ripples straight into the domain. Keep the ORM/table mapping on a boundary data-model + a mapper, and the domain entity framework-free (map row↔domain through a repository).
  • Domain fused to persistence infrastructure: CliSession app/models/cli_session.rb:3 — `CliSession` is a domain concept fused to persistence ON ITS OWN DECLARATION (Rails ActiveRecord — `ApplicationRecord`) — the domain entity IS the ActiveRecord row (active-record), and it carries domain behaviour on the persistence type. A schema/persistence change ripples straight into the domain. Keep the ORM/table mapping on a boundary data-model + a mapper, and the domain entity framework-free (map row↔domain through a repository).
  • Domain fused to persistence infrastructure: Client app/models/client.rb:3 — `Client` is a domain concept fused to persistence ON ITS OWN DECLARATION (Rails ActiveRecord — `ApplicationRecord`) — the domain entity IS the ActiveRecord row (active-record), and it carries domain behaviour on the persistence type. A schema/persistence change ripples straight into the domain. Keep the ORM/table mapping on a boundary data-model + a mapper, and the domain entity framework-free (map row↔domain through a repository).
  • Domain fused to persistence infrastructure: Company app/models/company.rb:3 — `Company` is a domain concept fused to persistence ON ITS OWN DECLARATION (Rails ActiveRecord — `ApplicationRecord`) — the domain entity IS the ActiveRecord row (active-record), and it carries domain behaviour on the persistence type. A schema/persistence change ripples straight into the domain. Keep the ORM/table mapping on a boundary data-model + a mapper, and the domain entity framework-free (map row↔domain through a repository).
  • Domain fused to persistence infrastructure: Employment app/models/employment.rb:3 — `Employment` is a domain concept fused to persistence ON ITS OWN DECLARATION (Rails ActiveRecord — `ApplicationRecord`) — the domain entity IS the ActiveRecord row (active-record), and it carries domain behaviour on the persistence type. A schema/persistence change ripples straight into the domain. Keep the ORM/table mapping on a boundary data-model + a mapper, and the domain entity framework-free (map row↔domain through a repository).
  • Domain fused to persistence infrastructure: Expense app/models/expense.rb:3 — `Expense` is a domain concept fused to persistence ON ITS OWN DECLARATION (Rails ActiveRecord — `ApplicationRecord`) — the domain entity IS the ActiveRecord row (active-record), and it carries domain behaviour on the persistence type. A schema/persistence change ripples straight into the domain. Keep the ORM/table mapping on a boundary data-model + a mapper, and the domain entity framework-free (map row↔domain through a repository).
  • Domain fused to persistence infrastructure: HiringAssignment app/models/hiring_assignment.rb:3 — `HiringAssignment` is a domain concept fused to persistence ON ITS OWN DECLARATION (Rails ActiveRecord — `ApplicationRecord`) — the domain entity IS the ActiveRecord row (active-record), and it carries domain behaviour on the persistence type. A schema/persistence change ripples straight into the domain. Keep the ORM/table mapping on a boundary data-model + a mapper, and the domain entity framework-free (map row↔domain through a repository).
  • Domain fused to persistence infrastructure: HiringInterview app/models/hiring_interview.rb:3 — `HiringInterview` is a domain concept fused to persistence ON ITS OWN DECLARATION (Rails ActiveRecord — `ApplicationRecord`) — the domain entity IS the ActiveRecord row (active-record), and it carries domain behaviour on the persistence type. A schema/persistence change ripples straight into the domain. Keep the ORM/table mapping on a boundary data-model + a mapper, and the domain entity framework-free (map row↔domain through a repository).
  • Domain fused to persistence infrastructure: HiringInterviewBooking app/models/hiring_interview_booking.rb:3 — `HiringInterviewBooking` is a domain concept fused to persistence ON ITS OWN DECLARATION (Rails ActiveRecord — `ApplicationRecord`) — the domain entity IS the ActiveRecord row (active-record), and it carries domain behaviour on the persistence type. A schema/persistence change ripples straight into the domain. Keep the ORM/table mapping on a boundary data-model + a mapper, and the domain entity framework-free (map row↔domain through a repository).
  • Domain fused to persistence infrastructure: HiringMessage app/models/hiring_message.rb:3 — `HiringMessage` is a domain concept fused to persistence ON ITS OWN DECLARATION (Rails ActiveRecord — `ApplicationRecord`) — the domain entity IS the ActiveRecord row (active-record), and it carries domain behaviour on the persistence type. A schema/persistence change ripples straight into the domain. Keep the ORM/table mapping on a boundary data-model + a mapper, and the domain entity framework-free (map row↔domain through a repository).
  • Domain fused to persistence infrastructure: HiringOffer app/models/hiring_offer.rb:3 — `HiringOffer` is a domain concept fused to persistence ON ITS OWN DECLARATION (Rails ActiveRecord — `ApplicationRecord`) — the domain entity IS the ActiveRecord row (active-record), and it carries domain behaviour on the persistence type. A schema/persistence change ripples straight into the domain. Keep the ORM/table mapping on a boundary data-model + a mapper, and the domain entity framework-free (map row↔domain through a repository).
  • Domain fused to persistence infrastructure: Invoice app/models/invoice.rb:3 — `Invoice` is a domain concept fused to persistence ON ITS OWN DECLARATION (Rails ActiveRecord — `ApplicationRecord`) — the domain entity IS the ActiveRecord row (active-record), and it carries domain behaviour on the persistence type. A schema/persistence change ripples straight into the domain. Keep the ORM/table mapping on a boundary data-model + a mapper, and the domain entity framework-free (map row↔domain through a repository).
  • Domain fused to persistence infrastructure: InvoiceTax app/models/invoice_tax.rb:3 — `InvoiceTax` is a domain concept fused to persistence ON ITS OWN DECLARATION (Rails ActiveRecord — `ApplicationRecord`) — the domain entity IS the ActiveRecord row (active-record), and it carries domain behaviour on the persistence type. A schema/persistence change ripples straight into the domain. Keep the ORM/table mapping on a boundary data-model + a mapper, and the domain entity framework-free (map row↔domain through a repository).
  • Domain fused to persistence infrastructure: Metric app/models/metric.rb:3 — `Metric` is a domain concept fused to persistence ON ITS OWN DECLARATION (Rails ActiveRecord — `ApplicationRecord`) — the domain entity IS the ActiveRecord row (active-record), and it carries domain behaviour on the persistence type. A schema/persistence change ripples straight into the domain. Keep the ORM/table mapping on a boundary data-model + a mapper, and the domain entity framework-free (map row↔domain through a repository).
  • Domain fused to persistence infrastructure: NativeGoogleAuthRequest app/models/native_google_auth_request.rb:3 — `NativeGoogleAuthRequest` is a domain concept fused to persistence ON ITS OWN DECLARATION (Rails ActiveRecord — `ApplicationRecord`) — the domain entity IS the ActiveRecord row (active-record), and it carries domain behaviour on the persistence type. A schema/persistence change ripples straight into the domain. Keep the ORM/table mapping on a boundary data-model + a mapper, and the domain entity framework-free (map row↔domain through a repository).
  • Domain fused to persistence infrastructure: NotificationPreference app/models/notification_preference.rb:3 — `NotificationPreference` is a domain concept fused to persistence ON ITS OWN DECLARATION (Rails ActiveRecord — `ApplicationRecord`) — the domain entity IS the ActiveRecord row (active-record), and it carries domain behaviour on the persistence type. A schema/persistence change ripples straight into the domain. Keep the ORM/table mapping on a boundary data-model + a mapper, and the domain entity framework-free (map row↔domain through a repository).
  • Domain fused to persistence infrastructure: QuickbooksConnection app/models/quickbooks_connection.rb:3 — `QuickbooksConnection` is a domain concept fused to persistence ON ITS OWN DECLARATION (Rails ActiveRecord — `ApplicationRecord`) — the domain entity IS the ActiveRecord row (active-record), and it carries domain behaviour on the persistence type. A schema/persistence change ripples straight into the domain. Keep the ORM/table mapping on a boundary data-model + a mapper, and the domain entity framework-free (map row↔domain through a repository).
  • Domain fused to persistence infrastructure: SalarySlip app/models/salary_slip.rb:3 — `SalarySlip` is a domain concept fused to persistence ON ITS OWN DECLARATION (Rails ActiveRecord — `ApplicationRecord`) — the domain entity IS the ActiveRecord row (active-record), and it carries domain behaviour on the persistence type. A schema/persistence change ripples straight into the domain. Keep the ORM/table mapping on a boundary data-model + a mapper, and the domain entity framework-free (map row↔domain through a repository).
  • Domain fused to persistence infrastructure: SignatureCallback app/models/signature_callback.rb:3 — `SignatureCallback` is a domain concept fused to persistence ON ITS OWN DECLARATION (Rails ActiveRecord — `ApplicationRecord`) — the domain entity IS the ActiveRecord row (active-record), and it carries domain behaviour on the persistence type. A schema/persistence change ripples straight into the domain. Keep the ORM/table mapping on a boundary data-model + a mapper, and the domain entity framework-free (map row↔domain through a repository).
  • Domain fused to persistence infrastructure: SignatureConnection app/models/signature_connection.rb:3 — `SignatureConnection` is a domain concept fused to persistence ON ITS OWN DECLARATION (Rails ActiveRecord — `ApplicationRecord`) — the domain entity IS the ActiveRecord row (active-record), and it carries domain behaviour on the persistence type. A schema/persistence change ripples straight into the domain. Keep the ORM/table mapping on a boundary data-model + a mapper, and the domain entity framework-free (map row↔domain through a repository).
  • Domain fused to persistence infrastructure: SignatureRequest app/models/signature_request.rb:3 — `SignatureRequest` is a domain concept fused to persistence ON ITS OWN DECLARATION (Rails ActiveRecord — `ApplicationRecord`) — the domain entity IS the ActiveRecord row (active-record), and it carries domain behaviour on the persistence type. A schema/persistence change ripples straight into the domain. Keep the ORM/table mapping on a boundary data-model + a mapper, and the domain entity framework-free (map row↔domain through a repository).
  • Domain fused to persistence infrastructure: SignatureReviewInvitation app/models/signature_review_invitation.rb:3 — `SignatureReviewInvitation` is a domain concept fused to persistence ON ITS OWN DECLARATION (Rails ActiveRecord — `ApplicationRecord`) — the domain entity IS the ActiveRecord row (active-record), and it carries domain behaviour on the persistence type. A schema/persistence change ripples straight into the domain. Keep the ORM/table mapping on a boundary data-model + a mapper, and the domain entity framework-free (map row↔domain through a repository).
  • Domain fused to persistence infrastructure: SubscriptionPurchaseEvent app/models/subscription_purchase_event.rb:3 — `SubscriptionPurchaseEvent` is a domain concept fused to persistence ON ITS OWN DECLARATION (Rails ActiveRecord — `ApplicationRecord`) — the domain entity IS the ActiveRecord row (active-record), and it carries domain behaviour on the persistence type. A schema/persistence change ripples straight into the domain. Keep the ORM/table mapping on a boundary data-model + a mapper, and the domain entity framework-free (map row↔domain through a repository).
  • Domain fused to persistence infrastructure: TaxDeclaration app/models/tax_declaration.rb:3 — `TaxDeclaration` is a domain concept fused to persistence ON ITS OWN DECLARATION (Rails ActiveRecord — `ApplicationRecord`) — the domain entity IS the ActiveRecord row (active-record), and it carries domain behaviour on the persistence type. A schema/persistence change ripples straight into the domain. Keep the ORM/table mapping on a boundary data-model + a mapper, and the domain entity framework-free (map row↔domain through a repository).
  • Domain fused to persistence infrastructure: User app/models/user.rb:3 — `User` is a domain concept fused to persistence ON ITS OWN DECLARATION (Rails ActiveRecord — `ApplicationRecord`) — the domain entity IS the ActiveRecord row (active-record), and it carries domain behaviour on the persistence type. A schema/persistence change ripples straight into the domain. Keep the ORM/table mapping on a boundary data-model + a mapper, and the domain entity framework-free (map row↔domain through a repository).
AC1 · Text alternatives · <img> without a text alternative · ×21
  • <img> without a text alternative app/javascript/src/common/EmptyStates/index.tsx:36 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
  • <img> without a text alternative app/javascript/src/common/EmptyStates/index.tsx:38 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
  • <img> without a text alternative app/javascript/src/common/Error/index.tsx:25 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
  • <img> without a text alternative app/javascript/src/components/Authentication/EmailVerification/EmailVerificationSuccess.tsx:20 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
  • <img> without a text alternative app/javascript/src/components/Expenses/List/Container/Table/TableRow.tsx:33 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
  • <img> without a text alternative app/javascript/src/components/Expenses/utils.jsx:77 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
  • <img> without a text alternative app/javascript/src/components/Expenses/utils.jsx:87 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
  • <img> without a text alternative app/javascript/src/components/InvoiceEmail/index.tsx:69 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
  • <img> without a text alternative app/javascript/src/components/InvoiceEmail/index.tsx:122 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
  • <img> without a text alternative app/javascript/src/components/InvoiceEmail/index.tsx:125 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
  • <img> without a text alternative app/javascript/src/components/Invoices/common/MoreOptions.tsx:55 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
  • <img> without a text alternative app/javascript/src/components/Navbar/UserActions.tsx:151 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
  • <img> without a text alternative app/javascript/src/components/OrganizationSetup/SignUpSuccess.tsx:17 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
  • <img> without a text alternative app/javascript/src/components/Profile/Layout/Navigation/UserInformation.tsx:108 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
  • <img> without a text alternative app/javascript/src/components/Profile/Organization/Import/importModal.tsx:38 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
  • <img> without a text alternative app/javascript/src/components/Profile/Organization/Import/importModal.tsx:61 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
  • <img> without a text alternative app/javascript/src/components/Profile/Organization/Payment/MobileView.tsx:64 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
  • <img> without a text alternative app/javascript/src/components/Profile/Organization/Payment/MobileView.tsx:76 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
  • <img> without a text alternative app/javascript/src/components/Profile/Organization/Payment/MobileView.tsx:83 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
  • <img> without a text alternative app/javascript/src/components/Reports/Header/index.tsx:125 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
  • <img> without a text alternative app/javascript/src/components/Reports/List/reportCard.tsx:9 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
AC4 · Keyboard semantics · Click handler on a non-interactive <div> · ×20
  • Click handler on a non-interactive <div> app/javascript/src/common/CustomAdvanceInput/index.tsx:57 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
  • Click handler on a non-interactive <div> app/javascript/src/common/CustomAdvanceInput/index.tsx:62 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
  • Click handler on a non-interactive <div> app/javascript/src/common/CustomCreatableSelect/index.tsx:91 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
  • Click handler on a non-interactive <div> app/javascript/src/common/CustomDateRangeWIthInput/index.tsx:223 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
  • Click handler on a non-interactive <div> app/javascript/src/common/CustomDateRangeWIthInput/index.tsx:245 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
  • Click handler on a non-interactive <div> app/javascript/src/common/CustomReactSelect/index.tsx:93 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
  • Click handler on a non-interactive <div> app/javascript/src/common/CustomTextareaAutosize.tsx:40 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
  • Click handler on a non-interactive <div> app/javascript/src/common/SearchDataRow/index.tsx:37 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
  • Click handler on a non-interactive <div> app/javascript/src/common/SearchTimeEntries.tsx:73 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
  • Click handler on a non-interactive <div> app/javascript/src/components/ClientInvoices/InvoiceSearch/SearchedDataRow.tsx:18 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
  • Click handler on a non-interactive <div> app/javascript/src/components/Clients/Modals/PaymentReminder/Step.tsx:25 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
  • Click handler on a non-interactive <div> app/javascript/src/components/Expenses/List/Header.tsx:21 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
  • Click handler on a non-interactive <div> app/javascript/src/components/Expenses/Modals/ExpenseForm.tsx:182 — A click handler on a plain element with no role and no tabindex: even where another element's key handler can reach it, assistive tech can neither focus it nor announce what it is. Use a <button>, or add role + tabIndex={0}.
  • Click handler on a non-interactive <div> app/javascript/src/components/Invoices/Invoice/BackButton.tsx:26 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
  • Click handler on a non-interactive <div> app/javascript/src/components/Invoices/Invoice/MarkInvoicePaidModal.tsx:133 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
  • Click handler on a non-interactive <div> app/javascript/src/components/Invoices/Invoice/MarkInvoicePaidModal.tsx:226 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
  • Click handler on a non-interactive <div> app/javascript/src/components/Invoices/List/FilterSideBar/index.tsx:282 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
  • Click handler on a non-interactive <div> app/javascript/src/components/Invoices/List/FilterSideBar/index.tsx:359 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
  • Click handler on a non-interactive <div> app/javascript/src/components/Invoices/List/FilterSideBar/index.tsx:438 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
  • Click handler on a non-interactive <div> app/javascript/src/components/Invoices/List/InvoiceSearch/SearchedDataRow.tsx:18 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
AC4 · Keyboard semantics · Click handler on a non-interactive <li> · ×14
  • Click handler on a non-interactive <li> app/javascript/src/StyledComponents/SummaryDashboard.tsx:32 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
  • Click handler on a non-interactive <li> app/javascript/src/common/SearchTimeEntries.tsx:114 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
  • Click handler on a non-interactive <li> app/javascript/src/components/ClientInvoices/Details/Header.tsx:151 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
  • Click handler on a non-interactive <li> app/javascript/src/components/Clients/ClientMobileMoreOptions.tsx:18 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
  • Click handler on a non-interactive <li> app/javascript/src/components/Clients/ClientMobileMoreOptions.tsx:28 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
  • Click handler on a non-interactive <li> app/javascript/src/components/Clients/Details/Header.tsx:218 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
  • Click handler on a non-interactive <li> app/javascript/src/components/Clients/Details/Header.tsx:228 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
  • Click handler on a non-interactive <li> app/javascript/src/components/Clients/Details/Header.tsx:251 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
  • Click handler on a non-interactive <li> app/javascript/src/components/Clients/Details/Header.tsx:261 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
  • Click handler on a non-interactive <li> app/javascript/src/components/Invoices/Invoice/MarkInvoicePaidModal.tsx:249 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
  • Click handler on a non-interactive <li> app/javascript/src/components/Invoices/List/BulkActionsWrapper/index.tsx:51 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
  • Click handler on a non-interactive <li> app/javascript/src/components/Invoices/List/BulkActionsWrapper/index.tsx:61 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
  • Click handler on a non-interactive <li> app/javascript/src/components/Invoices/List/MoreOptions.tsx:121 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
  • Click handler on a non-interactive <li> app/javascript/src/components/Invoices/List/MoreOptions.tsx:147 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
AC2 · Forms & labels · <button> with no accessible text · ×12
  • <button> with no accessible text app/javascript/src/StyledComponents/Pagination/index.tsx:52 — A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one).
  • <button> with no accessible text app/javascript/src/StyledComponents/Pagination/index.tsx:87 — A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one).
  • <button> with no accessible text app/javascript/src/common/ChartBar/index.tsx:36 — A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one).
  • <button> with no accessible text app/javascript/src/common/CustomYearPicker/index.tsx:61 — A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one).
  • <button> with no accessible text app/javascript/src/common/CustomYearPicker/index.tsx:89 — A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one).
  • <button> with no accessible text app/javascript/src/common/Mobile/AddEditModalHeader/index.tsx:10 — A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one).
  • <button> with no accessible text app/javascript/src/common/Table/index.tsx:177 — A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one).
  • <button> with no accessible text app/javascript/src/common/Table/index.tsx:186 — A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one).
  • <button> with no accessible text app/javascript/src/components/Authentication/SignUp/PrivacyPolicyModal.tsx:19 — A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one).
  • <button> with no accessible text app/javascript/src/components/Authentication/SignUp/TermsOfServiceModal.tsx:15 — A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one).
  • <button> with no accessible text app/javascript/src/components/ClientInvoices/Header.tsx:111 — A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one).
  • <button> with no accessible text app/javascript/src/components/Clients/Contacts/AddContacts.tsx:54 — A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one).
AC2 · Forms & labels · <input> without a programmatic label · ×8
  • <input> without a programmatic label app/javascript/src/StyledComponents/TimeInput/index.tsx:69 — This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label htmlFor>, a wrapping <label>, or aria-label.
  • <input> without a programmatic label app/javascript/src/common/CustomDateRangeWIthInput/index.tsx:224 — This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label htmlFor>, a wrapping <label>, or aria-label.
  • <input> without a programmatic label app/javascript/src/common/CustomDateRangeWIthInput/index.tsx:246 — This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label htmlFor>, a wrapping <label>, or aria-label.
  • <input> without a programmatic label app/javascript/src/common/CustomInputText/index.tsx:63 — This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label htmlFor>, a wrapping <label>, or aria-label.
  • <input> without a programmatic label app/javascript/src/common/LocaleSelector/LocaleDropdown.tsx:103 — This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label htmlFor>, a wrapping <label>, or aria-label.
  • <input> without a programmatic label app/javascript/src/common/SearchTimeEntries.tsx:87 — This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label htmlFor>, a wrapping <label>, or aria-label.
  • <input> without a programmatic label app/javascript/src/components/ClientInvoices/Header.tsx:103 — This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label htmlFor>, a wrapping <label>, or aria-label.
  • <input> without a programmatic label app/javascript/src/components/ClientInvoices/Header.tsx:139 — This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label htmlFor>, a wrapping <label>, or aria-label.
AC3 · Page structure · <html> without a lang · ×7
  • <html> without a lang app/views/layouts/pdf.html.erb:2 — The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
  • <html> without a lang app/views/pdfs/analytics_export.html.erb:2 — The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
  • <html> without a lang app/views/pdfs/client_revenues.html.erb:2 — The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
  • <html> without a lang app/views/pdfs/invoices.html.erb:2 — The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
  • <html> without a lang app/views/pdfs/outstanding_overdue_invoices.html.erb:2 — The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
  • <html> without a lang app/views/pdfs/payments.html.erb:2 — The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
  • <html> without a lang public/test-mobile-nav.html:2 — The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
AC2 · Forms & labels · <label> that labels no control · ×6
  • <label> that labels no control app/javascript/src/common/SearchTimeEntries.tsx:77 — This <label> has no htmlFor and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label htmlFor="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
  • <label> that labels no control app/javascript/src/components/Analytics/components/AnalyticsFilters.tsx:64 — This <label> has no htmlFor and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label htmlFor="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
  • <label> that labels no control app/javascript/src/components/Analytics/components/AnalyticsFilters.tsx:80 — This <label> has no htmlFor and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label htmlFor="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
  • <label> that labels no control app/javascript/src/components/Analytics/components/AnalyticsFilters.tsx:96 — This <label> has no htmlFor and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label htmlFor="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
  • <label> that labels no control app/javascript/src/components/Clients/ClientForm/MobileClientEditor.tsx:262 — This <label> has no htmlFor and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label htmlFor="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
  • <label> that labels no control app/javascript/src/components/Clients/ClientForm/MobileClientEditor.tsx:348 — This <label> has no htmlFor and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label htmlFor="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
D28 · Secrets (history) · REDACTED · ×5
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D28 · Secrets (history) · High secret · ×5
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
AC2 · Forms & labels · <select> without a programmatic label · ×3
  • <select> without a programmatic label app/javascript/src/StyledComponents/Pagination/index.tsx:105 — This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <select> without a programmatic label app/javascript/src/common/CustomYearPicker/index.tsx:69 — This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <select> without a programmatic label app/javascript/src/components/Clients/ClientsTable.tsx:313 — This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
D14 · License Compliance · Banned license · ×3
  • Banned license: bundler-audit — `bundler-audit` 0.9.3 is published on rubygems.org under GPL-3.0-or-later, which this policy bans, and it is in the RUNTIME closure of this repository's Bundler manifests — so it is installed by everything that installs this repository, not just by its test harness. Replace it, or record an accepted exception.
  • Banned license: device_detector — `device_detector` 1.1.0 is published on rubygems.org under LGPL-3.0, which this policy bans, and it is in the RUNTIME closure of this repository's Bundler manifests — so it is installed by everything that installs this repository, not just by its test harness. Replace it, or record an accepted exception. ★ The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do — that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository's licence policy rather than replacing it: add `LGPL-3.0-only` / `LGPL-3.0-or-later` to the allow-list of the licence check your CI runs (`license-checker --onlyAllow`, the `allow-licenses` input of GitHub's dependency-review-action, `[licenses] allow` in cargo-deny's deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan's banned set is not read from that file, so the row stays until it is hidden.
  • Banned license: ruby_audit — `ruby_audit` 3.1.0 is published on rubygems.org under GPL-3.0-or-later, which this policy bans, and it is in the RUNTIME closure of this repository's Bundler manifests — so it is installed by everything that installs this repository, not just by its test harness. Replace it, or record an accepted exception.
D31 · IaC & Container Security · High IaC · ×3
  • REDACTED
  • REDACTED
  • REDACTED
AC3 · Page structure · Document without a <title> · ×2
  • Document without a <title> app/views/layouts/pdf.html.erb:2 — A page with no <title> gives no name in the tab, history or screen-reader page list. Add a descriptive <title> in <head>.
  • Document without a <title> app/views/payroll_india_mailer/report.html.erb:2 — A page with no <title> gives no name in the tab, history or screen-reader page list. Add a descriptive <title> in <head>.
AC4 · Keyboard semantics · Hover-only interaction on <div> · ×2
  • Hover-only interaction on <div> app/javascript/src/StyledComponents/Tooltip.tsx:43 — This <div> binds mouse-enter and mouse-leave and nothing else — no click, no key handler, no focus handler, and no tabIndex={0}, so it cannot even take focus. A keyboard user cannot hover, so whatever the pair reveals or highlights is reachable with a mouse only. Bind the same state to focus/blur as well, and add tabIndex={0}="0" so the element can receive that focus.
  • Hover-only interaction on <div> app/javascript/src/components/Invoices/List/BulkActionsWrapper/BulkActions.tsx:36 — This <div> binds mouse-enter and mouse-leave and nothing else — no click, no key handler, no focus handler, and no tabIndex={0}, so it cannot even take focus. A keyboard user cannot hover, so whatever the pair reveals or highlights is reachable with a mouse only. Bind the same state to focus/blur as well, and add tabIndex={0}="0" so the element can receive that focus.
AC4 · Keyboard semantics · Click handler on a non-interactive <tr> · ×2
  • Click handler on a non-interactive <tr> app/javascript/src/common/Table/index.tsx:152 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
  • Click handler on a non-interactive <tr> app/javascript/src/components/Expenses/List/Container/Table/TableRow.tsx:52 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
AC4 · Keyboard semantics · Click handler on a non-interactive <span> · ×2
  • Click handler on a non-interactive <span> app/javascript/src/components/Expenses/utils.jsx:152 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
  • Click handler on a non-interactive <span> app/javascript/src/components/Invoices/List/BulkActionsWrapper/AppliedFilters.tsx:77 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
D11 · Test Reliability · Test declared unreliable · ×2
  • Test declared unreliable: upload_avatar spec/system/profile/avatar_upload_spec.rb:35 — This test is disabled or skipped with a reason naming unreliability — the repository's own words: "Canvas-based image cropping is unreliable in headless Chrome CI". A test that is skipped for flakiness is neither passing nor protecting the code it covers; either stabilise it or delete it, but do not leave it disabled indefinitely. (Found by reading the repository's own test source — the suite itself was not re-run, since the reliability runner does not support this ecosystem.)
  • Test declared unreliable: upload_avatar spec/system/profile/avatar_upload_spec.rb:50 — This test is disabled or skipped with a reason naming unreliability — the repository's own words: "Canvas-based image cropping is unreliable in headless Chrome CI". A test that is skipped for flakiness is neither passing nor protecting the code it covers; either stabilise it or delete it, but do not leave it disabled indefinitely. (Found by reading the repository's own test source — the suite itself was not re-run, since the reliability runner does not support this ecosystem.)
D13 · REDACTED Scanning · Leaked secret · ×2
  • REDACTED
  • REDACTED
D34 · Knowledge Freshness · Orphaned knowledge · ×2
  • Orphaned knowledge app/javascript/src/components/TimesheetEntries/index.tsx:1 — No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
  • Orphaned knowledge app/javascript/src/components/Authentication/SignUp/PrivacyPolicyModal.tsx:1 — No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
D35 · Change Coupling · Boundary-crossing change coupling · ×2
  • Boundary-crossing change coupling: client.rb ↔ client_policy.rb app/models/client.rb:1 — `app/models/client.rb` (context models) and `app/policies/client_policy.rb` (context policies) sit in DIFFERENT parts of the tree yet change together 57% of the time (8 of the 14 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 8 shared commits counted here, the most recent 3 are `8f60165c` feat: add signed invoice options; `29d5adcc` fix: show EIN on invoices; `e3ea1186` Admin & owner should be able to upload client logo when adding a new … — run `git show` on any of them.
  • Boundary-crossing change coupling: company.rb ↔ company_policy.rb app/models/company.rb:1 — `app/models/company.rb` (context models) and `app/policies/company_policy.rb` (context policies) 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 `4e1f64a9` feat(billing): add stripe-managed subscriptions and plan gating; `422b3726` fix(specs): align system coverage with current billing UI; `40a17c86` Enable Google calendar integration (#1453) — run `git show` on any of them.
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
R8 · Dependency Hygiene · Unlisted import '@eslint/js' · ×1
  • Unlisted import '@eslint/js' eslint.config.mjs:2 — Imported but not declared in any reachable package.json — installs work only by hoisting accident.
Serious — 1364 finding(s)
D3 · God Classes · FunctionTooLong · ×225
  • FunctionTooLong: ExpensesTable.ExpensesTable app/javascript/src/components/Expenses/ExpensesTable.tsx:199 — FunctionTooLong — ExpensesTable runs 1222 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 1122 over it, 12.22× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: index.InvoiceEditor app/javascript/src/components/Invoices/InvoiceEditor/index.tsx:62 — FunctionTooLong — InvoiceEditor runs 864 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 764 over it, 8.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: TeamTable.TeamTable app/javascript/src/components/Team/TeamTable.tsx:102 — FunctionTooLong — TeamTable runs 847 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 747 over it, 8.47× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: index.BillingIdentityPanel app/javascript/src/components/Profile/BillingIdentity/index.tsx:61 — FunctionTooLong — BillingIdentityPanel runs 798 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 698 over it, 7.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: index.PayrollWorkspace app/javascript/src/components/ConsultantPayroll/index.tsx:108 — FunctionTooLong — PayrollWorkspace runs 790 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 690 over it, 7.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: OrgEditForm.OrgEditForm app/javascript/src/components/Profile/Organization/Edit/OrgEditForm.tsx:127 — FunctionTooLong — OrgEditForm runs 779 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 679 over it, 7.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: index.TimeTracking app/javascript/src/components/TimeTracking/index.tsx:45 — FunctionTooLong — TimeTracking runs 776 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 676 over it, 7.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: ProfileEditor.ProfileEditor app/javascript/src/components/Profile/Personal/User/Edit/ProfileEditor.tsx:32 — FunctionTooLong — ProfileEditor runs 690 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 590 over it, 6.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: Editor.OrganizationHolidaysEditor app/javascript/src/components/Profile/Organization/Holidays/Editor.tsx:85 — FunctionTooLong — OrganizationHolidaysEditor runs 688 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 588 over it, 6.88× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: FloatingTimer.FloatingTimer app/javascript/src/components/TimesheetEntries/FloatingTimer.tsx:89 — FunctionTooLong — FloatingTimer runs 671 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 571 over it, 6.71× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: index.InvoicesPage app/javascript/src/components/Invoices/index.tsx:38 — FunctionTooLong — InvoicesPage runs 641 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 541 over it, 6.41× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: index.DeclarationWorkspace app/javascript/src/components/TaxDeclarations/index.tsx:66 — FunctionTooLong — DeclarationWorkspace runs 636 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 536 over it, 6.36× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: index.InvoicePreview app/javascript/src/components/Invoices/InvoicePreview/index.tsx:90 — FunctionTooLong — InvoicePreview runs 623 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 523 over it, 6.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: RazorpayConnection.RazorpayConnection app/javascript/src/components/Profile/Organization/Payment/RazorpayConnection.tsx:104 — FunctionTooLong — RazorpayConnection runs 580 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 480 over it, 5.80× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: EntryForm.AddEntry app/javascript/src/components/TimeTracking/EntryForm.tsx:32 — FunctionTooLong — AddEntry runs 574 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 474 over it, 5.74× 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.TimesheetEntries app/javascript/src/components/TimesheetEntries/index.tsx:37 — FunctionTooLong — TimesheetEntries runs 556 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 456 over it, 5.56× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: WorkspaceView.OutstandingInvoicesWorkspaceView app/javascript/src/components/Reports/OutstandingInvoiceReport/WorkspaceView.tsx:191 — FunctionTooLong — OutstandingInvoicesWorkspaceView runs 546 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 446 over it, 5.46× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: ReceiptDetail.ReceiptDetail app/javascript/src/components/Hiring/ReceiptDetail.tsx:21 — FunctionTooLong — ReceiptDetail runs 543 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 443 over it, 5.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: PaymentsTable.PaymentsTable app/javascript/src/components/payments/PaymentsTable.tsx:106 — FunctionTooLong — PaymentsTable runs 521 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 421 over it, 5.21× 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: InterviewBookings.InterviewBookings app/javascript/src/components/Hiring/InterviewBookings.tsx:41 — FunctionTooLong — InterviewBookings runs 520 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 420 over it, 5.20× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: ApplicationAssignments.ApplicationAssignments app/javascript/src/components/Hiring/ApplicationAssignments.tsx:63 — FunctionTooLong — ApplicationAssignments runs 517 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 417 over it, 5.17× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: Editor.LoadedEditor app/javascript/src/components/Agreements/Editor.tsx:27 — FunctionTooLong — LoadedEditor runs 502 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 402 over it, 5.02× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: ApplicationInterviews.ApplicationInterviews app/javascript/src/components/Hiring/ApplicationInterviews.tsx:41 — FunctionTooLong — ApplicationInterviews runs 501 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 401 over it, 5.01× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: PtoPanel.PtoPanel app/javascript/src/components/Payroll/PtoPanel.tsx:279 — FunctionTooLong — PtoPanel runs 493 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 393 over it, 4.93× 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: DeliveryPanel.DeliveryPanel app/javascript/src/components/DocumentSignatures/DeliveryPanel.tsx:35 — FunctionTooLong — DeliveryPanel runs 492 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 392 over it, 4.92× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • + 200 more in this group — see findings.md.
D15 · Churn × Complexity Hotspots · Hotspot · ×49
  • Hotspot: app/javascript/src/components/Expenses/ExpensesTable.tsx app/javascript/src/components/Expenses/ExpensesTable.tsx:199 — app/javascript/src/components/Expenses/ExpensesTable.tsx changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 118 in ExpensesTable.ExpensesTable at line 199. 2 of those changes were fix/bug commits, and the other 3 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 13:34:34 +05:30' --until='2026-11-16 13:34:34 +05:30' --full-history --no-merges -- app/javascript/src/components/Expenses/ExpensesTable.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: app/javascript/src/components/Profile/EmployeeRecords/index.tsx app/javascript/src/components/Profile/EmployeeRecords/index.tsx:44 — app/javascript/src/components/Profile/EmployeeRecords/index.tsx changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 80 in index.Records at line 44. 1 of those changes was a fix/bug commit, and the other 6 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 13:34:34 +05:30' --until='2026-11-16 13:34:34 +05:30' --full-history --no-merges -- app/javascript/src/components/Profile/EmployeeRecords/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: app/javascript/src/components/DocumentSignatures/DeliveryPanel.tsx app/javascript/src/components/DocumentSignatures/DeliveryPanel.tsx:35 — app/javascript/src/components/DocumentSignatures/DeliveryPanel.tsx changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 101 in DeliveryPanel.DeliveryPanel at line 35. 4 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 13:34:34 +05:30' --until='2026-11-16 13:34:34 +05:30' --full-history --no-merges -- app/javascript/src/components/DocumentSignatures/DeliveryPanel.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: app/javascript/src/components/Dashboard/DashboardLayout.tsx app/javascript/src/components/Dashboard/DashboardLayout.tsx:44 — app/javascript/src/components/Dashboard/DashboardLayout.tsx changed 15 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 32 in DashboardLayout.DashboardLayout at line 44. 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 13:34:34 +05:30' --until='2026-11-16 13:34:34 +05:30' --full-history --no-merges -- app/javascript/src/components/Dashboard/DashboardLayout.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: app/javascript/src/components/Agreements/Editor.tsx app/javascript/src/components/Agreements/Editor.tsx:27 — app/javascript/src/components/Agreements/Editor.tsx changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 78 in Editor.LoadedEditor at line 27. 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 13:34:34 +05:30' --until='2026-11-16 13:34:34 +05:30' --full-history --no-merges -- app/javascript/src/components/Agreements/Editor.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: app/javascript/src/components/ConsultantPayroll/index.tsx app/javascript/src/components/ConsultantPayroll/index.tsx:108 — app/javascript/src/components/ConsultantPayroll/index.tsx changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 65 in index.PayrollWorkspace at line 108. 1 of those changes was a fix/bug commit, and the other 6 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 13:34:34 +05:30' --until='2026-11-16 13:34:34 +05:30' --full-history --no-merges -- app/javascript/src/components/ConsultantPayroll/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: app/javascript/src/components/SalarySlips/index.tsx app/javascript/src/components/SalarySlips/index.tsx:36 — app/javascript/src/components/SalarySlips/index.tsx changed 8 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 53 in index.SalarySlipArchive at line 36. 3 of those changes were fix/bug commits, and the other 5 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 13:34:34 +05:30' --until='2026-11-16 13:34:34 +05:30' --full-history --no-merges -- app/javascript/src/components/SalarySlips/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: app/javascript/src/components/Hiring/CandidateMessages.tsx app/javascript/src/components/Hiring/CandidateMessages.tsx:49 — app/javascript/src/components/Hiring/CandidateMessages.tsx changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 84 in CandidateMessages.CandidateMessages at line 49. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 13:34:34 +05:30' --until='2026-11-16 13:34:34 +05:30' --full-history --no-merges -- app/javascript/src/components/Hiring/CandidateMessages.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: app/javascript/src/components/Profile/Organization/Payment/Page.tsx app/javascript/src/components/Profile/Organization/Payment/Page.tsx:63 — app/javascript/src/components/Profile/Organization/Payment/Page.tsx changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 139 in Page.OrganizationPaymentSettingsPage at line 63. 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 13:34:34 +05:30' --until='2026-11-16 13:34:34 +05:30' --full-history --no-merges -- app/javascript/src/components/Profile/Organization/Payment/Page.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: app/javascript/src/components/TaxDeclarations/index.tsx app/javascript/src/components/TaxDeclarations/index.tsx:66 — app/javascript/src/components/TaxDeclarations/index.tsx changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 69 in index.DeclarationWorkspace at line 66. 1 of those changes was a fix/bug commit, and the other 5 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 13:34:34 +05:30' --until='2026-11-16 13:34:34 +05:30' --full-history --no-merges -- app/javascript/src/components/TaxDeclarations/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: app/javascript/src/components/Hiring/ApplicationInterviews.tsx app/javascript/src/components/Hiring/ApplicationInterviews.tsx:41 — app/javascript/src/components/Hiring/ApplicationInterviews.tsx changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 65 in ApplicationInterviews.ApplicationInterviews at line 41. 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 13:34:34 +05:30' --until='2026-11-16 13:34:34 +05:30' --full-history --no-merges -- app/javascript/src/components/Hiring/ApplicationInterviews.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: app/javascript/src/components/Payroll/Review.tsx app/javascript/src/components/Payroll/Review.tsx:405 — app/javascript/src/components/Payroll/Review.tsx changed 8 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 46 in Review.Review at line 405. 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 13:34:34 +05:30' --until='2026-11-16 13:34:34 +05:30' --full-history --no-merges -- app/javascript/src/components/Payroll/Review.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: app/javascript/src/components/DocumentSignatures/Editor.tsx app/javascript/src/components/DocumentSignatures/Editor.tsx:30 — app/javascript/src/components/DocumentSignatures/Editor.tsx changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 91 in Editor.Editor 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 13:34:34 +05:30' --until='2026-11-16 13:34:34 +05:30' --full-history --no-merges -- app/javascript/src/components/DocumentSignatures/Editor.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: app/javascript/src/components/Hiring/Settings.tsx app/javascript/src/components/Hiring/Settings.tsx:25 — app/javascript/src/components/Hiring/Settings.tsx changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 50 in Settings.Settings at line 25. 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 13:34:34 +05:30' --until='2026-11-16 13:34:34 +05:30' --full-history --no-merges -- app/javascript/src/components/Hiring/Settings.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: app/javascript/src/components/Invoices/InvoiceEditor/index.tsx app/javascript/src/components/Invoices/InvoiceEditor/index.tsx:62 — app/javascript/src/components/Invoices/InvoiceEditor/index.tsx changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 167 in index.InvoiceEditor at line 62. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 13:34:34 +05:30' --until='2026-11-16 13:34:34 +05:30' --full-history --no-merges -- app/javascript/src/components/Invoices/InvoiceEditor/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: app/javascript/src/components/Hiring/InterviewBookings.tsx app/javascript/src/components/Hiring/InterviewBookings.tsx:41 — app/javascript/src/components/Hiring/InterviewBookings.tsx changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 81 in InterviewBookings.InterviewBookings at line 41. 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 13:34:34 +05:30' --until='2026-11-16 13:34:34 +05:30' --full-history --no-merges -- app/javascript/src/components/Hiring/InterviewBookings.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: app/javascript/src/components/Hiring/Picker.tsx app/javascript/src/components/Hiring/Picker.tsx:34 — app/javascript/src/components/Hiring/Picker.tsx changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 45 in Picker.Picker at line 34. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 13:34:34 +05:30' --until='2026-11-16 13:34:34 +05:30' --full-history --no-merges -- app/javascript/src/components/Hiring/Picker.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: app/javascript/src/components/Invoices/InvoicePreview/index.tsx app/javascript/src/components/Invoices/InvoicePreview/index.tsx:90 — app/javascript/src/components/Invoices/InvoicePreview/index.tsx changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 105 in index.InvoicePreview at line 90. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 13:34:34 +05:30' --until='2026-11-16 13:34:34 +05:30' --full-history --no-merges -- app/javascript/src/components/Invoices/InvoicePreview/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: app/javascript/src/components/Payroll/RunPreparation.tsx app/javascript/src/components/Payroll/RunPreparation.tsx:289 — app/javascript/src/components/Payroll/RunPreparation.tsx changed 10 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 28 in RunPreparation.ConsultantRow at line 289. 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 13:34:34 +05:30' --until='2026-11-16 13:34:34 +05:30' --full-history --no-merges -- app/javascript/src/components/Payroll/RunPreparation.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: app/javascript/src/components/Hiring/ApplicationForms.tsx app/javascript/src/components/Hiring/ApplicationForms.tsx:32 — app/javascript/src/components/Hiring/ApplicationForms.tsx changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 69 in ApplicationForms.ApplicationForms 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 13:34:34 +05:30' --until='2026-11-16 13:34:34 +05:30' --full-history --no-merges -- app/javascript/src/components/Hiring/ApplicationForms.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: app/javascript/src/components/Profile/Organization/Payment/RazorpayConnection.tsx app/javascript/src/components/Profile/Organization/Payment/RazorpayConnection.tsx:104 — app/javascript/src/components/Profile/Organization/Payment/RazorpayConnection.tsx changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 78 in RazorpayConnection.RazorpayConnection at line 104. 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 13:34:34 +05:30' --until='2026-11-16 13:34:34 +05:30' --full-history --no-merges -- app/javascript/src/components/Profile/Organization/Payment/RazorpayConnection.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: app/javascript/src/components/Hiring/ApplicationAssignments.tsx app/javascript/src/components/Hiring/ApplicationAssignments.tsx:63 — app/javascript/src/components/Hiring/ApplicationAssignments.tsx changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 111 in ApplicationAssignments.ApplicationAssignments at line 63. 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 13:34:34 +05:30' --until='2026-11-16 13:34:34 +05:30' --full-history --no-merges -- app/javascript/src/components/Hiring/ApplicationAssignments.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: app/javascript/src/components/Hiring/ApplicationDetail.tsx app/javascript/src/components/Hiring/ApplicationDetail.tsx:20 — app/javascript/src/components/Hiring/ApplicationDetail.tsx changed 10 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 18 in ApplicationDetail.ApplicationDetail 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 13:34:34 +05:30' --until='2026-11-16 13:34:34 +05:30' --full-history --no-merges -- app/javascript/src/components/Hiring/ApplicationDetail.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: app/javascript/src/components/DocumentSignatures/PdfPages.tsx app/javascript/src/components/DocumentSignatures/PdfPages.tsx:36 — app/javascript/src/components/DocumentSignatures/PdfPages.tsx changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 45 in PdfPages.PdfPages at line 36. 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 13:34:34 +05:30' --until='2026-11-16 13:34:34 +05:30' --full-history --no-merges -- app/javascript/src/components/DocumentSignatures/PdfPages.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: app/javascript/src/components/Payroll/MercuryPayments.tsx app/javascript/src/components/Payroll/MercuryPayments.tsx:540 — app/javascript/src/components/Payroll/MercuryPayments.tsx changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 35 in MercuryPayments.Leg at line 540. 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 13:34:34 +05:30' --until='2026-11-16 13:34:34 +05:30' --full-history --no-merges -- app/javascript/src/components/Payroll/MercuryPayments.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.
  • + 24 more in this group — see findings.md.
D3 · God Classes · FileTooLong · ×44
  • FileTooLong: Payment/Page.tsx app/javascript/src/components/Profile/Organization/Payment/Page.tsx — FileTooLong — 1883 significant lines (blank, comment-only and punctuation-only lines excluded), about 97% of them inside a single declaration: OrganizationPaymentSettingsPage (63-2214). The bar is 500 significant lines; this is 1383 over it, 3.77× 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: Expenses/ExpensesTable.tsx app/javascript/src/components/Expenses/ExpensesTable.tsx — FileTooLong — 1395 significant lines (blank, comment-only and punctuation-only lines excluded), about 88% of them inside a single declaration: ExpensesTable (199-1682). The bar is 500 significant lines; this is 895 over it, 2.79× 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: mobile/App.tsx apps/mobile/App.tsx — 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: Team/TeamTable.tsx app/javascript/src/components/Team/TeamTable.tsx — FileTooLong — 932 significant lines (blank, comment-only and punctuation-only lines excluded), about 91% of them inside a single declaration: TeamTable (102-1115). The bar is 500 significant lines; this is 432 over it, 1.86× 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: InvoiceEditor/index.tsx app/javascript/src/components/Invoices/InvoiceEditor/index.tsx — FileTooLong — 922 significant lines (blank, comment-only and punctuation-only lines excluded), about 94% of them inside a single declaration: InvoiceEditor (62-1124). The bar is 500 significant lines; this is 422 over it, 1.84× 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: Payroll/MercuryPayments.tsx app/javascript/src/components/Payroll/MercuryPayments.tsx — FileTooLong — 922 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 422 over it, 1.84× 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: Edit/OrgEditForm.tsx app/javascript/src/components/Profile/Organization/Edit/OrgEditForm.tsx — FileTooLong — 897 significant lines (blank, comment-only and punctuation-only lines excluded), about 87% of them inside a single declaration: OrgEditForm (127-996). The bar is 500 significant lines; this is 397 over it, 1.79× 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: ConsultantPayroll/index.tsx app/javascript/src/components/ConsultantPayroll/index.tsx — FileTooLong — 892 significant lines (blank, comment-only and punctuation-only lines excluded), about 89% of them inside a single declaration: PayrollWorkspace (108-1005). The bar is 500 significant lines; this is 392 over it, 1.78× 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: BillingIdentity/index.tsx app/javascript/src/components/Profile/BillingIdentity/index.tsx — FileTooLong — 874 significant lines (blank, comment-only and punctuation-only lines excluded), about 91% of them inside a single declaration: BillingIdentityPanel (61-1000). The bar is 500 significant lines; this is 374 over it, 1.75× 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: Billing/index.tsx app/javascript/src/components/Profile/Organization/Billing/index.tsx — FileTooLong — 851 significant lines (blank, comment-only and punctuation-only lines excluded), about 94% of them inside a single declaration: Billing (61-1037). The bar is 500 significant lines; this is 351 over it, 1.70× 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: Payroll/PtoPanel.tsx app/javascript/src/components/Payroll/PtoPanel.tsx — FileTooLong — 849 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 349 over it, 1.70× 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: TimeTracking/index.tsx app/javascript/src/components/TimeTracking/index.tsx — FileTooLong — 817 significant lines (blank, comment-only and punctuation-only lines excluded), about 95% of them inside a single declaration: TimeTracking (45-1077). The bar is 500 significant lines; this is 317 over it, 1.63× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
  • FileTooLong: TimeEntryReport/index.tsx app/javascript/src/components/Reports/TimeEntryReport/index.tsx — FileTooLong — 797 significant lines (blank, comment-only and punctuation-only lines excluded), about 72% of them inside a single declaration: TimeEntryReport (258-988). The bar is 500 significant lines; this is 297 over it, 1.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: Holidays/Editor.tsx app/javascript/src/components/Profile/Organization/Holidays/Editor.tsx — FileTooLong — 752 significant lines (blank, comment-only and punctuation-only lines excluded), about 91% of them inside a single declaration: OrganizationHolidaysEditor (85-874). The bar is 500 significant lines; this is 252 over it, 1.50× 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: TimesheetEntries/FloatingTimer.tsx app/javascript/src/components/TimesheetEntries/FloatingTimer.tsx — FileTooLong — 749 significant lines (blank, comment-only and punctuation-only lines excluded), about 90% of them inside a single declaration: FloatingTimer (89-940). The bar is 500 significant lines; this is 249 over it, 1.50× 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: Edit/ProfileEditor.tsx app/javascript/src/components/Profile/Personal/User/Edit/ProfileEditor.tsx — FileTooLong — 721 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 221 over it, 1.44× 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: PaymentReport/index.tsx app/javascript/src/components/Reports/PaymentReport/index.tsx — FileTooLong — 721 significant lines (blank, comment-only and punctuation-only lines excluded), about 83% of them inside a single declaration: PaymentReport (149-887). The bar is 500 significant lines; this is 221 over it, 1.44× 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: InvoicePreview/index.tsx app/javascript/src/components/Invoices/InvoicePreview/index.tsx — FileTooLong — 707 significant lines (blank, comment-only and punctuation-only lines excluded), about 88% of them inside a single declaration: InvoicePreview (90-835). The bar is 500 significant lines; this is 207 over it, 1.41× 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: TaxDeclarations/index.tsx app/javascript/src/components/TaxDeclarations/index.tsx — FileTooLong — 699 significant lines (blank, comment-only and punctuation-only lines excluded), about 91% of them inside a single declaration: DeclarationWorkspace (66-783). The bar is 500 significant lines; this is 199 over it, 1.40× 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: OutstandingInvoiceReport/WorkspaceView.tsx app/javascript/src/components/Reports/OutstandingInvoiceReport/WorkspaceView.tsx — FileTooLong — 679 significant lines (blank, comment-only and punctuation-only lines excluded), about 80% of them inside a single declaration: OutstandingInvoicesWorkspaceView (191-841). The bar is 500 significant lines; this is 179 over it, 1.36× 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: RevenueByClientReport/index.tsx app/javascript/src/components/Reports/RevenueByClientReport/index.tsx — FileTooLong — 675 significant lines (blank, comment-only and punctuation-only lines excluded), about 80% of them inside a single declaration: RevenueByClientReport (150-821). The bar is 500 significant lines; this is 175 over it, 1.35× 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: Invoices/index.tsx app/javascript/src/components/Invoices/index.tsx — FileTooLong — 673 significant lines (blank, comment-only and punctuation-only lines excluded), about 95% of them inside a single declaration: InvoicesPage (38-881). The bar is 500 significant lines; this is 173 over it, 1.35× 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: Payroll/RunPreparation.tsx app/javascript/src/components/Payroll/RunPreparation.tsx — FileTooLong — 666 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 166 over it, 1.33× 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: Payroll/Review.tsx app/javascript/src/components/Payroll/Review.tsx — FileTooLong — 665 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 165 over it, 1.33× 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: Payment/RazorpayConnection.tsx app/javascript/src/components/Profile/Organization/Payment/RazorpayConnection.tsx — FileTooLong — 664 significant lines (blank, comment-only and punctuation-only lines excluded), about 87% of them inside a single declaration: RazorpayConnection (104-803). The bar is 500 significant lines; this is 164 over it, 1.33× 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.
  • + 19 more in this group — see findings.md.
R4 · Test Coverage · No test reaches this file · ×40
  • No test reaches this file app/javascript/src/i18n/locales/en.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 app/javascript/src/i18n/locales/hi.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 app/javascript/src/i18n/locales/ta.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 app/javascript/src/i18n/locales/fr.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 app/javascript/src/i18n/locales/ml.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 app/javascript/src/i18n/locales/de.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 app/javascript/src/components/Profile/Organization/Payment/Page.tsx:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file app/javascript/src/i18n/locales/es.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 app/javascript/src/i18n/locales/it.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 app/javascript/src/i18n/locales/pt-BR.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 app/javascript/src/i18n/locales/te.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 app/javascript/src/i18n/locales/id.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 app/javascript/src/i18n/locales/nl.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 app/javascript/src/i18n/locales/kn.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 app/javascript/src/i18n/locales/bn.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 app/javascript/src/i18n/locales/tr.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 app/javascript/src/i18n/locales/gu.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 app/javascript/src/i18n/locales/mr.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 app/javascript/src/i18n/locales/ur.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 app/javascript/src/i18n/locales/pa.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 app/javascript/src/i18n/locales/ja.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 app/javascript/src/i18n/locales/ko.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 app/javascript/src/i18n/locales/zh-CN.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 app/javascript/src/components/Expenses/ExpensesTable.tsx:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file apps/mobile/App.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.
  • + 15 more in this group — see findings.md.
X2 · Cancellation propagation · Async function without AbortSignal · ×24
  • Async function without AbortSignal: request apps/mobile/src/api.ts:19 — `request` 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: getInvoices app/javascript/src/services/invoiceApi.ts:193 — `getInvoices` awaits `axios.get(…)` 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: `axios.get(url, { signal })`.
  • Async function without AbortSignal: getInvoice app/javascript/src/services/invoiceApi.ts:243 — `getInvoice` awaits `axios.get(…)` 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: `axios.get(url, { signal })`.
  • Async function without AbortSignal: createInvoice app/javascript/src/services/invoiceApi.ts:249 — `createInvoice` awaits `axios.post(…)` 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: `axios.post(url, { signal })`.
  • Async function without AbortSignal: updateInvoice app/javascript/src/services/invoiceApi.ts:261 — `updateInvoice` awaits `axios.patch(…)` 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: `axios.patch(url, { signal })`.
  • Async function without AbortSignal: deleteInvoice app/javascript/src/services/invoiceApi.ts:276 — `deleteInvoice` awaits `axios.delete(…)` 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: `axios.delete(url, { signal })`.
  • Async function without AbortSignal: sendInvoice app/javascript/src/services/invoiceApi.ts:280 — `sendInvoice` awaits `axios.post(…)` 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: `axios.post(url, { signal })`.
  • Async function without AbortSignal: sendReminder app/javascript/src/services/invoiceApi.ts:299 — `sendReminder` awaits `axios.post(…)` 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: `axios.post(url, { signal })`.
  • Async function without AbortSignal: waiveInvoice app/javascript/src/services/invoiceApi.ts:318 — `waiveInvoice` awaits `axios.patch(…)` 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: `axios.patch(url, { signal })`.
  • Async function without AbortSignal: downloadInvoice app/javascript/src/services/invoiceApi.ts:324 — `downloadInvoice` awaits `axios.get(…)` 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: `axios.get(url, { signal })`.
  • Async function without AbortSignal: getClients app/javascript/src/services/invoiceApi.ts:332 — `getClients` awaits `axios.get(…)` 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: `axios.get(url, { signal })`.
  • Async function without AbortSignal: getTaxConfigurations app/javascript/src/services/invoiceApi.ts:354 — `getTaxConfigurations` awaits `axios.get(…)` 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: `axios.get(url, { signal })`.
  • Async function without AbortSignal: fetchCurrentUser app/javascript/src/hooks/useCurrentUser.ts:38 — `fetchCurrentUser` 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: fetchUserDetails app/javascript/src/components/AppWithUserData.tsx:148 — `fetchUserDetails` 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: queryFn app/javascript/src/components/TimesheetEntries/FloatingTimer.tsx:123 — `queryFn` awaits `axios.get(…)` 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: `axios.get(url, { signal })`.
  • Async function without AbortSignal: queryFn app/javascript/src/components/Reports/TimeEntryReport/index.tsx:334 — `queryFn` awaits `axios.get(…)` 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: `axios.get(url, { signal })`.
  • Async function without AbortSignal: queryFn app/javascript/src/components/Reports/RevenueByClientReport/index.tsx:185 — `queryFn` awaits `axios.get(…)` 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: `axios.get(url, { signal })`.
  • Async function without AbortSignal: queryFn app/javascript/src/components/Reports/PaymentReport/index.tsx:192 — `queryFn` awaits `axios.get(…)` 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: `axios.get(url, { signal })`.
  • Async function without AbortSignal: queryFn app/javascript/src/components/Reports/AccountsAgingReport/index.tsx:122 — `queryFn` awaits `axios.get(…)` 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: `axios.get(url, { signal })`.
  • Async function without AbortSignal: fetchBlobs app/javascript/src/components/Expenses/utils.jsx:157 — `fetchBlobs` 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: fetch app/javascript/src/components/DocumentSignatures/pdfResources.ts:11 — `fetch` 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: isSessionStillUnauthorized REDACTED:157 — `isSessionStillUnauthorized` 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: googleAuth REDACTED:225 — `googleAuth` 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: preview app/javascript/entrypoints/profitability_planning.ts:24 — `preview` 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 })`.
D15 · Churn × Complexity Hotspots · Repeated repair · ×22
  • Repeated repair: app/javascript/src/components/Payroll/paymentLabels.ts app/javascript/src/components/Payroll/paymentLabels.ts:206 — app/javascript/src/components/Payroll/paymentLabels.ts changed 10 times in last 90 days and 7 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 3 (its worst body is paymentLabels.errorMessage at line 206), 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: require explicit payroll bank declarations”; “fix: harden payroll reference identity and accounts handoff recovery”; “fix: recheck split approval under its lock and keep the first hold reason”; “fix: let a corrected spouse account replace only the failed transfer”. 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 13:34:34 +05:30' --until='2026-11-16 13:34:34 +05:30' --full-history --no-merges -- app/javascript/src/components/Payroll/paymentLabels.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.
  • Repeated repair: app/services/payroll/split_arrangements.rb app/services/payroll/split_arrangements.rb:10 — app/services/payroll/split_arrangements.rb changed 6 times in last 90 days and 6 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 8 (its worst body is SplitArrangements.request! at line 10), 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: recheck split approval under its lock and keep the first hold reason”; “fix: keep Mercury holds on empty reads and let pending corrections be withdrawn”; “fix: let a corrected spouse account replace only the failed transfer”; “fix: keep Mercury holds durable and scope split locks to completable groups”. 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 13:34:34 +05:30' --until='2026-11-16 13:34:34 +05:30' --full-history --no-merges -- app/services/payroll/split_arrangements.rb`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: app/services/payroll/pto_ledger.rb app/services/payroll/pto_ledger.rb:264 — app/services/payroll/pto_ledger.rb changed 7 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 11 (its worst body is PtoLedger.historical_values at line 264), 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: preserve explicit payroll reviews and concurrent retry integrity”; “fix: clarify duplicate PTO treatment validation”; “fix: resolve explicit PTO split remainders in exact minutes”; “fix: preserve exact PTO money and prepare 3.1.0 release”. 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 13:34:34 +05:30' --until='2026-11-16 13:34:34 +05:30' --full-history --no-merges -- app/services/payroll/pto_ledger.rb`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: app/models/payments_provider.rb app/models/payments_provider.rb:145 — app/models/payments_provider.rb changed 7 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 7 (its worst body is PaymentsProvider.paypal_ready_for_invoices? at line 145), 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: warn safely when provider credentials cannot decrypt”; “fix: preserve provider credentials across session key rotation”; “fix(payments): reconcile uncertain Razorpay link creation”; “fix(payments): preserve Razorpay OAuth recovery and maintain tokens”. 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 13:34:34 +05:30' --until='2026-11-16 13:34:34 +05:30' --full-history --no-merges -- app/models/payments_provider.rb`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: app/models/invoice.rb app/models/invoice.rb:397 — app/models/invoice.rb changed 7 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 12 (its worst body is Invoice.calculate_base_currency_amount at line 397), 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(invoices): share ledger subtotal rules with PDFs”; “fix(payments): enforce invoice holds and remaining balances”; “fix(payments): reconcile uncertain Razorpay link creation”; “fix(payments): retain captured payments through review and recovery”. 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 13:34:34 +05:30' --until='2026-11-16 13:34:34 +05:30' --full-history --no-merges -- app/models/invoice.rb`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: app/services/payment_providers/razorpay_oauth_connection.rb app/services/payment_providers/razorpay_oauth_connection.rb:668 — app/services/payment_providers/razorpay_oauth_connection.rb changed 5 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 12 (its worst body is RazorpayOauthConnection.store_credentials! at line 668), 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(payments): reconcile uncertain Razorpay link creation”; “fix(payments): retain captured payments through review and recovery”; “fix(payments): preserve Razorpay OAuth recovery and maintain tokens”; “fix(payments): clear Razorpay OAuth code-smell and CodeQL failures”. 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 13:34:34 +05:30' --until='2026-11-16 13:34:34 +05:30' --full-history --no-merges -- app/services/payment_providers/razorpay_oauth_connection.rb`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: app/services/subscriptions/stripe_sync_service.rb app/services/subscriptions/stripe_sync_service.rb:106 — app/services/subscriptions/stripe_sync_service.rb changed 5 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 10 (its worst body is StripeSyncService.purchase_event_to_deliver at line 106), 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(billing): close gaps in purchase announcement delivery”; “fix(billing): make purchase announcements durable”; “fix(billing): announce purchases after commit and limit polling”; “fix: prevent duplicate subscription checkout and recover activation”. 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 13:34:34 +05:30' --until='2026-11-16 13:34:34 +05:30' --full-history --no-merges -- app/services/subscriptions/stripe_sync_service.rb`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: app/controllers/api/v1/subscriptions_controller.rb app/controllers/api/v1/subscriptions_controller.rb:13 — app/controllers/api/v1/subscriptions_controller.rb changed 5 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 6 (its worst body is SubscriptionsController.checkout at line 13), 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(billing): explain subscriptions that are waiting for payment”; “fix(billing): announce purchases after commit and limit polling”; “fix(billing): keep purchase alerts when polling activates first”; “fix: prevent duplicate subscription checkout and recover activation”. 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 13:34:34 +05:30' --until='2026-11-16 13:34:34 +05:30' --full-history --no-merges -- app/controllers/api/v1/subscriptions_controller.rb`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: app/services/payroll/mercury_setup.rb app/services/payroll/mercury_setup.rb:120 — app/services/payroll/mercury_setup.rb changed 4 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 9 (its worst body is MercurySetup.recipient_mismatches at line 120), 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: recheck bank completeness before legacy submission”; “fix: document bank contracts and complete paid PTO fixture”; “fix: require explicit payroll bank declarations”; “fix: close Mercury payroll gaps found in review”. 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 13:34:34 +05:30' --until='2026-11-16 13:34:34 +05:30' --full-history --no-merges -- app/services/payroll/mercury_setup.rb`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: app/services/payroll/mercury_payment_review.rb app/services/payroll/mercury_payment_review.rb:153 — app/services/payroll/mercury_payment_review.rb changed 4 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 15 (its worst body is MercuryPaymentReview.actions at line 153), 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: require explicit payroll bank declarations”; “fix: keep Mercury holds durable and scope split locks to completable groups”; “fix: hold Mercury transfers when bank records stay ambiguous”; “fix: close Mercury payroll gaps found in review”. 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 13:34:34 +05:30' --until='2026-11-16 13:34:34 +05:30' --full-history --no-merges -- app/services/payroll/mercury_payment_review.rb`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: app/controllers/invoices/payments_controller.rb app/controllers/invoices/payments_controller.rb:9 — app/controllers/invoices/payments_controller.rb changed 5 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 14 (its worst body is PaymentsController.new at line 9), 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(payments): enforce invoice holds and remaining balances”; “fix(payments): reconcile uncertain Razorpay link creation”; “fix(payments): retain captured payments through review and recovery”. 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 13:34:34 +05:30' --until='2026-11-16 13:34:34 +05:30' --full-history --no-merges -- app/controllers/invoices/payments_controller.rb`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: app/services/payroll/india_handoff_review.rb app/services/payroll/india_handoff_review.rb:55 — app/services/payroll/india_handoff_review.rb changed 4 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 13 (its worst body is IndiaHandoffReview.handoff_detail at line 55), 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: require explicit payroll bank declarations”; “fix: address payroll review feedback and browser CI races”; “fix: bind India payroll confirmation to the reviewed bank details”. 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 13:34:34 +05:30' --until='2026-11-16 13:34:34 +05:30' --full-history --no-merges -- app/services/payroll/india_handoff_review.rb`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: scripts/ci/dependency_audit.mjs scripts/ci/dependency_audit.mjs:88 — scripts/ci/dependency_audit.mjs changed 4 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 12 (its worst body is dependency_audit.verifyAudit at line 88), 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: attest minimatch runtime helpers”; “fix(deps): align docs minimatch update and security verification”; “fix: keep Formik on a patched deepmerge and round report totals”. 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 13:34:34 +05:30' --until='2026-11-16 13:34:34 +05:30' --full-history --no-merges -- scripts/ci/dependency_audit.mjs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: app/services/handle_stripe_checkout_event_service.rb app/services/handle_stripe_checkout_event_service.rb:45 — app/services/handle_stripe_checkout_event_service.rb changed 4 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 10 (its worst body is HandleStripeCheckoutEventService.handle_event at line 45), 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(payments): classify checkout settlement failures as server errors”; “fix(payments): preserve settlements across notification failures”; “fix: prevent duplicate subscription checkout and recover activation”. 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 13:34:34 +05:30' --until='2026-11-16 13:34:34 +05:30' --full-history --no-merges -- app/services/handle_stripe_checkout_event_service.rb`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: REDACTED REDACTED:43 — REDACTED changed 4 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 8 (its worst body is RazorpayConnectionsController.callback at line 43), 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(payments): report Razorpay recovery outcomes accurately”; “fix(payments): reconcile uncertain Razorpay link creation”; “fix(payments): retain captured payments through review and recovery”. 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 13:34:34 +05:30' --until='2026-11-16 13:34:34 +05:30' --full-history --no-merges -- REDACTED`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: app/models/payroll_split_arrangement.rb app/models/payroll_split_arrangement.rb:72 — app/models/payroll_split_arrangement.rb changed 3 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 11 (its worst body is PayrollSplitArrangement.valid_details at line 72), 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: document bank contracts and complete paid PTO fixture”; “fix: require explicit payroll bank declarations”; “fix: keep Mercury holds on empty reads and let pending corrections be withdrawn”. 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 13:34:34 +05:30' --until='2026-11-16 13:34:34 +05:30' --full-history --no-merges -- app/models/payroll_split_arrangement.rb`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: app/services/invoice_payment/stripe_payment_succeeded.rb app/services/invoice_payment/stripe_payment_succeeded.rb:13 — app/services/invoice_payment/stripe_payment_succeeded.rb 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 StripePaymentSucceeded.process at line 13), 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(payments): preserve late Stripe captures for reconciliation”; “fix(payments): preserve settlements across notification failures”; “fix(payments): deduplicate Stripe payments across webhook events”. 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 13:34:34 +05:30' --until='2026-11-16 13:34:34 +05:30' --full-history --no-merges -- app/services/invoice_payment/stripe_payment_succeeded.rb`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: app/models/payroll_payment_instruction.rb app/models/payroll_payment_instruction.rb:157 — app/models/payroll_payment_instruction.rb 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 13 (its worst body is PayrollPaymentInstruction.same_company at line 157), 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: keep Mercury holds durable and scope split locks to completable groups”; “fix: hold Mercury transfers when bank records stay ambiguous”; “fix: close Mercury payroll gaps found in review”. 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 13:34:34 +05:30' --until='2026-11-16 13:34:34 +05:30' --full-history --no-merges -- app/models/payroll_payment_instruction.rb`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: app/models/subscription_purchase_event.rb app/models/subscription_purchase_event.rb:21 — app/models/subscription_purchase_event.rb 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 4 (its worst body is SubscriptionPurchaseEvent.enqueue_delivery at line 21), 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(billing): report exhausted purchase delivery retries”; “fix(billing): verify recovery schedule and explain retries”; “fix(billing): close gaps in purchase announcement delivery”. 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 13:34:34 +05:30' --until='2026-11-16 13:34:34 +05:30' --full-history --no-merges -- app/models/subscription_purchase_event.rb`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: app/services/subscriptions/purchase_event_delivery.rb app/services/subscriptions/purchase_event_delivery.rb:51 — app/services/subscriptions/purchase_event_delivery.rb 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 4 (its worst body is PurchaseEventDelivery.send_alert at line 51), 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(billing): report exhausted purchase delivery retries”; “fix(billing): verify recovery schedule and explain retries”; “fix(billing): close gaps in purchase announcement delivery”. 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 13:34:34 +05:30' --until='2026-11-16 13:34:34 +05:30' --full-history --no-merges -- app/services/subscriptions/purchase_event_delivery.rb`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: REDACTED REDACTED:91 — REDACTED 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 15 (its worst body is DocxImport.validate_upload! at line 91), 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: address agreement review cases and verify Linux PDF fonts”; “fix: resolve agreement CI complexity and dependency audit failures”; “fix: reject tracked Word changes before importing clauses”. 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 13:34:34 +05:30' --until='2026-11-16 13:34:34 +05:30' --full-history --no-merges -- REDACTED`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: config/initializers/encoding_sanitizer.rb config/initializers/encoding_sanitizer.rb:91 — config/initializers/encoding_sanitizer.rb 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 7 (its worst body is SanitizedInput.read at line 91), 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: address agreement review cases and verify Linux PDF fonts”; “fix: preserve Unicode request bodies and byte reads”; “fix: stop the remaining production 500s reported by Sentry (#2435)”. 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 13:34:34 +05:30' --until='2026-11-16 13:34:34 +05:30' --full-history --no-merges -- config/initializers/encoding_sanitizer.rb`: 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 · ClassTooLong · ×21
  • ClassTooLong: ExpensesTable app/javascript/src/components/Expenses/ExpensesTable.tsx:1 — ClassTooLong — 1222 significant lines (blank, comment-only and punctuation-only lines excluded), 4 methods. The bar is 400 significant lines; this is 822 over it, 3.06× 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: TeamTable app/javascript/src/components/Team/TeamTable.tsx:1 — ClassTooLong — 847 significant lines (blank, comment-only and punctuation-only lines excluded), 5 methods. The bar is 400 significant lines; this is 447 over it, 2.12× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: OrgEditForm app/javascript/src/components/Profile/Organization/Edit/OrgEditForm.tsx:1 — ClassTooLong — 779 significant lines (blank, comment-only and punctuation-only lines excluded), 3 methods. The bar is 400 significant lines; this is 379 over it, 1.95× 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: FloatingTimer app/javascript/src/components/TimesheetEntries/FloatingTimer.tsx:1 — ClassTooLong — 671 significant lines (blank, comment-only and punctuation-only lines excluded), 2 methods. The bar is 400 significant lines; this is 271 over it, 1.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: RazorpayConnection app/javascript/src/components/Profile/Organization/Payment/RazorpayConnection.tsx:1 — ClassTooLong — 580 significant lines (blank, comment-only and punctuation-only lines excluded), 3 methods. The bar is 400 significant lines; this is 180 over it, 1.45× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: MobileProfileEditor app/javascript/src/components/Profile/Personal/User/Edit/MobileProfileEditor.tsx:1 — ClassTooLong — 574 significant lines (blank, comment-only and punctuation-only lines excluded), 1 methods. The bar is 400 significant lines; this is 174 over it, 1.44× 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: ReceiptDetail app/javascript/src/components/Hiring/ReceiptDetail.tsx:1 — ClassTooLong — 543 significant lines (blank, comment-only and punctuation-only lines excluded), 1 methods. The bar is 400 significant lines; this is 143 over it, 1.36× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: PaymentsTable app/javascript/src/components/payments/PaymentsTable.tsx:1 — ClassTooLong — 521 significant lines (blank, comment-only and punctuation-only lines excluded), 5 methods. The bar is 400 significant lines; this is 121 over it, 1.30× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: InterviewBookings app/javascript/src/components/Hiring/InterviewBookings.tsx:1 — ClassTooLong — 520 significant lines (blank, comment-only and punctuation-only lines excluded), 1 methods. The bar is 400 significant lines; this is 120 over it, 1.30× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: ApplicationAssignments app/javascript/src/components/Hiring/ApplicationAssignments.tsx:1 — ClassTooLong — 517 significant lines (blank, comment-only and punctuation-only lines excluded), 2 methods. The bar is 400 significant lines; this is 117 over it, 1.29× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: ApplicationInterviews app/javascript/src/components/Hiring/ApplicationInterviews.tsx:1 — ClassTooLong — 501 significant lines (blank, comment-only and punctuation-only lines excluded), 1 methods. The bar is 400 significant lines; this is 101 over it, 1.25× 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: PtoPanel app/javascript/src/components/Payroll/PtoPanel.tsx:1 — ClassTooLong — 493 significant lines (blank, comment-only and punctuation-only lines excluded), 5 methods. The bar is 400 significant lines; this is 93 over it, 1.23× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: App apps/mobile/App.tsx:1 — ClassTooLong — 492 significant lines (blank, comment-only and punctuation-only lines excluded), 18 methods. The bar is 400 significant lines; this is 92 over it, 1.23× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: DeliveryPanel app/javascript/src/components/DocumentSignatures/DeliveryPanel.tsx:1 — ClassTooLong — 492 significant lines (blank, comment-only and punctuation-only lines excluded), 2 methods. The bar is 400 significant lines; this is 92 over it, 1.23× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: InvoiceList app/javascript/src/components/Invoices/InvoiceList.tsx:1 — ClassTooLong — 478 significant lines (blank, comment-only and punctuation-only lines excluded), 1 methods. The bar is 400 significant lines; this is 78 over it, 1.20× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: CandidateMessages app/javascript/src/components/Hiring/CandidateMessages.tsx:1 — ClassTooLong — 467 significant lines (blank, comment-only and punctuation-only lines excluded), 2 methods. The bar is 400 significant lines; this is 67 over it, 1.17× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: PaymentEntryForm app/javascript/src/components/payments/Modals/PaymentEntryForm.tsx:1 — ClassTooLong — 466 significant lines (blank, comment-only and punctuation-only lines excluded), 1 methods. The bar is 400 significant lines; this is 66 over it, 1.17× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: Editor app/javascript/src/components/DocumentSignatures/Editor.tsx:1 — ClassTooLong — 461 significant lines (blank, comment-only and punctuation-only lines excluded), 1 methods. The bar is 400 significant lines; this is 61 over it, 1.15× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: Sidebar app/javascript/src/components/Navbar/Sidebar.tsx:1 — ClassTooLong — 453 significant lines (blank, comment-only and punctuation-only lines excluded), 1 methods. The bar is 400 significant lines; this is 53 over it, 1.13× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: ClientsTable app/javascript/src/components/Clients/ClientsTable.tsx:1 — ClassTooLong — 428 significant lines (blank, comment-only and punctuation-only lines excluded), 2 methods. The bar is 400 significant lines; this is 28 over it, 1.07× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: ApplicationDecisions app/javascript/src/components/Hiring/ApplicationDecisions.tsx:1 — ClassTooLong — 408 significant lines (blank, comment-only and punctuation-only lines excluded), 1 methods. The bar is 400 significant lines; this is 8 over it, 1.02× 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.
D31 · IaC & Container Security · Medium IaC · ×21
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D3 · God Classes · TooManyMethods · ×18
  • TooManyMethods: RazorpayOauthConnection app/services/payment_providers/razorpay_oauth_connection.rb:6 — TooManyMethods — 76 methods. The bar is 30 methods; this is 46 over it, 2.53× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: CollectionsController app/controllers/api/v1/mobile/collections_controller.rb:3 — TooManyMethods — 55 methods. The bar is 30 methods; this is 25 over it, 1.83× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: User app/models/user.rb:3 — TooManyMethods — 48 methods. The bar is 30 methods; this is 18 over it, 1.60× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: Invoice app/models/invoice.rb:3 — TooManyMethods — 47 methods. The bar is 30 methods; this is 17 over it, 1.57× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: AnalyticsController app/controllers/analytics_controller.rb:3 — TooManyMethods — 46 methods. The bar is 30 methods; this is 16 over it, 1.53× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: MercuryReconciliation app/services/payroll/mercury_reconciliation.rb:4 — TooManyMethods — 45 methods. The bar is 30 methods; this is 15 over it, 1.50× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: HarvestTimeEntriesImporter app/services/imports/harvest_time_entries_importer.rb:8 — TooManyMethods — 40 methods. The bar is 30 methods; this is 10 over it, 1.33× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: PtoLedger app/services/payroll/pto_ledger.rb:4 — TooManyMethods — 40 methods. The bar is 30 methods; this is 10 over it, 1.33× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: DocxImport REDACTED:6 — TooManyMethods — 37 methods. The bar is 30 methods; this is 7 over it, 1.23× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: Assignments app/services/hiring/assignments.rb:4 — TooManyMethods — 37 methods. The bar is 30 methods; this is 7 over it, 1.23× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: MercuryPayment app/services/payroll/mercury_payment.rb:4 — TooManyMethods — 37 methods. The bar is 30 methods; this is 7 over it, 1.23× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: Company app/models/company.rb:3 — TooManyMethods — 36 methods. The bar is 30 methods; this is 6 over it, 1.20× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: CompensationProfitability app/services/reports/compensation_profitability.rb:4 — TooManyMethods — 36 methods. The bar is 30 methods; this is 6 over it, 1.20× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: PaymentsProvider app/models/payments_provider.rb:3 — TooManyMethods — 33 methods. The bar is 30 methods; this is 3 over it, 1.10× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: BillingIdentity app/services/payroll/billing_identity.rb:3 — TooManyMethods — 33 methods. The bar is 30 methods; this is 3 over it, 1.10× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: TrackingService app/services/analytics/tracking_service.rb:4 — TooManyMethods — 32 methods. The bar is 30 methods; this is 2 over it, 1.07× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: ConsultantRevision app/services/payroll/consultant_revision.rb:4 — TooManyMethods — 32 methods. The bar is 30 methods; this is 2 over it, 1.07× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: Snapshot app/services/payroll/snapshot.rb:7 — TooManyMethods — 32 methods. The bar is 30 methods; this is 2 over it, 1.07× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
AC6 · Visual & motion safety · Focus outline removed in CSS without a · ×15
  • Focus outline removed in CSS without a :focus replacement app/javascript/stylesheets/application.scss:290 — `.focus-ring` 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.
  • Focus outline removed in CSS without a :focus replacement app/javascript/stylesheets/application.scss:323 — `.sidebar__reset` 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.
  • Focus outline removed in CSS without a :focus replacement app/javascript/stylesheets/application.scss:327 — `.sidebar__apply` 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.
  • Focus outline removed in CSS without a :focus replacement app/javascript/stylesheets/application.scss:394 — `.header__searchInput` 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.
  • Focus outline removed in CSS without a :focus replacement app/javascript/stylesheets/application.scss:398 — `.header__button` 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.
  • Focus outline removed in CSS without a :focus replacement app/javascript/stylesheets/application.scss:438 — `.form__textarea` 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.
  • Focus outline removed in CSS without a :focus replacement app/javascript/stylesheets/application.scss:442 — `.form__input_submit` 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.
  • Focus outline removed in CSS without a :focus replacement app/javascript/stylesheets/application.scss:446 — `.form__input` 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.
  • Focus outline removed in CSS without a :focus replacement app/javascript/stylesheets/application.scss:458 — `.form__button` 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.
  • Focus outline removed in CSS without a :focus replacement app/javascript/stylesheets/application.scss:462 — `.form__button_outline` 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.
  • Focus outline removed in CSS without a :focus replacement app/javascript/stylesheets/application.scss:474 — `.form__save` 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.
  • Focus outline removed in CSS without a :focus replacement app/javascript/stylesheets/application.scss:478 — `.form__cancel` 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.
  • Focus outline removed in CSS without a :focus replacement app/javascript/stylesheets/application.scss:487 — `.button` 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.
  • Focus outline removed in CSS without a :focus replacement app/javascript/stylesheets/application.scss:530 — `.page-content__search-input` 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.
  • Focus outline removed in CSS without a :focus replacement app/javascript/stylesheets/application.scss:546 — `.page-content__new-user-button` 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.
D35 · Change Coupling · Change coupling · ×14
  • Change coupling: MobileProfileEditor.tsx ↔ ProfileEditor.tsx app/javascript/src/components/Profile/Personal/User/Edit/MobileProfileEditor.tsx:1 — `app/javascript/src/components/Profile/Personal/User/Edit/MobileProfileEditor.tsx` and `app/javascript/src/components/Profile/Personal/User/Edit/ProfileEditor.tsx` change together 85% of the time (11 of the 13 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency between them. They sit in the same directory, but in this ecosystem each file is its own module — a sibling reference still needs an import — so the missing import edge is real: the coupling runs through shared behaviour, not a declared dependency. If they duplicate structure, extract the common part into one unit; otherwise the coupling is hidden and worth breaking. You can check this without leaving the row: of the 11 shared commits counted here, the most recent 3 are `b9e67ab1` fix(profile): clamp phone input to 15 digits; `1f18dcb8` fix: enforce profile DOB and phone validation; `f79e20b9` fix(i18n): harden locale fallback and profile language settings (at that commit the files were still `app/javascript/src/components/Profile/Personal/User/Edit/MobileEditPage.tsx` and `app/javascript/src/components/Profile/Personal/User/Edit/StaticPage.tsx`) — run `git show` on any of them.
  • Change coupling: ClientEditor.tsx ↔ MobileClientEditor.tsx app/javascript/src/components/Clients/ClientForm/ClientEditor.tsx:1 — `app/javascript/src/components/Clients/ClientForm/ClientEditor.tsx` and `app/javascript/src/components/Clients/ClientForm/MobileClientEditor.tsx` change together 79% of the time (15 of the 19 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency between them. They sit in the same directory, but in this ecosystem each file is its own module — a sibling reference still needs an import — so the missing import edge is real: the coupling runs through shared behaviour, not a declared dependency. If they duplicate structure, extract the common part into one unit; otherwise the coupling is hidden and worth breaking. You can check this without leaving the row: of the 15 shared commits counted here, the most recent 3 are `4295eafb` fix: remove duplicate toast notifications when saving a client; `8cdf4b71` fix: harden invoice signature handling; `8f60165c` feat: add signed invoice options — run `git show` on any of them.
  • Change coupling: CreateClientModal.tsx ↔ EditClientModal.tsx app/javascript/src/components/Clients/Modals/CreateClientModal.tsx:1 — `app/javascript/src/components/Clients/Modals/CreateClientModal.tsx` and `app/javascript/src/components/Clients/Modals/EditClientModal.tsx` change together 76% of the time (13 of the 17 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency between them. They sit in the same directory, but in this ecosystem each file is its own module — a sibling reference still needs an import — so the missing import edge is real: the coupling runs through shared behaviour, not a declared dependency. If they duplicate structure, extract the common part into one unit; otherwise the coupling is hidden and worth breaking. You can check this without leaving the row: of the 13 shared commits counted here, the most recent 3 are `501d48f2` refactor(clients): rename client editors; `be4182c1` Add client role (#1369) (at that commit the files were still `app/javascript/src/components/Clients/Modals/NewClient.tsx` and `app/javascript/src/components/Clients/Modals/EditClient.tsx`); `2a64d50a` Modal component added on remaining pages (#1337) (at that commit the files were still `app/javascript/src/components/Clients/Modals/NewClient.tsx` and `app/javascript/src/components/Clients/Modals/EditClient.tsx`) — run `git show` on any of them.
  • Change coupling: filter_parameter_logging.rb ↔ api.rb config/initializers/filter_parameter_logging.rb:1 — `config/initializers/filter_parameter_logging.rb` and `config/routes/api.rb` change together 72% of the time (13 of the 18 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 13 shared commits counted here, the most recent 3 are `4fbef540` feat(hiring): record explicit Admin decisions and holds; `09b00bf1` feat(hiring): import verified Google Calendar bookings; `d7d08d19` feat(hiring): add manual interview scheduling — run `git show` on any of them.
  • Change coupling: REDACTED ↔ REDACTED REDACTED:1 — `REDACTED` and `REDACTED` change together 67% of the time (10 of the 15 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 10 shared commits counted here, the most recent 3 are `adefedd1` feat: mobile-first auth and billing, responsive CI net, Expo sessions…; `f4f6d3d3` fix(auth): improve disabled button contrast on auth forms; `c086acd8` fix(auth): improve theme contrast on sign in — run `git show` on any of them.
  • Change coupling: InvoiceListHeader.tsx ↔ InvoiceListTableHeader.tsx app/javascript/src/components/Invoices/List/InvoiceListHeader.tsx:1 — `app/javascript/src/components/Invoices/List/InvoiceListHeader.tsx` and `app/javascript/src/components/Invoices/List/Table/InvoiceListTableHeader.tsx` change together 64% of the time (7 of the 11 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `ff92e1e0` refactor(invoices): rename invoice list headers; `0e4840cb` Invoice list page mobile view updated (#965) (at that commit the files were still `app/javascript/src/components/Invoices/List/Header.tsx` and `app/javascript/src/components/Invoices/List/Table/TableHeader.tsx`); `89b7ca08` Ux review invoice list (#961) (at that commit the files were still `app/javascript/src/components/Invoices/List/Header.tsx` and `app/javascript/src/components/Invoices/List/Table/TableHeader.tsx`) — run `git show` on any of them.
  • Change coupling: EditMembersListForm.tsx ↔ index.tsx app/javascript/src/components/Projects/Details/EditMembersListForm.tsx:1 — `app/javascript/src/components/Projects/Details/EditMembersListForm.tsx` and `app/javascript/src/components/Projects/Details/index.tsx` change together 60% of the time (9 of the 15 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency between them. They sit in the same directory, but in this ecosystem each file is its own module — a sibling reference still needs an import — so the missing import edge is real: the coupling runs through shared behaviour, not a declared dependency. If they duplicate structure, extract the common part into one unit; otherwise the coupling is hidden and worth breaking. You can check this without leaving the row: of the 9 shared commits counted here, the most recent 3 are `5500aa54` fix: project team updates not reflected and last member cannot be rem…; `26d99408` fix(projects): modernize details and remove legacy invoice flow; `b04f0b57` Modal component: mobile screen (#1342) — run `git show` on any of them.
  • Change coupling: index.tsx ↔ index.tsx app/javascript/src/components/Reports/OutstandingInvoiceReport/index.tsx:1 — `app/javascript/src/components/Reports/OutstandingInvoiceReport/index.tsx` and `app/javascript/src/components/Reports/RevenueByClientReport/index.tsx` change together 60% of the time (6 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `e8f0228e` Export options for revenue & invoice reports (#1851); `c8666827` Fixed reset and filter counter issue on Revenue filter page (#1165); `887fad75` Hide unused frontend components (#640) (at that commit the files were still `app/javascript/src/components/Reports/outstandingInvoices/index.tsx` and `app/javascript/src/components/Reports/revenueByClient/index.tsx`) — run `git show` on any of them.
  • Change coupling: index.tsx ↔ index.tsx app/javascript/src/components/Reports/OutstandingInvoiceReport/index.tsx:1 — `app/javascript/src/components/Reports/OutstandingInvoiceReport/index.tsx` and `app/javascript/src/components/Reports/TimeEntryReport/index.tsx` change together 60% of the time (6 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `316cfa7f` Missing loader added (#1844); `c8666827` Fixed reset and filter counter issue on Revenue filter page (#1165); `887fad75` Hide unused frontend components (#640) (at that commit the files were still `app/javascript/src/components/Reports/outstandingInvoices/index.tsx` and `app/javascript/src/components/Reports/timeEntry/index.tsx`) — run `git show` on any of them.
  • Change coupling: InvoiceListTable.tsx ↔ index.tsx app/javascript/src/components/Invoices/List/Table/InvoiceListTable.tsx:1 — `app/javascript/src/components/Invoices/List/Table/InvoiceListTable.tsx` and `app/javascript/src/components/Invoices/List/index.tsx` change together 56% of the time (10 of the 18 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 10 shared commits counted here, the most recent 3 are `0adf1ab3` refactor(invoices): rename invoice list and selection tables; `ff92e1e0` refactor(invoices): rename invoice list headers (at that commit the file was still `app/javascript/src/components/Invoices/List/Table/index.tsx`); `00846446` Fix: Application breaking when pay button was clicked (#1325) (at that commit the file was still `app/javascript/src/components/Invoices/List/Table/index.tsx`) — run `git show` on any of them.
  • Change coupling: InvoiceListHeader.tsx ↔ InvoiceListTable.tsx app/javascript/src/components/Invoices/List/InvoiceListHeader.tsx:1 — `app/javascript/src/components/Invoices/List/InvoiceListHeader.tsx` and `app/javascript/src/components/Invoices/List/Table/InvoiceListTable.tsx` change together 56% of the time (10 of the 18 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 10 shared commits counted here, the most recent 3 are `ff92e1e0` refactor(invoices): rename invoice list headers (at that commit the file was still `app/javascript/src/components/Invoices/List/Table/index.tsx`); `89b7ca08` Ux review invoice list (#961) (at that commit the files were still `app/javascript/src/components/Invoices/List/Header.tsx` and `app/javascript/src/components/Invoices/List/Table/index.tsx`); `ad6fb2e6` Invoice filter UI update (#745) (at that commit the files were still `app/javascript/src/components/Invoices/List/Header.tsx` and `app/javascript/src/components/Invoices/List/Table/index.tsx`) — run `git show` on any of them.
  • Change coupling: LeaveBlock.tsx ↔ overview_service.rb app/javascript/src/components/LeaveManagement/Container/LeaveBlock.tsx:1 — `app/javascript/src/components/LeaveManagement/Container/LeaveBlock.tsx` and `app/services/timeoff_entries/overview_service.rb` change together 55% of the time (6 of the 11 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) and are written in DIFFERENT LANGUAGES, so no import can join them and they cannot be co-located into one unit — they compile and ship as separate artifacts. What binds them is a CONTRACT across that boundary — an event or message name, a route, a serialised shape — that each side currently spells out on its own, which is exactly why a change to one drags the other. Declare that contract once where both sides read it (a shared schema, a generated constants file, an interface-definition file) so a change on one side fails the other's build instead of drifting silently; where the surface is too small to be worth that, name the counterpart in a comment on both sides so the next reader finds it. There is nothing here to merge. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `f2ec55cc` feat: Add custom leaves support for time off entries (#2036) (at that commit the file was still `app/services/timeoff_entries/index_service.rb`); `d5b0e646` Fix negative pto calculation (#1843) (at that commit the file was still `app/services/timeoff_entries/index_service.rb`); `9098d42e` Updated design of filters on Leave management page (#1794) (at that commit the file was still `app/services/timeoff_entries/index_service.rb`) — run `git show` on any of them.
  • Change coupling: index.tsx ↔ overview_service.rb app/javascript/src/components/LeaveManagement/index.tsx:1 — `app/javascript/src/components/LeaveManagement/index.tsx` and `app/services/timeoff_entries/overview_service.rb` 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) and are written in DIFFERENT LANGUAGES, so no import can join them and they cannot be co-located into one unit — they compile and ship as separate artifacts. What binds them is a CONTRACT across that boundary — an event or message name, a route, a serialised shape — that each side currently spells out on its own, which is exactly why a change to one drags the other. Declare that contract once where both sides read it (a shared schema, a generated constants file, an interface-definition file) so a change on one side fails the other's build instead of drifting silently; where the surface is too small to be worth that, name the counterpart in a comment on both sides so the next reader finds it. There is nothing here to merge. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `f2ec55cc` feat: Add custom leaves support for time off entries (#2036) (at that commit the file was still `app/services/timeoff_entries/index_service.rb`); `6c771126` Fix multiple usernames and PTOs issue (#1830) (at that commit the file was still `app/services/timeoff_entries/index_service.rb`); `f7debe08` Updated Leaves & Holidays balance cards according to the design (#1776) (at that commit the file was still `app/services/timeoff_entries/index_service.rb`) — run `git show` on any of them.
  • Change coupling: LineItem.tsx ↔ LineItemEditorRow.tsx app/javascript/src/components/Invoices/Invoice/LineItem.tsx:1 — `app/javascript/src/components/Invoices/Invoice/LineItem.tsx` and `app/javascript/src/components/Invoices/common/NewLineItemRow/LineItemEditorRow.tsx` change together 50% of the time (5 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 5 shared commits counted here, the most recent 3 are `6e02d334` Fix invoice line-item employee name rendering (#2192); `44a7a6e8` Generate invoice page updates (#806) (at that commit the file was still `app/javascript/src/components/Invoices/common/NewLineItemRow/NewLineItemStatic.tsx`); `03f9dad5` Fixed invoice time entries hourly value along with invoice pdf (#653) (at that commit the file was still `app/javascript/src/components/Invoices/common/NewLineItemRow/NewLineItemStatic.tsx`) — run `git show` on any of them.
AC6 · Visual & motion safety · Focus outline removed inline · ×12
  • Focus outline removed inline app/javascript/src/common/LocaleSelector/LocaleDropdown.tsx:103 — <input> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
  • Focus outline removed inline app/javascript/src/components/Clients/Details/TotalHoursChart.tsx:35 — <select> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
  • Focus outline removed inline app/javascript/src/components/Clients/Modals/AddProject.tsx:58 — <select> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
  • Focus outline removed inline app/javascript/src/components/Clients/Modals/AddProject.tsx:77 — <input> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
  • Focus outline removed inline app/javascript/src/components/Clients/Modals/AddProject.tsx:132 — <button> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
  • Focus outline removed inline app/javascript/src/components/Clients/TotalHoursChart.tsx:60 — <select> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
  • Focus outline removed inline app/javascript/src/components/Profile/Organization/Details/MobileHeader.tsx:19 — <button> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
  • Focus outline removed inline app/javascript/src/components/Profile/Organization/Details/MobileHeader.tsx:31 — <button> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
  • Focus outline removed inline app/javascript/src/components/Profile/Organization/Holidays/Editor.tsx:206 — <select> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
  • Focus outline removed inline app/javascript/src/components/Profile/Organization/Payment/MobileView.tsx:36 — <button> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
  • Focus outline removed inline app/javascript/src/components/Projects/Details/TotalHoursChart.tsx:25 — <select> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
  • Focus outline removed inline app/javascript/src/components/payments/PaymentSearch/index.tsx:94 — <input> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
X3 · Exception handling · Swallowed exception (caught, then discarded) · ×12
  • Swallowed exception (caught, then discarded) config/environments/production.rb:7 — `… rescue nil` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) app/services/currency_conversion_service.rb:93 — `rescue StandardError` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) app/services/pdf_generation/invoice_service.rb:83 — `rescue StandardError` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) app/services/hiring/email_content.rb:142 — `… rescue Encoding::UTF_8` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) app/models/concerns/pg_searchable.rb:116 — `rescue` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) app/mcp/pro_access_checker.rb:15 — `rescue StandardError` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) app/mcp/server_factory.rb:46 — `rescue StandardError` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) app/mcp/server_factory.rb:52 — `rescue StandardError` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) app/mcp/tools/base_tool.rb:90 — `rescue StandardError` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) app/javascript/src/i18n/index.ts:146 — `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, or keep only the failure you expect and rethrow the rest (`catch (e) { if (!(e instanceof SyntaxError)) throw e; … }`, or test `e.name`), because a JavaScript catch takes every exception, programming errors included.
  • Swallowed exception (caught, then discarded) app/controllers/agent_readiness_controller.rb:263 — `rescue StandardError` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) app/controllers/concerns/authenticable.rb:65 — `rescue StandardError` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
X3 · Exception handling · Swallowed exception (empty catch) · ×10
  • Swallowed exception (empty catch) script/launch_matrix/verify.mjs:85 — 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) script/launch_matrix/verify.mjs:97 — 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) app/javascript/src/utils/runtimeRecovery.ts:92 — 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) app/javascript/src/utils/runtimeRecovery.ts:119 — 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) app/javascript/src/components/common/CompactLocaleSwitcher.tsx:37 — 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) app/javascript/src/components/Profile/Personal/User/Edit/ProfileEditor.tsx:580 — 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) app/javascript/src/components/Profile/Organization/Payment/RazorpayConnection.tsx:198 — 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) app/javascript/src/components/Profile/Organization/Payment/RazorpayConnection.tsx:229 — 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) app/javascript/src/components/DocumentSignatures/api.ts:44 — 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) app/javascript/src/components/Agreements/api.ts:56 — 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.
D4 · Code Duplication · Edited copy of a member (4 corresponding lines) · ×9
  • Edited copy of a member (4 corresponding lines) app/controllers/api/v1/hiring/assignment_reviews_controller.rb:31 — app/controllers/api/v1/hiring/assignment_reviews_controller.rb:31-34 | app/controllers/api/v1/hiring/assignments_controller.rb:42-45 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (4 corresponding lines) app/jobs/payroll_bank_change_recovery_job.rb:5 — app/jobs/payroll_bank_change_recovery_job.rb:5-8 | app/jobs/payroll_profile_completion_recovery_job.rb:6-9 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (4 corresponding lines) app/models/hiring_assignment_submission.rb:94 — app/models/hiring_assignment_submission.rb:94-99 | app/services/hiring/form.rb:127-130 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (4 corresponding lines) app/controllers/internal_api/v1/analytics_controller.rb:125 — app/controllers/internal_api/v1/analytics_controller.rb:125-128 | app/controllers/internal_api/v1/analytics_exports_controller.rb:118-121 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (4 corresponding lines) app/policies/users/device_policy.rb:20 — app/policies/users/device_policy.rb:20-23 | app/policies/users/previous_employment_policy.rb:12-15 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (4 corresponding lines) app/policies/users/device_policy.rb:5 — app/policies/users/device_policy.rb:5-8 | app/policies/users/previous_employment_policy.rb:5-8 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (4 corresponding lines) app/services/payroll/mercury_reconciliation.rb:189 — app/services/payroll/mercury_reconciliation.rb:189-192 | app/services/payroll/split_arrangements.rb:95-99 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (4 corresponding lines) app/models/hiring_decision.rb:58 — app/models/hiring_decision.rb:58-61 | app/models/hiring_offer.rb:109-112 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (4 corresponding lines) app/controllers/reports/compensation_profitability_controller.rb:97 — app/controllers/reports/compensation_profitability_controller.rb:97-100 | REDACTED:70-74 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
AC3 · Page structure · Page without a main landmark · ×7
  • Page without a main landmark app/views/layouts/pdf.html.erb:2 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
  • Page without a main landmark app/views/pdfs/analytics_export.html.erb:2 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
  • Page without a main landmark app/views/pdfs/client_revenues.html.erb:2 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
  • Page without a main landmark app/views/pdfs/invoices.html.erb:2 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
  • Page without a main landmark app/views/pdfs/outstanding_overdue_invoices.html.erb:2 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
  • Page without a main landmark app/views/pdfs/payments.html.erb:2 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
  • Page without a main landmark public/test-mobile-nav.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 · Animation without a prefers-reduced-motion guard · ×7
  • Animation without a prefers-reduced-motion guard app/javascript/src/components/Dashboard/MonochromeCharts.tsx:61 — <div> moves — its `animate-spin` utility runs with no motion-safe:/motion-reduce: variant — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:.
  • Animation without a prefers-reduced-motion guard app/javascript/src/components/Dashboard/MonochromeCharts.tsx:214 — <div> moves — its `animate-spin` utility runs with no motion-safe:/motion-reduce: variant — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:.
  • Animation without a prefers-reduced-motion guard app/javascript/src/components/Dashboard/MonochromeCharts.tsx:240 — <div> moves — its inline style sets `animation: slideIn 1s ease-out` — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:.
  • Animation without a prefers-reduced-motion guard app/javascript/src/components/Invoices/List/RecentlyUpdated/InfiniteScrollRecentlyUpdated.tsx:222 — <div> moves — its `animate-spin` utility runs with no motion-safe:/motion-reduce: variant — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:.
  • Animation without a prefers-reduced-motion guard app/javascript/src/components/Settings/Preferences/index.tsx:311 — <div> moves — its `animate-spin` utility runs with no motion-safe:/motion-reduce: variant — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:.
  • Animation without a prefers-reduced-motion guard app/javascript/src/components/TimeTracking/WeekDaySelector.tsx:66 — <span> moves — its `animate-ping` utility runs with no motion-safe:/motion-reduce: variant — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:.
  • Animation without a prefers-reduced-motion guard public/test-mobile-nav.html:88 — `.sidebar` moves (`transition: transform 0.3s ease`) 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.
D17 · Explicit Debt · TodoComment · ×7
  • TodoComment spec/models/client_search_spec.rb:135 — # TODO: implement includes option in Searchable concern — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `# REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment spec/models/client_search_spec.rb:143 — # TODO: implement fields option in Searchable concern — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `# REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment spec/models/client_search_spec.rb:152 — # TODO: implement fields option in Searchable concern — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `# REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment spec/models/concerns/pg_searchable_spec.rb:100 — # TODO: implement fuzzy_search method — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `# REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment app/javascript/src/components/Reports/RevenueByClientReport/WorkspaceView.tsx:258 — // TODO: Implement export functionality — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment app/javascript/src/components/Clients/TotalHoursChart.tsx:19 — // TODO: replace with ChartBar data type if available — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment app/controllers/api/v1/time_tracking_controller.rb:3 — # TODO: Refactoring -> can be merge with time entries controller — 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.
D4 · Code Duplication · Duplicated block (5 lines × 2) · ×7
  • Duplicated block (5 lines × 2) app/controllers/api/v1/employee_records_controller.rb:85 — app/controllers/api/v1/employee_records_controller.rb:85-89 | app/controllers/api/v1/tax_declarations_controller.rb:98-102 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (5 lines × 2) app/controllers/api/v1/consultant_billing_identities_controller.rb:87 — app/controllers/api/v1/consultant_billing_identities_controller.rb:87-91 | app/controllers/api/v1/consultant_invoice_authorizations_controller.rb:51-56 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (5 lines × 2) app/controllers/webhooks/paypal_controller.rb:28 — app/controllers/webhooks/paypal_controller.rb:28-32 | app/controllers/webhooks/razorpay_controller.rb:68-72 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (5 lines × 2) app/controllers/api/v1/hiring/decision_messages_controller.rb:7 — app/controllers/api/v1/hiring/decision_messages_controller.rb:7-11 | app/controllers/api/v1/hiring/offer_messages_controller.rb:7-11 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (5 lines × 2) app/services/expenses/fetch_service.rb:67 — app/services/expenses/fetch_service.rb:67-71 | app/services/invoices/index_service.rb:119-123 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (5 lines × 2) app/controllers/api/v1/consultant_billing_identities_controller.rb:97 — app/controllers/api/v1/consultant_billing_identities_controller.rb:97-101 | app/controllers/api/v1/consultant_invoice_authorizations_controller.rb:62-66 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (5 lines × 2) db/migrate/20261108200500_protect_payroll_pto_history.rb:99 — db/migrate/20261108200500_protect_payroll_pto_history.rb:99-103 | db/migrate/20261108200500_protect_payroll_pto_history.rb:150-154 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
IC1 · Incompleteness & stubs · Markup wires an event to an empty handler · ×7
  • Markup wires an event to an empty handler app/javascript/src/components/Clients/Header/index.tsx:58 — `onSelect` is wired to an arrow whose body is empty — the markup attaches a listener that does nothing. Implement the handler, or remove the attribute that wires it.
  • Markup wires an event to an empty handler app/javascript/src/components/Expenses/Modals/ExpenseForm.tsx:194 — `onChange` is wired to an arrow whose body is empty — the markup attaches a listener that does nothing. Implement the handler, or remove the attribute that wires it.
  • Markup wires an event to an empty handler app/javascript/src/components/Invoices/Invoice/MarkInvoicePaidModal.tsx:127 — `onChange` is wired to an arrow whose body is empty — the markup attaches a listener that does nothing. Implement the handler, or remove the attribute that wires it.
  • Markup wires an event to an empty handler app/javascript/src/components/Invoices/Invoice/MarkInvoicePaidModal.tsx:149 — `onChange` is wired to an arrow whose body is empty — the markup attaches a listener that does nothing. Implement the handler, or remove the attribute that wires it.
  • Markup wires an event to an empty handler app/javascript/src/components/Invoices/Invoice/MarkInvoicePaidModal.tsx:277 — `onChange` is wired to an arrow whose body is empty — the markup attaches a listener that does nothing. Implement the handler, or remove the attribute that wires it.
  • Markup wires an event to an empty handler app/javascript/src/components/Team/List/Header.tsx:45 — `onSelect` is wired to an arrow whose body is empty — the markup attaches a listener that does nothing. Implement the handler, or remove the attribute that wires it.
  • Markup wires an event to an empty handler app/javascript/src/components/payments/Modals/PaymentEntryForm.tsx:417 — `onChange` is wired to an arrow whose body is empty — the markup attaches a listener that does nothing. Implement the handler, or remove the attribute that wires it.
AC2 · Forms & labels · <Select> field component without a label · ×6
  • <Select> field component without a label app/javascript/src/common/SearchTimeEntries.tsx:49 — This select is named only by the placeholder of its value part. Nothing is typed into a select, so the placeholder does not vanish on input: it is shown as the trigger's text until a value is chosen, and then the chosen value replaces it — so at no point does the control state what the choice is for, and the trigger's role (combobox) takes its name from the author, not from that text. Name it: an aria-label on the trigger, or an id on the trigger with a <label htmlFor> pointing at it.
  • <Select> field component without a label app/javascript/src/components/Analytics/components/AnalyticsFilters.tsx:65 — This select is named only by the placeholder of its value part. Nothing is typed into a select, so the placeholder does not vanish on input: it is shown as the trigger's text until a value is chosen, and then the chosen value replaces it — so at no point does the control state what the choice is for, and the trigger's role (combobox) takes its name from the author, not from that text. Name it: an aria-label on the trigger, or an id on the trigger with a <label htmlFor> pointing at it.
  • <Select> field component without a label app/javascript/src/components/Clients/ClientForm/ClientEditor.tsx:259 — This select is named only by the placeholder of its value part. Nothing is typed into a select, so the placeholder does not vanish on input: it is shown as the trigger's text until a value is chosen, and then the chosen value replaces it — so at no point does the control state what the choice is for, and the trigger's role (combobox) takes its name from the author, not from that text. Name it: an aria-label on the trigger, or an id on the trigger with a <label htmlFor> pointing at it.
  • <Select> field component without a label app/javascript/src/components/Clients/ClientForm/ClientEditor.tsx:358 — This select is named only by the placeholder of its value part. Nothing is typed into a select, so the placeholder does not vanish on input: it is shown as the trigger's text until a value is chosen, and then the chosen value replaces it — so at no point does the control state what the choice is for, and the trigger's role (combobox) takes its name from the author, not from that text. Name it: an aria-label on the trigger, or an id on the trigger with a <label htmlFor> pointing at it.
  • <Select> field component without a label app/javascript/src/components/Clients/ClientForm/MobileClientEditor.tsx:265 — This select is named only by the placeholder of its value part. Nothing is typed into a select, so the placeholder does not vanish on input: it is shown as the trigger's text until a value is chosen, and then the chosen value replaces it — so at no point does the control state what the choice is for, and the trigger's role (combobox) takes its name from the author, not from that text. Name it: an aria-label on the trigger, or an id on the trigger with a <label htmlFor> pointing at it.
  • <Select> field component without a label app/javascript/src/components/Clients/ClientForm/MobileClientEditor.tsx:351 — This select is named only by the placeholder of its value part. Nothing is typed into a select, so the placeholder does not vanish on input: it is shown as the trigger's text until a value is chosen, and then the chosen value replaces it — so at no point does the control state what the choice is for, and the trigger's role (combobox) takes its name from the author, not from that text. Name it: an aria-label on the trigger, or an id on the trigger with a <label htmlFor> pointing at it.
AC3 · Page structure · Data table has no header cells · ×6
  • Data table has no header cells app/javascript/src/components/ClientInvoices/Details/InvoiceTotalSummary.tsx:18 — A <table> with data cells but no <th> gives assistive technology no way to associate cells with their headers. Mark the header row/column cells as <th> (with a scope).
  • Data table has no header cells app/javascript/src/components/InvoiceEmail/InvoiceTotalSummary.tsx:18 — A <table> with data cells but no <th> gives assistive technology no way to associate cells with their headers. Mark the header row/column cells as <th> (with a scope).
  • Data table has no header cells app/javascript/src/components/Invoices/Invoice/InvoiceTotalSummary.tsx:18 — A <table> with data cells but no <th> gives assistive technology no way to associate cells with their headers. Mark the header row/column cells as <th> (with a scope).
  • Data table has no header cells app/javascript/src/components/Invoices/common/InvoiceTotal/index.tsx:60 — A <table> with data cells but no <th> gives assistive technology no way to associate cells with their headers. Mark the header row/column cells as <th> (with a scope).
  • Data table has no header cells app/javascript/src/components/LeaveManagement/Container/Table/index.tsx:8 — A <table> with data cells but no <th> gives assistive technology no way to associate cells with their headers. Mark the header row/column cells as <th> (with a scope).
  • Data table has no header cells app/views/devise/shared/_footer.html.erb:6 — A <table> with data cells but no <th> gives assistive technology no way to associate cells with their headers. Mark the header row/column cells as <th> (with a scope).
D4 · Code Duplication · Edited copy of a member (3 corresponding lines) · ×6
  • Edited copy of a member (3 corresponding lines) app/services/hiring/interviews.rb:194 — app/services/hiring/interviews.rb:194-196 | app/services/hiring/scheduling.rb:228-232 — These two members are one piece of code written twice and then edited apart: 3 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (3 corresponding lines) app/services/payroll_calculation/values.rb:52 — app/services/payroll_calculation/values.rb:52-54 | app/services/reports/compensation_profitability.rb:62-66 — These two members are one piece of code written twice and then edited apart: 3 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (3 corresponding lines) REDACTED:91 — REDACTED:91-93 | app/services/payroll/service_fee_review.rb:119-121 — These two members are one piece of code written twice and then edited apart: 3 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (3 corresponding lines) app/controllers/api/v1/custom_leaves_controller.rb:7 — app/controllers/api/v1/custom_leaves_controller.rb:7-9 | app/controllers/api/v1/leave_with_leave_types_controller.rb:7-9 — These two members are one piece of code written twice and then edited apart: 3 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (3 corresponding lines) app/controllers/internal_api/v1/analytics_controller.rb:132 — app/controllers/internal_api/v1/analytics_controller.rb:132-134 | app/controllers/internal_api/v1/analytics_exports_controller.rb:125-127 — These two members are one piece of code written twice and then edited apart: 3 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (3 corresponding lines) app/controllers/internal_api/v1/analytics_controller.rb:138 — app/controllers/internal_api/v1/analytics_controller.rb:138-140 | app/controllers/internal_api/v1/analytics_exports_controller.rb:131-133 — These two members are one piece of code written twice and then edited apart: 3 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
P7 · Outbound HTTP resilience · Outbound HTTP without resilience · ×6
  • Outbound HTTP without resilience app/services/hubspot_integration_service.rb:4 — `HTTParty` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
  • Outbound HTTP without resilience app/services/hubspot_integration_service.rb:34 — `HTTParty.post` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
  • Outbound HTTP without resilience app/services/mobile_otp/delivery.rb:41 — `Net::HTTP.start` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
  • Outbound HTTP without resilience app/services/payment_providers/razorpay_client.rb:125 — `HTTParty` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
  • Outbound HTTP without resilience app/services/quick_books/client.rb:41 — `Faraday.new` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
  • Outbound HTTP without resilience app/services/quick_books/oauth_client.rb:68 — `Faraday.new` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
AC3 · Page structure · Heading level jumps from h1 to h3 · ×5
  • Heading level jumps from h1 to h3 app/javascript/src/components/Invoices/List/Table/TableRow.tsx:158 — Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
  • Heading level jumps from h1 to h3 app/javascript/src/components/Profile/EmployeeRecords/index.tsx:273 — Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
  • Heading level jumps from h1 to h3 app/javascript/src/components/payments/Mobile/Table/TableRow.tsx:32 — Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
  • Heading level jumps from h1 to h3 app/javascript/src/components/payments/Table/TableRow.tsx:120 — Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
  • Heading level jumps from h1 to h3 app/views/analytics/index.html.erb:108 — Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
D4 · Code Duplication · Edited copy of a member (14 corresponding lines) · ×5
  • Edited copy of a member (14 corresponding lines) db/migrate/20261108201000_create_payroll_pto_notifications.rb:5 — db/migrate/20261108201000_create_payroll_pto_notifications.rb:5-18 | db/migrate/20261109140000_create_payroll_bank_change_notices.rb:5-20 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (14 corresponding lines) app/models/hiring_assignment_submission.rb:25 — app/models/hiring_assignment_submission.rb:25-40 | app/models/hiring_submission.rb:43-56 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (14 corresponding lines) app/services/hiring/decisions.rb:56 — app/services/hiring/decisions.rb:56-69 | app/services/hiring/offers.rb:50-65 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (14 corresponding lines) app/services/hiring/delivery.rb:11 — app/services/hiring/delivery.rb:11-24 | app/services/payroll/india_delivery.rb:14-27 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (14 corresponding lines) app/services/hiring/interviews.rb:84 — app/services/hiring/interviews.rb:84-97 | app/services/hiring/scheduling.rb:71-86 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (6 corresponding lines) · ×5
  • Edited copy of a member (6 corresponding lines) app/controllers/api/v1/agreement_templates_controller.rb:62 — app/controllers/api/v1/agreement_templates_controller.rb:62-67 | app/controllers/api/v1/agreements_controller.rb:114-120 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (6 corresponding lines) app/controllers/api/v1/hiring/interviews_controller.rb:13 — app/controllers/api/v1/hiring/interviews_controller.rb:13-18 | app/controllers/api/v1/hiring/interviews_controller.rb:22-27 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (6 corresponding lines) app/controllers/internal_api/v1/analytics_controller.rb:114 — app/controllers/internal_api/v1/analytics_controller.rb:114-121 | app/controllers/internal_api/v1/analytics_exports_controller.rb:109-114 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (6 corresponding lines) app/services/hiring/offer_communication.rb:14 — app/services/hiring/offer_communication.rb:14-20 | app/services/hiring/onboarding.rb:164-169 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (6 corresponding lines) app/controllers/api/v1/application_controller.rb:61 — app/controllers/api/v1/application_controller.rb:61-68 | app/controllers/application_controller.rb:26-31 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
S1 · Web-Security Posture · Weak hash algorithm · ×5
  • Weak hash algorithm app/controllers/hiring_portal_controller.rb:139 — MD5/SHA1 is computed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ (`Digest::SHA256` or `OpenSSL::Digest.new("SHA256")`) for content integrity, or a KDF (bcrypt/Argon2/scrypt) for password storage. If it only derives a non-security identifier (a cache key, an avatar URL, an ETag), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as xxhash or murmurhash says it in code — since the algorithm alone cannot distinguish the two uses. Where a protocol this code does not own fixes the digest (a k-anonymity range query, a legacy signature format), the protocol decides; say so beside the call.
  • Weak hash algorithm app/services/hiring/assignments.rb:194 — MD5/SHA1 is computed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ (`Digest::SHA256` or `OpenSSL::Digest.new("SHA256")`) for content integrity, or a KDF (bcrypt/Argon2/scrypt) for password storage. If it only derives a non-security identifier (a cache key, an avatar URL, an ETag), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as xxhash or murmurhash says it in code — since the algorithm alone cannot distinguish the two uses. Where a protocol this code does not own fixes the digest (a k-anonymity range query, a legacy signature format), the protocol decides; say so beside the call.
  • Weak hash algorithm REDACTED:59 — MD5/SHA1 is computed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ (`Digest::SHA256` or `OpenSSL::Digest.new("SHA256")`) for content integrity, or a KDF (bcrypt/Argon2/scrypt) for password storage. If it only derives a non-security identifier (a cache key, an avatar URL, an ETag), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as xxhash or murmurhash says it in code — since the algorithm alone cannot distinguish the two uses. Where a protocol this code does not own fixes the digest (a k-anonymity range query, a legacy signature format), the protocol decides; say so beside the call.
  • Weak hash algorithm REDACTED:65 — MD5/SHA1 is computed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ (`Digest::SHA256` or `OpenSSL::Digest.new("SHA256")`) for content integrity, or a KDF (bcrypt/Argon2/scrypt) for password storage. If it only derives a non-security identifier (a cache key, an avatar URL, an ETag), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as xxhash or murmurhash says it in code — since the algorithm alone cannot distinguish the two uses. Where a protocol this code does not own fixes the digest (a k-anonymity range query, a legacy signature format), the protocol decides; say so beside the call.
  • Weak hash algorithm app/services/signatures/upload.rb:31 — MD5/SHA1 is computed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ (`Digest::SHA256` or `OpenSSL::Digest.new("SHA256")`) for content integrity, or a KDF (bcrypt/Argon2/scrypt) for password storage. If it only derives a non-security identifier (a cache key, an avatar URL, an ETag), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as xxhash or murmurhash says it in code — since the algorithm alone cannot distinguish the two uses. Where a protocol this code does not own fixes the digest (a k-anonymity range query, a legacy signature format), the protocol decides; say so beside the call.
AC2 · Forms & labels · <DatePicker> field component without a label · ×4
  • <DatePicker> field component without a label app/javascript/src/common/CustomDatePicker/index.tsx:71 — 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 app/javascript/src/common/CustomDateRangePicker/index.tsx:198 — 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 app/javascript/src/common/CustomDateRangeWIthInput/index.tsx:270 — 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 app/javascript/src/common/CustomYearPicker/SingleYearDatePicker.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.
D4 · Code Duplication · Edited copy of a member (16 corresponding lines) · ×4
  • Edited copy of a member (16 corresponding lines) app/controllers/api/v1/salary_slips_controller.rb:67 — app/controllers/api/v1/salary_slips_controller.rb:67-84 | app/controllers/api/v1/tax_declarations_controller.rb:87-102 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (16 corresponding lines) REDACTED:5 — REDACTED:5-20 | REDACTED:5-23 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (16 corresponding lines) lib/authentication/github.rb:20 — lib/authentication/github.rb:20-36 | lib/authentication/google.rb:20-35 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (16 corresponding lines) app/services/timeoff_entries/calculate_total_duration_of_defined_leaves_service.rb:121 — app/services/timeoff_entries/calculate_total_duration_of_defined_leaves_service.rb:121-136 | app/services/timeoff_entries/calculate_total_duration_of_defined_leaves_service.rb:140-158 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (5 corresponding lines) · ×4
  • Edited copy of a member (5 corresponding lines) config/initializers/encoding_sanitizer.rb:65 — config/initializers/encoding_sanitizer.rb:65-69 | config/initializers/encoding_sanitizer.rb:120-125 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (5 corresponding lines) app/services/payroll/invoice_authorization.rb:96 — app/services/payroll/invoice_authorization.rb:96-100 | app/services/payroll/billing_identity.rb:186-190 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (5 corresponding lines) app/controllers/api/v1/hiring/base_controller.rb:74 — app/controllers/api/v1/hiring/base_controller.rb:74-78 | app/services/hiring/pipeline.rb:56-60 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (5 corresponding lines) app/controllers/api/v1/cli/timesheet_entries_controller.rb:25 — app/controllers/api/v1/cli/timesheet_entries_controller.rb:25-33 | app/controllers/api/v1/timesheet_entry_controller.rb:40-44 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
IC1 · Incompleteness & stubs · Both branches are identical · ×4
  • Both branches are identical — the condition decides nothing app/javascript/src/components/Invoices/InvoiceSummary/index.tsx:61 — Both arms of this conditional expression are the same, so no input can make the condition matter. Implement the distinction that was intended, or drop the condition.
  • Both branches are identical — the condition decides nothing app/javascript/src/components/Reports/Filters/index.tsx:75 — The `if` and its `else` contain the same statements, so no input can make the condition matter. Implement the distinction that was intended, or drop the branch and keep the body.
  • Both branches are identical — the condition decides nothing app/javascript/src/components/Reports/OutstandingInvoiceReport/Filters/index.tsx:42 — The `if` and its `else` contain the same statements, so no input can make the condition matter. Implement the distinction that was intended, or drop the branch and keep the body.
  • Both branches are identical — the condition decides nothing app/javascript/src/components/TimesheetEntries/TimeEntryForm/MobileEntryForm.tsx:407 — Both arms of this conditional expression are the same, so no input can make the condition matter. Implement the distinction that was intended, or drop the condition.
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D30 · Dependency Vulnerabilities · Medium CVE · ×3
  • REDACTED
  • REDACTED
  • REDACTED
D4 · Code Duplication · Edited copy of a member (7 corresponding lines) · ×3
  • Edited copy of a member (7 corresponding lines) app/controllers/api/v1/consultant_billing_identities_controller.rb:95 — app/controllers/api/v1/consultant_billing_identities_controller.rb:95-101 | app/controllers/api/v1/consultant_invoice_authorizations_controller.rb:60-66 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (7 corresponding lines) app/controllers/analytics_controller.rb:148 — app/controllers/analytics_controller.rb:148-154 | app/controllers/analytics_controller.rb:291-297 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (7 corresponding lines) db/migrate/20231115121129_create_ses_invalid_emails.rb:5 — db/migrate/20231115121129_create_ses_invalid_emails.rb:5-11 | db/migrate/20260320110008_drop_ses_invalid_emails_table.rb:12-19 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (13 corresponding lines) · ×3
  • Edited copy of a member (13 corresponding lines) app/jobs/payroll_bank_change_notice_job.rb:5 — app/jobs/payroll_bank_change_notice_job.rb:5-17 | app/jobs/payroll_profile_completion_request_job.rb:6-21 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (13 corresponding lines) db/migrate/20261108020000_add_hiring_offer_messages.rb:19 — db/migrate/20261108020000_add_hiring_offer_messages.rb:19-31 | db/migrate/20261108040000_add_hiring_assignment_messages.rb:19-32 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (13 corresponding lines) app/services/payment_providers/razorpay_payment_link_service.rb:162 — app/services/payment_providers/razorpay_payment_link_service.rb:162-177 | app/services/payment_providers/razorpay_payment_link_service.rb:181-193 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (9 corresponding lines) · ×3
  • Edited copy of a member (9 corresponding lines) app/services/invoice_payment/stripe_checkout_fulfillment.rb:54 — app/services/invoice_payment/stripe_checkout_fulfillment.rb:54-63 | app/services/invoice_payment/stripe_payment_succeeded.rb:35-43 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (9 corresponding lines) db/migrate/20230309061149_copy_company_address_to_address_model.rb:5 — db/migrate/20230309061149_copy_company_address_to_address_model.rb:5-13 | db/migrate/20230309090124_copy_client_address_to_address_model.rb:5-13 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (9 corresponding lines) app/services/weekly_reminder_for_missed_entries_service.rb:114 — app/services/weekly_reminder_for_missed_entries_service.rb:114-123 | app/services/analytics/team_productivity_analytics.rb:162-170 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (1 corresponding lines) · ×3
  • Edited copy of a member (1 corresponding lines) app/models/india_tax/salary_estimate.rb:105 — app/models/india_tax/salary_estimate.rb:105-108 | app/services/hiring/form.rb:118-118 — These two members are one piece of code written twice and then edited apart: 1 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (1 corresponding lines) app/services/hiring/calendar_events.rb:90 — app/services/hiring/calendar_events.rb:90-92 | app/services/hiring/form.rb:149-149 — These two members are one piece of code written twice and then edited apart: 1 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (1 corresponding lines) app/models/agent.rb:21 — app/models/agent.rb:21-21 | app/models/timesheet_entry.rb:116-116 — These two members are one piece of code written twice and then edited apart: 1 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
IC1 · Incompleteness & stubs · Empty method body · ×3
  • Empty method body — does nothing with its inputs app/javascript/src/components/Reports/context/RevenueByClientContext.tsx:21 — `handleRemoveSingleFilter` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it.
  • Empty method body — does nothing with its inputs app/javascript/src/components/Reports/context/TimeEntryReportContext.tsx:24 — `handleRemoveSingleFilter` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it.
  • Empty method body — does nothing with its inputs app/javascript/src/components/Reports/context/outstandingOverdueInvoiceContext.tsx:21 — `handleRemoveSingleFilter` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it.
AC6 · Visual & motion safety · Low contrast colour pair in CSS (2.7 · ×2
  • Low contrast colour pair in CSS (2.7:1) app/views/reports/compensation_profitability/show.html.erb:20 — `button, .button` sets color: white on background-color: #a78bfa — 2.7:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
  • Low contrast colour pair in CSS (2.7:1) app/views/reports/profitability_scenarios/_styles.html.erb:8 — `button[type=submit],.button` sets color: white on background-color: #a78bfa — 2.7:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
D1 · Cyclomatic Complexity · WeeklyEntriesCard.WeeklyEntriesCard (cyclomatic 30) · ×2
  • WeeklyEntriesCard.WeeklyEntriesCard (cyclomatic 30) app/javascript/src/components/TimeTracking/WeeklyEntriesCard.tsx:16 — WeeklyEntriesCard.WeeklyEntriesCard has cyclomatic complexity 30 (threshold 15). Most of this is not in the body itself: 8 of the 30 points are its own statements and the rest belongs to 10 function items inside it that branch (handleDurationClick, handleSaveEntry, handleUpdateEntry, …). 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.
  • WeeklyEntriesCard.WeeklyEntriesCard (cyclomatic 30) app/javascript/src/components/TimesheetEntries/WeekView/WeeklyEntriesCard.tsx:20 — WeeklyEntriesCard.WeeklyEntriesCard has cyclomatic complexity 30 (threshold 15). Most of this is not in the body itself: 9 of the 30 points are its own statements and the rest belongs to 11 function items inside it that branch (handleDurationClick, a function literal at line 243, handleSaveEntry, …). 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.TimeTracking · ×2
  • index.TimeTracking::TimeTrackingContent (cyclomatic 25) app/javascript/src/components/TimeTracking/index.tsx:815 — index.TimeTracking::TimeTrackingContent has cyclomatic complexity 25 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators. This shape REPEATS in the file: one other method here (index.TimeTracking::fetchTimeTrackingData) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
  • index.TimeTracking::fetchTimeTrackingData (cyclomatic 16) app/javascript/src/components/TimeTracking/index.tsx:165 — index.TimeTracking::fetchTimeTrackingData 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. This shape REPEATS in the file: one other method here (index.TimeTracking::TimeTrackingContent) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D1 · Cyclomatic Complexity · Header.Header (cyclomatic 22) · ×2
  • Header.Header (cyclomatic 22) app/javascript/src/components/ClientInvoices/Details/Header.tsx:15 — Header.Header has cyclomatic complexity 22 (threshold 15). Of this number, 15 points are the body's own statements and 7 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.
  • Header.Header (cyclomatic 22) app/javascript/src/components/InvoiceEmail/Header.tsx:9 — Header.Header has cyclomatic complexity 22 (threshold 15). Of this number, 15 points are the body's own statements and 7 belong to one function item 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.
D10 · Test Quality · No assertions · ×2
  • No assertions: analyze weekly and monthly views analyze-time-tracking.spec.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.
  • No assertions: should edit existing time entry spec/e2e/time-tracking.spec.ts:210 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
D2 · Cognitive Complexity · index.Workspace (cognitive 24) · ×2
  • index.Workspace (cognitive 24) app/javascript/src/components/Agreements/index.tsx:232 — index.Workspace has cognitive complexity 24 (threshold 15). Drivers by points: boolean chains 10, if/else 6 (7 pts), ternaries 5 (6 pts), error handling 1 (nesting depth added 2). Most of this is not in the body itself: 9 of the 24 points are its own statements and the rest belongs to 6 function items inside it that branch (create, a function literal at line 258, a function literal at line 328, …). 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.
  • index.Workspace (cognitive 24) app/javascript/src/components/DocumentSignatures/index.tsx:195 — index.Workspace has cognitive complexity 24 (threshold 15). Drivers by points: boolean chains 12, if/else 9 (10 pts), error handling 1, ternaries 1 (nesting depth added 1). Most of this is not in the body itself: 10 of the 24 points are its own statements and the rest belongs to 5 function items inside it that branch (create, a function literal at line 232, a function literal at line 238, …). 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 · index.Holidays · ×2
  • index.Holidays::handleDatePicker (cognitive 22) app/javascript/src/components/Profile/Organization/Holidays/index.tsx:196 — index.Holidays::handleDatePicker has cognitive complexity 22 (threshold 15). Drivers by points: if/else 10 (22 pts) (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: one other method here (index.Holidays::handleHolidateNameChange) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
  • index.Holidays::handleHolidateNameChange (cognitive 22) app/javascript/src/components/Profile/Organization/Holidays/index.tsx:304 — index.Holidays::handleHolidateNameChange has cognitive complexity 22 (threshold 15). Drivers by points: if/else 10 (22 pts) (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: one other method here (index.Holidays::handleDatePicker) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D2 · Cognitive Complexity · Header.Header (cognitive 16) · ×2
  • Header.Header (cognitive 16) app/javascript/src/components/ClientInvoices/Header.tsx:13 — Header.Header has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (8 pts), boolean chains 7, error handling 1 (nesting depth added 1). Most of this is not in the body itself: 5 of the 16 points are its own statements and the rest belongs to 5 function items inside it that branch (a function literal at line 32, a function literal at line 23, a function literal at line 45, …). 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.
  • Header.Header (cognitive 16) app/javascript/src/components/TimeTracking/Header.tsx:14 — Header.Header has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 6, if/else 6, ternaries 4. Most of this is not in the body itself: 6 of the 16 points are its own statements and the rest belongs to 5 function items inside it that branch (getLabel, getRightArrowAction, getLeftArrowAction, …). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D29 · Static Analysis (SAST) · REDACTED · ×2
  • REDACTED
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×2
  • REDACTED
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×2
  • REDACTED
  • REDACTED
D32 · Data Compliance (PII/GDPR) · REDACTED
  • REDACTED
  • REDACTED
D4 · Code Duplication · Edited copies of one member (3 members, 6+ corresponding lines) · ×2
  • Edited copies of one member (3 members, 6+ corresponding lines) app/services/hiring/assignment_communication.rb:91 — app/services/hiring/assignment_communication.rb:91-98 | app/services/hiring/feedback_communication.rb:43-48 | app/services/hiring/offer_communication.rb:62-67 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 6 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 6+ corresponding lines) db/migrate/20220221043632_create_company_users.rb:5 — db/migrate/20220221043632_create_company_users.rb:5-10 | db/migrate/20230612105554_add_client_memebers.rb:5-10 | db/migrate/20240426053100_create_custom_leave_users.rb:5-10 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 6 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (18 corresponding lines) · ×2
  • Edited copy of a member (18 corresponding lines) app/services/hiring/assignment_communication.rb:15 — app/services/hiring/assignment_communication.rb:15-34 | app/services/hiring/decision_communication.rb:14-31 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (18 corresponding lines) tools/miru-cli/cmd/miru/main.go:1352 — tools/miru-cli/cmd/miru/main.go:1352-1369 | tools/miru-cli/cmd/miru/main.go:1371-1388 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (8 corresponding lines) · ×2
  • Edited copy of a member (8 corresponding lines) app/models/hiring_decision.rb:47 — app/models/hiring_decision.rb:47-54 | app/services/hiring/pipeline.rb:72-80 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (8 corresponding lines) app/services/invoice_payment/stripe_checkout_failed.rb:25 — app/services/invoice_payment/stripe_checkout_failed.rb:25-32 | app/services/invoice_payment/stripe_payment_failed.rb:25-33 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (11 corresponding lines) · ×2
  • Edited copy of a member (11 corresponding lines) db/migrate/20261107160000_add_hiring_feedback_notifications.rb:5 — db/migrate/20261107160000_add_hiring_feedback_notifications.rb:5-15 | db/migrate/20261107180000_add_hiring_decision_messages.rb:5-17 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (11 corresponding lines) app/services/analytics/exports/pdf_service.rb:21 — app/services/analytics/exports/pdf_service.rb:21-31 | app/services/pdf_generation/invoice_service.rb:88-98 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Duplicated block (9 lines × 2) · ×2
  • Duplicated block (9 lines × 2) app/controllers/api/v1/employee_record_admin_controller.rb:28 — app/controllers/api/v1/employee_record_admin_controller.rb:28-36 | app/controllers/api/v1/employee_records_controller.rb:137-145 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (9 lines × 2) app/controllers/api/v1/mobile/collections_controller.rb:392 — app/controllers/api/v1/mobile/collections_controller.rb:392-400 | app/services/mobile_otp/login_challenge.rb:163-171 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (6 lines × 2) · ×2
  • Duplicated block (6 lines × 2) app/controllers/api/v1/hiring/assignments_controller.rb:53 — app/controllers/api/v1/hiring/assignments_controller.rb:53-58 | app/controllers/api/v1/hiring/interviews_controller.rb:33-38 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `app/controllers/api/v1/hiring/assignments_controller.rb:50` calls `service` and `app/controllers/api/v1/hiring/interviews_controller.rb:30` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (6 lines × 2) app/services/mobile_otp/challenge_token.rb:17 — app/services/mobile_otp/challenge_token.rb:17-22 | app/services/passkeys/challenge_token.rb:14-19 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
D4 · Code Duplication · Duplicated block (8 lines × 2) · ×2
  • Duplicated block (8 lines × 2) app/controllers/api/v1/mobile/otps_controller.rb:12 — app/controllers/api/v1/mobile/otps_controller.rb:12-19 | app/controllers/api/v1/users/otps_controller.rb:15-22 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (8 lines × 2) app/models/invoice_tax.rb:22 — app/models/invoice_tax.rb:22-29 | app/models/tax_configuration.rb:20-27 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
D4 · Code Duplication · Duplicated block (12 lines × 2) · ×2
  • Duplicated block (12 lines × 2) app/services/analytics/client_revenue_analytics.rb:143 — app/services/analytics/client_revenue_analytics.rb:143-154 | app/services/analytics/expense_trend_analyzer.rb:120-131 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (12 lines × 2) tools/miru-cli/cmd/miru/main.go:1089 — tools/miru-cli/cmd/miru/main.go:1089-1100 | tools/miru-cli/cmd/miru/main.go:1127-1138 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
R10 · Code Duplication · Duplicated block with local edits (85 matched lines × 2 locations) · ×2
  • Duplicated block with local edits (85 matched lines × 2 locations) app/javascript/src/components/Hiring/InterviewFeedback.tsx:413 — app/javascript/src/components/Hiring/InterviewFeedback.tsx:413 · app/javascript/src/components/Hiring/InterviewReviews.tsx:310 — the two spans are one implementation copied and then locally edited — 354 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
  • Duplicated block with local edits (85 matched lines × 2 locations) app/javascript/src/components/Hiring/ReceiptDetail.tsx:40 — app/javascript/src/components/Hiring/ReceiptDetail.tsx:40 · app/javascript/src/components/Hiring/Settings.tsx:35 — the two spans are one implementation copied and then locally edited — 433 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 (83 matched lines × 2 locations) · ×2
  • Duplicated block with local edits (83 matched lines × 2 locations) app/javascript/src/components/Hiring/AssignmentLibrary.tsx:47 — app/javascript/src/components/Hiring/AssignmentLibrary.tsx:47 · app/javascript/src/components/Hiring/Roles.tsx:100 — the two spans are one implementation copied and then locally edited — 410 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
  • Duplicated block with local edits (83 matched lines × 2 locations) app/javascript/src/components/ui/dialog.tsx:8 — app/javascript/src/components/ui/dialog.tsx:8 · app/javascript/src/components/ui/sheet.tsx:7 — the two spans are one implementation copied and then locally edited — 438 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.
R11 · Import Boundaries · Boundary violation [package · ×2
  • Boundary violation [package:third-party-deep-import] app/javascript/src/components/DocumentSignatures/PdfPages.tsx:9 — app/javascript/src/components/DocumentSignatures/PdfPages.tsx:9 imports pdfjs-dist/build/pdf.worker.min.mjs?url, 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:relative-cross-package] app/javascript/src/components/DocumentSignatures/pdfResources.ts:3 — app/javascript/src/components/DocumentSignatures/pdfResources.ts:3 reaches into another package with a relative path (../../../../../node_modules/pdfjs-dist/{cmaps/*,standard_fonts/*,wasm/*,LICENSE}) — import the package by name instead.
R7 · Dead Code · Dead file (~361 LoC) · ×2
  • Dead file (~361 LoC) app/javascript/src/components/Hiring/Portal.tsx — no import path from any entry point (128 application, 14 tooling, 6 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (app/javascript/entrypoints/hiring_form.ts) — 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 (~361 LoC) app/javascript/src/components/Profile/Organization/Edit/Page.tsx — no import path from any entry point (128 application, 14 tooling, 6 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 (~303 LoC) · ×2
  • Dead file (~303 LoC) app/javascript/src/components/Invoices/List/RecentlyUpdated/InfiniteScrollRecentlyUpdated.tsx — no import path from any entry point (128 application, 14 tooling, 6 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (app/javascript/src/components/Invoices/AdminDashboard/index.tsx, app/javascript/src/components/Invoices/List/InvoiceListContent.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 (~303 LoC) app/javascript/src/components/Invoices/List/Table/TableRow.tsx — no import path from any entry point (128 application, 14 tooling, 6 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (app/javascript/src/components/Invoices/List/Table/InvoiceListTable.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 (~267 LoC) · ×2
  • Dead file (~267 LoC) app/javascript/src/components/Invoices/List/MoreOptions.tsx — no import path from any entry point (128 application, 14 tooling, 6 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (app/javascript/src/components/Invoices/List/Table/TableRow.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 (~267 LoC) app/javascript/src/components/Invoices/common/SendInvoiceContainer/index.tsx — no import path from any entry point (128 application, 14 tooling, 6 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (app/javascript/src/components/Invoices/List/Table/TableRow.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 (~205 LoC) · ×2
  • Dead file (~205 LoC) app/javascript/src/components/Hiring/PortalField.tsx — no import path from any entry point (128 application, 14 tooling, 6 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (app/javascript/src/components/Hiring/AssessmentPortal.tsx, app/javascript/src/components/Hiring/Portal.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 (~205 LoC) app/javascript/src/components/TimesheetEntries/TimeEntryForm/DesktopTimeEntryForm.tsx — no import path from any entry point (128 application, 14 tooling, 6 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (app/javascript/src/components/TimesheetEntries/TimeEntryForm/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 (~184 LoC) · ×2
  • Dead file (~184 LoC) app/javascript/src/components/Team/modals/TeamForm.tsx — no import path from any entry point (128 application, 14 tooling, 6 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (app/javascript/src/components/Team/modals/AddEditMember.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 (~184 LoC) app/javascript/src/components/TimeoffEntries/EntryCard/index.tsx — no import path from any entry point (128 application, 14 tooling, 6 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (app/javascript/src/components/TimeoffEntries/TimeoffEntryManager/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 (~182 LoC) · ×2
  • Dead file (~182 LoC) app/javascript/src/components/Invoices/common/InvoiceDetails/ClientSelection.tsx — no import path from any entry point (128 application, 14 tooling, 6 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (app/javascript/src/components/Invoices/common/InvoiceDetails/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 (~182 LoC) app/javascript/src/components/Reports/Filters/SidebarTeamMembersFilter.tsx — no import path from any entry point (128 application, 14 tooling, 6 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (app/javascript/src/components/Reports/Filters/Sidebar.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
X17 · Uncapped recursion over a caller-supplied document · Recursive walk over a caller-supplied document has no depth cap · ×2
  • Recursive walk over a caller-supplied document has no depth cap app/services/payroll_calculation/values.rb:39 — `immutable` is public and takes `value` — which it walks as a `Hash` — from its caller, and it calls itself at line 39 (`self.immutable`) with a piece of `value` (and at line 40) — and nowhere in `immutable` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends stack per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. A walk like this one raises `SystemStackError` past about 3,800 levels on the main thread and about 1,000 on a `Thread` — where Puma serves requests and Sidekiq runs jobs (MRI 3.3 and 4.0). `JSON.parse` stops at 100 levels by default, but the other parsers a caller may use do not: `YAML.safe_load` builds 1,400 levels from 2.8 KB, `Oj.load` 100,000, REXML 200,000, and `JSON.load` on json 2.7 (Ruby 3.3's default) or `JSON.parse(…, max_nesting: false)` 58,000. `SystemStackError` is not a `StandardError`: a bare `rescue` or `rescue => e` around the call does not stop it. Thread a depth argument through `immutable` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
  • Recursive walk over a caller-supplied document has no depth cap app/services/payroll/india_handoff.rb:20 — `line_digest` is public, takes a document from its caller (line 7) and hands it to `canonical`, which walks `value` as a `Hash` and calls itself at line 20 (`self.canonical`) with a piece of `value` (and at line 21) — and nowhere in `canonical` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends stack per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. A walk like this one raises `SystemStackError` past about 3,800 levels on the main thread and about 1,000 on a `Thread` — where Puma serves requests and Sidekiq runs jobs (MRI 3.3 and 4.0). `JSON.parse` stops at 100 levels by default, but the other parsers a caller may use do not: `YAML.safe_load` builds 1,400 levels from 2.8 KB, `Oj.load` 100,000, REXML 200,000, and `JSON.load` on json 2.7 (Ruby 3.3's default) or `JSON.parse(…, max_nesting: false)` 58,000. `SystemStackError` is not a `StandardError`: a bare `rescue` or `rescue => e` around the call does not stop it. Thread a depth argument through `canonical` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
AC2 · Forms & labels · <AsyncSelect> field component without a label · ×1
  • <AsyncSelect> field component without a label app/javascript/src/common/CustomAsyncSelect/index.tsx:35 — 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.
AC3 · Page structure · Text directly inside a table row · ×1
  • Text directly inside a table row app/javascript/src/components/Invoices/List/Table/TableRow.tsx:109 — A <tr> may hold only <td>/<th> cells. Text or a value written between the cells is moved out of the table by the browser, so it is read detached from its row. Wrap it in a <td>.
AC3 · Page structure · Heading level jumps from h1 to h6 · ×1
  • Heading level jumps from h1 to h6 app/javascript/src/components/Subscriptions/PlanSelection/index.tsx:52 — Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
AC6 · Visual & motion safety · Low contrast Tailwind colour pair (3.8 · ×1
  • Low contrast Tailwind colour pair (3.8:1) app/javascript/src/components/Dashboard/DashboardTimerControl.tsx:252 — This element's Tailwind text/background colour utilities fall below the 4.5:1 WCAG AA minimum for normal text. Pick a darker or lighter shade.
AC6 · Visual & motion safety · Low contrast Tailwind colour pair (4.1 · ×1
  • Low contrast Tailwind colour pair (4.1:1) app/javascript/src/components/Dashboard/DashboardTimerControl.tsx:327 — This element's Tailwind text/background colour utilities fall below the 4.5:1 WCAG AA minimum for normal text. Pick a darker or lighter shade.
AC6 · Visual & motion safety · Low contrast Tailwind colour pair (1.5 · ×1
  • Low contrast Tailwind colour pair (1.5:1) app/javascript/src/components/payments/Success/index.tsx:53 — This element's Tailwind text/background colour utilities fall below the 4.5:1 WCAG AA minimum for normal text. Pick a darker or lighter shade.
AC6 · Visual & motion safety · Low contrast colour pair (3.1 · ×1
  • Low contrast colour pair (3.1:1) app/views/subscription_mailer/trial_pro_features.html.erb:31 — The inline foreground/background colours fall below the 4.5:1 WCAG AA minimum for normal text. Darken/lighten one of them.
D1 · Cyclomatic Complexity · index.InvoiceEditor (cyclomatic 167) · ×1
  • index.InvoiceEditor (cyclomatic 167) app/javascript/src/components/Invoices/InvoiceEditor/index.tsx:62 — index.InvoiceEditor has cyclomatic complexity 167 (threshold 15). Of this number, 76 points are the body's own statements and 91 belong to 34 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 · Page.OrganizationPaymentSettingsPage (cyclomatic 139) · ×1
  • Page.OrganizationPaymentSettingsPage (cyclomatic 139) app/javascript/src/components/Profile/Organization/Payment/Page.tsx:63 — Page.OrganizationPaymentSettingsPage has cyclomatic complexity 139 (threshold 15). Of this number, 53 points are the body's own statements and 86 belong to 23 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 · ExpensesTable.ExpensesTable (cyclomatic 118) · ×1
  • ExpensesTable.ExpensesTable (cyclomatic 118) app/javascript/src/components/Expenses/ExpensesTable.tsx:199 — ExpensesTable.ExpensesTable has cyclomatic complexity 118 (threshold 15). Of this number, 50 points are the body's own statements and 68 belong to 30 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 · DeliveryPanel.DeliveryPanel (cyclomatic 101) · ×1
  • DeliveryPanel.DeliveryPanel (cyclomatic 101) app/javascript/src/components/DocumentSignatures/DeliveryPanel.tsx:35 — DeliveryPanel.DeliveryPanel has cyclomatic complexity 101 (threshold 15). Of this number, 62 points are the body's own statements and 39 belong to 11 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 · index.Billing (cyclomatic 98) · ×1
  • index.Billing (cyclomatic 98) app/javascript/src/components/Profile/Organization/Billing/index.tsx:61 — index.Billing has cyclomatic complexity 98 (threshold 15). Of this number, 62 points are the body's own statements and 36 belong to 11 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 · Editor.Editor (cyclomatic 91) · ×1
  • Editor.Editor (cyclomatic 91) app/javascript/src/components/DocumentSignatures/Editor.tsx:30 — Editor.Editor has cyclomatic complexity 91 (threshold 15). Of this number, 38 points are the body's own statements and 53 belong to 17 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 · ReceiptDetail.ReceiptDetail (cyclomatic 89) · ×1
  • ReceiptDetail.ReceiptDetail (cyclomatic 89) app/javascript/src/components/Hiring/ReceiptDetail.tsx:21 — ReceiptDetail.ReceiptDetail has cyclomatic complexity 89 (threshold 15). Of this number, 49 points are the body's own statements and 40 belong to 8 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 · InvoiceApiService.transformApiInvoice (cyclomatic 85) · ×1
  • InvoiceApiService.transformApiInvoice (cyclomatic 85) app/javascript/src/services/invoiceApi.ts:435 — InvoiceApiService.transformApiInvoice has cyclomatic complexity 85 (threshold 15). Of this number, 55 points are the body's own statements and 30 belong to 3 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 · CandidateMessages.CandidateMessages (cyclomatic 84) · ×1
  • CandidateMessages.CandidateMessages (cyclomatic 84) app/javascript/src/components/Hiring/CandidateMessages.tsx:49 — CandidateMessages.CandidateMessages has cyclomatic complexity 84 (threshold 15). Of this number, 50 points are the body's own statements and 34 belong to 9 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 · TeamTable.TeamTable (cyclomatic 83) · ×1
  • TeamTable.TeamTable (cyclomatic 83) app/javascript/src/components/Team/TeamTable.tsx:102 — TeamTable.TeamTable has cyclomatic complexity 83 (threshold 15). Of this number, 32 points are the body's own statements and 51 belong to 24 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 · InterviewBookings.InterviewBookings (cyclomatic 81) · ×1
  • InterviewBookings.InterviewBookings (cyclomatic 81) app/javascript/src/components/Hiring/InterviewBookings.tsx:41 — InterviewBookings.InterviewBookings has cyclomatic complexity 81 (threshold 15). Of this number, 44 points are the body's own statements and 37 belong to 9 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 · index.Records (cyclomatic 80) · ×1
  • index.Records (cyclomatic 80) app/javascript/src/components/Profile/EmployeeRecords/index.tsx:44 — index.Records has cyclomatic complexity 80 (threshold 15). Of this number, 30 points are the body's own statements and 50 belong to 18 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 · Editor.LoadedEditor (cyclomatic 78) · ×1
  • Editor.LoadedEditor (cyclomatic 78) app/javascript/src/components/Agreements/Editor.tsx:27 — Editor.LoadedEditor has cyclomatic complexity 78 (threshold 15). Of this number, 27 points are the body's own statements and 51 belong to 19 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.InvoiceAuthorizationPanel (cyclomatic 78) · ×1
  • index.InvoiceAuthorizationPanel (cyclomatic 78) app/javascript/src/components/Profile/InvoiceAuthorization/index.tsx:20 — index.InvoiceAuthorizationPanel has cyclomatic complexity 78 (threshold 15). Of this number, 29 points are the body's own statements and 49 belong to 9 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 · RazorpayConnection.RazorpayConnection (cyclomatic 78) · ×1
  • RazorpayConnection.RazorpayConnection (cyclomatic 78) app/javascript/src/components/Profile/Organization/Payment/RazorpayConnection.tsx:104 — RazorpayConnection.RazorpayConnection has cyclomatic complexity 78 (threshold 15). Of this number, 39 points are the body's own statements and 39 belong to 14 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 · App.App (cyclomatic 78) · ×1
  • App.App (cyclomatic 78) apps/mobile/App.tsx:239 — App.App has cyclomatic complexity 78 (threshold 15). Of this number, 31 points are the body's own statements and 47 belong to 19 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 · EntryForm.AddEntry (cyclomatic 73) · ×1
  • EntryForm.AddEntry (cyclomatic 73) app/javascript/src/components/TimeTracking/EntryForm.tsx:32 — EntryForm.AddEntry has cyclomatic complexity 73 (threshold 15). Of this number, 25 points are the body's own statements and 48 belong to 16 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 · FloatingTimer.FloatingTimer (cyclomatic 73) · ×1
  • FloatingTimer.FloatingTimer (cyclomatic 73) app/javascript/src/components/TimesheetEntries/FloatingTimer.tsx:89 — FloatingTimer.FloatingTimer has cyclomatic complexity 73 (threshold 15). Of this number, 25 points are the body's own statements and 48 belong to 27 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.PaymentReport (cyclomatic 70) · ×1
  • index.PaymentReport (cyclomatic 70) app/javascript/src/components/Reports/PaymentReport/index.tsx:149 — index.PaymentReport has cyclomatic complexity 70 (threshold 15). Of this number, 37 points are the body's own statements and 33 belong to 18 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.
D1 · Cyclomatic Complexity · ApplicationForms.ApplicationForms (cyclomatic 69) · ×1
  • ApplicationForms.ApplicationForms (cyclomatic 69) app/javascript/src/components/Hiring/ApplicationForms.tsx:32 — ApplicationForms.ApplicationForms has cyclomatic complexity 69 (threshold 15). Of this number, 28 points are the body's own statements and 41 belong to 13 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.DeclarationWorkspace (cyclomatic 69) · ×1
  • index.DeclarationWorkspace (cyclomatic 69) app/javascript/src/components/TaxDeclarations/index.tsx:66 — index.DeclarationWorkspace has cyclomatic complexity 69 (threshold 15). Of this number, 42 points are the body's own statements and 27 belong to 14 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 · index.Holidays (cyclomatic 68) · ×1
  • index.Holidays (cyclomatic 68) app/javascript/src/components/Profile/Organization/Holidays/index.tsx:16 — index.Holidays has cyclomatic complexity 68 (threshold 15). Most of this is not in the body itself: 3 of the 68 points are its own statements and the rest belongs to 21 function items inside it that branch (a function literal at line 480, handleDatePicker, handleHolidateNameChange, …). 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.TimeEntryReport (cyclomatic 68) · ×1
  • index.TimeEntryReport (cyclomatic 68) app/javascript/src/components/Reports/TimeEntryReport/index.tsx:258 — index.TimeEntryReport has cyclomatic complexity 68 (threshold 15). Of this number, 29 points are the body's own statements and 39 belong to 19 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 · index.TimeoffForm (cyclomatic 66) · ×1
  • index.TimeoffForm (cyclomatic 66) app/javascript/src/components/TimeoffEntries/TimeoffForm/index.tsx:18 — index.TimeoffForm has cyclomatic complexity 66 (threshold 15). Most of this is not in the body itself: 2 of the 66 points are its own statements and the rest belongs to 19 function items inside it that branch (handleFillData, getPayload, a function literal at line 56, …). 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 · Onboarding.Onboarding (cyclomatic 65) · ×1
  • Onboarding.Onboarding (cyclomatic 65) app/javascript/src/components/Hiring/Onboarding.tsx:61 — Onboarding.Onboarding has cyclomatic complexity 65 (threshold 15). Of this number, 40 points are the body's own statements and 25 belong to 7 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 · index.PayrollWorkspace (cyclomatic 65) · ×1
  • index.PayrollWorkspace (cyclomatic 65) app/javascript/src/components/ConsultantPayroll/index.tsx:108 — index.PayrollWorkspace has cyclomatic complexity 65 (threshold 15). Of this number, 39 points are the body's own statements and 26 belong to 16 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 · ApplicationInterviews.ApplicationInterviews (cyclomatic 65) · ×1
  • ApplicationInterviews.ApplicationInterviews (cyclomatic 65) app/javascript/src/components/Hiring/ApplicationInterviews.tsx:41 — ApplicationInterviews.ApplicationInterviews has cyclomatic complexity 65 (threshold 15). Of this number, 33 points are the body's own statements and 32 belong to 14 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 · InvoiceList.InvoiceList (cyclomatic 64) · ×1
  • InvoiceList.InvoiceList (cyclomatic 64) app/javascript/src/components/Invoices/InvoiceList.tsx:78 — InvoiceList.InvoiceList has cyclomatic complexity 64 (threshold 15). Of this number, 33 points are the body's own statements and 31 belong to 11 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 · ApplicationAssignments.ApplicationAssignments (cyclomatic 61) · ×1
  • ApplicationAssignments.ApplicationAssignments (cyclomatic 61) app/javascript/src/components/Hiring/ApplicationAssignments.tsx:63 — ApplicationAssignments.ApplicationAssignments has cyclomatic complexity 61 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators. This shape REPEATS in the file: one other method here (ApplicationAssignments.ApplicationAssignments::save) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D1 · Cyclomatic Complexity · index.BillingIdentityPanel (cyclomatic 60) · ×1
  • index.BillingIdentityPanel (cyclomatic 60) app/javascript/src/components/Profile/BillingIdentity/index.tsx:61 — index.BillingIdentityPanel has cyclomatic complexity 60 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators. This shape REPEATS in the file: one other method here (index.BillingIdentityPanel::failed) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D1 · Cyclomatic Complexity · WorkspaceView.OutstandingInvoicesWorkspaceView (cyclomatic 60) · ×1
  • WorkspaceView.OutstandingInvoicesWorkspaceView (cyclomatic 60) app/javascript/src/components/Reports/OutstandingInvoiceReport/WorkspaceView.tsx:191 — WorkspaceView.OutstandingInvoicesWorkspaceView has cyclomatic complexity 60 (threshold 15). Of this number, 31 points are the body's own statements and 29 belong to 18 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 · ApplicationDecisions.ApplicationDecisions (cyclomatic 59) · ×1
  • ApplicationDecisions.ApplicationDecisions (cyclomatic 59) app/javascript/src/components/Hiring/ApplicationDecisions.tsx:71 — ApplicationDecisions.ApplicationDecisions has cyclomatic complexity 59 (threshold 15). Of this number, 31 points are the body's own statements and 28 belong to 9 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 · ClientEditor.ClientEditor (cyclomatic 58) · ×1
  • ClientEditor.ClientEditor (cyclomatic 58) app/javascript/src/components/Clients/ClientForm/ClientEditor.tsx:37 — ClientEditor.ClientEditor has cyclomatic complexity 58 (threshold 15). Most of this is not in the body itself: 1 of the 58 points is its own statement and the rest belongs to 5 function items inside it that branch (a function literal at line 108, handleSubmit, a function literal at line 58, …). 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 · PaymentsTable.PaymentsTable (cyclomatic 58) · ×1
  • PaymentsTable.PaymentsTable (cyclomatic 58) app/javascript/src/components/payments/PaymentsTable.tsx:106 — PaymentsTable.PaymentsTable has cyclomatic complexity 58 (threshold 15). Of this number, 20 points are the body's own statements and 38 belong to 18 function items inside it that branch. To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
D1 · Cyclomatic Complexity · Editor.OrganizationHolidaysEditor (cyclomatic 56) · ×1
  • Editor.OrganizationHolidaysEditor (cyclomatic 56) app/javascript/src/components/Profile/Organization/Holidays/Editor.tsx:85 — Editor.OrganizationHolidaysEditor has cyclomatic complexity 56 (threshold 15). Of this number, 40 points are the body's own statements and 16 belong to 9 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 · animated-time-input.AnimatedTimeInput (cyclomatic 56) · ×1
  • animated-time-input.AnimatedTimeInput (cyclomatic 56) app/javascript/src/components/ui/animated-time-input.tsx:98 — animated-time-input.AnimatedTimeInput has cyclomatic complexity 56 (threshold 15). Of this number, 19 points are the body's own statements and 37 belong to 12 function items inside it that branch. To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
D1 · Cyclomatic Complexity · ApplicationOffers.ApplicationOffers (cyclomatic 54) · ×1
  • ApplicationOffers.ApplicationOffers (cyclomatic 54) app/javascript/src/components/Hiring/ApplicationOffers.tsx:74 — ApplicationOffers.ApplicationOffers has cyclomatic complexity 54 (threshold 15). Of this number, 26 points are the body's own statements and 28 belong to 10 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 · enhanced-search.UnifiedSearch (cyclomatic 54) · ×1
  • enhanced-search.UnifiedSearch (cyclomatic 54) REDACTED:321 — enhanced-search.UnifiedSearch has cyclomatic complexity 54 (threshold 15). Of this number, 32 points are the body's own statements and 22 belong to 11 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 · index.InvoicesPage (cyclomatic 54) · ×1
  • index.InvoicesPage (cyclomatic 54) app/javascript/src/components/Invoices/index.tsx:38 — index.InvoicesPage has cyclomatic complexity 54 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions. This shape REPEATS in the file: one other method here (index.InvoicesPage::handleInvoiceAction) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D1 · Cyclomatic Complexity · MobileProfileEditor.MobileProfileEditor (cyclomatic 54) · ×1
  • MobileProfileEditor.MobileProfileEditor (cyclomatic 54) app/javascript/src/components/Profile/Personal/User/Edit/MobileProfileEditor.tsx:30 — MobileProfileEditor.MobileProfileEditor has cyclomatic complexity 54 (threshold 15). Of this number, 52 points are the body's own statements and 2 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 · index.CompanyDetailsForm (cyclomatic 53) · ×1
  • index.CompanyDetailsForm (cyclomatic 53) app/javascript/src/components/OrganizationSetup/CompanyDetailsForm/index.tsx:28 — index.CompanyDetailsForm has cyclomatic complexity 53 (threshold 15). Most of this is not in the body itself: 2 of the 53 points are its own statements and the rest belongs to 8 function items inside it that branch (a function literal at line 219, onLogoChange, a function literal at line 66, …). 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.SalarySlipArchive (cyclomatic 53) · ×1
  • index.SalarySlipArchive (cyclomatic 53) app/javascript/src/components/SalarySlips/index.tsx:36 — index.SalarySlipArchive has cyclomatic complexity 53 (threshold 15). Of this number, 27 points are the body's own statements and 26 belong to 13 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 · index.InvoicePreview (cyclomatic 51) · ×1
  • index.InvoicePreview (cyclomatic 51) app/javascript/src/components/Invoices/InvoicePreview/index.tsx:90 — index.InvoicePreview has cyclomatic complexity 51 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators. This shape REPEATS in the file: one other method here (index.InvoicePreview::handleSendSubmit) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D1 · Cyclomatic Complexity · index.FilterSidebar (cyclomatic 51) · ×1
  • index.FilterSidebar (cyclomatic 51) app/javascript/src/components/Invoices/List/FilterSideBar/index.tsx:22 — index.FilterSidebar has cyclomatic complexity 51 (threshold 15). Of this number, 18 points are the body's own statements and 33 belong to 12 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.RevenueByClientReportFilters (cyclomatic 51) · ×1
  • index.RevenueByClientReportFilters (cyclomatic 51) app/javascript/src/components/Reports/RevenueByClientReport/Filters/index.tsx:19 — index.RevenueByClientReportFilters has cyclomatic complexity 51 (threshold 15). Most of this is not in the body itself: 8 of the 51 points are its own statements and the rest belongs to 16 function items inside it that branch (a function literal at line 80, handleSelectFilter, a function literal at line 241, …). 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 · Settings.Settings (cyclomatic 50) · ×1
  • Settings.Settings (cyclomatic 50) app/javascript/src/components/Hiring/Settings.tsx:25 — Settings.Settings has cyclomatic complexity 50 (threshold 15). Of this number, 32 points are the body's own statements and 18 belong to 8 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 · index.Invoices (cyclomatic 50) · ×1
  • index.Invoices (cyclomatic 50) app/javascript/src/components/Invoices/List/index.tsx:24 — index.Invoices has cyclomatic complexity 50 (threshold 15). Most of this is not in the body itself: 5 of the 50 points are its own statements and the rest belongs to 12 function items inside it that branch (fetchPaymentSettings, loadInvoices, InvoicesLayout, …). 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 · PaymentEntryForm.PaymentEntryForm (cyclomatic 50) · ×1
  • PaymentEntryForm.PaymentEntryForm (cyclomatic 50) app/javascript/src/components/payments/Modals/PaymentEntryForm.tsx:31 — PaymentEntryForm.PaymentEntryForm has cyclomatic complexity 50 (threshold 15). Most of this is not in the body itself: 4 of the 50 points are its own statements and the rest belongs to 10 function items inside it that branch (a function literal at line 159, a function literal at line 198, isAddPaymentBtnActive, …). 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 · DashboardHome.DashboardHome (cyclomatic 49) · ×1
  • DashboardHome.DashboardHome (cyclomatic 49) app/javascript/src/components/Dashboard/DashboardHome.tsx:33 — DashboardHome.DashboardHome has cyclomatic complexity 49 (threshold 15). Of this number, 26 points are the body's own statements and 23 belong to 8 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 · CalendarBooking.CalendarBooking (cyclomatic 48) · ×1
  • CalendarBooking.CalendarBooking (cyclomatic 48) app/javascript/src/components/Hiring/CalendarBooking.tsx:39 — CalendarBooking.CalendarBooking has cyclomatic complexity 48 (threshold 15). Of this number, 23 points are the body's own statements and 25 belong to 6 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 · index.RevenueByClientReport (cyclomatic 48) · ×1
  • index.RevenueByClientReport (cyclomatic 48) app/javascript/src/components/Reports/RevenueByClientReport/index.tsx:150 — index.RevenueByClientReport has cyclomatic complexity 48 (threshold 15). Of this number, 26 points are the body's own statements and 22 belong to 13 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.
D1 · Cyclomatic Complexity · Portal.Portal (cyclomatic 46) · ×1
  • Portal.Portal (cyclomatic 46) app/javascript/src/components/Hiring/Portal.tsx:22 — Portal.Portal has cyclomatic complexity 46 (threshold 15). Of this number, 18 points are the body's own statements and 28 belong to 12 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 · PtoPanel.PtoPanel (cyclomatic 46) · ×1
  • PtoPanel.PtoPanel (cyclomatic 46) app/javascript/src/components/Payroll/PtoPanel.tsx:279 — PtoPanel.PtoPanel has cyclomatic complexity 46 (threshold 15). Of this number, 34 points are the body's own statements and 12 belong to 9 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 · Review.Review (cyclomatic 46) · ×1
  • Review.Review (cyclomatic 46) app/javascript/src/components/Payroll/Review.tsx:405 — Review.Review has cyclomatic complexity 46 (threshold 15). Of this number, 27 points are the body's own statements and 19 belong to 3 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.
D1 · Cyclomatic Complexity · PdfPages.PdfPages (cyclomatic 45) · ×1
  • PdfPages.PdfPages (cyclomatic 45) app/javascript/src/components/DocumentSignatures/PdfPages.tsx:36 — PdfPages.PdfPages has cyclomatic complexity 45 (threshold 15). Most of this is not in the body itself: 11 of the 45 points are its own statements and the rest belongs to 13 function items inside it that branch (a function literal at line 126, a function literal at line 346, move, …). 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 · AssessmentPortal.AssessmentPortal (cyclomatic 45) · ×1
  • AssessmentPortal.AssessmentPortal (cyclomatic 45) app/javascript/src/components/Hiring/AssessmentPortal.tsx:32 — AssessmentPortal.AssessmentPortal has cyclomatic complexity 45 (threshold 15). Of this number, 19 points are the body's own statements and 26 belong to 11 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 · Picker.Picker (cyclomatic 45) · ×1
  • Picker.Picker (cyclomatic 45) app/javascript/src/components/Hiring/Picker.tsx:34 — Picker.Picker has cyclomatic complexity 45 (threshold 15). Most of this is not in the body itself: 12 of the 45 points are its own statements and the rest belongs to 10 function items inside it that branch (a function literal at line 105, a function literal at line 85, a function literal at line 78, …). 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.ChartWithSummary (cyclomatic 45) · ×1
  • index.ChartWithSummary (cyclomatic 45) app/javascript/src/components/Invoices/ChartWithSummary/index.tsx:34 — index.ChartWithSummary has cyclomatic complexity 45 (threshold 15). Most of this is not in the body itself: 9 of the 45 points are its own statements and the rest belongs to 10 function items inside it that branch (a function literal at line 87, a function literal at line 149, parseNumber, …). 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.CustomDateRangeWithInput (cyclomatic 44) · ×1
  • index.CustomDateRangeWithInput (cyclomatic 44) app/javascript/src/common/CustomDateRangeWIthInput/index.tsx:32 — index.CustomDateRangeWithInput has cyclomatic complexity 44 (threshold 15). Most of this is not in the body itself: 14 of the 44 points are its own statements and the rest belongs to 7 function items inside it that branch (checkIsValidDateRange, validateDateInput, setValidDate, …). 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 · InterviewPanel.InterviewPanel (cyclomatic 44) · ×1
  • InterviewPanel.InterviewPanel (cyclomatic 44) app/javascript/src/components/Hiring/InterviewPanel.tsx:20 — InterviewPanel.InterviewPanel has cyclomatic complexity 44 (threshold 15). Of this number, 24 points are the body's own statements and 20 belong to 8 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 · Sidebar.Sidebar (cyclomatic 44) · ×1
  • Sidebar.Sidebar (cyclomatic 44) app/javascript/src/components/Navbar/Sidebar.tsx:63 — Sidebar.Sidebar has cyclomatic complexity 44 (threshold 15). Of this number, 25 points are the body's own statements and 19 belong to 5 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 · ProfileEditor.ProfileEditor (cyclomatic 44) · ×1
  • ProfileEditor.ProfileEditor (cyclomatic 44) app/javascript/src/components/Profile/Personal/User/Edit/ProfileEditor.tsx:32 — ProfileEditor.ProfileEditor has cyclomatic complexity 44 (threshold 15). Of this number, 43 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 · index.PreferencesSettingsPage (cyclomatic 44) · ×1
  • index.PreferencesSettingsPage (cyclomatic 44) app/javascript/src/components/Settings/Preferences/index.tsx:51 — index.PreferencesSettingsPage has cyclomatic complexity 44 (threshold 15). Most of this is not in the body itself: 7 of the 44 points are its own statements and the rest belongs to 15 function items inside it that branch (fetchPreferences, a function literal at line 426, a function literal at line 208, …). 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 · ReviewPanel.ReviewPanel (cyclomatic 43) · ×1
  • ReviewPanel.ReviewPanel (cyclomatic 43) app/javascript/src/components/DocumentSignatures/ReviewPanel.tsx:10 — ReviewPanel.ReviewPanel has cyclomatic complexity 43 (threshold 15). Of this number, 27 points are the body's own statements and 16 belong to 5 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 · ApplicationScreening.ApplicationScreening (cyclomatic 42) · ×1
  • ApplicationScreening.ApplicationScreening (cyclomatic 42) app/javascript/src/components/Hiring/ApplicationScreening.tsx:55 — ApplicationScreening.ApplicationScreening has cyclomatic complexity 42 (threshold 15). Of this number, 25 points are the body's own statements and 17 belong to 6 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 · OrgEditForm.OrgEditForm (cyclomatic 42) · ×1
  • OrgEditForm.OrgEditForm (cyclomatic 42) app/javascript/src/components/Profile/Organization/Edit/OrgEditForm.tsx:127 — OrgEditForm.OrgEditForm has cyclomatic complexity 42 (threshold 15). Of this number, 37 points are the body's own statements and 5 belong to 5 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.
D1 · Cyclomatic Complexity · Sidebar.ReportFiltersPanel (cyclomatic 42) · ×1
  • Sidebar.ReportFiltersPanel (cyclomatic 42) app/javascript/src/components/Reports/Filters/Sidebar.tsx:31 — Sidebar.ReportFiltersPanel has cyclomatic complexity 42 (threshold 15). Most of this is not in the body itself: 4 of the 42 points are its own statements and the rest belongs to 13 function items inside it that branch (getActiveFilterCount, a function literal at line 131, a function literal at line 173, …). 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.CustomDateRangePicker (cyclomatic 41) · ×1
  • index.CustomDateRangePicker (cyclomatic 41) app/javascript/src/common/CustomDateRangePicker/index.tsx:16 — index.CustomDateRangePicker has cyclomatic complexity 41 (threshold 15). Most of this is not in the body itself: 5 of the 41 points are its own statements and the rest belongs to 8 function items inside it that branch (checkIsValidDateRange, validateDateInput, a function literal at line 213, …). 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 · ExpenseTrendsPage.ExpenseTrendsPage (cyclomatic 41) · ×1
  • ExpenseTrendsPage.ExpenseTrendsPage (cyclomatic 41) app/javascript/src/components/Analytics/ExpenseTrendsPage.tsx:54 — ExpenseTrendsPage.ExpenseTrendsPage has cyclomatic complexity 41 (threshold 15). Of this number, 34 points are the body's own statements and 7 belong to 6 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.
D1 · Cyclomatic Complexity · DashboardTimerControl.DashboardTimerControl (cyclomatic 41) · ×1
  • DashboardTimerControl.DashboardTimerControl (cyclomatic 41) app/javascript/src/components/Dashboard/DashboardTimerControl.tsx:42 — DashboardTimerControl.DashboardTimerControl has cyclomatic complexity 41 (threshold 15). Of this number, 23 points are the body's own statements and 18 belong to 12 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 · AssignmentReviews.ReviewDetail (cyclomatic 41) · ×1
  • AssignmentReviews.ReviewDetail (cyclomatic 41) app/javascript/src/components/Hiring/AssignmentReviews.tsx:36 — AssignmentReviews.ReviewDetail has cyclomatic complexity 41 (threshold 15). Of this number, 20 points are the body's own statements and 21 belong to 8 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 · index.AccountsAgingReport (cyclomatic 41) · ×1
  • index.AccountsAgingReport (cyclomatic 41) app/javascript/src/components/Reports/AccountsAgingReport/index.tsx:105 — index.AccountsAgingReport has cyclomatic complexity 41 (threshold 15). Of this number, 20 points are the body's own statements and 21 belong to 15 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.
D1 · Cyclomatic Complexity · AppWithUserData.AppWithUserData (cyclomatic 40) · ×1
  • AppWithUserData.AppWithUserData (cyclomatic 40) app/javascript/src/components/AppWithUserData.tsx:104 — AppWithUserData.AppWithUserData has cyclomatic complexity 40 (threshold 15). Most of this is not in the body itself: 7 of the 40 points are its own statements and the rest belongs to 9 function items inside it that branch (a function literal at line 148, a function literal at line 283, a function literal at line 118, …). 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.FinancialDetailsForm (cyclomatic 38) · ×1
  • index.FinancialDetailsForm (cyclomatic 38) app/javascript/src/components/OrganizationSetup/FinancialDetailsForm/index.tsx:25 — index.FinancialDetailsForm has cyclomatic complexity 38 (threshold 15). Most of this is not in the body itself: 2 of the 38 points are its own statements and the rest belongs to 5 function items inside it that branch (a function literal at line 64, isBtnDisabled, a function literal at line 76, …). 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 · ClientInsightsPage.ClientInsightsPage (cyclomatic 37) · ×1
  • ClientInsightsPage.ClientInsightsPage (cyclomatic 37) app/javascript/src/components/Analytics/ClientInsightsPage.tsx:52 — ClientInsightsPage.ClientInsightsPage has cyclomatic complexity 37 (threshold 15). Of this number, 33 points are the body's own statements and 4 belong to 4 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.
D1 · Cyclomatic Complexity · AssignmentTemplateEditor.AssignmentTemplateEditor (cyclomatic 37) · ×1
  • AssignmentTemplateEditor.AssignmentTemplateEditor (cyclomatic 37) app/javascript/src/components/Hiring/AssignmentTemplateEditor.tsx:31 — AssignmentTemplateEditor.AssignmentTemplateEditor has cyclomatic complexity 37 (threshold 15). Most of this is not in the body itself: 12 of the 37 points are its own statements and the rest belongs to 13 function items inside it that branch (save, a function literal at line 384, a function literal at line 67, …). 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 · InfiniteScrollRecentlyUpdated.InfiniteScrollRecentlyUpdated (cyclomatic 37) · ×1
  • InfiniteScrollRecentlyUpdated.InfiniteScrollRecentlyUpdated (cyclomatic 37) app/javascript/src/components/Invoices/List/RecentlyUpdated/InfiniteScrollRecentlyUpdated.tsx:25 — InfiniteScrollRecentlyUpdated.InfiniteScrollRecentlyUpdated has cyclomatic complexity 37 (threshold 15). Most of this is not in the body itself: 14 of the 37 points are its own statements and the rest belongs to 7 function literals inside it that branch (lines 71, 54, 42, …). 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 · ProjectsTable.ProjectsTable (cyclomatic 37) · ×1
  • ProjectsTable.ProjectsTable (cyclomatic 37) app/javascript/src/components/Projects/ProjectsTable.tsx:66 — ProjectsTable.ProjectsTable has cyclomatic complexity 37 (threshold 15). Most of this is not in the body itself: 13 of the 37 points are its own statements and the rest belongs to 15 function items inside it that branch (getStatusIcon, getStatusBadge, handleEdit, …). 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 · MobileEntryForm.AddEntryMobile (cyclomatic 37) · ×1
  • MobileEntryForm.AddEntryMobile (cyclomatic 37) app/javascript/src/components/TimeTracking/MobileView/MobileEntryForm.tsx:30 — MobileEntryForm.AddEntryMobile has cyclomatic complexity 37 (threshold 15). Of this number, 26 points are the body's own statements and 11 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 · LeaveManagementContent.LeaveManagementContent (cyclomatic 36) · ×1
  • LeaveManagementContent.LeaveManagementContent (cyclomatic 36) app/javascript/src/components/LeaveManagement/LeaveManagementContent.tsx:45 — LeaveManagementContent.LeaveManagementContent has cyclomatic complexity 36 (threshold 15). Of this number, 16 points are the body's own statements and 20 belong to 9 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 · MobileEntryForm.AddEntryMobile (cyclomatic 36) · ×1
  • MobileEntryForm.AddEntryMobile (cyclomatic 36) app/javascript/src/components/TimesheetEntries/TimeEntryForm/MobileEntryForm.tsx:29 — MobileEntryForm.AddEntryMobile has cyclomatic complexity 36 (threshold 15). Of this number, 24 points are the body's own statements and 12 belong to 8 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 · ExpenseForm.ExpenseForm (cyclomatic 35) · ×1
  • ExpenseForm.ExpenseForm (cyclomatic 35) app/javascript/src/components/Expenses/Modals/ExpenseForm.tsx:35 — ExpenseForm.ExpenseForm has cyclomatic complexity 35 (threshold 15). Of this number, 19 points are the body's own statements and 16 belong to 8 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 · InterviewFeedback.FeedbackForm (cyclomatic 35) · ×1
  • InterviewFeedback.FeedbackForm (cyclomatic 35) app/javascript/src/components/Hiring/InterviewFeedback.tsx:47 — InterviewFeedback.FeedbackForm has cyclomatic complexity 35 (threshold 15). Of this number, 18 points are the body's own statements and 17 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 · MercuryPayments.Leg (cyclomatic 35) · ×1
  • MercuryPayments.Leg (cyclomatic 35) app/javascript/src/components/Payroll/MercuryPayments.tsx:540 — MercuryPayments.Leg has cyclomatic complexity 35 (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 · Pipeline.Pipeline (cyclomatic 34) · ×1
  • Pipeline.Pipeline (cyclomatic 34) app/javascript/src/components/Hiring/Pipeline.tsx:56 — Pipeline.Pipeline has cyclomatic complexity 34 (threshold 15). Most of this is not in the body itself: 11 of the 34 points are its own statements and the rest belongs to 7 function literals inside it that branch (lines 231, 82, 150, …). 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 · AccountSecurity.AccountSecurity (cyclomatic 34) · ×1
  • AccountSecurity.AccountSecurity (cyclomatic 34) app/javascript/src/components/Profile/Personal/User/AccountSecurity.tsx:28 — AccountSecurity.AccountSecurity has cyclomatic complexity 34 (threshold 15). Of this number, 19 points are the body's own statements and 15 belong to 9 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 · PortalField.PortalField (cyclomatic 33) · ×1
  • PortalField.PortalField (cyclomatic 33) app/javascript/src/components/Hiring/PortalField.tsx:19 — PortalField.PortalField has cyclomatic complexity 33 (threshold 15). Of this number, 30 points are the body's own statements and 3 belong to 3 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 · index.Filters (cyclomatic 33) · ×1
  • index.Filters (cyclomatic 33) app/javascript/src/components/Invoices/MultipleEntriesModal/Filters/index.tsx:19 — index.Filters has cyclomatic complexity 33 (threshold 15). Most of this is not in the body itself: 10 of the 33 points are its own statements and the rest belongs to 10 function items inside it that branch (a function literal at line 52, a function literal at line 43, handleSelectFilter, …). 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.OrgEdit (cyclomatic 33) · ×1
  • index.OrgEdit (cyclomatic 33) app/javascript/src/components/Profile/Organization/Edit/index.tsx:146 — index.OrgEdit has cyclomatic complexity 33 (threshold 15). Most of this is not in the body itself: 2 of the 33 points are its own statements and the rest belongs to 7 function items inside it that branch (getData, updateOrgDetails, a function literal at line 164, …). 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 · FilterSideBar.TimeEntryReportFilterSidebar (cyclomatic 33) · ×1
  • FilterSideBar.TimeEntryReportFilterSidebar (cyclomatic 33) app/javascript/src/components/Reports/Filters/FilterSideBar.tsx:20 — FilterSideBar.TimeEntryReportFilterSidebar has cyclomatic complexity 33 (threshold 15). Most of this is not in the body itself: 2 of the 33 points are its own statements and the rest belongs to 12 function items inside it that branch (a function literal at line 104, a function literal at line 149, handleSelectFilter, …). 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 · DashboardLayout.DashboardLayout (cyclomatic 32) · ×1
  • DashboardLayout.DashboardLayout (cyclomatic 32) app/javascript/src/components/Dashboard/DashboardLayout.tsx:44 — DashboardLayout.DashboardLayout has cyclomatic complexity 32 (threshold 15). Of this number, 21 points are the body's own statements and 11 belong to 8 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 · chart.ChartTooltipContent (cyclomatic 31) · ×1
  • chart.ChartTooltipContent (cyclomatic 31) REDACTED:115 — chart.ChartTooltipContent has cyclomatic complexity 31 (threshold 15). Most of this is not in the body itself: 5 of the 31 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 187, 135). 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 · SignUpForm.SignUpForm (cyclomatic 31) · ×1
  • SignUpForm.SignUpForm (cyclomatic 31) REDACTED:30 — SignUpForm.SignUpForm has cyclomatic complexity 31 (threshold 15). Most of this is not in the body itself: 4 of the 31 points are its own statements and the rest belongs to 7 function items inside it that branch (isBtnDisabled, a function literal at line 174, showPasswordCriteria, …). 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 · ClientsTable.ClientsTable (cyclomatic 31) · ×1
  • ClientsTable.ClientsTable (cyclomatic 31) app/javascript/src/components/Clients/ClientsTable.tsx:78 — ClientsTable.ClientsTable has cyclomatic complexity 31 (threshold 15). Of this number, 18 points are the body's own statements and 13 belong to 10 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 · AcknowledgementQueue.AcknowledgementQueue (cyclomatic 31) · ×1
  • AcknowledgementQueue.AcknowledgementQueue (cyclomatic 31) app/javascript/src/components/Hiring/AcknowledgementQueue.tsx:13 — AcknowledgementQueue.AcknowledgementQueue has cyclomatic complexity 31 (threshold 15). Of this number, 17 points are the body's own statements and 14 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 · ProjectForm.ProjectForm (cyclomatic 31) · ×1
  • ProjectForm.ProjectForm (cyclomatic 31) app/javascript/src/components/Projects/List/Mobile/ProjectForm.tsx:19 — ProjectForm.ProjectForm has cyclomatic complexity 31 (threshold 15). Most of this is not in the body itself: 8 of the 31 points are its own statements and the rest belongs to 9 function items inside it that branch (a function literal at line 170, createProject, editProject, …). 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 · Mailboxes.Mailboxes (cyclomatic 30) · ×1
  • Mailboxes.Mailboxes (cyclomatic 30) app/javascript/src/components/Hiring/Mailboxes.tsx:12 — Mailboxes.Mailboxes has cyclomatic complexity 30 (threshold 15). Most of this is not in the body itself: 13 of the 30 points are its own statements and the rest belongs to 7 function items inside it that branch (update, create, a function literal at line 246, …). 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 · RevenueForecastPage.RevenueForecastPage (cyclomatic 29) · ×1
  • RevenueForecastPage.RevenueForecastPage (cyclomatic 29) app/javascript/src/components/Analytics/RevenueForecastPage.tsx:83 — RevenueForecastPage.RevenueForecastPage has cyclomatic complexity 29 (threshold 15). Of this number, 24 points are the body's own statements and 5 belong to 4 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.
D1 · Cyclomatic Complexity · Sidebar.SidebarItem (cyclomatic 29) · ×1
  • Sidebar.SidebarItem (cyclomatic 29) app/javascript/src/components/Dashboard/Sidebar.tsx:64 — Sidebar.SidebarItem has cyclomatic complexity 29 (threshold 15). Of this number, 20 points are the body's own statements and 9 belong to 2 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 · index.Workspace (cyclomatic 29) · ×1
  • index.Workspace (cyclomatic 29) app/javascript/src/components/Hiring/index.tsx:304 — index.Workspace has cyclomatic complexity 29 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · InvoiceApiService.formatInvoiceForApi (cyclomatic 29) · ×1
  • InvoiceApiService.formatInvoiceForApi (cyclomatic 29) app/javascript/src/services/invoiceApi.ts:371 — InvoiceApiService.formatInvoiceForApi has cyclomatic complexity 29 (threshold 15). Most of this is not in the body itself: 4 of the 29 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 405, 388). 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 · Fields.Fields (cyclomatic 28) · ×1
  • Fields.Fields (cyclomatic 28) app/javascript/src/components/DocumentSignatures/Fields.tsx:13 — Fields.Fields has cyclomatic complexity 28 (threshold 15). Of this number, 24 points are the body's own statements and 4 belong to 4 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.
D1 · Cyclomatic Complexity · InterviewReviews.Handover (cyclomatic 28) · ×1
  • InterviewReviews.Handover (cyclomatic 28) app/javascript/src/components/Hiring/InterviewReviews.tsx:13 — InterviewReviews.Handover has cyclomatic complexity 28 (threshold 15). Of this number, 19 points are the body's own statements and 9 belong to 5 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 · index.MonthlyRevenueChart (cyclomatic 28) · ×1
  • index.MonthlyRevenueChart (cyclomatic 28) app/javascript/src/components/Invoices/MonthlyRevenueChart/index.tsx:42 — index.MonthlyRevenueChart has cyclomatic complexity 28 (threshold 15). Most of this is not in the body itself: 10 of the 28 points are its own statements and the rest belongs to 7 function items inside it that branch (parseNumber, CustomTooltip, a function literal at line 89, …). 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 · RunPreparation.ConsultantRow (cyclomatic 28) · ×1
  • RunPreparation.ConsultantRow (cyclomatic 28) app/javascript/src/components/Payroll/RunPreparation.tsx:289 — RunPreparation.ConsultantRow has cyclomatic complexity 28 (threshold 15). Of this number, 27 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · index.EmploymentDetailsEdit (cyclomatic 28) · ×1
  • index.EmploymentDetailsEdit (cyclomatic 28) app/javascript/src/components/Profile/Personal/Employment/Edit/index.tsx:28 — index.EmploymentDetailsEdit has cyclomatic complexity 28 (threshold 15). Most of this is not in the body itself: 8 of the 28 points are its own statements and the rest belongs to 10 function items inside it that branch (updateEmploymentDetails, getDetails, a function literal at line 73, …). 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 · AddEditProject.AddEditProject (cyclomatic 28) · ×1
  • AddEditProject.AddEditProject (cyclomatic 28) app/javascript/src/components/Projects/Modals/AddEditProject.tsx:25 — AddEditProject.AddEditProject has cyclomatic complexity 28 (threshold 15). Of this number, 14 points are the body's own statements and 14 belong to 6 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 · verify.evaluateCheck (cyclomatic 28) · ×1
  • verify.evaluateCheck (cyclomatic 28) script/launch_matrix/verify.mjs:124 — verify.evaluateCheck has cyclomatic complexity 28 (threshold 15). Of this number, 24 points are the body's own statements and 4 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 · TeamAnalyticsPage.TeamAnalyticsPage (cyclomatic 27) · ×1
  • TeamAnalyticsPage.TeamAnalyticsPage (cyclomatic 27) app/javascript/src/components/Analytics/TeamAnalyticsPage.tsx:48 — TeamAnalyticsPage.TeamAnalyticsPage has cyclomatic complexity 27 (threshold 15). Of this number, 25 points are the body's own statements and 2 belong to 2 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 · enhanced-search.DefaultSearchResultItem (cyclomatic 27) · ×1
  • enhanced-search.DefaultSearchResultItem (cyclomatic 27) REDACTED:177 — enhanced-search.DefaultSearchResultItem has cyclomatic complexity 27 (threshold 15). Of this number, 24 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.
D1 · Cyclomatic Complexity · index.Workspace (cyclomatic 27) · ×1
  • index.Workspace (cyclomatic 27) app/javascript/src/components/DocumentSignatures/index.tsx:195 — index.Workspace has cyclomatic complexity 27 (threshold 15). Most of this is not in the body itself: 13 of the 27 points are its own statements and the rest belongs to 5 function items inside it that branch (create, a function literal at line 232, a function literal at line 238, …). 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 · ApplicationAssignments.ApplicationAssignments · ×1
  • ApplicationAssignments.ApplicationAssignments::save (cyclomatic 27) app/javascript/src/components/Hiring/ApplicationAssignments.tsx:194 — ApplicationAssignments.ApplicationAssignments::save has cyclomatic complexity 27 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages. This shape REPEATS in the file: one other method here (ApplicationAssignments.ApplicationAssignments) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D1 · Cyclomatic Complexity · PreflightSummary.PreflightSummary (cyclomatic 27) · ×1
  • PreflightSummary.PreflightSummary (cyclomatic 27) app/javascript/src/components/Payroll/PreflightSummary.tsx:70 — PreflightSummary.PreflightSummary has cyclomatic complexity 27 (threshold 15). Of this number, 26 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 · Reports.Reports (cyclomatic 27) · ×1
  • Reports.Reports (cyclomatic 27) app/javascript/src/components/Profile/EmployeeRecords/Reports.tsx:9 — Reports.Reports has cyclomatic complexity 27 (threshold 15). Most of this is not in the body itself: 10 of the 27 points are its own statements and the rest belongs to 7 function items inside it that branch (load, perform, a function literal at line 89, …). 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 · SelectProject.SelectProject (cyclomatic 27) · ×1
  • SelectProject.SelectProject (cyclomatic 27) app/javascript/src/components/TimeTracking/SelectProject.tsx:36 — SelectProject.SelectProject has cyclomatic complexity 27 (threshold 15). Most of this is not in the body itself: 11 of the 27 points are its own statements and the rest belongs to 3 function items inside it that branch (handleSaveButton, handleCancelButton, handleClientChange). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · Configuration.valid_value? (cyclomatic 27) · ×1
  • Configuration.valid_value? (cyclomatic 27) app/services/signatures/configuration.rb:98 — Configuration.valid_value? has cyclomatic complexity 27 (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.Workspace (cyclomatic 26) · ×1
  • index.Workspace (cyclomatic 26) app/javascript/src/components/Agreements/index.tsx:232 — index.Workspace has cyclomatic complexity 26 (threshold 15). Of this number, 13 points are the body's own statements and 13 belong to 6 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 · PersonalProfileSummary.PersonalProfileSummary (cyclomatic 26) · ×1
  • PersonalProfileSummary.PersonalProfileSummary (cyclomatic 26) app/javascript/src/components/Profile/Personal/User/PersonalProfileSummary.tsx:25 — PersonalProfileSummary.PersonalProfileSummary has cyclomatic complexity 26 (threshold 15). Of this number, 18 points are the body's own statements and 8 belong to one function item 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 · Page.DeviceEditPage (cyclomatic 26) · ×1
  • Page.DeviceEditPage (cyclomatic 26) app/javascript/src/components/Profile/Personal/Devices/Edit/Page.tsx:74 — Page.DeviceEditPage has cyclomatic complexity 26 (threshold 15). Most of this is not in the body itself: 3 of the 26 points are its own statements and the rest belongs to 9 function items inside it that branch (a function literal at line 213, handleCancel, a function literal at line 474, …). 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 · MonthCalendar.MonthCalendar (cyclomatic 26) · ×1
  • MonthCalendar.MonthCalendar (cyclomatic 26) app/javascript/src/components/TimeTracking/MonthCalendar.tsx:30 — MonthCalendar.MonthCalendar has cyclomatic complexity 26 (threshold 15). Most of this is not in the body itself: 6 of the 26 points are its own statements and the rest belongs to 7 function items inside it that branch (handleMonthChange, a function literal at line 222, a function literal at line 251, …). 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 · WeeklyEntries.WeeklyEntries (cyclomatic 26) · ×1
  • WeeklyEntries.WeeklyEntries (cyclomatic 26) app/javascript/src/components/TimeTracking/WeeklyEntries.tsx:32 — WeeklyEntries.WeeklyEntries has cyclomatic complexity 26 (threshold 15). Most of this is not in the body itself: 11 of the 26 points are its own statements and the rest belongs to 7 function items inside it that branch (a function literal at line 68, handleEditEntries, a function literal at line 59, …). 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 · SignatureRequestRevision.valid_archive (cyclomatic 26) · ×1
  • SignatureRequestRevision.valid_archive (cyclomatic 26) app/models/signature_request_revision.rb:147 — SignatureRequestRevision.valid_archive 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 · Review.Review (cyclomatic 25) · ×1
  • Review.Review (cyclomatic 25) app/javascript/src/components/DocumentSignatures/Review.tsx:40 — Review.Review has cyclomatic complexity 25 (threshold 15). Most of this is not in the body itself: 9 of the 25 points are its own statements and the rest belongs to 9 function items inside it that branch (a function literal at line 49, a function literal at line 276, loadOlder, …). 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 · ApiHandler.constructor (cyclomatic 25) · ×1
  • ApiHandler.constructor (cyclomatic 25) REDACTED:31 — ApiHandler.constructor 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 3 function literals inside it that branch (lines 56, 43, 116). 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.AnalyticsHome (cyclomatic 25) · ×1
  • index.AnalyticsHome (cyclomatic 25) app/javascript/src/components/Analytics/index.tsx:65 — index.AnalyticsHome has cyclomatic complexity 25 (threshold 15). Of this number, 24 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 · index.InvoiceTable (cyclomatic 25) · ×1
  • index.InvoiceTable (cyclomatic 25) app/javascript/src/components/Invoices/common/InvoiceTable/index.tsx:13 — index.InvoiceTable has cyclomatic complexity 25 (threshold 15). Most of this is not in the body itself: 7 of the 25 points are its own statements and the rest belongs to 7 function items inside it that branch (lineItemKey, handleAddEntry, 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 · RunPreparation.ProfileCompletionRequestPanel (cyclomatic 25) · ×1
  • RunPreparation.ProfileCompletionRequestPanel (cyclomatic 25) app/javascript/src/components/Payroll/RunPreparation.tsx:184 — RunPreparation.ProfileCompletionRequestPanel has cyclomatic complexity 25 (threshold 15). Of this number, 15 points are the body's own statements and 10 belong to one function item 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 · UserInformation.UserInformation (cyclomatic 25) · ×1
  • UserInformation.UserInformation (cyclomatic 25) app/javascript/src/components/Profile/Layout/Navigation/UserInformation.tsx:10 — UserInformation.UserInformation has cyclomatic complexity 25 (threshold 15). Most of this is not in the body itself: 10 of the 25 points are its own statements and the rest belongs to 5 function items inside it that branch (getAvatar, handleProfileImageChange, handleDeleteProfileImage, …). 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.UserDetailsView (cyclomatic 25) · ×1
  • index.UserDetailsView (cyclomatic 25) app/javascript/src/components/Profile/Personal/User/index.tsx:23 — index.UserDetailsView has cyclomatic complexity 25 (threshold 15). Of this number, 16 points are the body's own statements and 9 belong to 3 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 · Form.valid_answer? (cyclomatic 25) · ×1
  • Form.valid_answer? (cyclomatic 25) app/services/hiring/form.rb:86 — Form.valid_answer? has cyclomatic complexity 25 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
D1 · Cyclomatic Complexity · OfferPortal.OfferPortal (cyclomatic 24) · ×1
  • OfferPortal.OfferPortal (cyclomatic 24) app/javascript/src/components/Hiring/OfferPortal.tsx:19 — OfferPortal.OfferPortal has cyclomatic complexity 24 (threshold 15). Most of this is not in the body itself: 11 of the 24 points are its own statements and the rest belongs to 6 function items inside it that branch (a function literal at line 29, a function literal at line 88, reply, …). 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.Generate (cyclomatic 24) · ×1
  • index.Generate (cyclomatic 24) app/javascript/src/components/Agreements/index.tsx:21 — index.Generate has cyclomatic complexity 24 (threshold 15). Of this number, 12 points are the body's own statements and 12 belong to 5 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 · MercuryPayments.SplitPanel (cyclomatic 24) · ×1
  • MercuryPayments.SplitPanel (cyclomatic 24) app/javascript/src/components/Payroll/MercuryPayments.tsx:191 — MercuryPayments.SplitPanel has cyclomatic complexity 24 (threshold 15). Of this number, 17 points are the body's own statements and 7 belong to 4 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.
D1 · Cyclomatic Complexity · ProfileImageCard.ProfileImageCard (cyclomatic 24) · ×1
  • ProfileImageCard.ProfileImageCard (cyclomatic 24) app/javascript/src/components/Profile/Personal/User/Edit/ProfileImageCard.tsx:126 — ProfileImageCard.ProfileImageCard has cyclomatic complexity 24 (threshold 15). Most of this is not in the body itself: 9 of the 24 points are its own statements and the rest belongs to 7 function items inside it that branch (handleFileSelection, handleCropUpload, handleDelete, …). 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 · PayrollPtoReviewJob.perform (cyclomatic 24) · ×1
  • PayrollPtoReviewJob.perform (cyclomatic 24) app/jobs/payroll_pto_review_job.rb:4 — PayrollPtoReviewJob.perform has cyclomatic complexity 24 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · Button.Button (cyclomatic 23) · ×1
  • Button.Button (cyclomatic 23) app/javascript/src/StyledComponents/Button.tsx:48 — Button.Button 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 · SignInForm.SignInForm (cyclomatic 23) · ×1
  • SignInForm.SignInForm (cyclomatic 23) REDACTED:31 — SignInForm.SignInForm has cyclomatic complexity 23 (threshold 15). Most of this is not in the body itself: 5 of the 23 points are its own statements and the rest belongs to 8 function items inside it that branch (handleSignInFormSubmit, completeLogin, a function literal at line 196, …). 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.MobileView (cyclomatic 23) · ×1
  • index.MobileView (cyclomatic 23) app/javascript/src/components/ClientInvoices/Details/MobileView/index.tsx:17 — index.MobileView has cyclomatic complexity 23 (threshold 15). Of this number, 22 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 · TableRow.TableRow (cyclomatic 23) · ×1
  • TableRow.TableRow (cyclomatic 23) app/javascript/src/components/Invoices/List/Table/TableRow.tsx:20 — TableRow.TableRow has cyclomatic complexity 23 (threshold 15). Of this number, 16 points are the body's own statements and 7 belong to 5 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 · EmploymentEditor.EmploymentEditor (cyclomatic 23) · ×1
  • EmploymentEditor.EmploymentEditor (cyclomatic 23) app/javascript/src/components/Profile/Personal/Employment/Edit/EmploymentEditor.tsx:19 — EmploymentEditor.EmploymentEditor 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 · MobileEmploymentEditor.MobileEmploymentEditor (cyclomatic 23) · ×1
  • MobileEmploymentEditor.MobileEmploymentEditor (cyclomatic 23) app/javascript/src/components/Profile/Personal/Employment/Edit/MobileEmploymentEditor.tsx:19 — MobileEmploymentEditor.MobileEmploymentEditor 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 · index.UserDetailsEdit (cyclomatic 23) · ×1
  • index.UserDetailsEdit (cyclomatic 23) app/javascript/src/components/Profile/Personal/User/Edit/index.tsx:36 — index.UserDetailsEdit has cyclomatic complexity 23 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This shape REPEATS in the file: one other method here (index.UserDetailsEdit::handleUpdateDetails) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D1 · Cyclomatic Complexity · AddEditMember.EditClient (cyclomatic 23) · ×1
  • AddEditMember.EditClient (cyclomatic 23) app/javascript/src/components/Team/modals/AddEditMember.tsx:53 — AddEditMember.EditClient has cyclomatic complexity 23 (threshold 15). Most of this is not in the body itself: 2 of the 23 points are its own statements and the rest belongs to 4 function items inside it that branch (a function literal at line 144, handleSubmit, a function literal at line 60, …). 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 · Configuration.valid_field? (cyclomatic 23) · ×1
  • Configuration.valid_field? (cyclomatic 23) app/services/signatures/configuration.rb:82 — Configuration.valid_field? 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 · Fields.Fields · ×1
  • Fields.Fields::save (cyclomatic 22) app/javascript/src/components/Agreements/Fields.tsx:164 — Fields.Fields::save 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 · Sidebar.Sidebar (cyclomatic 22) · ×1
  • Sidebar.Sidebar (cyclomatic 22) app/javascript/src/components/Dashboard/Sidebar.tsx:213 — Sidebar.Sidebar has cyclomatic complexity 22 (threshold 15). Of this number, 12 points are the body's own statements and 10 belong to 6 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 · Inbox.Inbox (cyclomatic 22) · ×1
  • Inbox.Inbox (cyclomatic 22) app/javascript/src/components/Hiring/Inbox.tsx:19 — Inbox.Inbox has cyclomatic complexity 22 (threshold 15). Most of this is not in the body itself: 10 of the 22 points are its own statements and the rest belongs to 5 function items inside it that branch (upload, a function literal at line 40, a function literal at line 51, …). 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 · Review.Line (cyclomatic 22) · ×1
  • Review.Line (cyclomatic 22) app/javascript/src/components/Payroll/Review.tsx:111 — Review.Line has cyclomatic complexity 22 (threshold 15). Of this number, 19 points are the body's own statements and 3 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 · outstandingOverdueInvoice.getReportData (cyclomatic 22) · ×1
  • outstandingOverdueInvoice.getReportData (cyclomatic 22) app/javascript/src/components/Reports/api/outstandingOverdueInvoice.ts:5 — outstandingOverdueInvoice.getReportData has cyclomatic complexity 22 (threshold 15). Most of this is not in the body itself: 10 of the 22 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 42, 72, 78, …). 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.AddEntry (cyclomatic 22) · ×1
  • index.AddEntry (cyclomatic 22) app/javascript/src/components/TimesheetEntries/TimeEntryForm/index.tsx:14 — index.AddEntry has cyclomatic complexity 22 (threshold 15). Most of this is not in the body itself: 7 of the 22 points are its own statements and the rest belongs to 6 function items inside it that branch (handleEdit, handleFillData, a function literal at line 87, …). 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.TimesheetEntries · ×1
  • index.TimesheetEntries::TimeTrackingLayout (cyclomatic 22) app/javascript/src/components/TimesheetEntries/index.tsx:620 — index.TimesheetEntries::TimeTrackingLayout 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 · SecondFactorForm.SecondFactorForm (cyclomatic 21) · ×1
  • SecondFactorForm.SecondFactorForm (cyclomatic 21) app/javascript/src/components/Authentication/SignIn/SecondFactorForm.tsx:9 — SecondFactorForm.SecondFactorForm has cyclomatic complexity 21 (threshold 15). Of this number, 13 points are the body's own statements and 8 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 · index.ClientInvoices (cyclomatic 21) · ×1
  • index.ClientInvoices (cyclomatic 21) app/javascript/src/components/ClientInvoices/index.tsx:14 — index.ClientInvoices has cyclomatic complexity 21 (threshold 15). Most of this is not in the body itself: 5 of the 21 points are its own statements and the rest belongs to 5 function items inside it that branch (InvoicesLayout, a function literal at line 66, fetchInvoices, …). 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 · formValidationSchema.getInitialvalues (cyclomatic 21) · ×1
  • formValidationSchema.getInitialvalues (cyclomatic 21) app/javascript/src/components/Clients/ClientForm/formValidationSchema.ts:106 — formValidationSchema.getInitialvalues has cyclomatic complexity 21 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · ApplicationRetention.ApplicationRetention (cyclomatic 21) · ×1
  • ApplicationRetention.ApplicationRetention (cyclomatic 21) app/javascript/src/components/Hiring/ApplicationRetention.tsx:23 — ApplicationRetention.ApplicationRetention has cyclomatic complexity 21 (threshold 15). Of this number, 11 points are the body's own statements and 10 belong to 5 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 · Roles.Roles (cyclomatic 21) · ×1
  • Roles.Roles (cyclomatic 21) app/javascript/src/components/Hiring/Roles.tsx:90 — Roles.Roles has cyclomatic complexity 21 (threshold 15). Most of this is not in the body itself: 7 of the 21 points are its own statements and the rest belongs to 5 function items inside it that branch (create, save, a function literal at line 292, …). 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 · MarkInvoicePaidModal.MarkInvoiceAsPaidModal (cyclomatic 21) · ×1
  • MarkInvoicePaidModal.MarkInvoiceAsPaidModal (cyclomatic 21) app/javascript/src/components/Invoices/Invoice/MarkInvoicePaidModal.tsx:17 — MarkInvoicePaidModal.MarkInvoiceAsPaidModal has cyclomatic complexity 21 (threshold 15). Of this number, 17 points are the body's own statements and 4 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 · WeekDaySelector.WeekDaySelector · ×1
  • WeekDaySelector.WeekDaySelector::renderDayButton (cyclomatic 21) app/javascript/src/components/TimeTracking/WeekDaySelector.tsx:21 — WeekDaySelector.WeekDaySelector::renderDayButton has cyclomatic complexity 21 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · ConsultantRevision.retained_selection? (cyclomatic 21) · ×1
  • ConsultantRevision.retained_selection? (cyclomatic 21) app/services/payroll/consultant_revision.rb:104 — ConsultantRevision.retained_selection? has cyclomatic complexity 21 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · validate.isValid (cyclomatic 20) · ×1
  • validate.isValid (cyclomatic 20) app/javascript/src/StyledComponents/TimeInput/validate.ts:1 — validate.isValid has cyclomatic complexity 20 (threshold 15). Of this number, 15 points are the body's own statements and 5 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 · index.CustomDatePicker (cyclomatic 20) · ×1
  • index.CustomDatePicker (cyclomatic 20) app/javascript/src/common/CustomDatePicker/index.tsx:12 — index.CustomDatePicker has cyclomatic complexity 20 (threshold 15). Most of this is not in the body itself: 3 of the 20 points are its own statements and the rest belongs to 5 function items inside it that branch (a function literal at line 78, parseDate, a function literal at line 150, …). 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.ClientDetails (cyclomatic 20) · ×1
  • index.ClientDetails (cyclomatic 20) app/javascript/src/components/Clients/Details/index.tsx:29 — index.ClientDetails has cyclomatic complexity 20 (threshold 15). Of this number, 19 points are the body's own statements and 1 belongs to one function item 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.Applications (cyclomatic 20) · ×1
  • index.Applications (cyclomatic 20) app/javascript/src/components/Hiring/index.tsx:28 — index.Applications has cyclomatic complexity 20 (threshold 15). Of this number, 13 points are the body's own statements and 7 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 · MercuryPayments.Consultant (cyclomatic 20) · ×1
  • MercuryPayments.Consultant (cyclomatic 20) app/javascript/src/components/Payroll/MercuryPayments.tsx:876 — MercuryPayments.Consultant has cyclomatic complexity 20 (threshold 15). Of this number, 15 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 · TimeEntriesDisplay.TimeEntriesDisplay · ×1
  • TimeEntriesDisplay.TimeEntriesDisplay::renderEntry (cyclomatic 20) app/javascript/src/components/TimeTracking/TimeEntriesDisplay.tsx:90 — TimeEntriesDisplay.TimeEntriesDisplay::renderEntry 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. This shape REPEATS in the file: one other method here (TimeEntriesDisplay.TimeEntriesDisplay) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D1 · Cyclomatic Complexity · SettingsController.render_settings (cyclomatic 20) · ×1
  • SettingsController.render_settings (cyclomatic 20) app/controllers/api/v1/hiring/settings_controller.rb:25 — SettingsController.render_settings 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 · NativeGoogleAuthRequest.exchange! (cyclomatic 20) · ×1
  • NativeGoogleAuthRequest.exchange! (cyclomatic 20) app/models/native_google_auth_request.rb:79 — NativeGoogleAuthRequest.exchange! 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 · CalendarEvents.normalize (cyclomatic 20) · ×1
  • CalendarEvents.normalize (cyclomatic 20) app/services/hiring/calendar_events.rb:58 — CalendarEvents.normalize 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 · BillingEvidence.valid? (cyclomatic 20) · ×1
  • BillingEvidence.valid? (cyclomatic 20) app/services/payroll/billing_evidence.rb:60 — BillingEvidence.valid? 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 · Header.Header (cyclomatic 19) · ×1
  • Header.Header (cyclomatic 19) app/javascript/src/components/ClientInvoices/Header.tsx:13 — Header.Header has cyclomatic complexity 19 (threshold 15). Of this number, 11 points are the body's own statements and 8 belong to 5 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.ProfileLink (cyclomatic 19) · ×1
  • index.ProfileLink (cyclomatic 19) app/javascript/src/components/DocumentSignatures/index.tsx:28 — index.ProfileLink has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 4 of the 19 points are its own statements and the rest belongs to 5 function literals inside it that branch (lines 76, 48, 155, …). 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 · ClientSelection.ClientSelection (cyclomatic 19) · ×1
  • ClientSelection.ClientSelection (cyclomatic 19) app/javascript/src/components/Invoices/common/InvoiceDetails/ClientSelection.tsx:12 — ClientSelection.ClientSelection has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 8 of the 19 points are its own statements and the rest belongs to 4 function items inside it that branch (autoGenerateInvoiceNumber, a function literal at line 36, handleClientChange, …). 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 · MobileFinancialDetailForm.MobileFinancialDetailForm (cyclomatic 19) · ×1
  • MobileFinancialDetailForm.MobileFinancialDetailForm (cyclomatic 19) app/javascript/src/components/OrganizationSetup/FinancialDetailsForm/MobileFinancialDetailForm.tsx:25 — MobileFinancialDetailForm.MobileFinancialDetailForm has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 2 of the 19 points are its own statements and the rest belongs to 5 function items inside it that branch (a function literal at line 61, isBtnDisabled, a function literal at line 74, …). 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 · List.labelForSetting (cyclomatic 19) · ×1
  • List.labelForSetting (cyclomatic 19) app/javascript/src/components/Profile/Layout/Navigation/List.tsx:16 — List.labelForSetting has cyclomatic complexity 19 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · index.InvoiceSignature (cyclomatic 19) · ×1
  • index.InvoiceSignature (cyclomatic 19) app/javascript/src/components/Profile/Organization/InvoiceSignature/index.tsx:14 — index.InvoiceSignature has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 9 of the 19 points are its own statements and the rest belongs to 3 function items inside it that branch (handleFileSelect, a function literal at line 27, handleDelete). 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 · TimeEntriesDisplay.TimeEntriesDisplay (cyclomatic 19) · ×1
  • TimeEntriesDisplay.TimeEntriesDisplay (cyclomatic 19) app/javascript/src/components/TimeTracking/TimeEntriesDisplay.tsx:34 — TimeEntriesDisplay.TimeEntriesDisplay 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. This shape REPEATS in the file: one other method here (TimeEntriesDisplay.TimeEntriesDisplay::renderEntry) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D1 · Cyclomatic Complexity · Pipeline.validate! (cyclomatic 19) · ×1
  • Pipeline.validate! (cyclomatic 19) app/services/hiring/pipeline.rb:29 — Pipeline.validate! 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 · Snapshot.valid_preparation? (cyclomatic 19) · ×1
  • Snapshot.valid_preparation? (cyclomatic 19) app/services/payroll/snapshot.rb:185 — Snapshot.valid_preparation? 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.customStyles (cyclomatic 18) · ×1
  • index.customStyles (cyclomatic 18) app/javascript/src/common/CustomReactSelectStyle/Styles/index.ts:7 — index.customStyles has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 1 of the 18 points is its own statement and the rest belongs to 6 function literals inside it that branch (lines 66, 31, 57, …). 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.InputField (cyclomatic 18) · ×1
  • index.InputField (cyclomatic 18) app/javascript/src/common/FormikFields/InputField/index.tsx:9 — index.InputField has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 7 of the 18 points are its own statements and the rest belongs to 3 function items inside it that branch (handleFieldChange, a function literal at line 74, clearErrorOnChange). 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 · Fields.FieldValue (cyclomatic 18) · ×1
  • Fields.FieldValue (cyclomatic 18) app/javascript/src/components/Agreements/Fields.tsx:61 — Fields.FieldValue has cyclomatic complexity 18 (threshold 15). Of this number, 14 points are the body's own statements and 4 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 · MobileClientEditor.MobileClientEditor (cyclomatic 18) · ×1
  • MobileClientEditor.MobileClientEditor (cyclomatic 18) app/javascript/src/components/Clients/ClientForm/MobileClientEditor.tsx:35 — MobileClientEditor.MobileClientEditor has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 2 of the 18 points are its own statements and the rest belongs to 4 function items inside it that branch (a function literal at line 121, handleSubmit, a function literal at line 267, …). 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 · ApplicationDetail.ApplicationDetail (cyclomatic 18) · ×1
  • ApplicationDetail.ApplicationDetail (cyclomatic 18) app/javascript/src/components/Hiring/ApplicationDetail.tsx:20 — ApplicationDetail.ApplicationDetail has cyclomatic complexity 18 (threshold 15). Of this number, 10 points are the body's own statements and 8 belong to 5 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 · ApplicationForm.ApplicationForm (cyclomatic 18) · ×1
  • ApplicationForm.ApplicationForm (cyclomatic 18) app/javascript/src/components/Hiring/ApplicationForm.tsx:13 — ApplicationForm.ApplicationForm has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 5 of the 18 points are its own statements and the rest belongs to one function item inside it that branches (submit). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · LeaveBlock.LeaveBlock (cyclomatic 18) · ×1
  • LeaveBlock.LeaveBlock (cyclomatic 18) app/javascript/src/components/LeaveManagement/Container/LeaveBlock.tsx:18 — LeaveBlock.LeaveBlock has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 8 of the 18 points are its own statements and the rest belongs to 3 function items inside it that branch (getLeaveColor, getLeaveIcon, getSelectedText). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · IndiaHandoffs.IndiaHandoffsPanel (cyclomatic 18) · ×1
  • IndiaHandoffs.IndiaHandoffsPanel (cyclomatic 18) app/javascript/src/components/Payroll/IndiaHandoffs.tsx:492 — IndiaHandoffs.IndiaHandoffsPanel has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 8 of the 18 points are its own statements and the rest belongs to 5 function items inside it that branch (perform, a function literal at line 514, a function literal at line 523, …). 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.UserDetailsEdit · ×1
  • index.UserDetailsEdit::handleUpdateDetails (cyclomatic 18) app/javascript/src/components/Profile/Personal/User/Edit/index.tsx:212 — index.UserDetailsEdit::handleUpdateDetails 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. This shape REPEATS in the file: one other method here (index.UserDetailsEdit) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D1 · Cyclomatic Complexity · SidebarStatusFilter.SidebarStatusFilter (cyclomatic 18) · ×1
  • SidebarStatusFilter.SidebarStatusFilter (cyclomatic 18) app/javascript/src/components/Reports/Filters/SidebarStatusFilter.tsx:15 — SidebarStatusFilter.SidebarStatusFilter 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 3 function items inside it that branch (getStatusColor, getStatusIcon, a function literal at line 106). 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.Header (cyclomatic 18) · ×1
  • index.Header (cyclomatic 18) app/javascript/src/components/Reports/Header/index.tsx:33 — index.Header has cyclomatic complexity 18 (threshold 15). Of this number, 13 points are the body's own statements and 5 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 · Header.Header (cyclomatic 18) · ×1
  • Header.Header (cyclomatic 18) app/javascript/src/components/TimeTracking/Header.tsx:14 — Header.Header has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 8 of the 18 points are its own statements and the rest belongs to 5 function items inside it that branch (getLabel, getRightArrowAction, getLeftArrowAction, …). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · TableRow.TableRow (cyclomatic 18) · ×1
  • TableRow.TableRow (cyclomatic 18) app/javascript/src/components/payments/Table/TableRow.tsx:18 — TableRow.TableRow has cyclomatic complexity 18 (threshold 15). Of this number, 16 points are the body's own statements and 2 belong to one function item 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 · DecisionCommunication.current_preview (cyclomatic 18) · ×1
  • DecisionCommunication.current_preview (cyclomatic 18) app/services/hiring/decision_communication.rb:79 — DecisionCommunication.current_preview 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 · Form.valid_field? (cyclomatic 18) · ×1
  • Form.valid_field? (cyclomatic 18) app/services/hiring/form.rb:133 — Form.valid_field? 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 · Onboarding.eligibility_reason (cyclomatic 18) · ×1
  • Onboarding.eligibility_reason (cyclomatic 18) app/services/hiring/onboarding.rb:218 — Onboarding.eligibility_reason 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 · useAnalyticsFilters.useAnalyticsFilters (cyclomatic 17) · ×1
  • useAnalyticsFilters.useAnalyticsFilters (cyclomatic 17) app/javascript/src/components/Analytics/useAnalyticsFilters.ts:21 — useAnalyticsFilters.useAnalyticsFilters has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 6 of the 17 points are its own statements and the rest belongs to 5 function literals inside it that branch (lines 65, 42, 79, …). 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 · ServiceFeePanel.ServiceFeePanel · ×1
  • ServiceFeePanel.ServiceFeePanel::save (cyclomatic 17) app/javascript/src/components/Payroll/ServiceFeePanel.tsx:83 — ServiceFeePanel.ServiceFeePanel::save 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. This shape REPEATS in the file: one other method here (ServiceFeePanel.ServiceFeePanel) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D1 · Cyclomatic Complexity · ServiceFeePanel.ServiceFeePanel (cyclomatic 17) · ×1
  • ServiceFeePanel.ServiceFeePanel (cyclomatic 17) app/javascript/src/components/Payroll/ServiceFeePanel.tsx:11 — ServiceFeePanel.ServiceFeePanel 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. This shape REPEATS in the file: one other method here (ServiceFeePanel.ServiceFeePanel::save) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D1 · Cyclomatic Complexity · index.TrialBanner (cyclomatic 17) · ×1
  • index.TrialBanner (cyclomatic 17) app/javascript/src/components/common/TrialBanner/index.tsx:10 — index.TrialBanner 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 · AssignmentLibrary.AssignmentLibrary (cyclomatic 17) · ×1
  • AssignmentLibrary.AssignmentLibrary (cyclomatic 17) app/javascript/src/components/Hiring/AssignmentLibrary.tsx:35 — AssignmentLibrary.AssignmentLibrary has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 6 of the 17 points are its own statements and the rest belongs to 5 function items inside it that branch (create, a function literal at line 222, 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.MultipleEntriesModal (cyclomatic 17) · ×1
  • index.MultipleEntriesModal (cyclomatic 17) app/javascript/src/components/Invoices/MultipleEntriesModal/index.tsx:19 — index.MultipleEntriesModal has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 6 of the 17 points are its own statements and the rest belongs to 5 function items inside it that branch (handleFilterParams, a function literal at line 44, handleSelectAll, …). 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.OrganizationSetup (cyclomatic 17) · ×1
  • index.OrganizationSetup (cyclomatic 17) app/javascript/src/components/OrganizationSetup/index.tsx:26 — index.OrganizationSetup has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 6 of the 17 points are its own statements and the rest belongs to 4 function items inside it that branch (onSaveBtnClick, isStepFormSubmittedOrVisited, generatePayload, …). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · index.BillingIdentityPanel · ×1
  • index.BillingIdentityPanel::failed (cyclomatic 17) app/javascript/src/components/Profile/BillingIdentity/index.tsx:108 — index.BillingIdentityPanel::failed has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages. This shape REPEATS in the file: one other method here (index.BillingIdentityPanel) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D1 · Cyclomatic Complexity · index.SsoSettingsForm (cyclomatic 17) · ×1
  • index.SsoSettingsForm (cyclomatic 17) app/javascript/src/components/Profile/Organization/Sso/index.tsx:23 — index.SsoSettingsForm has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 4 of the 17 points are its own statements and the rest belongs to 5 function items inside it that branch (handleSubmit, a function literal at line 32, addDomain, …). 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.buildPersonalDetails (cyclomatic 17) · ×1
  • index.buildPersonalDetails (cyclomatic 17) app/javascript/src/components/Profile/index.tsx:14 — index.buildPersonalDetails 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 · index.TimeEntryReportFilters (cyclomatic 17) · ×1
  • index.TimeEntryReportFilters (cyclomatic 17) app/javascript/src/components/Reports/Filters/index.tsx:21 — index.TimeEntryReportFilters has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 8 of the 17 points are its own statements and the rest belongs to 5 function items inside it that branch (handleApplyBtnDisable, handleSelectFilter, submitApplyFilter, …). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · EntryCard.EntryCard (cyclomatic 17) · ×1
  • EntryCard.EntryCard (cyclomatic 17) app/javascript/src/components/TimeTracking/EntryCard.tsx:65 — EntryCard.EntryCard has cyclomatic complexity 17 (threshold 15). Of this number, 13 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 · time-input.TimeInput (cyclomatic 17) · ×1
  • time-input.TimeInput (cyclomatic 17) app/javascript/src/components/ui/time-input.tsx:36 — time-input.TimeInput 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 3 function items inside it that branch (onChangeHandler, a function literal at line 63, getType). 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.Payments (cyclomatic 17) · ×1
  • index.Payments (cyclomatic 17) app/javascript/src/components/payments/index.tsx:17 — index.Payments 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 7 function items inside it that branch (PaymentsLayout, handleEscKeyPress, fetchInvoiceList, …). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · HiringAssignmentSubmission.valid_answers (cyclomatic 17) · ×1
  • HiringAssignmentSubmission.valid_answers (cyclomatic 17) app/models/hiring_assignment_submission.rb:70 — HiringAssignmentSubmission.valid_answers 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 · ProjectMember.record_profitability_billing_rate (cyclomatic 17) · ×1
  • ProjectMember.record_profitability_billing_rate (cyclomatic 17) app/models/project_member.rb:13 — ProjectMember.record_profitability_billing_rate has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · Document.validate_attributes (cyclomatic 17) · ×1
  • Document.validate_attributes (cyclomatic 17) app/services/agreements/document.rb:155 — Document.validate_attributes 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 · Onboarding.presentation (cyclomatic 17) · ×1
  • Onboarding.presentation (cyclomatic 17) app/services/hiring/onboarding.rb:285 — Onboarding.presentation 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 · MercuryRevisionGuard.protected_line_with_reports? (cyclomatic 17) · ×1
  • MercuryRevisionGuard.protected_line_with_reports? (cyclomatic 17) app/services/payroll/mercury_revision_guard.rb:59 — MercuryRevisionGuard.protected_line_with_reports? 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 · Snapshot.resolved? (cyclomatic 17) · ×1
  • Snapshot.resolved? (cyclomatic 17) app/services/payroll/snapshot.rb:338 — Snapshot.resolved? 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 · Result.process_response_by_group_by (cyclomatic 17) · ×1
  • Result.process_response_by_group_by (cyclomatic 17) app/services/reports/time_entries/result.rb:33 — Result.process_response_by_group_by 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 · index.InvoicePreview · ×1
  • index.InvoicePreview::handleSendSubmit (cyclomatic 16) app/javascript/src/components/Invoices/InvoicePreview/index.tsx:204 — index.InvoicePreview::handleSendSubmit has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This shape REPEATS in the file: one other method here (index.InvoicePreview) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D1 · Cyclomatic Complexity · index.InvoicesPage · ×1
  • index.InvoicesPage::handleInvoiceAction (cyclomatic 16) app/javascript/src/components/Invoices/index.tsx:778 — index.InvoicesPage::handleInvoiceAction has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This shape REPEATS in the file: one other method here (index.InvoicesPage) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D1 · Cyclomatic Complexity · index.LeaveManagement (cyclomatic 16) · ×1
  • index.LeaveManagement (cyclomatic 16) app/javascript/src/components/LeaveManagement/index.tsx:13 — index.LeaveManagement has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 3 of the 16 points are its own statements and the rest belongs to 5 function items inside it that branch (handlefilterTimeoffEntries, a function literal at line 34, LeaveManagementLayout, …). 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 · IndiaHandoffs.Handoff (cyclomatic 16) · ×1
  • IndiaHandoffs.Handoff (cyclomatic 16) app/javascript/src/components/Payroll/IndiaHandoffs.tsx:179 — IndiaHandoffs.Handoff has cyclomatic complexity 16 (threshold 15). Of this number, 12 points are the body's own statements and 4 belong to 3 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.
D1 · Cyclomatic Complexity · RunPreparation.PrepareRevisionPanel (cyclomatic 16) · ×1
  • RunPreparation.PrepareRevisionPanel (cyclomatic 16) app/javascript/src/components/Payroll/RunPreparation.tsx:573 — RunPreparation.PrepareRevisionPanel has cyclomatic complexity 16 (threshold 15). Of this number, 8 points are the body's own statements and 8 belong to 5 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 · Page.OrganizationSettingsPage · ×1
  • Page.OrganizationSettingsPage::formatAddress (cyclomatic 16) app/javascript/src/components/Profile/Organization/Details/Page.tsx:130 — Page.OrganizationSettingsPage::formatAddress has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This shape REPEATS in the file: one other method here (Page.OrganizationSettingsPage) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D1 · Cyclomatic Complexity · Page.OrganizationSettingsPage (cyclomatic 16) · ×1
  • Page.OrganizationSettingsPage (cyclomatic 16) app/javascript/src/components/Profile/Organization/Details/Page.tsx:44 — Page.OrganizationSettingsPage has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This shape REPEATS in the file: one other method here (Page.OrganizationSettingsPage::formatAddress) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D1 · Cyclomatic Complexity · importModal.ImportModal (cyclomatic 16) · ×1
  • importModal.ImportModal (cyclomatic 16) app/javascript/src/components/Profile/Organization/Import/importModal.tsx:16 — importModal.ImportModal has cyclomatic complexity 16 (threshold 15). Of this number, 10 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 · index.ProjectDetails (cyclomatic 16) · ×1
  • index.ProjectDetails (cyclomatic 16) app/javascript/src/components/Projects/Details/index.tsx:35 — index.ProjectDetails has cyclomatic complexity 16 (threshold 15). Of this number, 10 points are the body's own statements and 6 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 · animated-textarea.AnimatedTextarea (cyclomatic 16) · ×1
  • animated-textarea.AnimatedTextarea (cyclomatic 16) app/javascript/src/components/ui/animated-textarea.tsx:13 — animated-textarea.AnimatedTextarea has cyclomatic complexity 16 (threshold 15). 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, 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 · HiringAssignmentTemplate.valid_fields (cyclomatic 16) · ×1
  • HiringAssignmentTemplate.valid_fields (cyclomatic 16) app/models/hiring_assignment_template.rb:32 — HiringAssignmentTemplate.valid_fields 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 · Decisions.decision_details (cyclomatic 16) · ×1
  • Decisions.decision_details (cyclomatic 16) app/services/hiring/decisions.rb:143 — Decisions.decision_details 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 · EmailContent.review_reason (cyclomatic 16) · ×1
  • EmailContent.review_reason (cyclomatic 16) app/services/hiring/email_content.rb:82 — EmailContent.review_reason 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 · Intake.normalized_input (cyclomatic 16) · ×1
  • Intake.normalized_input (cyclomatic 16) app/services/hiring/intake.rb:72 — Intake.normalized_input 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 · Screening.validate_input! (cyclomatic 16) · ×1
  • Screening.validate_input! (cyclomatic 16) app/services/hiring/screening.rb:65 — Screening.validate_input! 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 · BillingEvidence.command_files (cyclomatic 16) · ×1
  • BillingEvidence.command_files (cyclomatic 16) app/services/payroll/billing_evidence.rb:13 — BillingEvidence.command_files 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 · MercuryPayment.local_blockers (cyclomatic 16) · ×1
  • MercuryPayment.local_blockers (cyclomatic 16) app/services/payroll/mercury_payment.rb:221 — MercuryPayment.local_blockers 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 · MercuryReconciliation.apply_linkage (cyclomatic 16) · ×1
  • MercuryReconciliation.apply_linkage (cyclomatic 16) app/services/payroll/mercury_reconciliation.rb:259 — MercuryReconciliation.apply_linkage 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 · ProfileCompletion.current_source (cyclomatic 16) · ×1
  • ProfileCompletion.current_source (cyclomatic 16) app/services/payroll/profile_completion.rb:46 — ProfileCompletion.current_source has cyclomatic complexity 16 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
D1 · Cyclomatic Complexity · PdfInfo.check_page_boxes (cyclomatic 16) · ×1
  • PdfInfo.check_page_boxes (cyclomatic 16) app/services/signatures/pdf_info.rb:99 — PdfInfo.check_page_boxes 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.
D2 · Cognitive Complexity · Page.OrganizationPaymentSettingsPage (cognitive 183) · ×1
  • Page.OrganizationPaymentSettingsPage (cognitive 183) app/javascript/src/components/Profile/Organization/Payment/Page.tsx:63 — Page.OrganizationPaymentSettingsPage has cognitive complexity 183 (threshold 15). Drivers by points: ternaries 28 (79 pts), boolean chains 71, if/else 19 (21 pts), error handling 12 (nesting depth added 53). Of this number, 90 points are the body's own statements and 93 belong to 23 function items 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 · index.InvoiceEditor (cognitive 136) · ×1
  • index.InvoiceEditor (cognitive 136) app/javascript/src/components/Invoices/InvoiceEditor/index.tsx:62 — index.InvoiceEditor has cognitive complexity 136 (threshold 15). Drivers by points: boolean chains 86, if/else 27 (28 pts), ternaries 20 (22 pts) (nesting depth added 3). Of this number, 59 points are the body's own statements and 77 belong to 34 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 · App.App (cognitive 114) · ×1
  • App.App (cognitive 114) apps/mobile/App.tsx:239 — App.App has cognitive complexity 114 (threshold 15). Drivers by points: ternaries 24 (71 pts), boolean chains 25, if/else 14, error handling 4 (nesting depth added 47). Of this number, 67 points are the body's own statements and 47 belong to 19 function items 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 · ExpensesTable.ExpensesTable (cognitive 104) · ×1
  • ExpensesTable.ExpensesTable (cognitive 104) app/javascript/src/components/Expenses/ExpensesTable.tsx:199 — ExpensesTable.ExpensesTable has cognitive complexity 104 (threshold 15). Drivers by points: boolean chains 46, ternaries 27 (35 pts), if/else 21, error handling 2 (nesting depth added 8). Of this number, 38 points are the body's own statements and 66 belong to 30 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.Records (cognitive 101) · ×1
  • index.Records (cognitive 101) app/javascript/src/components/Profile/EmployeeRecords/index.tsx:44 — index.Records has cognitive complexity 101 (threshold 15). Drivers by points: ternaries 21 (57 pts), boolean chains 33, if/else 9 (10 pts), error handling 1 (nesting depth added 37). Of this number, 33 points are the body's own statements and 68 belong to 18 function items 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 · Editor.Editor (cognitive 92) · ×1
  • Editor.Editor (cognitive 92) app/javascript/src/components/DocumentSignatures/Editor.tsx:30 — Editor.Editor has cognitive complexity 92 (threshold 15). Drivers by points: if/else 29 (35 pts), boolean chains 30, ternaries 14 (22 pts), error handling 4, loops 1 (nesting depth added 14). Of this number, 38 points are the body's own statements and 54 belong to 17 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, 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 · RazorpayConnection.RazorpayConnection (cognitive 85) · ×1
  • RazorpayConnection.RazorpayConnection (cognitive 85) app/javascript/src/components/Profile/Organization/Payment/RazorpayConnection.tsx:104 — RazorpayConnection.RazorpayConnection has cognitive complexity 85 (threshold 15). Drivers by points: boolean chains 43, if/else 17 (20 pts), ternaries 10 (17 pts), error handling 5 (nesting depth added 10). Of this number, 38 points are the body's own statements and 47 belong to 14 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 · index.TimeoffForm (cognitive 81) · ×1
  • index.TimeoffForm (cognitive 81) app/javascript/src/components/TimeoffEntries/TimeoffForm/index.tsx:18 — index.TimeoffForm has cognitive complexity 81 (threshold 15). Drivers by points: if/else 36 (50 pts), boolean chains 28, ternaries 3 (nesting depth added 14). Most of this is not in the body itself: 1 of the 81 points is its own statement and the rest belongs to 19 function items inside it that branch (handleFillData, getPayload, handleEditTimeoffEntry, …). 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 · index.Workspace (cognitive 77) · ×1
  • index.Workspace (cognitive 77) app/javascript/src/components/Hiring/index.tsx:304 — index.Workspace has cognitive complexity 77 (threshold 15). Drivers by points: ternaries 11 (66 pts), boolean chains 10, if/else 1 (nesting depth added 55). 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 · FloatingTimer.FloatingTimer (cognitive 77) · ×1
  • FloatingTimer.FloatingTimer (cognitive 77) app/javascript/src/components/TimesheetEntries/FloatingTimer.tsx:89 — FloatingTimer.FloatingTimer has cognitive complexity 77 (threshold 15). Drivers by points: ternaries 26 (37 pts), if/else 20 (21 pts), boolean chains 18, error handling 1 (nesting depth added 12). Of this number, 32 points are the body's own statements and 45 belong to 27 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, 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 · DeliveryPanel.DeliveryPanel (cognitive 75) · ×1
  • DeliveryPanel.DeliveryPanel (cognitive 75) app/javascript/src/components/DocumentSignatures/DeliveryPanel.tsx:35 — DeliveryPanel.DeliveryPanel has cognitive complexity 75 (threshold 15). Drivers by points: boolean chains 44, if/else 19 (24 pts), ternaries 4, error handling 3 (nesting depth added 5). Of this number, 44 points are the body's own statements and 31 belong to 11 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 · CandidateMessages.CandidateMessages (cognitive 74) · ×1
  • CandidateMessages.CandidateMessages (cognitive 74) app/javascript/src/components/Hiring/CandidateMessages.tsx:49 — CandidateMessages.CandidateMessages has cognitive complexity 74 (threshold 15). Drivers by points: boolean chains 36, ternaries 11 (20 pts), if/else 15, error handling 3 (nesting depth added 9). Of this number, 48 points are the body's own statements and 26 belong to 9 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 · ReceiptDetail.ReceiptDetail (cognitive 72) · ×1
  • ReceiptDetail.ReceiptDetail (cognitive 72) app/javascript/src/components/Hiring/ReceiptDetail.tsx:21 — ReceiptDetail.ReceiptDetail has cognitive complexity 72 (threshold 15). Drivers by points: boolean chains 43, if/else 15 (18 pts), ternaries 7 (8 pts), error handling 3 (nesting depth added 4). Of this number, 40 points are the body's own statements and 32 belong to 8 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 · TeamTable.TeamTable (cognitive 72) · ×1
  • TeamTable.TeamTable (cognitive 72) app/javascript/src/components/Team/TeamTable.tsx:102 — TeamTable.TeamTable has cognitive complexity 72 (threshold 15). Drivers by points: boolean chains 37, if/else 15 (16 pts), ternaries 12 (15 pts), match/switch 3, error handling 1 (nesting depth added 4). Of this number, 27 points are the body's own statements and 45 belong to 24 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 · EntryForm.AddEntry (cognitive 72) · ×1
  • EntryForm.AddEntry (cognitive 72) app/javascript/src/components/TimeTracking/EntryForm.tsx:32 — EntryForm.AddEntry has cognitive complexity 72 (threshold 15). Drivers by points: boolean chains 30, if/else 20 (23 pts), ternaries 11 (16 pts), error handling 3 (nesting depth added 8). Of this number, 22 points are the body's own statements and 50 belong to 16 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 · InvoiceApiService.transformApiInvoice (cognitive 71) · ×1
  • InvoiceApiService.transformApiInvoice (cognitive 71) app/javascript/src/services/invoiceApi.ts:435 — InvoiceApiService.transformApiInvoice has cognitive complexity 71 (threshold 15). Drivers by points: boolean chains 52, if/else 8 (14 pts), ternaries 5 (nesting depth added 6). Of this number, 38 points are the body's own statements and 33 belong to 3 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 · index.Billing (cognitive 69) · ×1
  • index.Billing (cognitive 69) app/javascript/src/components/Profile/Organization/Billing/index.tsx:61 — index.Billing has cognitive complexity 69 (threshold 15). Drivers by points: boolean chains 33, if/else 21 (24 pts), ternaries 6 (7 pts), error handling 5 (nesting depth added 4). Of this number, 32 points are the body's own statements and 37 belong to 11 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 · InterviewBookings.InterviewBookings (cognitive 66) · ×1
  • InterviewBookings.InterviewBookings (cognitive 66) app/javascript/src/components/Hiring/InterviewBookings.tsx:41 — InterviewBookings.InterviewBookings has cognitive complexity 66 (threshold 15). Drivers by points: boolean chains 40, if/else 13 (16 pts), ternaries 8 (9 pts), error handling 1 (nesting depth added 4). Of this number, 31 points are the body's own statements and 35 belong to 9 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 · index.TimeEntryReport (cognitive 66) · ×1
  • index.TimeEntryReport (cognitive 66) app/javascript/src/components/Reports/TimeEntryReport/index.tsx:258 — index.TimeEntryReport has cognitive complexity 66 (threshold 15). Drivers by points: boolean chains 33, ternaries 18 (21 pts), if/else 11, error handling 1 (nesting depth added 3). Of this number, 28 points are the body's own statements and 38 belong to 19 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 · index.DeclarationWorkspace (cognitive 66) · ×1
  • index.DeclarationWorkspace (cognitive 66) app/javascript/src/components/TaxDeclarations/index.tsx:66 — index.DeclarationWorkspace has cognitive complexity 66 (threshold 15). Drivers by points: boolean chains 41, ternaries 8 (12 pts), if/else 8 (9 pts), error handling 4 (nesting depth added 5). Of this number, 37 points are the body's own statements and 29 belong to 14 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 · Editor.LoadedEditor (cognitive 64) · ×1
  • Editor.LoadedEditor (cognitive 64) app/javascript/src/components/Agreements/Editor.tsx:27 — Editor.LoadedEditor has cognitive complexity 64 (threshold 15). Drivers by points: boolean chains 30, if/else 23 (27 pts), ternaries 5, error handling 2 (nesting depth added 4). Of this number, 23 points are the body's own statements and 41 belong to 19 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, 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.InvoiceAuthorizationPanel (cognitive 63) · ×1
  • index.InvoiceAuthorizationPanel (cognitive 63) app/javascript/src/components/Profile/InvoiceAuthorization/index.tsx:20 — index.InvoiceAuthorizationPanel has cognitive complexity 63 (threshold 15). Drivers by points: boolean chains 36, if/else 16 (17 pts), ternaries 7 (8 pts), error handling 2 (nesting depth added 2). Of this number, 18 points are the body's own statements and 45 belong to 9 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 · index.PaymentReport (cognitive 63) · ×1
  • index.PaymentReport (cognitive 63) app/javascript/src/components/Reports/PaymentReport/index.tsx:149 — index.PaymentReport has cognitive complexity 63 (threshold 15). Drivers by points: boolean chains 42, ternaries 17 (18 pts), if/else 3 (nesting depth added 1). Of this number, 32 points are the body's own statements and 31 belong to 18 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 · WorkspaceView.OutstandingInvoicesWorkspaceView (cognitive 60) · ×1
  • WorkspaceView.OutstandingInvoicesWorkspaceView (cognitive 60) app/javascript/src/components/Reports/OutstandingInvoiceReport/WorkspaceView.tsx:191 — WorkspaceView.OutstandingInvoicesWorkspaceView has cognitive complexity 60 (threshold 15). Drivers by points: boolean chains 27, ternaries 23 (24 pts), if/else 9 (nesting depth added 1). Of this number, 30 points are the body's own statements and 30 belong to 18 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 · InvoiceList.InvoiceList (cognitive 58) · ×1
  • InvoiceList.InvoiceList (cognitive 58) app/javascript/src/components/Invoices/InvoiceList.tsx:78 — InvoiceList.InvoiceList has cognitive complexity 58 (threshold 15). Drivers by points: boolean chains 34, ternaries 6 (13 pts), if/else 10, error handling 1 (nesting depth added 7). Of this number, 24 points are the body's own statements and 34 belong to 11 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 · index.CompanyDetailsForm (cognitive 57) · ×1
  • index.CompanyDetailsForm (cognitive 57) app/javascript/src/components/OrganizationSetup/CompanyDetailsForm/index.tsx:28 — index.CompanyDetailsForm has cognitive complexity 57 (threshold 15). Drivers by points: boolean chains 34, ternaries 10 (13 pts), if/else 9 (10 pts) (nesting depth added 4). Most of this is not in the body itself: 1 of the 57 points is its own statement and the rest belongs to 8 function items inside it that branch (a function literal at line 219, onLogoChange, a function literal at line 66, …). 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 · Sidebar.ReportFiltersPanel (cognitive 56) · ×1
  • Sidebar.ReportFiltersPanel (cognitive 56) app/javascript/src/components/Reports/Filters/Sidebar.tsx:31 — Sidebar.ReportFiltersPanel has cognitive complexity 56 (threshold 15). Drivers by points: if/else 34 (38 pts), boolean chains 10, ternaries 4 (8 pts) (nesting depth added 8). Most of this is not in the body itself: 3 of the 56 points are its own statements and the rest belongs to 13 function items inside it that branch (a function literal at line 131, a function literal at line 173, getActiveFilterCount, …). 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 · index.RevenueByClientReportFilters (cognitive 55) · ×1
  • index.RevenueByClientReportFilters (cognitive 55) app/javascript/src/components/Reports/RevenueByClientReport/Filters/index.tsx:19 — index.RevenueByClientReportFilters has cognitive complexity 55 (threshold 15). Drivers by points: if/else 25 (26 pts), boolean chains 14, ternaries 9 (13 pts), error handling 2 (nesting depth added 5). Most of this is not in the body itself: 6 of the 55 points are its own statements and the rest belongs to 16 function items inside it that branch (handleSelectFilter, a function literal at line 80, a function literal at line 275, …). 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 · ApplicationForms.ApplicationForms (cognitive 54) · ×1
  • ApplicationForms.ApplicationForms (cognitive 54) app/javascript/src/components/Hiring/ApplicationForms.tsx:32 — ApplicationForms.ApplicationForms has cognitive complexity 54 (threshold 15). Drivers by points: if/else 17 (21 pts), boolean chains 20, ternaries 9 (10 pts), error handling 3 (nesting depth added 5). Of this number, 21 points are the body's own statements and 33 belong to 13 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.SalarySlipArchive (cognitive 54) · ×1
  • index.SalarySlipArchive (cognitive 54) app/javascript/src/components/SalarySlips/index.tsx:36 — index.SalarySlipArchive has cognitive complexity 54 (threshold 15). Drivers by points: boolean chains 26, ternaries 8 (16 pts), if/else 6 (7 pts), error handling 3 (4 pts), loops 1 (nesting depth added 10). Of this number, 30 points are the body's own statements and 24 belong to 13 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 · Onboarding.Onboarding (cognitive 51) · ×1
  • Onboarding.Onboarding (cognitive 51) app/javascript/src/components/Hiring/Onboarding.tsx:61 — Onboarding.Onboarding has cognitive complexity 51 (threshold 15). Drivers by points: boolean chains 32, if/else 12 (14 pts), ternaries 4, error handling 1 (nesting depth added 2). Of this number, 27 points are the body's own statements and 24 belong to 7 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 · ApplicationInterviews.ApplicationInterviews (cognitive 51) · ×1
  • ApplicationInterviews.ApplicationInterviews (cognitive 51) app/javascript/src/components/Hiring/ApplicationInterviews.tsx:41 — ApplicationInterviews.ApplicationInterviews has cognitive complexity 51 (threshold 15). Drivers by points: boolean chains 28, if/else 13 (14 pts), ternaries 8, error handling 1 (nesting depth added 1). Of this number, 24 points are the body's own statements and 27 belong to 14 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 · Pipeline.Pipeline (cognitive 51) · ×1
  • Pipeline.Pipeline (cognitive 51) app/javascript/src/components/Hiring/Pipeline.tsx:56 — Pipeline.Pipeline has cognitive complexity 51 (threshold 15). Drivers by points: ternaries 16 (34 pts), boolean chains 11, if/else 6 (nesting depth added 18). Of this number, 23 points are the body's own statements and 28 belong to 7 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.FilterSidebar (cognitive 51) · ×1
  • index.FilterSidebar (cognitive 51) app/javascript/src/components/Invoices/List/FilterSideBar/index.tsx:22 — index.FilterSidebar has cognitive complexity 51 (threshold 15). Drivers by points: if/else 27 (28 pts), boolean chains 16, ternaries 5 (6 pts), error handling 1 (nesting depth added 2). Most of this is not in the body itself: 14 of the 51 points are its own statements and the rest belongs to 12 function items inside it that branch (handleSelectFilter, a function literal at line 67, a function literal at line 240, …). 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 · ApplicationDecisions.ApplicationDecisions (cognitive 50) · ×1
  • ApplicationDecisions.ApplicationDecisions (cognitive 50) app/javascript/src/components/Hiring/ApplicationDecisions.tsx:71 — ApplicationDecisions.ApplicationDecisions has cognitive complexity 50 (threshold 15). Drivers by points: boolean chains 26, if/else 14 (15 pts), ternaries 6 (8 pts), error handling 1 (nesting depth added 3). Of this number, 22 points are the body's own statements and 28 belong to 9 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 · PortalField.PortalField (cognitive 49) · ×1
  • PortalField.PortalField (cognitive 49) app/javascript/src/components/Hiring/PortalField.tsx:19 — PortalField.PortalField has cognitive complexity 49 (threshold 15). Drivers by points: ternaries 15 (36 pts), boolean chains 12, if/else 1 (nesting depth added 21). Of this number, 42 points are the body's own statements and 7 belong to 3 function items 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 · ClientEditor.ClientEditor (cognitive 49) · ×1
  • ClientEditor.ClientEditor (cognitive 49) app/javascript/src/components/Clients/ClientForm/ClientEditor.tsx:37 — ClientEditor.ClientEditor has cognitive complexity 49 (threshold 15). Drivers by points: boolean chains 30, ternaries 12 (13 pts), error handling 2 (4 pts), if/else 2 (nesting depth added 3). None of this is in the body itself: all 49 points belong to 5 function items inside it that branch (a function literal at line 108, handleSubmit, a function literal at line 58, …). 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 · index.PayrollWorkspace (cognitive 49) · ×1
  • index.PayrollWorkspace (cognitive 49) app/javascript/src/components/ConsultantPayroll/index.tsx:108 — index.PayrollWorkspace has cognitive complexity 49 (threshold 15). Drivers by points: boolean chains 32, ternaries 4 (8 pts), if/else 5, error handling 4 (nesting depth added 4). Of this number, 28 points are the body's own statements and 21 belong to 16 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 · FilterSideBar.TimeEntryReportFilterSidebar (cognitive 49) · ×1
  • FilterSideBar.TimeEntryReportFilterSidebar (cognitive 49) app/javascript/src/components/Reports/Filters/FilterSideBar.tsx:20 — FilterSideBar.TimeEntryReportFilterSidebar has cognitive complexity 49 (threshold 15). Drivers by points: if/else 32 (37 pts), ternaries 3 (7 pts), boolean chains 5 (nesting depth added 9). Most of this is not in the body itself: 1 of the 49 points is its own statement and the rest belongs to 12 function items inside it that branch (a function literal at line 104, a function literal at line 149, handleSelectFilter, …). 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 · CalendarBooking.CalendarBooking (cognitive 48) · ×1
  • CalendarBooking.CalendarBooking (cognitive 48) app/javascript/src/components/Hiring/CalendarBooking.tsx:39 — CalendarBooking.CalendarBooking has cognitive complexity 48 (threshold 15). Drivers by points: boolean chains 25, if/else 16 (19 pts), error handling 3, ternaries 1 (nesting depth added 3). Of this number, 19 points are the body's own statements and 29 belong to 6 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 · index.ChartWithSummary (cognitive 48) · ×1
  • index.ChartWithSummary (cognitive 48) app/javascript/src/components/Invoices/ChartWithSummary/index.tsx:34 — index.ChartWithSummary has cognitive complexity 48 (threshold 15). Drivers by points: ternaries 17 (26 pts), if/else 10 (12 pts), boolean chains 10 (nesting depth added 11). Most of this is not in the body itself: 12 of the 48 points are its own statements and the rest belongs to 10 function items inside it that branch (a function literal at line 149, parseNumber, a function literal at line 87, …). 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 · index.Invoices (cognitive 47) · ×1
  • index.Invoices (cognitive 47) app/javascript/src/components/Invoices/List/index.tsx:24 — index.Invoices has cognitive complexity 47 (threshold 15). Drivers by points: boolean chains 21, if/else 15 (18 pts), ternaries 4, error handling 3, loops 1 (nesting depth added 3). Most of this is not in the body itself: 4 of the 47 points are its own statements and the rest belongs to 12 function items inside it that branch (loadInvoices, InvoicesLayout, fetchPaymentSettings, …). 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 · index.RevenueByClientReport (cognitive 47) · ×1
  • index.RevenueByClientReport (cognitive 47) app/javascript/src/components/Reports/RevenueByClientReport/index.tsx:150 — index.RevenueByClientReport has cognitive complexity 47 (threshold 15). Drivers by points: boolean chains 30, ternaries 13 (14 pts), if/else 3 (nesting depth added 1). Of this number, 25 points are the body's own statements and 22 belong to 13 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 · PaymentsTable.PaymentsTable (cognitive 47) · ×1
  • PaymentsTable.PaymentsTable (cognitive 47) app/javascript/src/components/payments/PaymentsTable.tsx:106 — PaymentsTable.PaymentsTable has cognitive complexity 47 (threshold 15). Drivers by points: boolean chains 23, ternaries 8 (11 pts), if/else 6, error handling 5, match/switch 2 (nesting depth added 3). Of this number, 18 points are the body's own statements and 29 belong to 18 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 · enhanced-search.UnifiedSearch (cognitive 46) · ×1
  • enhanced-search.UnifiedSearch (cognitive 46) REDACTED:321 — enhanced-search.UnifiedSearch has cognitive complexity 46 (threshold 15). Drivers by points: boolean chains 25, if/else 14 (15 pts), ternaries 3 (5 pts), error handling 1 (nesting depth added 3). Of this number, 25 points are the body's own statements and 21 belong to 11 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 · Review.Review (cognitive 46) · ×1
  • Review.Review (cognitive 46) app/javascript/src/components/Payroll/Review.tsx:405 — Review.Review has cognitive complexity 46 (threshold 15). Drivers by points: boolean chains 22, if/else 8 (13 pts), ternaries 4 (10 pts), error handling 1 (nesting depth added 11). Of this number, 19 points are the body's own statements and 27 belong to 3 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 · AssignmentTemplateEditor.AssignmentTemplateEditor (cognitive 45) · ×1
  • AssignmentTemplateEditor.AssignmentTemplateEditor (cognitive 45) app/javascript/src/components/Hiring/AssignmentTemplateEditor.tsx:31 — AssignmentTemplateEditor.AssignmentTemplateEditor has cognitive complexity 45 (threshold 15). Drivers by points: boolean chains 19, ternaries 9 (16 pts), if/else 8 (9 pts), error handling 1 (nesting depth added 8). Most of this is not in the body itself: 12 of the 45 points are its own statements and the rest belongs to 13 function items inside it that branch (save, a function literal at line 67, a function literal at line 384, …). 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 · index.BillingIdentityPanel (cognitive 45) · ×1
  • index.BillingIdentityPanel (cognitive 45) app/javascript/src/components/Profile/BillingIdentity/index.tsx:61 — index.BillingIdentityPanel has cognitive complexity 45 (threshold 15). Drivers by points: boolean chains 77, if/else 24 (25 pts), ternaries 11 (12 pts), error handling 4 (5 pts) (nesting depth added 3). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators. This shape REPEATS in the file: one other method here (index.BillingIdentityPanel::failed) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D2 · Cognitive Complexity · animated-time-input.AnimatedTimeInput (cognitive 45) · ×1
  • animated-time-input.AnimatedTimeInput (cognitive 45) app/javascript/src/components/ui/animated-time-input.tsx:98 — animated-time-input.AnimatedTimeInput has cognitive complexity 45 (threshold 15). Drivers by points: boolean chains 17, if/else 11 (12 pts), ternaries 8 (11 pts), match/switch 5 (nesting depth added 4). Of this number, 18 points are the body's own statements and 27 belong to 12 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 · AppWithUserData.AppWithUserData (cognitive 44) · ×1
  • AppWithUserData.AppWithUserData (cognitive 44) app/javascript/src/components/AppWithUserData.tsx:104 — AppWithUserData.AppWithUserData has cognitive complexity 44 (threshold 15). Drivers by points: if/else 21 (29 pts), boolean chains 12, ternaries 2, error handling 1 (nesting depth added 8). Most of this is not in the body itself: 6 of the 44 points are its own statements and the rest belongs to 9 function items inside it that branch (a function literal at line 148, a function literal at line 118, a function literal at line 283, …). 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 · index.CustomDateRangePicker (cognitive 44) · ×1
  • index.CustomDateRangePicker (cognitive 44) app/javascript/src/common/CustomDateRangePicker/index.tsx:16 — index.CustomDateRangePicker has cognitive complexity 44 (threshold 15). Drivers by points: if/else 18 (21 pts), boolean chains 18, ternaries 5 (nesting depth added 3). Most of this is not in the body itself: 4 of the 44 points are its own statements and the rest belongs to 8 function items inside it that branch (checkIsValidDateRange, validateDateInput, showDateInputErrorMessage, …). 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 · Sidebar.SidebarItem (cognitive 44) · ×1
  • Sidebar.SidebarItem (cognitive 44) app/javascript/src/components/Dashboard/Sidebar.tsx:64 — Sidebar.SidebarItem has cognitive complexity 44 (threshold 15). Drivers by points: ternaries 10 (28 pts), boolean chains 15, if/else 1 (nesting depth added 18). Of this number, 35 points are the body's own statements and 9 belong to 2 function items 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 · DashboardTimerControl.DashboardTimerControl (cognitive 43) · ×1
  • DashboardTimerControl.DashboardTimerControl (cognitive 43) app/javascript/src/components/Dashboard/DashboardTimerControl.tsx:42 — DashboardTimerControl.DashboardTimerControl has cognitive complexity 43 (threshold 15). Drivers by points: ternaries 20 (24 pts), boolean chains 12, if/else 6, error handling 1 (nesting depth added 4). Of this number, 25 points are the body's own statements and 18 belong to 12 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 · Portal.Portal (cognitive 42) · ×1
  • Portal.Portal (cognitive 42) app/javascript/src/components/Hiring/Portal.tsx:22 — Portal.Portal has cognitive complexity 42 (threshold 15). Drivers by points: boolean chains 19, if/else 13 (14 pts), ternaries 4 (5 pts), error handling 4 (nesting depth added 2). Most of this is not in the body itself: 14 of the 42 points are its own statements and the rest belongs to 12 function items inside it that branch (a function literal at line 32, uploadResume, refresh, …). 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 · index.CustomDateRangeWithInput (cognitive 42) · ×1
  • index.CustomDateRangeWithInput (cognitive 42) app/javascript/src/common/CustomDateRangeWIthInput/index.tsx:32 — index.CustomDateRangeWithInput has cognitive complexity 42 (threshold 15). Drivers by points: boolean chains 20, if/else 17 (20 pts), ternaries 2 (nesting depth added 3). Most of this is not in the body itself: 10 of the 42 points are its own statements and the rest belongs to 7 function items inside it that branch (checkIsValidDateRange, validateDateInput, showDateInputErrorMessage, …). 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 · ReviewPanel.ReviewPanel (cognitive 42) · ×1
  • ReviewPanel.ReviewPanel (cognitive 42) app/javascript/src/components/DocumentSignatures/ReviewPanel.tsx:10 — ReviewPanel.ReviewPanel has cognitive complexity 42 (threshold 15). Drivers by points: boolean chains 22, ternaries 9 (14 pts), if/else 4, error handling 2 (nesting depth added 5). Of this number, 24 points are the body's own statements and 18 belong to 5 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 · OrgEditForm.OrgEditForm (cognitive 42) · ×1
  • OrgEditForm.OrgEditForm (cognitive 42) app/javascript/src/components/Profile/Organization/Edit/OrgEditForm.tsx:127 — OrgEditForm.OrgEditForm has cognitive complexity 42 (threshold 15). Drivers by points: boolean chains 29, ternaries 7 (8 pts), if/else 5 (nesting depth added 1). Of this number, 37 points are the body's own statements and 5 belong to 5 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 · Picker.Picker (cognitive 41) · ×1
  • Picker.Picker (cognitive 41) app/javascript/src/components/Hiring/Picker.tsx:34 — Picker.Picker has cognitive complexity 41 (threshold 15). Drivers by points: boolean chains 18, if/else 13 (14 pts), ternaries 7 (9 pts) (nesting depth added 3). Most of this is not in the body itself: 9 of the 41 points are its own statements and the rest belongs to 10 function items inside it that branch (a function literal at line 105, a function literal at line 85, a function literal at line 156, …). 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 · ApplicationAssignments.ApplicationAssignments (cognitive 41) · ×1
  • ApplicationAssignments.ApplicationAssignments (cognitive 41) app/javascript/src/components/Hiring/ApplicationAssignments.tsx:63 — ApplicationAssignments.ApplicationAssignments has cognitive complexity 41 (threshold 15). Drivers by points: boolean chains 51, if/else 27 (33 pts), ternaries 4 (6 pts), error handling 3 (nesting depth added 8). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators. This shape REPEATS in the file: one other method here (ApplicationAssignments.ApplicationAssignments::save) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D2 · Cognitive Complexity · index.InvoicePreview (cognitive 41) · ×1
  • index.InvoicePreview (cognitive 41) app/javascript/src/components/Invoices/InvoicePreview/index.tsx:90 — index.InvoicePreview has cognitive complexity 41 (threshold 15). Drivers by points: boolean chains 55, if/else 23 (27 pts), ternaries 8 (13 pts), error handling 3, match/switch 2 (3 pts) (nesting depth added 10). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators. This shape REPEATS in the file: one other method here (index.InvoicePreview::handleSendSubmit) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D2 · Cognitive Complexity · index.InvoicesPage (cognitive 41) · ×1
  • index.InvoicesPage (cognitive 41) app/javascript/src/components/Invoices/index.tsx:38 — index.InvoicesPage has cognitive complexity 41 (threshold 15). Drivers by points: if/else 41 (58 pts), boolean chains 48, ternaries 7 (15 pts), error handling 11, match/switch 2 (3 pts) (nesting depth added 26). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (index.InvoicesPage::handleInvoiceAction) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D2 · Cognitive Complexity · MobileProfileEditor.MobileProfileEditor (cognitive 41) · ×1
  • MobileProfileEditor.MobileProfileEditor (cognitive 41) app/javascript/src/components/Profile/Personal/User/Edit/MobileProfileEditor.tsx:30 — MobileProfileEditor.MobileProfileEditor has cognitive complexity 41 (threshold 15). Drivers by points: boolean chains 21, ternaries 18, if/else 2. Of this number, 38 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 · index.AccountsAgingReport (cognitive 41) · ×1
  • index.AccountsAgingReport (cognitive 41) app/javascript/src/components/Reports/AccountsAgingReport/index.tsx:105 — index.AccountsAgingReport has cognitive complexity 41 (threshold 15). Drivers by points: boolean chains 26, ternaries 9, if/else 5 (6 pts) (nesting depth added 1). Of this number, 19 points are the body's own statements and 22 belong to 15 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 · PaymentEntryForm.PaymentEntryForm (cognitive 41) · ×1
  • PaymentEntryForm.PaymentEntryForm (cognitive 41) app/javascript/src/components/payments/Modals/PaymentEntryForm.tsx:31 — PaymentEntryForm.PaymentEntryForm has cognitive complexity 41 (threshold 15). Drivers by points: boolean chains 17, if/else 9 (11 pts), ternaries 9 (11 pts), error handling 1, match/switch 1 (nesting depth added 4). Most of this is not in the body itself: 3 of the 41 points are its own statements and the rest belongs to 10 function items inside it that branch (a function literal at line 159, a function literal at line 198, handleAddPayment, …). 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 · AssessmentPortal.AssessmentPortal (cognitive 40) · ×1
  • AssessmentPortal.AssessmentPortal (cognitive 40) app/javascript/src/components/Hiring/AssessmentPortal.tsx:32 — AssessmentPortal.AssessmentPortal has cognitive complexity 40 (threshold 15). Drivers by points: boolean chains 17, if/else 14 (15 pts), ternaries 4 (5 pts), error handling 3 (nesting depth added 2). Most of this is not in the body itself: 14 of the 40 points are its own statements and the rest belongs to 11 function items inside it that branch (a function literal at line 42, refresh, mutate, …). 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 · Sidebar.Sidebar (cognitive 40) · ×1
  • Sidebar.Sidebar (cognitive 40) app/javascript/src/components/Navbar/Sidebar.tsx:63 — Sidebar.Sidebar has cognitive complexity 40 (threshold 15). Drivers by points: boolean chains 28, if/else 5, ternaries 5, error handling 2. Of this number, 23 points are the body's own statements and 17 belong to 5 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 · index.EmploymentDetailsEdit (cognitive 40) · ×1
  • index.EmploymentDetailsEdit (cognitive 40) app/javascript/src/components/Profile/Personal/Employment/Edit/index.tsx:28 — index.EmploymentDetailsEdit has cognitive complexity 40 (threshold 15). Drivers by points: if/else 20 (29 pts), boolean chains 5, ternaries 4, error handling 2 (nesting depth added 9). Most of this is not in the body itself: 5 of the 40 points are its own statements and the rest belongs to 10 function items inside it that branch (updateEmploymentDetails, getDetails, a function literal at line 73, …). 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 · Fields.FieldValue (cognitive 39) · ×1
  • Fields.FieldValue (cognitive 39) app/javascript/src/components/Agreements/Fields.tsx:61 — Fields.FieldValue has cognitive complexity 39 (threshold 15). Drivers by points: ternaries 12 (35 pts), boolean chains 4 (nesting depth added 23). Of this number, 25 points are the body's own statements and 14 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 · ExpenseTrendsPage.ExpenseTrendsPage (cognitive 39) · ×1
  • ExpenseTrendsPage.ExpenseTrendsPage (cognitive 39) app/javascript/src/components/Analytics/ExpenseTrendsPage.tsx:54 — ExpenseTrendsPage.ExpenseTrendsPage has cognitive complexity 39 (threshold 15). Drivers by points: ternaries 16 (21 pts), boolean chains 18 (nesting depth added 5). Of this number, 31 points are the body's own statements and 8 belong to 6 function literals 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 · ClientInsightsPage.ClientInsightsPage (cognitive 37) · ×1
  • ClientInsightsPage.ClientInsightsPage (cognitive 37) app/javascript/src/components/Analytics/ClientInsightsPage.tsx:52 — ClientInsightsPage.ClientInsightsPage has cognitive complexity 37 (threshold 15). Drivers by points: ternaries 15 (21 pts), boolean chains 16 (nesting depth added 6). Of this number, 31 points are the body's own statements and 6 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 · DashboardHome.DashboardHome (cognitive 37) · ×1
  • DashboardHome.DashboardHome (cognitive 37) app/javascript/src/components/Dashboard/DashboardHome.tsx:33 — DashboardHome.DashboardHome has cognitive complexity 37 (threshold 15). Drivers by points: boolean chains 21, ternaries 7 (8 pts), if/else 4 (5 pts), match/switch 3 (nesting depth added 2). Of this number, 22 points are the body's own statements and 15 belong to 8 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 · Reports.Reports (cognitive 37) · ×1
  • Reports.Reports (cognitive 37) app/javascript/src/components/Profile/EmployeeRecords/Reports.tsx:9 — Reports.Reports has cognitive complexity 37 (threshold 15). Drivers by points: if/else 12 (19 pts), boolean chains 12, ternaries 3 (5 pts), error handling 1 (nesting depth added 9). Most of this is not in the body itself: 10 of the 37 points are its own statements and the rest belongs to 7 function items inside it that branch (a function literal at line 89, perform, load, …). 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 · index.PreferencesSettingsPage (cognitive 37) · ×1
  • index.PreferencesSettingsPage (cognitive 37) app/javascript/src/components/Settings/Preferences/index.tsx:51 — index.PreferencesSettingsPage has cognitive complexity 37 (threshold 15). Drivers by points: boolean chains 18, if/else 14, ternaries 3, error handling 2. Most of this is not in the body itself: 5 of the 37 points are its own statements and the rest belongs to 15 function items inside it that branch (fetchPreferences, a function literal at line 426, handleToggle, …). 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 · AssignmentReviews.ReviewDetail (cognitive 36) · ×1
  • AssignmentReviews.ReviewDetail (cognitive 36) app/javascript/src/components/Hiring/AssignmentReviews.tsx:36 — AssignmentReviews.ReviewDetail has cognitive complexity 36 (threshold 15). Drivers by points: boolean chains 18, if/else 14 (16 pts), error handling 2 (nesting depth added 2). Most of this is not in the body itself: 14 of the 36 points are its own statements and the rest belongs to 8 function items inside it that branch (save, download, failed, …). 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 · AccountSecurity.AccountSecurity (cognitive 36) · ×1
  • AccountSecurity.AccountSecurity (cognitive 36) app/javascript/src/components/Profile/Personal/User/AccountSecurity.tsx:28 — AccountSecurity.AccountSecurity has cognitive complexity 36 (threshold 15). Drivers by points: ternaries 8 (17 pts), boolean chains 12, error handling 4, if/else 3 (nesting depth added 9). Most of this is not in the body itself: 14 of the 36 points are its own statements and the rest belongs to 9 function items inside it that branch (confirmAction, a function literal at line 285, a function literal at line 267, …). 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 · Editor.OrganizationHolidaysEditor (cognitive 36) · ×1
  • Editor.OrganizationHolidaysEditor (cognitive 36) app/javascript/src/components/Profile/Organization/Holidays/Editor.tsx:85 — Editor.OrganizationHolidaysEditor has cognitive complexity 36 (threshold 15). Drivers by points: boolean chains 23, ternaries 6 (7 pts), if/else 5 (6 pts) (nesting depth added 2). Of this number, 28 points are the body's own statements and 8 belong to 9 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 · LeaveManagementContent.LeaveManagementContent (cognitive 35) · ×1
  • LeaveManagementContent.LeaveManagementContent (cognitive 35) app/javascript/src/components/LeaveManagement/LeaveManagementContent.tsx:45 — LeaveManagementContent.LeaveManagementContent has cognitive complexity 35 (threshold 15). Drivers by points: boolean chains 20, ternaries 9 (12 pts), if/else 3 (nesting depth added 3). Most of this is not in the body itself: 14 of the 35 points are its own statements and the rest belongs to 9 function items inside it that branch (renderEntryCard, a function literal at line 121, a function literal at line 87, …). 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 · ApplicationScreening.ApplicationScreening (cognitive 34) · ×1
  • ApplicationScreening.ApplicationScreening (cognitive 34) app/javascript/src/components/Hiring/ApplicationScreening.tsx:55 — ApplicationScreening.ApplicationScreening has cognitive complexity 34 (threshold 15). Drivers by points: boolean chains 21, if/else 10 (11 pts), error handling 1, ternaries 1 (nesting depth added 1). Of this number, 18 points are the body's own statements and 16 belong to 6 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 · InterviewPanel.InterviewPanel (cognitive 34) · ×1
  • InterviewPanel.InterviewPanel (cognitive 34) app/javascript/src/components/Hiring/InterviewPanel.tsx:20 — InterviewPanel.InterviewPanel has cognitive complexity 34 (threshold 15). Drivers by points: boolean chains 19, if/else 9 (10 pts), ternaries 4, error handling 1 (nesting depth added 1). Of this number, 17 points are the body's own statements and 17 belong to 8 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 · PdfPages.PdfPages (cognitive 33) · ×1
  • PdfPages.PdfPages (cognitive 33) app/javascript/src/components/DocumentSignatures/PdfPages.tsx:36 — PdfPages.PdfPages has cognitive complexity 33 (threshold 15). Drivers by points: boolean chains 14, if/else 13, ternaries 5 (6 pts) (nesting depth added 1). Most of this is not in the body itself: 9 of the 33 points are its own statements and the rest belongs to 13 function items inside it that branch (a function literal at line 126, move, keyboard, …). 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 · InfiniteScrollRecentlyUpdated.InfiniteScrollRecentlyUpdated (cognitive 33) · ×1
  • InfiniteScrollRecentlyUpdated.InfiniteScrollRecentlyUpdated (cognitive 33) app/javascript/src/components/Invoices/List/RecentlyUpdated/InfiniteScrollRecentlyUpdated.tsx:25 — InfiniteScrollRecentlyUpdated.InfiniteScrollRecentlyUpdated has cognitive complexity 33 (threshold 15). Drivers by points: boolean chains 20, if/else 11 (12 pts), error handling 1 (nesting depth added 1). Most of this is not in the body itself: 9 of the 33 points are its own statements and the rest belongs to 7 function literals inside it that branch (lines 71, 54, 42, …). 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 · ProfileEditor.ProfileEditor (cognitive 33) · ×1
  • ProfileEditor.ProfileEditor (cognitive 33) app/javascript/src/components/Profile/Personal/User/Edit/ProfileEditor.tsx:32 — ProfileEditor.ProfileEditor has cognitive complexity 33 (threshold 15). Drivers by points: boolean chains 22, ternaries 10, error handling 1. 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, 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 · Fields.Fields (cognitive 32) · ×1
  • Fields.Fields (cognitive 32) app/javascript/src/components/Agreements/Fields.tsx:134 — Fields.Fields has cognitive complexity 32 (threshold 15). Drivers by points: boolean chains 18, ternaries 8 (9 pts), if/else 5 (nesting depth added 1). Most of this is not in the body itself: 7 of the 32 points are its own statements and the rest belongs to 9 function items inside it that branch (save, edit, a function literal at line 255, …). 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 · ClientsTable.ClientsTable (cognitive 32) · ×1
  • ClientsTable.ClientsTable (cognitive 32) app/javascript/src/components/Clients/ClientsTable.tsx:78 — ClientsTable.ClientsTable has cognitive complexity 32 (threshold 15). Drivers by points: boolean chains 12, ternaries 9 (12 pts), if/else 7, error handling 1 (nesting depth added 3). Of this number, 17 points are the body's own statements and 15 belong to 10 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 · PtoPanel.PtoPanel (cognitive 32) · ×1
  • PtoPanel.PtoPanel (cognitive 32) app/javascript/src/components/Payroll/PtoPanel.tsx:279 — PtoPanel.PtoPanel has cognitive complexity 32 (threshold 15). Drivers by points: boolean chains 29, if/else 2, error handling 1. Of this number, 29 points are the body's own statements and 3 belong to 9 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 · WeeklyEntriesCard.WeeklyEntriesCard (cognitive 32) · ×1
  • WeeklyEntriesCard.WeeklyEntriesCard (cognitive 32) app/javascript/src/components/TimeTracking/WeeklyEntriesCard.tsx:16 — WeeklyEntriesCard.WeeklyEntriesCard has cognitive complexity 32 (threshold 15). Drivers by points: if/else 13 (15 pts), ternaries 7 (9 pts), boolean chains 6, error handling 2 (nesting depth added 4). Most of this is not in the body itself: 5 of the 32 points are its own statements and the rest belongs to 10 function items inside it that branch (handleDurationClick, handleSaveEntry, a function literal at line 189, …). 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 · ExpenseForm.ExpenseForm (cognitive 31) · ×1
  • ExpenseForm.ExpenseForm (cognitive 31) app/javascript/src/components/Expenses/Modals/ExpenseForm.tsx:35 — ExpenseForm.ExpenseForm has cognitive complexity 31 (threshold 15). Drivers by points: boolean chains 22, if/else 5, ternaries 4. Of this number, 16 points are the body's own statements and 15 belong to 8 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 · Settings.Settings (cognitive 31) · ×1
  • Settings.Settings (cognitive 31) app/javascript/src/components/Hiring/Settings.tsx:25 — Settings.Settings has cognitive complexity 31 (threshold 15). Drivers by points: boolean chains 17, if/else 7 (8 pts), ternaries 4 (5 pts), error handling 1 (nesting depth added 2). Of this number, 17 points are the body's own statements and 14 belong to 8 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 · index.OrgEdit (cognitive 31) · ×1
  • index.OrgEdit (cognitive 31) app/javascript/src/components/Profile/Organization/Edit/index.tsx:146 — index.OrgEdit has cognitive complexity 31 (threshold 15). Drivers by points: boolean chains 20, if/else 7, error handling 2, ternaries 2. Most of this is not in the body itself: 1 of the 31 points is its own statement and the rest belongs to 7 function items inside it that branch (getData, updateOrgDetails, a function literal at line 294, …). 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 · AddEditProject.AddEditProject (cognitive 31) · ×1
  • AddEditProject.AddEditProject (cognitive 31) app/javascript/src/components/Projects/Modals/AddEditProject.tsx:25 — AddEditProject.AddEditProject has cognitive complexity 31 (threshold 15). Drivers by points: boolean chains 11, ternaries 6 (9 pts), if/else 7 (8 pts), error handling 2 (3 pts) (nesting depth added 5). Most of this is not in the body itself: 14 of the 31 points are its own statements and the rest belongs to 6 function items inside it that branch (handleProjectData, getProject, getClientList, …). 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 · InterviewFeedback.FeedbackForm (cognitive 30) · ×1
  • InterviewFeedback.FeedbackForm (cognitive 30) app/javascript/src/components/Hiring/InterviewFeedback.tsx:47 — InterviewFeedback.FeedbackForm has cognitive complexity 30 (threshold 15). Drivers by points: boolean chains 15, if/else 9 (12 pts), ternaries 2, error handling 1 (nesting depth added 3). Most of this is not in the body itself: 13 of the 30 points are its own statements and the rest belongs to 7 function items inside it that branch (submit, a function literal at line 65, a function literal at line 76, …). 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 · index.Filters (cognitive 30) · ×1
  • index.Filters (cognitive 30) app/javascript/src/components/Invoices/MultipleEntriesModal/Filters/index.tsx:19 — index.Filters has cognitive complexity 30 (threshold 15). Drivers by points: if/else 14 (15 pts), boolean chains 9, ternaries 6 (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 10 function items inside it that branch (a function literal at line 52, handleSelectFilter, defaultDateRange, …). 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 · MercuryPayments.Consultant (cognitive 30) · ×1
  • MercuryPayments.Consultant (cognitive 30) app/javascript/src/components/Payroll/MercuryPayments.tsx:876 — MercuryPayments.Consultant has cognitive complexity 30 (threshold 15). Drivers by points: ternaries 7 (18 pts), boolean chains 12 (nesting depth added 11). 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, 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 · ProjectForm.ProjectForm (cognitive 30) · ×1
  • ProjectForm.ProjectForm (cognitive 30) app/javascript/src/components/Projects/List/Mobile/ProjectForm.tsx:19 — ProjectForm.ProjectForm has cognitive complexity 30 (threshold 15). Drivers by points: if/else 12 (13 pts), ternaries 8 (9 pts), boolean chains 8 (nesting depth added 2). Most of this is not in the body itself: 6 of the 30 points are its own statements and the rest belongs to 9 function items inside it that branch (a function literal at line 170, a function literal at line 125, getProject, …). 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 · ProjectsTable.ProjectsTable (cognitive 30) · ×1
  • ProjectsTable.ProjectsTable (cognitive 30) app/javascript/src/components/Projects/ProjectsTable.tsx:66 — ProjectsTable.ProjectsTable has cognitive complexity 30 (threshold 15). Drivers by points: boolean chains 15, ternaries 7 (9 pts), if/else 4, match/switch 2 (nesting depth added 2). Most of this is not in the body itself: 10 of the 30 points are its own statements and the rest belongs to 15 function items inside it that branch (a function literal at line 168, a function literal at line 274, a function literal at line 237, …). 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 · MobileEntryForm.AddEntryMobile (cognitive 30) · ×1
  • MobileEntryForm.AddEntryMobile (cognitive 30) app/javascript/src/components/TimesheetEntries/TimeEntryForm/MobileEntryForm.tsx:29 — MobileEntryForm.AddEntryMobile has cognitive complexity 30 (threshold 15). Drivers by points: if/else 12 (14 pts), boolean chains 11, ternaries 5 (nesting depth added 2). Most of this is not in the body itself: 14 of the 30 points are its own statements and the rest belongs to 8 function items inside it that branch (a function literal at line 67, a function literal at line 90, a function literal at line 83, …). 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 · SelectProject.SelectProject (cognitive 29) · ×1
  • SelectProject.SelectProject (cognitive 29) app/javascript/src/components/TimeTracking/SelectProject.tsx:36 — SelectProject.SelectProject has cognitive complexity 29 (threshold 15). Drivers by points: boolean chains 14, if/else 10 (14 pts), ternaries 1 (nesting depth added 4). Most of this is not in the body itself: 8 of the 29 points are its own statements and the rest belongs to 3 function items inside it that branch (handleSaveButton, handleCancelButton, handleClientChange). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · index.AddEntry (cognitive 29) · ×1
  • index.AddEntry (cognitive 29) app/javascript/src/components/TimesheetEntries/TimeEntryForm/index.tsx:14 — index.AddEntry has cognitive complexity 29 (threshold 15). Drivers by points: if/else 14 (21 pts), boolean chains 6, ternaries 2 (nesting depth added 7). Most of this is not in the body itself: 6 of the 29 points are its own statements and the rest belongs to 6 function items inside it that branch (handleEdit, handleSave, handleFillData, …). 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 · TeamAnalyticsPage.TeamAnalyticsPage (cognitive 28) · ×1
  • TeamAnalyticsPage.TeamAnalyticsPage (cognitive 28) app/javascript/src/components/Analytics/TeamAnalyticsPage.tsx:48 — TeamAnalyticsPage.TeamAnalyticsPage has cognitive complexity 28 (threshold 15). Drivers by points: ternaries 14 (18 pts), boolean chains 10 (nesting depth added 4). 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: 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 · AcknowledgementQueue.AcknowledgementQueue (cognitive 28) · ×1
  • AcknowledgementQueue.AcknowledgementQueue (cognitive 28) app/javascript/src/components/Hiring/AcknowledgementQueue.tsx:13 — AcknowledgementQueue.AcknowledgementQueue has cognitive complexity 28 (threshold 15). Drivers by points: boolean chains 10, ternaries 6 (9 pts), if/else 7 (8 pts), error handling 1 (nesting depth added 4). Of this number, 16 points are the body's own statements and 12 belong to 4 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 · chart.ChartTooltipContent (cognitive 27) · ×1
  • chart.ChartTooltipContent (cognitive 27) REDACTED:115 — chart.ChartTooltipContent has cognitive complexity 27 (threshold 15). Drivers by points: boolean chains 14, ternaries 6 (9 pts), if/else 4 (nesting depth added 3). Most of this is not in the body itself: 4 of the 27 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 187, 135). 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 · DashboardLayout.DashboardLayout (cognitive 27) · ×1
  • DashboardLayout.DashboardLayout (cognitive 27) app/javascript/src/components/Dashboard/DashboardLayout.tsx:44 — DashboardLayout.DashboardLayout has cognitive complexity 27 (threshold 15). Drivers by points: boolean chains 18, ternaries 6, if/else 2, error handling 1. Of this number, 16 points are the body's own statements and 11 belong to 8 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 · Mailboxes.Mailboxes (cognitive 27) · ×1
  • Mailboxes.Mailboxes (cognitive 27) app/javascript/src/components/Hiring/Mailboxes.tsx:12 — Mailboxes.Mailboxes has cognitive complexity 27 (threshold 15). Drivers by points: if/else 12 (14 pts), boolean chains 11, error handling 2 (nesting depth added 2). Most of this is not in the body itself: 11 of the 27 points are its own statements and the rest belongs to 7 function items inside it that branch (update, create, 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 · MercuryPayments.Leg (cognitive 27) · ×1
  • MercuryPayments.Leg (cognitive 27) app/javascript/src/components/Payroll/MercuryPayments.tsx:540 — MercuryPayments.Leg has cognitive complexity 27 (threshold 15). Drivers by points: boolean chains 22, ternaries 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 · MobileEntryForm.AddEntryMobile (cognitive 27) · ×1
  • MobileEntryForm.AddEntryMobile (cognitive 27) app/javascript/src/components/TimeTracking/MobileView/MobileEntryForm.tsx:30 — MobileEntryForm.AddEntryMobile has cognitive complexity 27 (threshold 15). Drivers by points: boolean chains 13, ternaries 7 (9 pts), if/else 5 (nesting depth added 2). Of this number, 15 points are the body's own statements and 12 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, 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 · WeeklyEntries.WeeklyEntries (cognitive 27) · ×1
  • WeeklyEntries.WeeklyEntries (cognitive 27) app/javascript/src/components/TimeTracking/WeeklyEntries.tsx:32 — WeeklyEntries.WeeklyEntries has cognitive complexity 27 (threshold 15). Drivers by points: if/else 12 (15 pts), boolean chains 11, error handling 1 (nesting depth added 3). Most of this is not in the body itself: 10 of the 27 points are its own statements and the rest belongs to 7 function items inside it that branch (a function literal at line 68, handleEditEntries, a function literal at line 127, …). 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 · WeeklyEntriesCard.WeeklyEntriesCard (cognitive 27) · ×1
  • WeeklyEntriesCard.WeeklyEntriesCard (cognitive 27) app/javascript/src/components/TimesheetEntries/WeekView/WeeklyEntriesCard.tsx:20 — WeeklyEntriesCard.WeeklyEntriesCard has cognitive complexity 27 (threshold 15). Drivers by points: ternaries 8 (10 pts), if/else 8, boolean chains 7, error handling 2 (nesting depth added 2). Most of this is not in the body itself: 5 of the 27 points are its own statements and the rest belongs to 11 function items inside it that branch (handleDurationClick, a function literal at line 243, handleSaveEntry, …). 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 · verify.evaluateCheck (cognitive 27) · ×1
  • verify.evaluateCheck (cognitive 27) script/launch_matrix/verify.mjs:124 — verify.evaluateCheck has cognitive complexity 27 (threshold 15). Drivers by points: boolean chains 15, if/else 7 (10 pts), loops 2 (nesting depth added 3). Of this number, 26 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 · Review.Review (cognitive 26) · ×1
  • Review.Review (cognitive 26) app/javascript/src/components/DocumentSignatures/Review.tsx:40 — Review.Review has cognitive complexity 26 (threshold 15). Drivers by points: ternaries 5 (9 pts), if/else 6 (7 pts), boolean chains 6, error handling 3 (4 pts) (nesting depth added 6). Most of this is not in the body itself: 10 of the 26 points are its own statements and the rest belongs to 9 function items inside it that branch (a function literal at line 49, loadOlder, a function literal at line 98, …). 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 · InterviewReviews.Handover (cognitive 26) · ×1
  • InterviewReviews.Handover (cognitive 26) app/javascript/src/components/Hiring/InterviewReviews.tsx:13 — InterviewReviews.Handover has cognitive complexity 26 (threshold 15). Drivers by points: boolean chains 17, if/else 7 (8 pts), error handling 1 (nesting depth added 1). Of this number, 16 points are the body's own statements and 10 belong to 5 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 · index.MonthlyRevenueChart (cognitive 26) · ×1
  • index.MonthlyRevenueChart (cognitive 26) app/javascript/src/components/Invoices/MonthlyRevenueChart/index.tsx:42 — index.MonthlyRevenueChart has cognitive complexity 26 (threshold 15). Drivers by points: if/else 9 (10 pts), ternaries 5 (10 pts), boolean chains 5, error handling 1 (nesting depth added 6). Most of this is not in the body itself: 8 of the 26 points are its own statements and the rest belongs to 7 function items inside it that branch (parseNumber, CustomTooltip, a function literal at line 89, …). 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 · index.InvoiceTable (cognitive 26) · ×1
  • index.InvoiceTable (cognitive 26) app/javascript/src/components/Invoices/common/InvoiceTable/index.tsx:13 — index.InvoiceTable has cognitive complexity 26 (threshold 15). Drivers by points: boolean chains 12, if/else 10 (11 pts), ternaries 2 (3 pts) (nesting depth added 2). Most of this is not in the body itself: 6 of the 26 points are its own statements and the rest belongs to 7 function items inside it that branch (handleAddEntry, getAddNewButton, lineItemKey, …). 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 · index.InvoicePreview · ×1
  • index.InvoicePreview::handleSendSubmit (cognitive 26) app/javascript/src/components/Invoices/InvoicePreview/index.tsx:204 — index.InvoicePreview::handleSendSubmit has cognitive complexity 26 (threshold 15). Drivers by points: if/else 11 (14 pts), ternaries 3 (8 pts), boolean chains 3, 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. This shape REPEATS in the file: one other method here (index.InvoicePreview) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D2 · Cognitive Complexity · Page.DeviceEditPage (cognitive 26) · ×1
  • Page.DeviceEditPage (cognitive 26) app/javascript/src/components/Profile/Personal/Devices/Edit/Page.tsx:74 — Page.DeviceEditPage has cognitive complexity 26 (threshold 15). Drivers by points: boolean chains 14, if/else 10 (11 pts), ternaries 1 (nesting depth added 1). Most of this is not in the body itself: 2 of the 26 points are its own statements and the rest belongs to 9 function items inside it that branch (a function literal at line 213, handleCancel, a function literal at line 115, …). 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 · verify.main (cognitive 26) · ×1
  • verify.main (cognitive 26) script/launch_matrix/verify.mjs:193 — verify.main has cognitive complexity 26 (threshold 15). Drivers by points: if/else 6 (14 pts), loops 4 (7 pts), boolean chains 3, ternaries 1 (2 pts) (nesting depth added 12). Of this number, 23 points are the body's own statements and 3 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 · SignatureRequestRevision.valid_archive (cognitive 26) · ×1
  • SignatureRequestRevision.valid_archive (cognitive 26) app/models/signature_request_revision.rb:147 — SignatureRequestRevision.valid_archive has cognitive complexity 26 (threshold 15). Drivers by points: boolean chains 21, if/else 4 (5 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 · index.AnalyticsHome (cognitive 25) · ×1
  • index.AnalyticsHome (cognitive 25) app/javascript/src/components/Analytics/index.tsx:65 — index.AnalyticsHome has cognitive complexity 25 (threshold 15). Drivers by points: ternaries 9 (15 pts), boolean chains 8, if/else 1 (2 pts) (nesting depth added 7). Of this number, 23 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 · index.FinancialDetailsForm (cognitive 25) · ×1
  • index.FinancialDetailsForm (cognitive 25) app/javascript/src/components/OrganizationSetup/FinancialDetailsForm/index.tsx:25 — index.FinancialDetailsForm has cognitive complexity 25 (threshold 15). Drivers by points: boolean chains 14, ternaries 8, if/else 3. 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 items inside it that branch (a function literal at line 64, isBtnDisabled, a function literal at line 76, …). 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 · index.UserDetailsEdit · ×1
  • index.UserDetailsEdit::handleUpdateDetails (cognitive 25) app/javascript/src/components/Profile/Personal/User/Edit/index.tsx:212 — index.UserDetailsEdit::handleUpdateDetails has cognitive complexity 25 (threshold 15). Drivers by points: if/else 13 (19 pts), ternaries 3, boolean chains 2, error handling 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (index.UserDetailsEdit) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D2 · Cognitive Complexity · AddEditMember.EditClient (cognitive 25) · ×1
  • AddEditMember.EditClient (cognitive 25) app/javascript/src/components/Team/modals/AddEditMember.tsx:53 — AddEditMember.EditClient has cognitive complexity 25 (threshold 15). Drivers by points: if/else 10 (12 pts), boolean chains 8, ternaries 2 (4 pts), error handling 1 (nesting depth added 4). Most of this is not in the body itself: 1 of the 25 points is its own statement and the rest belongs to 4 function items inside it that branch (handleSubmit, a function literal at line 144, a function literal at line 60, …). 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 · Delivery.process (cognitive 25) · ×1
  • Delivery.process (cognitive 25) app/services/signatures/delivery.rb:13 — Delivery.process has cognitive complexity 25 (threshold 15). Drivers by points: error handling 6 (21 pts), if/else 2, boolean chains 1, match/switch 1 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · RevenueForecastPage.RevenueForecastPage (cognitive 24) · ×1
  • RevenueForecastPage.RevenueForecastPage (cognitive 24) app/javascript/src/components/Analytics/RevenueForecastPage.tsx:83 — RevenueForecastPage.RevenueForecastPage has cognitive complexity 24 (threshold 15). Drivers by points: boolean chains 13, ternaries 10 (11 pts) (nesting depth added 1). Of this number, 18 points are the body's own statements and 6 belong to 4 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 · SignInForm.SignInForm (cognitive 24) · ×1
  • SignInForm.SignInForm (cognitive 24) REDACTED:31 — SignInForm.SignInForm has cognitive complexity 24 (threshold 15). Drivers by points: boolean chains 11, if/else 10 (11 pts), error handling 1, ternaries 1 (nesting depth added 1). Most of this is not in the body itself: 4 of the 24 points are its own statements and the rest belongs to 8 function items inside it that branch (handleSignInFormSubmit, completeLogin, a function literal at line 196, …). 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 · SignUpForm.SignUpForm (cognitive 24) · ×1
  • SignUpForm.SignUpForm (cognitive 24) REDACTED:30 — SignUpForm.SignUpForm has cognitive complexity 24 (threshold 15). Drivers by points: boolean chains 14, if/else 6 (8 pts), error handling 1, ternaries 1 (nesting depth added 2). Most of this is not in the body itself: 3 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 174, showPasswordCriteria, handleSignUpFormSubmit, …). 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 · ApplicationAssignments.ApplicationAssignments · ×1
  • ApplicationAssignments.ApplicationAssignments::save (cognitive 24) app/javascript/src/components/Hiring/ApplicationAssignments.tsx:194 — ApplicationAssignments.ApplicationAssignments::save has cognitive complexity 24 (threshold 15). Drivers by points: if/else 11 (13 pts), boolean chains 6, ternaries 3 (4 pts), error handling 1 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition. This shape REPEATS in the file: one other method here (ApplicationAssignments.ApplicationAssignments) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D2 · Cognitive Complexity · index.Applications (cognitive 24) · ×1
  • index.Applications (cognitive 24) app/javascript/src/components/Hiring/index.tsx:28 — index.Applications has cognitive complexity 24 (threshold 15). Drivers by points: ternaries 5 (14 pts), boolean chains 8, if/else 2 (nesting depth added 9). Of this number, 17 points are the body's own statements and 7 belong to 4 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 · ClientSelection.ClientSelection (cognitive 24) · ×1
  • ClientSelection.ClientSelection (cognitive 24) app/javascript/src/components/Invoices/common/InvoiceDetails/ClientSelection.tsx:12 — ClientSelection.ClientSelection has cognitive complexity 24 (threshold 15). Drivers by points: if/else 11 (15 pts), boolean chains 5, ternaries 1 (4 pts) (nesting depth added 7). Most of this is not in the body itself: 3 of the 24 points are its own statements and the rest belongs to 4 function items inside it that branch (autoGenerateInvoiceNumber, a function literal at line 36, handleClientChange, …). 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 · Review.Line (cognitive 24) · ×1
  • Review.Line (cognitive 24) app/javascript/src/components/Payroll/Review.tsx:111 — Review.Line has cognitive complexity 24 (threshold 15). Drivers by points: ternaries 11 (16 pts), boolean chains 8 (nesting depth added 5). Of this number, 19 points are the body's own statements and 5 belong to 3 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 · PersonalProfileSummary.PersonalProfileSummary (cognitive 24) · ×1
  • PersonalProfileSummary.PersonalProfileSummary (cognitive 24) app/javascript/src/components/Profile/Personal/User/PersonalProfileSummary.tsx:25 — PersonalProfileSummary.PersonalProfileSummary has cognitive complexity 24 (threshold 15). Drivers by points: boolean chains 13, if/else 7, ternaries 4. Of this number, 16 points are the body's own statements and 8 belong to one function item 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 · index.UserDetailsView (cognitive 24) · ×1
  • index.UserDetailsView (cognitive 24) app/javascript/src/components/Profile/Personal/User/index.tsx:23 — index.UserDetailsView has cognitive complexity 24 (threshold 15). Drivers by points: if/else 8 (10 pts), boolean chains 7, ternaries 5 (6 pts), error handling 1 (nesting depth added 3). Of this number, 12 points are the body's own statements and 12 belong to 3 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, 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.InvoiceSignature (cognitive 24) · ×1
  • index.InvoiceSignature (cognitive 24) app/javascript/src/components/Profile/Organization/InvoiceSignature/index.tsx:14 — index.InvoiceSignature has cognitive complexity 24 (threshold 15). Drivers by points: ternaries 4 (9 pts), boolean chains 6, if/else 6, error handling 3 (nesting depth added 5). Of this number, 13 points are the body's own statements and 11 belong to 3 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ProfileImageCard.ProfileImageCard (cognitive 24) · ×1
  • ProfileImageCard.ProfileImageCard (cognitive 24) app/javascript/src/components/Profile/Personal/User/Edit/ProfileImageCard.tsx:126 — ProfileImageCard.ProfileImageCard has cognitive complexity 24 (threshold 15). Drivers by points: if/else 9, boolean chains 8, ternaries 4, error handling 3. Most of this is not in the body itself: 8 of the 24 points are its own statements and the rest belongs to 7 function items inside it that branch (handleFileSelection, handleCropUpload, handleDelete, …). 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 · Configuration.valid_value? (cognitive 24) · ×1
  • Configuration.valid_value? (cognitive 24) app/services/signatures/configuration.rb:98 — Configuration.valid_value? has cognitive complexity 24 (threshold 15). Drivers by points: boolean chains 17, if/else 5, error handling 1, match/switch 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 · Roles.Roles (cognitive 23) · ×1
  • Roles.Roles (cognitive 23) app/javascript/src/components/Hiring/Roles.tsx:90 — Roles.Roles has cognitive complexity 23 (threshold 15). Drivers by points: if/else 9 (11 pts), boolean chains 6, ternaries 3 (4 pts), error handling 2 (nesting depth added 3). Most of this is not in the body itself: 7 of the 23 points are its own statements and the rest belongs to 5 function items inside it that branch (create, save, a function literal at line 292, …). 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 · index.MultipleEntriesModal (cognitive 23) · ×1
  • index.MultipleEntriesModal (cognitive 23) app/javascript/src/components/Invoices/MultipleEntriesModal/index.tsx:19 — index.MultipleEntriesModal has cognitive complexity 23 (threshold 15). Drivers by points: ternaries 5 (11 pts), if/else 9 (10 pts), boolean chains 2 (nesting depth added 7). Most of this is not in the body itself: 11 of the 23 points are its own statements and the rest belongs to 5 function items inside it that branch (handleFilterParams, a function literal at line 44, handleSelectAll, …). 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 · RunPreparation.ConsultantRow (cognitive 23) · ×1
  • RunPreparation.ConsultantRow (cognitive 23) app/javascript/src/components/Payroll/RunPreparation.tsx:289 — RunPreparation.ConsultantRow has cognitive complexity 23 (threshold 15). Drivers by points: boolean chains 18, ternaries 4 (5 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 · UserInformation.UserInformation (cognitive 23) · ×1
  • UserInformation.UserInformation (cognitive 23) app/javascript/src/components/Profile/Layout/Navigation/UserInformation.tsx:10 — UserInformation.UserInformation has cognitive complexity 23 (threshold 15). Drivers by points: boolean chains 11, if/else 7, error handling 3, ternaries 2. Most of this is not in the body itself: 8 of the 23 points are its own statements and the rest belongs to 5 function items inside it that branch (getAvatar, handleProfileImageChange, handleDeleteProfileImage, …). 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 · Page.OrganizationSettingsPage (cognitive 23) · ×1
  • Page.OrganizationSettingsPage (cognitive 23) app/javascript/src/components/Profile/Organization/Details/Page.tsx:44 — Page.OrganizationSettingsPage has cognitive complexity 23 (threshold 15). Drivers by points: boolean chains 19, if/else 9 (15 pts), ternaries 7 (15 pts), 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. This shape REPEATS in the file: one other method here (Page.OrganizationSettingsPage::formatAddress) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D2 · Cognitive Complexity · PayrollPtoReviewJob.perform (cognitive 23) · ×1
  • PayrollPtoReviewJob.perform (cognitive 23) app/jobs/payroll_pto_review_job.rb:4 — PayrollPtoReviewJob.perform has cognitive complexity 23 (threshold 15). Drivers by points: boolean chains 11, if/else 11, error handling 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 · OfferPortal.OfferPortal (cognitive 22) · ×1
  • OfferPortal.OfferPortal (cognitive 22) app/javascript/src/components/Hiring/OfferPortal.tsx:19 — OfferPortal.OfferPortal has cognitive complexity 22 (threshold 15). Drivers by points: if/else 8 (9 pts), boolean chains 7, ternaries 3 (5 pts), error handling 1 (nesting depth added 3). Most of this is not in the body itself: 7 of the 22 points are its own statements and the rest belongs to 6 function items inside it that branch (a function literal at line 29, reply, a function literal at line 88, …). 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 · Header.Header (cognitive 22) · ×1
  • Header.Header (cognitive 22) app/javascript/src/components/ClientInvoices/Details/Header.tsx:15 — Header.Header has cognitive complexity 22 (threshold 15). Drivers by points: if/else 6 (9 pts), boolean chains 8, ternaries 3 (5 pts) (nesting depth added 5). Of this number, 11 points are the body's own statements and 11 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 · RunPreparation.ProfileCompletionRequestPanel (cognitive 22) · ×1
  • RunPreparation.ProfileCompletionRequestPanel (cognitive 22) app/javascript/src/components/Payroll/RunPreparation.tsx:184 — RunPreparation.ProfileCompletionRequestPanel has cognitive complexity 22 (threshold 15). Drivers by points: boolean chains 10, if/else 6 (7 pts), ternaries 3 (4 pts), error handling 1 (nesting depth added 2). Of this number, 11 points are the body's own statements and 11 belong to one function item 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 · EmploymentEditor.EmploymentEditor (cognitive 22) · ×1
  • EmploymentEditor.EmploymentEditor (cognitive 22) app/javascript/src/components/Profile/Personal/Employment/Edit/EmploymentEditor.tsx:19 — EmploymentEditor.EmploymentEditor has cognitive complexity 22 (threshold 15). Drivers by points: boolean chains 15, 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 · MobileEmploymentEditor.MobileEmploymentEditor (cognitive 22) · ×1
  • MobileEmploymentEditor.MobileEmploymentEditor (cognitive 22) app/javascript/src/components/Profile/Personal/Employment/Edit/MobileEmploymentEditor.tsx:19 — MobileEmploymentEditor.MobileEmploymentEditor has cognitive complexity 22 (threshold 15). Drivers by points: boolean chains 15, 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 · Page.TimeEntryReportPage (cognitive 22) · ×1
  • Page.TimeEntryReportPage (cognitive 22) app/javascript/src/components/Reports/TimeEntryReport/Page.tsx:23 — Page.TimeEntryReportPage has cognitive complexity 22 (threshold 15). Drivers by points: if/else 14 (18 pts), boolean chains 2, loops 1, ternaries 1 (nesting depth added 4). Most of this is not in the body itself: 4 of the 22 points are its own statements and the rest belongs to 4 function items inside it that branch (updateFilterCounter, handleRemoveSingleFilter, handlePageClick, …). 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 · Configuration.valid_field? (cognitive 22) · ×1
  • Configuration.valid_field? (cognitive 22) app/services/signatures/configuration.rb:82 — Configuration.valid_field? has cognitive complexity 22 (threshold 15). Drivers by points: boolean chains 19, if/else 3. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · ApiHandler.constructor (cognitive 21) · ×1
  • ApiHandler.constructor (cognitive 21) REDACTED:31 — ApiHandler.constructor has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (12 pts), boolean chains 9 (nesting depth added 4). None of this is in the body itself: all 21 points belong to 3 function literals inside it that branch (lines 56, 43, 116). 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.Generate (cognitive 21) · ×1
  • index.Generate (cognitive 21) app/javascript/src/components/Agreements/index.tsx:21 — index.Generate has cognitive complexity 21 (threshold 15). Drivers by points: boolean chains 10, if/else 6 (7 pts), ternaries 3, error handling 1 (nesting depth added 1). Most of this is not in the body itself: 9 of the 21 points are its own statements and the rest belongs to 5 function items inside it that branch (generate, a function literal at line 57, a function literal at line 64, …). 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 · InvoiceApiService.formatInvoiceForApi (cognitive 21) · ×1
  • InvoiceApiService.formatInvoiceForApi (cognitive 21) app/javascript/src/services/invoiceApi.ts:371 — InvoiceApiService.formatInvoiceForApi has cognitive complexity 21 (threshold 15). Drivers by points: boolean chains 19, ternaries 2. Most of this is not in the body itself: 3 of the 21 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 405, 388). 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 · MarkInvoicePaidModal.MarkInvoiceAsPaidModal (cognitive 21) · ×1
  • MarkInvoicePaidModal.MarkInvoiceAsPaidModal (cognitive 21) app/javascript/src/components/Invoices/Invoice/MarkInvoicePaidModal.tsx:17 — MarkInvoicePaidModal.MarkInvoiceAsPaidModal has cognitive complexity 21 (threshold 15). Drivers by points: ternaries 6 (10 pts), boolean chains 7, if/else 3 (4 pts) (nesting depth added 5). Of this number, 17 points are the body's own statements and 4 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 · Page.OrganizationSettingsPage · ×1
  • Page.OrganizationSettingsPage::formatAddress (cognitive 21) app/javascript/src/components/Profile/Organization/Details/Page.tsx:130 — Page.OrganizationSettingsPage::formatAddress has cognitive complexity 21 (threshold 15). Drivers by points: if/else 9 (15 pts), boolean chains 6 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (Page.OrganizationSettingsPage) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D2 · Cognitive Complexity · TimeEntriesDisplay.TimeEntriesDisplay (cognitive 21) · ×1
  • TimeEntriesDisplay.TimeEntriesDisplay (cognitive 21) app/javascript/src/components/TimeTracking/TimeEntriesDisplay.tsx:34 — TimeEntriesDisplay.TimeEntriesDisplay has cognitive complexity 21 (threshold 15). Drivers by points: ternaries 13 (22 pts), boolean chains 18, if/else 7 (11 pts) (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (TimeEntriesDisplay.TimeEntriesDisplay::renderEntry) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D2 · Cognitive Complexity · ApplicationOffers.ApplicationOffers (cognitive 20) · ×1
  • ApplicationOffers.ApplicationOffers (cognitive 20) app/javascript/src/components/Hiring/ApplicationOffers.tsx:74 — ApplicationOffers.ApplicationOffers has cognitive complexity 20 (threshold 15). Drivers by points: boolean chains 23, if/else 12 (13 pts), ternaries 8 (11 pts), 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. This shape REPEATS in the file: one other method here (ApplicationOffers.ApplicationOffers::send) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D2 · Cognitive Complexity · index.ClientInvoices (cognitive 20) · ×1
  • index.ClientInvoices (cognitive 20) app/javascript/src/components/ClientInvoices/index.tsx:14 — index.ClientInvoices has cognitive complexity 20 (threshold 15). Drivers by points: boolean chains 12, if/else 3 (4 pts), ternaries 2, error handling 1, loops 1 (nesting depth added 1). Most of this is not in the body itself: 4 of the 20 points are its own statements and the rest belongs to 5 function items inside it that branch (InvoicesLayout, a function literal at line 66, cleanParams, …). 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 · formValidationSchema.getInitialvalues (cognitive 20) · ×1
  • formValidationSchema.getInitialvalues (cognitive 20) app/javascript/src/components/Clients/ClientForm/formValidationSchema.ts:106 — formValidationSchema.getInitialvalues has cognitive complexity 20 (threshold 15). Drivers by points: boolean chains 20. 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 · Inbox.Inbox (cognitive 20) · ×1
  • Inbox.Inbox (cognitive 20) app/javascript/src/components/Hiring/Inbox.tsx:19 — Inbox.Inbox has cognitive complexity 20 (threshold 15). Drivers by points: boolean chains 10, if/else 7 (8 pts), error handling 1, ternaries 1 (nesting depth added 1). Most of this is not in the body itself: 8 of the 20 points are its own statements and the rest belongs to 5 function items inside it that branch (upload, a function literal at line 40, a function literal at line 51, …). 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 · index.LeaveManagement (cognitive 20) · ×1
  • index.LeaveManagement (cognitive 20) app/javascript/src/components/LeaveManagement/index.tsx:13 — index.LeaveManagement has cognitive complexity 20 (threshold 15). Drivers by points: if/else 10 (11 pts), boolean chains 5, ternaries 2 (4 pts) (nesting depth added 3). Most of this is not in the body itself: 2 of the 20 points are its own statements and the rest belongs to 5 function items inside it that branch (handlefilterTimeoffEntries, a function literal at line 34, LeaveManagementLayout, …). 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 · HiringAssignmentSubmission.valid_answers (cognitive 20) · ×1
  • HiringAssignmentSubmission.valid_answers (cognitive 20) app/models/hiring_assignment_submission.rb:70 — HiringAssignmentSubmission.valid_answers has cognitive complexity 20 (threshold 15). Drivers by points: boolean chains 10, if/else 6 (10 pts) (nesting depth added 4). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · Reconcile.process (cognitive 20) · ×1
  • Reconcile.process (cognitive 20) app/services/signatures/reconcile.rb:11 — Reconcile.process has cognitive complexity 20 (threshold 15). Drivers by points: error handling 5 (15 pts), if/else 4, boolean chains 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · MobileClientEditor.MobileClientEditor (cognitive 19) · ×1
  • MobileClientEditor.MobileClientEditor (cognitive 19) app/javascript/src/components/Clients/ClientForm/MobileClientEditor.tsx:35 — MobileClientEditor.MobileClientEditor has cognitive complexity 19 (threshold 15). Drivers by points: boolean chains 6, ternaries 5, error handling 2 (4 pts), if/else 4 (nesting depth added 2). Most of this is not in the body itself: 1 of the 19 points is its own statement and the rest belongs to 4 function items inside it that branch (a function literal at line 121, handleSubmit, a function literal at line 267, …). 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 · Header.Header (cognitive 19) · ×1
  • Header.Header (cognitive 19) app/javascript/src/components/InvoiceEmail/Header.tsx:9 — Header.Header has cognitive complexity 19 (threshold 15). Drivers by points: boolean chains 8, if/else 6, ternaries 3 (5 pts) (nesting depth added 2). Of this number, 11 points are the body's own statements and 8 belong to one function item 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, 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 · MoreOptions.MoreOptions (cognitive 19) · ×1
  • MoreOptions.MoreOptions (cognitive 19) app/javascript/src/components/Invoices/List/MoreOptions.tsx:18 — MoreOptions.MoreOptions has cognitive complexity 19 (threshold 15). Drivers by points: boolean chains 8, if/else 4 (6 pts), ternaries 3 (5 pts) (nesting depth added 4). Of this number, 13 points are the body's own statements and 6 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 · TableRow.TableRow (cognitive 19) · ×1
  • TableRow.TableRow (cognitive 19) app/javascript/src/components/Invoices/List/Table/TableRow.tsx:20 — TableRow.TableRow has cognitive complexity 19 (threshold 15). Drivers by points: boolean chains 9, if/else 7 (8 pts), error handling 1 (2 pts) (nesting depth added 2). Most of this is not in the body itself: 9 of the 19 points are its own statements and the rest belongs to 5 function items inside it that branch (submitSendInvoice, handleCheckboxChange, handleTooltip, …). 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 · index.InvoicesPage · ×1
  • index.InvoicesPage::handleInvoiceAction (cognitive 19) app/javascript/src/components/Invoices/index.tsx:778 — index.InvoicesPage::handleInvoiceAction has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9 (16 pts), boolean chains 2, match/switch 1 (nesting depth added 7). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident. This shape REPEATS in the file: one other method here (index.InvoicesPage) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D2 · Cognitive Complexity · LeaveBlock.LeaveBlock (cognitive 19) · ×1
  • LeaveBlock.LeaveBlock (cognitive 19) app/javascript/src/components/LeaveManagement/Container/LeaveBlock.tsx:18 — LeaveBlock.LeaveBlock has cognitive complexity 19 (threshold 15). Drivers by points: ternaries 7 (9 pts), boolean chains 6, if/else 4 (nesting depth added 2). Most of this is not in the body itself: 9 of the 19 points are its own statements and the rest belongs to 3 function items inside it that branch (getLeaveColor, getLeaveIcon, getSelectedText). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · outstandingOverdueInvoice.getReportData (cognitive 19) · ×1
  • outstandingOverdueInvoice.getReportData (cognitive 19) app/javascript/src/components/Reports/api/outstandingOverdueInvoice.ts:5 — outstandingOverdueInvoice.getReportData has cognitive complexity 19 (threshold 15). Drivers by points: boolean chains 9, if/else 7 (9 pts), error handling 1 (nesting depth added 2). Of this number, 11 points are the body's own statements and 8 belong to 4 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 · MonthCalendar.MonthCalendar · ×1
  • MonthCalendar.MonthCalendar::handleMonthChange (cognitive 19) app/javascript/src/components/TimeTracking/MonthCalendar.tsx:65 — MonthCalendar.MonthCalendar::handleMonthChange has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (13 pts), boolean chains 3, ternaries 1 (2 pts), loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · index.TimeoffEntryCard (cognitive 19) · ×1
  • index.TimeoffEntryCard (cognitive 19) app/javascript/src/components/TimeoffEntries/EntryCard/index.tsx:16 — index.TimeoffEntryCard has cognitive complexity 19 (threshold 15). Drivers by points: if/else 12 (16 pts), ternaries 2, boolean chains 1 (nesting depth added 4). Most of this is not in the body itself: 3 of the 19 points are its own statements and the rest belongs to 5 function items inside it that branch (handleDuplicateTimeoffEntry, getPayload, a function literal at line 39, …). 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 · index.TimesheetEntries · ×1
  • index.TimesheetEntries::handleMonthChange (cognitive 19) app/javascript/src/components/TimesheetEntries/index.tsx:549 — index.TimesheetEntries::handleMonthChange has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (13 pts), boolean chains 3, ternaries 1 (2 pts), loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · NativeGoogleAuthRequest.exchange! (cognitive 19) · ×1
  • NativeGoogleAuthRequest.exchange! (cognitive 19) app/models/native_google_auth_request.rb:79 — NativeGoogleAuthRequest.exchange! has cognitive complexity 19 (threshold 15). Drivers by points: boolean chains 15, if/else 4. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · BillingEvidence.valid? (cognitive 19) · ×1
  • BillingEvidence.valid? (cognitive 19) app/services/payroll/billing_evidence.rb:60 — BillingEvidence.valid? has cognitive complexity 19 (threshold 15). Drivers by points: boolean chains 13, if/else 5, error handling 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 · ConsultantRevision.retained_selection? (cognitive 19) · ×1
  • ConsultantRevision.retained_selection? (cognitive 19) app/services/payroll/consultant_revision.rb:104 — ConsultantRevision.retained_selection? has cognitive complexity 19 (threshold 15). Drivers by points: boolean chains 14, if/else 3 (4 pts), match/switch 1 (nesting depth added 1). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
D2 · Cognitive Complexity · Snapshot.valid_preparation? (cognitive 19) · ×1
  • Snapshot.valid_preparation? (cognitive 19) app/services/payroll/snapshot.rb:185 — Snapshot.valid_preparation? has cognitive complexity 19 (threshold 15). Drivers by points: boolean chains 12, if/else 6 (7 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 · index.ClientDetails (cognitive 18) · ×1
  • index.ClientDetails (cognitive 18) app/javascript/src/components/Clients/Details/index.tsx:29 — index.ClientDetails has cognitive complexity 18 (threshold 15). Drivers by points: boolean chains 9, ternaries 3 (5 pts), if/else 3, error handling 1 (nesting depth added 2). 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, 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 · AssignmentLibrary.AssignmentLibrary (cognitive 18) · ×1
  • AssignmentLibrary.AssignmentLibrary (cognitive 18) app/javascript/src/components/Hiring/AssignmentLibrary.tsx:35 — AssignmentLibrary.AssignmentLibrary has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (7 pts), boolean chains 6, ternaries 3 (4 pts), error handling 1 (nesting depth added 2). Most of this is not in the body itself: 6 of the 18 points are its own statements and the rest belongs to 5 function items inside it that branch (create, a function literal at line 222, 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.
D2 · Cognitive Complexity · ApplicationForm.ApplicationForm · ×1
  • ApplicationForm.ApplicationForm::submit (cognitive 18) app/javascript/src/components/Hiring/ApplicationForm.tsx:35 — ApplicationForm.ApplicationForm::submit has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (12 pts), boolean chains 5, error handling 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · index.BillingIdentityPanel · ×1
  • index.BillingIdentityPanel::failed (cognitive 18) app/javascript/src/components/Profile/BillingIdentity/index.tsx:108 — index.BillingIdentityPanel::failed has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (8 pts), boolean chains 6, error handling 1 (2 pts), ternaries 2 (nesting depth added 2). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages. This shape REPEATS in the file: one other method here (index.BillingIdentityPanel) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D2 · Cognitive Complexity · List.labelForSetting (cognitive 18) · ×1
  • List.labelForSetting (cognitive 18) app/javascript/src/components/Profile/Layout/Navigation/List.tsx:16 — List.labelForSetting has cognitive complexity 18 (threshold 15). Drivers by points: if/else 18. 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 · TimeEntriesDisplay.TimeEntriesDisplay · ×1
  • TimeEntriesDisplay.TimeEntriesDisplay::renderEntry (cognitive 18) app/javascript/src/components/TimeTracking/TimeEntriesDisplay.tsx:90 — TimeEntriesDisplay.TimeEntriesDisplay::renderEntry has cognitive complexity 18 (threshold 15). Drivers by points: boolean chains 10, ternaries 4 (7 pts), if/else 1 (nesting depth added 3). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators. This shape REPEATS in the file: one other method here (TimeEntriesDisplay.TimeEntriesDisplay) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D2 · Cognitive Complexity · WeekDaySelector.WeekDaySelector · ×1
  • WeekDaySelector.WeekDaySelector::renderDayButton (cognitive 18) app/javascript/src/components/TimeTracking/WeekDaySelector.tsx:21 — WeekDaySelector.WeekDaySelector::renderDayButton has cognitive complexity 18 (threshold 15). Drivers by points: boolean chains 9, ternaries 6 (9 pts) (nesting depth added 3). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · Document.validate_attributes (cognitive 18) · ×1
  • Document.validate_attributes (cognitive 18) app/services/agreements/document.rb:155 — Document.validate_attributes has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (12 pts), boolean chains 5, match/switch 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 · Pipeline.validate! (cognitive 18) · ×1
  • Pipeline.validate! (cognitive 18) app/services/hiring/pipeline.rb:29 — Pipeline.validate! has cognitive complexity 18 (threshold 15). Drivers by points: boolean chains 11, if/else 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 · Snapshot.resolved? (cognitive 18) · ×1
  • Snapshot.resolved? (cognitive 18) app/services/payroll/snapshot.rb:338 — Snapshot.resolved? has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (10 pts), boolean chains 8 (nesting depth added 3). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · index.customStyles (cognitive 17) · ×1
  • index.customStyles (cognitive 17) app/javascript/src/common/CustomReactSelectStyle/Styles/index.ts:7 — index.customStyles has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 13 (14 pts), boolean chains 3 (nesting depth added 1). None of this is in the body itself: all 17 points belong to 6 function literals inside it that branch (lines 66, 31, 57, …). 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.InputField (cognitive 17) · ×1
  • index.InputField (cognitive 17) app/javascript/src/common/FormikFields/InputField/index.tsx:9 — index.InputField has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 7, if/else 5, ternaries 4 (5 pts) (nesting depth added 1). Most of this is not in the body itself: 4 of the 17 points are its own statements and the rest belongs to 3 function items inside it that branch (handleFieldChange, a function literal at line 74, clearErrorOnChange). 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 · useAnalyticsFilters.useAnalyticsFilters (cognitive 17) · ×1
  • useAnalyticsFilters.useAnalyticsFilters (cognitive 17) app/javascript/src/components/Analytics/useAnalyticsFilters.ts:21 — useAnalyticsFilters.useAnalyticsFilters has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 8 (9 pts), boolean chains 7, if/else 1 (nesting depth added 1). Most of this is not in the body itself: 5 of the 17 points are its own statements and the rest belongs to 5 function literals inside it that branch (lines 65, 42, 79, …). 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 · Sidebar.Sidebar (cognitive 17) · ×1
  • Sidebar.Sidebar (cognitive 17) app/javascript/src/components/Dashboard/Sidebar.tsx:213 — Sidebar.Sidebar has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 12, ternaries 2 (3 pts), if/else 2 (nesting depth added 1). Of this number, 11 points are the body's own statements and 6 belong to 6 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 · index.EstimateWorkspace (cognitive 17) · ×1
  • index.EstimateWorkspace (cognitive 17) app/javascript/src/components/IndiaTaxEstimates/index.tsx:79 — index.EstimateWorkspace has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 5 (9 pts), boolean chains 7, error handling 1 (nesting depth added 4). Of this number, 9 points are the body's own statements and 8 belong to 6 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · IndiaHandoffs.IndiaHandoffsPanel (cognitive 17) · ×1
  • IndiaHandoffs.IndiaHandoffsPanel (cognitive 17) app/javascript/src/components/Payroll/IndiaHandoffs.tsx:492 — IndiaHandoffs.IndiaHandoffsPanel has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 9, if/else 5 (7 pts), error handling 1 (nesting depth added 2). Most of this is not in the body itself: 5 of the 17 points are its own statements and the rest belongs to 5 function items inside it that branch (perform, a function literal at line 514, a function literal at line 523, …). 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 · time-input.TimeInput (cognitive 17) · ×1
  • time-input.TimeInput (cognitive 17) app/javascript/src/components/ui/time-input.tsx:36 — time-input.TimeInput has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (10 pts), boolean chains 5, ternaries 2 (nesting depth added 3). Most of this is not in the body itself: 4 of the 17 points are its own statements and the rest belongs to 3 function items inside it that branch (onChangeHandler, a function literal at line 63, getType). 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 · index.TimeTracking · ×1
  • index.TimeTracking::TimeTrackingContent (cognitive 17) app/javascript/src/components/TimeTracking/index.tsx:815 — index.TimeTracking::TimeTrackingContent 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 · index.Payments (cognitive 17) · ×1
  • index.Payments (cognitive 17) app/javascript/src/components/payments/index.tsx:17 — index.Payments has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 5 (7 pts), if/else 4, boolean chains 3, error handling 3 (nesting depth added 2). Most of this is not in the body itself: 4 of the 17 points are its own statements and the rest belongs to 7 function items inside it that branch (PaymentsLayout, handleEscKeyPress, fetchInvoiceList, …). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · AgreementsController.parties (cognitive 17) · ×1
  • AgreementsController.parties (cognitive 17) app/controllers/api/v1/agreements_controller.rb:19 — AgreementsController.parties has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (9 pts), boolean chains 8 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · Form.valid_answer? (cognitive 17) · ×1
  • Form.valid_answer? (cognitive 17) app/services/hiring/form.rb:86 — Form.valid_answer? has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 12, ternaries 1 (2 pts), error handling 1, if/else 1, match/switch 1 (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 · Form.valid_field? (cognitive 17) · ×1
  • Form.valid_field? (cognitive 17) app/services/hiring/form.rb:133 — Form.valid_field? has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 10, if/else 6, ternaries 1. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · ApplicationOffers.ApplicationOffers · ×1
  • ApplicationOffers.ApplicationOffers::send (cognitive 16) app/javascript/src/components/Hiring/ApplicationOffers.tsx:173 — ApplicationOffers.ApplicationOffers::send has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 6 (9 pts), if/else 4 (5 pts), boolean chains 1, error handling 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (ApplicationOffers.ApplicationOffers) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D2 · Cognitive Complexity · index.CustomDatePicker (cognitive 16) · ×1
  • index.CustomDatePicker (cognitive 16) app/javascript/src/common/CustomDatePicker/index.tsx:12 — index.CustomDatePicker has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 6, if/else 5, ternaries 4, loops 1. Most of this is not in the body itself: 2 of the 16 points are its own statements and the rest belongs to 5 function items inside it that branch (a function literal at line 78, parseDate, a function literal at line 150, …). 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 · index.MobileView (cognitive 16) · ×1
  • index.MobileView (cognitive 16) app/javascript/src/components/ClientInvoices/Details/MobileView/index.tsx:17 — index.MobileView has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 13, ternaries 2, if/else 1. Of this number, 15 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 · currency.currencyFormat (cognitive 16) · ×1
  • currency.currencyFormat (cognitive 16) app/javascript/src/helpers/currency.ts:30 — currency.currencyFormat has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 5 (8 pts), boolean chains 7, if/else 1 (nesting depth added 3). Of this number, 13 points are the body's own statements and 3 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 · enhanced-search.DefaultSearchResultItem (cognitive 16) · ×1
  • enhanced-search.DefaultSearchResultItem (cognitive 16) REDACTED:177 — enhanced-search.DefaultSearchResultItem has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 11, ternaries 2 (3 pts), if/else 2 (nesting depth added 1). 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 · index.ClientList (cognitive 16) · ×1
  • index.ClientList (cognitive 16) app/javascript/src/components/Clients/List/index.tsx:18 — index.ClientList has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 5 (12 pts), boolean chains 4 (nesting depth added 7). 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 · ServiceFeePanel.ServiceFeePanel · ×1
  • ServiceFeePanel.ServiceFeePanel::save (cognitive 16) app/javascript/src/components/Payroll/ServiceFeePanel.tsx:83 — ServiceFeePanel.ServiceFeePanel::save has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (11 pts), boolean chains 3, error handling 1, ternaries 1 (nesting depth added 3). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ApplicationRetention.ApplicationRetention (cognitive 16) · ×1
  • ApplicationRetention.ApplicationRetention (cognitive 16) app/javascript/src/components/Hiring/ApplicationRetention.tsx:23 — ApplicationRetention.ApplicationRetention has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 8, if/else 6, error handling 1, ternaries 1. Of this number, 8 points are the body's own statements and 8 belong to 5 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 · ApplicationDetail.ApplicationDetail (cognitive 16) · ×1
  • ApplicationDetail.ApplicationDetail (cognitive 16) app/javascript/src/components/Hiring/ApplicationDetail.tsx:20 — ApplicationDetail.ApplicationDetail has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 5 (6 pts), boolean chains 5, if/else 5 (nesting depth added 1). Of this number, 9 points are the body's own statements and 7 belong to 5 function literals 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 · AppliedFilters.AppliedFilters (cognitive 16) · ×1
  • AppliedFilters.AppliedFilters (cognitive 16) app/javascript/src/components/Invoices/List/BulkActionsWrapper/AppliedFilters.tsx:8 — AppliedFilters.AppliedFilters has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (11 pts), boolean chains 3, loops 1, ternaries 1 (nesting depth added 5). Most of this is not in the body itself: 3 of the 16 points are its own statements and the rest belongs to 2 function items inside it that branch (handleRemoveFilter, a function literal at line 50). 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 · PreflightSummary.PreflightSummary (cognitive 16) · ×1
  • PreflightSummary.PreflightSummary (cognitive 16) app/javascript/src/components/Payroll/PreflightSummary.tsx:70 — PreflightSummary.PreflightSummary has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 10, ternaries 6. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · index.AuditLog (cognitive 16) · ×1
  • index.AuditLog (cognitive 16) app/javascript/src/components/Profile/Organization/AuditLog/index.tsx:83 — index.AuditLog has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 5 (8 pts), boolean chains 7, error handling 1 (nesting depth added 3). Of this number, 9 points are the body's own statements and 7 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 · index.SsoSettingsForm (cognitive 16) · ×1
  • index.SsoSettingsForm (cognitive 16) app/javascript/src/components/Profile/Organization/Sso/index.tsx:23 — index.SsoSettingsForm has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 7, if/else 4, ternaries 3, error handling 2. Most of this is not in the body itself: 3 of the 16 points are its own statements and the rest belongs to 5 function items inside it that branch (handleSubmit, a function literal at line 32, addDomain, …). 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 · index.UserDetailsEdit (cognitive 16) · ×1
  • index.UserDetailsEdit (cognitive 16) app/javascript/src/components/Profile/Personal/User/Edit/index.tsx:36 — index.UserDetailsEdit has cognitive complexity 16 (threshold 15). Drivers by points: if/else 27 (39 pts), boolean chains 19, ternaries 5, error handling 2 (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. This shape REPEATS in the file: one other method here (index.UserDetailsEdit::handleUpdateDetails) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D2 · Cognitive Complexity · TableRow.TableRow (cognitive 16) · ×1
  • TableRow.TableRow (cognitive 16) app/javascript/src/components/payments/Table/TableRow.tsx:18 — TableRow.TableRow has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 10, ternaries 5 (6 pts) (nesting depth added 1). Of this number, 14 points are the body's own statements and 2 belong to one function item 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 · HiringOffer.valid_lifecycle (cognitive 16) · ×1
  • HiringOffer.valid_lifecycle (cognitive 16) app/models/hiring_offer.rb:81 — HiringOffer.valid_lifecycle has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 11, if/else 3, ternaries 1 (2 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 · Snapshot.apply! (cognitive 16) · ×1
  • Snapshot.apply! (cognitive 16) app/services/signatures/snapshot.rb:8 — Snapshot.apply! has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (7 pts), boolean chains 5, ternaries 3 (4 pts) (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D3 · God Classes · MethodTooLong · ×1
  • MethodTooLong: InvoiceApiService.transformApiInvoice app/javascript/src/services/invoiceApi.ts:435 — MethodTooLong — transformApiInvoice runs 136 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 36 over it, 1.36× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
D32 · Data Compliance (PII/GDPR) · REDACTED · ×1
  • REDACTED
D4 · Code Duplication · Edited copy of a member (22 corresponding lines) · ×1
  • Edited copy of a member (22 corresponding lines) db/migrate/20261107170000_create_hiring_decisions.rb:5 — db/migrate/20261107170000_create_hiring_decisions.rb:5-26 | db/migrate/20261108010000_create_hiring_offers.rb:5-34 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (15 corresponding lines) · ×1
  • Edited copy of a member (15 corresponding lines) app/services/hiring/assignment_communication.rb:102 — app/services/hiring/assignment_communication.rb:102-124 | app/services/hiring/offer_communication.rb:71-85 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (12 corresponding lines) · ×1
  • Edited copy of a member (12 corresponding lines) app/services/hiring/assignment_communication.rb:47 — app/services/hiring/assignment_communication.rb:47-62 | app/services/hiring/offer_communication.rb:28-39 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (19 corresponding lines) · ×1
  • Edited copy of a member (19 corresponding lines) app/services/quick_books/exporters/invoice.rb:7 — app/services/quick_books/exporters/invoice.rb:7-25 | app/services/quick_books/exporters/payment.rb:7-32 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (17 corresponding lines) · ×1
  • Edited copy of a member (17 corresponding lines) app/controllers/api/v1/time_tracking_controller.rb:11 — app/controllers/api/v1/time_tracking_controller.rb:11-29 | app/controllers/api/v1/timesheet_entry_controller.rb:10-26 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 11+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 11+ corresponding lines) app/controllers/document_reviews_controller.rb:53 — app/controllers/document_reviews_controller.rb:53-63 | app/controllers/hiring_assignment_portal_controller.rb:77-88 | app/controllers/hiring_portal_controller.rb:99-109 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 8+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 8+ corresponding lines) app/services/hiring/assignments.rb:328 — app/services/hiring/assignments.rb:328-338 | app/services/hiring/offers.rb:113-120 | app/services/hiring/scheduling.rb:125-133 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (25 corresponding lines) · ×1
  • Edited copy of a member (25 corresponding lines) app/controllers/internal_api/v1/analytics_controller.rb:84 — app/controllers/internal_api/v1/analytics_controller.rb:84-110 | app/controllers/internal_api/v1/analytics_exports_controller.rb:73-97 — These two members are one piece of code written twice and then edited apart: 25 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (10 corresponding lines) · ×1
  • Edited copy of a member (10 corresponding lines) app/controllers/api/v1/team_members/notification_preferences_controller.rb:5 — app/controllers/api/v1/team_members/notification_preferences_controller.rb:5-14 | app/controllers/api/v1/team_members/notification_preferences_controller.rb:18-33 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 12+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 12+ corresponding lines) app/mcp/tools/expense_create_tool.rb:26 — app/mcp/tools/expense_create_tool.rb:26-46 | app/mcp/tools/invoice_send_tool.rb:27-44 | app/mcp/tools/time_create_tool.rb:26-46 | app/mcp/tools/time_update_tool.rb:31-42 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 7+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 7+ corresponding lines) app/jobs/quick_books/export_customer_job.rb:10 — app/jobs/quick_books/export_customer_job.rb:10-16 | app/jobs/quick_books/export_invoice_job.rb:10-18 | app/jobs/quick_books/export_payment_job.rb:10-19 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 7 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 3+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 3+ corresponding lines) app/services/hiring/assignments.rb:311 — app/services/hiring/assignments.rb:311-313 | app/services/hiring/intake.rb:91-94 | app/services/hiring/interviews.rb:108-110 | app/services/hiring/screening.rb:109-112 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 3 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 4+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 4+ corresponding lines) app/services/hiring/decisions.rb:113 — app/services/hiring/decisions.rb:113-116 | app/services/hiring/interviews.rb:101-104 | app/services/hiring/offers.rb:133-136 | app/services/hiring/onboarding.rb:173-176 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 4 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (5 members, 1+ corresponding lines) · ×1
  • Edited copies of one member (5 members, 1+ corresponding lines) app/models/hiring_assignment_submission.rb:89 — app/models/hiring_assignment_submission.rb:89-90 | app/models/hiring_decision.rb:65-65 | app/models/hiring_interview_booking.rb:134-134 | app/services/hiring/assignments.rb:319-320 | app/services/hiring/form.rb:122-123 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 1 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (2 corresponding lines) · ×1
  • Edited copy of a member (2 corresponding lines) app/services/payroll/pto_ledger.rb:342 — app/services/payroll/pto_ledger.rb:342-343 | app/services/payroll/service_fee_review.rb:125-126 — These two members are one piece of code written twice and then edited apart: 2 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (7 members, 9+ corresponding lines) · ×1
  • Edited copies of one member (7 members, 9+ corresponding lines) app/mcp/tools/client_list_tool.rb:18 — app/mcp/tools/client_list_tool.rb:18-27 | app/mcp/tools/expense_list_tool.rb:18-27 | app/mcp/tools/invoice_show_tool.rb:19-27 | app/mcp/tools/payment_show_tool.rb:19-27 | app/mcp/tools/project_list_tool.rb:18-27 | app/mcp/tools/time_list_tool.rb:20-29 | app/mcp/tools/workspace_whoami_tool.rb:13-21 — These 7 members are one piece of code written 7 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 7 times and the copies will drift further apart.
D4 · Code Duplication · Duplicated block (11 lines × 3) · ×1
  • Duplicated block (11 lines × 3) REDACTED:33 — REDACTED:33-43 | REDACTED:49-59 | REDACTED:66-76 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
D4 · Code Duplication · Duplicated block (6–7 lines × 2) · ×1
  • Duplicated block (6–7 lines × 2) app/controllers/api/v1/team_members/notification_preferences_controller.rb:7 — app/controllers/api/v1/team_members/notification_preferences_controller.rb:7-13 | app/controllers/api/v1/team_members/notification_preferences_controller.rb:25-30 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `app/controllers/api/v1/team_members/notification_preferences_controller.rb:7` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (20 lines × 2) · ×1
  • Duplicated block (20 lines × 2) app/policies/team_members/detail_policy.rb:5 — app/policies/team_members/detail_policy.rb:5-24 | app/policies/team_members/notification_preference_policy.rb:5-24 — before extracting anything, compare `app/policies/team_members/detail_policy.rb` and `app/policies/team_members/notification_preference_policy.rb` as WHOLE FILES: 89% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (11 lines × 2) · ×1
  • Duplicated block (11 lines × 2) app/controllers/api/v1/invoices_controller.rb:208 — app/controllers/api/v1/invoices_controller.rb:208-218 | app/controllers/api/v1/mobile/collections_controller.rb:411-421 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (5 lines × 3) · ×1
  • Duplicated block (5 lines × 3) app/models/signature_request_revision.rb:225 — app/models/signature_request_revision.rb:225-229 | app/services/payroll/billing_identity.rb:178-182 | app/services/payroll/india_handoff.rb:19-23 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `app/models/signature_request_revision.rb:225` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (9 lines × 3) · ×1
  • Duplicated block (9 lines × 3) app/services/invoice_payment/paypal_capture_fulfillment.rb:238 — app/services/invoice_payment/paypal_capture_fulfillment.rb:238-246 | app/services/invoice_payment/razorpay_payment_link_fulfillment.rb:113-121 | app/services/invoice_payment/razorpay_payment_link_webhook_fulfillment.rb:173-181 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once.
D4 · Code Duplication · Edited copy of a member (33 corresponding lines) · ×1
  • Edited copy of a member (33 corresponding lines) tools/miru-cli/cmd/miru/main.go:723 — tools/miru-cli/cmd/miru/main.go:723-755 | tools/miru-cli/cmd/miru/main.go:757-794 — These two members are one piece of code written twice and then edited apart: 33 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (35 corresponding lines) · ×1
  • Edited copy of a member (35 corresponding lines) tools/miru-cli/cmd/miru/main.go:1223 — tools/miru-cli/cmd/miru/main.go:1223-1258 | tools/miru-cli/cmd/miru/main.go:1459-1493 — These two members are one piece of code written twice and then edited apart: 35 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 23+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 23+ corresponding lines) tools/miru-cli/cmd/miru/main.go:389 — tools/miru-cli/cmd/miru/main.go:389-411 | tools/miru-cli/cmd/miru/main.go:1086-1108 | tools/miru-cli/cmd/miru/main.go:1124-1146 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 23 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Duplicated block (24 lines × 2) · ×1
  • Duplicated block (24 lines × 2) tools/miru-cli/cmd/miru/main.go:729 — tools/miru-cli/cmd/miru/main.go:729-752 | tools/miru-cli/cmd/miru/main.go:768-791 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
D4 · Code Duplication · Duplicated block (14–17 lines × 3) · ×1
  • Duplicated block (14–17 lines × 3) tools/miru-cli/cmd/miru/main.go:1242 — tools/miru-cli/cmd/miru/main.go:1242-1258 | tools/miru-cli/cmd/miru/main.go:1294-1307 | tools/miru-cli/cmd/miru/main.go:1477-1493 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `tools/miru-cli/cmd/miru/main.go:1242` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. The matched lines also register a scope-exit action (a `defer`-style statement) that runs when the function holding them returns: moved into a called unit it would run when THAT unit returns instead — before the caller uses what it releases — so keep the registration at the call site and extract only the work around it, or have the extracted unit hand the resource back for the caller to register. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `tools/miru-cli/cmd/miru/main.go:1240` calls `Set` and `tools/miru-cli/cmd/miru/main.go:1475` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (10 lines × 3) · ×1
  • Duplicated block (10 lines × 3) tools/miru-cli/cmd/miru/main.go:811 — tools/miru-cli/cmd/miru/main.go:811-820 | tools/miru-cli/cmd/miru/main.go:1087-1096 | tools/miru-cli/cmd/miru/main.go:1125-1134 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `tools/miru-cli/cmd/miru/main.go:811` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (10 lines × 2) · ×1
  • Duplicated block (10 lines × 2) tools/miru-cli/cmd/miru/main.go:1355 — tools/miru-cli/cmd/miru/main.go:1355-1364 | tools/miru-cli/cmd/miru/main.go:1374-1383 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `tools/miru-cli/cmd/miru/main.go:1355` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D6 · Cohesion (LCOM4) · Low cohesion · ×1
  • Low cohesion: InvoiceApiService (LCOM4 7) app/javascript/src/services/invoiceApi.ts:120 — InvoiceApiService's methods fall into 7 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 7 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
IC1 · Incompleteness & stubs · Guard cannot change the result · ×1
  • Guard cannot change the result — returns what the code already falls through to app/javascript/src/components/TimeTracking/EntryCard.tsx:60 — 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 32 sibling directories (293 clone groups) · ×1
  • Duplication concentrated across 32 sibling directories (293 clone groups) app/javascript/src/components/TimeTracking/MobileView/MobileEntryForm.tsx:56 — 293 duplicated blocks under app/javascript/src/components/ have copies in at least two of the sibling directories Agreements, Analytics, Authentication, ClientInvoices, Clients, ConsultantPayroll (+26 more sibling(s) not listed) — 142 of them are reported below, and 151 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 293 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 293 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 293 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 (42 clone groups) · ×1
  • Duplication concentrated across 8 sibling directories (42 clone groups) app/javascript/src/components/Reports/PaymentReport/index.tsx:98 — 42 duplicated blocks under app/javascript/src/components/Reports/ have copies in at least two of the sibling directories AccountsAgingReport, Container, Filters, List, OutstandingInvoiceReport, PaymentReport (+2 more sibling(s) not listed) — 29 of them are reported below, and 13 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 42 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 42 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 42 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 12 sibling directories (16 clone groups) · ×1
  • Duplication concentrated across 12 sibling directories (16 clone groups) app/javascript/src/components/Invoices/List/FilterSideBar/filterOptions.ts:1 — 16 duplicated blocks under app/javascript/src/components/Invoices/ have copies in at least two of the sibling directories AdminDashboard, ChartWithSummary, CompactInvoiceSummary, Invoice, InvoiceEditor, InvoicePreview (+6 more sibling(s) not listed) — 10 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 16 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 16 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 16 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 (15 clone groups) · ×1
  • Duplication concentrated across 5 sibling directories (15 clone groups) app/javascript/src/components/Profile/Organization/Edit/Page.tsx:50 — 15 duplicated blocks under app/javascript/src/components/Profile/ have copies in at least two of the sibling directories BillingIdentity, EmployeeRecords, InvoiceAuthorization, Organization, Personal — 7 of them are reported below, and 8 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 6 sibling directories (13 clone groups) · ×1
  • Duplication concentrated across 6 sibling directories (13 clone groups) app/javascript/src/StyledComponents/TimeInput/index.tsx:22 — 13 duplicated blocks under app/javascript/src/ have copies in at least two of the sibling directories StyledComponents, common, components, constants, context, services — 5 of them are reported below, and 8 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 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 4 sibling directories (10 clone groups) · ×1
  • Duplication concentrated across 4 sibling directories (10 clone groups) app/javascript/src/components/Profile/Personal/Employment/Edit/MobileEmploymentEditor.tsx:14 — 10 duplicated blocks under app/javascript/src/components/Profile/Personal/ have copies in at least two of the sibling directories Automation, Devices, Employment, User — 5 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 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 8 sibling directories (7 clone groups) · ×1
  • Duplication concentrated across 8 sibling directories (7 clone groups) app/javascript/src/common/CustomDateRangePicker/index.tsx:24 — 7 duplicated blocks under app/javascript/src/common/ have copies in at least two of the sibling directories AppErrorBoundary, CustomCreatableSelect, CustomDatePicker, CustomDateRangePicker, CustomDateRangeWIthInput, CustomReactSelect (+2 more sibling(s) not listed) — 6 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 7 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 7 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 7 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) · ×1
  • Duplication concentrated across 5 sibling directories (5 clone groups) REDACTED:27 — 5 of the duplicated blocks reported below have copies in at least two of the sibling directories EmailVerification, ForgotPassword, ResetPassword, SignIn, SignUp under app/javascript/src/components/Authentication/. 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 (395 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (395 matched lines × 2 locations) app/javascript/src/components/TimeTracking/MobileView/MobileEntryForm.tsx:56 — app/javascript/src/components/TimeTracking/MobileView/MobileEntryForm.tsx:56 · app/javascript/src/components/TimesheetEntries/TimeEntryForm/MobileEntryForm.tsx:51 — the two spans are one implementation copied and then locally edited — 1880 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 (300 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (300 matched lines × 2 locations) app/javascript/src/components/Hiring/ApplicationDecisions.tsx:92 — app/javascript/src/components/Hiring/ApplicationDecisions.tsx:92 · app/javascript/src/components/Hiring/ApplicationOffers.tsx:92 — the two spans are one implementation copied and then locally edited — 1587 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 (284 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (284 matched lines × 2 locations) app/javascript/src/components/Invoices/List/FilterSideBar/index.tsx:47 — app/javascript/src/components/Invoices/List/FilterSideBar/index.tsx:47 · app/javascript/src/components/Reports/RevenueByClientReport/Filters/index.tsx:65 — the two spans are one implementation copied and then locally edited — 1450 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 (257 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (257 matched lines × 2 locations) app/javascript/src/components/Profile/Personal/User/Edit/MobileProfileEditor.tsx:128 — app/javascript/src/components/Profile/Personal/User/Edit/MobileProfileEditor.tsx:128 · app/javascript/src/components/Profile/Personal/User/Edit/ProfileEditor.tsx:133 — the two spans are one implementation copied and then locally edited — 1052 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 (241 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (241 matched lines × 2 locations) app/javascript/src/components/Analytics/ClientInsightsPage.tsx:52 — app/javascript/src/components/Analytics/ClientInsightsPage.tsx:52 · app/javascript/src/components/Analytics/ExpenseTrendsPage.tsx:54 — the two spans are one implementation copied and then locally edited — 1169 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 (235 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (235 matched lines × 2 locations) app/javascript/src/common/CustomDateRangePicker/index.tsx:24 — app/javascript/src/common/CustomDateRangePicker/index.tsx:24 · app/javascript/src/common/CustomDateRangeWIthInput/index.tsx:44 — the two spans are one implementation copied and then locally edited — 1209 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 (228 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (228 matched lines × 2 locations) app/javascript/src/components/Clients/ClientsTable.tsx:102 — app/javascript/src/components/Clients/ClientsTable.tsx:102 · app/javascript/src/components/Projects/ProjectsTable.tsx:86 — the two spans are one implementation copied and then locally edited — 1229 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 (213 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (213 matched lines × 2 locations) app/javascript/src/components/TimeoffEntries/TimeoffForm/MobileTimeoffForm.tsx:62 — app/javascript/src/components/TimeoffEntries/TimeoffForm/MobileTimeoffForm.tsx:62 · app/javascript/src/components/TimesheetEntries/TimeEntryForm/MobileEntryForm.tsx:167 — the two spans are one implementation copied and then locally edited — 839 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 (207 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (207 matched lines × 2 locations) app/javascript/src/components/Projects/ProjectsTable.tsx:161 — app/javascript/src/components/Projects/ProjectsTable.tsx:161 · app/javascript/src/components/Team/TeamTable.tsx:377 — the two spans are one implementation copied and then locally edited — 1145 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 (206 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (206 matched lines × 2 locations) app/javascript/src/components/TimeTracking/WeeklyEntriesCard.tsx:31 — app/javascript/src/components/TimeTracking/WeeklyEntriesCard.tsx:31 · app/javascript/src/components/TimesheetEntries/WeekView/WeeklyEntriesCard.tsx:34 — the two spans are one implementation copied and then locally edited — 1105 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 (195 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (195 matched lines × 2 locations) app/javascript/src/components/Reports/Filters/FilterSideBar.tsx:28 — app/javascript/src/components/Reports/Filters/FilterSideBar.tsx:28 · app/javascript/src/components/Reports/Filters/Sidebar.tsx:39 — the two spans are one implementation copied and then locally edited — 1187 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 (176 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (176 matched lines × 2 locations) app/javascript/src/components/OrganizationSetup/FinancialDetailsForm/MobileFinancialDetailForm.tsx:25 — app/javascript/src/components/OrganizationSetup/FinancialDetailsForm/MobileFinancialDetailForm.tsx:25 · app/javascript/src/components/OrganizationSetup/FinancialDetailsForm/index.tsx:25 — the two spans are one implementation copied and then locally edited — 777 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 · Wholesale file copy (172 identical lines × 2 files) · ×1
  • Wholesale file copy (172 identical lines × 2 files) app/javascript/src/components/Profile/Personal/Employment/Edit/EmploymentEditor.tsx:1 — app/javascript/src/components/Profile/Personal/Employment/Edit/EmploymentEditor.tsx:1 · app/javascript/src/components/Profile/Personal/Employment/Edit/MobileEmploymentEditor.tsx:1 — these 2 files are line-for-line copies of one another — 172 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 with local edits (168 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (168 matched lines × 2 locations) app/javascript/src/components/Analytics/ExpenseTrendsPage.tsx:134 — app/javascript/src/components/Analytics/ExpenseTrendsPage.tsx:134 · app/javascript/src/components/Analytics/TeamAnalyticsPage.tsx:104 — the two spans are one implementation copied and then locally edited — 806 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 (163 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (163 matched lines × 2 locations) REDACTED:27 — REDACTED:27 · REDACTED:26 — the two spans are one implementation copied and then locally edited — 761 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 (142 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (142 matched lines × 2 locations) app/javascript/src/components/Clients/Modals/PaymentReminder/MobileView/index.tsx:17 — app/javascript/src/components/Clients/Modals/PaymentReminder/MobileView/index.tsx:17 · app/javascript/src/components/Clients/Modals/PaymentReminder/index.tsx:18 — the two spans are one implementation copied and then locally edited — 666 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 (139 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (139 matched lines × 2 locations) app/javascript/src/components/Projects/ProjectsTable.tsx:181 — app/javascript/src/components/Projects/ProjectsTable.tsx:181 · app/javascript/src/components/payments/PaymentsTable.tsx:447 — the two spans are one implementation copied and then locally edited — 663 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 (116 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (116 matched lines × 2 locations) app/javascript/src/components/Agreements/index.tsx:299 — app/javascript/src/components/Agreements/index.tsx:299 · app/javascript/src/components/DocumentSignatures/index.tsx:280 — the two spans are one implementation copied and then locally edited — 565 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 (104 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (104 matched lines × 2 locations) app/javascript/src/components/Hiring/ApplicationInterviews.tsx:103 — app/javascript/src/components/Hiring/ApplicationInterviews.tsx:103 · app/javascript/src/components/Hiring/InterviewPanel.tsx:62 — the two spans are one implementation copied and then locally edited — 574 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 (101 lines × 2 locations) · ×1
  • Duplicated block (101 lines × 2 locations) app/javascript/src/components/Expenses/ExpensesTable.tsx:1161 — app/javascript/src/components/Expenses/ExpensesTable.tsx:1161 · app/javascript/src/components/Expenses/ExpensesTable.tsx:1429 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
R10 · Code Duplication · Duplicated block with local edits (91 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (91 matched lines × 2 locations) app/javascript/src/components/Reports/PaymentReport/index.tsx:98 — app/javascript/src/components/Reports/PaymentReport/index.tsx:98 · app/javascript/src/components/Reports/RevenueByClientReport/index.tsx:118 — the two spans are one implementation copied and then locally edited — 675 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 · Wholesale file copy (84 identical lines × 2 files) · ×1
  • Wholesale file copy (84 identical lines × 2 files) app/javascript/src/components/Clients/Contacts/AddContacts.tsx:1 — app/javascript/src/components/Clients/Contacts/AddContacts.tsx:1 · app/javascript/src/components/Clients/Contacts/EditContact.tsx:1 — these 2 files are line-for-line copies of one another — 84 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 with local edits (79 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (79 matched lines × 2 locations) app/javascript/src/components/Authentication/ForgotPassword/index.tsx:48 — app/javascript/src/components/Authentication/ForgotPassword/index.tsx:48 · app/javascript/src/components/Authentication/ResetPassword/index.tsx:51 — the two spans are one implementation copied and then locally edited — 352 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 (78 lines × 2 locations) · ×1
  • Duplicated block (78 lines × 2 locations) app/javascript/src/components/Hiring/AssessmentPortal.tsx:29 — app/javascript/src/components/Hiring/AssessmentPortal.tsx:29 · app/javascript/src/components/Hiring/Portal.tsx:19 — 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 (77 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (77 matched lines × 2 locations) app/javascript/src/components/TaxDeclarations/index.tsx:265 — app/javascript/src/components/TaxDeclarations/index.tsx:265 · app/javascript/src/components/TaxDeclarations/index.tsx:417 — the two spans are one implementation copied and then locally edited — 339 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 · Wholesale file copy (76 identical lines × 2 files) · ×1
  • Wholesale file copy (76 identical lines × 2 files) app/javascript/src/common/CustomCreatableSelect/index.tsx:1 — app/javascript/src/common/CustomCreatableSelect/index.tsx:1 · app/javascript/src/common/CustomReactSelect/index.tsx:1 — these 2 files are line-for-line copies of one another — 76 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 (74 lines × 2 locations) · ×1
  • Duplicated block (74 lines × 2 locations) app/javascript/src/components/Reports/PaymentReport/index.tsx:814 — app/javascript/src/components/Reports/PaymentReport/index.tsx:814 · app/javascript/src/components/Reports/RevenueByClientReport/index.tsx:748 — 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 · Wholesale file copy (73 identical lines × 2 files) · ×1
  • Wholesale file copy (73 identical lines × 2 files) app/javascript/src/components/ClientInvoices/Details/InvoiceTotalSummary.tsx:1 — app/javascript/src/components/ClientInvoices/Details/InvoiceTotalSummary.tsx:1 · app/javascript/src/components/InvoiceEmail/InvoiceTotalSummary.tsx:1 — these 2 files are line-for-line copies of one another — 73 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.
R2 · Cyclomatic Complexity · Complex function InvoiceEditor (cyclomatic 74, cognitive 55) · ×1
  • Complex function InvoiceEditor (cyclomatic 74, cognitive 55) app/javascript/src/components/Invoices/InvoiceEditor/index.tsx:62 — InvoiceEditor has cyclomatic complexity 74 and cognitive complexity 55; 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 Billing (cyclomatic 62, cognitive 41) · ×1
  • Complex function Billing (cyclomatic 62, cognitive 41) app/javascript/src/components/Profile/Organization/Billing/index.tsx:61 — Billing has cyclomatic complexity 62 and cognitive complexity 41; 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 transformApiInvoice (cyclomatic 55, cognitive 38) · ×1
  • Complex function transformApiInvoice (cyclomatic 55, cognitive 38) app/javascript/src/services/invoiceApi.ts:435 — transformApiInvoice has cyclomatic complexity 55 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 DeliveryPanel (cyclomatic 54, cognitive 41) · ×1
  • Complex function DeliveryPanel (cyclomatic 54, cognitive 41) app/javascript/src/components/DocumentSignatures/DeliveryPanel.tsx:35 — DeliveryPanel has cyclomatic complexity 54 and cognitive complexity 41; 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 ApplicationAssignments (cyclomatic 54, cognitive 41) · ×1
  • Complex function ApplicationAssignments (cyclomatic 54, cognitive 41) app/javascript/src/components/Hiring/ApplicationAssignments.tsx:63 — ApplicationAssignments has cyclomatic complexity 54 and cognitive complexity 41; 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 InvoicesPage (cyclomatic 54, cognitive 40) · ×1
  • Complex function InvoicesPage (cyclomatic 54, cognitive 40) app/javascript/src/components/Invoices/index.tsx:38 — InvoicesPage has cyclomatic complexity 54 and cognitive complexity 40; 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 OrganizationPaymentSettingsPage (cyclomatic 53, cognitive 48) · ×1
  • Complex function OrganizationPaymentSettingsPage (cyclomatic 53, cognitive 48) app/javascript/src/components/Profile/Organization/Payment/Page.tsx:63 — OrganizationPaymentSettingsPage has cyclomatic complexity 53 and cognitive complexity 48; 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 MobileProfileEditor (cyclomatic 52, cognitive 51) · ×1
  • Complex function MobileProfileEditor (cyclomatic 52, cognitive 51) app/javascript/src/components/Profile/Personal/User/Edit/MobileProfileEditor.tsx:30 — MobileProfileEditor has cyclomatic complexity 52 and cognitive complexity 51; 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 InvoicePreview (cyclomatic 52, cognitive 45) · ×1
  • Complex function InvoicePreview (cyclomatic 52, cognitive 45) app/javascript/src/components/Invoices/InvoicePreview/index.tsx:90 — InvoicePreview has cyclomatic complexity 52 and cognitive complexity 45; 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 BillingIdentityPanel (cyclomatic 51, cognitive 41) · ×1
  • Complex function BillingIdentityPanel (cyclomatic 51, cognitive 41) app/javascript/src/components/Profile/BillingIdentity/index.tsx:61 — BillingIdentityPanel has cyclomatic complexity 51 and cognitive complexity 41; 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 51, cognitive 38) · ×1
  • Complex function (anonymous) (cyclomatic 51, cognitive 38) app/javascript/src/components/Clients/ClientForm/ClientEditor.tsx:108 — (anonymous) has cyclomatic complexity 51 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 ExpensesTable (cyclomatic 50, cognitive 38) · ×1
  • Complex function ExpensesTable (cyclomatic 50, cognitive 38) app/javascript/src/components/Expenses/ExpensesTable.tsx:199 — ExpensesTable has cyclomatic complexity 50 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 ProfileEditor (cyclomatic 43, cognitive 42) · ×1
  • Complex function ProfileEditor (cyclomatic 43, cognitive 42) app/javascript/src/components/Profile/Personal/User/Edit/ProfileEditor.tsx:32 — ProfileEditor has cyclomatic complexity 43 and cognitive complexity 42; 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 CandidateMessages (cyclomatic 41, cognitive 36) · ×1
  • Complex function CandidateMessages (cyclomatic 41, cognitive 36) app/javascript/src/components/Hiring/CandidateMessages.tsx:49 — CandidateMessages has cyclomatic complexity 41 and cognitive complexity 36; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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 PayrollWorkspace (cyclomatic 40, cognitive 35) · ×1
  • Complex function PayrollWorkspace (cyclomatic 40, cognitive 35) app/javascript/src/components/ConsultantPayroll/index.tsx:108 — PayrollWorkspace has cyclomatic complexity 40 and cognitive complexity 35; 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 Onboarding (cyclomatic 40, cognitive 33) · ×1
  • Complex function Onboarding (cyclomatic 40, cognitive 33) app/javascript/src/components/Hiring/Onboarding.tsx:61 — Onboarding has cyclomatic complexity 40 and cognitive complexity 33; 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 DeclarationWorkspace (cyclomatic 39, cognitive 34) · ×1
  • Complex function DeclarationWorkspace (cyclomatic 39, cognitive 34) app/javascript/src/components/TaxDeclarations/index.tsx:66 — DeclarationWorkspace has cyclomatic complexity 39 and cognitive complexity 34; 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 InterviewBookings (cyclomatic 38, cognitive 32) · ×1
  • Complex function InterviewBookings (cyclomatic 38, cognitive 32) app/javascript/src/components/Hiring/InterviewBookings.tsx:41 — InterviewBookings has cyclomatic complexity 38 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 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 OrgEditForm (cyclomatic 37, cognitive 36) · ×1
  • Complex function OrgEditForm (cyclomatic 37, cognitive 36) app/javascript/src/components/Profile/Organization/Edit/OrgEditForm.tsx:127 — OrgEditForm has cyclomatic complexity 37 and cognitive complexity 36; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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 Editor (cyclomatic 37, cognitive 34) · ×1
  • Complex function Editor (cyclomatic 37, cognitive 34) app/javascript/src/components/DocumentSignatures/Editor.tsx:30 — Editor has cyclomatic complexity 37 and cognitive complexity 34; 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 PaymentReport (cyclomatic 37, cognitive 33) · ×1
  • Complex function PaymentReport (cyclomatic 37, cognitive 33) app/javascript/src/components/Reports/PaymentReport/index.tsx:149 — PaymentReport has cyclomatic complexity 37 and cognitive complexity 33; 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 ReceiptDetail (cyclomatic 37, cognitive 30) · ×1
  • Complex function ReceiptDetail (cyclomatic 37, cognitive 30) app/javascript/src/components/Hiring/ReceiptDetail.tsx:21 — ReceiptDetail has cyclomatic complexity 37 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 Leg (cyclomatic 35, cognitive 32) · ×1
  • Complex function Leg (cyclomatic 35, cognitive 32) app/javascript/src/components/Payroll/MercuryPayments.tsx:540 — Leg has cyclomatic complexity 35 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 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 ExpenseTrendsPage (cyclomatic 34, cognitive 28) · ×1
  • Complex function ExpenseTrendsPage (cyclomatic 34, cognitive 28) app/javascript/src/components/Analytics/ExpenseTrendsPage.tsx:54 — ExpenseTrendsPage has cyclomatic complexity 34 and cognitive complexity 28; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 33, cognitive 31) · ×1
  • Complex function (anonymous) (cyclomatic 33, cognitive 31) app/javascript/src/components/OrganizationSetup/CompanyDetailsForm/index.tsx:219 — (anonymous) has cyclomatic complexity 33 and cognitive complexity 31; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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 ClientInsightsPage (cyclomatic 33, cognitive 27) · ×1
  • Complex function ClientInsightsPage (cyclomatic 33, cognitive 27) app/javascript/src/components/Analytics/ClientInsightsPage.tsx:52 — ClientInsightsPage has cyclomatic complexity 33 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 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 Settings (cyclomatic 33, cognitive 24) · ×1
  • Complex function Settings (cyclomatic 33, cognitive 24) app/javascript/src/components/Hiring/Settings.tsx:25 — Settings has cyclomatic complexity 33 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 (anonymous) (cyclomatic 32, cognitive 35) · ×1
  • Complex function (anonymous) (cyclomatic 32, cognitive 35) REDACTED:321 — (anonymous) has cyclomatic complexity 32 and cognitive complexity 35; 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 RazorpayConnection (cyclomatic 32, cognitive 30) · ×1
  • Complex function RazorpayConnection (cyclomatic 32, cognitive 30) app/javascript/src/components/Profile/Organization/Payment/RazorpayConnection.tsx:104 — RazorpayConnection has cyclomatic complexity 32 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 OutstandingInvoicesWorkspaceView (cyclomatic 31, cognitive 29) · ×1
  • Complex function OutstandingInvoicesWorkspaceView (cyclomatic 31, cognitive 29) app/javascript/src/components/Reports/OutstandingInvoiceReport/WorkspaceView.tsx:191 — OutstandingInvoicesWorkspaceView has cyclomatic complexity 31 and cognitive complexity 29; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function TeamTable (cyclomatic 31, cognitive 26) · ×1
  • Complex function TeamTable (cyclomatic 31, cognitive 26) app/javascript/src/components/Team/TeamTable.tsx:102 — TeamTable has cyclomatic complexity 31 and cognitive complexity 26; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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 App (cyclomatic 31, cognitive 26) · ×1
  • Complex function App (cyclomatic 31, cognitive 26) apps/mobile/App.tsx:239 — App has cyclomatic complexity 31 and cognitive complexity 26; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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 PortalField (cyclomatic 30, cognitive 28) · ×1
  • Complex function PortalField (cyclomatic 30, cognitive 28) app/javascript/src/components/Hiring/PortalField.tsx:19 — PortalField has cyclomatic complexity 30 and cognitive complexity 28; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function Records (cyclomatic 30, cognitive 28) · ×1
  • Complex function Records (cyclomatic 30, cognitive 28) app/javascript/src/components/Profile/EmployeeRecords/index.tsx:44 — Records has cyclomatic complexity 30 and cognitive complexity 28; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function OrganizationHolidaysEditor (cyclomatic 30, cognitive 27) · ×1
  • Complex function OrganizationHolidaysEditor (cyclomatic 30, cognitive 27) app/javascript/src/components/Profile/Organization/Holidays/Editor.tsx:85 — OrganizationHolidaysEditor has cyclomatic complexity 30 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 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 TimeEntryReport (cyclomatic 29, cognitive 25) · ×1
  • Complex function TimeEntryReport (cyclomatic 29, cognitive 25) app/javascript/src/components/Reports/TimeEntryReport/index.tsx:258 — TimeEntryReport has cyclomatic complexity 29 and cognitive complexity 25; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function Workspace (cyclomatic 29, cognitive 22) · ×1
  • Complex function Workspace (cyclomatic 29, cognitive 22) app/javascript/src/components/Hiring/index.tsx:304 — Workspace has cyclomatic complexity 29 and cognitive complexity 22; 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 InvoiceAuthorizationPanel (cyclomatic 29, cognitive 20) · ×1
  • Complex function InvoiceAuthorizationPanel (cyclomatic 29, cognitive 20) app/javascript/src/components/Profile/InvoiceAuthorization/index.tsx:20 — InvoiceAuthorizationPanel has cyclomatic complexity 29 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 InvoiceList (cyclomatic 29, cognitive 18) · ×1
  • Complex function InvoiceList (cyclomatic 29, cognitive 18) app/javascript/src/components/Invoices/InvoiceList.tsx:78 — InvoiceList has cyclomatic complexity 29 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 ConsultantRow (cyclomatic 28, cognitive 25) · ×1
  • Complex function ConsultantRow (cyclomatic 28, cognitive 25) app/javascript/src/components/Payroll/RunPreparation.tsx:289 — ConsultantRow has cyclomatic complexity 28 and cognitive complexity 25; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R3 · Large Files · app/javascript/src/components/Profile/Organization/Payment/Page.tsx · ×1
  • app/javascript/src/components/Profile/Organization/Payment/Page.tsx: 2121 lines of code app/javascript/src/components/Profile/Organization/Payment/Page.tsx:1 — app/javascript/src/components/Profile/Organization/Payment/Page.tsx has 2121 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 · app/javascript/src/components/Expenses/ExpensesTable.tsx · ×1
  • app/javascript/src/components/Expenses/ExpensesTable.tsx: 1594 lines of code app/javascript/src/components/Expenses/ExpensesTable.tsx:1 — app/javascript/src/components/Expenses/ExpensesTable.tsx has 1594 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 · apps/mobile/App.tsx · ×1
  • apps/mobile/App.tsx: 1164 lines of code apps/mobile/App.tsx:1 — apps/mobile/App.tsx has 1164 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 · app/javascript/src/components/Payroll/MercuryPayments.tsx · ×1
  • app/javascript/src/components/Payroll/MercuryPayments.tsx: 1056 lines of code app/javascript/src/components/Payroll/MercuryPayments.tsx:1 — app/javascript/src/components/Payroll/MercuryPayments.tsx has 1056 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 · app/javascript/src/components/Team/TeamTable.tsx · ×1
  • app/javascript/src/components/Team/TeamTable.tsx: 1052 lines of code app/javascript/src/components/Team/TeamTable.tsx:1 — app/javascript/src/components/Team/TeamTable.tsx has 1052 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 · app/javascript/src/components/Invoices/InvoiceEditor/index.tsx · ×1
  • app/javascript/src/components/Invoices/InvoiceEditor/index.tsx: 1039 lines of code app/javascript/src/components/Invoices/InvoiceEditor/index.tsx:1 — app/javascript/src/components/Invoices/InvoiceEditor/index.tsx has 1039 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 · app/javascript/src/components/ConsultantPayroll/index.tsx · ×1
  • app/javascript/src/components/ConsultantPayroll/index.tsx: 995 lines of code app/javascript/src/components/ConsultantPayroll/index.tsx:1 — app/javascript/src/components/ConsultantPayroll/index.tsx has 995 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 · app/javascript/src/components/Profile/BillingIdentity/index.tsx · ×1
  • app/javascript/src/components/Profile/BillingIdentity/index.tsx: 988 lines of code app/javascript/src/components/Profile/BillingIdentity/index.tsx:1 — app/javascript/src/components/Profile/BillingIdentity/index.tsx has 988 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 · app/javascript/src/components/Profile/Organization/Edit/OrgEditForm.tsx · ×1
  • app/javascript/src/components/Profile/Organization/Edit/OrgEditForm.tsx: 964 lines of code app/javascript/src/components/Profile/Organization/Edit/OrgEditForm.tsx:1 — app/javascript/src/components/Profile/Organization/Edit/OrgEditForm.tsx has 964 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 · app/javascript/src/components/Profile/Organization/Billing/index.tsx · ×1
  • app/javascript/src/components/Profile/Organization/Billing/index.tsx: 962 lines of code app/javascript/src/components/Profile/Organization/Billing/index.tsx:1 — app/javascript/src/components/Profile/Organization/Billing/index.tsx has 962 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 · app/javascript/src/components/Payroll/PtoPanel.tsx · ×1
  • app/javascript/src/components/Payroll/PtoPanel.tsx: 960 lines of code app/javascript/src/components/Payroll/PtoPanel.tsx:1 — app/javascript/src/components/Payroll/PtoPanel.tsx has 960 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 · app/javascript/src/components/TimeTracking/index.tsx · ×1
  • app/javascript/src/components/TimeTracking/index.tsx: 951 lines of code app/javascript/src/components/TimeTracking/index.tsx:1 — app/javascript/src/components/TimeTracking/index.tsx has 951 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 · app/javascript/src/components/Reports/TimeEntryReport/index.tsx · ×1
  • app/javascript/src/components/Reports/TimeEntryReport/index.tsx: 918 lines of code app/javascript/src/components/Reports/TimeEntryReport/index.tsx:1 — app/javascript/src/components/Reports/TimeEntryReport/index.tsx has 918 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 · app/javascript/src/components/TimesheetEntries/FloatingTimer.tsx · ×1
  • app/javascript/src/components/TimesheetEntries/FloatingTimer.tsx: 859 lines of code app/javascript/src/components/TimesheetEntries/FloatingTimer.tsx:1 — app/javascript/src/components/TimesheetEntries/FloatingTimer.tsx 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 · app/javascript/src/components/Profile/Organization/Holidays/Editor.tsx · ×1
  • app/javascript/src/components/Profile/Organization/Holidays/Editor.tsx: 839 lines of code app/javascript/src/components/Profile/Organization/Holidays/Editor.tsx:1 — app/javascript/src/components/Profile/Organization/Holidays/Editor.tsx has 839 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 · app/javascript/src/components/Reports/PaymentReport/index.tsx · ×1
  • app/javascript/src/components/Reports/PaymentReport/index.tsx: 829 lines of code app/javascript/src/components/Reports/PaymentReport/index.tsx:1 — app/javascript/src/components/Reports/PaymentReport/index.tsx has 829 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: 802 lines of code REDACTED:1 — REDACTED has 802 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 · app/javascript/src/components/Invoices/index.tsx · ×1
  • app/javascript/src/components/Invoices/index.tsx: 794 lines of code app/javascript/src/components/Invoices/index.tsx:1 — app/javascript/src/components/Invoices/index.tsx has 794 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 · app/javascript/src/components/Invoices/InvoicePreview/index.tsx · ×1
  • app/javascript/src/components/Invoices/InvoicePreview/index.tsx: 788 lines of code app/javascript/src/components/Invoices/InvoicePreview/index.tsx:1 — app/javascript/src/components/Invoices/InvoicePreview/index.tsx has 788 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 · app/javascript/src/components/Profile/Personal/User/Edit/ProfileEditor.tsx · ×1
  • app/javascript/src/components/Profile/Personal/User/Edit/ProfileEditor.tsx: 778 lines of code app/javascript/src/components/Profile/Personal/User/Edit/ProfileEditor.tsx:1 — app/javascript/src/components/Profile/Personal/User/Edit/ProfileEditor.tsx has 778 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 · app/javascript/src/components/Payroll/Review.tsx · ×1
  • app/javascript/src/components/Payroll/Review.tsx: 774 lines of code app/javascript/src/components/Payroll/Review.tsx:1 — app/javascript/src/components/Payroll/Review.tsx has 774 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 · app/javascript/src/components/Reports/RevenueByClientReport/index.tsx · ×1
  • app/javascript/src/components/Reports/RevenueByClientReport/index.tsx: 774 lines of code app/javascript/src/components/Reports/RevenueByClientReport/index.tsx:1 — app/javascript/src/components/Reports/RevenueByClientReport/index.tsx has 774 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 · app/javascript/src/components/TaxDeclarations/index.tsx · ×1
  • app/javascript/src/components/TaxDeclarations/index.tsx: 772 lines of code app/javascript/src/components/TaxDeclarations/index.tsx:1 — app/javascript/src/components/TaxDeclarations/index.tsx has 772 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 · app/javascript/src/components/Reports/OutstandingInvoiceReport/WorkspaceView.tsx · ×1
  • app/javascript/src/components/Reports/OutstandingInvoiceReport/WorkspaceView.tsx: 757 lines of code app/javascript/src/components/Reports/OutstandingInvoiceReport/WorkspaceView.tsx:1 — app/javascript/src/components/Reports/OutstandingInvoiceReport/WorkspaceView.tsx has 757 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 · app/javascript/src/components/Payroll/RunPreparation.tsx · ×1
  • app/javascript/src/components/Payroll/RunPreparation.tsx: 752 lines of code app/javascript/src/components/Payroll/RunPreparation.tsx:1 — app/javascript/src/components/Payroll/RunPreparation.tsx has 752 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 · app/javascript/src/components/Profile/Organization/Payment/RazorpayConnection.tsx · ×1
  • app/javascript/src/components/Profile/Organization/Payment/RazorpayConnection.tsx: 751 lines of code app/javascript/src/components/Profile/Organization/Payment/RazorpayConnection.tsx:1 — app/javascript/src/components/Profile/Organization/Payment/RazorpayConnection.tsx has 751 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 · app/javascript/src/components/Profile/EmployeeRecords/index.tsx · ×1
  • app/javascript/src/components/Profile/EmployeeRecords/index.tsx: 743 lines of code app/javascript/src/components/Profile/EmployeeRecords/index.tsx:1 — app/javascript/src/components/Profile/EmployeeRecords/index.tsx has 743 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 · app/javascript/src/components/payments/PaymentsTable.tsx · ×1
  • app/javascript/src/components/payments/PaymentsTable.tsx: 717 lines of code app/javascript/src/components/payments/PaymentsTable.tsx:1 — app/javascript/src/components/payments/PaymentsTable.tsx has 717 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: 716 lines of code REDACTED:1 — REDACTED has 716 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 · app/javascript/src/components/TimeTracking/EntryForm.tsx · ×1
  • app/javascript/src/components/TimeTracking/EntryForm.tsx: 691 lines of code app/javascript/src/components/TimeTracking/EntryForm.tsx:1 — app/javascript/src/components/TimeTracking/EntryForm.tsx has 691 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 · app/javascript/src/components/TimesheetEntries/index.tsx · ×1
  • app/javascript/src/components/TimesheetEntries/index.tsx: 682 lines of code app/javascript/src/components/TimesheetEntries/index.tsx:1 — app/javascript/src/components/TimesheetEntries/index.tsx has 682 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 · app/javascript/src/components/Reports/AccountsAgingReport/index.tsx · ×1
  • app/javascript/src/components/Reports/AccountsAgingReport/index.tsx: 667 lines of code app/javascript/src/components/Reports/AccountsAgingReport/index.tsx:1 — app/javascript/src/components/Reports/AccountsAgingReport/index.tsx has 667 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 · app/javascript/src/components/Agreements/Editor.tsx · ×1
  • app/javascript/src/components/Agreements/Editor.tsx: 665 lines of code app/javascript/src/components/Agreements/Editor.tsx:1 — app/javascript/src/components/Agreements/Editor.tsx has 665 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 · app/javascript/src/components/Profile/Personal/User/Edit/MobileProfileEditor.tsx · ×1
  • app/javascript/src/components/Profile/Personal/User/Edit/MobileProfileEditor.tsx: 647 lines of code app/javascript/src/components/Profile/Personal/User/Edit/MobileProfileEditor.tsx:1 — app/javascript/src/components/Profile/Personal/User/Edit/MobileProfileEditor.tsx has 647 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 · app/javascript/src/components/Hiring/ApplicationAssignments.tsx · ×1
  • app/javascript/src/components/Hiring/ApplicationAssignments.tsx: 644 lines of code app/javascript/src/components/Hiring/ApplicationAssignments.tsx:1 — app/javascript/src/components/Hiring/ApplicationAssignments.tsx has 644 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 · app/javascript/src/components/Hiring/ReceiptDetail.tsx · ×1
  • app/javascript/src/components/Hiring/ReceiptDetail.tsx: 629 lines of code app/javascript/src/components/Hiring/ReceiptDetail.tsx:1 — app/javascript/src/components/Hiring/ReceiptDetail.tsx has 629 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 · app/javascript/src/components/Hiring/InterviewBookings.tsx · ×1
  • app/javascript/src/components/Hiring/InterviewBookings.tsx: 619 lines of code app/javascript/src/components/Hiring/InterviewBookings.tsx:1 — app/javascript/src/components/Hiring/InterviewBookings.tsx has 619 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 · app/javascript/src/components/Navbar/Sidebar.tsx · ×1
  • app/javascript/src/components/Navbar/Sidebar.tsx: 617 lines of code app/javascript/src/components/Navbar/Sidebar.tsx:1 — app/javascript/src/components/Navbar/Sidebar.tsx has 617 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 · app/javascript/src/components/Hiring/ApplicationInterviews.tsx · ×1
  • app/javascript/src/components/Hiring/ApplicationInterviews.tsx: 614 lines of code app/javascript/src/components/Hiring/ApplicationInterviews.tsx:1 — app/javascript/src/components/Hiring/ApplicationInterviews.tsx has 614 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 · app/javascript/src/components/Invoices/InvoiceList.tsx · ×1
  • app/javascript/src/components/Invoices/InvoiceList.tsx: 612 lines of code app/javascript/src/components/Invoices/InvoiceList.tsx:1 — app/javascript/src/components/Invoices/InvoiceList.tsx has 612 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R6 · Tooling · This package's lint script runs in no CI job · ×1
  • This package's lint script runs in no CI job docs/package.json:22 — The package in `docs` declares the lint script `lint` (`eslint "src/**/*.{js,jsx,ts,tsx}" --fix`), but no step of this repository's CI runs it, by name, through another script, a Makefile target or a workspace runner, and no CI step runs the linter over the package itself. The rules it sets are enforced nowhere a pull request can fail. Run it in CI: a step that runs `npm run lint` in `docs` (or the workspace's task runner).
R7 · Dead Code · Dead file (~763 LoC) · ×1
  • Dead file (~763 LoC) app/javascript/src/components/TimesheetEntries/index.tsx — no import path from any entry point (128 application, 14 tooling, 6 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 (~640 LoC) · ×1
  • Dead file (~640 LoC) app/javascript/src/components/Navbar/Sidebar.tsx — no import path from any entry point (128 application, 14 tooling, 6 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 (~557 LoC) · ×1
  • Dead file (~557 LoC) app/javascript/src/components/Reports/RevenueByClientReport/WorkspaceView.tsx — no import path from any entry point (128 application, 14 tooling, 6 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 (~512 LoC) · ×1
  • Dead file (~512 LoC) app/javascript/src/components/Invoices/List/FilterSideBar/index.tsx — no import path from any entry point (128 application, 14 tooling, 6 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 (~509 LoC) · ×1
  • Dead file (~509 LoC) app/javascript/src/components/Invoices/AdminDashboard/index.tsx — no import path from any entry point (128 application, 14 tooling, 6 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 (~496 LoC) · ×1
  • Dead file (~496 LoC) app/javascript/src/components/TimesheetEntries/TimeEntryForm/MobileEntryForm.tsx — no import path from any entry point (128 application, 14 tooling, 6 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (app/javascript/src/components/TimesheetEntries/TimeEntryForm/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 (~466 LoC) · ×1
  • Dead file (~466 LoC) app/javascript/src/components/Reports/Filters/FilterSideBar.tsx — no import path from any entry point (128 application, 14 tooling, 6 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (app/javascript/src/components/Reports/TimeEntryReport/Page.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 (~463 LoC) · ×1
  • Dead file (~463 LoC) app/javascript/src/components/Hiring/AssessmentPortal.tsx — no import path from any entry point (128 application, 14 tooling, 6 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (app/javascript/entrypoints/hiring_assignment.ts) — 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 (~453 LoC) · ×1
  • Dead file (~453 LoC) app/javascript/src/components/Reports/RevenueByClientReport/Filters/index.tsx — no import path from any entry point (128 application, 14 tooling, 6 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 (~437 LoC) · ×1
  • Dead file (~437 LoC) app/javascript/src/components/TimesheetEntries/WeekView/WeeklyEntriesCard.tsx — no import path from any entry point (128 application, 14 tooling, 6 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (app/javascript/src/components/TimesheetEntries/WeekView/WeeklyEntries.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 (~432 LoC) · ×1
  • Dead file (~432 LoC) app/javascript/src/components/Reports/Filters/Sidebar.tsx — no import path from any entry point (128 application, 14 tooling, 6 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 (~424 LoC) · ×1
  • Dead file (~424 LoC) app/javascript/src/components/Invoices/List/index.tsx — no import path from any entry point (128 application, 14 tooling, 6 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 (~414 LoC) · ×1
  • Dead file (~414 LoC) scripts/ci/authentication_flow.mjs — no import path from any entry point (128 application, 14 tooling, 6 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (scripts/ci/authentication_e2e.mjs) — 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 (~380 LoC) · ×1
  • Dead file (~380 LoC) app/javascript/src/components/Invoices/MonthlyRevenueChart/index.tsx — no import path from any entry point (128 application, 14 tooling, 6 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (app/javascript/src/components/Invoices/AdminDashboard/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 (~365 LoC) · ×1
  • Dead file (~365 LoC) app/javascript/src/components/DocumentSignatures/Review.tsx — no import path from any entry point (128 application, 14 tooling, 6 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (app/javascript/entrypoints/document_review.ts) — 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 (~364 LoC) · ×1
  • Dead file (~364 LoC) app/javascript/src/common/CustomDateRangeWIthInput/index.tsx — no import path from any entry point (128 application, 14 tooling, 6 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (app/javascript/src/components/Reports/Filters/DateRangeFilter.tsx, app/javascript/src/components/Reports/Filters/SidebarDateRangeFilter.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 (~307 LoC) · ×1
  • Dead file (~307 LoC) app/javascript/src/components/Team/modals/AddEditMember.tsx — no import path from any entry point (128 application, 14 tooling, 6 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (app/javascript/src/components/Team/modals/Modals.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 (~296 LoC) · ×1
  • Dead file (~296 LoC) app/javascript/src/components/Reports/Filters/index.tsx — no import path from any entry point (128 application, 14 tooling, 6 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 (~263 LoC) · ×1
  • Dead file (~263 LoC) app/javascript/src/components/Profile/Organization/Import/importModal.tsx — no import path from any entry point (128 application, 14 tooling, 6 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (app/javascript/src/components/Profile/Organization/Import/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 (~250 LoC) · ×1
  • Dead file (~250 LoC) app/javascript/src/components/Reports/TimeEntryReport/Page.tsx — no import path from any entry point (128 application, 14 tooling, 6 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 (~221 LoC) · ×1
  • Dead file (~221 LoC) app/javascript/src/components/TimesheetEntries/TimeEntryForm/index.tsx — no import path from any entry point (128 application, 14 tooling, 6 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (app/javascript/src/components/TimesheetEntries/TimeEntryManager/index.tsx, app/javascript/src/components/TimesheetEntries/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 (~220 LoC) · ×1
  • Dead file (~220 LoC) app/javascript/src/components/Hiring/OfferPortal.tsx — no import path from any entry point (128 application, 14 tooling, 6 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (app/javascript/entrypoints/hiring_offer.ts) — 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 (~201 LoC) · ×1
  • Dead file (~201 LoC) app/javascript/src/components/Invoices/ThemeToggle/index.tsx — no import path from any entry point (128 application, 14 tooling, 6 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 (~196 LoC) · ×1
  • Dead file (~196 LoC) app/javascript/src/components/Reports/Filters/SidebarGroupByFilter.tsx — no import path from any entry point (128 application, 14 tooling, 6 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (app/javascript/src/components/Reports/Filters/Sidebar.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 (~195 LoC) · ×1
  • Dead file (~195 LoC) app/javascript/src/components/Invoices/RecentSales/index.tsx — no import path from any entry point (128 application, 14 tooling, 6 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 (~191 LoC) · ×1
  • Dead file (~191 LoC) scripts/qa/payroll-review-approval-state.mjs — no import path from any entry point (128 application, 14 tooling, 6 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 (~174 LoC) · ×1
  • Dead file (~174 LoC) app/javascript/entrypoints/profitability_planning.ts — no import path from any entry point (128 application, 14 tooling, 6 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
R8 · Dependency Hygiene · Unused dependency '@fontsource-variable/inter' · ×1
  • Unused dependency '@fontsource-variable/inter' package.json:5 — 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 '@fontsource/plus-jakarta-sans' · ×1
  • Unused dependency '@fontsource/plus-jakarta-sans' package.json:6 — 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 '@radix-ui/react-accordion' · ×1
  • Unused dependency '@radix-ui/react-accordion' package.json:9 — 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 '@radix-ui/react-aspect-ratio' · ×1
  • Unused dependency '@radix-ui/react-aspect-ratio' package.json:10 — 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 '@radix-ui/react-hover-card' · ×1
  • Unused dependency '@radix-ui/react-hover-card' package.json:16 — 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 '@radix-ui/react-navigation-menu' · ×1
  • Unused dependency '@radix-ui/react-navigation-menu' package.json:19 — 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 '@radix-ui/react-progress' · ×1
  • Unused dependency '@radix-ui/react-progress' package.json:21 — 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 '@radix-ui/react-separator' · ×1
  • Unused dependency '@radix-ui/react-separator' package.json:25 — 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 '@radix-ui/react-toggle' · ×1
  • Unused dependency '@radix-ui/react-toggle' package.json:29 — 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 'currency-symbol-map' · ×1
  • Unused dependency 'currency-symbol-map' package.json:52 — 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 'html-react-parser' · ×1
  • Unused dependency 'html-react-parser' package.json:57 — 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 'react-infinite-scroll-component' · ×1
  • Unused dependency 'react-infinite-scroll-component' package.json:74 — 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 'react-transition-group' · ×1
  • Unused dependency 'react-transition-group' package.json:82 — 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 'spark-md5' · ×1
  • Unused dependency 'spark-md5' package.json:87 — 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 'react-native-web' · ×1
  • Unused dependency 'react-native-web' apps/mobile/package.json:22 — Declared in apps/mobile/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.
X24 · Document value interpolated into markup unescaped · Untrusted text written into markup unescaped · ×1
  • Untrusted text written into markup unescaped REDACTED:79 — `Object.entries(THEMES).map(([theme,prefix])=>` ${prefix} [data-chart=${id}] { ${colorConfig.map(([key,itemConfig])=>{…` is text this program did not author, and it is written into the text of an element through `dangerouslySetInnerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Minor — 235 finding(s)
D34 · Knowledge Freshness · Orphaned file · ×108
  • Orphaned file app/javascript/src/components/TimesheetEntries/TimeEntryForm/MobileEntryForm.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 app/javascript/src/components/Invoices/List/FilterSideBar/index.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 app/javascript/src/constants/currencyList.ts: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 app/javascript/src/components/Analytics/ClientInsightsPage.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 app/javascript/src/components/Analytics/ExpenseTrendsPage.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 app/javascript/src/components/Reports/Filters/FilterSideBar.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 app/javascript/src/components/Reports/RevenueByClientReport/Filters/index.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 app/javascript/src/components/Analytics/index.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 app/javascript/src/components/Analytics/RevenueForecastPage.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 app/javascript/src/components/Analytics/TeamAnalyticsPage.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 config/initializers/new_framework_defaults_7_1.rb: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 app/javascript/src/components/TimeoffEntries/TimeoffForm/MobileTimeoffForm.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 config/initializers/pagy.rb: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 app/javascript/src/components/Team/modals/AddEditMember.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 app/javascript/src/components/Invoices/List/Table/TableRow.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 app/javascript/src/constants/countryList.ts: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 app/javascript/src/components/Reports/Filters/index.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 app/javascript/src/components/Invoices/MultipleEntriesModal/Filters/index.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 app/javascript/src/components/Invoices/List/MoreOptions.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 app/javascript/src/components/Clients/Details/index.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 app/services/analytics/exports/formatter.rb: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 app/services/timeoff_entries/calculate_total_duration_of_defined_leaves_service.rb: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 app/javascript/src/components/Navbar/utils.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 app/javascript/src/components/Team/modals/TeamForm.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 app/services/analytics/client_revenue_analytics.rb: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.
  • + 83 more in this group — see findings.md.
X10 · Duplicated predicate · Duplicated predicate · ×40
  • Duplicated predicate app/javascript/src/components/ClientInvoices/Details/Header.tsx:52 — `!!paypalPayment?.enabled && !!paypalPayment?.url` appears character-identically in 2 files — app/javascript/src/components/ClientInvoices/Details/Header.tsx, app/javascript/src/components/InvoiceEmail/Header.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 app/javascript/src/components/TimeTracking/EntryForm.tsx:544 — `!client && "opacity-50 cursor-not-allowed"` appears character-identically in 2 files — app/javascript/src/components/TimeTracking/EntryForm.tsx, app/javascript/src/components/TimeTracking/SelectProject.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 app/javascript/src/components/Hiring/AssessmentPortal.tsx:164 — `!file.size || file.size > 5 * 1024 * 1024` appears character-identically in 2 files — app/javascript/src/components/Hiring/AssessmentPortal.tsx, app/javascript/src/components/Hiring/Portal.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 app/javascript/src/components/TimeTracking/Header.tsx:145 — `!isDesktop && setOpenOsCalendar(!openOsCalendar)` appears character-identically in 2 files — app/javascript/src/components/TimeTracking/Header.tsx, app/javascript/src/components/TimesheetEntries/Header/CalendarNavigator/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 app/javascript/src/components/Clients/ClientForm/UploadLogo.tsx:24 — `!isValid.fileExtension && !isValid.fileSizeValid` appears character-identically in 2 files — app/javascript/src/components/Clients/ClientForm/UploadLogo.tsx, app/javascript/src/components/OrganizationSetup/CompanyDetailsForm/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 app/javascript/src/components/Profile/EmployeeRecords/Reports.tsx:58 — `(await errorMessage(failure)) || text("failed")` appears character-identically in 2 files — app/javascript/src/components/Profile/EmployeeRecords/Reports.tsx, app/javascript/src/components/Profile/EmployeeRecords/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 app/javascript/src/components/Invoices/InvoiceEditor/index.tsx:567 — `address.address_line_1 || address.addressLine1` appears character-identically in 2 files — app/javascript/src/components/Invoices/InvoiceEditor/index.tsx, app/javascript/src/components/Invoices/InvoicePreview/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 app/javascript/src/components/Invoices/InvoiceEditor/index.tsx:568 — `address.address_line_2 || address.addressLine2` appears character-identically in 2 files — app/javascript/src/components/Invoices/InvoiceEditor/index.tsx, app/javascript/src/components/Invoices/InvoicePreview/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 app/javascript/src/components/Invoices/InvoiceEditor/index.tsx:572 — `address.pin || address.postalCode || address.zipCode` appears character-identically in 2 files — app/javascript/src/components/Invoices/InvoiceEditor/index.tsx, app/javascript/src/components/Invoices/InvoicePreview/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 app/javascript/src/components/Hiring/ApplicationDetail.tsx:135 — `application.owner?.full_name || "Unassigned"` appears character-identically in 3 files — app/javascript/src/components/Hiring/ApplicationDetail.tsx, app/javascript/src/components/Hiring/Pipeline.tsx, app/javascript/src/components/Hiring/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 app/javascript/src/components/Hiring/ApplicationDetail.tsx:130 — `application.role?.title || "No role yet"` appears character-identically in 3 files — app/javascript/src/components/Hiring/ApplicationDetail.tsx, app/javascript/src/components/Hiring/Pipeline.tsx, app/javascript/src/components/Hiring/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 app/javascript/src/components/Hiring/ApplicationDecisions.tsx:225 — `axios.isAxiosError(failure) && failure.response && failure.response.status < 500` appears character-identically in 3 files — app/javascript/src/components/Hiring/ApplicationDecisions.tsx, app/javascript/src/components/Hiring/ApplicationOffers.tsx, app/javascript/src/components/Hiring/Onboarding.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 app/javascript/src/components/payments/Mobile/Table/TableRow.tsx:43 — `baseCurrency && currencyFormat(baseCurrency, amount)` appears character-identically in 2 files — app/javascript/src/components/payments/Mobile/Table/TableRow.tsx, app/javascript/src/components/payments/Table/TableRow.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 app/javascript/src/components/ConsultantPayroll/index.tsx:457 — `busy || archive.pagination.page >= archive.pagination.pages` appears character-identically in 3 files — app/javascript/src/components/ConsultantPayroll/index.tsx, app/javascript/src/components/SalarySlips/index.tsx, app/javascript/src/components/TaxDeclarations/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 app/javascript/src/components/TimeTracking/MobileView/MobileEntryForm.tsx:69 — `client && project && note && selectedDate && duration` appears character-identically in 2 files — app/javascript/src/components/TimeTracking/MobileView/MobileEntryForm.tsx, app/javascript/src/components/TimesheetEntries/TimeEntryForm/MobileEntryForm.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 app/javascript/src/components/ClientInvoices/Details/InvoiceDetails.tsx:63 — `company.dateFormat || company.date_format` appears character-identically in 3 files — app/javascript/src/components/ClientInvoices/Details/InvoiceDetails.tsx, app/javascript/src/components/ClientInvoices/Details/MobileView/index.tsx, app/javascript/src/components/InvoiceEmail/InvoiceDetails.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 app/javascript/src/components/TimeTracking/TimeEntriesDisplay.tsx:55 — `company?.date_format || company?.dateFormat` appears character-identically in 2 files — app/javascript/src/components/TimeTracking/TimeEntriesDisplay.tsx, app/javascript/src/components/TimeoffEntries/TimeoffForm/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 app/javascript/src/components/TimeTracking/EntryForm.tsx:74 — `company?.date_format || company?.dateFormat || "MM-DD-YYYY"` appears character-identically in 4 files — app/javascript/src/components/TimeTracking/EntryForm.tsx, app/javascript/src/components/TimeTracking/MobileView/MobileEntryForm.tsx, app/javascript/src/components/TimeTracking/MonthCalendar.tsx, app/javascript/src/components/TimeTracking/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 app/javascript/src/components/TimeTracking/WeeklyEntriesCard.tsx:68 — `currentEntries[num] && ["unbilled", "billed"].includes(currentEntries[num]["bill_status"])` appears character-identically in 2 files — app/javascript/src/components/TimeTracking/WeeklyEntriesCard.tsx, app/javascript/src/components/TimesheetEntries/WeekView/WeeklyEntriesCard.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 app/javascript/src/components/Analytics/useAnalyticsFilters.ts:85 — `currentFrom === nextFromString && currentTo === nextToString` appears character-identically in 4 files — app/javascript/src/components/Analytics/useAnalyticsFilters.ts, app/javascript/src/components/Reports/PaymentReport/index.tsx, app/javascript/src/components/Reports/RevenueByClientReport/index.tsx, app/javascript/src/components/Reports/TimeEntryReport/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 app/javascript/src/components/Reports/PaymentReport/index.tsx:544 — `date > new Date() || date < new Date("1900-01-01")` appears character-identically in 3 files — app/javascript/src/components/Reports/PaymentReport/index.tsx, app/javascript/src/components/Reports/RevenueByClientReport/index.tsx, app/javascript/src/components/Reports/TimeEntryReport/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 app/javascript/src/components/Invoices/InvoiceEditor/index.tsx:131 — `date instanceof Date && !isNaN(date.getTime())` appears character-identically in 2 files — app/javascript/src/components/Invoices/InvoiceEditor/index.tsx, app/javascript/src/services/invoiceApi.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 app/javascript/src/common/CustomDateRangePicker/index.tsx:122 — `dayjs(dateInput).format(validFormat) == dateInput || new Date(dateInput).toString() == dateInput` appears character-identically in 2 files — app/javascript/src/common/CustomDateRangePicker/index.tsx, app/javascript/src/common/CustomDateRangeWIthInput/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 app/javascript/src/common/CustomDateRangePicker/index.tsx:153 — `dayjs(dateInput).isAfter(dateRange.from, "day") || dayjs(dateInput).isSame(dateRange.from, "day")` appears character-identically in 2 files — app/javascript/src/common/CustomDateRangePicker/index.tsx, app/javascript/src/common/CustomDateRangeWIthInput/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 app/javascript/src/common/CustomDateRangePicker/index.tsx:146 — `dayjs(dateInput).isBefore(dateRange.to, "day") || dayjs(dateInput).isSame(dateRange.to, "day")` appears character-identically in 2 files — app/javascript/src/common/CustomDateRangePicker/index.tsx, app/javascript/src/common/CustomDateRangeWIthInput/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 · ×26
  • Pending state with no failure state app/javascript/src/components/PlanAccessGate.tsx:22 — The view draws `<Loader class="h-screen"/>` under `loading && ! effectiveCompany`, but `loading` 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 app/javascript/src/components/payments/index.tsx:92 — The view draws `<Loader/>` under `loading`, but `loading` 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 app/javascript/src/components/TimesheetEntries/index.tsx:617 — The view draws `<Loader/>` under `loading`, but `loading` 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 app/javascript/src/components/Team/List/index.tsx:91 — The view draws `<Loader/>` under `loading`, but `loading` 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 app/javascript/src/components/Reports/TimeEntryReport/Page.tsx:195 — The view draws `<Loader/>` under `loading`, but `loading` 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 app/javascript/src/components/Projects/Details/index.tsx:154 — The view draws `<Loader/>` under `loading`, but `loading` 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 app/javascript/src/components/Profile/Personal/User/index.tsx:133 — The view draws `<Loader class="min-h-70v"/>` 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 app/javascript/src/components/Profile/Personal/NotificationPreferences/index.tsx:102 — The view draws `<div class="flex min-h-70v items-center justify-center">` under `isLoading || userLoading`, 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 app/javascript/src/components/Profile/Personal/Employment/index.tsx:89 — The view draws `<Loader class="min-h-70v"/>` 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 app/javascript/src/components/Profile/Personal/Devices/index.tsx:76 — The view draws `<Loader class="min-h-[60vh]"/>` 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 app/javascript/src/components/Profile/Personal/Devices/Edit/index.tsx:103 — The view draws `<Loader class="min-h-screen flex items-center justify-center"/>` 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 app/javascript/src/components/Profile/Organization/TaxConfiguration/index.tsx:159 — The view draws `Loading...` 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 app/javascript/src/components/Profile/Organization/Edit/index.tsx:567 — The view draws `<Loader class="min-h-screen flex items-center justify-center"/>` 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 app/javascript/src/components/Profile/Layout/Navigation/MobileNav.tsx:83 — The view draws `<div class="flex h-80v w-full flex-col justify-center">` 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 app/javascript/src/components/LeaveManagement/index.tsx:130 — The view draws `<Loader/>` under `isLoading || ! user`, 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 app/javascript/src/components/Invoices/Invoice/ViewHistory/index.tsx:55 — The view draws `<div class="flex h-full items-center justify-center">` under `loading`, but `loading` 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 app/javascript/src/components/InvoiceEmail/index.tsx:48 — The view draws `<div class="flex h-80v w-full flex-col justify-center">` under `loading`, but `loading` 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 app/javascript/src/components/Expenses/List/index.tsx:64 — The view draws `<div class="flex h-80v w-full flex-col justify-center">` 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 app/javascript/src/components/Expenses/Details/index.tsx:88 — The view draws `<div class="flex h-80v w-full flex-col justify-center">` 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 app/javascript/src/components/Dashboard/DashboardHome.tsx:431 — The view draws `<>` under `isFetchingNextPage`, but `isFetchingNextPage` 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 app/javascript/src/components/Clients/index.tsx:88 — The view draws `<Loader/>` under `loading`, but `loading` 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 app/javascript/src/components/Clients/Details/index.tsx:107 — The view draws `<Loader/>` under `loading`, but `loading` 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 app/javascript/src/components/Clients/Contacts/index.tsx:60 — The view draws `<Loader/>` 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 app/javascript/src/components/ClientInvoices/index.tsx:108 — The view draws `<Loader/>` under `loading`, but `loading` 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 app/javascript/src/components/ClientInvoices/Details/index.tsx:44 — The view draws `<Loader/>` under `loading`, but `loading` 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.
  • + 1 more in this group — see findings.md.
P2 · Observability · Console output used as the logging channel · ×21
  • Console output used as the logging channel app/javascript/src/hooks/useDashboard.ts:50 — `app/javascript/src/hooks/useDashboard.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 app/javascript/src/hooks/useDashboard.ts:76 — `app/javascript/src/hooks/useDashboard.ts` reports through `console.*` at line 76 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 app/javascript/src/hooks/useDashboard.ts:111 — `app/javascript/src/hooks/useDashboard.ts` reports through `console.*` at line 111 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 app/javascript/src/hooks/useDashboard.ts:129 — `app/javascript/src/hooks/useDashboard.ts` reports through `console.*` at line 129 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 app/javascript/src/components/payments/Header.tsx:52 — `app/javascript/src/components/payments/Header.tsx` reports through `console.*` at line 52 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 app/javascript/src/components/TimesheetEntries/FloatingTimer.tsx:143 — `app/javascript/src/components/TimesheetEntries/FloatingTimer.tsx` reports through `console.*` at line 143 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 app/javascript/src/components/TimeTracking/WeeklyEntries.tsx:144 — `app/javascript/src/components/TimeTracking/WeeklyEntries.tsx` reports through `console.*` at line 144 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 app/javascript/src/components/Team/List/Header.tsx:33 — `app/javascript/src/components/Team/List/Header.tsx` reports through `console.*` at line 33 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 app/javascript/src/components/Settings/Preferences/index.tsx:144 — `app/javascript/src/components/Settings/Preferences/index.tsx` reports through `console.*` at line 144 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 app/javascript/src/components/Settings/Preferences/index.tsx:182 — `app/javascript/src/components/Settings/Preferences/index.tsx` reports through `console.*` at line 182 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 app/javascript/src/components/Profile/Personal/User/index.tsx:62 — `app/javascript/src/components/Profile/Personal/User/index.tsx` reports through `console.*` at line 62 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 app/javascript/src/components/Profile/Personal/User/Edit/index.tsx:125 — `app/javascript/src/components/Profile/Personal/User/Edit/index.tsx` reports through `console.*` at line 125 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 app/javascript/src/components/Profile/Personal/Employment/index.tsx:52 — `app/javascript/src/components/Profile/Personal/Employment/index.tsx` reports through `console.*` at line 52 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 app/javascript/src/components/Profile/Personal/Employment/Edit/index.tsx:122 — `app/javascript/src/components/Profile/Personal/Employment/Edit/index.tsx` reports through `console.*` at line 122 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 app/javascript/src/components/Profile/Organization/Details/Page.tsx:119 — `app/javascript/src/components/Profile/Organization/Details/Page.tsx` reports through `console.*` at line 119 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 app/javascript/src/components/Invoices/usePaginatedInvoices.ts:84 — `app/javascript/src/components/Invoices/usePaginatedInvoices.ts` reports through `console.*` at line 84 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 app/javascript/src/components/Invoices/MonthlyRevenueChart/index.tsx:142 — `app/javascript/src/components/Invoices/MonthlyRevenueChart/index.tsx` reports through `console.*` at line 142 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 app/javascript/src/components/Invoices/List/RecentlyUpdated/InfiniteScrollRecentlyUpdated.tsx:101 — `app/javascript/src/components/Invoices/List/RecentlyUpdated/InfiniteScrollRecentlyUpdated.tsx` reports through `console.*` at line 101 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 app/javascript/src/components/Invoices/Invoice/PaymentDetails.tsx:35 — `app/javascript/src/components/Invoices/Invoice/PaymentDetails.tsx` reports through `console.*` at line 35 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 app/javascript/src/components/Invoices/Invoice/ViewHistory/index.tsx:22 — `app/javascript/src/components/Invoices/Invoice/ViewHistory/index.tsx` reports through `console.*` at line 22 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 app/javascript/src/components/Clients/ClientsTable.tsx:128 — `app/javascript/src/components/Clients/ClientsTable.tsx` 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.
D24 · Comment Value · redundant comment · ×10
  • redundant comment REDACTED:593 — "Reports (Time Entries)" repeats the code it sits on: 3 of its 3 words (reports, time, entries) are already in `export const reportsApi = {`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment REDACTED:604 — "Reports: Accounts Aging" repeats the code it sits on: 3 of its 3 words (reports, accounts, aging) are already in `export const reportsAccountsAgingApi = {`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment REDACTED:612 — "Reports: Outstanding/Overdue" repeats the code it sits on: 3 of its 3 words (reports, outstanding, overdue) are already in `export const reportsOutstandingOverdueInvoiceApi = {`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment REDACTED:620 — "Reports: Client Revenue" repeats the code it sits on: 3 of its 3 words (reports, client, revenue) are already in `export const reportsClientRevenueApi = {`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment app/javascript/src/components/Invoices/index.tsx:579 — "Call the download API" repeats the code it sits on: 3 of its 3 words (call, download, api) are already in `const blob = await invoiceApi.downloadInvoice(id);`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment app/javascript/src/components/Navbar/Sidebar.tsx:156 — "Personal settings items" repeats the code it sits on: 3 of its 3 words (personal, settings, items) are already in `const personalSettingsItems = [`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment app/javascript/src/components/Navbar/Sidebar.tsx:205 — "Organization settings items" repeats the code it sits on: 3 of its 3 words (organization, settings, items) are already in `const orgSettingsItems = [`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment spec/e2e/time-tracking.spec.ts:87 — "Click Add Entry" repeats the code it sits on: 3 of its 3 words (click, add, entry) are already in `await page.getByRole('button', { name: 'Add Entry' }).click();`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment spec/e2e/time-tracking.spec.ts:147 — "Click Today button" repeats the code it sits on: 3 of its 3 words (click, today, button) are already in `await page.getByRole('button', { name: 'Today' }).click();`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment tests/invoice-pdf.spec.ts:26 — 8 comments in this file only repeat the code they sit on (lines 26, 32, 56, 59, 62, 76, 113, 116), for example "Wait for invoice detail page". Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
IC1 · Incompleteness & stubs · Blanket warning suppression · ×6
  • Blanket warning suppression app/javascript/src/common/Mobile/HOC/withLayout/index.tsx:1 — A bare `eslint-disable` or `@ts-nocheck` with no rule list switches every lint rule or the whole type checker off for the rest of the file — hidden debt. Disable the specific rule on the specific line, with a justification, instead.
  • Blanket warning suppression app/javascript/src/components/TimeTracking/Header.tsx:1 — A bare `eslint-disable` or `@ts-nocheck` with no rule list switches every lint rule or the whole type checker off for the rest of the file — hidden debt. Disable the specific rule on the specific line, with a justification, instead.
  • Blanket warning suppression app/javascript/src/components/TimesheetEntries/Header/CalendarNavigator/index.tsx:1 — A bare `eslint-disable` or `@ts-nocheck` with no rule list switches every lint rule or the whole type checker off for the rest of the file — hidden debt. Disable the specific rule on the specific line, with a justification, instead.
  • Blanket warning suppression app/javascript/src/components/TimesheetEntries/Header/index.tsx:1 — A bare `eslint-disable` or `@ts-nocheck` with no rule list switches every lint rule or the whole type checker off for the rest of the file — hidden debt. Disable the specific rule on the specific line, with a justification, instead.
  • Blanket warning suppression app/javascript/src/components/TimesheetEntries/WeekView/WeeklyEntriesCard.tsx:1 — A bare `eslint-disable` or `@ts-nocheck` with no rule list switches every lint rule or the whole type checker off for the rest of the file — hidden debt. Disable the specific rule on the specific line, with a justification, instead.
  • Blanket warning suppression app/javascript/src/components/TimesheetEntries/index.tsx:1 — A bare `eslint-disable` or `@ts-nocheck` with no rule list switches every lint rule or the whole type checker off for the rest of the file — hidden debt. Disable the specific rule on the specific line, with a justification, instead.
X7 · Silent fallback defaults · Silent fallback default in rescue · ×4
  • Silent fallback default in rescue app/controllers/agent_readiness_controller.rb:263 — `miru_version` rescues every error into `"3.0.0"` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the rescue or above the method, and the row stops firing.
  • Silent fallback default in rescue app/mcp/server_factory.rb:46 — `normalized_context` rescues every error into `{}` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the rescue or above the method, and the row stops firing.
  • Silent fallback default in rescue app/mcp/server_factory.rb:52 — `miru_version` rescues every error into `"0.0.0"` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the rescue or above the method, and the row stops firing.
  • Silent fallback default in rescue app/mcp/tools/base_tool.rb:90 — `context` rescues every error into `{}` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the rescue or above the method, and the row stops firing.
D31 · IaC & Container Security · Low IaC · ×2
  • REDACTED
  • REDACTED
M4 · Documentation accuracy · README/code drift · ×2
  • README/code drift docs/README.md:76 — docs/README.md names React 18, but the manifest declares `react` 19.1.10. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift docs/intro.md:90 — docs/intro.md names React 18, but the manifest declares `react` 19.1.10. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
X7 · Silent fallback defaults · Silent fallback default in catch · ×2
  • Silent fallback default in catch app/javascript/src/i18n/index.ts:176 — `getStoredBrowserCountry` swallows every exception into `return ""` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
  • Silent fallback default in catch app/javascript/src/i18n/index.ts:188 — `getStoredBrowserTimeZone` swallows every exception into `return ""` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
D16 · Bus Factor · Off-boarding risk · ×1
  • Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 199 significant file(s) lose their only recent owner: app/javascript/src/i18n/locales/ta.ts, app/javascript/src/i18n/locales/ml.ts, app/javascript/src/i18n/locales/te.ts, app/javascript/src/i18n/locales/kn.ts, app/javascript/src/i18n/locales/bn.ts, app/javascript/src/i18n/locales/hi.ts, app/javascript/src/i18n/locales/mr.ts, app/javascript/src/i18n/locales/gu.ts (+191 more). Pair on, review, or document these before any departure.
D21 · Naming Consistency · `{ title, description, ctaLabel = "View invoices", ctaPath = Paths.INVOICES.replace("/*", ""), }` spells `INVOICES` where 25 names in the project spell it `Invoices` · ×1
  • `{ title, description, ctaLabel = "View invoices", ctaPath = Paths.INVOICES.replace("/*", ""), }` spells `INVOICES` where 25 names in the project spell it `Invoices` app/javascript/src/components/Analytics/components/AnalyticsStates.tsx:62 — 25 of 26 names in project @saeloun/miru-web spell the token `Invoices` (25 of 26; unit: names in project @saeloun/miru-web containing `Invoices`). Peers: NoInvoices.NoInvoices (app/javascript/src/components/ClientInvoices/List/NoInvoices.tsx:5); index.ClientInvoices (app/javascript/src/components/ClientInvoices/index.tsx:14); MobileInvoicesList.MobileInvoicesList (app/javascript/src/components/Clients/Modals/PaymentReminder/MobileView/MobileInvoicesList.tsx:8); AdminDashboardProps.fetchInvoices (app/javascript/src/components/Invoices/AdminDashboard/index.tsx:43); InvoiceListProps.totalInvoices (app/javascript/src/components/Invoices/InvoiceList.tsx:56). Rename to `{ title, description, ctaLabel = "View invoices", ctaPath = Paths.Invoices.replace("/*", ""), }`. [rule N6]
D26 · Project Cohesion · Projects may be oversized for their cohesion · ×1
  • Projects may be oversized for their cohesion package.json:1 — `(repository root)` (233180 LoC, 2299 module-visible types across 355 directories) overshoots its size bounds. 1 of 4 build unit(s) (Go, npm) overshoot their size bounds, lowering Project Cohesion to 5.0/10. Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
D27 · Navigability · Pass-through layer · ×1
  • Pass-through layer app/javascript/src/components/ui/toastr.tsx:3 — Toastr: all 4 public methods forward their arguments unchanged to toast and add no behaviour — an extra hop (and usually an extra interface) to trace through. Call toast directly, or give the layer a job.
D28 · Secrets (history) · Rotate the exposed credentials · ×1
  • REDACTED
D34 · Knowledge Freshness · Further orphaned files (smaller) · ×1
  • Further orphaned files (smaller) — 108 smaller file(s) also have no living knowledge — folded into the freshness score and metrics rather than raised one row each — most significant first: app/javascript/src/components/TimesheetEntries/TimeEntryForm/MobileEntryForm.tsx, app/javascript/src/components/Invoices/List/FilterSideBar/index.tsx, app/javascript/src/constants/currencyList.ts, app/javascript/src/components/Analytics/ClientInsightsPage.tsx, app/javascript/src/components/Analytics/ExpenseTrendsPage.tsx, app/javascript/src/components/Reports/Filters/FilterSideBar.tsx, app/javascript/src/components/Reports/RevenueByClientReport/Filters/index.tsx, app/javascript/src/components/Analytics/index.tsx (and 100 more) (110 orphaned of 724 analysed files in total, counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated, example/demo and scaffolding-template trees and test files identified by path convention, largest first; 724 of the 1959 production source files in this repository met that bar). Attach the read to the next change that touches one of them: have a second person review that change, and leave behind a short comment or test recording what the file is for, so the knowledge comes back at the cost of a change you were making anyway.
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
P3 · Security & performance tooling · No dependency-update automation · ×1
  • No dependency-update automation package.json:4 — `package.json` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`.
P4 · Deployment & Rollback · No release approval gate · ×1
  • No release approval gate .github/workflows/docker-build.yml:70 — Deployment is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever reaches the release trigger goes to production unreviewed, so a mistaken merge or tag is live before anyone can stop it.
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 2/26 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 — 1/2 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.2 `!` null assertions per 1k TypeScript source lines — 30 assertion(s) across the 185352 source line(s) of the 806 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: app/javascript/entrypoints/profitability_planning.ts (15), app/javascript/src/components/Hiring/ApplicationAssignments.tsx (3), app/javascript/src/components/Hiring/InterviewReviews.tsx (3). 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.
X7 · Silent fallback defaults · Silent fallback default on lookup miss · ×1
  • Silent fallback default on lookup miss app/services/payroll/india_handoff.rb:82 — `dispatch_blocker` answers `"consultant_inactive"` when `RecordNotFound` is raised, with no log or raise — a missing file, record or key silently becomes that value. Log the miss or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the rescue or above the method, and the row stops firing.
Minor — 1 finding(s)
D12 · Dependency Hygiene · Outdated · ×1
  • Outdated: golang.org/x/term — `golang.org/x/term` is required at v0.45.0 in REDACTED, but v0.48.0 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get golang.org/x/term@v0.48.0 && go mod tidy` and commit the updated REDACTED and go.sum.

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-0c4ed4ca740345beb1ff2daa94b1c635/history.json --exit-code 0 --source .2artifacts/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-0c4ed4ca740345beb1ff2daa94b1c635/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=2442" --report-format json --report-path /tmp/watchdog-gitleaks-0c4ed4ca740345beb1ff2daa94b1c635/history-2.json --exit-code 0 --source .3artifacts/raw/gitleaks-history-2.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-0c4ed4ca740345beb1ff2daa94b1c635/tree.json --exit-code 0 --source .2artifacts/raw/gitleaks-tree.json
D29 · Static Analysis (SAST)semgrep—semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt --exclude vendor .38artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilitiestrivy—trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** .3artifacts/raw/trivy-fs.json
D31 · IaC & Container Securitytrivy—trivy config --format json --quiet .26artifacts/raw/trivy-config.json
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 --exclude vendor .3artifacts/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 01a1e8e7-66be-72a5-9a0d-504de39316f0 · 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