Public report of calcom/cal.diy, published 26 October 2026. It has the same score, grades and number of
findings as the full report. The details of security findings (where they are in the code, which known
vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive reportMeasured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.10.5). 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, 26 October 2026, 16:56 UTC · Survey ID cd_fcc46847d2da45cbbcecf34bf0dc4474
calcom/cal.diy
Measured 26 October 2026, 16:52 UTC, at code version 0f19cc4
Regression: 2 dimensions fell since the last survey
A regression is a drop of 0.5 points or more in the score, or of 2.5 or more out of 10 in a dimension, since the last survey.
CAI scoreAt riskDown 2 since the last survey
The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.
A large codebase: 334,040 lines of product code in 111 projects, tests not counted · Estimated rebuild effort: about 3.8 person-years · Weakest lens: Production Readiness, 22
Findings by how serious they are
440 critical2215 serious1695 minor
8 dimensions are left out of the score. For each one, Watchdog either couldn't measure it in this code, or found no evidence of the safeguard it looks for, such as a tested backup restore. They count neither for nor against the score, and Limitations lists each one with its reason.
This survey was produced by
Watchdog
Producer
Canine Development
Analyzer
Watchdog engine 1.0.0
Measured
26 October 2026, 16:52 UTC
A measurement, not a certificate. The Code Assurance Index records a number
together with the evidence it was worked out from, so anyone can recalculate it, but it doesn't certify or guarantee
the code. The standard was written by Canine Development, which also builds Watchdog. It is open to any tool that
implements it, and today Watchdog is the only one that does.
A critical security finding is open, such as a library with a known critical vulnerability or a password or key found in the code. The score itself is unchanged, but its band shows At risk until the finding is fixed. See the Security and Compliance lens.
The score is deterministic, which means the same code always gets the same score. Watchdog works it out with tools that follow published rules, and an AI model never decides it, so anyone who applies the same rules to the same code gets the same number. How it is done is explained under Methodology ▸
96of 96 dimensions measured by tools.
4127of 4350 findings point to an exact file and line, so you can open each one in the code. The other 223 concern the repository as a whole, such as missing documentation.
96dimensions across 8 lenses, read from 334,040 lines of product code in 111 projects.
calcom/cal.diy is rated At risk because critical security findings are open, most of them in the build pipeline. Its score is held back because six passwords or keys sit in the current code and we found no automated security scanning of the code, its secrets or its dependencies. It scores 32 out of 100, which the At risk rating leaves unchanged.
Production Readiness, at 22, is the weakest lens and counts most in the score. The best first step is replacing the six exposed passwords or keys and switching the old ones off, worth about 8 points. Fixing the test command with no tests behind it comes next, worth about 2 points. Raising Production Readiness to 70 would lift the score to about 40.
102 pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Eighty-one known security holes in the packages the code depends on can be used by attackers, and seventy-one secrets can leak from the build pipeline. Pinning each tool to an exact version, updating the vulnerable packages and limiting each secret to its own step would close these risks. Fixing the weaknesses the scanner points to would fix the 18 security weaknesses in the code, and the 16 passwords or keys in the code's history and the six passwords or keys in the code need replacing, with the old ones switched off. The 40 images with no text description need a text description.
The product code is 334,040 lines, about €560,000 to rebuild.
A lens is capped at Adequate while one of its dimensions scores below 4 out of 10, however well the rest of the lens does. That way a serious problem in one place always shows in the lens's rating.
How the score is built: what each lens counts forThe lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.
If Production Readiness rose from 22 to 70, the lowest score rated Strong, the score would rise from 32 to about 40.
Code composition: what the lines of code are
Product code 69%Tests 31%
New since the last survey: 336 findings
These 336 critical or serious findings weren't in the previous survey, on 12 October 2026. The first 100 are listed here, and the findings file in the download package lists them all.
Test Quality · Skipped test: create team event using CreateTeamEventTypeAtom packages/platform/examples/base/tests/create-team-event-type-atom/create-team-event-type.e2e.ts
Test Quality · Skipped test: availability page loads with all components packages/platform/examples/base/tests/availability-settings-atom/availability-settings-atom.e2e.ts
Test Quality · Skipped test: should remove unicode packages/lib/slugify.test.ts
Test Quality · Skipped test: should return the correct working hours given a specific availability, timezone, and date range packages/features/schedules/lib/date-ranges.test.ts
Test Quality · Skipped test: should return the correct working hours in the month were DST ends packages/features/schedules/lib/date-ranges.test.ts
Test Quality · Skipped test: and in loading state, should not prefetch and thus return time range of current month even when column view extra days are present(which keeps the date in the current month) packages/features/schedules/hooks/useTimesForSchedule.timezone.test.ts
Test Quality · Skipped test: and in loading state, should not prefetch and thus return time range of current month even when column view extra days are present(which keeps the date in the current month) packages/features/schedules/hooks/useTimesForSchedule.timezone.test.ts
Test Quality · Skipped test: should return null when user doesn't have access to event type packages/features/eventtypes/lib/getEventTypeById.integration-test.ts
Test Quality · Skipped test: should fail a booking if yearly booking limits are already reached 1. year with limits reached: should fail to book 2. following year without bookings: should create a booking in the database packages/features/bookings/lib/handleNewBooking/test/booking-limits.test.ts
Test Quality · Skipped test: should reuse the same modal packages/embeds/embed-core/src/embed.test.ts
Test Quality · Skipped test: COEP flag if not enabled, embed is blocked packages/embeds/embed-core/playwright/tests/inline.e2e.ts
Test Quality · Skipped test: (unnamed test) packages/app-store/googlecalendar/tests/google-calendar.e2e.ts
Test Quality · Skipped test: (unnamed test) packages/app-store/googlecalendar/tests/google-calendar.e2e.ts
Test Quality · Skipped test: (unnamed test) packages/app-store/googlecalendar/tests/google-calendar.e2e.ts
Test Quality · Skipped test: (unnamed test) packages/app-store/googlecalendar/tests/google-calendar.e2e.ts
Test Quality · Skipped test: (unnamed test) packages/app-store/googlecalendar/tests/google-calendar.e2e.ts
Test Quality · Skipped test: (unnamed test) packages/app-store/googlecalendar/tests/google-calendar.e2e.ts
Test Quality · Skipped test: (unnamed test) packages/app-store/googlecalendar/tests/google-calendar.e2e.ts
Test Quality · Skipped test: (unnamed test) packages/app-store/googlecalendar/tests/google-calendar.e2e.ts
Test Quality · Skipped test: test that PER_WEEK duration limits work correctly apps/web/test/lib/getSchedule.test.ts
Test Quality · Skipped test: global team duration limit blocks slots if one fixed host reached limit apps/web/test/lib/getSchedule.test.ts
Test Quality · Skipped test: test that combined booking and duration limits work correctly apps/web/test/lib/getSchedule.test.ts
Test Quality · Skipped test: should fail recurring booking if second slot is already booked apps/web/pages/api/book/recurring-event.test.ts
Test Quality · Skipped test: should when when a fixed host is not available on the second slot apps/web/pages/api/book/recurring-event.test.ts
Test Quality · Skipped test: /POST/v2/calendars/${OFFICE_365_CALENDAR}/disconnect: it should respond with a 201 returning back the user deleted calendar credentials apps/api/v2/src/platform/calendars/controllers/calendars.controller.e2e-spec.ts
Test Quality · Skipped test: can book with attendeeAddress location apps/api/v2/src/platform/bookings/2024-08-13/controllers/e2e/user-bookings.e2e-spec.ts
Test Quality · Skipped test: POST /v2/destination-calendars: it should respond with a 200 returning back the user updated destination calendar apps/api/v2/src/modules/destination-calendars/controllers/destination-calendars.controller.e2e-spec.ts
Boundary Type-Coupling · Cross-context type SlotFormat (enums → v2) apps/api/v2/src/modules/slots/slots-2024-04-15/services/slots-output.service.ts
Boundary Type-Coupling · Cross-context type GetSlotsInput_2024_09_04 (types → v2) apps/api/v2/src/modules/slots/slots-2024-09-04/controllers/slots.controller.ts
Boundary Type-Coupling · Cross-context type GetSlotsInput_2024_09_04 (types → v2) apps/api/v2/src/modules/slots/slots-2024-09-04/services/slots-input.service.ts
Boundary Type-Coupling · Cross-context type SlotFormat (enums → v2) apps/api/v2/src/modules/slots/slots-2024-09-04/services/slots-output.service.ts
Boundary Type-Coupling · Cross-context type GetSlotsInput_2024_09_04 (types → v2) apps/api/v2/src/modules/slots/slots-2024-09-04/services/slots.service.ts
Boundary Type-Coupling · Cross-context type Status (types → v2) apps/api/v2/src/platform/bookings/2024-04-15/outputs/get-bookings.output.ts
Boundary Type-Coupling · Cross-context type CreateBookingInput (types → v2) apps/api/v2/src/platform/bookings/2024-08-13/controllers/bookings.controller.ts
Boundary Type-Coupling · Cross-context type RescheduleBookingInput (types → v2) apps/api/v2/src/platform/bookings/2024-08-13/controllers/bookings.controller.ts
Boundary Type-Coupling · Cross-context type CancelBookingInput (types → v2) apps/api/v2/src/platform/bookings/2024-08-13/controllers/bookings.controller.ts
Boundary Type-Coupling · Cross-context type CreateBookingInput (types → v2) apps/api/v2/src/platform/bookings/2024-08-13/services/bookings.service.ts
Boundary Type-Coupling · Cross-context type CreateBookingInput (types → v2) apps/api/v2/src/platform/bookings/2024-08-13/services/bookings.service.ts
Boundary Type-Coupling · Cross-context type CreateBookingInput (types → v2) apps/api/v2/src/platform/bookings/2024-08-13/services/bookings.service.ts
Boundary Type-Coupling · Cross-context type RescheduleBookingInput (types → v2) apps/api/v2/src/platform/bookings/2024-08-13/services/bookings.service.ts
Boundary Type-Coupling · Cross-context type RescheduleBookingInput (types → v2) apps/api/v2/src/platform/bookings/2024-08-13/services/bookings.service.ts
Boundary Type-Coupling · Cross-context type CancelBookingInput (types → v2) apps/api/v2/src/platform/bookings/2024-08-13/services/bookings.service.ts
Boundary Type-Coupling · Cross-context type CreateBookingInput (types → v2) apps/api/v2/src/platform/bookings/2024-08-13/services/errors.service.ts
Boundary Type-Coupling · Cross-context type BookingInputLocation_2024_08_13 (types → v2) apps/api/v2/src/platform/bookings/2024-08-13/services/input.service.ts
Boundary Type-Coupling · Cross-context type UpdateBookingInputLocation_2024_08_13 (types → v2) apps/api/v2/src/platform/bookings/2024-08-13/services/input.service.ts
Boundary Type-Coupling · Cross-context type RescheduleBookingInput (types → v2) apps/api/v2/src/platform/bookings/2024-08-13/services/input.service.ts
Boundary Type-Coupling · Cross-context type RescheduleBookingInput (types → v2) apps/api/v2/src/platform/bookings/2024-08-13/services/input.service.ts
Boundary Type-Coupling · Cross-context type CancelBookingInput (types → v2) apps/api/v2/src/platform/bookings/2024-08-13/services/input.service.ts
Boundary Type-Coupling · Cross-context type CancelBookingInput (types → v2) apps/api/v2/src/platform/bookings/2024-08-13/services/input.service.ts
Boundary Type-Coupling · Cross-context type PrivateLinkOutput (types → v2) apps/api/v2/src/platform/event-types-private-links/services/private-links.service.ts
Boundary Type-Coupling · Cross-context type PrivateLinkOutput (types → v2) apps/api/v2/src/platform/event-types-private-links/services/private-links.service.ts
Boundary Type-Coupling · Cross-context type PrivateLinkOutput (types → v2) apps/api/v2/src/platform/event-types-private-links/services/private-links.service.ts
Boundary Type-Coupling · Cross-context type PrivateLinkOutput (types → v2) apps/api/v2/src/platform/event-types-private-links/services/private-links-output.service.ts
Boundary Type-Coupling · Cross-context type PrivateLinkOutput (types → v2) apps/api/v2/src/platform/event-types-private-links/services/private-links-output.service.ts
Boundary Type-Coupling · Cross-context type InputBookingField_2024_06_14 (types → v2) apps/api/v2/src/platform/event-types/event-types_2024_06_14/services/input-event-types.service.ts
Boundary Type-Coupling · Cross-context type OutputBookingField_2024_06_14 (types → v2) apps/api/v2/src/platform/event-types/event-types_2024_06_14/transformers/internal-to-api/booking-fields.ts
Boundary Type-Coupling · Cross-context type BookingWindow_2024_06_14 (types → v2) apps/api/v2/src/platform/event-types/event-types_2024_06_14/transformers/internal-to-api/future-booking-limits.ts
Boundary Type-Coupling · Cross-context type ConfirmationPolicy_2024_06_14 (types → v2) apps/api/v2/src/platform/event-types/event-types_2024_06_14/transformers/internal-to-api/requires-confirmation.ts
Boundary Type-Coupling · Cross-context type InputLocation_2024_06_14 (types → v2) apps/api/v2/src/platform/event-types/event-types_2024_06_14/transformers/api-to-internal/locations.ts
Boundary Type-Coupling · Cross-context type InputTeamLocation_2024_06_14 (types → v2) apps/api/v2/src/platform/event-types/event-types_2024_06_14/transformers/api-to-internal/locations.ts
Boundary Type-Coupling · Cross-context type IconName (ui → web) apps/web/app/icons/IconGrid.tsx
Boundary Type-Coupling · Cross-context type DataTableRow (features → web) apps/web/modules/bookings/types.ts
Boundary Type-Coupling · Cross-context type BlocklistScope (features → web) apps/web/modules/blocklist/components/BlocklistEntryDetailsSheet.tsx
Boundary Type-Coupling · Cross-context type BlocklistScope (features → web) apps/web/modules/blocklist/components/BlockedEntriesTable.tsx
Boundary Type-Coupling · Cross-context type BlocklistScope (features → web) apps/web/modules/blocklist/components/BookingReportDetailsModal.tsx
Boundary Type-Coupling · Cross-context type BlocklistScope (features → web) apps/web/modules/blocklist/components/CreateBlocklistEntryModal.tsx
Boundary Type-Coupling · Cross-context type BlocklistScope (features → web) apps/web/modules/blocklist/components/PendingReportsTable.tsx
Boundary Type-Coupling · Cross-context type CombinedFilterSegment (features → web) apps/web/modules/data-table/components/segment/DuplicateSegmentDialog.tsx
Boundary Type-Coupling · Cross-context type SegmentIdentifier (features → web) apps/web/modules/data-table/hooks/useSegments.ts
Boundary Type-Coupling · Cross-context type EventLocationType (app-store → web) apps/web/modules/event-types/components/locations/LocationInput.tsx
Boundary Type-Coupling · Cross-context type IconName (ui → web) apps/web/modules/onboarding/components/plan-icon.tsx
Boundary Type-Coupling · Cross-context type BookingStatus (trpc → app-store) packages/app-store/locations.ts
Boundary Type-Coupling · Cross-context type UserType (features → stripepayment) packages/app-store/stripepayment/lib/customer.ts
Boundary Type-Coupling · Cross-context type UserType (features → stripepayment) packages/app-store/stripepayment/lib/customer.ts
Boundary Type-Coupling · Cross-context type UserType (features → app-store) packages/app-store/_utils/stripe.ts
Boundary Type-Coupling · Cross-context type JsonValue (atoms → salesforce) packages/app-store/salesforce/lib/eventTypeService.ts
Boundary Type-Coupling · Cross-context type EventLocationType (app-store → features) packages/features/apps/components/AppSetDefaultLinkDialog.tsx
Boundary Type-Coupling · Cross-context type BookingReportStatus (web → features) packages/features/bookingReport/repositories/IBookingReportRepository.ts
Boundary Type-Coupling · Cross-context type BookingReportStatus (web → features) packages/features/bookingReport/repositories/IBookingReportRepository.ts
Boundary Type-Coupling · Cross-context type BookingReportStatus (web → features) packages/features/bookingReport/repositories/IBookingReportRepository.ts
Boundary Type-Coupling · Cross-context type BookingReportStatus (web → features) packages/features/bookingReport/repositories/IBookingReportRepository.ts
Boundary Type-Coupling · Cross-context type BookingReportStatus (web → features) packages/features/bookingReport/repositories/IBookingReportRepository.ts
Boundary Type-Coupling · Cross-context type BookingReportStatus (web → features) packages/features/bookingReport/repositories/PrismaBookingReportRepository.ts
Watchdog compares every finding with the previous survey's. A finding that has only moved to another line in the same file counts as the same finding, so only new findings appear here. Advisory notes from the AI model are left out, because the model words them afresh in every survey.
Fixed since the last survey: 5431 findings
These 5431 critical or serious findings were in the previous survey, on 12 October 2026, and are gone from this one. The first 100 are listed here.
€190,000 to €930,000, for 3,100 to 9,834 hours of work, about 3.8 person-years for 2 to 8 engineers
Difficulty of the problem
High, 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 32. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
Size
Large: 334,040 lines of product code
What it is not
Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one.
How the estimate is made: Watchdog prices the hours a team would need to write this code again, at €60 to €95 an hour. Declarations and boilerplate are priced at a fast rate and logic at a slower one, and the logic is then multiplied by the difficulty of the problem and by the quality factor. The estimate can be about 30% off either way, and it moves most with the hourly rate and the difficulty. For this code, every line is priced as straight logic, which keeps the estimate on the low side.
Top priorities
The three actions that raise the score most for the work they take. The full ranked list is in the Roadmap.
1
Resolve the 6 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (4), REDACTED (2).
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 €560,000 to build again, about 3.8 person-years of work. Its weakest lens is Production Readiness, at 22 (Critical). 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 6 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 8 points for low effort, because it clears the 6 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.3 out of 10. Code at that level is slower to change than clean code, and Watchdog estimates the extra work at 7% to 15% on every change. The history of the code shows how much it changes: about 1,724 lines over the last 90 days, which is about 6,992 lines a year. At that pace, the extra work comes to an estimated 1.2 to 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 Watchdog's own: code scoring 8 out of 10 or more adds no extra work, and each point below 8 adds 2.5% to 5.6% to every change, 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 · Cohesion (LCOM4) · the code's change history
What to do: Start with the files listed under Churn × Complexity Hotspots, which change often and are hard to read, because that is where the extra work is paid most often.
Architecture — module dependency graph
Project dependencies, layered top-to-bottom; arrows show direction. Any dashed red edge points upward or sideways, which only happens where the projects form a dependency cycle. A graph without cycles has none.
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.
2240 modules, with 1882 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; 2200 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.
1 pair of types, where a type in apps.api.v2.src.lib.services.regular-booking_service uses a type in apps.api.v2.src.modules.prisma.prisma-write_service.
apps.api.v2.src.lib.services.regular-booking_service uses apps.api.v2.src.modules.prisma.prisma-write_service, so a change to apps.api.v2.src.modules.prisma.prisma-write_service can break apps.api.v2.src.lib.services.regular-booking_service, while a change to apps.api.v2.src.lib.services.regular-booking_service can't break apps.api.v2.src.modules.prisma.prisma-write_service.
Position
Below the diagonal: apps.api.v2.src.lib.services.regular-booking_service uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in apps.api.v2.src.modules.prisma.prisma-read_service uses a type in apps.api.v2.src.modules.prisma.prisma-write_service.
apps.api.v2.src.modules.prisma.prisma-read_service uses apps.api.v2.src.modules.prisma.prisma-write_service, so a change to apps.api.v2.src.modules.prisma.prisma-write_service can break apps.api.v2.src.modules.prisma.prisma-read_service, while a change to apps.api.v2.src.modules.prisma.prisma-read_service can't break apps.api.v2.src.modules.prisma.prisma-write_service.
Position
Below the diagonal: apps.api.v2.src.modules.prisma.prisma-read_service uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in apps.api.v2.src.platform.bookings.2024-04-15.outputs.get-booking_output uses a type in apps.api.v2.src.platform.bookings.2024-04-15.inputs.create-booking_input.
apps.api.v2.src.platform.bookings.2024-04-15.outputs.get-booking_output uses apps.api.v2.src.platform.bookings.2024-04-15.inputs.create-booking_input, so a change to apps.api.v2.src.platform.bookings.2024-04-15.inputs.create-booking_input can break apps.api.v2.src.platform.bookings.2024-04-15.outputs.get-booking_output, while a change to apps.api.v2.src.platform.bookings.2024-04-15.outputs.get-booking_output can't break apps.api.v2.src.platform.bookings.2024-04-15.inputs.create-booking_input.
Position
Below the diagonal: apps.api.v2.src.platform.bookings.2024-04-15.outputs.get-booking_output uses a module listed above it, which is the healthy direction.
packages.emails.templates.organizer-scheduled-email uses packages.emails.templates._base-email, so a change to packages.emails.templates._base-email can break packages.emails.templates.organizer-scheduled-email, while a change to packages.emails.templates.organizer-scheduled-email can't break packages.emails.templates._base-email.
Position
Below the diagonal: packages.emails.templates.organizer-scheduled-email uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in packages.emails.templates.organizer-scheduled-email uses a type in packages.features.calendars.weeklyview.types.events.
packages.emails.templates.organizer-scheduled-email uses packages.features.calendars.weeklyview.types.events, so a change to packages.features.calendars.weeklyview.types.events can break packages.emails.templates.organizer-scheduled-email, while a change to packages.emails.templates.organizer-scheduled-email can't break packages.features.calendars.weeklyview.types.events.
Position
Below the diagonal: packages.emails.templates.organizer-scheduled-email uses a module listed above it, which is the healthy direction.
packages.features.webhooks.lib.dto.types uses packages.features.calendars.weeklyview.types.events, so a change to packages.features.calendars.weeklyview.types.events can break packages.features.webhooks.lib.dto.types, while a change to packages.features.webhooks.lib.dto.types can't break packages.features.calendars.weeklyview.types.events.
Position
Below the diagonal: packages.features.webhooks.lib.dto.types uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in apps.api.v2.src.modules.credentials.credentials_repository uses a type in apps.api.v2.src.modules.prisma.prisma-write_service.
apps.api.v2.src.modules.credentials.credentials_repository uses apps.api.v2.src.modules.prisma.prisma-write_service, so a change to apps.api.v2.src.modules.prisma.prisma-write_service can break apps.api.v2.src.modules.credentials.credentials_repository, while a change to apps.api.v2.src.modules.credentials.credentials_repository can't break apps.api.v2.src.modules.prisma.prisma-write_service.
Position
Below the diagonal: apps.api.v2.src.modules.credentials.credentials_repository uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in apps.api.v2.src.modules.credentials.credentials_repository uses a type in apps.api.v2.src.modules.prisma.prisma-read_service.
apps.api.v2.src.modules.credentials.credentials_repository uses apps.api.v2.src.modules.prisma.prisma-read_service, so a change to apps.api.v2.src.modules.prisma.prisma-read_service can break apps.api.v2.src.modules.credentials.credentials_repository, while a change to apps.api.v2.src.modules.credentials.credentials_repository can't break apps.api.v2.src.modules.prisma.prisma-read_service.
Position
Below the diagonal: apps.api.v2.src.modules.credentials.credentials_repository uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in apps.api.v2.src.modules.oauth-clients.oauth-client_repository uses a type in apps.api.v2.src.modules.prisma.prisma-write_service.
apps.api.v2.src.modules.oauth-clients.oauth-client_repository uses apps.api.v2.src.modules.prisma.prisma-write_service, so a change to apps.api.v2.src.modules.prisma.prisma-write_service can break apps.api.v2.src.modules.oauth-clients.oauth-client_repository, while a change to apps.api.v2.src.modules.oauth-clients.oauth-client_repository can't break apps.api.v2.src.modules.prisma.prisma-write_service.
Position
Below the diagonal: apps.api.v2.src.modules.oauth-clients.oauth-client_repository uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in apps.api.v2.src.modules.oauth-clients.oauth-client_repository uses a type in apps.api.v2.src.modules.prisma.prisma-read_service.
apps.api.v2.src.modules.oauth-clients.oauth-client_repository uses apps.api.v2.src.modules.prisma.prisma-read_service, so a change to apps.api.v2.src.modules.prisma.prisma-read_service can break apps.api.v2.src.modules.oauth-clients.oauth-client_repository, while a change to apps.api.v2.src.modules.oauth-clients.oauth-client_repository can't break apps.api.v2.src.modules.prisma.prisma-read_service.
Position
Below the diagonal: apps.api.v2.src.modules.oauth-clients.oauth-client_repository uses a module listed above it, which is the healthy direction.
apps.api.v2.src.modules.users.users_repository uses apps.api.v2.src.modules.prisma.prisma-write_service, so a change to apps.api.v2.src.modules.prisma.prisma-write_service can break apps.api.v2.src.modules.users.users_repository, while a change to apps.api.v2.src.modules.users.users_repository can't break apps.api.v2.src.modules.prisma.prisma-write_service.
Position
Below the diagonal: apps.api.v2.src.modules.users.users_repository uses a module listed above it, which is the healthy direction.
apps.api.v2.src.modules.users.users_repository uses apps.api.v2.src.modules.prisma.prisma-read_service, so a change to apps.api.v2.src.modules.prisma.prisma-read_service can break apps.api.v2.src.modules.users.users_repository, while a change to apps.api.v2.src.modules.users.users_repository can't break apps.api.v2.src.modules.prisma.prisma-read_service.
Position
Below the diagonal: apps.api.v2.src.modules.users.users_repository uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in apps.api.v2.src.modules.users.users_repository uses a type in apps.api.v2.src.platform.bookings.2024-04-15.outputs.get-booking_output.
apps.api.v2.src.modules.users.users_repository uses apps.api.v2.src.platform.bookings.2024-04-15.outputs.get-booking_output, so a change to apps.api.v2.src.platform.bookings.2024-04-15.outputs.get-booking_output can break apps.api.v2.src.modules.users.users_repository, while a change to apps.api.v2.src.modules.users.users_repository can't break apps.api.v2.src.platform.bookings.2024-04-15.outputs.get-booking_output.
Position
Below the diagonal: apps.api.v2.src.modules.users.users_repository uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in apps.api.v2.src.platform.bookings.2024-08-13.repositories.bookings_repository uses a type in apps.api.v2.src.modules.prisma.prisma-write_service.
apps.api.v2.src.platform.bookings.2024-08-13.repositories.bookings_repository uses apps.api.v2.src.modules.prisma.prisma-write_service, so a change to apps.api.v2.src.modules.prisma.prisma-write_service can break apps.api.v2.src.platform.bookings.2024-08-13.repositories.bookings_repository, while a change to apps.api.v2.src.platform.bookings.2024-08-13.repositories.bookings_repository can't break apps.api.v2.src.modules.prisma.prisma-write_service.
Position
Below the diagonal: apps.api.v2.src.platform.bookings.2024-08-13.repositories.bookings_repository uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in apps.api.v2.src.platform.bookings.2024-08-13.repositories.bookings_repository uses a type in apps.api.v2.src.modules.prisma.prisma-read_service.
apps.api.v2.src.platform.bookings.2024-08-13.repositories.bookings_repository uses apps.api.v2.src.modules.prisma.prisma-read_service, so a change to apps.api.v2.src.modules.prisma.prisma-read_service can break apps.api.v2.src.platform.bookings.2024-08-13.repositories.bookings_repository, while a change to apps.api.v2.src.platform.bookings.2024-08-13.repositories.bookings_repository can't break apps.api.v2.src.modules.prisma.prisma-read_service.
Position
Below the diagonal: apps.api.v2.src.platform.bookings.2024-08-13.repositories.bookings_repository uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in apps.api.v2.src.platform.event-types.event-types_2024_04_15.controllers.event-types_controller uses a type in apps.api.v2.src.modules.prisma.prisma-read_service.
apps.api.v2.src.platform.event-types.event-types_2024_04_15.controllers.event-types_controller uses apps.api.v2.src.modules.prisma.prisma-read_service, so a change to apps.api.v2.src.modules.prisma.prisma-read_service can break apps.api.v2.src.platform.event-types.event-types_2024_04_15.controllers.event-types_controller, while a change to apps.api.v2.src.platform.event-types.event-types_2024_04_15.controllers.event-types_controller can't break apps.api.v2.src.modules.prisma.prisma-read_service.
Position
Below the diagonal: apps.api.v2.src.platform.event-types.event-types_2024_04_15.controllers.event-types_controller uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in apps.api.v2.src.platform.event-types.event-types_2024_06_14.event-types_repository uses a type in apps.api.v2.src.modules.prisma.prisma-write_service.
apps.api.v2.src.platform.event-types.event-types_2024_06_14.event-types_repository uses apps.api.v2.src.modules.prisma.prisma-write_service, so a change to apps.api.v2.src.modules.prisma.prisma-write_service can break apps.api.v2.src.platform.event-types.event-types_2024_06_14.event-types_repository, while a change to apps.api.v2.src.platform.event-types.event-types_2024_06_14.event-types_repository can't break apps.api.v2.src.modules.prisma.prisma-write_service.
Position
Below the diagonal: apps.api.v2.src.platform.event-types.event-types_2024_06_14.event-types_repository uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in apps.api.v2.src.platform.event-types.event-types_2024_06_14.event-types_repository uses a type in apps.api.v2.src.modules.prisma.prisma-read_service.
apps.api.v2.src.platform.event-types.event-types_2024_06_14.event-types_repository uses apps.api.v2.src.modules.prisma.prisma-read_service, so a change to apps.api.v2.src.modules.prisma.prisma-read_service can break apps.api.v2.src.platform.event-types.event-types_2024_06_14.event-types_repository, while a change to apps.api.v2.src.platform.event-types.event-types_2024_06_14.event-types_repository can't break apps.api.v2.src.modules.prisma.prisma-read_service.
Position
Below the diagonal: apps.api.v2.src.platform.event-types.event-types_2024_06_14.event-types_repository uses a module listed above it, which is the healthy direction.
packages.lib uses apps.api.v2.src.platform.bookings.2024-04-15.inputs.create-booking_input, so a change to apps.api.v2.src.platform.bookings.2024-04-15.inputs.create-booking_input can break packages.lib, while a change to packages.lib can't break apps.api.v2.src.platform.bookings.2024-04-15.inputs.create-booking_input.
Position
Below the diagonal: packages.lib uses a module listed above it, which is the healthy direction.
packages.lib uses apps.api.v2.src.platform.calendars.outputs.connected-calendars_output, so a change to apps.api.v2.src.platform.calendars.outputs.connected-calendars_output can break packages.lib, while a change to packages.lib can't break apps.api.v2.src.platform.calendars.outputs.connected-calendars_output.
Position
Below the diagonal: packages.lib uses a module listed above it, which is the healthy direction.
packages.lib uses packages.features.calendars.weeklyview.types.events, so a change to packages.features.calendars.weeklyview.types.events can break packages.lib, while a change to packages.lib can't break packages.features.calendars.weeklyview.types.events.
Position
Below the diagonal: packages.lib uses a module listed above it, which is the healthy direction.
packages.lib uses apps.api.v2.src.platform.bookings.2024-04-15.outputs.get-booking_output, so a change to apps.api.v2.src.platform.bookings.2024-04-15.outputs.get-booking_output can break packages.lib, while a change to packages.lib can't break apps.api.v2.src.platform.bookings.2024-04-15.outputs.get-booking_output.
Position
Below the diagonal: packages.lib uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in packages.trpc.server.routers.viewer.slots.util uses a type in packages.features.bookings.repositories.BookingRepository.
packages.trpc.server.routers.viewer.slots.util uses packages.features.bookings.repositories.BookingRepository, so a change to packages.features.bookings.repositories.BookingRepository can break packages.trpc.server.routers.viewer.slots.util, while a change to packages.trpc.server.routers.viewer.slots.util can't break packages.features.bookings.repositories.BookingRepository.
Position
Below the diagonal: packages.trpc.server.routers.viewer.slots.util uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in packages.trpc.server.routers.viewer.slots.util uses a type in apps.api.v2.src.platform.bookings.2024-04-15.outputs.get-booking_output.
packages.trpc.server.routers.viewer.slots.util uses apps.api.v2.src.platform.bookings.2024-04-15.outputs.get-booking_output, so a change to apps.api.v2.src.platform.bookings.2024-04-15.outputs.get-booking_output can break packages.trpc.server.routers.viewer.slots.util, while a change to packages.trpc.server.routers.viewer.slots.util can't break apps.api.v2.src.platform.bookings.2024-04-15.outputs.get-booking_output.
Position
Below the diagonal: packages.trpc.server.routers.viewer.slots.util uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in apps.api.v2.src.modules.oauth-clients.controllers.oauth-client-users.oauth-client-users_controller uses a type in apps.api.v2.src.platform.bookings.2024-04-15.outputs.get-booking_output.
apps.api.v2.src.modules.oauth-clients.controllers.oauth-client-users.oauth-client-users_controller uses apps.api.v2.src.platform.bookings.2024-04-15.outputs.get-booking_output, so a change to apps.api.v2.src.platform.bookings.2024-04-15.outputs.get-booking_output can break apps.api.v2.src.modules.oauth-clients.controllers.oauth-client-users.oauth-client-users_controller, while a change to apps.api.v2.src.modules.oauth-clients.controllers.oauth-client-users.oauth-client-users_controller can't break apps.api.v2.src.platform.bookings.2024-04-15.outputs.get-booking_output.
Position
Below the diagonal: apps.api.v2.src.modules.oauth-clients.controllers.oauth-client-users.oauth-client-users_controller uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in apps.api.v2.src.modules.oauth-clients.controllers.oauth-client-users.oauth-client-users_controller uses a type in apps.api.v2.src.modules.oauth-clients.oauth-client_repository.
apps.api.v2.src.modules.oauth-clients.controllers.oauth-client-users.oauth-client-users_controller uses apps.api.v2.src.modules.oauth-clients.oauth-client_repository, so a change to apps.api.v2.src.modules.oauth-clients.oauth-client_repository can break apps.api.v2.src.modules.oauth-clients.controllers.oauth-client-users.oauth-client-users_controller, while a change to apps.api.v2.src.modules.oauth-clients.controllers.oauth-client-users.oauth-client-users_controller can't break apps.api.v2.src.modules.oauth-clients.oauth-client_repository.
Position
Below the diagonal: apps.api.v2.src.modules.oauth-clients.controllers.oauth-client-users.oauth-client-users_controller uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in apps.api.v2.src.modules.oauth-clients.controllers.oauth-client-users.oauth-client-users_controller uses a type in apps.api.v2.src.modules.users.users_repository.
apps.api.v2.src.modules.oauth-clients.controllers.oauth-client-users.oauth-client-users_controller uses apps.api.v2.src.modules.users.users_repository, so a change to apps.api.v2.src.modules.users.users_repository can break apps.api.v2.src.modules.oauth-clients.controllers.oauth-client-users.oauth-client-users_controller, while a change to apps.api.v2.src.modules.oauth-clients.controllers.oauth-client-users.oauth-client-users_controller can't break apps.api.v2.src.modules.users.users_repository.
Position
Below the diagonal: apps.api.v2.src.modules.oauth-clients.controllers.oauth-client-users.oauth-client-users_controller uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in apps.api.v2.src.modules.slots.slots-2024-09-04.services.slots_service uses a type in apps.api.v2.src.lib.services.available-slots_service.
apps.api.v2.src.modules.slots.slots-2024-09-04.services.slots_service uses apps.api.v2.src.lib.services.available-slots_service, so a change to apps.api.v2.src.lib.services.available-slots_service can break apps.api.v2.src.modules.slots.slots-2024-09-04.services.slots_service, while a change to apps.api.v2.src.modules.slots.slots-2024-09-04.services.slots_service can't break apps.api.v2.src.lib.services.available-slots_service.
Position
Below the diagonal: apps.api.v2.src.modules.slots.slots-2024-09-04.services.slots_service uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in apps.api.v2.src.modules.slots.slots-2024-09-04.services.slots_service uses a type in apps.api.v2.src.platform.bookings.2024-04-15.outputs.get-booking_output.
apps.api.v2.src.modules.slots.slots-2024-09-04.services.slots_service uses apps.api.v2.src.platform.bookings.2024-04-15.outputs.get-booking_output, so a change to apps.api.v2.src.platform.bookings.2024-04-15.outputs.get-booking_output can break apps.api.v2.src.modules.slots.slots-2024-09-04.services.slots_service, while a change to apps.api.v2.src.modules.slots.slots-2024-09-04.services.slots_service can't break apps.api.v2.src.platform.bookings.2024-04-15.outputs.get-booking_output.
Position
Below the diagonal: apps.api.v2.src.modules.slots.slots-2024-09-04.services.slots_service uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in apps.api.v2.src.modules.slots.slots-2024-09-04.services.slots_service uses a type in apps.api.v2.src.platform.event-types.event-types_2024_06_14.event-types_repository.
apps.api.v2.src.modules.slots.slots-2024-09-04.services.slots_service uses apps.api.v2.src.platform.event-types.event-types_2024_06_14.event-types_repository, so a change to apps.api.v2.src.platform.event-types.event-types_2024_06_14.event-types_repository can break apps.api.v2.src.modules.slots.slots-2024-09-04.services.slots_service, while a change to apps.api.v2.src.modules.slots.slots-2024-09-04.services.slots_service can't break apps.api.v2.src.platform.event-types.event-types_2024_06_14.event-types_repository.
Position
Below the diagonal: apps.api.v2.src.modules.slots.slots-2024-09-04.services.slots_service uses a module listed above it, which is the healthy direction.
apps.api.v2.src.modules.users.services.users_service uses apps.api.v2.src.modules.users.users_repository, so a change to apps.api.v2.src.modules.users.users_repository can break apps.api.v2.src.modules.users.services.users_service, while a change to apps.api.v2.src.modules.users.services.users_service can't break apps.api.v2.src.modules.users.users_repository.
Position
Below the diagonal: apps.api.v2.src.modules.users.services.users_service uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in apps.api.v2.src.platform.bookings.2024-08-13.services.input_service uses a type in apps.api.v2.src.platform.bookings.2024-04-15.outputs.get-booking_output.
apps.api.v2.src.platform.bookings.2024-08-13.services.input_service uses apps.api.v2.src.platform.bookings.2024-04-15.outputs.get-booking_output, so a change to apps.api.v2.src.platform.bookings.2024-04-15.outputs.get-booking_output can break apps.api.v2.src.platform.bookings.2024-08-13.services.input_service, while a change to apps.api.v2.src.platform.bookings.2024-08-13.services.input_service can't break apps.api.v2.src.platform.bookings.2024-04-15.outputs.get-booking_output.
Position
Below the diagonal: apps.api.v2.src.platform.bookings.2024-08-13.services.input_service uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in apps.api.v2.src.platform.bookings.2024-08-13.services.input_service uses a type in apps.api.v2.src.modules.users.users_repository.
apps.api.v2.src.platform.bookings.2024-08-13.services.input_service uses apps.api.v2.src.modules.users.users_repository, so a change to apps.api.v2.src.modules.users.users_repository can break apps.api.v2.src.platform.bookings.2024-08-13.services.input_service, while a change to apps.api.v2.src.platform.bookings.2024-08-13.services.input_service can't break apps.api.v2.src.modules.users.users_repository.
Position
Below the diagonal: apps.api.v2.src.platform.bookings.2024-08-13.services.input_service uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in apps.api.v2.src.platform.bookings.2024-08-13.services.input_service uses a type in apps.api.v2.src.platform.bookings.2024-08-13.repositories.bookings_repository.
apps.api.v2.src.platform.bookings.2024-08-13.services.input_service uses apps.api.v2.src.platform.bookings.2024-08-13.repositories.bookings_repository, so a change to apps.api.v2.src.platform.bookings.2024-08-13.repositories.bookings_repository can break apps.api.v2.src.platform.bookings.2024-08-13.services.input_service, while a change to apps.api.v2.src.platform.bookings.2024-08-13.services.input_service can't break apps.api.v2.src.platform.bookings.2024-08-13.repositories.bookings_repository.
Position
Below the diagonal: apps.api.v2.src.platform.bookings.2024-08-13.services.input_service uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in apps.api.v2.src.platform.bookings.2024-08-13.services.input_service uses a type in apps.api.v2.src.platform.event-types.event-types_2024_06_14.event-types_repository.
apps.api.v2.src.platform.bookings.2024-08-13.services.input_service uses apps.api.v2.src.platform.event-types.event-types_2024_06_14.event-types_repository, so a change to apps.api.v2.src.platform.event-types.event-types_2024_06_14.event-types_repository can break apps.api.v2.src.platform.bookings.2024-08-13.services.input_service, while a change to apps.api.v2.src.platform.bookings.2024-08-13.services.input_service can't break apps.api.v2.src.platform.event-types.event-types_2024_06_14.event-types_repository.
Position
Below the diagonal: apps.api.v2.src.platform.bookings.2024-08-13.services.input_service uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in apps.api.v2.src.platform.calendars.services.calendars_service uses a type in apps.api.v2.src.modules.prisma.prisma-write_service.
apps.api.v2.src.platform.calendars.services.calendars_service uses apps.api.v2.src.modules.prisma.prisma-write_service, so a change to apps.api.v2.src.modules.prisma.prisma-write_service can break apps.api.v2.src.platform.calendars.services.calendars_service, while a change to apps.api.v2.src.platform.calendars.services.calendars_service can't break apps.api.v2.src.modules.prisma.prisma-write_service.
Position
Below the diagonal: apps.api.v2.src.platform.calendars.services.calendars_service uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in apps.api.v2.src.platform.calendars.services.calendars_service uses a type in apps.api.v2.src.modules.credentials.credentials_repository.
apps.api.v2.src.platform.calendars.services.calendars_service uses apps.api.v2.src.modules.credentials.credentials_repository, so a change to apps.api.v2.src.modules.credentials.credentials_repository can break apps.api.v2.src.platform.calendars.services.calendars_service, while a change to apps.api.v2.src.platform.calendars.services.calendars_service can't break apps.api.v2.src.modules.credentials.credentials_repository.
Position
Below the diagonal: apps.api.v2.src.platform.calendars.services.calendars_service uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in apps.api.v2.src.platform.calendars.services.calendars_service uses a type in apps.api.v2.src.modules.users.users_repository.
apps.api.v2.src.platform.calendars.services.calendars_service uses apps.api.v2.src.modules.users.users_repository, so a change to apps.api.v2.src.modules.users.users_repository can break apps.api.v2.src.platform.calendars.services.calendars_service, while a change to apps.api.v2.src.platform.calendars.services.calendars_service can't break apps.api.v2.src.modules.users.users_repository.
Position
Below the diagonal: apps.api.v2.src.platform.calendars.services.calendars_service uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in apps.api.v2.src.platform.bookings.2024-04-15.controllers.bookings_controller uses a type in apps.api.v2.src.platform.bookings.2024-04-15.inputs.create-booking_input.
apps.api.v2.src.platform.bookings.2024-04-15.controllers.bookings_controller uses apps.api.v2.src.platform.bookings.2024-04-15.inputs.create-booking_input, so a change to apps.api.v2.src.platform.bookings.2024-04-15.inputs.create-booking_input can break apps.api.v2.src.platform.bookings.2024-04-15.controllers.bookings_controller, while a change to apps.api.v2.src.platform.bookings.2024-04-15.controllers.bookings_controller can't break apps.api.v2.src.platform.bookings.2024-04-15.inputs.create-booking_input.
Position
Below the diagonal: apps.api.v2.src.platform.bookings.2024-04-15.controllers.bookings_controller uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in apps.api.v2.src.platform.bookings.2024-04-15.controllers.bookings_controller uses a type in apps.api.v2.src.lib.services.regular-booking_service.
apps.api.v2.src.platform.bookings.2024-04-15.controllers.bookings_controller uses apps.api.v2.src.lib.services.regular-booking_service, so a change to apps.api.v2.src.lib.services.regular-booking_service can break apps.api.v2.src.platform.bookings.2024-04-15.controllers.bookings_controller, while a change to apps.api.v2.src.platform.bookings.2024-04-15.controllers.bookings_controller can't break apps.api.v2.src.lib.services.regular-booking_service.
Position
Below the diagonal: apps.api.v2.src.platform.bookings.2024-04-15.controllers.bookings_controller uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in apps.api.v2.src.platform.bookings.2024-04-15.controllers.bookings_controller uses a type in apps.api.v2.src.modules.prisma.prisma-read_service.
apps.api.v2.src.platform.bookings.2024-04-15.controllers.bookings_controller uses apps.api.v2.src.modules.prisma.prisma-read_service, so a change to apps.api.v2.src.modules.prisma.prisma-read_service can break apps.api.v2.src.platform.bookings.2024-04-15.controllers.bookings_controller, while a change to apps.api.v2.src.platform.bookings.2024-04-15.controllers.bookings_controller can't break apps.api.v2.src.modules.prisma.prisma-read_service.
Position
Below the diagonal: apps.api.v2.src.platform.bookings.2024-04-15.controllers.bookings_controller uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in apps.api.v2.src.platform.bookings.2024-04-15.controllers.bookings_controller uses a type in apps.api.v2.src.platform.bookings.2024-04-15.outputs.get-booking_output.
apps.api.v2.src.platform.bookings.2024-04-15.controllers.bookings_controller uses apps.api.v2.src.platform.bookings.2024-04-15.outputs.get-booking_output, so a change to apps.api.v2.src.platform.bookings.2024-04-15.outputs.get-booking_output can break apps.api.v2.src.platform.bookings.2024-04-15.controllers.bookings_controller, while a change to apps.api.v2.src.platform.bookings.2024-04-15.controllers.bookings_controller can't break apps.api.v2.src.platform.bookings.2024-04-15.outputs.get-booking_output.
Position
Below the diagonal: apps.api.v2.src.platform.bookings.2024-04-15.controllers.bookings_controller uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in apps.api.v2.src.platform.bookings.2024-04-15.controllers.bookings_controller uses a type in apps.api.v2.src.modules.oauth-clients.oauth-client_repository.
apps.api.v2.src.platform.bookings.2024-04-15.controllers.bookings_controller uses apps.api.v2.src.modules.oauth-clients.oauth-client_repository, so a change to apps.api.v2.src.modules.oauth-clients.oauth-client_repository can break apps.api.v2.src.platform.bookings.2024-04-15.controllers.bookings_controller, while a change to apps.api.v2.src.platform.bookings.2024-04-15.controllers.bookings_controller can't break apps.api.v2.src.modules.oauth-clients.oauth-client_repository.
Position
Below the diagonal: apps.api.v2.src.platform.bookings.2024-04-15.controllers.bookings_controller uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in apps.api.v2.src.platform.bookings.2024-04-15.controllers.bookings_controller uses a type in apps.api.v2.src.modules.users.users_repository.
apps.api.v2.src.platform.bookings.2024-04-15.controllers.bookings_controller uses apps.api.v2.src.modules.users.users_repository, so a change to apps.api.v2.src.modules.users.users_repository can break apps.api.v2.src.platform.bookings.2024-04-15.controllers.bookings_controller, while a change to apps.api.v2.src.platform.bookings.2024-04-15.controllers.bookings_controller can't break apps.api.v2.src.modules.users.users_repository.
Position
Below the diagonal: apps.api.v2.src.platform.bookings.2024-04-15.controllers.bookings_controller uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in apps.api.v2.src.platform.bookings.2024-04-15.controllers.bookings_controller uses a type in apps.api.v2.src.modules.users.services.users_service.
apps.api.v2.src.platform.bookings.2024-04-15.controllers.bookings_controller uses apps.api.v2.src.modules.users.services.users_service, so a change to apps.api.v2.src.modules.users.services.users_service can break apps.api.v2.src.platform.bookings.2024-04-15.controllers.bookings_controller, while a change to apps.api.v2.src.platform.bookings.2024-04-15.controllers.bookings_controller can't break apps.api.v2.src.modules.users.services.users_service.
Position
Below the diagonal: apps.api.v2.src.platform.bookings.2024-04-15.controllers.bookings_controller uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in apps.api.v2.src.platform.bookings.2024-08-13.services.bookings_service uses a type in apps.api.v2.src.lib.services.regular-booking_service.
apps.api.v2.src.platform.bookings.2024-08-13.services.bookings_service uses apps.api.v2.src.lib.services.regular-booking_service, so a change to apps.api.v2.src.lib.services.regular-booking_service can break apps.api.v2.src.platform.bookings.2024-08-13.services.bookings_service, while a change to apps.api.v2.src.platform.bookings.2024-08-13.services.bookings_service can't break apps.api.v2.src.lib.services.regular-booking_service.
Position
Below the diagonal: apps.api.v2.src.platform.bookings.2024-08-13.services.bookings_service uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in apps.api.v2.src.platform.bookings.2024-08-13.services.bookings_service uses a type in apps.api.v2.src.modules.prisma.prisma-read_service.
apps.api.v2.src.platform.bookings.2024-08-13.services.bookings_service uses apps.api.v2.src.modules.prisma.prisma-read_service, so a change to apps.api.v2.src.modules.prisma.prisma-read_service can break apps.api.v2.src.platform.bookings.2024-08-13.services.bookings_service, while a change to apps.api.v2.src.platform.bookings.2024-08-13.services.bookings_service can't break apps.api.v2.src.modules.prisma.prisma-read_service.
Position
Below the diagonal: apps.api.v2.src.platform.bookings.2024-08-13.services.bookings_service uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in apps.api.v2.src.platform.bookings.2024-08-13.services.bookings_service uses a type in apps.api.v2.src.modules.oauth-clients.oauth-client_repository.
apps.api.v2.src.platform.bookings.2024-08-13.services.bookings_service uses apps.api.v2.src.modules.oauth-clients.oauth-client_repository, so a change to apps.api.v2.src.modules.oauth-clients.oauth-client_repository can break apps.api.v2.src.platform.bookings.2024-08-13.services.bookings_service, while a change to apps.api.v2.src.platform.bookings.2024-08-13.services.bookings_service can't break apps.api.v2.src.modules.oauth-clients.oauth-client_repository.
Position
Below the diagonal: apps.api.v2.src.platform.bookings.2024-08-13.services.bookings_service uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in apps.api.v2.src.platform.bookings.2024-08-13.services.bookings_service uses a type in apps.api.v2.src.modules.users.users_repository.
apps.api.v2.src.platform.bookings.2024-08-13.services.bookings_service uses apps.api.v2.src.modules.users.users_repository, so a change to apps.api.v2.src.modules.users.users_repository can break apps.api.v2.src.platform.bookings.2024-08-13.services.bookings_service, while a change to apps.api.v2.src.platform.bookings.2024-08-13.services.bookings_service can't break apps.api.v2.src.modules.users.users_repository.
Position
Below the diagonal: apps.api.v2.src.platform.bookings.2024-08-13.services.bookings_service uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in apps.api.v2.src.platform.bookings.2024-08-13.services.bookings_service uses a type in apps.api.v2.src.platform.bookings.2024-08-13.repositories.bookings_repository.
apps.api.v2.src.platform.bookings.2024-08-13.services.bookings_service uses apps.api.v2.src.platform.bookings.2024-08-13.repositories.bookings_repository, so a change to apps.api.v2.src.platform.bookings.2024-08-13.repositories.bookings_repository can break apps.api.v2.src.platform.bookings.2024-08-13.services.bookings_service, while a change to apps.api.v2.src.platform.bookings.2024-08-13.services.bookings_service can't break apps.api.v2.src.platform.bookings.2024-08-13.repositories.bookings_repository.
Position
Below the diagonal: apps.api.v2.src.platform.bookings.2024-08-13.services.bookings_service uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in apps.api.v2.src.platform.bookings.2024-08-13.services.bookings_service uses a type in apps.api.v2.src.platform.event-types.event-types_2024_06_14.event-types_repository.
apps.api.v2.src.platform.bookings.2024-08-13.services.bookings_service uses apps.api.v2.src.platform.event-types.event-types_2024_06_14.event-types_repository, so a change to apps.api.v2.src.platform.event-types.event-types_2024_06_14.event-types_repository can break apps.api.v2.src.platform.bookings.2024-08-13.services.bookings_service, while a change to apps.api.v2.src.platform.bookings.2024-08-13.services.bookings_service can't break apps.api.v2.src.platform.event-types.event-types_2024_06_14.event-types_repository.
Position
Below the diagonal: apps.api.v2.src.platform.bookings.2024-08-13.services.bookings_service uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in apps.api.v2.src.platform.bookings.2024-08-13.services.bookings_service uses a type in apps.api.v2.src.modules.users.services.users_service.
apps.api.v2.src.platform.bookings.2024-08-13.services.bookings_service uses apps.api.v2.src.modules.users.services.users_service, so a change to apps.api.v2.src.modules.users.services.users_service can break apps.api.v2.src.platform.bookings.2024-08-13.services.bookings_service, while a change to apps.api.v2.src.platform.bookings.2024-08-13.services.bookings_service can't break apps.api.v2.src.modules.users.services.users_service.
Position
Below the diagonal: apps.api.v2.src.platform.bookings.2024-08-13.services.bookings_service uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in apps.api.v2.src.platform.bookings.2024-08-13.services.bookings_service uses a type in apps.api.v2.src.platform.bookings.2024-08-13.services.input_service.
apps.api.v2.src.platform.bookings.2024-08-13.services.bookings_service uses apps.api.v2.src.platform.bookings.2024-08-13.services.input_service, so a change to apps.api.v2.src.platform.bookings.2024-08-13.services.input_service can break apps.api.v2.src.platform.bookings.2024-08-13.services.bookings_service, while a change to apps.api.v2.src.platform.bookings.2024-08-13.services.bookings_service can't break apps.api.v2.src.platform.bookings.2024-08-13.services.input_service.
Position
Below the diagonal: apps.api.v2.src.platform.bookings.2024-08-13.services.bookings_service uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in apps.api.v2.src.platform.calendars.controllers.calendars_controller uses a type in apps.api.v2.src.platform.calendars.outputs.connected-calendars_output.
apps.api.v2.src.platform.calendars.controllers.calendars_controller uses apps.api.v2.src.platform.calendars.outputs.connected-calendars_output, so a change to apps.api.v2.src.platform.calendars.outputs.connected-calendars_output can break apps.api.v2.src.platform.calendars.controllers.calendars_controller, while a change to apps.api.v2.src.platform.calendars.controllers.calendars_controller can't break apps.api.v2.src.platform.calendars.outputs.connected-calendars_output.
Position
Below the diagonal: apps.api.v2.src.platform.calendars.controllers.calendars_controller uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in apps.api.v2.src.platform.calendars.controllers.calendars_controller uses a type in apps.api.v2.src.platform.bookings.2024-04-15.outputs.get-booking_output.
apps.api.v2.src.platform.calendars.controllers.calendars_controller uses apps.api.v2.src.platform.bookings.2024-04-15.outputs.get-booking_output, so a change to apps.api.v2.src.platform.bookings.2024-04-15.outputs.get-booking_output can break apps.api.v2.src.platform.calendars.controllers.calendars_controller, while a change to apps.api.v2.src.platform.calendars.controllers.calendars_controller can't break apps.api.v2.src.platform.bookings.2024-04-15.outputs.get-booking_output.
Position
Below the diagonal: apps.api.v2.src.platform.calendars.controllers.calendars_controller uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in apps.api.v2.src.platform.calendars.controllers.calendars_controller uses a type in apps.api.v2.src.platform.calendars.services.calendars_service.
apps.api.v2.src.platform.calendars.controllers.calendars_controller uses apps.api.v2.src.platform.calendars.services.calendars_service, so a change to apps.api.v2.src.platform.calendars.services.calendars_service can break apps.api.v2.src.platform.calendars.controllers.calendars_controller, while a change to apps.api.v2.src.platform.calendars.controllers.calendars_controller can't break apps.api.v2.src.platform.calendars.services.calendars_service.
Position
Below the diagonal: apps.api.v2.src.platform.calendars.controllers.calendars_controller uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in apps.api.v2.src.platform.event-types.event-types_2024_06_14.services.event-types_service uses a type in apps.api.v2.src.modules.prisma.prisma-write_service.
apps.api.v2.src.platform.event-types.event-types_2024_06_14.services.event-types_service uses apps.api.v2.src.modules.prisma.prisma-write_service, so a change to apps.api.v2.src.modules.prisma.prisma-write_service can break apps.api.v2.src.platform.event-types.event-types_2024_06_14.services.event-types_service, while a change to apps.api.v2.src.platform.event-types.event-types_2024_06_14.services.event-types_service can't break apps.api.v2.src.modules.prisma.prisma-write_service.
Position
Below the diagonal: apps.api.v2.src.platform.event-types.event-types_2024_06_14.services.event-types_service uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in apps.api.v2.src.platform.event-types.event-types_2024_06_14.services.event-types_service uses a type in apps.api.v2.src.platform.bookings.2024-04-15.outputs.get-booking_output.
apps.api.v2.src.platform.event-types.event-types_2024_06_14.services.event-types_service uses apps.api.v2.src.platform.bookings.2024-04-15.outputs.get-booking_output, so a change to apps.api.v2.src.platform.bookings.2024-04-15.outputs.get-booking_output can break apps.api.v2.src.platform.event-types.event-types_2024_06_14.services.event-types_service, while a change to apps.api.v2.src.platform.event-types.event-types_2024_06_14.services.event-types_service can't break apps.api.v2.src.platform.bookings.2024-04-15.outputs.get-booking_output.
Position
Below the diagonal: apps.api.v2.src.platform.event-types.event-types_2024_06_14.services.event-types_service uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in apps.api.v2.src.platform.event-types.event-types_2024_06_14.services.event-types_service uses a type in apps.api.v2.src.modules.users.users_repository.
apps.api.v2.src.platform.event-types.event-types_2024_06_14.services.event-types_service uses apps.api.v2.src.modules.users.users_repository, so a change to apps.api.v2.src.modules.users.users_repository can break apps.api.v2.src.platform.event-types.event-types_2024_06_14.services.event-types_service, while a change to apps.api.v2.src.platform.event-types.event-types_2024_06_14.services.event-types_service can't break apps.api.v2.src.modules.users.users_repository.
Position
Below the diagonal: apps.api.v2.src.platform.event-types.event-types_2024_06_14.services.event-types_service uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in apps.api.v2.src.platform.event-types.event-types_2024_06_14.services.event-types_service uses a type in apps.api.v2.src.platform.event-types.event-types_2024_06_14.event-types_repository.
apps.api.v2.src.platform.event-types.event-types_2024_06_14.services.event-types_service uses apps.api.v2.src.platform.event-types.event-types_2024_06_14.event-types_repository, so a change to apps.api.v2.src.platform.event-types.event-types_2024_06_14.event-types_repository can break apps.api.v2.src.platform.event-types.event-types_2024_06_14.services.event-types_service, while a change to apps.api.v2.src.platform.event-types.event-types_2024_06_14.services.event-types_service can't break apps.api.v2.src.platform.event-types.event-types_2024_06_14.event-types_repository.
Position
Below the diagonal: apps.api.v2.src.platform.event-types.event-types_2024_06_14.services.event-types_service uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in apps.api.v2.src.platform.event-types.event-types_2024_06_14.services.event-types_service uses a type in apps.api.v2.src.modules.users.services.users_service.
apps.api.v2.src.platform.event-types.event-types_2024_06_14.services.event-types_service uses apps.api.v2.src.modules.users.services.users_service, so a change to apps.api.v2.src.modules.users.services.users_service can break apps.api.v2.src.platform.event-types.event-types_2024_06_14.services.event-types_service, while a change to apps.api.v2.src.platform.event-types.event-types_2024_06_14.services.event-types_service can't break apps.api.v2.src.modules.users.services.users_service.
Position
Below the diagonal: apps.api.v2.src.platform.event-types.event-types_2024_06_14.services.event-types_service uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in apps.api.v2.src.platform.bookings.2024-08-13.controllers.bookings_controller uses a type in apps.api.v2.src.modules.users.services.users_service.
apps.api.v2.src.platform.bookings.2024-08-13.controllers.bookings_controller uses apps.api.v2.src.modules.users.services.users_service, so a change to apps.api.v2.src.modules.users.services.users_service can break apps.api.v2.src.platform.bookings.2024-08-13.controllers.bookings_controller, while a change to apps.api.v2.src.platform.bookings.2024-08-13.controllers.bookings_controller can't break apps.api.v2.src.modules.users.services.users_service.
Position
Below the diagonal: apps.api.v2.src.platform.bookings.2024-08-13.controllers.bookings_controller uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in apps.api.v2.src.platform.bookings.2024-08-13.controllers.bookings_controller uses a type in apps.api.v2.src.platform.bookings.2024-08-13.services.bookings_service.
apps.api.v2.src.platform.bookings.2024-08-13.controllers.bookings_controller uses apps.api.v2.src.platform.bookings.2024-08-13.services.bookings_service, so a change to apps.api.v2.src.platform.bookings.2024-08-13.services.bookings_service can break apps.api.v2.src.platform.bookings.2024-08-13.controllers.bookings_controller, while a change to apps.api.v2.src.platform.bookings.2024-08-13.controllers.bookings_controller can't break apps.api.v2.src.platform.bookings.2024-08-13.services.bookings_service.
Position
Below the diagonal: apps.api.v2.src.platform.bookings.2024-08-13.controllers.bookings_controller uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in apps.api.v2.src.platform.event-types.event-types_2024_06_14.controllers.event-types_controller uses a type in packages.platform.types.event-types.event-types_2024_06_14.inputs.create-event-type_input.
apps.api.v2.src.platform.event-types.event-types_2024_06_14.controllers.event-types_controller uses packages.platform.types.event-types.event-types_2024_06_14.inputs.create-event-type_input, so a change to packages.platform.types.event-types.event-types_2024_06_14.inputs.create-event-type_input can break apps.api.v2.src.platform.event-types.event-types_2024_06_14.controllers.event-types_controller, while a change to apps.api.v2.src.platform.event-types.event-types_2024_06_14.controllers.event-types_controller can't break packages.platform.types.event-types.event-types_2024_06_14.inputs.create-event-type_input.
Position
Below the diagonal: apps.api.v2.src.platform.event-types.event-types_2024_06_14.controllers.event-types_controller uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in apps.api.v2.src.platform.event-types.event-types_2024_06_14.controllers.event-types_controller uses a type in packages.platform.types.event-types.event-types_2024_06_14.inputs.update-event-type_input.
apps.api.v2.src.platform.event-types.event-types_2024_06_14.controllers.event-types_controller uses packages.platform.types.event-types.event-types_2024_06_14.inputs.update-event-type_input, so a change to packages.platform.types.event-types.event-types_2024_06_14.inputs.update-event-type_input can break apps.api.v2.src.platform.event-types.event-types_2024_06_14.controllers.event-types_controller, while a change to apps.api.v2.src.platform.event-types.event-types_2024_06_14.controllers.event-types_controller can't break packages.platform.types.event-types.event-types_2024_06_14.inputs.update-event-type_input.
Position
Below the diagonal: apps.api.v2.src.platform.event-types.event-types_2024_06_14.controllers.event-types_controller uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in apps.api.v2.src.platform.event-types.event-types_2024_06_14.controllers.event-types_controller uses a type in apps.api.v2.src.platform.event-types.event-types_2024_06_14.services.event-types_service.
apps.api.v2.src.platform.event-types.event-types_2024_06_14.controllers.event-types_controller uses apps.api.v2.src.platform.event-types.event-types_2024_06_14.services.event-types_service, so a change to apps.api.v2.src.platform.event-types.event-types_2024_06_14.services.event-types_service can break apps.api.v2.src.platform.event-types.event-types_2024_06_14.controllers.event-types_controller, while a change to apps.api.v2.src.platform.event-types.event-types_2024_06_14.controllers.event-types_controller can't break apps.api.v2.src.platform.event-types.event-types_2024_06_14.services.event-types_service.
Position
Below the diagonal: apps.api.v2.src.platform.event-types.event-types_2024_06_14.controllers.event-types_controller uses a module listed above it, which is the healthy direction.
At a glance — Code Health · 45% · Weak · gated by D1, D2, X4, X5 ·
Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).
OWASP category
Findings
Severity
A05:2025 — Injection
252
High / Critical
A03:2025 — Software Supply Chain Failures
168
High / Critical
A07:2025 — Authentication Failures
23
High / Critical
A02:2025 — Security Misconfiguration
14
High / Critical
A01:2025 — Broken Access Control
5
Medium
A08:2025 — Software or Data Integrity Failures
1
Medium
Roadmap
Immediately resolve the six leaked secrets, prioritizing REDACTED and REDACTED, while adding a SAST step to CI to prevent future security regressions. Strengthen operational resilience by codifying backups and geo-recovery in infrastructure as code and documenting recovery procedures. Finally, clean up the dependency tree by removing unused packages and explicitly declaring imports, and address the empty test suite to ensure reliable testing.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Resolve the 6 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (4), REDACTED (2).
Add a SAST step to CI running what this repository's stack ships: CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security — so a security regression fails the build instead of landing.
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 — 440
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 — 2215
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 — 1695
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 8
Something this survey could not settle
from the outside, and which could be critical or serious. Either a control was required and no
positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves
nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean
result. These are excluded from the score rather than awarded a pass, so the number on the cover neither
rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each
one is named under Limitations.
Methodology & how to trust this report
Watchdog is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. 96 of 96 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); none rely on LLM judgement. Overall confidence is 0.9 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.
Every figure here is one of three kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact; ◐ Advisory — an LLM prose judgement. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10; ◐ Sampled · advisory marks an LLM verdict over a bounded sample — advisory, never a deterministic measurement.
What we checked — 96 dimensions across the health lenses
Each chip is a dimension scored from real signals across architecture, testing, dependencies, security & compliance, documentation, git-history and code quality — in one coherent pass. A surface report typically covers a handful.
How to trust any code-health report — three questions
Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 4127 of 4350 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
Is there a tool behind the number? Every score below names the method that produced it — Roslyn, git, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — not a narrative.
Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
This report answers yes to all three. That's the bar to hold any assessment to.
Tools & methods
The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.
Method
Backs
Version
Evaluator
Roslyn static analysis
Complexity, cohesion, coupling, dead code, API surface, layering
What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.
D19 Documentation Quality — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
D19 Documentation Quality — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 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 — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
D22 Internal API Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22's deterministic call-shape rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
D24 Comment Value — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
D27 Navigability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
D32 Data Compliance (PII/GDPR) — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. `apps/api/v2/src/main.ts`, `apps/api/v2/src/modules/conferencing/repositories/conferencing.repository.ts`, `apps/api/v2/src/platform/calendars/calendars.repository.ts`, `apps/api/v2/src/platform/event-types/event-types_2024_06_14/services/output-event-types.service.ts`, `apps/api/v2/src/platform/event-types/event-types_2024_06_14/transformers/api-to-internal/interval-limits.ts`, … (+85 more) 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.
D44 Platform End-of-Life — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This dimension reads a project's own statement about the platform it runs on: a TargetFramework in a .NET project file, a .nvmrc or .python-version, a capped requires-python, a Rust toolchain file or Cargo.toml rust-version, a .go-version, .java-version, .ruby-version, .tool-versions or .sdkmanrc, a go.mod go directive, a Maven or Gradle Java level or toolchain, a Gemfile's ruby directive, a mix.exs elixir requirement, a rebar.config minimum_otp_vsn, a pubspec.yaml SDK constraint, a build.sbt scalaVersion, or a framework major pinned by a dependency constraint. This repository carries none of them, so nothing about its platform was established. That is a gap in this analyzer's coverage, NOT a finding that the platform is supported — a language whose runtime is declared elsewhere (Package.swift, a REDACTED) is simply not read here yet.
AC1 Text alternatives — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 211 further occurrence(s) are not listed individually; the score already reflects all 251.
AC2 Forms & labels — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 120 further occurrence(s) are not listed individually; the score already reflects all 160.
AXR1 Runtime accessibility — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DockerCompose (REDACTED). compose up failed (exit 14 — a file the compose project references is missing) — time="2026-10-26T16:53:52Z" level=warning msg="The \"DATABASE_URL\" variable is not set. Defaulting to a blank string." env file .env not found: stat .env: no such file or directory; runtime evidence skipped.
DM9 Scattered domain decisions — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Arm two tells a construction that PRODUCES a measurement from one that merely passes it along, and this repository's frontend does not compute that fact. A measurement built independently in two places would not appear above.
DM9 Scattered domain decisions — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Some of this repository's production types come from a frontend that does not bind comparison operands to the members they read, which arm one needs, and those types were not walked for this dimension. The counts above speak for the languages that declare it.
IC1 Incompleteness & stubs — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 177 further occurrence(s) are not listed individually; the score already reflects all 217.
M4 Documentation accuracy — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9). 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.
P2 Observability — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 206 further occurrence(s) are not listed individually; the score already reflects all 246.
R10 Code Duplication — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The filesystem refused the listing or the read of: packages/prisma/.env. Every other path was read.
R10 Code Duplication — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 1227 further occurrence(s) are not listed individually; the score already reflects all 1267.
R11 Import Boundaries — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 2142 further occurrence(s) are not listed individually; the score already reflects all 2182.
R3 Large Files — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 93 further occurrence(s) are not listed individually; the score already reflects all 133.
R4 Test Coverage — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 1248 further occurrence(s) are not listed individually; the score already reflects all 1288.
R7 Dead Code — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 547 further occurrence(s) are not listed individually; the score already reflects all 587.
X2 Cancellation propagation — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 57 further occurrence(s) are not listed individually; the score already reflects all 97.
X27 Collection changed while being enumerated — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and Java, Rust, Erlang, F#, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded, no Java, Rust, Erlang, F#, Python, Dart, Ruby, Scala or Kotlin was found, and this repository's PHP is not read yet, 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.
X4 Structured logging — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 50 further occurrence(s) are not listed individually; the score already reflects all 90.
Repo exclusion declarations: 2 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
Watchdog assesses the repository exactly as committed, and only the repository. By design it does not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.
D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
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.
D8 Code Coverage: Coverage is measured by building and running the test suite inside Watchdog's isolated image — the target repo is never modified, and nothing on your systems runs. So coverage exists only when the suite builds and runs within the inline time budget; one that needs external services, can't build, or exceeds the budget yields no coverage (D8 then degrades to not-measured, not a low score). Line coverage also says nothing about assertion quality.
D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
D11 Test Reliability: Flakiness is inferred from history/markers — Watchdog runs the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
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 is an LLM read of the decision records present — it cannot know about decisions made and never recorded, and its verdict is sampled and advisory.
D23 Boundary Type-Coupling: Boundary leakage is detected from type references across detected contexts — leaks that flow through primitives, serialization or shared infrastructure may not surface as a typed reference.
D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
D32 Data Compliance (PII/GDPR): PII/GDPR signals are heuristic pattern matches in code — they flag likely handling concerns, not legal compliance, and cannot trace where data actually flows at runtime.
D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
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.
AC7 A11y enforcement: Enforcement is scored from in-repo config/CI evidence only — an a11y gate enforced in external tooling with no in-repo trace can't be credited, and a configured linter is presence, not proof the rules actually run or block a merge.
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.
C3 Audit Trail: This control is scored from in-repo evidence only — a working control configured outside the repository leaves no signal a static scan can credit.
C4 Data Retention: This control is scored from in-repo evidence only — its real-world effectiveness, exercised only at runtime, is outside a static scan.
M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
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.
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.
277 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was RegularBookingService.handler at 282. A further 4 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 business-days-plugin.BusinessDaysPlugin at 35 — 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: packages/dayjs/plugins/business-days-plugin.ts (business-days-plugin.BusinessDaysPlugin at 35), packages/features/booking-audit/lib/service/BookingAuditTaskConsumer.ts (BookingAuditTaskConsumer.getRecordType at 16). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
+ 269 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 2 bodies over 120 down to 120 or less in Cyclomatic Complexity — start with RegularBookingService.handler (cyclomatic 282), bookings-single-view.Success (cyclomatic 204). — 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 3.9 to about 5.1/10, projected with the scoring formula itself and assuming each lands exactly at 120; a cleaner split scores higher.
Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d1_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How hard the code is for a person to follow, beyond raw branching.
Method: Cognitive complexity per method (Sonar-style nesting-penalized score), computed exhaustively over production code, excluding test projects. Deterministic.
+ 320 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 1 body over 240 down to 240 or less in Cognitive Complexity — start with RegularBookingService.handler (cognitive 453). — Refactoring it lifts Cognitive Complexity from 2.4 to about 3.5/10.
Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes6.4 / 10Adequate✓ Tool-verified
What it measures: Over-large classes that try to do too much ("god classes").
Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.
Resolve the 218 FunctionTooLong finding(s) in God Classes — start with Setup.tsx (7), VideoApiAdapter.ts (4), REDACTED (3). — One of this dimension's main actionable groups (218 warning-level).
Resolve the 48 FileTooLong finding(s) in God Classes — start with CalendarService.ts (3), RegularBookingService.ts, REDACTED. — One of this dimension's main actionable groups (48 warning-level).
Resolve the 17 MethodTooLong finding(s) in God Classes — start with eventTypeRepository.ts (3), REDACTED (2), CalendarService.ts (2). — One of this dimension's main actionable groups (17 warning-level).
Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling9.2 / 10Stronggated by 11 serious findings✓ 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.
110 production modules (npm), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 11 module(s) off the main sequence, with abstractness counted on 87 of the 110 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
Off the main sequence: @calcom/config · ×11
What to do
Resolve the 11 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (11 warning-level).
Enforce Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d5_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether a class's methods are focused on a single responsibility.
Method: LCOM4 cohesion per production class with at least two methods: connected components of methods sharing state or calls, computed syntactically. Deterministic, not a proxy.
Coverage: Exhaustive · type-level: LCOM4 cohesion computed over every production class — the population is all types, not a name convention.
Resolve the 7 Low cohesion finding(s) in Cohesion (LCOM4) — start with REDACTED, atoms.schedules.controller.ts, bookings.controller.ts. — One of this dimension's main actionable groups (7 warning-level).
Enforce Cohesion (LCOM4) in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
Detailed fixes: d6_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether 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.
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).
What to do
Enforce Architectural Integrity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d7_recommendation.md.
Do you agree with this assessment?
D8 · Code Coverage8.2 / 10Strong✓ Tool-verified
What it measures: How much of the code is actually exercised by tests.
Method: Coverage from coverlet runs or committed reports (Cobertura/OpenCover/lcov), computed per-file with structured exclusions for generated, trivial, and glue code. When the suite can't be built/run in-image AND no report is committed, coverage is reported NOT-MEASURED (excluded from the score) with the precondition to make it measurable — never a LoC-ratio proxy folded in as if measured. Deterministic.
Line coverage 45.1% — 205 file(s) below 50%. Measured from the JavaScript/TypeScript suite (vitest + @vitest/coverage-v8 via `yarn install --immutable --mode=skip-build` in the repository root; jest via `yarn install --immutable --mode=skip-build` in apps/api/v2/; vitest in packages/app-store/closecom/: not run; jest in packages/platform/atoms/: not run; jest via `yarn install --immutable --mode=skip-build` in packages/platform/utils/; vitest in packages/testing/: not run).
Resolve the 205 Low coverage finding(s) in Code Coverage — start with REDACTED (3), REDACTED (3), CalendarService.ts (3). — One of this dimension's main actionable groups (205 warning-level).
Enforce Code Coverage in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
Detailed fixes: d8_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D9 · Test Distribution8.4 / 10Strong✓ Tool-verified
What it measures: Whether the test suite has a healthy mix of unit / integration / end-to-end tests.
Method: Test projects classified (Unit/Integration/BDD/E2E) from compiled metadata; test methods counted exhaustively across projects with placement-agnostic disk fallback. Deterministic.
5036 test methods: 4433 unit, 0 integration, 0 BDD, 603 e2e. The JavaScript/TypeScript suite contributes 5036 `it`/`test` case(s) across 502 test file(s) declaring at least one; its tier split is read from package names and paths only.
What to do
Improve Test Distribution — currently 8.4/10. — 5036 test methods: 4433 unit, 0 integration, 0 BDD, 603 e2e. The JavaScript/TypeScript suite contributes 5036 `it`/`test` case(s) across 502 test file(s) declaring at least one; its tier split is read from package names and paths only.
Detailed fixes: d9_recommendation.md.
Do you agree with this assessment?
D10 · Test Quality9.8 / 10Stronggated by 69 serious findings✓ Tool-verified
What it measures: Whether the tests truly assert behaviour rather than just running the code.
Method: Per-test assertions, skips, and mock references analyzed via Roslyn; structured skip-reason tags (BUG:/ENV:) separate documented deferrals from debt. Deterministic.
31 skipped (4 with a documented reason), 42 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 5036 tests.
No assertions: toggles bold formatting when bold button is clicked · ×42packages/ui/components/editor/plugins/ToolbarPlugin.test.tsx:130
Skipped test: create team event using CreateTeamEventTypeAtom · ×27packages/platform/examples/base/tests/create-team-event-type-atom/create-team-event-type.e2e.ts:6
Resolve the 81 Mock-dominated test finding(s) in Test Quality — start with CalendarSubscriptionService.test.ts (11), next-auth-options.test.ts (11), OAuthManager.test.ts (10). — One of this dimension's main actionable groups (81 recommendation-level).
Resolve the 42 No assertions finding(s) in Test Quality — start with webhook-producer-booking-requested.test.ts (7), FormBuilder.test.tsx (7), fresh-booking.test.ts (5). — One of this dimension's main actionable groups (42 warning-level).
Resolve the 27 Skipped test finding(s) in Test Quality — start with google-calendar.e2e.ts (8), getSchedule.test.ts (3), date-ranges.test.ts (2). — One of this dimension's main actionable groups (27 warning-level).
Enforce Test Quality in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d10_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D11 · Test Reliability10.0 / 10Adequategated by 1 critical finding✓ Tool-verified
What it measures: Whether the tests pass reliably, with no flakiness.
Method: Suite re-run N times within tiered wall-clock budgets (unit to e2e); tests failing non-deterministically across runs flagged; guarded tests retried when #if guards detected.
0 flaky across 1 measured tier(s). JavaScript/TypeScript (vitest via `yarn install --immutable --mode=skip-build` in the repository root (2155 tests); jest via `yarn install --immutable --mode=skip-build` in apps/api/v2/ (82 tests); vitest via `yarn install --immutable --mode=skip-build` in packages/app-store/closecom/ (0 tests); jest via `yarn install --immutable --mode=skip-build` in packages/platform/atoms/ (0 tests); jest via `yarn install --immutable --mode=skip-build` in packages/platform/utils/ (8 tests); vitest via `yarn install --immutable --mode=skip-build` in packages/testing/ (0 tests)): measured (0 flaky).
Test suite declares a test script but contains no test files: packages/platform/atoms/
What to do
Resolve the 1 Test suite declares a test script but contains no test files finding(s) in Test Reliability. — One of this dimension's main actionable groups (1 issue-level).
Detailed fixes: d11_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether dependencies are current, secure, and not bloated.
Method: Manifest scan via dotnet list package across all projects; worst-signal-per-package deduction (saturating for vulnerabilities, capped-linear for deprecation/outdated) per KLoC. Exhaustive, deterministic.
205 outdated direct production npm dependency(ies) of 243 graded, 8 pinning defect(s), across 117 REDACTED (110 of them the product) and 2 committed lockfile(s). 243 of 249 resolved direct production dependency(ies) were graded against registry.npmjs.org (6 not published there — private or renamed). Development dependencies are deliberately not graded for currency: that grade is about what SHIPS. 6 direct dependency(ies) — production, development or optional — are marked DEPRECATED by their publisher (the registry's per-version mark, or the lockfile's copy of it when the registry could not be asked); deprecated transitive packages are listed but not charged. Whether any is UNMAINTAINED is not graded — the registry publishes no maintenance status, and release age does not stand in for one. Whether any is UNUSED is not graded either: that is a source question, and the frontend dependency lens (R8) answers it in this same run. Known CVEs in this dependency graph are D30's question, read from the manifest there.
Deprecated: querystring · ×6REDACTED:82
One package at two majors across the workspace: next · ×5
+ 1 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 6 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (6). — One of this dimension's main actionable groups (6 warning-level).
Resolve the 5 One package at two majors across the workspace finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (5 warning-level).
Resolve the 3 Floating npm dependency finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (3 warning-level).
Detailed fixes: d12_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.
Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.
Resolve the 6 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (4), REDACTED (2). — One of this dimension's main actionable groups (6 issue-level).
Enforce REDACTED Scanning in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d13_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the licenses of third-party packages are compatible with your policy.
Method: Third-party package licenses resolved from declared package metadata and checked against the configured policy (allow/deny/copyleft). Deterministic; clean = no incompatible license found at metadata depth.
0 of 243 shipped npm package(s) use a banned license. Licences were resolved from registry.npmjs.org over the 249 production dependency(ies) this repository's committed lockfile resolves, across 110 product REDACTED manifest(s). Its 322 `devDependencies` declaration(s) are excluded: a consumer installs none of them. ★ DEPTH: this is the DIRECT production set the lockfile resolves, NOT the transitive closure — only one of the four lock dialects this pass reads states a full graph, so a banned licence pulled in only by a dependency's OWN dependencies is outside this verdict, exactly as the JVM arm's declaration-site verdict is. ★ Each licence is the one the registry publishes for the package's CURRENT release rather than for the pinned version, which is the same caveat the Hex and RubyGems arms carry. 7 of them publish no licence this pass can read on registry.npmjs.org — an absent field, `UNLICENSED`, or a `SEE LICENSE IN <file>` pointer into a tarball this pass does not download; that is missing data, not a violation, and none of them is charged. A further 6 package(s) the lockfile resolves are not published on the public registry at all — a private scope, a workspace-internal name or a git install — and are outside this verdict. This repository publishes itself under ISC / MIT / SEE LICENSE IN LICENSE / UNLICENSED, which is its own choice and is not judged here.
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.
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.
56 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is packages/coss-ui/src/icons.tsx. Counted over 1267 of the 4311 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 · ×4
Further sole-owners (lower concentration)
✓ On the Gold path — maintain.
Detailed fixes: d16_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Acknowledged debt left in the code — TODOs, dead code, suppressed warnings.
Method: Roslyn syntactic debt markers (suppressions/TODO/FIXME/HACK/empty-catch/commented-code/Obsolete) plus SymbolFinder dead-code analysis; weighted-debt-per-KLoC density deducted 2.0x per unit. Deterministic, exhaustive.
289 deducted task-comment markers across 332849 LoC (0.1/KLoC) → score 9.8. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
Resolve the 240 TodoComment finding(s) in Explicit Debt — start with REDACTED (9), VideoApiAdapter.ts (8), types.ts (6). — One of this dimension's main actionable groups (240 warning-level).
Resolve the 36 FixmeComment finding(s) in Explicit Debt — start with fresh-booking.test.ts (3), recurring-event.test.ts (3), REDACTED (2). — One of this dimension's main actionable groups (36 warning-level).
Resolve the 13 HackComment finding(s) in Explicit Debt — start with locations.ts (3), build.ts (2), LargeCalendar.tsx (2). — One of this dimension's main actionable groups (13 warning-level).
Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the project's documentation is clear, complete, and useful.
Method: Every README, docs/ document and root guide parsed by its markup and measured in Unicode letters. Published: a runnable or packaged .NET project whose README (or a document it links, or a root guide) shows no example, and a root README naming none of three or more projects. Overview, licence, boilerplate, wall-of-text, empty-section and XML-doc rows are measured and withheld (counted in gaps) after adjudication. Deterministic, exhaustive, advisory.
1 of 1 documentation facets pass in full. 73 document(s) read across 1 unit(s).
✓ On the Gold path — maintain.
Detailed fixes: d19_recommendation.md.
Do you agree with this assessment?
D20 · ADR Quality6.7 / 10Adequate✓ Tool-verified
What it measures: Whether architecture decisions are recorded well (context, decision, consequences).
Method: Per-ADR judgment by language model at low temperature with two-pass stability; confidence is share of ADRs evaluated; enforcement-field presence detected deterministically. Advisory.
1 of 3 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). How well each record argues its case is not measured.
ADR Context section is emptyspecs/_templates/decisions.md:5detected by adr-integrity
ADR Decision section is emptyspecs/_templates/decisions.md:14detected by adr-integrity
ADR Consequences section is emptyspecs/_templates/decisions.md:18detected by adr-integrity
What to do
Resolve the 1 ADR Context section is empty finding(s) in ADR Quality — start with decisions.md. — One of this dimension's main actionable groups (1 recommendation-level).
Resolve the 1 ADR Decision section is empty finding(s) in ADR Quality — start with decisions.md. — One of this dimension's main actionable groups (1 recommendation-level).
Resolve the 1 ADR Consequences section is empty finding(s) in ADR Quality — start with decisions.md. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d20_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether domain types (IDs, enums, value objects) leak across bounded-context boundaries.
Method: Cross-context domain-type leakage via Roslyn structural classification (strongly-typed IDs / value objects) over every public surface. Exhaustive, deterministic, type-level aggregate-boundary check.
Coverage: Bounded contexts derived from NAMESPACE prefix (or graph-inferred where available); cross-boundary domain-type leakage then checked exhaustively over every public member of every type.
78 domain type(s) cross context boundaries across 91 contexts.
Cross-context type BookingReportStatus (web → features) · ×8packages/features/bookingReport/repositories/IBookingReportRepository.ts:25
Cross-context type BookingStatus (trpc → features) · ×6packages/features/bookings/repositories/IBookingRepository.ts:23
Cross-context type CreateBookingInput (types → v2) · ×5apps/api/v2/src/platform/bookings/2024-08-13/controllers/bookings.controller.ts:105
Cross-context type RescheduleBookingInput (types → v2) · ×5apps/api/v2/src/platform/bookings/2024-08-13/controllers/bookings.controller.ts:296
Cross-context type PrivateLinkOutput (types → v2) · ×5apps/api/v2/src/platform/event-types-private-links/services/private-links.service.ts:20
+ 33 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 8 Cross-context type BookingReportStatus (web → features) finding(s) in Boundary Type-Coupling — start with IBookingReportRepository.ts (5), PrismaBookingReportRepository.ts (3). — One of this dimension's main actionable groups (8 warning-level).
Resolve the 6 Cross-context type BookingStatus (trpc → features) finding(s) in Boundary Type-Coupling — start with IBookingRepository.ts, BookingRepository.ts, handleConfirmation.ts. — One of this dimension's main actionable groups (6 warning-level).
Resolve the 5 Cross-context type CreateBookingInput (types → v2) finding(s) in Boundary Type-Coupling — start with bookings.service.ts (3), bookings.controller.ts, errors.service.ts. — One of this dimension's main actionable groups (5 warning-level).
Enforce Boundary Type-Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
Detailed fixes: d23_recommendation.md · top locations in Appendix A, every location in findings.md.
10 of 111 build units (npm) flagged as possibly oversized/incoherent.
Projects may be oversized for their cohesion
What to do
Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d26_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.
Method: 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.
16 finding(s): 0 critical, 16 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
Resolve the 10 REDACTED finding(s) in Secrets (history) — start with REDACTED (4), REDACTED (2), REDACTED. — One of this dimension's main actionable groups (10 issue-level).
Resolve the 6 High secret finding(s) in Secrets (history) — start with REDACTED (5), REDACTED. — One of this dimension's main actionable groups (6 issue-level).
Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d28_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.
Method: Polyglot static analysis via semgrep across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.
Coverage: semgrep pattern rules over all files — exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).
252 finding(s): 0 critical, 196 high, 56 medium, 0 low. 89 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 104 file(s) — `apps/api/v2/src/main.ts` (line 66), `apps/api/v2/src/modules/conferencing/repositories/conferencing.repository.ts` (line 23), `apps/api/v2/src/modules/event-types/controllers/event-types-webhooks.controller.e2e-spec.ts` (line 116, line 129, line 142, …), `apps/api/v2/src/modules/oauth-clients/controllers/oauth-client-webhooks/oauth-client-webhooks.controller.e2e-spec.ts` (line 183, line 196, line 206, …), `apps/api/v2/src/modules/webhooks/controllers/webhooks.controller.e2e-spec.ts` (line 82, line 95, line 108, …), … (+99 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 13 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
+ 18 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 13 REDACTED finding(s) charged to Static Analysis (SAST) — the other 89 are reported here at file:line but scored by D36 (supply-chain provenance), which charges them once. — One of this dimension's main actionable groups (102 issue-level, 13 of them charged here).
Resolve the 31 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (8), REDACTED (4), REDACTED (4). — One of this dimension's main actionable groups (31 issue-level).
Resolve the 30 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (17), REDACTED (12), REDACTED. — One of this dimension's main actionable groups (30 issue-level).
Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any dependency has a known published vulnerability (CVE), direct or transitive, in ANY ecosystem the repository declares — Dart pub, Elixir and Erlang via Hex, Go modules, Java and Kotlin via Maven/Gradle, JavaScript/npm, .NET/NuGet, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift.
Method: Dependency-CVE scan across every ecosystem the repository declares, scored ONCE. Three sources are unioned and deduplicated by advisory identity (rule id + alias closure, CVE<->GHSA) scoped to package+version, keeping the worst severity: `osv-scanner --recursive` over osv.dev for Dart pub, Elixir/Hex (and Erlang, whose `rebar.lock` syft first converts to a CycloneDX SBOM the scanner reads, with rows attributed back to the lock), Go, Java and Kotlin via Maven/Gradle (and Scala, whose sbt build's pinned direct declarations are written into a CycloneDX SBOM the scanner reads, with rows attributed back to the build file), npm, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift; `trivy fs --scanners vuln` for npm lockfiles; and `dotnet list package --vulnerable --include-transitive` for NuGet (with per-advisory collapse of the project x target-framework fan-out), plus a DECLARED-dependency arm that resolves a published gem's gemspec against rubygems.org where no Gemfile.lock is committed. `SeverityScore(c,h,m,l, normalizer 8.0)`. NotApplicable only when NO ecosystem is readable; if any applicable ecosystem could not be scanned the findings are REPORTED and the score is withheld. Supersedes the npm and OSV arms, retired 2026-09-05.
+ 1 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 68 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (56), REDACTED (12). — One of this dimension's main actionable groups (68 issue-level).
Resolve the 8 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (4), REDACTED (4). — One of this dimension's main actionable groups (8 issue-level).
Resolve the 3 High vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED (2), REDACTED. — One of this dimension's main actionable groups (3 issue-level).
Detailed fixes: d30_recommendation.md · top locations in Appendix A, every location in findings.md.
Resolve the 8 High IaC finding(s) in IaC & Container Security — start with REDACTED (5), REDACTED (2), REDACTED. — One of this dimension's main actionable groups (8 issue-level).
Resolve the 5 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (4), REDACTED. — One of this dimension's main actionable groups (5 warning-level).
Resolve the 1 Low IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d31_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D32 · Data Compliance (PII/GDPR)6.0 / 10Adequate✓ 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 Watchdog's 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.
5 finding(s): 0 critical, 0 high, 5 medium, 0 low. semgrep could not parse 90 file(s) — `apps/api/v2/src/main.ts`, `apps/api/v2/src/modules/conferencing/repositories/conferencing.repository.ts`, `apps/api/v2/src/platform/calendars/calendars.repository.ts`, `apps/api/v2/src/platform/event-types/event-types_2024_06_14/services/output-event-types.service.ts`, `apps/api/v2/src/platform/event-types/event-types_2024_06_14/transformers/api-to-internal/interval-limits.ts`, … (+85 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.
REDACTED
What to do
Resolve the 5 REDACTED finding(s) in Data Compliance (PII/GDPR) — start with REDACTED (2), REDACTED, REDACTED. — One of this dimension's main actionable groups (5 warning-level).
Detailed fixes: d32_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether anyone still has living knowledge of each file, or it has been orphaned — last understood long ago by someone now gone quiet. The sibling of the bus factor: D16 asks who owns it, D34 asks whether anyone still knows it.
Method: File orphaning as total living-knowledge decay below one focused-commit's worth within a year, computed per-file from the D16 decay model. Exhaustive, deterministic over fixed history.
1188 of 1267 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is packages/app-store/salesforce/lib/CrmService.ts. Counted over 1267 of the 4311 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
Orphaned file · ×1185REDACTED:1
Most significant orphaned file · ×3packages/app-store/salesforce/lib/CrmService.ts:1
Concentrated knowledge decay
What to do
Resolve the 1185 Orphaned file finding(s) in Knowledge Freshness — start with REDACTED (20), REDACTED (17), CalendarService.ts (11). — One of this dimension's main actionable groups (1185 recommendation-level).
Resolve the 3 Most significant orphaned file finding(s) in Knowledge Freshness — start with REDACTED, REDACTED, EventManager.ts. — One of this dimension's main actionable groups (3 recommendation-level).
Resolve the 1 Concentrated knowledge decay finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d34_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.
Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.
Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling. A non-source file is never a coupling PARTICIPANT either: documentation, schemas, config and data files are dropped with the rest, so a code↔docs pair — a command and the reference page that restates it — is not reported however strongly the two co-change; nor is coupling that runs THROUGH a build step or config file.
Resolve the 9 Change coupling finding(s) in Change Coupling — start with RegularBookingService.ts (2), PremiumTextfield.tsx, event-types.repository.ts. — One of this dimension's main actionable groups (9 warning-level).
Detailed fixes: d35_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the build pipeline provides supply-chain integrity — generated provenance/attestation, signed artifacts (cosign/sigstore), an SBOM, and pinned build actions. Presence of the configuration, not a runtime guarantee.
Method: Supply-chain provenance/signing read deterministically from CI/build config (.github/workflows, .gitlab-ci.yml, azure-pipelines, Jenkinsfile, .circleci) + the release surface: four signals — generated provenance/attestation (SLSA/in-toto/actions-attest), artifact signing (cosign/sigstore/gitsign), an SBOM (syft/sbom-action/*.spdx.json/*.cdx.json), and SHA-pinned build actions — scored 10·present/denom. NotApplicable without a build pipeline. Detects configuration presence, not runtime enforcement.
+ 6 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 13 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (13 warning-level).
Resolve the 2 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d36_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the repository publishes a coordinated-vulnerability-disclosure policy (SECURITY.md or security.txt) with a reporting contact, so finders know how to report a vulnerability. Presence of a policy file with a contact, not whether the policy is adequate or honoured.
Method: Vulnerability-disclosure policy read deterministically from the repo: a SECURITY.md (root/.github/docs) or .well-known/security.txt / security.txt, regex-checked for a reporting contact (email / URL / mailto). Present + contact → 10; present without a contact → 4; NotApplicable when no policy file exists (it may live off-repo). Detects the policy file's presence + contact, not its adequacy.
What it measures: Whether any dependency the repository declares is published as MALICIOUS rather than merely vulnerable — a package that is an attacker's work, in any ecosystem osv-scanner reads. Scored apart from D30 because the answer is binary: there is no safe version to upgrade to, and the fix is to remove the package and rotate every credential it could have read.
Method: The same dependency scan D30 reads, partitioned on the scanner's own classification rather than rescanned: a row is MALICIOUS when its id is in the `MAL-` space (the ossf/malicious-packages feed) OR its `database_specific.cwe_ids` carries `CWE-506` ("Embedded Malicious Code"). Both channels are structural; the summary text is deliberately NOT read, because a malicious-package record whose summary says only "Critical severity vulnerability" is a real shape ([GHSA redacted]) and a text matcher misses it. Scored BINARY: any surviving row is 0, whatever its severity and however many CVEs sit beside it — a hostile dependency is not a quantity. Applicability and degradation are D30's: NotApplicable only when no ecosystem is readable, and an unscannable ecosystem degrades rather than reading clean. SCORED, not informational.
Resolve the 1 Malicious package finding(s) in Malicious Dependencies — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d43_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
Frontend & cross-cutting dimensions
R = React/JS · M = Maturity · P = Readiness.
AC1 · Text alternatives2.0 / 10Critical✓ 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. (×40) — apps/web/public/country-flag-icons/3x2/index.html:50, apps/web/public/country-flag-icons/3x2/index.html:61, apps/web/public/country-flag-icons/3x2/index.html:72, …
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.
Do you agree with this assessment?
AC2 · Forms & labels4.8 / 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 fieldset groups related controls but has no <legend> to name the group. Add a <legend> as its first child — or, if the group already has a visible caption beside it (or the fieldset is there only to disable its subtree and carries no group box), point aria-labelledby at that caption's id instead, which names the group without rendering a second one. (×8) — apps/web/components/apps/applecalendar/Setup.tsx:77, apps/web/components/apps/caldavcalendar/Setup.tsx:63, apps/web/components/apps/exchange2013calendar/Setup.tsx:57, …
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). (×6) — apps/web/components/apps/ics-feedcalendar/Setup.tsx:77, apps/web/components/dialog/WrongAssignmentDialog.tsx:117, apps/web/modules/apps/components/AllApps.tsx:91, …
This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed. (×5) — apps/web/components/booking/CancelBooking.tsx:53, apps/web/components/booking/CancelBooking.tsx:66, apps/web/components/booking/CancelBooking.tsx:231, …
This UI-library field component has no label / aria-label / aria-labelledby / id — and neither does anything it renders (a name prop is the form-submission key, not a label) — 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. (×7) — apps/web/components/dialog/RescheduleDialog.tsx:51, apps/web/components/settings/TravelScheduleModal.tsx:135, apps/web/modules/booking-audit/components/BookingHistory.tsx:121, …
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. (×14) — apps/web/modules/blocklist/components/BlocklistEntryDetailsSheet.tsx:75, apps/web/modules/blocklist/components/BlocklistEntryDetailsSheet.tsx:82, apps/web/modules/blocklist/components/BlocklistEntryDetailsSheet.tsx:91, …
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.
Other · Accessibility — Whether pages declare a language (well-formed BCP-47) and a non-empty title, expose exactly one main landmark and a sane heading order with non-empty headings, keep zoom enabled, title their iframes, give data tables header cells, and avoid meta-refresh. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: html lang, document <title>, a main landmark and heading order on full documents only, plus zoom-disabling viewports, untitled iframes and meta-refresh anywhere. Deterministic, per structural checkpoint.
Coverage: Population: the PARSED MARKUP documents (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx). The page-level checks — lang, title, single main landmark — fire ONCE PER FULL DOCUMENT (an <html> root) and never on a partial or component fragment, so a repo of fragments is assessed only on the per-element checks (heading order, table headers, iframe titles, meta-refresh, zoom). Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en"). (×8) — apps/web/app/global-error.tsx:15, apps/web/public/country-flag-icons/3x2/index.html:3, packages/embeds/embed-core/index.html:1, …
A page with no <title> gives no name in the tab, history or screen-reader page list. Declare it the way this router does — Next App Router `export const metadata = { title }`, React Router/Remix `export function meta`, TanStack Start `head`, or a Helmet/Head component. (×2) — apps/web/app/global-error.tsx:15, apps/web/app/layout.tsx:108
No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. (×4) — apps/web/app/layout.tsx:108, apps/web/public/country-flag-icons/3x2/index.html:3, packages/embeds/embed-core/index.html:1, …
Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one. (×2) — apps/web/app/notFoundClient.tsx:100, apps/web/components/apps/AppPage.tsx:423
user-scalable=no/0 or a maximum-scale below 2 stops low-vision users zooming to 200%. Remove the zoom restriction from the viewport meta. — apps/web/components/PageWrapper.tsx:67
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). (×3) — REDACTED:564, REDACTED:590, REDACTED:619
A page with no <title> gives no name in the tab, history or screen-reader page list. Add a descriptive <title> in <head>. (×5) — packages/embeds/embed-core/preview.html:1, packages/embeds/embed-react/element-click.html:1, packages/embeds/embed-react/floating.html:1, …
An iframe with no title (or an empty one) is announced only as "frame". Add a non-empty title describing its content, or an aria-label. — packages/features/embed/lib/EmbedTabs.tsx:200
What to do
Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
Other · Accessibility — Whether 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".
This <div role="dialog"> is a modal dialog, but nothing moves focus into it when it opens and nothing keeps focus inside it while it is open, so a keyboard or screen-reader user keeps acting on the content behind it (WCAG 2.4.3). Use a native <dialog> opened with showModal(), a dialog component that traps focus, or move focus to the dialog on open, trap Tab inside it (or make the page behind inert) and return focus to the control that opened it on close. (×5) — apps/web/app/(use-page-wrapper)/payment/[uid]/PaymentPage.tsx:107, apps/web/modules/bookings/components/BookingSuccessCard.tsx:38, apps/web/modules/bookings/components/DecoyBookingSuccessCard.tsx:38, …
A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler. (×12) — apps/web/components/apps/installation/AccountsStepCard.tsx:43, REDACTED:49, apps/web/components/ui/LimitedBadges.tsx:93, …
This <div role="dialog"> is a modal dialog, but focus is moved into it, but nothing keeps it there: Tab walks out to the page behind, so a keyboard or screen-reader user keeps acting on the content behind it (WCAG 2.4.3). Use a native <dialog> opened with showModal(), a dialog component that traps focus, or move focus to the dialog on open, trap Tab inside it (or make the page behind inert) and return focus to the control that opened it on close. — REDACTED:504
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. — apps/web/modules/calendars/weeklyview/components/event/EventList.tsx:108
The repo's own CSS styles .cursor-pointer with `cursor: pointer`, so this <div> is a control — but it has no role, no tabIndex={0} and no key handler, so it can only be reached with a mouse. Use a <button>, or add role + tabIndex={0} + a key handler. — apps/web/modules/event-types/views/event-types-listing-view.tsx:837
The repo's own CSS styles .cursor-pointer with `cursor: pointer`, so this <img> is a control — but it has no role, no tabIndex={0} and no key handler, so it can only be reached with a mouse. Use a <button>, or add role + tabIndex={0} + a key handler. — apps/web/modules/settings/components/BookerLayoutSelector.tsx:189
An <a href="#"> (or javascript:) with a click handler is a button dressed as a link — it announces the wrong role and stops working without JS. Use a <button> for an action. — apps/web/modules/webhooks/components/WebhookListItem.tsx:108
This <div> carries tabIndex={0}, so it is in the tab order and a keyboard user will land on it — but its behaviour is bound to the pointer only, with no key handler. A tabindex makes an element focusable, not operable: Enter and Space fire a click on a native <button> or <a href> and nowhere else, so this can be focused and never activated. Use a <button>, or handle Enter/Space in a key handler. — packages/ui/components/editor/plugins/ToolbarPlugin.tsx:211
What to do
Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
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.
aria-hidden="true" here hides the subtree from assistive tech, but a focusable descendant stays in the tab order — a keyboard user can land on a control screen readers can't see. Add inert, take the descendants out of the tab order (tabindex="-1"), or drop aria-hidden. (×3) — apps/web/app/(use-page-wrapper)/payment/[uid]/PaymentPage.tsx:103, REDACTED:498, packages/platform/atoms/event-types/payments/PaymentForm.tsx:57
What to do
Use valid, non-abstract roles, supply the ARIA state each role requires, and never put aria-hidden on a focusable element.
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.
<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). (×5) — apps/web/components/booking/BookingListItem.tsx:909, apps/web/components/booking/BookingListItem.tsx:988, REDACTED:740, …
<svg> 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:. (×2) — packages/app-store/giphy/components/SearchDialog.tsx:155, packages/ui/components/button/Button.tsx:288
<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). — packages/app-store/vital/components/AppConfiguration.tsx:132
`.react-calendar 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. — packages/ui/components/form/date-range-picker/styles.css:36
`.editor-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. — packages/ui/components/editor/stylesEditor.css:44
`.link-editor .link-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. — packages/ui/components/editor/stylesEditor.css:299
`.outline-none` 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. — packages/platform/atoms/globals.css:5853
`.focus\:outline-none:focus` 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. — packages/platform/atoms/globals.css:6901
`.focus\:outline-none\!:focus` 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. — packages/platform/atoms/globals.css:6905
`.focus-visible\:outline-none:focus-visible` 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. — packages/platform/atoms/globals.css:6976
`.react-tel-input .form-control` 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. — packages/platform/atoms/globals.css:11691
`.react-tel-input .country-list` 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. — packages/platform/atoms/globals.css:11767
`.react-tel-input .country-list .search-box` 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. — packages/platform/atoms/globals.css:11823
`.animate-fade-in-up` moves (`animation: fade-in-up 0.6s var(--animation-delay, 0s) cubic-bezier(0.21, 1.02, 0.73, 1) forwards`) 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. — packages/platform/atoms/globals.css:3291
`.animate-spinning` moves (`animation: 0.75s linear infinite spinning`) 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. — packages/platform/atoms/globals.css:3300
`.data-\[state\=closed\]\:animate-out[data-state="closed"]` moves (`animation: exit var(--tw-animation-duration, var(--tw-duration, 0.15s)) var(--tw-ease, ease)
var(--tw-animation-delay, 0s) var(--tw-animation-iteration-count, 1)
var(--tw-animation-direction, normal) var(--tw-animation-fill-mode, none)`) 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. — packages/platform/atoms/globals.css:7233
`.data-\[state\=open\]\:animate-in[data-state="open"]` moves (`animation: enter var(--tw-animation-duration, var(--tw-duration, 0.15s)) var(--tw-ease, ease)
var(--tw-animation-delay, 0s) var(--tw-animation-iteration-count, 1)
var(--tw-animation-direction, normal) var(--tw-animation-fill-mode, none)`) 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. — packages/platform/atoms/globals.css:7259
`.data-\[swipe\=end\]\:animate-out[data-swipe="end"]` moves (`animation: exit var(--tw-animation-duration, var(--tw-duration, 0.15s)) var(--tw-ease, ease)
var(--tw-animation-delay, 0s) var(--tw-animation-iteration-count, 1)
var(--tw-animation-direction, normal) var(--tw-animation-fill-mode, none)`) 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. — packages/platform/atoms/globals.css:7309
`.loader` moves (`animation: 2s infinite loader`) 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. — packages/platform/atoms/globals.css:10396
`.loader-inner` moves (`animation: 2s ease-in infinite loader-inner`) 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. — packages/platform/atoms/globals.css:10403
`.slideInBottom` moves (`animation-name: slideInBottom`) 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. (×2) — packages/platform/atoms/globals.css:10457, apps/web/styles/globals.css:334
`.slideInTop` moves (`animation-name: slideInTop`) 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. (×2) — packages/platform/atoms/globals.css:10473, apps/web/styles/globals.css:353
`.loader-inner` moves (`animation: loader-inner 2s infinite ease-in`) 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. (×2) — packages/embeds/embed-core/src/loader.css:49, apps/web/styles/globals.css:254
`.loader` moves (`animation: loader 2s infinite 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. (×2) — packages/embeds/embed-core/src/loader.css:60, apps/web/styles/globals.css:247
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.
Do you agree with this assessment?
AC7 · A11y enforcement4.0 / 10Weak✓ Tool-verified
Other · Accessibility — Whether accessibility is ENFORCED in the toolchain — an accessibility checker configured over the markup (an a11y lint rule set, e.g. eslint-plugin-jsx-a11y or vuejs-accessibility where the project lints JavaScript) and an automated accessibility assertion wired into tests or CI (axe/pa11y/Lighthouse or an equivalent) — on the Documented→Verified→Prevented ladder.
Method: Repo config/CI scan: an accessibility checker configured over the markup (an a11y lint rule set such as eslint-plugin-jsx-a11y / vuejs-accessibility where JavaScript is linted) and an automated accessibility assertion in tests or CI (axe/pa11y/Lighthouse or equivalent), graded on the Documented→Verified→Prevented rungs. Deterministic, presence/rung detection.
Coverage: Population: the repository's own tooling configuration — lint config, test and CI files — NOT the markup. It is read for a configured accessibility checker and an automated accessibility assertion (axe/pa11y/Lighthouse, or a native-toolkit equivalent), and it credits an INVOCATION, never a mention: a licence filename, an import comment or a doc reference earns no rung. Enforcement configured entirely outside the repository leaves no evidence here and cannot be credited.
No accessibility enforcement found — your Biome config enables no a11y rules and there's no axe/pa11y/Lighthouse in tests or CI. Start by turning on Biome's own a11y rule group to catch issues at author time. What was searched, so you can tell an absence from a miss: the 881 markup file(s) this pass actually assessed, the linter configuration checked in beside them, and this repository's test and CI files — matched by name against the accessibility checkers this dimension carries. An audit run outside the repository, a hosted scanner, or a check whose name is not one of those, is not seen here.
What to do
Enforce accessibility in the toolchain you already use: enable Biome's a11y rule group in your biome.json `linter.rules` (it is off whenever `recommended` is false and the group is unlisted), then assert with vitest-axe in tests, then gate axe/pa11y/Lighthouse in CI.
Other · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified. How each file's role is decided, because the split is only as good as that: a generated name or a build-output tree makes it Generated, a test project makes it Test, and otherwise the file's NAMESPACE and PATH words are matched against fixed vocabularies in a fixed ORDER — domain, then infrastructure, then application — so a file whose words hit two layers is counted under the earlier one. A production file matching none of them counts as application, so that share reads 'application or unclassified' rather than a measured application layer. Roles come from naming convention, never from what the code does. On this repository the split was taken from the source tree on disk rather than from a loaded .NET workspace, so a file's role is decided by its PATH segments alone — no declared namespace was available to add to the evidence — and generated output is excluded from the census entirely rather than counted as a generated share.
Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.
Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.
What to do
The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
Other · Architecture — Whether the project-reference graph is acyclic (cycles block independent build/deploy and signal eroding boundaries).
Method: Project reference cycles via elementary-DFS over real .csproj references, using the engine shared with D5/D7; cyclic versus acyclic. Exhaustive, deterministic.
Other · Architecture — Whether dependencies point inward (Domain ← Application ← Infrastructure/Web) — the clean-architecture dependency rule, checked across the project graph.
Method: Layer violations by name-segment inference (Domain/Core to Application to Infrastructure/Web) over the project-reference graph. Exhaustive over all projects, deterministic.
Other · Architecture — Whether the codebase has a recognisable, scale-appropriate structure (a named architectural style, or modular enough for its size) rather than being an ad-hoc ball of mud.
Method: Roslyn plus csproj analysis: architecture style detection (DDD, clean, vertical-slice, CQRS) and structure fitness for repo size. Deterministic.
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.
`BookingAuditProducerService` declares 18 required operations: `queueCreatedAudit`, `queueRescheduledAudit`, `queueAcceptedAudit`, `queueCancelledAudit`, `queueRescheduleRequestedAudit`, `queueAttendeeAddedAudit`, `queueNoShowUpdatedAudit`, `queueRejectedAudit`, `queueAttendeeRemovedAudit`, `queueReassignmentAudit`, `queueLocationChangedAudit`, `queueSeatBookedAudit`, `queueSeatRescheduledAudit`, `queueBulkAcceptedAudit`, `queueBulkCancelledAudit`, `queueBulkCreatedAudit`, `queueBulkRescheduledAudit`, `queueBulkRejectedAudit`. Counted over its REQUIRED operations — a method signature or a function-typed property with no `?`, once per signature; optional members and data properties are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — packages/features/booking-audit/lib/service/BookingAuditProducerService.interface.ts:32
`IBookingReportRepository` declares 18 required operations: `createReport`, `findAllReportedBookings`, `findGroupedReportedBookings`, `findReportsByIds`, `linkWatchlistToReport`, `updateReportStatus`, `bulkLinkWatchlistWithStatus`, `bulkLinkGlobalWatchlistWithSystemStatus`, `countPendingReports`, `updateSystemReportStatus`, `bulkUpdateSystemReportStatus`, `countSystemPendingReports`, `dismissReportsByEmail`, `dismissSystemReportsByEmail`, `findPendingReportsByEmail`, `findPendingReportsByDomain`, `findPendingSystemReportsByEmail`, `findPendingSystemReportsByDomain`. Counted over its REQUIRED operations — a method signature or a function-typed property with no `?`, once per signature; optional members and data properties are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — packages/features/bookingReport/repositories/IBookingReportRepository.ts:84
What to do
Split fat interfaces into focused role-interfaces so clients depend only on what they use.
Do you agree with this assessment?
C1 · Data Protection3.5 / 10Weak✓ Tool-verified
Other · Security — Whether sensitive data is encrypted at rest and in transit and keys are vaulted.
Method: Roslyn plus filesystem scan: encryption presence (EF ColumnEncryption, key-vault references, HTTPS enforcement) and key-derivation KDF detection. Deterministic.
What to do
Strengthen data-at-rest protection: vault your keys (AWS KMS / Secrets Manager, Azure Key Vault, GCP KMS / REDACTED Manager, HashiCorp Vault) and encrypt the most sensitive columns (typeorm-encrypted, prisma-field-encryption, mongoose-field-encryption or MongoDB CSFLE) — partial coverage still leaves gaps.
Enforce HTTPS (serve through https.createServer / NestJS httpsOptions, or redirect plain HTTP with express-sslify behind your TLS terminator) so data in transit is always encrypted.
Other · Security — Whether access is authorized by default — a framework authorization attribute/decorator or policy, or imperative guard methods (throw-on-violation) called from handlers.
Method: Roslyn scan: [Authorize] usage and authorization policies, plus imperative throw-on-violation guard methods detected via syntax. Deterministic.
Do you agree with this assessment?
C3 · Audit Trail7.5 / 10Strong✓ Tool-verified
Other · Security — Whether changes to sensitive data are recorded (who, what, when) for compliance + incident response.
An audit mechanism is present, but the trail is not yet complete — missing: an ORM write hook every change flows through (a TypeORM/MikroORM subscriber, a Sequelize or Mongoose hook, Prisma middleware or a query extension, or an event-store append), per-model coverage (@Audited, or a change-history plugin such as mongoose-history or sequelize-paper-trail applied to each model).
What to do
Back the audit convention with a structural mechanism: an ORM write hook (a TypeORM/MikroORM subscriber, a Sequelize or Mongoose hook, Prisma middleware) writing every sensitive change to an audit-log table, and apply it to each model that needs a who-changed-what trail.
Do you agree with this assessment?
C4 · Data Retention10.0 / 10Exemplary✓ Tool-verified
Other · Security — Whether data has a defined lifetime — retention periods, TTLs, cleanup jobs (storage limitation).
Method: Roslyn scan: retention/TTL configuration presence in schema; CascadeDelete detected but not scored as retention control. Deterministic, gated by PII presence.
Do you agree with this assessment?
DM10 · One transaction, one aggregate10.0 / 10Exemplary○ Nothing flagged
Other · Domain Modelling — Whether a single operation mutates more than one aggregate root. An aggregate is a consistency boundary, so saving two together fuses them into one — the second's invariants come to depend on the first's transaction, and the pair can no longer be separated. Reads of other aggregates are not counted.
Method: Neutral body surface (DDD-gated): every method body scanned for repository WRITE calls (Add/Update/Save/Remove/Delete/Insert/Store and their async forms), keyed on the ARGUMENT type rather than the repository type — three `IRepository<T>` writes collapse to one repository but are three distinct aggregates. Reads (Get/Find/Load/Query) are excluded, so loading another aggregate for context never counts. Score is offending methods over methods that write at all. Deterministic.
Other · Domain Modelling — Whether one domain rule is decided — or one measurement produced — in more than one place, rather than living on the type that owns it.
Method: Neutral body surface plus Roslyn (DDD-gated), two arms. DECISION (Roslyn only): a predicate over a domain type's members judged in two or more types, where none of those decisions live on the owning type — operands of comparisons and relational property patterns only, so a member merely passed as an argument is not judged. DERIVATION: a plain all-numeric carrier of ≥2 members, with no base type and exactly one constructor, CONSTRUCTED as the result of a method (returned or assigned, never inline as an argument) in two or more types other than its own — the same measurement produced twice, which centralising the judgement does not fix. DERIVATION runs on every language whose frontend declares the produced-or-passed fact per construction (Roslyn and the Java sidecar today); a target with only the derivation arm carries an engine gap naming the decision arm as not assessed, and a frontend that declares nothing keeps the dimension not measured rather than clean. Single-member rules, test code and generated code are out of population for both. Advisory.
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.
A shipped function's whole body still throws a "not implemented" error — generated scaffolding that was never completed. Implement it or remove the dead surface. (×33) — packages/app-store/alby/lib/PaymentService.ts:94, packages/app-store/alby/lib/PaymentService.ts:97, packages/app-store/alby/lib/PaymentService.ts:101, …
What to do
Finish or delete the functions that still throw "not implemented", and replace placeholder text before shipping.
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.
`checkLicense` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — apps/api/v2/src/modules/deployments/deployments.service.ts:15
`checkBookingRequiresAuthenticationSetting` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — apps/api/v2/src/platform/bookings/2024-08-13/services/bookings.service.ts:169
`hasRequiredBookingFieldsResponses` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — apps/api/v2/src/platform/bookings/2024-08-13/services/bookings.service.ts:217
`validateCustomEventNameInput` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — apps/api/v2/src/platform/event-types/event-types_2024_06_14/services/input-event-types.service.ts:519
`generateSwaggerForApp` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — apps/api/v2/src/swagger/generate-swagger.ts:21
`Page` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — apps/web/app/(booking-page-wrapper)/booking/dry-run-successful/page.tsx:15
`ServerPageWrapper` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. (×3) — apps/web/app/(use-page-wrapper)/auth/oauth2/authorize/page.tsx:15, apps/web/app/(use-page-wrapper)/auth/verify-email/page.tsx:15, apps/web/app/(use-page-wrapper)/more/page.tsx:15
`ServerPage` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. (×3) — apps/web/app/(use-page-wrapper)/availability/troubleshoot/page.tsx:15, apps/web/app/(use-page-wrapper)/upgrade/page.tsx:14, apps/web/app/(use-page-wrapper)/video/no-meeting-found/page.tsx:14
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. (×3) — apps/web/components/PageWrapperAppDir.tsx:29, apps/web/components/ui/UsernameAvailability/PremiumTextfield.tsx:247, apps/web/modules/settings/my-account/profile-view.tsx:631
The guard above `return opts.singular;` also returns `opts.singular`, so no input can make it matter. Implement the distinction that was intended, or delete the guard. — apps/web/components/integrations/SubHeadingTitleWithConnections.tsx:6
The guard above `return RemainingProviders;` also returns `RemainingProviders`, so no input can make it matter. Implement the distinction that was intended, or delete the guard. (×2) — apps/web/lib/app-providers-app-dir.tsx:120, apps/web/lib/app-providers.tsx:287
`mutate` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it. (×2) — apps/web/modules/data-table/components/segment/SaveFilterSegmentButton.tsx:30, apps/web/modules/data-table/components/segment/SaveFilterSegmentButton.tsx:34
`onCheckedChange` 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. — apps/web/modules/feature-flags/components/AssignFeatureSheet.tsx:176
The guard above `return null;` also returns `null`, so no input can make it matter. Implement the distinction that was intended, or delete the guard. (×2) — apps/web/modules/users/components/UserTable/ChangeUserRoleModal.tsx:8, apps/web/modules/users/components/UserTable/InviteMemberModal.tsx:25
`AlbyPaymentService` has 6 unfinished members out of 10 declared members (methods and accessors, whether or not each carries a body) — a scaffolded class that was never implemented. — packages/app-store/alby/lib/PaymentService.ts:17
`update` throws an exception whose message says it isn't finished — a not-implemented stub wearing an ordinary exception. Implement it or remove it. (×3) — packages/app-store/alby/lib/PaymentService.ts:94, packages/app-store/btcpayserver/lib/PaymentService.ts:154, packages/app-store/hitpay/lib/PaymentService.ts:200
`refund` throws an exception whose message says it isn't finished — a not-implemented stub wearing an ordinary exception. Implement it or remove it. — packages/app-store/alby/lib/PaymentService.ts:97
`collectCard` throws an exception whose message says it isn't finished — a not-implemented stub wearing an ordinary exception. Implement it or remove it. (×2) — packages/app-store/alby/lib/PaymentService.ts:101, packages/app-store/btcpayserver/lib/PaymentService.ts:161
`chargeCard` throws an exception whose message says it isn't finished — a not-implemented stub wearing an ordinary exception. Implement it or remove it. (×2) — packages/app-store/alby/lib/PaymentService.ts:109, packages/app-store/btcpayserver/lib/PaymentService.ts:170
`getPaymentPaidStatus` throws an exception whose message says it isn't finished — a not-implemented stub wearing an ordinary exception. Implement it or remove it. (×2) — packages/app-store/alby/lib/PaymentService.ts:115, packages/app-store/btcpayserver/lib/PaymentService.ts:177
`getPaymentDetails` throws an exception whose message says it isn't finished — a not-implemented stub wearing an ordinary exception. Implement it or remove it. (×2) — packages/app-store/alby/lib/PaymentService.ts:118, packages/app-store/btcpayserver/lib/PaymentService.ts:181
`getFirstDelegationConferencingCredential` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in. — packages/app-store/delegationCredential.ts:138
`getFirstDelegationConferencingCredentialAppLocation` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in. — packages/app-store/delegationCredential.ts:144
`findUniqueDelegationCalendarCredential` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in. — packages/app-store/delegationCredential.ts:150
`HitPayPaymentService` has 6 unfinished members out of 10 declared members (methods and accessors, whether or not each carries a body) — a scaffolded class that was never implemented. — packages/app-store/hitpay/lib/PaymentService.ts:26
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.
Maturity · Maturity — Whether the repo and its projects have a README, and whether it's substantive and current.
Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.
What to do
Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
Add a README to the 90 of 118 project(s) that lack one — worth up to 1.5 pts.
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.
3 ADR-shaped document(s) detected by content — `SPEC-WORKFLOW.md`, `specs/_templates/decisions.md`, `specs/cancellation-reason-requirement/decisions.md`. They are not under a conventional ADR folder (docs/adr/) and are not named NNNN-title.md, and this check found them by their decision signature rather than by where they live — so a reader who does not already know these paths has no route to them. Detected by content signature only: records kept outside the repository, or written without a Status/Decision/Consequences shape, are not visible to this check and are not counted here.
What to do
Move ADRs under docs/adr/ (or docs/adrs/) and name them NNNN-title.md so they're easy to find.
Maturity · Maturity — Whether the README actually describes the code that exists (LLM-judged, advisory).
Method: Judged by language model at low temperature: README accuracy versus actual projects, within a disclosed tolerance. Advisory, not a measured number.
agents/README.md links to `rules/patterns-workflow-triggers.md`, but `agents/rules/patterns-workflow-triggers.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, 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. — agents/README.md:66
packages/features/booking-audit/README.md names UUID 7, but the manifest declares `uuid` 8.3.2. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, 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. — packages/features/booking-audit/README.md:25
specs/_templates/docs/README.md links to `./screenshots/step-1.png`, but `specs/_templates/docs/screenshots/step-1.png` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, 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. — specs/_templates/docs/README.md:13
specs/_templates/docs/README.md links to `./screenshots/step-2.png`, but `specs/_templates/docs/screenshots/step-2.png` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, 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. — specs/_templates/docs/README.md:19
What to do
Reconcile the README with reality: agents/README.md links to `rules/patterns-workflow-triggers.md`, but `agents/rules/patterns-workflow-triggers.md` does not exist; packages/features/booking-audit/README.md names UUID 7, but the manifest declares `uuid` 8.3.2; specs/_templates/docs/README.md links to `./screenshots/step-1.png`, but `specs/_templates/docs/screenshots/step-1.png` does not exist; specs/_templates/docs/README.md links to `./screenshots/step-2.png`, but `specs/_templates/docs/screenshots/step-2.png` does not exist.
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.
Do you agree with this assessment?
P10 · Library API & versioning10.0 / 10Exemplary○ Nothing flagged
Readiness · Readiness — For a library: a deliberate (small) public API surface and explicit semantic versioning so consumers can depend on it safely.
Method: Roslyn scan: public API surface area and semantic-versioning markers (SemVer attributes, changelog entries) for libraries; off .NET, a library is the ecosystem's publication act (an npm package that is not private and names an entry point, a PyPI distribution with a build system, a Rust library crate, a Maven/Gradle module that publishes, a Go module with no package main, a gemspec, a Composer library, a SwiftPM library product, a pub.dev or Hex package), its surface is the share of types the language model records as public (Rust, Swift, Java, Kotlin, Go, Dart; not measured where the model records no type visibility or, as in TypeScript, only module-level export), and its version is read from the manifest, a semver CHANGELOG, release tooling or semver git tags. Exhaustive, deterministic.
Do you agree with this assessment?
P2 · Observability6.6 / 10Adequate✓ Tool-verified
Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.
Only 42/48 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `apps/api`, `apps/docs`, `example-apps/credential-sync`, `packages/app-store-cli`, `packages/platform/examples/base` and 1 more.
`apps/api/v2/src/swagger/copy-swagger-module.ts` reports through `console.*` at line 23 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — apps/api/v2/src/swagger/copy-swagger-module.ts:23
`apps/api/v2/src/swagger/generate-swagger-script.ts` reports through `console.*` at line 9 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — apps/api/v2/src/swagger/generate-swagger-script.ts:9
`apps/api/v2/src/swagger/generate-swagger-script.ts` reports through `console.*` at line 13 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — apps/api/v2/src/swagger/generate-swagger-script.ts:13
`apps/api/v2/src/swagger/generate-swagger-script.ts` reports through `console.*` at line 24 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — apps/api/v2/src/swagger/generate-swagger-script.ts:24
`apps/api/v2/src/modules/stripe/utils/getReturnToValueFromQueryState.ts` reports through `console.*` at line 6 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — apps/api/v2/src/modules/stripe/utils/getReturnToValueFromQueryState.ts:6
`apps/api/v2/src/modules/stripe/utils/getReturnToValueFromQueryState.ts` reports through `console.*` at line 16 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — apps/api/v2/src/modules/stripe/utils/getReturnToValueFromQueryState.ts:16
`apps/api/v2/src/modules/stripe/controllers/stripe.controller.ts` 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. — apps/api/v2/src/modules/stripe/controllers/stripe.controller.ts:142
`apps/api/v2/src/modules/slots/slots-2024-04-15/workers/slots.worker.ts` reports through `console.*` at line 30 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — apps/api/v2/src/modules/slots/slots-2024-04-15/workers/slots.worker.ts:30
`apps/web/cron-tester.ts` reports through `console.*` at line 16 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — apps/web/cron-tester.ts:16
`apps/web/cron-tester.ts` reports through `console.*` at line 20 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — apps/web/cron-tester.ts:20
`apps/web/cron-tester.ts` reports through `console.*` at line 36 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — apps/web/cron-tester.ts:36
`apps/web/getNextjsOrgRewriteConfig.ts` reports through `console.*` at line 40 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — apps/web/getNextjsOrgRewriteConfig.ts:40
`apps/web/server/lib/auth/login/getServerSideProps.tsx` reports through `console.*` at line 65 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — apps/web/server/lib/auth/login/getServerSideProps.tsx:65
`apps/web/public/service-worker.js` reports through `console.*` at line 12 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — apps/web/public/service-worker.js:12
`apps/web/public/service-worker.js` reports through `console.*` at line 53 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — apps/web/public/service-worker.js:53
`apps/web/public/service-worker.js` reports through `console.*` at line 56 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — apps/web/public/service-worker.js:56
`apps/web/public/service-worker.js` reports through `console.*` at line 58 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — apps/web/public/service-worker.js:58
`apps/web/public/service-worker.js` reports through `console.*` at line 100 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — apps/web/public/service-worker.js:100
`apps/web/public/service-worker.js` reports through `console.*` at line 104 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — apps/web/public/service-worker.js:104
`apps/web/playwright/lib/next-server.ts` reports through `console.*` at line 32 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — apps/web/playwright/lib/next-server.ts:32
`apps/web/playwright/lib/testUtils.ts` reports through `console.*` at line 335 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — apps/web/playwright/lib/testUtils.ts:335
`apps/web/playwright/lib/testUtils.ts` reports through `console.*` at line 470 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — apps/web/playwright/lib/testUtils.ts:470
`apps/web/playwright/lib/testUtils.ts` reports through `console.*` at line 476 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — apps/web/playwright/lib/testUtils.ts:476
`REDACTED` reports through `console.*` at line 83 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — REDACTED:83
`apps/web/modules/signup-view.tsx` reports through `console.*` at line 277 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — apps/web/modules/signup-view.tsx:277
`REDACTED` 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. — REDACTED:144
`REDACTED` reports through `console.*` at line 152 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — REDACTED:152
`apps/web/modules/users/views/users-add-view.tsx` reports through `console.*` at line 25 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — apps/web/modules/users/views/users-add-view.tsx:25
`apps/web/modules/users/views/users-edit-view.tsx` reports through `console.*` at line 42 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — apps/web/modules/users/views/users-edit-view.tsx:42
`apps/web/modules/users/components/UsersTable.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. — apps/web/modules/users/components/UsersTable.tsx:52
`apps/web/modules/onboarding/hooks/useSubmitOnboarding.ts` reports through `console.*` at line 128 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — apps/web/modules/onboarding/hooks/useSubmitOnboarding.ts:128
`apps/web/modules/onboarding/hooks/useSubmitPersonalOnboarding.ts` reports through `console.*` at line 56 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — apps/web/modules/onboarding/hooks/useSubmitPersonalOnboarding.ts:56
`apps/web/modules/onboarding/hooks/useSubmitPersonalOnboarding.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. — apps/web/modules/onboarding/hooks/useSubmitPersonalOnboarding.ts:84
`apps/web/modules/notifications/components/WebPushContext.tsx` reports through `console.*` at line 48 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — apps/web/modules/notifications/components/WebPushContext.tsx:48
`apps/web/modules/notifications/components/WebPushContext.tsx` reports through `console.*` at line 73 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — apps/web/modules/notifications/components/WebPushContext.tsx:73
`apps/web/modules/notifications/components/WebPushContext.tsx` reports through `console.*` at line 100 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — apps/web/modules/notifications/components/WebPushContext.tsx:100
`REDACTED` reports through `console.*` at line 121 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — REDACTED:121
`apps/web/modules/event-types/views/event-types-listing-view.tsx` reports through `console.*` at line 305 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — apps/web/modules/event-types/views/event-types-listing-view.tsx:305
`apps/web/modules/event-types/views/event-types-listing-view.tsx` reports through `console.*` at line 360 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — apps/web/modules/event-types/views/event-types-listing-view.tsx:360
What to do
Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
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.
Consider OpenTelemetry tracing/metrics (@opentelemetry/sdk-node) and a health-check endpoint (@godaddy/terminus or a /health route) for operability.
Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).
Method: Filesystem scan: SAST configuration, dependency-update automation, secret scanning, and a benchmark harness or benchmark step — in this repository's own ecosystem. Exhaustive, deterministic.
No static application security testing detected. For this repository's stack, add CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security as a CI step. What was searched, so you can tell an absence from a miss: the 126685 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
What to do
Add a SAST step to CI running what this repository's stack ships: CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security — so a security regression fails the build instead of landing.
Enable Dependabot/Renovate or a dependency-review gate.
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
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.
Do you agree with this assessment?
P5 · DR & Backup0.0 / 10Critical✓ 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.
A persistence guard (data volume / purge-protection) was found, but no backup, geo-recovery or RTO/RPO controls were evidenced — a volume that survives a container recreate is not a tested restore from catastrophic loss.
What to do
Codify backups + geo-recovery in IaC and document RTO/RPO and the restore procedure — a persistence guard alone is not disaster recovery.
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.
`fetch(` 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. (×5) — apps/api/v2/src/modules/conferencing/services/office365-video.service.ts:81, apps/api/v2/src/modules/conferencing/services/office365-video.service.ts:95, apps/api/v2/src/modules/conferencing/services/zoom-video.service.ts:65, …
What to do
Bound every outbound call: pass `signal: AbortSignal.timeout(ms)` to `fetch`, set `timeout` on the axios instance (`axios.create({ timeout })`), and add retries with back-off (`axios-retry`, `p-retry`) and a breaker (`opossum`, `cockatiel`) around dependencies that fail.
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.
Readiness · Performance — Whether asynchronous code stays responsive — it avoids sync-over-async blocking (a .NET .Wait()/.GetAwaiter().GetResult(), a time.sleep or blocking HTTP call inside a Python coroutine, a *Sync call inside an async JavaScript function, block_on inside a Rust async fn, runBlocking inside a Kotlin suspend function, block() inside a Reactor publisher) that stalls a thread or event loop and risks deadlock, and, where the code is a reusable library on .NET, awaits with ConfigureAwait(false) so it never captures and stalls its caller's context.
Method: Production-source scan: sync-over-async blocking counted everywhere — .Wait()/.GetAwaiter().GetResult() in .NET; off .NET, read from the language model, a blocking call inside an async function (Python, TS/JS, Rust, Kotlin, Swift, Dart) or inside a Java method returning a Reactor Mono/Flux or a Scala method returning a Future or effect — and, for a .NET library with ≥5 awaits, the share of awaits using ConfigureAwait(false). Deterministic, syntax/text detection.
`fs.existsSync` in `generateSwaggerForApp` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — apps/api/v2/src/swagger/generate-swagger.ts:32
`fs.unlinkSync` in `generateSwaggerForApp` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — apps/api/v2/src/swagger/generate-swagger.ts:33
`fs.writeFileSync` in `generateSwaggerForApp` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — apps/api/v2/src/swagger/generate-swagger.ts:34
`spawnSync` in `generateSwaggerForApp` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — apps/api/v2/src/swagger/generate-swagger.ts:35
`fs.readFileSync` in `getStaticProps` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — apps/web/lib/apps/[slug]/getStaticProps.ts:99
`execSync` in `create` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. (×4) — packages/app-store-cli/src/core.ts:78, packages/app-store-cli/src/core.ts:79, packages/app-store-cli/src/core.ts:92, …
`fs.readFileSync` in `create` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. (×2) — packages/app-store-cli/src/core.ts:120, packages/app-store-cli/src/core.ts:140
`fs.writeFileSync` in `create` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. (×2) — packages/app-store-cli/src/core.ts:136, packages/app-store-cli/src/core.ts:137
`execSync` in `anonymous function` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/app-store-cli/src/core.ts:151
`execSync` in `generateAppFiles` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/app-store-cli/src/core.ts:156
`readFileSync` in `sendVerificationRequest` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/features/auth/lib/sendVerificationRequest.ts:25
`fs.readFileSync` in `main` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/platform/libraries/scripts/prepublish.js:53
`fs.writeFileSync` in `main` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/platform/libraries/scripts/prepublish.js:56
What to do
TypeScript/JavaScript: use the promise APIs (fs/promises, a promisified child_process.execFile, the async zlib/crypto functions) and await them instead of the *Sync variants.
Do you agree with this assessment?
R1 · Type Safety10.0 / 10Exemplary✓ Tool-verified
React / JS · Code Health — How much of the frontend is typed TypeScript vs untyped JavaScript.
Method: Frontend file inventory: the share of typed TypeScript vs untyped JavaScript across the source tree. Deterministic, exhaustive over frontend files.
React / JS · Code Health — Near-exact copy-pasted blocks of substantial extent across the frontend (the D4 clone algorithm over JS/TS tokens, D-386): 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. Deterministic.
167 duplicated blocks under packages/app-store/ have copies in at least two of the sibling directories _components, _lib, _utils, alby, applecalendar, attio (+77 more sibling(s) not listed) — 139 of them are reported below, and 28 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 167 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 167 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 167 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. — packages/app-store/_components/crm/WriteToObjectSettings.tsx:4
114 duplicated blocks under the repository root have copies in at least two of the sibling directories apps, packages, scripts — 69 of them are reported below, and 45 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 114 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 114 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 114 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — apps/api/v2/src/modules/atoms/services/event-types-atom.service.ts:196
80 duplicated blocks under packages/ have copies in at least two of the sibling directories app-store, emails, embeds, features, lib, platform (+4 more sibling(s) not listed) — 48 of them are reported below, and 32 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 80 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 80 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 80 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. — packages/features/calendars/components/DestinationCalendarSelector.tsx:156
62 duplicated blocks under packages/features/ have copies in at least two of the sibling directories availability, booking-audit, bookingReference, bookings, busyTimes, calendars (+18 more sibling(s) not listed) — 17 of them are reported below, and 45 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 62 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 62 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 62 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. — packages/features/bookingReference/repositories/BookingReferenceRepository.integration-test.ts:29
47 duplicated blocks under apps/api/v2/src/ have copies in at least two of the sibling directories lib, middleware, modules, platform — 19 of them are reported below, and 28 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 47 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 47 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 47 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — apps/api/v2/src/modules/teams/event-types/services/output-team-event-types.service.ts:26
35 duplicated blocks under apps/api/v2/src/modules/ have copies in at least two of the sibling directories api-keys, atoms, auth, cal-unified-calendars, conferencing, deployments (+11 more sibling(s) not listed) — 18 of them are reported below, and 17 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 35 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 35 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 35 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. — apps/api/v2/src/modules/destination-calendars/outputs/destination-calendars.output.ts:7
26 duplicated blocks under packages/trpc/server/routers/viewer/ have copies in at least two of the sibling directories admin, apiKeys, apps, auth, availability, bookings (+15 more sibling(s) not listed) — 13 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 26 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 26 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 26 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. — packages/trpc/server/routers/viewer/apps/_router.tsx:51
24 duplicated blocks under apps/api/v2/src/platform/ have copies in at least two of the sibling directories bookings, calendars, event-types, event-types-private-links, gcal, me (+1 more sibling(s) not listed) — 11 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 24 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 24 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 24 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. — apps/api/v2/src/platform/bookings/2024-04-15/outputs/get-bookings.output.ts:30
24 duplicated blocks under apps/web/modules/ have copies in at least two of the sibling directories apps, auth, blocklist, bookings, calendar-view, data-table (+8 more sibling(s) not listed) — 15 of them are reported below, and 9 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 24 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 24 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 24 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. — apps/web/modules/settings/my-account/general-view.tsx:85
22 duplicated blocks under apps/web/ have copies in at least two of the sibling directories app, components, lib, modules — 15 of them are reported below, and 7 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 22 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 22 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 22 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. — apps/web/components/getting-started/steps-views/UserProfile.tsx:130
15 duplicated blocks under packages/platform/atoms/ have copies in at least two of the sibling directories availability, connect, event-types, hooks, list-schedules — 11 of them are reported below, and 4 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 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. — packages/platform/atoms/connect/conferencing-apps/hooks/useConnect.ts:32
14 duplicated blocks under apps/web/app/(use-page-wrapper)/ have copies in at least two of the sibling directories (main-nav), apps, auth, availability, event-types, getting-started (+5 more sibling(s) not listed) — 9 of them are reported below, and 5 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 14 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 14 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 14 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — apps/web/app/(use-page-wrapper)/availability/[schedule]/page.tsx:10
13 duplicated blocks under apps/web/components/apps/ have copies in at least two of the sibling directories alby, applecalendar, btcpayserver, caldavcalendar, exchange2013calendar, exchange2016calendar (+5 more sibling(s) not listed) — 11 of them are reported below, and 2 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 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. — apps/web/components/apps/btcpayserver/Setup.tsx:33
10 duplicated blocks under apps/api/v2/src/modules/auth/decorators/ have copies in at least two of the sibling directories get-membership, get-optional-user, get-org, get-team, get-user — 1 of them are reported below, and 9 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. — apps/api/v2/src/modules/auth/decorators/get-optional-user/get-optional-user.decorator.ts:7
9 duplicated blocks under packages/platform/atoms/hooks/ have copies in at least two of the sibling directories bookings, calendars, connect, organizations, schedules, stripe — 4 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 9 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 9 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 9 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — packages/platform/atoms/hooks/calendars/useDeleteCalendarCredentials.ts:49
8 duplicated blocks under packages/trpc/server/routers/ have copies in at least two of the sibling directories loggedInViewer, publicViewer, viewer — 2 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 8 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 8 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 8 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — packages/trpc/server/routers/loggedInViewer/_router.tsx:35
7 duplicated blocks under packages/features/webhooks/lib/ have copies in at least two of the sibling directories dto, factory, infrastructure, interface, service, types — 2 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 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. — packages/features/webhooks/lib/dto/types.ts:220
7 duplicated blocks under packages/platform/types/event-types/event-types_2024_06_14/ have copies in at least two of the sibling directories inputs, outputs — 4 of them are reported below, and 3 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 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. — packages/platform/types/event-types/event-types_2024_06_14/inputs/locations.input.ts:244
5 duplicated blocks under apps/web/modules/settings/ have copies in at least two of the sibling directories admin, developer, my-account, oauth — 3 of them are reported below, and 2 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 5 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 5 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 5 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — apps/web/modules/settings/admin/oauth-clients-admin-view.tsx:18
5 duplicated blocks under packages/platform/types/ have copies in at least two of the sibling directories bookings, event-types, slots — 3 of them are reported below, and 2 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 5 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 5 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 5 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — packages/platform/types/bookings/2024-08-13/inputs/location.input.ts:16
packages/platform/types/event-types/event-types_2024_06_14/inputs/create-event-type.input.ts:209 · packages/platform/types/event-types/event-types_2024_06_14/inputs/update-event-type.input.ts:142 — the two spans are one implementation copied and then locally edited — 1969 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. — packages/platform/types/event-types/event-types_2024_06_14/inputs/create-event-type.input.ts:209
packages/app-store/_components/crm/WriteToObjectSettings.tsx:4 · packages/app-store/salesforce/components/components/WriteToObjectSettings.tsx:4 — these 2 files are line-for-line copies of one another — 306 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. — packages/app-store/_components/crm/WriteToObjectSettings.tsx:4
packages/app-store/feishucalendar/lib/CalendarService.ts:1 · packages/app-store/larkcalendar/lib/CalendarService.ts:1 — these 2 files are line-for-line copies of one another — 255 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. — packages/app-store/feishucalendar/lib/CalendarService.ts:1
packages/coss-ui/src/components/autocomplete.tsx:14 · packages/coss-ui/src/components/combobox.tsx:57 — 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. — packages/coss-ui/src/components/autocomplete.tsx:14
packages/features/eventtypes/repositories/eventTypeRepository.ts:541 · packages/features/eventtypes/repositories/eventTypeRepository.ts:821 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/features/eventtypes/repositories/eventTypeRepository.ts:541
apps/web/components/apps/btcpayserver/Setup.tsx:33 · apps/web/components/apps/hitpay/Setup.tsx:29 — the two spans are one implementation copied and then locally edited — 988 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. — apps/web/components/apps/btcpayserver/Setup.tsx:33
scripts/seed-performance-testing.ts:72 · REDACTED:732 — the 2 copies are spread across 2 files, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases. — scripts/seed-performance-testing.ts:72
apps/web/components/ui/UsernameAvailability/PremiumTextfield.tsx:31 · apps/web/components/ui/UsernameAvailability/UsernameTextfield.tsx:22 — the two spans are one implementation copied and then locally edited — 743 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. — apps/web/components/ui/UsernameAvailability/PremiumTextfield.tsx:31
packages/ui/components/image-uploader/BannerUploader.tsx:26 · packages/ui/components/image-uploader/ImageUploader.tsx:28 — the two spans are one implementation copied and then locally edited — 816 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. — packages/ui/components/image-uploader/BannerUploader.tsx:26
apps/web/components/apps/alby/AlbyPaymentComponent.tsx:16 · apps/web/components/apps/btcpayserver/BtcpayPaymentComponent.tsx:14 — the two spans are one implementation copied and then locally edited — 798 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. — apps/web/components/apps/alby/AlbyPaymentComponent.tsx:16
apps/web/components/security/EnableTwoFactorModal.tsx:31 · apps/web/components/settings/EnableTwoFactorModal.tsx:35 — the two spans are one implementation copied and then locally edited — 913 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. — apps/web/components/security/EnableTwoFactorModal.tsx:31
packages/app-store/exchange2013calendar/lib/CalendarService.ts:21 · packages/app-store/exchange2016calendar/lib/CalendarService.ts:21 — these 2 files are line-for-line copies of one another — 140 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. — packages/app-store/exchange2013calendar/lib/CalendarService.ts:21
packages/coss-ui/src/components/dialog.tsx:11 · packages/coss-ui/src/components/sheet.tsx:9 — the two spans are one implementation copied and then locally edited — 532 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. — packages/coss-ui/src/components/dialog.tsx:11
packages/app-store/vital/lib/reschedule.ts:1 · packages/app-store/wipemycalother/lib/reschedule.ts:1 — these 2 files are line-for-line copies of one another — 130 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. — packages/app-store/vital/lib/reschedule.ts:1
packages/app-store/btcpayserver/components/KeyInput.tsx:3 · packages/app-store/hitpay/components/KeyInput.tsx:3 — these 2 files are line-for-line copies of one another — 120 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. — packages/app-store/btcpayserver/components/KeyInput.tsx:3
packages/app-store/feishucalendar/types/FeishuCalendar.ts:2 · packages/app-store/larkcalendar/types/LarkCalendar.ts:2 — these 2 files are line-for-line copies of one another — 110 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. — packages/app-store/feishucalendar/types/FeishuCalendar.ts:2
apps/web/modules/apps/components/ConferencingAppsViewWebWrapper.tsx:72 · apps/web/modules/apps/installed/[category]/installed-category-view.tsx:64 — the two spans are one implementation copied and then locally edited — 476 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. — apps/web/modules/apps/components/ConferencingAppsViewWebWrapper.tsx:72
packages/features/bookingReference/repositories/BookingReferenceRepository.integration-test.ts:29 · packages/features/credentials/handleDeleteCredential.integration-test.ts:69 — the two spans are one implementation copied and then locally edited — 504 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. — packages/features/bookingReference/repositories/BookingReferenceRepository.integration-test.ts:29
apps/api/v2/src/platform/event-types/event-types_2024_04_15/services/event-types.service.ts:58 · apps/api/v2/src/platform/event-types/event-types_2024_06_14/services/event-types.service.ts:166 — the two spans are one implementation copied and then locally edited — 621 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. — apps/api/v2/src/platform/event-types/event-types_2024_04_15/services/event-types.service.ts:58
packages/app-store/feishucalendar/lib/AppAccessToken.ts:1 · packages/app-store/larkcalendar/lib/AppAccessToken.ts:1 — these 2 files are line-for-line copies of one another — 95 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. — packages/app-store/feishucalendar/lib/AppAccessToken.ts: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.
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.
apps/web/app/api/defaultResponderForAppDir.ts:2 imports next/dist/server/api-utils, 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. — apps/web/app/api/defaultResponderForAppDir.ts:2
apps/web/app/icons/page.tsx:9 reaches into another package with a relative path (../../../../packages/ui/components/icon/icon-list.mjs) — import the package by name instead. — apps/web/app/icons/page.tsx:9
apps/web/components/apps/DestinationCalendarSettingsWebWrapper.tsx:9 reaches into another package with a relative path (../../../../packages/platform/atoms/destination-calendar/DestinationCalendar) — import the package by name instead. — apps/web/components/apps/DestinationCalendarSettingsWebWrapper.tsx:9
apps/web/components/apps/DestinationCalendarSettingsWebWrapper.tsx:10 reaches into another package with a relative path (../../../../packages/platform/atoms/src/components/atoms-wrapper) — import the package by name instead. — apps/web/components/apps/DestinationCalendarSettingsWebWrapper.tsx:10
apps/web/modules/auth/setup-view.tsx:11 imports @calcom/ui/components/form/wizard/WizardForm, which the target package's REDACTED `exports` does not declare — use a declared entry or declare the subpath. — apps/web/modules/auth/setup-view.tsx:11
apps/web/modules/bookings/components/EventMeta.tsx:20 reaches into another package with a relative path (../../../../../i18n.json) — import the package by name instead. — apps/web/modules/bookings/components/EventMeta.tsx:20
apps/web/modules/event-types/components/AddVerifiedEmail.tsx:11 reaches into another package with a relative path (../../../../../packages/platform/atoms/event-types/hooks/useAddVerifiedEmail) — import the package by name instead. — apps/web/modules/event-types/components/AddVerifiedEmail.tsx:11
apps/web/modules/event-types/components/AddVerifiedEmail.tsx:12 reaches into another package with a relative path (../../../../../packages/platform/atoms/event-types/hooks/useGetVerifiedEmails) — import the package by name instead. — apps/web/modules/event-types/components/AddVerifiedEmail.tsx:12
apps/web/modules/event-types/components/AddVerifiedEmail.tsx:13 reaches into another package with a relative path (../../../../../packages/platform/atoms/hooks/useVerifyCode) — import the package by name instead. — apps/web/modules/event-types/components/AddVerifiedEmail.tsx:13
apps/web/modules/event-types/components/AddVerifiedEmail.tsx:14 reaches into another package with a relative path (../../../../../packages/platform/atoms/hooks/useVerifyEmail) — import the package by name instead. — apps/web/modules/event-types/components/AddVerifiedEmail.tsx:14
apps/web/modules/event-types/components/EventTypeLayout.tsx:31 reaches into another package with a relative path (../../../../../packages/platform/atoms/src/components/ui/shell) — import the package by name instead. — apps/web/modules/event-types/components/EventTypeLayout.tsx:31
packages/app-store/AppDependencyComponent.tsx:6 imports @coss/ui/icons, a package this repository publishes, but this package's own REDACTED does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies. — packages/app-store/AppDependencyComponent.tsx:6
packages/app-store/_appRegistry.ts:6 imports @calcom/prisma, a package this repository publishes, but this package's own REDACTED does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies. — packages/app-store/_appRegistry.ts:6
packages/app-store/_appRegistry.ts:7 imports @calcom/prisma/zod-utils, a package this repository publishes, but this package's own REDACTED does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies. — packages/app-store/_appRegistry.ts:7
packages/app-store/_components/AppCard.tsx:6 imports @calcom/atoms/hooks/useIsPlatform, a package this repository publishes, but this package's own REDACTED does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies. — packages/app-store/_components/AppCard.tsx:6
packages/app-store/_pages/setup/_getServerSideProps.tsx:4 reaches into another package with a relative path (../../alby/pages/setup/_getServerSideProps) — import the package by name instead. — packages/app-store/_pages/setup/_getServerSideProps.tsx:4
packages/app-store/_pages/setup/_getServerSideProps.tsx:5 reaches into another package with a relative path (../../make/pages/setup/_getServerSideProps) — import the package by name instead. — packages/app-store/_pages/setup/_getServerSideProps.tsx:5
packages/app-store/_pages/setup/_getServerSideProps.tsx:6 reaches into another package with a relative path (../../stripepayment/pages/setup/_getServerSideProps) — import the package by name instead. — packages/app-store/_pages/setup/_getServerSideProps.tsx:6
packages/app-store/_pages/setup/_getServerSideProps.tsx:7 reaches into another package with a relative path (../../hitpay/pages/setup/_getServerSideProps) — import the package by name instead. — packages/app-store/_pages/setup/_getServerSideProps.tsx:7
packages/app-store/_pages/setup/_getServerSideProps.tsx:8 reaches into another package with a relative path (../../btcpayserver/pages/setup/_getServerSideProps) — import the package by name instead. — packages/app-store/_pages/setup/_getServerSideProps.tsx:8
packages/app-store/_utils/bulkUpdateEventsToDefaultLocation.ts:3 imports @calcom/prisma/zod-utils, a package this repository publishes, but this package's own REDACTED does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies. — packages/app-store/_utils/bulkUpdateEventsToDefaultLocation.ts:3
packages/app-store/_utils/bulkUpdateTeamEventsToDefaultLocation.ts:2 imports @calcom/prisma/zod-utils, a package this repository publishes, but this package's own REDACTED does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies. — packages/app-store/_utils/bulkUpdateTeamEventsToDefaultLocation.ts:2
packages/app-store/_utils/calendars/processExternalId.ts:3 reaches into another package with a relative path (../../office365calendar) — import the package by name instead. — packages/app-store/_utils/calendars/processExternalId.ts:3
packages/app-store/_utils/findValidApiKey.ts:2 imports @calcom/prisma, a package this repository publishes, but this package's own REDACTED does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies. — packages/app-store/_utils/findValidApiKey.ts:2
packages/app-store/_utils/getAppKeysFromSlug.ts:1 imports @calcom/prisma, a package this repository publishes, but this package's own REDACTED does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies. — packages/app-store/_utils/getAppKeysFromSlug.ts:1
packages/app-store/_utils/getBulkEventTypes.ts:1 imports @calcom/prisma, a package this repository publishes, but this package's own REDACTED does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies. — packages/app-store/_utils/getBulkEventTypes.ts:1
packages/app-store/_utils/getBulkEventTypes.ts:2 imports @calcom/prisma/zod-utils, a package this repository publishes, but this package's own REDACTED does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies. — packages/app-store/_utils/getBulkEventTypes.ts:2
packages/app-store/_utils/getCalendar.ts:9 imports @calcom/prisma, a package this repository publishes, but this package's own REDACTED does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies. — packages/app-store/_utils/getCalendar.ts:9
packages/app-store/_utils/getConnectedApps.ts:7 imports @calcom/prisma/selects/credential, a package this repository publishes, but this package's own REDACTED does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies. — packages/app-store/_utils/getConnectedApps.ts:7
packages/app-store/_utils/getDefaultLocations.ts:5 imports @calcom/prisma/zod-utils, a package this repository publishes, but this package's own REDACTED does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies. — packages/app-store/_utils/getDefaultLocations.ts:5
packages/app-store/_utils/getEnabledAppsFromCredentials.ts:3 imports @calcom/prisma, a package this repository publishes, but this package's own REDACTED does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies. — packages/app-store/_utils/getEnabledAppsFromCredentials.ts:3
packages/app-store/_utils/installation.ts:3 imports @calcom/prisma, a package this repository publishes, but this package's own REDACTED does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies. — packages/app-store/_utils/installation.ts:3
packages/app-store/_utils/invalidateCredential.ts:1 imports @calcom/prisma, a package this repository publishes, but this package's own REDACTED does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies. — packages/app-store/_utils/invalidateCredential.ts:1
packages/app-store/_utils/oauth/createOAuthAppCredential.ts:4 imports @calcom/prisma, a package this repository publishes, but this package's own REDACTED does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies. — packages/app-store/_utils/oauth/createOAuthAppCredential.ts:4
packages/app-store/_utils/oauth/markTokenAsExpired.ts:1 imports @calcom/prisma, a package this repository publishes, but this package's own REDACTED does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies. — packages/app-store/_utils/oauth/markTokenAsExpired.ts:1
packages/app-store/_utils/oauth/updateProfilePhotoGoogle.ts:8 imports @calcom/prisma, a package this repository publishes, but this package's own REDACTED does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies. — packages/app-store/_utils/oauth/updateProfilePhotoGoogle.ts:8
packages/app-store/_utils/oauth/updateTokenObject.ts:5 imports @calcom/prisma, a package this repository publishes, but this package's own REDACTED does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies. — packages/app-store/_utils/oauth/updateTokenObject.ts:5
packages/app-store/_utils/payments/getPaymentAppData.ts:6 reaches into another package with a relative path (../../stripepayment/zod) — import the package by name instead. — packages/app-store/_utils/payments/getPaymentAppData.ts:6
packages/app-store/_utils/payments/handlePaymentSuccess.ts:2 imports @calcom/emails/email-manager, a package this repository publishes, but this package's own REDACTED does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies. — packages/app-store/_utils/payments/handlePaymentSuccess.ts:2
packages/app-store/_utils/payments/handlePaymentSuccess.ts:22 imports @calcom/prisma, a package this repository publishes, but this package's own REDACTED does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies. — packages/app-store/_utils/payments/handlePaymentSuccess.ts:22
What to do
Fix the listed violations: declare the workspace packages these files import in the importing package's own REDACTED dependencies (1493 rows) — those imports are already bare package specifiers, so the import statements do not change, only the manifest; import through the target package's declared public entry rather than a deep path into its internals or a relative path into its directory (685 rows); move the shared test helper into a source directory production code may depend on (4 rows).
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.
handler has cyclomatic complexity 313 and cognitive complexity 494; 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. — packages/features/bookings/lib/service/RegularBookingService.ts:486
Success has cyclomatic complexity 169 and cognitive complexity 127; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:108
updateHandler has cyclomatic complexity 105 and cognitive complexity 120; 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. — packages/trpc/server/routers/viewer/eventTypes/heavy/update.handler.ts:60
handler has cyclomatic complexity 71 and cognitive complexity 78; 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. — packages/features/bookings/lib/handleCancelBooking.ts:81
(anonymous) has cyclomatic complexity 66 and cognitive complexity 53; 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/web/modules/bookings/components/Booker.tsx:91
_getAvailableSlots has cyclomatic complexity 59 and cognitive complexity 80; 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:897
signIn has cyclomatic complexity 58 and cognitive complexity 120; 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. — packages/features/auth/lib/next-auth-options.ts:788
superRefineField has cyclomatic complexity 54 and cognitive complexity 90; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/features/bookings/lib/getBookingResponsesSchema.ts:88
getPublicEvent has cyclomatic complexity 51 and cognitive complexity 57; 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. — packages/features/eventtypes/lib/getPublicEvent.ts:284
confirmHandler has cyclomatic complexity 51 and cognitive complexity 54; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/trpc/server/routers/viewer/bookings/confirm.handler.ts:51
updateProfileHandler has cyclomatic complexity 50 and cognitive complexity 67; 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. — packages/trpc/server/routers/viewer/me/updateProfile.handler.ts:41
getServerSideProps has cyclomatic complexity 49 and cognitive complexity 50; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — apps/web/modules/bookings/views/bookings-single-view.getServerSideProps.tsx:39
BookingListItem has cyclomatic complexity 49 and cognitive complexity 39; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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/web/components/booking/BookingListItem.tsx:130
outOfOfficeCreateOrUpdate has cyclomatic complexity 48 and cognitive complexity 60; 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. — packages/trpc/server/routers/viewer/ooo/outOfOfficeCreateOrUpdate.handler.ts:27
_getUserAvailability has cyclomatic complexity 47 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 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. — packages/features/availability/lib/getUserAvailability.ts:361
Signup has cyclomatic complexity 47 and cognitive complexity 39; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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/web/modules/signup-view.tsx:192
REDACTED has cyclomatic complexity 46 and cognitive complexity 60; 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. — packages/features/auth/lib/next-auth-options.ts:418
AppForm has cyclomatic complexity 46 and cognitive complexity 54; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/app-store-cli/src/components/AppCreateUpdateForm.tsx:14
BookerPlatformWrapperComponent has cyclomatic complexity 45 and cognitive complexity 39; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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. — packages/platform/atoms/booker/BookerPlatformWrapper.tsx:50
_getBusyTimesFromLimitsForUsers has cyclomatic complexity 43 and cognitive complexity 155; 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:379
What to do
Break down the listed branch-heavy functions; aim P95 cyclomatic ≤ 5.
Do you agree with this assessment?
R3 · Large Files8.8 / 10Strong✓ Tool-verified
React / JS · Code Health — How many source files exceed the large-file threshold.
Method: Components/modules exceeding the large-file threshold, counted exhaustively across the frontend source tree. Deterministic.
apps/api/v2/src/platform/event-types/event-types_2024_06_14/controllers/event-types.controller.e2e-spec.ts has 2902 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/api/v2/src/platform/event-types/event-types_2024_06_14/controllers/event-types.controller.e2e-spec.ts:1
packages/features/bookings/lib/service/RegularBookingService.ts has 2455 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/features/bookings/lib/service/RegularBookingService.ts:1
REDACTED has 2284 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
packages/features/bookings/repositories/BookingRepository.ts has 2061 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/features/bookings/repositories/BookingRepository.ts:1
packages/features/eventtypes/repositories/eventTypeRepository.ts has 1797 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/features/eventtypes/repositories/eventTypeRepository.ts:1
packages/app-store/salesforce/lib/CrmService.ts has 1714 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/app-store/salesforce/lib/CrmService.ts:1
REDACTED has 1549 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
REDACTED has 1507 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
apps/web/modules/event-types/components/tabs/advanced/EventAdvancedTab.tsx has 1476 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/web/modules/event-types/components/tabs/advanced/EventAdvancedTab.tsx:1
REDACTED has 1412 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
REDACTED has 1320 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
packages/testing/src/lib/bookingScenario/expects.ts has 1276 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/testing/src/lib/bookingScenario/expects.ts:1
REDACTED has 1275 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
REDACTED has 1270 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
packages/features/bookings/lib/EventManager.ts has 1207 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/features/bookings/lib/EventManager.ts:1
packages/features/auth/lib/next-auth-options.ts has 1139 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/features/auth/lib/next-auth-options.ts:1
apps/api/v2/src/platform/bookings/2024-08-13/services/bookings.service.ts has 1088 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/api/v2/src/platform/bookings/2024-08-13/services/bookings.service.ts:1
apps/web/components/booking/BookingListItem.tsx has 1086 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/web/components/booking/BookingListItem.tsx:1
packages/trpc/server/routers/viewer/bookings/get.handler.ts has 1061 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/trpc/server/routers/viewer/bookings/get.handler.ts:1
packages/features/eventtypes/components/tabs/limits/EventLimitsTab.tsx has 1051 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/features/eventtypes/components/tabs/limits/EventLimitsTab.tsx:1
apps/web/modules/event-types/components/tabs/advanced/FormBuilder.tsx has 1024 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/web/modules/event-types/components/tabs/advanced/FormBuilder.tsx:1
apps/web/modules/event-types/views/event-types-listing-view.tsx has 999 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — apps/web/modules/event-types/views/event-types-listing-view.tsx:1
apps/web/modules/bookings/components/BookingDetailsSheet.tsx has 987 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/web/modules/bookings/components/BookingDetailsSheet.tsx:1
packages/prisma/zod-utils.ts has 980 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/prisma/zod-utils.ts:1
packages/features/flags/features.repository.integration-test.ts has 976 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/features/flags/features.repository.integration-test.ts:1
packages/features/profile/repositories/ProfileRepository.ts has 976 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/features/profile/repositories/ProfileRepository.ts:1
packages/lib/CalendarService.ts has 907 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/lib/CalendarService.ts:1
packages/app-store/googlecalendar/lib/CalendarService.ts has 885 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/app-store/googlecalendar/lib/CalendarService.ts:1
REDACTED has 870 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
apps/web/modules/event-types/components/tabs/availability/EventAvailabilityTab.tsx has 844 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/web/modules/event-types/components/tabs/availability/EventAvailabilityTab.tsx:1
apps/web/modules/signup-view.tsx has 818 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/web/modules/signup-view.tsx:1
apps/web/modules/event-types/components/locations/HostLocations.tsx has 793 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/web/modules/event-types/components/locations/HostLocations.tsx:1
packages/features/bookings/lib/getLuckyUser.ts has 786 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/features/bookings/lib/getLuckyUser.ts:1
packages/features/feature-opt-in/services/FeatureOptInService.integration-test.ts has 785 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/features/feature-opt-in/services/FeatureOptInService.integration-test.ts:1
apps/api/v2/src/platform/bookings/2024-08-13/services/input.service.ts has 783 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/api/v2/src/platform/bookings/2024-08-13/services/input.service.ts:1
packages/features/availability/lib/getUserAvailability.ts 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. — packages/features/availability/lib/getUserAvailability.ts:1
packages/features/bookings/Booker/store.ts has 756 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/features/bookings/Booker/store.ts:1
packages/platform/atoms/availability/AvailabilitySettings.tsx has 754 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/platform/atoms/availability/AvailabilitySettings.tsx:1
apps/web/playwright/manage-booking-questions.e2e.ts 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. — apps/web/playwright/manage-booking-questions.e2e.ts:1
apps/web/modules/users/components/UserTable/UserListTable.tsx has 750 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/web/modules/users/components/UserTable/UserListTable.tsx:1
What to do
Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
Do you agree with this assessment?
R4 · Test Coverage6.6 / 10Adequate✓ Tool-verified
React / JS · Readiness — Static test reachability (D-386): the share of production files reachable from any test via the import graph — measured without running anything.
Method: Static test reachability: the share of production files reachable from any test via the import graph — measured without running anything. Deterministic.
No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one. (×40) — apps/api/v2/src/platform/event-types/event-types_2024_06_14/controllers/event-types.controller.e2e-spec.ts:1, REDACTED:1, REDACTED:1, …
What to do
Add tests that import the unreached modules (directly or through their public entry).
Do you agree with this assessment?
R6 · Tooling10.0 / 10Exemplary✓ Tool-verified
React / JS · Readiness — Whether the project wires up test, lint and typecheck — detected from each REDACTED 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: REDACTED scanned for test/lint/typecheck script wiring. Deterministic presence check.
Do you agree with this assessment?
R7 · Dead Code5.9 / 10Adequate✓ 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.
2 file(s) (~102 LoC) were excluded from dead-code analysis. This package DOES declare main/module/exports — but every declared target is missing from the scanned tree, which is what a build-output entry (dist/, lib/, out/) looks like before the package is built. Point a declared target at the source entry, or build the package before scanning, so reachability can follow it. — packages/config
2 file(s) (~37 LoC) were excluded from dead-code analysis. This package's entry point(s) resolved, but the walk stopped one hop in: packages/kysely/index.ts imports './types', which is not in the scanned tree. That is usually a generated or build-output module, so reachability cannot see past it and no dead-code claim is made about this package. Nothing is necessarily wrong here. — packages/kysely
24 file(s) (~2306 LoC) were excluded from dead-code analysis. This package's entry point(s) resolved, but the walk stopped one hop in: packages/prisma/client/index.ts imports '../generated/prisma/client', which is not in the scanned tree. That is usually a generated or build-output module, so reachability cannot see past it and no dead-code claim is made about this package. Nothing is necessarily wrong here. — packages/prisma
Unreachable from the 919 application, 89 tooling and 646 test entry point(s) detected in this repo. Gate removals on `yarn run build` — an undetected custom entry would make these reachable.
no import path from any entry point (919 application, 89 tooling, 646 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 (×28) — packages/features/watchlist/lib/freeEmailDomainCheck/freeEmailDomains.ts, apps/api/v2/src/platform/event-types/event-types_2024_06_14/controllers/event-types.controller.e2e-spec.ts, apps/web/modules/users/components/UserTable/UserListTable.tsx, …
no import path from any entry point (919 application, 89 tooling, 646 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/features/booking-audit/di/BookingAuditTaskerProducerService.module.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 — packages/features/booking-audit/lib/service/BookingAuditTaskerProducerService.ts
no import path from any entry point (919 application, 89 tooling, 646 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/web/modules/users/components/UserTable/UserListTable.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) — apps/web/modules/users/components/UserTable/UserTableActions.tsx, apps/web/modules/users/components/UserTable/BulkActions/EventTypesList.tsx
no import path from any entry point (919 application, 89 tooling, 646 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (packages/features/booking-audit/di/BookingAuditProducerService.container.ts, packages/features/booking-audit/lib/service/BookingAuditTaskerProducerService.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 — packages/features/booking-audit/lib/service/BookingAuditProducerService.interface.ts
no import path from any entry point (919 application, 89 tooling, 646 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/lib/domainManager/organization.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 — packages/lib/domainManager/deploymentServices/cloudflare.ts
no import path from any entry point (919 application, 89 tooling, 646 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/web/components/security/TwoFactorAuthSection.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 — apps/web/components/security/EnableTwoFactorModal.tsx
no import path from any entry point (919 application, 89 tooling, 646 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/web/modules/users/components/UserTable/EditSheet/EditUserSheet.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 — apps/web/modules/users/components/UserTable/EditSheet/EditUserForm.tsx
no import path from any entry point (919 application, 89 tooling, 646 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/web/components/ui/form/CheckedSelect.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 — packages/features/form/components/Select.tsx
What to do
Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
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 REDACTED — installs work only by hoisting accident. (×22) — packages/embeds/vite.config.js:2, apps/api/v2/src/bootstrap.ts:16, apps/api/v2/src/modules/apps/services/gcal.service.ts:3, …
Imported only as a TYPE and declared in no reachable REDACTED. The import is erased at compile time, so nothing is installed and no runtime resolution depends on it — but type-checking a clean clone will fail. Declare the typings it resolves through (or the package itself) in the owning REDACTED. (×3) — apps/api/v2/src/lib/logger.bridge.ts:2, apps/web/app/WithEmbedSSR.test.ts:1, apps/web/app/api/social/og/image/route.tsx:3
Declared in the root REDACTED 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. (×3)
Every import is type-only — move it to devDependencies. — apps/api/v2/src/platform/calendars/services/outlook.service.ts:7
Only test files import it (first: apps/web/playwright/fixtures/users.ts:14) — move it to devDependencies. — REDACTED:90
What to do
Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
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.
Other · Security — Read from this repository's JavaScript/TypeScript source: cryptographic hygiene (weak hash or cipher, key material fixed in the source) and outbound TLS (certificate validation, protocol version) — facts about code that hold whether or not it serves anything itself. Markup this repository SHIPS is scored for third-party script integrity whether or not the repository serves it itself, since a page handed to a consumer runs in that consumer’s origin. This repository commits the configuration that serves its own HTTP surface, so that configuration was read in full for the security response headers it sets. The server controls — HTTPS enforcement, HSTS, cookie flags, input validation — are NOT assessed for JavaScript/TypeScript: each is scored as an absence, an absence is only reportable over the production HTTP server, and in this ecosystem the file that opens the port is build output or a framework launcher rather than a file in the source tree. Their absence here is not a finding about this repository. Its Node HTTP listeners were read for HTTPS enforcement alone — TLS served, a redirect to https:// or HSTS, or a TLS-terminating proxy configuration committed beside the server — each judged per server package.
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.
`rejectUnauthorized: false` is set on a TLS client, so every peer certificate is accepted — including one an attacker presents. Chain, expiry, revocation and hostname are all skipped, so an attacker on the network path can present any certificate and read or rewrite the traffic — the connection is encrypted to the attacker, not to the intended host. Remove the option so Node validates the peer. If the server presents a self-signed or privately-issued certificate, trust THAT issuer rather than every certificate: pass its CA as `ca` (or set `NODE_EXTRA_CA_CERTS`), which keeps the chain and hostname checks on. A managed database or broker that documents `rejectUnauthorized: false` publishes a CA bundle for exactly this purpose. — packages/app-store/exchangecalendar/lib/CalendarService.ts:204
`CAL_VIDEO_RECORDING_TOKEN_SECRET` is the MAC key, and its shipped DEFAULT is a compile-time constant — an installation that never overrides it encrypts with a value published in this repository, and the code cannot distinguish that state from a configured one. A key that ships with the source is not secret: every contributor, fork, mirror and released binary carries it, so anyone holding the repository can decrypt what any installation encrypted, and there is no way to invalidate what was already protected because every deployment built from this source shares the value. Where the constant is a password salt the consequence differs but is no smaller — one global salt means precomputation amortises across every installation, which is the property salting exists to destroy. Read the value from configuration, an environment variable or a secrets manager at startup and FAIL FAST when it is absent, so a missing key stops the process instead of silently falling back to a shared default; treat the committed value as disclosed and rotate it rather than only deleting the line. For a salt, generate a fresh random one per password and store it alongside the hash. — packages/lib/videoTokens.ts:5
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+ (`createHash("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. (×4) — apps/web/scripts/copy-app-store-static.js:35, packages/features/auth/lib/verifyCodeUnAuthenticated.ts:17, packages/features/auth/lib/verifyEmail.ts:105, …
`decryptedKey.password === password` checks a password against the stored one in plaintext, so the store holds the password itself and whoever reads it holds every account. — apps/api/v2/src/platform/calendars/services/apple-calendar.service.ts:82
`decryptedCredential.password === password` checks a password against the stored one in plaintext, so the store holds the password itself and whoever reads it holds every account. — packages/app-store/applecalendar/api/add.ts:37
`//unpkg.com/react-grab/dist/index.global.js` is executed by this page with no Subresource Integrity. Whoever can answer that request — the CDN, anyone who compromises it, anyone on the network path — runs arbitrary script in this page's origin, with its session. The URL also names no version, so it resolves to whatever that origin serves at fetch time — the executed bytes can change with nobody touching this repository. 8 such include(s) across the repository's markup. — apps/web/app/layout.tsx:124
`http(…).listen(…)` serves plain HTTP on a network address, and nothing in its package enforces HTTPS: no TLS served (`https.createServer`, Fastify `https`, Nest `httpsOptions`), no redirect of plain requests to `https://`, no `Strict-Transport-Security` (helmet sends it by default), and no TLS-terminating proxy configuration committed beside it — so a browser may talk to it in clear text. (−2.0 on this card.) — apps/api/index.js:18
What to do
Stop accepting every TLS certificate: delete `rejectUnauthorized: false` / `NODE_TLS_REJECT_UNAUTHORIZED=0` so the chain, hostname and expiry are verified, and trust a self-signed or private server by passing its CA (`ca`, or `NODE_EXTRA_CA_CERTS`) — never by switching verification off.
Load cryptographic key and salt material from configuration, an environment variable or a secrets manager rather than fixing it in the source, and fail fast at startup when it is absent — a default that silently works is the one that reaches production. Rotate anything already committed: it must be treated as disclosed. Salts should be generated per password and stored with the hash, never shared across installations.
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 4 sites, not one: `apps/web/scripts/copy-app-store-static.js:35` (createHash("md5")), `packages/features/auth/lib/verifyCodeUnAuthenticated.ts:17` (createHash("md5")), `packages/features/auth/lib/verifyEmail.ts:105` (createHash("md5")), `packages/trpc/server/routers/viewer/me/get.handler.ts:122` (createHash("md5")). Each is a separate decision — fixing only the line this row cites leaves the others in place.
Store passwords with a salted, deliberately slow KDF — scrypt or PBKDF2 from node:crypto, or bcrypt/Argon2 — and compare with a constant-time check. A fast digest of a password, however it is encoded, is reversed by precomputed tables or GPU guessing. Start in `apps/api/v2/src/platform/calendars/services/apple-calendar.service.ts:82`.
Pin third-party scripts and verify them: name an exact version in the URL and add an `integrity="sha384-…"` hash alongside `crossorigin="anonymous"` (both are required — an integrity hash on a cross-origin script without `crossorigin` is not evaluated, it blocks the script). Where the vendor ships a continuously-updated loader and publishes no stable hash (tag managers, analytics, chat widgets), Subresource Integrity is not available: constrain it instead with a `Content-Security-Policy` that names the exact origins allowed to execute, and drop the script from the pages that do not need it. Where the page is shipped inside a package that others host, prefer vendoring the asset and serving it from the app’s own origin, so no consumer inherits a third-party dependency they did not choose.
Enforce HTTPS on each listed server: serve TLS itself, or redirect plain requests to `https://` and send `Strict-Transport-Security` (`helmet()` does by default) behind the TLS-terminating proxy — and commit that proxy's configuration beside the service. A server only this machine reaches should bind `127.0.0.1`.
Other · Code Health — Whether the code avoids sync-over-async (deadlock-prone blocking on tasks) and async void.
Method: Roslyn syntax scan: async methods scanned for .Wait()/.GetAwaiter().GetResult() and async-void outside event handlers. Deterministic, hard fact per invocation.
Other · Code Health — Whether any branch is dead by construction — a switch arm whose label can never equal a case-normalised subject, or an `else if` whose predicate the arm above has already swallowed.
Method: Roslyn syntax + semantics: switch labels compared against the subject's own case normaliser, and if/else-if chains checked for a literal an earlier arm's containment test already swallows. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X13 · Undrained process stream10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a child process that has BOTH standard streams redirected drains both — reading one to the end while the other is never read deadlocks once the child fills the unread pipe.
Method: Roslyn syntax + semantics: ProcessStartInfo launches with both streams redirected, checked for a drain of each stream across the enclosing type. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `spawn` imported from `child_process` whose stdout and stderr are both pipes (no options, no `stdio`, or `stdio` of `'pipe'`), bound to a local that never leaves its scope, where exactly one of the two streams is read, the other never, and the child’s `close`/`exit` (or the read stream’s end) is awaited; a shell redirect in the call’s arguments or a `kill` of the child suppresses it. The same rule reads Python’s `subprocess.Popen`, Dart’s `Process.start`, Ruby’s `Open3.popen3`, and Scala’s JDK process starts (`new ProcessBuilder(…).start()` with no `redirectErrorStream`/`redirectError`/`redirectOutput`/`inheritIO`, `Runtime.getRuntime.exec`) where one of `getInputStream`/`getErrorStream` is read and the other never while `waitFor()` is called or the read stream is read to its end. Deterministic, provable per finding. Advisory.
Other · Security — Whether a hand-rolled public/private IP check can be walked past — a method that unwraps IPv4-mapped IPv6 but returns the opposite verdict for the same host written as IPv4-compatible, 6to4 or NAT64.
Method: Roslyn syntax + semantics: methods that unwrap IPv4-mapped IPv6 and hand-roll IPv4 range carve-outs, checked for whether the IPv6 branch also accounts for the IPv4-compatible, 6to4 and NAT64 embeddings. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X15 · Unvalidated length from an untrusted reader10.0 / 10Exemplary○ Nothing flagged
Other · Security — Whether a length read out of the stream being parsed is bounded before it is allocated or read — an unchecked count taken from the input lets the input choose the allocation.
Method: Roslyn syntax + semantics: integer lengths read from a BinaryReader and spent on a bulk read or an array allocation, checked for any comparison or bounding call on the value anywhere in the method. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a loop that shortens a string until it fits a length budget has a floor — one with none grinds the value down to the empty string, or past it into a negative-length `Substring`.
Method: Roslyn syntax + semantics: while/do loops whose body's only effect on a string is to drop its last character, checked for whether anything — a direct comparison on the length, a body guard, a break — bounds that length below. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `while`/`do` loop whose body’s one assignment to a value is `x = x.slice(0, -1)` or `x = x.slice|substring|substr(0, x.length - 1)`, driven by a condition that reads `x.length` only as a term of a larger expression — never compared directly, never tested for truthiness, and with no other read of `x` — and whose body has no `break`, `return`, `throw` or `if` naming `x`. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X17 · Uncapped recursion over a caller-supplied document3.5 / 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.
`isEqual` is exported and takes `value: unknown` from its caller, and it calls itself at line 9 (`isEqual`) with a piece of `value` (and at line 21) — and nowhere in `isEqual` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame 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. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `isEqual` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — packages/lib/isEqual.ts:9
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.
Other · Code Health — Whether a type's disposal matches what it OWNS — releasing what it created, leaving alone what it was handed, and not declaring a finalizer for state that has nothing unmanaged to finalize.
Method: Roslyn syntax + semantics: every assignment to a disposable field is read to decide whether the type CREATED the value or was handed it, and the type's disposal is checked against that answer — an injected interface it disposes, a value it constructed and never releases, a finalizer on a type holding nothing unmanaged, and a disposable local whose every reference is a plain member read. A value handed to a container that disposes its contents (a parent control's `Controls` collection, a component `IContainer`) is released by that container and is not reported; generated code is out of population. On a repository with no .NET source the same ownership questions are read in JavaScript/TypeScript off the engine’s own token stream (test, vendored, generated and minified paths not): a class declaring `dispose()`, `[Symbol.dispose]()` or `[Symbol.asyncDispose]()` that disposes a field it was handed through a constructor parameter typed as a repository interface or resolved by a dependency-injection container; that assigns a field only ever from `new X(…)` of a disposable class and neither releases it anywhere in the class nor names it in its disposal member or a method that member calls, nor hands it to anything else; and a `const`/`let` local built from literals only whose every reference opens a statement operating on a non-release member of it. A class is disposable when every repository declaration of its name declares or inherits a disposal member, or when it is a documented library disposable (`vscode` EventEmitter, CancellationTokenSource and Disposable; three.js geometries, materials, textures, render targets, renderers, controls and composers). The finalizer arm has no JavaScript counterpart: a class cannot declare one. Dart is read for the owned-and-never-released arm: a Flutter `State` (or a class declaring `dispose()`/`close()`) whose library-private field is written only with direct creations of a framework controller, `FocusNode`, `StreamController` or periodic `Timer` (or a `.listen(…)` into a field declared `StreamSubscription`), which nothing in the class or its library releases (`dispose`/`close`/`cancel`) and which is never handed on except as a named argument. Ruby is read for the owned-and-never-released arm and the abandoned-local arm: a class declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose instance variable is written only with a blockless core descriptor creation (`File.open`/`new`, `Tempfile`, `Dir.open`, `IO.popen`, the `socket` and `openssl` socket classes) that no method of the class closes and that is never handed on (passed, returned, stored, exposed by `attr_reader`, delegated) — a class whose superclass or mixin lies outside the repository is not judged — and a blockless creation read through and dropped (`File.open(path).read`) or held in a local that is never closed, returned, passed or stored (a `&:read` block-pass, an `autoclose: false` borrow and a `fileno` hand-over are not abandonment). PHP is read for the same two arms: a class (not a trait, and not one using a trait) declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose `private` property (or a `final` class's `protected` one) is written only with a direct core `fopen`, `tmpfile`, `popen`, `proc_open`, `fsockopen`, `stream_socket_client`/`server` or `opendir` that nothing in the class closes (`fclose`, `pclose`, `closedir`, `unset`, a reset to `null`) and that is never handed on, and a handle held in a function's local, or read through as the argument of a reader, that is never closed, returned, passed, captured or stored; a `php://` stream, `curl_init`, `SplFileObject`, `PDO` and a function the repository declares under the core name are not read. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a method that temporarily changes state belonging to the whole process — the working directory, an environment variable — puts it back on EVERY path: a restore reached only when nothing throws leaks the change to the rest of the process.
Method: Roslyn syntax + semantics: method bodies that write the process working directory or an environment variable and write it back in the same body, checked for whether that restore sits in a `finally`/`catch` or only on the straight-line path. On a repository with no .NET source the same rule reads production JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not): `process.chdir`, `process.env.NAME =`/`["NAME"] =` and `delete process.env.NAME`, and Deno’s `Deno.chdir`/`Deno.env.set`/`Deno.env.delete`, paired per function body (a nested function or arrow is its own body, and module top-level code is none), where the last write puts back a local the body captured from the same global or deletes a variable the first write set, with at least one statement between them; a write in a `catch`/`finally` of that body silences it. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether 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 17/113 async functions that make a cancellable request (fetch, axios, ky, ofetch) 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.
`refreshTokens` 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 })`. — packages/platform/atoms/lib/http.ts:57
`refreshAccessToken` 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 })`. (×4) — packages/lib/CloseCom.ts:247, packages/app-store/zohocalendar/lib/CalendarService.ts:38, packages/app-store/webex/lib/VideoApiAdapter.ts:60, …
`_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 })`. — packages/lib/CloseCom.ts:460
`http` 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 })`. — packages/lib/fetch-wrapper.ts:3
`fetchUsername` 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 })`. — packages/lib/fetchUsername.ts:8
`checkCfTurnstileToken` 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 })`. — packages/lib/server/checkCfTurnstileToken.ts:7
`isBlacklisted` 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 })`. — packages/lib/server/username.ts:40
`fetchHolidays` 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 })`. — packages/lib/holidays/GoogleCalendarClient.ts:47
`api` 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 })`. — packages/lib/domainManager/deploymentServices/cloudflare.ts:175
`createDomain` 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 })`. — packages/lib/domainManager/deploymentServices/vercel.ts:21
`deleteDomain` 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 })`. — packages/lib/domainManager/deploymentServices/vercel.ts:57
`handleWebhookScheduledTriggers` 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 })`. — packages/features/webhooks/lib/handleWebhookScheduledTriggers.ts:8
`_sendPayload` 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 })`. — packages/features/webhooks/lib/sendPayload.ts:301
`sendWebhookDirectly` 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 })`. — packages/features/webhooks/lib/service/WebhookService.ts:75
`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 })`. — packages/features/calendar-subscription/adapters/Office365CalendarSubscription.adapter.ts:233
`downloadImageDataFromUrl` 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 })`. — packages/features/auth/signup/utils/prefillAvatar.ts:12
`fetchSignup` 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 })`. — packages/features/auth/signup/lib/fetchSignup.ts:28
`REDACTED` 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 })`. — packages/features/auth/lib/next-auth-options.ts:418
`submitResponseAndGetRoutingResult` 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:142
`getNodeMailerPayload` 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 })`. (×2) — packages/emails/templates/attendee-daily-video-download-transcript-email.ts:24, packages/emails/templates/organizer-daily-video-download-transcript-email.ts:23
`fetchNewTokenObject` 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 })`. — packages/app-store/zoomvideo/lib/VideoApiAdapter.ts:391
`createContacts` awaits `axios(…)` 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(url, { signal })`. (×2) — REDACTED:62, REDACTED:122
`getContacts` awaits `axios(…)` 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(url, { signal })`. (×2) — REDACTED:94, REDACTED:158
`updateMeeting` awaits `axios(…)` 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(url, { signal })`. — REDACTED:159
`deleteMeeting` awaits `axios(…)` 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(url, { signal })`. — REDACTED:186
`refreshAccessToken` awaits `axios(…)` 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(url, { signal })`. — REDACTED:215
`getUserInfo` 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 })`. — packages/app-store/zohocalendar/lib/CalendarService.ts:104
`refreshAccessToken` 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 })`. — REDACTED:69
`updateEvent` awaits `axios.put(…)` 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.put(url, { signal })`. — REDACTED:248
`deleteEvent` 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 })`. — REDACTED:278
`getVitalsConfig` 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 })`. — packages/app-store/vital/components/AppConfiguration.tsx:55
`getLinkToken` 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 })`. — packages/app-store/vital/components/InstallAppButton.tsx:6
`deleteMeeting` 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 })`. — packages/app-store/tandemvideo/lib/VideoApiAdapter.ts:146
What to do
Thread an AbortSignal through async functions that make requests, so the work stops when its caller gives up.
Other · Code Health — Whether a `when` guard is free of side effects — a guard that increments a counter or assigns while deciding whether its arm matches applies that change during PATTERN MATCHING, on an arm that may not be selected, and skips it entirely when a short-circuit to its left answers first.
Method: Roslyn syntax: `when` guards on case labels and switch-expression arms, read for a mutation (`++`/`--`/assignment) sitting in a position the guard's own `&&`/`||`/`??`/`?:`/`?.` can skip. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a method that TAKES a lock or semaphore and gives it back from a flag-guarded `finally` returns the value that flag implies — reporting success while the guard hands the primitive back admits a second caller the exclusion was there to keep out, and reporting failure while the guard keeps it leaves nothing to ever give it back.
Method: Roslyn syntax: `try` statements whose `finally` releases a synchronisation primitive under a bare local-bool guard, where the method also TOOK that same primitive before the `try`, checked for a `return` of a bool literal whose value disagrees with the flag state the method's own straight-line assignments put it in. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether the work a diagnostic log line costs is paid only when that line is wanted — C# evaluates a call's arguments BEFORE the call, so a trace/debug message joined or projected out of a collection is built in full on every pass, and then discarded by a sink the shipped configuration leaves switched off.
Method: Roslyn syntax: log calls at a diagnostic level (a `Log`-prefixed method naming Trace/Debug/Verbose, or a bare `Debug`/`Trace`/`Verbose` on a receiver named for a logger), whose argument list is read for a call whose cost scales with a sequence — a LINQ operator, a materialisation, `string.Join`, a serializer — with no enclosing level check or conditional-compilation region. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `debug`/`trace`/`verbose` call on a receiver named for a logger, or a `log`-prefixed method naming the level, whose argument calls an array operator (`map`/`filter`/`reduce`/`sort`/…), `Array.from`, `Object.keys/values/entries`, `JSON.stringify`/`util.inspect` over anything but a literal, or an array `join` — outside any arrow or function passed as an argument, which the logger calls only when the level is on — with no enclosing `if`, `&&` or `?:` whose condition names a level, a level string, or the `NODE_ENV`/`__DEV__`/`DEV` build switch. Deterministic, provable per finding. Advisory.
`debug` at line 710 is called with an argument built by `usersWithCredentials.map((user) => user.email)` (line 711), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch. — REDACTED:710
`debug` at line 177 is called with an argument built by `passedSelectedCalendars.map(getPiiFreeSelectedCalendar)` (line 181), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch. — packages/features/calendars/lib/getCalendarsEvents.ts:177
`debug` at line 222 is called with an argument built by `calendarCredentials.map(getPiiFreeCredential)` (line 225), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch. — packages/features/calendars/lib/getCalendarsEvents.ts:222
`debug` at line 58 is called with an argument built by `selectedCalendars.map((c) => c.id)` (line 61), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch. — packages/features/calendar-subscription/lib/cache/CalendarCacheWrapper.ts:58
`debug` at line 145 is called with an argument built by `selectedCalendars.map((c) => c.id)` (line 148), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch. — packages/features/calendar-subscription/lib/cache/CalendarCacheWrapper.ts:145
`debug` at line 185 is called with an argument built by `bookings?.map((booking) => getPiiFreeBooking(booking))` (line 188), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch. — packages/features/busyTimes/services/getBusyTimes.ts:185
`debug` at line 424 is called with an argument built by `usersWithMaxShortfall.map((user) => user.email)` (line 428), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch. — packages/features/bookings/lib/getLuckyUser.ts:424
`debug` at line 952 is called with an argument built by `qualifiedRRUsers.map((user) => user.id)` (line 955), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch. — packages/features/bookings/lib/service/RegularBookingService.ts:952
`debug` at line 980 is called with an argument built by `qualifiedRRUsers.map((user) => user.id)` (line 983), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch. — packages/features/bookings/lib/service/RegularBookingService.ts:980
`debug` at line 1009 is called with an argument built by `availableUsers.map((user) => user.id)` (line 1012), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch. — packages/features/bookings/lib/service/RegularBookingService.ts:1009
`debug` at line 1692 is called with an argument built by `attendeesList.map((guest) => ({ timeZone : guest.timeZone }))` (line 1696), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch. — packages/features/bookings/lib/service/RegularBookingService.ts:1692
`debug` at line 212 is called with an argument built by `users.map(getPiiFreeUser)` (line 215), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch. — packages/features/bookings/lib/handleNewBooking/loadAndValidateUsers.ts:212
`debug` at line 282 is called with an argument built by `bookingUids.join(",")` (line 283), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch. — packages/features/booking-audit/lib/service/BookingAuditTaskConsumer.ts:282
`debug` at line 294 is called with an argument built by `bookingUids.join(",")` (line 295), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch. — packages/features/booking-audit/lib/service/BookingAuditTaskConsumer.ts:294
`debug` at line 86 is called with an argument built by `JSON.stringify(err)` (line 86), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch. — apps/web/pages/_error.tsx:86
What to do
Each finding names the diagnostic call and the expression inside its argument whose cost scales with a collection. Confirm from the two that the argument is built before the call — that is JavaScript's evaluation order, not a guess — then put the construction behind the level check the logger offers (`if (logger.isLevelEnabled('debug'))` for pino and winston, `isDebugEnabled()` for log4js, the repository's own debug flag where it has one), or hand the logger the object and a format string (`logger.debug({ payload }, 'raw request')`) so the serialising happens only when the line is written. Moving the call is not the fix: it is the join/projection/stringify in the argument that is paid, wherever the call sits.
Do you agree with this assessment?
X24 · Document value interpolated into markup unescaped4.2 / 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.
`script.script` 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. — apps/web/app/(use-page-wrapper)/layout.tsx:34
``${JSON.stringify(speculationRules)}`` 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. — apps/web/app/SpeculationRules.tsx:29
`eventType.descriptionAsSafeHTML||""` 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. — apps/web/components/eventtype/EventTypeDescriptionSafeHTML.tsx:9
``(function (w, d, s, l, i) {
w[l] = w[l] || []; w[l].push({ 'gtm.start': new Date().getTime()…` 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. — apps/web/modules/signup-view.tsx:350
`process.env.NEXT_PUBLIC_GTM_ID` is text this program did not author, and it is written into a URL attribute 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. — apps/web/modules/signup-view.tsx:360
`props.safeBio` 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:108
``
window.calNewLocale = "${newLocale}";
window.calIsDesktopApp = ${isDesktopApp};
…` 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. — apps/web/pages/_document.tsx:60
`parseValue(script.content)||""` 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:146
`location` is text this program did not author, and it is written into the text of an element through markup this function returns 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. — packages/app-store/hubspot/lib/CrmService.ts:84
`htmlContent.replaceAll("<p>",`<p style="${css}">`).replaceAll("<li>",`<li style="${css}">`)` 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:27
`html` 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. — packages/emails/src/components/RawHtml.tsx:5
`skeletonContent` is text this program did not author, and it is written into the text of an element through `innerHTML` 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. — packages/embeds/embed-core/src/EmbedElement.ts:195
`window.Cal.__css` is text this program did not author, and it is written into the text of an element through `innerHTML` 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. (×3) — packages/embeds/embed-core/src/FloatingButton/FloatingButton.ts:104, packages/embeds/embed-core/src/Inline/inline.ts:37, packages/embeds/embed-core/src/ModalBox/ModalBox.ts:249
`css` is text this program did not author, and it is written into the text of an element through `innerHTML` 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:87
`generateDataAttributes({pageType,theme,layout,})` is text this program did not author, and it is written into an unquoted attribute through `innerHTML` 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. HTML text encoding does not help in an unquoted attribute — whitespace ends it; quote the attribute and encode the value. (×2) — REDACTED:969, REDACTED:1258
`uid` is text this program did not author, and it is written into a quoted attribute value through `innerHTML` 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:1263
`descriptionAsSafeHtml` 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:101
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.
Other · Code Health — Whether a value the caller is invited to supply is the value the type actually uses — a constructor parameter stored in a private field that nothing ever reads while the default it was given is spelled out a second time at the site that should have read it, a keyed lookup that falls back to a different setting than the one its key names while the same type falls back to the matching one for that same key, or a culture-sensitive parse given no format provider by a type that feeds its own settable culture to the same kind of parse elsewhere, or a number an entry point writes to standard output under the host's culture while the same entry point formats with the invariant culture elsewhere. Either way, every caller who supplies a value silently gets something else.
Method: Roslyn syntax: private instance fields of a non-partial type assigned in a constructor from one of its own parameters with a `??` fallback, checked for whether anything in the type body reads the field and whether that same fallback expression is spelled out again outside the constructor; and `??` fallbacks onto a member access from a lookup call carrying exactly one string literal, grouped by that key across the type and checked for a fallback member whose folded name disagrees with the key while a sibling site for the same key agrees with it. On a repository with no .NET source the first two arms read JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `#x`, `private` or `private` parameter-property instance field filled in the constructor from a parameter (or one member of one) through `??`/`||` or a parameter default, never read anywhere in the file by name, whose constructed default is spelled again in the class body; and `lookup("key") ?? s.member` grouped by key per class, or per module outside every class. The culture arm has no JavaScript counterpart: its parses take no locale. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X28 · Index access outside its own emptiness guard10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a condition that tests a value for emptiness indexes that same value only where the test holds — an `||` written one parenthesis too far to the left leaves an index access outside the guard beside it, so the empty case the guard exists to anticipate reaches the index and throws.
Method: Roslyn syntax only, no semantic model: the OUTERMOST `&&`/`||` of every boolean condition, read for a symbol the condition tests for emptiness (`string.IsNullOrEmpty`/`IsNullOrWhiteSpace`, a `Length`/`Count` comparison against a literal, `Any()`, a `Length`/`Count` pattern, or a comparison against `""`) and ALSO indexes. Each `symbol[...]` access is placed by a boolean-reachability walk from the access up to the outermost connective: an access is COVERED when some enclosing step has it in the right operand and the left operand, under the truth value that step forces, proves the symbol non-empty — a recursion over `&&`/`||` whose true- and false-directions are asymmetric. A finding needs BOTH an uncovered access and a covered one on the same symbol in the same condition, which is the agreeing twin that separates a misplaced parenthesis from an unrelated length test. Bare index accesses with no emptiness test in the condition are neither counted nor reported; a non-identifier receiver and a lambda nested inside the condition are outside the population. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X29 · Per-element action decided by a fixed element10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a decision taken once per element is taken ABOUT that element — a test inside a counted loop that reads a fixed subscript of the very collection its guarded statement indexes by the loop variable applies element zero's answer to all of them, so the elements that differ from it are all handled wrongly, and in the same direction.
Method: Roslyn syntax only, no semantic model: every `for` statement declaring exactly ONE loop variable, and every `if` inside its body that is not under a nested loop or a lambda. A site enters the population when the `if`’s condition never mentions the loop variable while the statement it guards indexes some collection by that variable ALONE (`c[i]`; `c[i + 1]` and `c[i, j]` are outside it). A finding additionally needs the AGREEING TWIN at the same-collection grain: the condition must read THAT SAME collection at a subscript that does not move — written into the condition, or reached through a local declared BEFORE the loop, so an alias bound inside the body is not followed. Both collection expressions must be simple identifiers. On a repository with no .NET source the same rule reads JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `for (let|var|const x = …; …; …)` with one declarator and a braced body, an alias followed only when it is declared before the loop in a block that encloses it and never assigned inside the loop. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether exceptions are handled rather than silently swallowed or rethrown with lost stack traces.
Method: Roslyn syntax scan: every catch clause counted; empty catches and bare rethrows flagged. Population is all catch clauses, not estimated. Deterministic, hard fact.
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. (×20) — packages/trpc/server/routers/loggedInViewer/unlinkConnectedAccount.handler.ts:32, packages/lib/recentImpersonations.ts:30, packages/lib/recentImpersonations.ts:36, …
`catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. (×6) — packages/lib/webstorage.ts:19, packages/lib/webstorage.ts:29, packages/lib/webstorage.ts:50, …
`catch (err)` 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. — packages/app-store/dub/api/callback.ts:59
What to do
Swallowed exception (empty catch)
Do you agree with this assessment?
X30 · Support guard that admits what it rejects10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a guard written as a NEGATED `||` says what its author meant — `!(a || b || x != k)` is `!a && !b && x == k` by De Morgan, so a bail-out that mixes capabilities the code needs with a fault it refuses turns inside out: it fires only where the capabilities are ABSENT, and lets every value the fault term names walk straight into the body that cannot handle it.
Method: Roslyn syntax only, no semantic model: every logical-not whose operand is a parenthesised `||` chain of two or more disjuncts, flattened (a left-nested `a || b || c` read once would see `(a || b)` as one disjunct). A site enters the population on that shape alone. A finding additionally needs the disjuncts to DISAGREE in polarity: at least one bare boolean read — an identifier or member access, never an invocation, which is a predicate rather than a capability flag — and at least one `x != <constant>`, the only form that negates into an exact-value pin (`== null` negates into a looser requirement and is outside the fault set). Consistently-polarised disjunctions, all-fault or all-capability, are counted and never reported; a negated `&&` is outside the population entirely. No same-receiver gate: it was measured to cost a real defect and remove no false positive. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether log calls use message templates (queryable) rather than interpolated strings.
Method: Roslyn syntax scan: every log call-site counted; interpolated-string first-argument violations flagged. Population is all log calls, not estimated. 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 `trace`/`debug`/`info`/`warn`/`error`/`fatal`/`verbose`/`silly`/`http`/`log` call on a receiver named for a logger, in a package whose own or an enclosing `REDACTED` declares a logger that carries values as fields (pino, pino-http, nestjs-pino, Fastify, winston, bunyan, tslog, LogTape, roarr), whose first deciding argument is a template literal with substitutions; an object-literal fields argument is stepped over, a plain string message clears the call. Python is read the same way: a `debug`/`info`/`warning`/`error`/`exception`/`critical`/`log` call on a logger in a file that imports the standard library’s `logging` or structlog (loguru, which formats at the call, is not judged), whose message is a whole f-string with a non-constant field; a `%`-formatted, `.format()`-ed or concatenated message is not convicted, as in C#. PHP is read the same way: a PSR-3 level call (`emergency`…`debug`, `log`) on a logger (`$logger`, `$this->logger`, Laravel’s `Log::`, `logger()`, `\Drupal::logger()`) in a package whose `composer.json` requires a PSR-3 logger or a framework that hands one out (psr/log, Monolog, Laravel, Symfony, Drupal, CakePHP), or a file that imports one, whose message is a double-quoted string interpolating a variable; a single-quoted message clears the call, and `sprintf` or `.` concatenation is not convicted, as in C#. Dart is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on Sentry’s structured logger (`Sentry.logger`) whose message is a whole string literal interpolating a value (`$name`, `${…}`); the `Sentry.logger.fmt` template API clears the call. Dart that logs only through loggers with one message and no fields (package:logging, package:logger, talker, dart:developer) is not applicable rather than a reach gap. Ruby is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on the console gem’s `Console` (declared by a Gemfile, gemspec or Gemfile.lock, or required) or, where SemanticLogger, Ougai or dry-logger is declared or required, on a receiver named for a logger (`logger`, `@logger`, `Rails.logger`, `log`), whose first deciding argument is, as the whole argument, a double-quoted string interpolating a non-constant value (`#{…}`, `#@ivar`); a plain literal clears the call, keyword arguments are the fields, and a block, `%`-format or `+` concatenation is not convicted. Ruby that logs only through the standard Logger (Rails.logger) is not applicable rather than a reach gap. Deterministic.
`error` at line 649 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.error({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.error('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — packages/lib/CalendarService.ts:649
`warn` at line 742 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.warn({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.warn('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — packages/lib/CalendarService.ts:742
`warn` at line 54 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.warn({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.warn('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — packages/lib/getIP.ts:54
`debug` at line 8 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.debug({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.debug('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — packages/lib/perf.ts:8
`debug` at line 156 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.debug({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.debug('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — packages/lib/sentryWrapper.ts:156
`silly` at line 210 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.silly({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.silly('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — packages/lib/isOutOfBounds.tsx:210
`info` at line 47 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.info({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.info('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — packages/lib/tasker/Tasker.ts:47
`info` at line 56 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.info({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.info('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — packages/lib/tasker/Tasker.ts:56
`error` at line 66 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.error({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.error('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — packages/lib/tasker/Tasker.ts:66
`warn` at line 75 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.warn({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.warn('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — packages/lib/tasker/Tasker.ts:75
`error` at line 81 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.error({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.error('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — packages/lib/tasker/Tasker.ts:81
`error` at line 56 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.error({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.error('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — packages/lib/server/defaultResponder.ts:56
`error` at line 42 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.error({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.error('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — packages/lib/server/service/lingoDotDev.ts:42
`error` at line 73 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.error({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.error('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — packages/lib/server/service/lingoDotDev.ts:73
`error` at line 106 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.error({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.error('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — packages/lib/server/service/lingoDotDev.ts:106
`error` at line 55 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.error({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.error('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — packages/lib/domainManager/organization.ts:55
`info` at line 41 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.info({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.info('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — packages/lib/domainManager/deploymentServices/cloudflare.ts:41
`info` at line 59 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.info({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.info('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — packages/lib/domainManager/deploymentServices/cloudflare.ts:59
`info` at line 74 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.info({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.info('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — packages/lib/domainManager/deploymentServices/cloudflare.ts:74
`info` at line 79 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.info({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.info('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — packages/lib/domainManager/deploymentServices/cloudflare.ts:79
`info` at line 85 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.info({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.info('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — packages/lib/domainManager/deploymentServices/cloudflare.ts:85
`info` at line 87 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.info({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.info('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — packages/lib/domainManager/deploymentServices/cloudflare.ts:87
`info` at line 155 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.info({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.info('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — packages/lib/domainManager/deploymentServices/cloudflare.ts:155
`error` at line 158 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.error({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.error('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — packages/lib/domainManager/deploymentServices/cloudflare.ts:158
`info` at line 170 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.info({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.info('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — packages/lib/domainManager/deploymentServices/cloudflare.ts:170
`info` at line 23 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.info({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.info('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — packages/lib/domainManager/deploymentServices/vercel.ts:23
`info` at line 58 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.info({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.info('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — packages/lib/domainManager/deploymentServices/vercel.ts:58
`log` at line 75 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.log({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.log('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — apps/api/v2/src/main.ts:75
`log` at line 48 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.log({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.log('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — apps/api/v2/src/vercel-webhook.controller.ts:48
`log` at line 88 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.log({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.log('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — apps/api/v2/src/vercel-webhook.controller.ts:88
`log` at line 97 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.log({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.log('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — apps/api/v2/src/vercel-webhook.controller.ts:97
`error` at line 101 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.error({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.error('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — apps/api/v2/src/vercel-webhook.controller.ts:101
`error` at line 26 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.error({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.error('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — apps/api/v2/src/platform/calendars/processors/calendars.processor.ts:26
`error` at line 75 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.error({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.error('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — apps/api/v2/src/platform/bookings/2024-08-13/services/booking-location-calendar-sync.service.ts:75
`log` at line 86 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.log({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.log('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — apps/api/v2/src/platform/bookings/2024-08-13/services/booking-location-calendar-sync.service.ts:86
`log` at line 95 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.log({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.log('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — apps/api/v2/src/platform/bookings/2024-08-13/services/booking-location-calendar-sync.service.ts:95
`warn` at line 105 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.warn({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.warn('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — apps/api/v2/src/platform/bookings/2024-08-13/services/booking-location-calendar-sync.service.ts:105
`log` at line 113 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.log({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.log('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — apps/api/v2/src/platform/bookings/2024-08-13/services/booking-location-calendar-sync.service.ts:113
`error` at line 117 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.error({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.error('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — apps/api/v2/src/platform/bookings/2024-08-13/services/booking-location-calendar-sync.service.ts:117
`error` at line 210 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.error({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.error('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — apps/api/v2/src/platform/bookings/2024-08-13/services/booking-location-integration.service.ts:210
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.
2/26 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.
~3.2 `!` null assertions per 1k TypeScript source lines — 1185 assertion(s) across the 365094 source line(s) of the 4247 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: REDACTED (60), packages/platform/types/event-types/event-types_2024_06_14/outputs/booking-fields.output.ts (53), apps/api/v2/src/platform/event-types/event-types_2024_04_15/outputs/get-event-type-public.output.ts (51). Each one tells the compiler to trust the author about null, suppressing the very diagnostic `strictNullChecks` exists to produce.
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 `?`).
Do you agree with this assessment?
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).
The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.
Unscored — 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.
P12 CI test-gate honesty — 3 observation(s) recorded · 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'.
X10 Duplicated predicate — 25 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X7 Silent fallback defaults — 7 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 1 control(s) we could not find positive evidence for
These checks grade a working control, and the repository shows no evidence of one. That is deliberately not scored as a zero: a repository cannot show an ops runbook, a database TTL or an infrastructure-side audit log, so absence of evidence here is not evidence the control is missing. It is also not a statement that the check is irrelevant to this codebase — the thing it grades applies; we just could not see it. Excluded from the score either way.
C5 Data-Subject Rights — Repo shows no corroborated data-subject-rights mechanism (erasure / export-portability / consent) tied to a subject id or GDPR vocabulary — absence of evidence is not evidence of a working control. A delete/anonymise identifier was seen but did not co-occur with GDPR vocabulary or a subject-id shape, so it was not credited (e.g. a save-slot DeleteAccount()). Implement erasure, data export/portability and consent tracking over the subject's records.
Not included — 41 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: NestJS makes a provider that injects a request-scoped one request-scoped itself (scope bubbles up the injection chain), and gives every consumer its own transient instance by contract.
AX2 Stateful singletons — Not applicable: PHP builds its object graph per request and shares none of it between requests. TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
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 14 — a file the compose project references is missing) — time="2026-10-26T16:53:52Z" level=warning msg="The \"DATABASE_URL\" variable is not set. Defaulting to a blank string." env file .env not found: stat .env: no such file or directory; 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.
D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
D21 Naming Consistency — Naming consistency is measured on C# only; JavaScript, PHP, TypeScript, html not measured.
D22 Internal API Consistency — API consistency is measured on C# only; the exposed TypeScript surface was not measured.
D24 Comment Value — D24 reads C# and Visual Basic comments only — this repository's production source is .php, .ts, .tsx, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
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.
D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.js,.ts), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
D4 Code Duplication — This repository's production source (.ts, .tsx) is not read by D4's token comparison, which compares .NET source: duplication in it is measured by R10 Code Duplication, the frontend lens's card running the same clone algorithm over the JS/TS token stream. Not scored here — read the R10 card for this repository's duplication.
D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
D44 Platform End-of-Life — Platform end-of-life not assessed — this repository declares no platform this pass reads
DM1 Aggregate boundaries — no aggregates detected — aggregate-boundary check not applicable
DM11 Constructible invalid state — no entities detected — construction-time invariants not assessable
DM2 Strongly-typed ids — no id-bearing domain types detected — strongly-typed-id adoption not assessable
DM3 Integration-event coupling — no integration events detected — coupling check not applicable
DM4 Rich vs anemic model — no data-bearing entities detected — rich-vs-anemic model not assessable
DM5 Encapsulated state — no domain entities found — DM5 grades how entities protect their state, and this repository declares none
DM6 Domain ↔ infrastructure boundary — this TypeScript/JavaScript repository maps no type to a persistence framework (TypeORM/Prisma/MikroORM/Sequelize/Mongoose), so DM6's domain↔infrastructure fusion read has no population to be taken over
DM7 Repository granularity — no repository abstraction detected (e.g. uses a document session)
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
P9 Domain vs controller coverage — coverage data present for 660 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 tinybench, mitata, benchmark.js, benny or vitest `bench(...)` calls in files that import them (or `*.bench.*` files), or one of those in a REDACTED, 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 applicable: TypeScript/JavaScript runs on a garbage-collected runtime that gives a program no allocation-control idiom to choose on a hot path — no pools, stack allocation or value types — so allocation awareness is not something this code can be rated on.
R5 Dependency Freshness — uses a bun 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.
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.
X26 Unsynchronised callback handoff — Not applicable: this check looks for a collection written by a callback on one thread while the body waiting on it touches it on another, and in this repository's languages no collection is reachable from two threads at once. PHP gives a request one thread of its own; the event-loop libraries (ReactPHP, Amp) run callbacks one at a time, and ext-parallel copies every value across its channels, so no array or collection is reachable from two threads at once. TypeScript/JavaScript runs every callback on the one thread that owns its objects: a callback runs only when the body waiting on it has yielded, never alongside it, and a worker thread receives a COPY of what it is sent. A SharedArrayBuffer carries raw bytes, never an Array, Map or Set, so no collection is reachable from two threads at once. Not a gap in the analyzer and not a finding about your code.
X27 Collection changed while being enumerated — not 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
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.
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.
AC1 · Text alternatives· <img> without a text alternative · ×40
<img> without a text alternative apps/web/public/country-flag-icons/3x2/index.html:50— 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 apps/web/public/country-flag-icons/3x2/index.html: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 apps/web/public/country-flag-icons/3x2/index.html:72— 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 apps/web/public/country-flag-icons/3x2/index.html: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 apps/web/public/country-flag-icons/3x2/index.html:94— 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 apps/web/public/country-flag-icons/3x2/index.html:105— 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 apps/web/public/country-flag-icons/3x2/index.html:116— 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 apps/web/public/country-flag-icons/3x2/index.html:127— 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 apps/web/public/country-flag-icons/3x2/index.html:138— 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 apps/web/public/country-flag-icons/3x2/index.html:149— 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 apps/web/public/country-flag-icons/3x2/index.html:160— 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 apps/web/public/country-flag-icons/3x2/index.html:171— 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 apps/web/public/country-flag-icons/3x2/index.html:182— 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 apps/web/public/country-flag-icons/3x2/index.html:193— 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 apps/web/public/country-flag-icons/3x2/index.html:204— 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 apps/web/public/country-flag-icons/3x2/index.html:215— 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 apps/web/public/country-flag-icons/3x2/index.html:226— 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 apps/web/public/country-flag-icons/3x2/index.html:237— 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 apps/web/public/country-flag-icons/3x2/index.html:248— 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 apps/web/public/country-flag-icons/3x2/index.html:259— 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 apps/web/public/country-flag-icons/3x2/index.html:270— 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 apps/web/public/country-flag-icons/3x2/index.html:281— 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 apps/web/public/country-flag-icons/3x2/index.html:292— 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 apps/web/public/country-flag-icons/3x2/index.html:303— 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 apps/web/public/country-flag-icons/3x2/index.html:314— An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
AC2 · Forms & labels· <label> that labels no control · ×14
<label> that labels no control apps/web/modules/blocklist/components/BlocklistEntryDetailsSheet.tsx:75— 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 apps/web/modules/blocklist/components/BlocklistEntryDetailsSheet.tsx:82— 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 apps/web/modules/blocklist/components/BlocklistEntryDetailsSheet.tsx:91— 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 apps/web/modules/blocklist/components/BlocklistEntryDetailsSheet.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 apps/web/modules/blocklist/components/BlocklistEntryDetailsSheet.tsx:109— 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 apps/web/modules/blocklist/components/BlocklistEntryDetailsSheet.tsx:118— 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 apps/web/modules/blocklist/components/BlocklistEntryDetailsSheet.tsx:126— 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 apps/web/modules/blocklist/components/BookingReportDetailsModal.tsx:87— 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 apps/web/modules/blocklist/components/BookingReportDetailsModal.tsx:93— 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 apps/web/modules/blocklist/components/BookingReportDetailsModal.tsx:102— 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 apps/web/modules/blocklist/components/BookingReportDetailsModal.tsx:110— 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 apps/web/modules/blocklist/components/BookingReportDetailsModal.tsx:115— 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 apps/web/modules/blocklist/components/BookingReportDetailsModal.tsx:120— 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 apps/web/modules/blocklist/components/BookingReportDetailsModal.tsx:125— 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.
<html> without a lang apps/web/app/global-error.tsx:15— The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
<html> without a lang apps/web/public/country-flag-icons/3x2/index.html:3— The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
<html> without a lang packages/embeds/embed-core/index.html:1— The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
<html> without a lang packages/embeds/embed-core/preview.html:1— The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
<html> without a lang packages/embeds/embed-react/element-click.html:1— The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
<html> without a lang packages/embeds/embed-react/floating.html:1— The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
<html> without a lang packages/embeds/embed-react/index.html:1— The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
<html> without a lang packages/embeds/embed-react/inline.html:1— The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
AC4 · Keyboard semantics· Click handler on a non-interactive <div> · ×8
Click handler on a non-interactive <div> apps/web/components/apps/installation/AccountsStepCard.tsx:43— 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> REDACTED:49— 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> apps/web/modules/bookings/components/DryRunMessage.tsx:13— 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> apps/web/modules/calendars/weeklyview/components/event/Empty.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 <div> packages/app-store/giphy/components/SearchDialog.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> packages/ui/components/editable-heading/EditableHeading.tsx:22— 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> packages/ui/components/form/inputs/TextField.tsx:86— 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> packages/ui/components/form/step/Steps.tsx:36— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
AC3 · Page structure· Document without a <title> · ×7
Document without a <title> apps/web/app/global-error.tsx:15— A page with no <title> gives no name in the tab, history or screen-reader page list. Declare it the way this router does — Next App Router `export const metadata = { title }`, React Router/Remix `export function meta`, TanStack Start `head`, or a Helmet/Head component.
Document without a <title> apps/web/app/layout.tsx:108— A page with no <title> gives no name in the tab, history or screen-reader page list. Declare it the way this router does — Next App Router `export const metadata = { title }`, React Router/Remix `export function meta`, TanStack Start `head`, or a Helmet/Head component.
Document without a <title> packages/embeds/embed-core/preview.html:1— 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> packages/embeds/embed-react/element-click.html:1— 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> packages/embeds/embed-react/floating.html:1— 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> packages/embeds/embed-react/index.html:1— 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> packages/embeds/embed-react/inline.html:1— A page with no <title> gives no name in the tab, history or screen-reader page list. Add a descriptive <title> in <head>.
AC2 · Forms & labels· <button> with no accessible text · ×6
<button> with no accessible text apps/web/components/apps/ics-feedcalendar/Setup.tsx:77— 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 apps/web/components/dialog/WrongAssignmentDialog.tsx:117— 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 apps/web/modules/apps/components/AllApps.tsx:91— 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 apps/web/modules/apps/components/AllApps.tsx:131— 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 apps/web/modules/bookings/components/event-meta/Duration.tsx:107— 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 apps/web/modules/bookings/components/event-meta/Duration.tsx:136— 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).
AC4 · Keyboard semantics· Click handler on a non-interactive <li> · ×3
Click handler on a non-interactive <li> apps/web/modules/apps/components/AllApps.tsx:102— 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> apps/web/modules/apps/components/AllApps.tsx:113— 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> apps/web/modules/bookings/components/event-meta/Duration.tsx:121— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
AC5 · ARIA correctness· aria-hidden hides a focusable element · ×3
aria-hidden hides a focusable element apps/web/app/(use-page-wrapper)/payment/[uid]/PaymentPage.tsx:103— aria-hidden="true" here hides the subtree from assistive tech, but a focusable descendant stays in the tab order — a keyboard user can land on a control screen readers can't see. Add inert, take the descendants out of the tab order (tabindex="-1"), or drop aria-hidden.
aria-hidden hides a focusable element REDACTED:498— aria-hidden="true" here hides the subtree from assistive tech, but a focusable descendant stays in the tab order — a keyboard user can land on a control screen readers can't see. Add inert, take the descendants out of the tab order (tabindex="-1"), or drop aria-hidden.
aria-hidden hides a focusable element packages/platform/atoms/event-types/payments/PaymentForm.tsx:57— aria-hidden="true" here hides the subtree from assistive tech, but a focusable descendant stays in the tab order — a keyboard user can land on a control screen readers can't see. Add inert, take the descendants out of the tab order (tabindex="-1"), or drop aria-hidden.
D30 · Dependency Vulnerabilities· High vulnerability · ×3
REDACTED
REDACTED
REDACTED
AC4 · Keyboard semantics· Clickable element isn't keyboard-operable · ×2
Clickable element isn't keyboard-operable apps/web/modules/event-types/views/event-types-listing-view.tsx:837— The repo's own CSS styles .cursor-pointer with `cursor: pointer`, so this <div> is a control — but it has no role, no tabIndex={0} and no key handler, so it can only be reached with a mouse. Use a <button>, or add role + tabIndex={0} + a key handler.
Clickable element isn't keyboard-operable apps/web/modules/settings/components/BookerLayoutSelector.tsx:189— The repo's own CSS styles .cursor-pointer with `cursor: pointer`, so this <img> is a control — but it has no role, no tabIndex={0} and no key handler, so it can only be reached with a mouse. Use a <button>, or add role + tabIndex={0} + a key handler.
Unlisted import 'dotenv' packages/embeds/vite.config.js:2— Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
Unlisted import 'dotenv' apps/web/cron-tester.ts:2— Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
S1 · Web-Security Posture· Password hashing without a KDF · ×2
Password hashing without a KDF apps/api/v2/src/platform/calendars/services/apple-calendar.service.ts:82— `decryptedKey.password === password` checks a password against the stored one in plaintext, so the store holds the password itself and whoever reads it holds every account.
Password hashing without a KDF packages/app-store/applecalendar/api/add.ts:37— `decryptedCredential.password === password` checks a password against the stored one in plaintext, so the store holds the password itself and whoever reads it holds every account.
Viewport restricts zoom apps/web/components/PageWrapper.tsx:67— user-scalable=no/0 or a maximum-scale below 2 stops low-vision users zooming to 200%. Remove the zoom restriction from the viewport meta.
AC3 · Page structure· <iframe> without a title · ×1
<iframe> without a title packages/features/embed/lib/EmbedTabs.tsx:200— An iframe with no title (or an empty one) is announced only as "frame". Add a non-empty title describing its content, or an aria-label.
AC4 · Keyboard semantics· Click handler on a non-interactive <span> · ×1
Click handler on a non-interactive <span> apps/web/components/ui/LimitedBadges.tsx:93— 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· Hover-only interaction on <div> · ×1
Hover-only interaction on <div> apps/web/modules/calendars/weeklyview/components/event/EventList.tsx:108— 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.
Focusable <div> isn't keyboard-operable packages/ui/components/editor/plugins/ToolbarPlugin.tsx:211— This <div> carries tabIndex={0}, so it is in the tab order and a keyboard user will land on it — but its behaviour is bound to the pointer only, with no key handler. A tabindex makes an element focusable, not operable: Enter and Space fire a click on a native <button> or <a href> and nowhere else, so this can be focused and never activated. Use a <button>, or handle Enter/Space in a key handler.
D11 · Test Reliability· Test suite declares a test script but contains no test files · ×1
Test suite declares a test script but contains no test files: packages/platform/atoms/ — The jest suite in packages/platform/atoms/ was installed and launched successfully, and the runner then found no test files to run — No tests found, exiting with code 1. The package declares a test script, so it reads as a tested package to anyone who checks its manifest, but there is nothing behind the declaration: no test case exists, so it cannot detect a regression and its presence overstates how much of this repository is tested. The ask is the owner's: write the first test for this package, or remove the test script from a package that has none. This is not a report that the tests FAIL — there are none.
Unlisted import 'express' apps/api/v2/src/bootstrap.ts:16— Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
Unlisted import 'googleapis-common' apps/api/v2/src/modules/apps/services/gcal.service.ts:3— Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
Unlisted import 'kysely' apps/api/v2/src/modules/kysely/kysely-read.service.ts:4— Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
Unlisted import '@formbricks/js' apps/web/modules/formbricks/hooks/useFormbricks.ts:1— Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
Unlisted import '@getalby/sdk' apps/web/components/apps/alby/Setup.tsx:1— Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
Unlisted import '@tanstack/react-table' apps/web/app/(use-page-wrapper)/settings/(admin-layout)/admin/playground/date-range-filter/page.tsx:5— Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
Unlisted import '@tanstack/react-virtual' apps/web/modules/data-table/components/DataTable.tsx:20— Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
Unlisted import '@testing-library/user-event' apps/web/modules/signup-view.test.tsx:3— Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
Unlisted import '@trpc/client' apps/web/app/_trpc/query-client.ts:5— Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
Unlisted import '@trpc/react-query' apps/web/app/_trpc/trpc.ts:5— Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
Unlisted import 'class-variance-authority' apps/web/modules/calendars/weeklyview/components/event/Event.tsx:6— Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
Unlisted import 'date-fns' apps/web/modules/blocklist/components/BlocklistEntryDetailsSheet.tsx:3— Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
Unlisted import 'framer-motion' apps/web/modules/auth/verify-view.tsx:11— Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
Unlisted import 'js-yaml' apps/web/lib/apps/[slug]/getStaticProps.ts:4— Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
Unlisted import 'lucide-react' apps/web/modules/auth/login-view.tsx:23— Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
Unlisted import 'REDACTED' apps/web/app/api/version/route.ts:3— Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
Unlisted import 'react-error-boundary' apps/web/components/error/BookingPageErrorBoundary.tsx:3— Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
Unlisted import 'react-inlinesvg' apps/web/app/providers.tsx:5— Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
Unlisted import 'react-qr-code' apps/web/components/apps/alby/AlbyPaymentComponent.tsx:13— Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
Unlisted import 'react-sticky-box' apps/web/modules/bookings/components/Booker.tsx:37— Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
TLS certificate validation disabled packages/app-store/exchangecalendar/lib/CalendarService.ts:204— `rejectUnauthorized: false` is set on a TLS client, so every peer certificate is accepted — including one an attacker presents. Chain, expiry, revocation and hostname are all skipped, so an attacker on the network path can present any certificate and read or rewrite the traffic — the connection is encrypted to the attacker, not to the intended host. Remove the option so Node validates the peer. If the server presents a self-signed or privately-issued certificate, trust THAT issuer rather than every certificate: pass its CA as `ca` (or set `NODE_EXTRA_CA_CERTS`), which keeps the chain and hostname checks on. A managed database or broker that documents `rejectUnauthorized: false` publishes a CA bundle for exactly this purpose.
S1 · Web-Security Posture· Cryptographic key material is a compile-time constant · ×1
Cryptographic key material is a compile-time constant packages/lib/videoTokens.ts:5— `CAL_VIDEO_RECORDING_TOKEN_SECRET` is the MAC key, and its shipped DEFAULT is a compile-time constant — an installation that never overrides it encrypts with a value published in this repository, and the code cannot distinguish that state from a configured one. A key that ships with the source is not secret: every contributor, fork, mirror and released binary carries it, so anyone holding the repository can decrypt what any installation encrypted, and there is no way to invalidate what was already protected because every deployment built from this source shares the value. Where the constant is a password salt the consequence differs but is no smaller — one global salt means precomputation amortises across every installation, which is the property salting exists to destroy. Read the value from configuration, an environment variable or a secrets manager at startup and FAIL FAST when it is absent, so a missing key stops the process instead of silently falling back to a shared default; treat the committed value as disclosed and rotate it rather than only deleting the line. For a salt, generate a fresh random one per password and store it alongside the hash.
TodoComment vitest.workspace.ts:49— // TODO: Ignore the api until tests are fixed — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment packages/ui/components/navigation/tabs/VerticalTabItem.tsx:92— // TODO: I don't think having apps-info as a data-test-id is right here as this is meant to be dumb component. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment packages/ui/components/form/select/Select.tsx:223— // TODO:Not able to get focus to work — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment packages/features/form/components/Select.tsx:183— // TODO:Not able to get focus to work — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment packages/ui/components/button/button.test.tsx:39— // TODO: (SEAN) Fix tests for button component. Seems to be a change in the way vitest/react-testing-library is working with the DOM. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment packages/trpc/server/createContext.ts:97— // TODO: @sean - figure out a way to make getIP be happy with trpc req. params — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment packages/trpc/server/routers/viewer/users/_router.ts:59— // TODO: Add search, pagination, etc. — 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 REDACTED:1305— // TODO: Also, handleNewBooking only seems to be using eventType?.schedule?.timeZone which seems to confirm that we should simplify it as well. — 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 REDACTED:1363— // TODO: Perf Optimization: Slots calculation logic already seems to consider the minimum booking notice and past booking time and thus there shouldn't be need to filter out slots here. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment packages/trpc/server/routers/viewer/me/getUserTopBanners.handler.ts:30— // TODO: Call top buildNonDelegationCredentials here can be avoided by moving credential prisma query to repository. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment packages/trpc/server/routers/viewer/bookings/confirm.handler.test.ts:3— // TODO: Bring this test back with the correct setup (no illegal imports) — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment packages/trpc/server/routers/viewer/bookings/editLocation.handler.test.ts:3— // TODO: Bring this test back with the correct setup (no illegal imports) — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment packages/trpc/server/routers/viewer/bookings/confirm.handler.ts:238— // TODO: Remove the usage of `bookingFields` in computing responses. We can do that by storing `label` with the response. Also, this would allow us to correctly show the label for a field even after the Event Type has been deleted. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment packages/trpc/server/routers/viewer/bookings/get.handler.ts:367— // TODO: write makeWhereClause equivalent for kysely — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment packages/trpc/server/routers/viewer/bookings/get.handler.ts:386— // TODO: write makeWhereClause equivalent for kysely — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment packages/trpc/server/routers/viewer/availability/team/listTeamAvailability.handler.ts:195— // Get all users TODO: — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment packages/trpc/server/routers/viewer/apps/listLocal.handler.ts:70— // TODO: Why don't we parse with schema here? Not doing it makes default() not work in schema. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment packages/trpc/server/routers/viewer/apps/toggle.handler.ts:77— // TODO: This should be done async probably using a queue. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment packages/trpc/server/routers/viewer/apps/toggle.handler.ts:120— // TODO: This should be done async probably using a queue. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment packages/trpc/server/routers/viewer/apps/toggle.handler.ts:123— // TODO: This update query can be removed by merging it with — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment packages/trpc/server/routers/publicViewer/markHostAsNoShow.handler.ts:9— // TODO: Track which attendee actually called this endpoint to mark host as no-show. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment packages/trpc/react/trpc.ts:25— // TODO: Update our trpc routes so they are more clear. — 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 apps/web/app/_trpc/trpc-client.ts:13— // TODO: Update our trpc routes so they are more clear. — 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 REDACTED:21— // TODO: We shouldn't need to implement adding a row to Payment table but that's a requirement right now. — 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 REDACTED:70— // TODO: App implementing PaymentService is supposed to send email by itself at the moment. — 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.
FunctionTooLong: RegularBookingService.handler packages/features/bookings/lib/service/RegularBookingService.ts:486— FunctionTooLong — handler runs 1470 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 1370 over it, 14.70× 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: EventAdvancedTab.EventAdvancedTab apps/web/modules/event-types/components/tabs/advanced/EventAdvancedTab.tsx:404— FunctionTooLong — EventAdvancedTab runs 948 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 848 over it, 9.48× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: signup-view.Signup apps/web/modules/signup-view.tsx:192— FunctionTooLong — Signup runs 561 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 461 over it, 5.61× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: next-auth-options.getOptions packages/features/auth/lib/next-auth-options.ts:374— FunctionTooLong — getOptions runs 533 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 433 over it, 5.33× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: Embed.EmbedTypeCodeAndPreviewDialogContent REDACTED:699— FunctionTooLong — EmbedTypeCodeAndPreviewDialogContent runs 531 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 431 over it, 5.31× 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: get.handler.getBookings packages/trpc/server/routers/viewer/bookings/get.handler.ts:93— FunctionTooLong — getBookings runs 525 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 425 over it, 5.25× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: BookingActionsDropdown.BookingActionsDropdown apps/web/components/booking/actions/BookingActionsDropdown.tsx:63— FunctionTooLong — BookingActionsDropdown runs 500 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 400 over it, 5.00× 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: event-types-listing-view.InfiniteEventTypeList apps/web/modules/event-types/views/event-types-listing-view.tsx:280— FunctionTooLong — InfiniteEventTypeList runs 481 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 381 over it, 4.81× 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: Booker.BookerComponent apps/web/modules/bookings/components/Booker.tsx:55— FunctionTooLong — BookerComponent runs 476 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 376 over it, 4.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: update.handler.updateHandler packages/trpc/server/routers/viewer/eventTypes/heavy/update.handler.ts:60— FunctionTooLong — updateHandler runs 475 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 375 over it, 4.75× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: seed.main REDACTED:634— FunctionTooLong — main runs 472 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 372 over it, 4.72× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: UserListTable.UserListTableContent apps/web/modules/users/components/UserTable/UserListTable.tsx:171— FunctionTooLong — UserListTableContent runs 465 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 365 over it, 4.65× 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: EventTypeAppCardInterface.EventTypeAppCard packages/app-store/salesforce/components/EventTypeAppCardInterface.tsx:24— FunctionTooLong — EventTypeAppCard runs 415 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 315 over it, 4.15× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: EventLimitsTab.EventLimitsTab packages/features/eventtypes/components/tabs/limits/EventLimitsTab.tsx:400— FunctionTooLong — EventLimitsTab runs 409 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 309 over it, 4.09× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: BookerPlatformWrapper.BookerPlatformWrapperComponent packages/platform/atoms/booker/BookerPlatformWrapper.tsx:50— FunctionTooLong — BookerPlatformWrapperComponent runs 408 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 308 over it, 4.08× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: WriteToObjectSettings.WriteToObjectSettings packages/app-store/salesforce/components/components/WriteToObjectSettings.tsx:22— FunctionTooLong — WriteToObjectSettings runs 393 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 293 over it, 3.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: WriteToObjectSettings.WriteToObjectSettings packages/app-store/_components/crm/WriteToObjectSettings.tsx:22— FunctionTooLong — WriteToObjectSettings runs 378 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 278 over it, 3.78× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: AppPage.AppPage apps/web/components/apps/AppPage.tsx:66— FunctionTooLong — AppPage runs 351 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 251 over it, 3.51× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: BookingListItem.BookingListItem apps/web/components/booking/BookingListItem.tsx:130— FunctionTooLong — BookingListItem runs 350 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 250 over it, 3.50× 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: CreateOrEditOutOfOfficeModal.CreateOrEditOutOfOfficeEntryModal apps/web/modules/settings/outOfOffice/CreateOrEditOutOfOfficeModal.tsx:32— FunctionTooLong — CreateOrEditOutOfOfficeEntryModal runs 329 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 229 over it, 3.29× 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: confirm.handler.confirmHandler packages/trpc/server/routers/viewer/bookings/confirm.handler.ts:51— FunctionTooLong — confirmHandler runs 317 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 217 over it, 3.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: EventSetupTab.EventSetupTab apps/web/modules/event-types/components/tabs/setup/EventSetupTab.tsx:66— FunctionTooLong — EventSetupTab runs 314 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 214 over it, 3.14× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: handleConfirmation.handleConfirmation packages/features/bookings/lib/handleConfirmation.ts:23— FunctionTooLong — handleConfirmation runs 311 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 211 over it, 3.11× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: handleCancelBooking.handler packages/features/bookings/lib/handleCancelBooking.ts:81— FunctionTooLong — handler runs 310 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 210 over it, 3.10× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: MultiplePrivateLinksController.MultiplePrivateLinksController apps/web/modules/event-types/components/MultiplePrivateLinksController.tsx:24— FunctionTooLong — MultiplePrivateLinksController runs 307 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 207 over it, 3.07× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FileTooLong: service/RegularBookingService.ts packages/features/bookings/lib/service/RegularBookingService.ts— FileTooLong — 1937 significant lines (blank, comment-only and punctuation-only lines excluded), about 76% of them inside a single declaration: handler (486-2578). The bar is 500 significant lines; this is 1437 over it, 3.87× 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: REDACTED REDACTED— FileTooLong — 1657 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 1157 over it, 3.31× 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: repositories/BookingRepository.ts packages/features/bookings/repositories/BookingRepository.ts— FileTooLong — 1513 significant lines (blank, comment-only and punctuation-only lines excluded), about 82% of them inside a single declaration: BookingRepository (340-2173). The bar is 500 significant lines; this is 1013 over it, 3.03× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: repositories/eventTypeRepository.ts packages/features/eventtypes/repositories/eventTypeRepository.ts— FileTooLong — 1303 significant lines (blank, comment-only and punctuation-only lines excluded), about 95% of them inside a single declaration: EventTypeRepository (81-1886). The bar is 500 significant lines; this is 803 over it, 2.61× 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: advanced/EventAdvancedTab.tsx apps/web/modules/event-types/components/tabs/advanced/EventAdvancedTab.tsx— FileTooLong — 1292 significant lines (blank, comment-only and punctuation-only lines excluded), about 73% of them inside a single declaration: EventAdvancedTab (404-1527). The bar is 500 significant lines; this is 792 over it, 2.58× 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: REDACTED packages/app-store/salesforce/lib/CrmService.ts— FileTooLong — 1268 significant lines (blank, comment-only and punctuation-only lines excluded), about 92% of them inside a single declaration: SalesforceCRMService (114-1930). The bar is 500 significant lines; this is 768 over it, 2.54× 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: REDACTED REDACTED— FileTooLong — 1198 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 698 over it, 2.40× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: REDACTED REDACTED— FileTooLong — 1127 significant lines (blank, comment-only and punctuation-only lines excluded), about 90% of them inside a single declaration: UserRepository (124-1665). The bar is 500 significant lines; this is 627 over it, 2.25× 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: REDACTED REDACTED— FileTooLong — 1116 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 616 over it, 2.23× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: REDACTED REDACTED— FileTooLong — 1030 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 530 over it, 2.06× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: REDACTED REDACTED— FileTooLong — 997 significant lines (blank, comment-only and punctuation-only lines excluded), about 88% of them inside a single declaration: AvailableSlotsService (143-1435). The bar is 500 significant lines; this is 497 over it, 1.99× 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: booking/BookingListItem.tsx apps/web/components/booking/BookingListItem.tsx— FileTooLong — 972 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 472 over it, 1.94× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: REDACTED REDACTED— FileTooLong — 891 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 391 over it, 1.78× 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: bookingScenario/expects.ts packages/testing/src/lib/bookingScenario/expects.ts— FileTooLong — 889 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 389 over it, 1.78× 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: limits/EventLimitsTab.tsx packages/features/eventtypes/components/tabs/limits/EventLimitsTab.tsx— FileTooLong — 870 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 370 over it, 1.74× 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: services/bookings.service.ts apps/api/v2/src/platform/bookings/2024-08-13/services/bookings.service.ts— FileTooLong — 851 significant lines (blank, comment-only and punctuation-only lines excluded), about 90% of them inside a single declaration: BookingsService_2024_08_13 (90-1222). 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: components/BookingDetailsSheet.tsx apps/web/modules/bookings/components/BookingDetailsSheet.tsx— FileTooLong — 839 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 339 over it, 1.68× 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: views/event-types-listing-view.tsx apps/web/modules/event-types/views/event-types-listing-view.tsx— FileTooLong — 837 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 337 over it, 1.67× 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: lib/EventManager.ts packages/features/bookings/lib/EventManager.ts— FileTooLong — 831 significant lines (blank, comment-only and punctuation-only lines excluded), about 89% of them inside a single declaration: EventManager (133-1349). The bar is 500 significant lines; this is 331 over it, 1.66× 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: advanced/FormBuilder.tsx apps/web/modules/event-types/components/tabs/advanced/FormBuilder.tsx— FileTooLong — 829 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 329 over it, 1.66× 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: bookings/get.handler.ts packages/trpc/server/routers/viewer/bookings/get.handler.ts— FileTooLong — 807 significant lines (blank, comment-only and punctuation-only lines excluded), about 65% of them inside a single declaration: getBookings (93-794). The bar is 500 significant lines; this is 307 over it, 1.61× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: lib/next-auth-options.ts packages/features/auth/lib/next-auth-options.ts— FileTooLong — 793 significant lines (blank, comment-only and punctuation-only lines excluded), about 67% of them inside a single declaration: getOptions (374-1211). The bar is 500 significant lines; this is 293 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: REDACTED REDACTED— FileTooLong — 775 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 275 over it, 1.55× 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: prisma/zod-utils.ts packages/prisma/zod-utils.ts— FileTooLong — 745 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 245 over it, 1.49× 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: availability/EventAvailabilityTab.tsx apps/web/modules/event-types/components/tabs/availability/EventAvailabilityTab.tsx— FileTooLong — 729 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 229 over it, 1.46× 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.
+ 23 more in this group — see findings.md.
D30 · Dependency Vulnerabilities· Medium CVE · ×48
No assertions: toggles bold formatting when bold button is clicked packages/ui/components/editor/plugins/ToolbarPlugin.test.tsx:130— 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, 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: toggles italic formatting when italic button is clicked packages/ui/components/editor/plugins/ToolbarPlugin.test.tsx:141— 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, 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: toggles link when link button is clicked packages/ui/components/editor/plugins/ToolbarPlugin.test.tsx:152— 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, 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: checkUndefinedInValue should not throw exception when the where object does not contain undefined values packages/prisma/extensions/disallow-undefined-delete-update-many.test.ts:28— 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, 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: checkUndefinedInValue should not throw exception when the where object contain null values packages/prisma/extensions/disallow-undefined-delete-update-many.test.ts:39— 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, 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 trigger guest no show webhook when no one joined the call packages/features/tasker/tasks/triggerNoShow/triggerGuestNoShow.test.ts:42— 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, 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 trigger guest no show webhook when guest didn't joined the call packages/features/tasker/tasks/triggerNoShow/triggerGuestNoShow.test.ts:205— 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, 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 trigger guest no show webhook when host didn't joined the rescheduled call packages/features/tasker/tasks/triggerNoShow/triggerGuestNoShow.test.ts:396— 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, 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 send updated attendees with noShow=true in webhook payload packages/features/tasker/tasks/triggerNoShow/triggerGuestNoShow.test.ts:778— 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, 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 trigger host no show webhook when no one joined the call packages/features/tasker/tasks/triggerNoShow/triggerHostNoShow.test.ts:42— 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, 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 trigger host no show webhook when host didn't joined the call packages/features/tasker/tasks/triggerNoShow/triggerHostNoShow.test.ts:184— 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, 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 trigger host no show webhook when host didn't joined the rescheduled call packages/features/tasker/tasks/triggerNoShow/triggerHostNoShow.test.ts:352— 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, 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 send updated attendees with noShow=true when host in attendees table doesn't join packages/features/tasker/tasks/triggerNoShow/triggerHostNoShow.test.ts:560— 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, 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: If the contact exists, create the event packages/features/crmManager/crmManager.test.ts:47— 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, 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 allow a booking if there is no conflicting booking in any of the users' selectedCalendars packages/features/bookings/lib/handleNewBooking/test/dynamic-group-booking.test.ts:43— 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, 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 create a successful booking with Zoom if used packages/features/bookings/lib/handleNewBooking/test/fresh-booking.test.ts:1470— 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, 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 create a booking with UTM tracking packages/features/bookings/lib/handleNewBooking/test/fresh-booking.test.ts:1714— 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, 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 allow a booking even if there is already a booking in the organizer's selectedCalendars(Single Calendar) with the overlapping time but useEventLevelSelectedCalendars is false and SelectedCalendar is for an event packages/features/bookings/lib/handleNewBooking/test/fresh-booking.test.ts:2038— 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, 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 allow a booking even if there is already a booking in the organizer's selectedCalendars(Single Calendar) with the overlapping time and useEventLevelSelectedCalendars is true but the selectedCalendar is of different eventType packages/features/bookings/lib/handleNewBooking/test/fresh-booking.test.ts:2202— 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, 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 make a fresh booking in PENDING state even when the booker is the organizer of the event-type 1. Should create a booking in the database with status PENDING 2. Should send emails to the booker as well as organizer for booking request and awaiting approval 3. Should trigger BOOKING_REQUESTED webhook packages/features/bookings/lib/handleNewBooking/test/fresh-booking.test.ts:2413— 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, 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: an error in updating a calendar event should not stop the rescheduling - Current behaviour is wrong as the booking is resheduled but no-one is notified of it packages/features/bookings/lib/handleNewBooking/test/reschedule.test.ts:492— 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, 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: when event type does NOT require confirmation, attendee reschedule of paid event creates a PENDING booking (payment handling removed) 1. Should cancel the existing booking 2. Should create a new booking in PENDING state (no payment processing available) 3. Should send rescheduled emails and trigger BOOKING_RESCHEDULED webhook packages/features/bookings/lib/handleNewBooking/test/reschedule.test.ts:1775— 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, 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: when event type DOES require confirmation, attendee reschedule of paid event needs host confirmation 1. Should cancel the existing booking and delete video/calendar events 2. Should create a new booking in PENDING state (host must confirm) 3. Should send BOOKING_REQUESTED emails and trigger BOOKING_REQUESTED webhook packages/features/bookings/lib/handleNewBooking/test/reschedule.test.ts:1952— 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, 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 call queueBookingRequestedWebhook when event type requires confirmation packages/features/bookings/lib/handleNewBooking/test/webhook-producer-booking-requested.test.ts:86— 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, 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 call queueBookingRequestedWebhook even when booker is the organizer packages/features/bookings/lib/handleNewBooking/test/webhook-producer-booking-requested.test.ts:167— 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, 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.
Boundary violation [package:third-party-deep-import] apps/web/app/api/defaultResponderForAppDir.ts:2— apps/web/app/api/defaultResponderForAppDir.ts:2 imports next/dist/server/api-utils, 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] apps/web/app/icons/page.tsx:9— apps/web/app/icons/page.tsx:9 reaches into another package with a relative path (../../../../packages/ui/components/icon/icon-list.mjs) — import the package by name instead.
Boundary violation [package:relative-cross-package] apps/web/components/apps/DestinationCalendarSettingsWebWrapper.tsx:9— apps/web/components/apps/DestinationCalendarSettingsWebWrapper.tsx:9 reaches into another package with a relative path (../../../../packages/platform/atoms/destination-calendar/DestinationCalendar) — import the package by name instead.
Boundary violation [package:relative-cross-package] apps/web/components/apps/DestinationCalendarSettingsWebWrapper.tsx:10— apps/web/components/apps/DestinationCalendarSettingsWebWrapper.tsx:10 reaches into another package with a relative path (../../../../packages/platform/atoms/src/components/atoms-wrapper) — import the package by name instead.
Boundary violation [package:deep-import] apps/web/modules/auth/setup-view.tsx:11— apps/web/modules/auth/setup-view.tsx:11 imports @calcom/ui/components/form/wizard/WizardForm, which the target package's REDACTED `exports` does not declare — use a declared entry or declare the subpath.
Boundary violation [package:relative-cross-package] apps/web/modules/bookings/components/EventMeta.tsx:20— apps/web/modules/bookings/components/EventMeta.tsx:20 reaches into another package with a relative path (../../../../../i18n.json) — import the package by name instead.
Boundary violation [package:relative-cross-package] apps/web/modules/event-types/components/AddVerifiedEmail.tsx:11— apps/web/modules/event-types/components/AddVerifiedEmail.tsx:11 reaches into another package with a relative path (../../../../../packages/platform/atoms/event-types/hooks/useAddVerifiedEmail) — import the package by name instead.
Boundary violation [package:relative-cross-package] apps/web/modules/event-types/components/AddVerifiedEmail.tsx:12— apps/web/modules/event-types/components/AddVerifiedEmail.tsx:12 reaches into another package with a relative path (../../../../../packages/platform/atoms/event-types/hooks/useGetVerifiedEmails) — import the package by name instead.
Boundary violation [package:relative-cross-package] apps/web/modules/event-types/components/AddVerifiedEmail.tsx:13— apps/web/modules/event-types/components/AddVerifiedEmail.tsx:13 reaches into another package with a relative path (../../../../../packages/platform/atoms/hooks/useVerifyCode) — import the package by name instead.
Boundary violation [package:relative-cross-package] apps/web/modules/event-types/components/AddVerifiedEmail.tsx:14— apps/web/modules/event-types/components/AddVerifiedEmail.tsx:14 reaches into another package with a relative path (../../../../../packages/platform/atoms/hooks/useVerifyEmail) — import the package by name instead.
Boundary violation [package:relative-cross-package] apps/web/modules/event-types/components/EventTypeLayout.tsx:31— apps/web/modules/event-types/components/EventTypeLayout.tsx:31 reaches into another package with a relative path (../../../../../packages/platform/atoms/src/components/ui/shell) — import the package by name instead.
Boundary violation [package:undeclared-workspace-dep] packages/app-store/AppDependencyComponent.tsx:6— packages/app-store/AppDependencyComponent.tsx:6 imports @coss/ui/icons, a package this repository publishes, but this package's own REDACTED does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies.
Boundary violation [package:undeclared-workspace-dep] packages/app-store/_appRegistry.ts:6— packages/app-store/_appRegistry.ts:6 imports @calcom/prisma, a package this repository publishes, but this package's own REDACTED does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies.
Boundary violation [package:undeclared-workspace-dep] packages/app-store/_appRegistry.ts:7— packages/app-store/_appRegistry.ts:7 imports @calcom/prisma/zod-utils, a package this repository publishes, but this package's own REDACTED does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies.
Boundary violation [package:undeclared-workspace-dep] packages/app-store/_components/AppCard.tsx:6— packages/app-store/_components/AppCard.tsx:6 imports @calcom/atoms/hooks/useIsPlatform, a package this repository publishes, but this package's own REDACTED does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies.
Boundary violation [package:relative-cross-package] packages/app-store/_pages/setup/_getServerSideProps.tsx:4— packages/app-store/_pages/setup/_getServerSideProps.tsx:4 reaches into another package with a relative path (../../alby/pages/setup/_getServerSideProps) — import the package by name instead.
Boundary violation [package:relative-cross-package] packages/app-store/_pages/setup/_getServerSideProps.tsx:5— packages/app-store/_pages/setup/_getServerSideProps.tsx:5 reaches into another package with a relative path (../../make/pages/setup/_getServerSideProps) — import the package by name instead.
Boundary violation [package:relative-cross-package] packages/app-store/_pages/setup/_getServerSideProps.tsx:6— packages/app-store/_pages/setup/_getServerSideProps.tsx:6 reaches into another package with a relative path (../../stripepayment/pages/setup/_getServerSideProps) — import the package by name instead.
Boundary violation [package:relative-cross-package] packages/app-store/_pages/setup/_getServerSideProps.tsx:7— packages/app-store/_pages/setup/_getServerSideProps.tsx:7 reaches into another package with a relative path (../../hitpay/pages/setup/_getServerSideProps) — import the package by name instead.
Boundary violation [package:relative-cross-package] packages/app-store/_pages/setup/_getServerSideProps.tsx:8— packages/app-store/_pages/setup/_getServerSideProps.tsx:8 reaches into another package with a relative path (../../btcpayserver/pages/setup/_getServerSideProps) — import the package by name instead.
Boundary violation [package:undeclared-workspace-dep] packages/app-store/_utils/bulkUpdateEventsToDefaultLocation.ts:3— packages/app-store/_utils/bulkUpdateEventsToDefaultLocation.ts:3 imports @calcom/prisma/zod-utils, a package this repository publishes, but this package's own REDACTED does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies.
Boundary violation [package:undeclared-workspace-dep] packages/app-store/_utils/bulkUpdateTeamEventsToDefaultLocation.ts:2— packages/app-store/_utils/bulkUpdateTeamEventsToDefaultLocation.ts:2 imports @calcom/prisma/zod-utils, a package this repository publishes, but this package's own REDACTED does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies.
Boundary violation [package:relative-cross-package] packages/app-store/_utils/calendars/processExternalId.ts:3— packages/app-store/_utils/calendars/processExternalId.ts:3 reaches into another package with a relative path (../../office365calendar) — import the package by name instead.
Boundary violation [package:undeclared-workspace-dep] packages/app-store/_utils/findValidApiKey.ts:2— packages/app-store/_utils/findValidApiKey.ts:2 imports @calcom/prisma, a package this repository publishes, but this package's own REDACTED does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies.
Boundary violation [package:undeclared-workspace-dep] packages/app-store/_utils/getAppKeysFromSlug.ts:1— packages/app-store/_utils/getAppKeysFromSlug.ts:1 imports @calcom/prisma, a package this repository publishes, but this package's own REDACTED does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies.
+ 15 more in this group — see findings.md.
R4 · Test Coverage· No test reaches this file · ×40
No test reaches this file apps/api/v2/src/platform/event-types/event-types_2024_06_14/controllers/event-types.controller.e2e-spec.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 REDACTED:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file REDACTED:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file apps/web/components/booking/BookingListItem.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/web/modules/bookings/components/BookingDetailsSheet.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/web/modules/event-types/views/event-types-listing-view.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/web/modules/signup-view.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 packages/embeds/embed-core/playground/lib/playground.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file apps/web/modules/users/components/UserTable/UserListTable.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/web/modules/settings/my-account/profile-view.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/api/v2/src/modules/slots/slots-2024-04-15/controllers/slots.controller.e2e-spec.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file apps/api/v2/src/modules/auth/oauth2/controllers/oauth2.controller.e2e-spec.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file apps/web/components/booking/actions/BookingActionsDropdown.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/api/v2/src/platform/bookings/2024-04-15/controllers/bookings.controller.e2e-spec.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file apps/web/modules/webhooks/components/WebhookForm.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/web/app/(use-page-wrapper)/settings/(settings-layout)/SettingsLayoutAppDirClient.tsx:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file REDACTED:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file apps/web/lib/apps/installation/[[...step]]/getServerSideProps.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 packages/app-store-cli/src/build.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file apps/web/modules/data-table/components/DataTable.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 scripts/seed-booking-audit.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file apps/web/components/apps/AppPage.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/web/modules/booking-audit/components/BookingHistory.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 packages/features/booking-audit/lib/service/BookingAuditTaskerProducerService.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 packages/app-store/dailyvideo/lib/scripts/deleteRecordings.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.
+ 15 more in this group — see findings.md.
X2 · Cancellation propagation· Async function without AbortSignal · ×39
Async function without AbortSignal: refreshTokens packages/platform/atoms/lib/http.ts:57— `refreshTokens` 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: refreshAccessToken packages/lib/CloseCom.ts:247— `refreshAccessToken` 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: _request packages/lib/CloseCom.ts:460— `_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: http packages/lib/fetch-wrapper.ts:3— `http` 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: fetchUsername packages/lib/fetchUsername.ts:8— `fetchUsername` 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: checkCfTurnstileToken packages/lib/server/checkCfTurnstileToken.ts:7— `checkCfTurnstileToken` 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: isBlacklisted packages/lib/server/username.ts:40— `isBlacklisted` 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: fetchHolidays packages/lib/holidays/GoogleCalendarClient.ts:47— `fetchHolidays` 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: api packages/lib/domainManager/deploymentServices/cloudflare.ts:175— `api` 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: createDomain packages/lib/domainManager/deploymentServices/vercel.ts:21— `createDomain` 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: deleteDomain packages/lib/domainManager/deploymentServices/vercel.ts:57— `deleteDomain` 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: handleWebhookScheduledTriggers packages/features/webhooks/lib/handleWebhookScheduledTriggers.ts:8— `handleWebhookScheduledTriggers` 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: _sendPayload packages/features/webhooks/lib/sendPayload.ts:301— `_sendPayload` 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: sendWebhookDirectly packages/features/webhooks/lib/service/WebhookService.ts:75— `sendWebhookDirectly` 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: request packages/features/calendar-subscription/adapters/Office365CalendarSubscription.adapter.ts:233— `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: downloadImageDataFromUrl packages/features/auth/signup/utils/prefillAvatar.ts:12— `downloadImageDataFromUrl` 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: fetchSignup packages/features/auth/signup/lib/fetchSignup.ts:28— `fetchSignup` 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: REDACTED packages/features/auth/lib/next-auth-options.ts:418— `REDACTED` 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: submitResponseAndGetRoutingResult REDACTED:142— `submitResponseAndGetRoutingResult` 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: getNodeMailerPayload packages/emails/templates/attendee-daily-video-download-transcript-email.ts:24— `getNodeMailerPayload` 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: getNodeMailerPayload packages/emails/templates/organizer-daily-video-download-transcript-email.ts:23— `getNodeMailerPayload` 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: fetchNewTokenObject packages/app-store/zoomvideo/lib/VideoApiAdapter.ts:391— `fetchNewTokenObject` 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: createContacts REDACTED:62— `createContacts` awaits `axios(…)` 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(url, { signal })`.
Async function without AbortSignal: getContacts REDACTED:94— `getContacts` awaits `axios(…)` 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(url, { signal })`.
Async function without AbortSignal: updateMeeting REDACTED:159— `updateMeeting` awaits `axios(…)` 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(url, { signal })`.
FixmeComment packages/ui/components/form/inputs/Form.tsx:29— // FIXME: Booking Pages don't have toast, so this error is never shown — 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.
FixmeComment packages/trpc/server/createNextApiHandler.ts:64— // FIXME: Using `max-age=1, stale-while-revalidate=60` fails some booking tests. — 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.
FixmeComment packages/trpc/server/routers/viewer/slots/reserveSlot.handler.ts:80— // FIXME: In case of team event, users doesn't have assignees, those are in hosts. users just have the creator of the event which is wrong. — 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.
FixmeComment packages/trpc/server/routers/viewer/bookings/confirm.handler.ts:317— // FIXME: It might be best to retrieve recurringEventId from the booking itself. — 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.
FixmeComment packages/trpc/server/routers/viewer/bookings/requestReschedule.handler.ts:173— // FIXME: error-handling — 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.
FixmeComment packages/testing/src/lib/bookingScenario/expects.ts:1012— // FIXME: File this bug and link ticket here. This is a bug in the code. metadata must be sent here like other BOOKING_CREATED webhook — 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.
FixmeComment packages/prisma/index.ts:74— // FIXME: Due to some reason, there are types failing in certain places due to the $extends. Fix it and then enable it — 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.
FixmeComment packages/lib/errors.ts:57— // FIXME: I don't know why we are handling gzipped case separately. This should be handled by fetch itself. — 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.
FixmeComment packages/features/eventtypes/components/tabs/limits/EventLimitsTab.tsx:1068— // @ts-expect-error FIXME Fix these typings — 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.
FixmeComment packages/features/busyTimes/services/getBusyTimes.ts:472— // FIXME: bookings that overlap on one side will never be counted — 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.
FixmeComment packages/features/bookings/repositories/BookingRepository.ts:1061— // FIXME: metadata is untyped — 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.
FixmeComment packages/features/bookings/repositories/BookingRepository.ts:1063— // FIXME: responses is untyped — 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.
FixmeComment packages/features/bookings/lib/handleNewBooking/test/fresh-booking.test.ts:686— // FIXME: We should send Broken Integration emails on calendar event creation failure — 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.
FixmeComment packages/features/bookings/lib/handleNewBooking/test/fresh-booking.test.ts:2761— // FIXME: We shouldn't throw error here, the behaviour should be fixed. — 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.
FixmeComment packages/features/bookings/lib/handleNewBooking/test/fresh-booking.test.ts:3203— // FIXME: Right now we need to reset the test Emails because email expects only tests first email content for an email address — 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.
FixmeComment packages/embeds/embed-snippet/src/index.ts:5— // FIXME: embed-snippet is a published package and shouldn't import from @calcom/types which is unpublished — 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.
FixmeComment packages/embeds/embed-core/src/sdk-action-manager.ts:318— //FIXME: Ensure that any action if it has :, it is properly encoded. — 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.
FixmeComment packages/embeds/embed-core/src/embed-iframe/lib/utils.ts:135— // FIXME: This event shouldn't be subscribable by the user. Only by the SDK. — 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.
FixmeComment packages/embeds/embed-core/src/embed-iframe/lib/utils.ts:152— // FIXME: If 0 can't be reached we need to just abandon our quest for perfect iframe and let scroll be there. Such case can be logged in the wild and fixed later on. — 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.
FixmeComment packages/app-store-cli/src/components/AppCreateUpdateForm.tsx:166— // FIXME: Even after CLI showing this message, it is stuck doing work before exiting — 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.
FixmeComment REDACTED:224— //FIXME: `externalCalendarId` is required by the `updateAllCalendarEvents` method, but is not used by zoho-bigin App. Not setting this property actually skips calling updateEvent.. — 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.
FixmeComment packages/app-store/vital/lib/reschedule.ts:158— // FIXME: error logging - non-Error type errors are currently discarded — 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.
FixmeComment packages/app-store/salesforce/lib/__tests__/CrmService.integration.test.ts:183— // FIXME: Seems like a bug as this should have been accountId but it is undefined — 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.
FixmeComment packages/app-store/salesforce/lib/__tests__/CrmService.integration.test.ts:204— // FIXME: Seems like a bug as this should have been accountId but it is undefined — 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.
FixmeComment apps/web/pagesAndRewritePaths.ts:83— // FIXME: I am not sure why public is needed here, an asset 'test' in public isn't accessible through "/public/test" but only through "/test" — 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.
Unfinished stub — throws a "not implemented" error packages/app-store/alby/lib/PaymentService.ts:94— A shipped function's whole body still throws a "not implemented" error — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws a "not implemented" error packages/app-store/alby/lib/PaymentService.ts:97— A shipped function's whole body still throws a "not implemented" error — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws a "not implemented" error packages/app-store/alby/lib/PaymentService.ts:101— A shipped function's whole body still throws a "not implemented" error — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws a "not implemented" error packages/app-store/alby/lib/PaymentService.ts:109— A shipped function's whole body still throws a "not implemented" error — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws a "not implemented" error packages/app-store/alby/lib/PaymentService.ts:115— A shipped function's whole body still throws a "not implemented" error — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws a "not implemented" error packages/app-store/alby/lib/PaymentService.ts:118— A shipped function's whole body still throws a "not implemented" error — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws a "not implemented" error packages/app-store/btcpayserver/lib/PaymentService.ts:154— A shipped function's whole body still throws a "not implemented" error — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws a "not implemented" error packages/app-store/btcpayserver/lib/PaymentService.ts:161— A shipped function's whole body still throws a "not implemented" error — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws a "not implemented" error packages/app-store/btcpayserver/lib/PaymentService.ts:170— A shipped function's whole body still throws a "not implemented" error — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws a "not implemented" error packages/app-store/btcpayserver/lib/PaymentService.ts:177— A shipped function's whole body still throws a "not implemented" error — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws a "not implemented" error packages/app-store/btcpayserver/lib/PaymentService.ts:181— A shipped function's whole body still throws a "not implemented" error — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws a "not implemented" error packages/app-store/hitpay/lib/PaymentService.ts:200— A shipped function's whole body still throws a "not implemented" error — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws a "not implemented" error packages/app-store/hitpay/lib/PaymentService.ts:203— A shipped function's whole body still throws a "not implemented" error — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws a "not implemented" error packages/app-store/hitpay/lib/PaymentService.ts:207— A shipped function's whole body still throws a "not implemented" error — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws a "not implemented" error packages/app-store/hitpay/lib/PaymentService.ts:215— A shipped function's whole body still throws a "not implemented" error — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws a "not implemented" error packages/app-store/hitpay/lib/PaymentService.ts:221— A shipped function's whole body still throws a "not implemented" error — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws a "not implemented" error packages/app-store/hitpay/lib/PaymentService.ts:224— A shipped function's whole body still throws a "not implemented" error — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws a "not implemented" error packages/app-store/mock-payment-app/lib/PaymentService.ts:60— A shipped function's whole body still throws a "not implemented" error — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws a "not implemented" error packages/app-store/mock-payment-app/lib/PaymentService.ts:63— A shipped function's whole body still throws a "not implemented" error — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws a "not implemented" error packages/app-store/mock-payment-app/lib/PaymentService.ts:122— A shipped function's whole body still throws a "not implemented" error — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws a "not implemented" error packages/app-store/mock-payment-app/lib/PaymentService.ts:125— A shipped function's whole body still throws a "not implemented" error — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws a "not implemented" error packages/app-store/mock-payment-app/lib/PaymentService.ts:128— A shipped function's whole body still throws a "not implemented" error — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws a "not implemented" error packages/app-store/paypal/lib/PaymentService.ts:98— A shipped function's whole body still throws a "not implemented" error — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws a "not implemented" error packages/app-store/paypal/lib/PaymentService.ts:101— A shipped function's whole body still throws a "not implemented" error — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws a "not implemented" error packages/app-store/paypal/lib/PaymentService.ts:181— A shipped function's whole body still throws a "not implemented" error — generated scaffolding that was never completed. Implement it or remove the dead surface.
Skipped test: create team event using CreateTeamEventTypeAtom packages/platform/examples/base/tests/create-team-event-type-atom/create-team-event-type.e2e.ts:6— Skipped — switched off by test.skip
Skipped test: availability page loads with all components packages/platform/examples/base/tests/availability-settings-atom/availability-settings-atom.e2e.ts:12— Skipped — switched off by test.skip
Skipped test: should remove unicode packages/lib/slugify.test.ts:58— Skipped — switched off by it.skip
Skipped test: should return the correct working hours given a specific availability, timezone, and date range packages/features/schedules/lib/date-ranges.test.ts:15— Skipped — switched off by it.skip
Skipped test: should return the correct working hours in the month were DST ends packages/features/schedules/lib/date-ranges.test.ts:162— Skipped — switched off by it.skip
Skipped test: and in loading state, should not prefetch and thus return time range of current month even when column view extra days are present(which keeps the date in the current month) packages/features/schedules/hooks/useTimesForSchedule.timezone.test.ts:278— Skipped — switched off by it.skip
Skipped test: and in loading state, should not prefetch and thus return time range of current month even when column view extra days are present(which keeps the date in the current month) packages/features/schedules/hooks/useTimesForSchedule.timezone.test.ts:537— Skipped — switched off by it.skip
Skipped test: should return null when user doesn't have access to event type packages/features/eventtypes/lib/getEventTypeById.integration-test.ts:135— Skipped — switched off by test.skip
Skipped test: should fail a booking if yearly booking limits are already reached 1. year with limits reached: should fail to book 2. following year without bookings: should create a booking in the database packages/features/bookings/lib/handleNewBooking/test/booking-limits.test.ts:48— Skipped — switched off by test.skip
Skipped test: should reuse the same modal packages/embeds/embed-core/src/embed.test.ts:713— Skipped — switched off by it.skip
Skipped test: COEP flag if not enabled, embed is blocked packages/embeds/embed-core/playwright/tests/inline.e2e.ts:34— Skipped — switched off by test.skip
Skipped test: (unnamed test) packages/app-store/googlecalendar/tests/google-calendar.e2e.ts:25— Skipped — switched off by test.skip
Skipped test: (unnamed test) packages/app-store/googlecalendar/tests/google-calendar.e2e.ts:38— Skipped — switched off by test.skip
Skipped test: (unnamed test) packages/app-store/googlecalendar/tests/google-calendar.e2e.ts:41— Skipped — switched off by test.skip
Skipped test: (unnamed test) packages/app-store/googlecalendar/tests/google-calendar.e2e.ts:42— Skipped — switched off by test.skip
Skipped test: (unnamed test) packages/app-store/googlecalendar/tests/google-calendar.e2e.ts:63— Skipped — switched off by test.skip
Skipped test: (unnamed test) packages/app-store/googlecalendar/tests/google-calendar.e2e.ts:75— Skipped — switched off by test.skip
Skipped test: (unnamed test) packages/app-store/googlecalendar/tests/google-calendar.e2e.ts:80— Skipped — switched off by test.skip
Skipped test: (unnamed test) packages/app-store/googlecalendar/tests/google-calendar.e2e.ts:107— Skipped — switched off by test.skip
Skipped test: test that PER_WEEK duration limits work correctly apps/web/test/lib/getSchedule.test.ts:1975— Skipped — switched off by test.skip
Skipped test: global team duration limit blocks slots if one fixed host reached limit apps/web/test/lib/getSchedule.test.ts:2079— Skipped — switched off by test.skip
Skipped test: test that combined booking and duration limits work correctly apps/web/test/lib/getSchedule.test.ts:2245— Skipped — switched off by test.skip
Skipped test: should fail recurring booking if second slot is already booked apps/web/pages/api/book/recurring-event.test.ts:256— Skipped — switched off by test.skip
Skipped test: should when when a fixed host is not available on the second slot apps/web/pages/api/book/recurring-event.test.ts:814— Skipped — switched off by test.skip
Skipped test: /POST/v2/calendars/${OFFICE_365_CALENDAR}/disconnect: it should respond with a 201 returning back the user deleted calendar credentials apps/api/v2/src/platform/calendars/controllers/calendars.controller.e2e-spec.ts:367— Skipped — switched off by it.skip
X24 · Document value interpolated into markup unescaped· Untrusted text written into markup unescaped · ×20
Untrusted text written into markup unescaped apps/web/app/(use-page-wrapper)/layout.tsx:34— `script.script` 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.
Untrusted text written into markup unescaped apps/web/app/SpeculationRules.tsx:29— ``${JSON.stringify(speculationRules)}`` 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.
Untrusted text written into markup unescaped apps/web/components/eventtype/EventTypeDescriptionSafeHTML.tsx:9— `eventType.descriptionAsSafeHTML||""` 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.
Untrusted text written into markup unescaped apps/web/modules/signup-view.tsx:350— ``(function (w, d, s, l, i) {
w[l] = w[l] || []; w[l].push({ 'gtm.start': new Date().getTime()…` 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.
Untrusted text written into markup unescaped apps/web/modules/signup-view.tsx:360— `process.env.NEXT_PUBLIC_GTM_ID` is text this program did not author, and it is written into a URL attribute 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.
Untrusted text written into markup unescaped REDACTED:108— `props.safeBio` 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.
Untrusted text written into markup unescaped apps/web/pages/_document.tsx:60— ``
window.calNewLocale = "${newLocale}";
window.calIsDesktopApp = ${isDesktopApp};
…` 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.
Untrusted text written into markup unescaped REDACTED:146— `parseValue(script.content)||""` 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.
Untrusted text written into markup unescaped packages/app-store/hubspot/lib/CrmService.ts:84— `location` is text this program did not author, and it is written into the text of an element through markup this function returns 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.
Untrusted text written into markup unescaped REDACTED:27— `htmlContent.replaceAll("<p>",`<p style="${css}">`).replaceAll("<li>",`<li style="${css}">`)` 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.
Untrusted text written into markup unescaped packages/emails/src/components/RawHtml.tsx:5— `html` 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.
Untrusted text written into markup unescaped packages/embeds/embed-core/src/EmbedElement.ts:195— `skeletonContent` is text this program did not author, and it is written into the text of an element through `innerHTML` 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.
Untrusted text written into markup unescaped packages/embeds/embed-core/src/FloatingButton/FloatingButton.ts:104— `window.Cal.__css` is text this program did not author, and it is written into the text of an element through `innerHTML` 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.
Untrusted text written into markup unescaped packages/embeds/embed-core/src/Inline/inline.ts:37— `window.Cal.__css` is text this program did not author, and it is written into the text of an element through `innerHTML` 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.
Untrusted text written into markup unescaped packages/embeds/embed-core/src/ModalBox/ModalBox.ts:249— `window.Cal.__css` is text this program did not author, and it is written into the text of an element through `innerHTML` 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.
Untrusted text written into markup unescaped REDACTED:87— `css` is text this program did not author, and it is written into the text of an element through `innerHTML` 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.
Untrusted text written into markup unescaped REDACTED:969— `generateDataAttributes({pageType,theme,layout,})` is text this program did not author, and it is written into an unquoted attribute through `innerHTML` 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. HTML text encoding does not help in an unquoted attribute — whitespace ends it; quote the attribute and encode the value.
Untrusted text written into markup unescaped REDACTED:1258— `generateDataAttributes({pageType,theme,layout,})` is text this program did not author, and it is written into an unquoted attribute through `innerHTML` 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. HTML text encoding does not help in an unquoted attribute — whitespace ends it; quote the attribute and encode the value.
Untrusted text written into markup unescaped REDACTED:1263— `uid` is text this program did not author, and it is written into a quoted attribute value through `innerHTML` 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.
Untrusted text written into markup unescaped REDACTED:101— `descriptionAsSafeHtml` 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.
Swallowed exception (empty catch) packages/trpc/server/routers/loggedInViewer/unlinkConnectedAccount.handler.ts:32— 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) packages/lib/recentImpersonations.ts:30— 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) packages/lib/recentImpersonations.ts:36— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) packages/lib/ssrfProtection.ts:187— 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) packages/lib/tracing/index.ts:86— 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) packages/features/webhooks/lib/sendPayload.ts:199— 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) packages/features/form-builder/schema.ts:157— 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) packages/features/credentials/services/CredentialDataService.ts:33— 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) packages/features/bookings/lib/handleSeats/cancel/cancelAttendeeSeat.ts:133— 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) packages/app-store-cli/src/components/AppCreateUpdateForm.tsx:50— 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) packages/app-store/webex/api/callback.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) packages/app-store/nextcloudtalk/api/callback.ts:43— 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) packages/app-store/jelly/api/callback.ts:31— 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) packages/app-store/basecamp3/api/callback.ts: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) packages/app-store/basecamp3/api/callback.ts:63— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) apps/web/proxy.ts:10— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) apps/web/modules/onboarding/store/onboarding-storage.ts:90— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) apps/web/modules/onboarding/store/onboarding-storage.ts:111— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) apps/web/components/booking/actions/BookingActionsDropdown.tsx:214— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) apps/web/components/apps/btcpayserver/BtcpayPaymentComponent.tsx:177— 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.
Sync-over-async blocking apps/api/v2/src/swagger/generate-swagger.ts:32— `fs.existsSync` in `generateSwaggerForApp` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking apps/api/v2/src/swagger/generate-swagger.ts:33— `fs.unlinkSync` in `generateSwaggerForApp` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking apps/api/v2/src/swagger/generate-swagger.ts:34— `fs.writeFileSync` in `generateSwaggerForApp` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking apps/api/v2/src/swagger/generate-swagger.ts:35— `spawnSync` in `generateSwaggerForApp` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking apps/web/lib/apps/[slug]/getStaticProps.ts:99— `fs.readFileSync` in `getStaticProps` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking packages/app-store-cli/src/core.ts:78— `execSync` in `create` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking packages/app-store-cli/src/core.ts:79— `execSync` in `create` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking packages/app-store-cli/src/core.ts:92— `execSync` in `create` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking packages/app-store-cli/src/core.ts:120— `fs.readFileSync` in `create` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking packages/app-store-cli/src/core.ts:136— `fs.writeFileSync` in `create` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking packages/app-store-cli/src/core.ts:137— `fs.writeFileSync` in `create` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking packages/app-store-cli/src/core.ts:140— `fs.readFileSync` in `create` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking packages/app-store-cli/src/core.ts:146— `execSync` in `create` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking packages/app-store-cli/src/core.ts:151— `execSync` in `anonymous function` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking packages/app-store-cli/src/core.ts:156— `execSync` in `generateAppFiles` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking packages/features/auth/lib/sendVerificationRequest.ts:25— `readFileSync` in `sendVerificationRequest` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking packages/platform/libraries/scripts/prepublish.js:53— `fs.readFileSync` in `main` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking packages/platform/libraries/scripts/prepublish.js:56— `fs.writeFileSync` in `main` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
AC6 · Visual & motion safety· Animation without a prefers-reduced-motion guard · ×17
Animation without a prefers-reduced-motion guard packages/app-store/giphy/components/SearchDialog.tsx:155— <svg> 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 packages/ui/components/button/Button.tsx:288— <svg> 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 packages/platform/atoms/globals.css:3291— `.animate-fade-in-up` moves (`animation: fade-in-up 0.6s var(--animation-delay, 0s) cubic-bezier(0.21, 1.02, 0.73, 1) forwards`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard packages/platform/atoms/globals.css:3300— `.animate-spinning` moves (`animation: 0.75s linear infinite spinning`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard packages/platform/atoms/globals.css:7233— `.data-\[state\=closed\]\:animate-out[data-state="closed"]` moves (`animation: exit var(--tw-animation-duration, var(--tw-duration, 0.15s)) var(--tw-ease, ease)
var(--tw-animation-delay, 0s) var(--tw-animation-iteration-count, 1)
var(--tw-animation-direction, normal) var(--tw-animation-fill-mode, none)`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard packages/platform/atoms/globals.css:7259— `.data-\[state\=open\]\:animate-in[data-state="open"]` moves (`animation: enter var(--tw-animation-duration, var(--tw-duration, 0.15s)) var(--tw-ease, ease)
var(--tw-animation-delay, 0s) var(--tw-animation-iteration-count, 1)
var(--tw-animation-direction, normal) var(--tw-animation-fill-mode, none)`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard packages/platform/atoms/globals.css:7309— `.data-\[swipe\=end\]\:animate-out[data-swipe="end"]` moves (`animation: exit var(--tw-animation-duration, var(--tw-duration, 0.15s)) var(--tw-ease, ease)
var(--tw-animation-delay, 0s) var(--tw-animation-iteration-count, 1)
var(--tw-animation-direction, normal) var(--tw-animation-fill-mode, none)`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard packages/platform/atoms/globals.css:10396— `.loader` moves (`animation: 2s infinite loader`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard packages/platform/atoms/globals.css:10403— `.loader-inner` moves (`animation: 2s ease-in infinite loader-inner`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard packages/platform/atoms/globals.css:10457— `.slideInBottom` moves (`animation-name: slideInBottom`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard packages/platform/atoms/globals.css:10473— `.slideInTop` moves (`animation-name: slideInTop`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard packages/embeds/embed-core/src/loader.css:49— `.loader-inner` moves (`animation: loader-inner 2s infinite ease-in`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard packages/embeds/embed-core/src/loader.css:60— `.loader` moves (`animation: loader 2s infinite 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.
Animation without a prefers-reduced-motion guard apps/web/styles/globals.css:247— `.loader` moves (`animation: loader 2s infinite 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.
Animation without a prefers-reduced-motion guard apps/web/styles/globals.css:254— `.loader-inner` moves (`animation: loader-inner 2s infinite ease-in`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard apps/web/styles/globals.css:334— `.slideInBottom` moves (`animation-name: slideInBottom`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard apps/web/styles/globals.css:353— `.slideInTop` moves (`animation-name: slideInTop`) 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.
MethodTooLong: AvailableSlotsService._getAvailableSlots REDACTED:897— MethodTooLong — _getAvailableSlots runs 356 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 256 over it, 3.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.
MethodTooLong: UserAvailabilityService._getUserAvailability packages/features/availability/lib/getUserAvailability.ts:361— MethodTooLong — _getUserAvailability runs 221 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 121 over it, 2.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.
MethodTooLong: EventTypeRepository.findById packages/features/eventtypes/repositories/eventTypeRepository.ts:545— MethodTooLong — findById runs 215 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 115 over it, 2.15× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: EventTypeRepository.findByIdForOrgAdmin packages/features/eventtypes/repositories/eventTypeRepository.ts:825— MethodTooLong — findByIdForOrgAdmin runs 213 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 113 over it, 2.13× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: BusyTimesService._getBusyTimes packages/features/busyTimes/services/getBusyTimes.ts:29— MethodTooLong — _getBusyTimes runs 173 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 73 over it, 1.73× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: AvailableSlotsService.calculateHostsAndAvailabilities REDACTED:678— MethodTooLong — calculateHostsAndAvailabilities runs 138 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 38 over it, 1.38× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: WebhookRepository.getFilteredWebhooksForUser packages/features/webhooks/lib/repository/WebhookRepository.ts:319— MethodTooLong — getFilteredWebhooksForUser runs 135 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 35 over it, 1.35× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: OutputEventTypesService_2024_06_14.getResponseEventType apps/api/v2/src/platform/event-types/event-types_2024_06_14/services/output-event-types.service.ts:139— MethodTooLong — getResponseEventType runs 134 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 34 over it, 1.34× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: SalesforceGraphQLClient.GetAccountRecordsForRRSkip packages/app-store/salesforce/lib/graphql/SalesforceGraphQLClient.ts:65— MethodTooLong — GetAccountRecordsForRRSkip runs 129 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 29 over it, 1.29× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: BookingsService_2024_08_13.hasRequiredBookingFieldsResponses apps/api/v2/src/platform/bookings/2024-08-13/services/bookings.service.ts:217— MethodTooLong — hasRequiredBookingFieldsResponses runs 120 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 20 over it, 1.20× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: GoogleCalendarService.createEvent packages/app-store/googlecalendar/lib/CalendarService.ts:180— MethodTooLong — createEvent runs 116 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 16 over it, 1.16× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: SalesforceCRMService.getContacts packages/app-store/salesforce/lib/CrmService.ts:539— MethodTooLong — getContacts runs 114 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 14 over it, 1.14× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: HitPayPaymentService.create packages/app-store/hitpay/lib/PaymentService.ts:38— MethodTooLong — create runs 113 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 13 over it, 1.13× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: EventTypeRepository.findForSlots packages/features/eventtypes/repositories/eventTypeRepository.ts:1243— MethodTooLong — findForSlots runs 111 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 11 over it, 1.11× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: EventManager.reschedule packages/features/bookings/lib/EventManager.ts:615— MethodTooLong — reschedule runs 108 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 8 over it, 1.08× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: BaseCalendarService.getAvailability packages/lib/CalendarService.ts:655— MethodTooLong — getAvailability runs 106 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 6 over it, 1.06× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: EventManager.createAllCalendarEvents packages/features/bookings/lib/EventManager.ts:873— MethodTooLong — createAllCalendarEvents runs 104 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 4 over it, 1.04× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
ClassTooLong: EventTypeRepository packages/features/eventtypes/repositories/eventTypeRepository.ts:81— ClassTooLong — 1241 significant lines (blank, comment-only and punctuation-only lines excluded), 35 methods. The bar is 400 significant lines; this is 841 over it, 3.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.
ClassTooLong: SalesforceCRMService packages/app-store/salesforce/lib/CrmService.ts:114— ClassTooLong — 1172 significant lines (blank, comment-only and punctuation-only lines excluded), 53 methods. The bar is 400 significant lines; this is 772 over it, 2.93× 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: EventAdvancedTab apps/web/modules/event-types/components/tabs/advanced/EventAdvancedTab.tsx:1— ClassTooLong — 948 significant lines (blank, comment-only and punctuation-only lines excluded), 1 methods. The bar is 400 significant lines; this is 548 over it, 2.37× 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: AvailableSlotsService REDACTED:143— ClassTooLong — 880 significant lines (blank, comment-only and punctuation-only lines excluded), 21 methods. The bar is 400 significant lines; this is 480 over it, 2.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: BookingsService_2024_08_13 apps/api/v2/src/platform/bookings/2024-08-13/services/bookings.service.ts:89— ClassTooLong — 770 significant lines (blank, comment-only and punctuation-only lines excluded), 30 methods. The bar is 400 significant lines; this is 370 over it, 1.93× 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: GoogleCalendarService packages/app-store/googlecalendar/lib/CalendarService.ts:77— ClassTooLong — 593 significant lines (blank, comment-only and punctuation-only lines excluded), 30 methods. The bar is 400 significant lines; this is 193 over it, 1.48× 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: InputBookingsService_2024_08_13 apps/api/v2/src/platform/bookings/2024-08-13/services/input.service.ts:81— ClassTooLong — 546 significant lines (blank, comment-only and punctuation-only lines excluded), 23 methods. The bar is 400 significant lines; this is 146 over it, 1.37× 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: LuckyUserService packages/features/bookings/lib/getLuckyUser.ts:156— ClassTooLong — 521 significant lines (blank, comment-only and punctuation-only lines excluded), 12 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: BookingActionsDropdown apps/web/components/booking/actions/BookingActionsDropdown.tsx:1— ClassTooLong — 500 significant lines (blank, comment-only and punctuation-only lines excluded), 1 methods. The bar is 400 significant lines; this is 100 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: Office365CalendarService packages/app-store/office365calendar/lib/CalendarService.ts:57— ClassTooLong — 487 significant lines (blank, comment-only and punctuation-only lines excluded), 24 methods. The bar is 400 significant lines; this is 87 over it, 1.22× 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: InputEventTypesService_2024_06_14 apps/api/v2/src/platform/event-types/event-types_2024_06_14/services/input-event-types.service.ts:55— ClassTooLong — 437 significant lines (blank, comment-only and punctuation-only lines excluded), 32 methods. The bar is 400 significant lines; this is 37 over it, 1.09× 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: UserAvailabilityService packages/features/availability/lib/getUserAvailability.ts:228— ClassTooLong — 437 significant lines (blank, comment-only and punctuation-only lines excluded), 10 methods. The bar is 400 significant lines; this is 37 over it, 1.09× 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: HubspotCalendarService packages/app-store/hubspot/lib/CrmService.ts:29— ClassTooLong — 430 significant lines (blank, comment-only and punctuation-only lines excluded), 28 methods. The bar is 400 significant lines; this is 30 over it, 1.08× 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: AvailabilitySettings packages/platform/atoms/availability/AvailabilitySettings.tsx:1— ClassTooLong — 423 significant lines (blank, comment-only and punctuation-only lines excluded), 5 methods. The bar is 400 significant lines; this is 23 over it, 1.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: BaseCalendarService packages/lib/CalendarService.ts:388— ClassTooLong — 415 significant lines (blank, comment-only and punctuation-only lines excluded), 14 methods. The bar is 400 significant lines; this is 15 over it, 1.04× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: EventLimitsTab packages/features/eventtypes/components/tabs/limits/EventLimitsTab.tsx:1— ClassTooLong — 409 significant lines (blank, comment-only and punctuation-only lines excluded), 9 methods. The bar is 400 significant lines; this is 9 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.
HackComment REDACTED:651— // HACK — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
HackComment REDACTED:40— // HACK: Redefine and don't import WEBAPP_URL as it causes import statement to be present in built file. — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
HackComment packages/app-store-cli/src/build.ts:298— // HACK: Key must be appId as this is used by eventType metadata and lookup is by appId — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
HackComment packages/app-store-cli/src/build.ts:310— // HACK: Key must be appId as this is used by eventType metadata and lookup is by appId — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
HackComment packages/app-store-cli/src/components/AppCreateUpdateForm.tsx:203— // HACK: This is a hack to exit the process manually because due to some reason cli isn't automatically exiting — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
HackComment packages/app-store/locations.ts:35— // HACK: `variable` and `defaultValueVariable` are required due to legacy reason where different locations were stored in different places. — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
HackComment packages/app-store/locations.ts:142— // HACK: — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
HackComment packages/app-store/locations.ts:263— // HACK: Translation ends up removing https? if it's in the beginning :( — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
HackComment apps/web/playwright/lib/testUtils.ts:301— // HACK: There seems to be some issue with the inputs to the form getting reset if we don't wait. — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
HackComment apps/web/modules/event-types/components/tabs/advanced/FormBuilder.tsx:134— // HACK: It allows any property name to be used for instead of `fields` property name — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
HackComment apps/web/modules/calendar-view/components/LargeCalendar.tsx:77— // HACK: force rerender when overlay events change — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
HackComment apps/web/modules/bookings/components/LargeCalendar.tsx:48— // HACK: force rerender when overlay events change — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
HackComment apps/web/app/(use-page-wrapper)/payment/[uid]/PaymentPage.tsx:79— // HACK: Look for stripe iframe and center position it just above the embed content — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
Fake-async — async method never awaits apps/api/v2/src/modules/deployments/deployments.service.ts:15— `checkLicense` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
Fake-async — async method never awaits apps/api/v2/src/platform/bookings/2024-08-13/services/bookings.service.ts:169— `checkBookingRequiresAuthenticationSetting` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
Fake-async — async method never awaits apps/api/v2/src/platform/bookings/2024-08-13/services/bookings.service.ts:217— `hasRequiredBookingFieldsResponses` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
Fake-async — async method never awaits apps/api/v2/src/platform/event-types/event-types_2024_06_14/services/input-event-types.service.ts:519— `validateCustomEventNameInput` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
Fake-async — async method never awaits apps/api/v2/src/swagger/generate-swagger.ts:21— `generateSwaggerForApp` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
Fake-async — async method never awaits apps/web/app/(booking-page-wrapper)/booking/dry-run-successful/page.tsx:15— `Page` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
Fake-async — async method never awaits apps/web/app/(use-page-wrapper)/auth/oauth2/authorize/page.tsx:15— `ServerPageWrapper` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
Fake-async — async method never awaits apps/web/app/(use-page-wrapper)/auth/verify-email/page.tsx:15— `ServerPageWrapper` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
Fake-async — async method never awaits apps/web/app/(use-page-wrapper)/availability/troubleshoot/page.tsx:15— `ServerPage` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
Fake-async — async method never awaits apps/web/app/(use-page-wrapper)/more/page.tsx:15— `ServerPageWrapper` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
Fake-async — async method never awaits apps/web/app/(use-page-wrapper)/upgrade/page.tsx:14— `ServerPage` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
Fake-async — async method never awaits apps/web/app/(use-page-wrapper)/video/no-meeting-found/page.tsx:14— `ServerPage` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
Unfinished stub — throws a "not implemented" exception packages/app-store/alby/lib/PaymentService.ts:94— `update` throws an exception whose message says it isn't finished — a not-implemented stub wearing an ordinary exception. Implement it or remove it.
Unfinished stub — throws a "not implemented" exception packages/app-store/alby/lib/PaymentService.ts:97— `refund` throws an exception whose message says it isn't finished — a not-implemented stub wearing an ordinary exception. Implement it or remove it.
Unfinished stub — throws a "not implemented" exception packages/app-store/alby/lib/PaymentService.ts:101— `collectCard` throws an exception whose message says it isn't finished — a not-implemented stub wearing an ordinary exception. Implement it or remove it.
Unfinished stub — throws a "not implemented" exception packages/app-store/alby/lib/PaymentService.ts:109— `chargeCard` throws an exception whose message says it isn't finished — a not-implemented stub wearing an ordinary exception. Implement it or remove it.
Unfinished stub — throws a "not implemented" exception packages/app-store/alby/lib/PaymentService.ts:115— `getPaymentPaidStatus` throws an exception whose message says it isn't finished — a not-implemented stub wearing an ordinary exception. Implement it or remove it.
Unfinished stub — throws a "not implemented" exception packages/app-store/alby/lib/PaymentService.ts:118— `getPaymentDetails` throws an exception whose message says it isn't finished — a not-implemented stub wearing an ordinary exception. Implement it or remove it.
Unfinished stub — throws a "not implemented" exception packages/app-store/btcpayserver/lib/PaymentService.ts:154— `update` throws an exception whose message says it isn't finished — a not-implemented stub wearing an ordinary exception. Implement it or remove it.
Unfinished stub — throws a "not implemented" exception packages/app-store/btcpayserver/lib/PaymentService.ts:161— `collectCard` throws an exception whose message says it isn't finished — a not-implemented stub wearing an ordinary exception. Implement it or remove it.
Unfinished stub — throws a "not implemented" exception packages/app-store/btcpayserver/lib/PaymentService.ts:170— `chargeCard` throws an exception whose message says it isn't finished — a not-implemented stub wearing an ordinary exception. Implement it or remove it.
Unfinished stub — throws a "not implemented" exception packages/app-store/btcpayserver/lib/PaymentService.ts:177— `getPaymentPaidStatus` throws an exception whose message says it isn't finished — a not-implemented stub wearing an ordinary exception. Implement it or remove it.
Unfinished stub — throws a "not implemented" exception packages/app-store/btcpayserver/lib/PaymentService.ts:181— `getPaymentDetails` throws an exception whose message says it isn't finished — a not-implemented stub wearing an ordinary exception. Implement it or remove it.
Unfinished stub — throws a "not implemented" exception packages/app-store/hitpay/lib/PaymentService.ts:200— `update` throws an exception whose message says it isn't finished — a not-implemented stub wearing an ordinary exception. Implement it or remove it.
Off the main sequence: @calcom/config — @calcom/config: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
Off the main sequence: @calcom/dayjs — @calcom/dayjs: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 7 project(s), so it's rigid to change.
Off the main sequence: @calcom/i18n — @calcom/i18n: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 9 project(s), so it's rigid to change.
Off the main sequence: @calcom/prisma — @calcom/prisma: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 31 project(s), so it's rigid to change.
Off the main sequence: @coss/ui — @coss/ui: abstractness 0.02, instability 0.00, distance 0.98 — zone of pain — concrete and depended on by 2 project(s), so it's rigid to change.
Off the main sequence: @calcom/embed-core — @calcom/embed-core: abstractness 0.06, instability 0.00, distance 0.94 — zone of pain — concrete and depended on by 3 project(s), so it's rigid to change.
Off the main sequence: @calcom/lib — @calcom/lib: abstractness 0.04, instability 0.04, distance 0.92 — zone of pain — concrete and depended on by 82 project(s), so it's rigid to change.
Off the main sequence: @calcom/ui — @calcom/ui: abstractness 0.06, instability 0.11, distance 0.83 — zone of pain — concrete and depended on by 8 project(s), so it's rigid to change.
Off the main sequence: @calcom/atoms — @calcom/atoms: abstractness 0.18, instability 0.00, distance 0.82 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
Off the main sequence: @calcom/platform-enums — @calcom/platform-enums: abstractness 0.00, instability 0.25, distance 0.75 — zone of pain — concrete and depended on by 3 project(s), so it's rigid to change.
Off the main sequence: @calcom/trpc — @calcom/trpc: abstractness 0.01, instability 0.25, distance 0.74 — zone of pain — concrete and depended on by 3 project(s), so it's rigid to change.
AC6 · Visual & motion safety· Focus outline removed in CSS without a · ×10
Focus outline removed in CSS without a :focus replacement packages/ui/components/form/date-range-picker/styles.css:36— `.react-calendar 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 packages/ui/components/editor/stylesEditor.css:44— `.editor-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 packages/ui/components/editor/stylesEditor.css:299— `.link-editor .link-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 packages/platform/atoms/globals.css:5853— `.outline-none` 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 packages/platform/atoms/globals.css:6901— `.focus\:outline-none:focus` 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 packages/platform/atoms/globals.css:6905— `.focus\:outline-none\!:focus` 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 packages/platform/atoms/globals.css:6976— `.focus-visible\:outline-none:focus-visible` 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 packages/platform/atoms/globals.css:11691— `.react-tel-input .form-control` 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 packages/platform/atoms/globals.css:11767— `.react-tel-input .country-list` 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 packages/platform/atoms/globals.css:11823— `.react-tel-input .country-list .search-box` 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.
Change coupling: RegularBookingService.ts ↔ getMockRequestDataForBooking.ts packages/features/bookings/lib/service/RegularBookingService.ts:1— `packages/features/bookings/lib/service/RegularBookingService.ts` and `packages/testing/src/lib/bookingScenario/getMockRequestDataForBooking.ts` change together 80% of the time (8 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 8 shared commits counted here, the most recent 3 are `82951cd0` chore: [Booking Flow Refactor - 5] Move post booking things to separa… (at that commit the file was still `apps/web/test/utils/bookingScenario/getMockRequestDataForBooking.ts`); `64297f02` feat: add user-specific email verification setting (#24298) (at that commit the files were still `packages/features/bookings/lib/handleNewBooking.ts` and `apps/web/test/utils/bookingScenario/getMockRequestDataForBooking.ts`); `0968fc56` feat: add utm tracking on booking (#19965) (at that commit the files were still `packages/features/bookings/lib/handleNewBooking.ts` and `apps/web/test/utils/bookingScenario/getMockRequestDataForBooking.ts`) — run `git show` on any of them.
Change coupling: RegularBookingService.ts ↔ expects.ts packages/features/bookings/lib/service/RegularBookingService.ts:1— `packages/features/bookings/lib/service/RegularBookingService.ts` and `packages/testing/src/lib/bookingScenario/expects.ts` change together 52% of the time (13 of the 25 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — 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 `9c97b2aa` feat: add usernameInOrg field to webhook organizer payload for organi… (at that commit the files were still `packages/features/bookings/lib/handleNewBooking.ts` and `apps/web/test/utils/bookingScenario/expects.ts`); `afea724e` fix: improve cancellation email of reschedule RR booking (#17768) (at that commit the files were still `packages/features/bookings/lib/handleNewBooking.ts` and `apps/web/test/utils/bookingScenario/expects.ts`); `0968fc56` feat: add utm tracking on booking (#19965) (at that commit the files were still `packages/features/bookings/lib/handleNewBooking.ts` and `apps/web/test/utils/bookingScenario/expects.ts`) — run `git show` on any of them.
Change coupling: PremiumTextfield.tsx ↔ UsernameTextfield.tsx apps/web/components/ui/UsernameAvailability/PremiumTextfield.tsx:1— `apps/web/components/ui/UsernameAvailability/PremiumTextfield.tsx` and `apps/web/components/ui/UsernameAvailability/UsernameTextfield.tsx` change together 75% of the time (12 of the 16 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — 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 12 shared commits counted here, the most recent 3 are `5417012c` Revert "fix: sanitize username input to prevent hyperlinks (#24210)" …; `7d16da5c` fix: sanitize username input to prevent hyperlinks (#24210); `587af331` perf: Use built types for appRouter (#20083) — run `git show` on any of them.
Change coupling: event-types.repository.ts ↔ output-event-types.service.ts apps/api/v2/src/platform/event-types/event-types_2024_06_14/event-types.repository.ts:1— `apps/api/v2/src/platform/event-types/event-types_2024_06_14/event-types.repository.ts` and `apps/api/v2/src/platform/event-types/event-types_2024_06_14/services/output-event-types.service.ts` change together 62% of the time (8 of the 13 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 8 shared commits counted here, the most recent 3 are `c0017114` fix(api): return empty bookingUrl for managed users in API v2 (#26826) (at that commit the files were still `apps/api/v2/src/ee/event-types/event-types_2024_06_14/event-types.repository.ts` and `apps/api/v2/src/ee/event-types/event-types_2024_06_14/services/output-event-types.service.ts`); `e879c923` feat(api): add bookingUrl field to event types API v2 response (#26195) (at that commit the files were still `apps/api/v2/src/ee/event-types/event-types_2024_06_14/event-types.repository.ts` and `apps/api/v2/src/ee/event-types/event-types_2024_06_14/services/output-event-types.service.ts`); `ad4cf0cc` fix: v2 hidden event types (#23584) (at that commit the files were still `apps/api/v2/src/ee/event-types/event-types_2024_06_14/event-types.repository.ts` and `apps/api/v2/src/ee/event-types/event-types_2024_06_14/services/output-event-types.service.ts`) — run `git show` on any of them.
Change coupling: REDACTED ↔ next-auth-options.ts apps/web/app/api/auth/two-factor/totp/disable/route.ts:1— `apps/web/app/api/auth/two-factor/totp/disable/route.ts` and `packages/features/auth/lib/next-auth-options.ts` 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, and counted over this repository's 10,000 most recent commits rather than its whole history — 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 `30cb8f74` revert: Revert UserPassword (#13680) (#13685) (at that commit the file was still `apps/web/pages/api/auth/two-factor/totp/disable.ts`); `0a68c6d0` revert: UserPassword (#13680) (at that commit the file was still `apps/web/pages/api/auth/two-factor/totp/disable.ts`); `7b0d5959` refactor: migrates user password to it's own table (#13628) (at that commit the file was still `apps/web/pages/api/auth/two-factor/totp/disable.ts`) — run `git show` on any of them.
Change coupling: layout.tsx ↔ PageWrapperAppDir.tsx apps/web/app/layout.tsx:1— `apps/web/app/layout.tsx` and `apps/web/components/PageWrapperAppDir.tsx` change together 54% of the time (7 of the 13 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — 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 `81224f32` feat: google ads conversion tracking (#25198); `b17b5a16` perf: make `useLocale` hook to use server-fetched i18n if in App rout…; `564c84da` fix: App theme being used in routing-form embed (#19489) — run `git show` on any of them.
Change coupling: event-types.service.ts ↔ event-types.service.ts apps/api/v2/src/platform/event-types/event-types_2024_04_15/services/event-types.service.ts:1— `apps/api/v2/src/platform/event-types/event-types_2024_04_15/services/event-types.service.ts` and `apps/api/v2/src/platform/event-types/event-types_2024_06_14/services/event-types.service.ts` 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, and counted over this repository's 10,000 most recent commits rather than its whole history — 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 `cb437231` fix: platform libraries barrel file extract event-types (#19846) (at that commit the files were still `apps/api/v2/src/ee/event-types/event-types_2024_04_15/services/event-types.service.ts` and `apps/api/v2/src/ee/event-types/event-types_2024_06_14/services/event-types.service.ts`); `1690770d` fix: check profiles and orgId from user.profiles apiv2 (#16249) (at that commit the files were still `apps/api/v2/src/ee/event-types/event-types_2024_04_15/services/event-types.service.ts` and `apps/api/v2/src/ee/event-types/event-types_2024_06_14/services/event-types.service.ts`); `23eb77b8` fix: re-booked booking metadata (#16074) (at that commit the files were still `apps/api/v2/src/ee/event-types/event-types_2024_04_15/services/event-types.service.ts` and `apps/api/v2/src/ee/event-types/event-types_2024_06_14/services/event-types.service.ts`) — run `git show` on any of them.
Change coupling: oauth-client-users.controller.ts ↔ oauth-clients.controller.ts apps/api/v2/src/modules/oauth-clients/controllers/oauth-client-users/oauth-client-users.controller.ts:1— `apps/api/v2/src/modules/oauth-clients/controllers/oauth-client-users/oauth-client-users.controller.ts` and `apps/api/v2/src/modules/oauth-clients/controllers/oauth-clients/oauth-clients.controller.ts` 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, and counted over this repository's 10,000 most recent commits rather than its whole history — 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 `19f4677d` chore: update docs (#26971); `eee31d6e` chore: tag deprecated platform oauth endpoints in api v2 (#26873); `b08997b5` fix: remove debug logs and clean up verbose logging (#25896) — run `git show` on any of them.
Change coupling: input-event-types.service.ts ↔ booking-fields.ts apps/api/v2/src/platform/event-types/event-types_2024_06_14/services/input-event-types.service.ts:1— `apps/api/v2/src/platform/event-types/event-types_2024_06_14/services/input-event-types.service.ts` and `apps/api/v2/src/platform/event-types/event-types_2024_06_14/transformers/api-to-internal/booking-fields.ts` 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, and counted over this repository's 10,000 most recent commits rather than its whole history — 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 `80fad2aa` fix: create event type with output of another create event type (#21273) (at that commit the files were still `apps/api/v2/src/ee/event-types/event-types_2024_06_14/services/input-event-types.service.ts` and `packages/lib/event-types/transformers/api-to-internal/booking-fields.ts`); `94a26031` feat: v2 api phone based organization team event types (#20134) (at that commit the files were still `apps/api/v2/src/ee/event-types/event-types_2024_06_14/services/input-event-types.service.ts` and `packages/lib/event-types/transformers/api-to-internal/booking-fields.ts`); `c8172ab7` refactor: v2 default booking fields (#18287) (at that commit the files were still `apps/api/v2/src/ee/event-types/event-types_2024_06_14/services/input-event-types.service.ts` and `packages/lib/event-types/transformers/api-to-internal/booking-fields.ts`) — run `git show` on any of them.
AC2 · Forms & labels· <fieldset> without a <legend> · ×8
<fieldset> without a <legend> apps/web/components/apps/applecalendar/Setup.tsx:77— A fieldset groups related controls but has no <legend> to name the group. Add a <legend> as its first child — or, if the group already has a visible caption beside it (or the fieldset is there only to disable its subtree and carries no group box), point aria-labelledby at that caption's id instead, which names the group without rendering a second one.
<fieldset> without a <legend> apps/web/components/apps/caldavcalendar/Setup.tsx:63— A fieldset groups related controls but has no <legend> to name the group. Add a <legend> as its first child — or, if the group already has a visible caption beside it (or the fieldset is there only to disable its subtree and carries no group box), point aria-labelledby at that caption's id instead, which names the group without rendering a second one.
<fieldset> without a <legend> apps/web/components/apps/exchange2013calendar/Setup.tsx:57— A fieldset groups related controls but has no <legend> to name the group. Add a <legend> as its first child — or, if the group already has a visible caption beside it (or the fieldset is there only to disable its subtree and carries no group box), point aria-labelledby at that caption's id instead, which names the group without rendering a second one.
<fieldset> without a <legend> apps/web/components/apps/exchange2016calendar/Setup.tsx:57— A fieldset groups related controls but has no <legend> to name the group. Add a <legend> as its first child — or, if the group already has a visible caption beside it (or the fieldset is there only to disable its subtree and carries no group box), point aria-labelledby at that caption's id instead, which names the group without rendering a second one.
<fieldset> without a <legend> apps/web/components/apps/exchangecalendar/Setup.tsx:101— A fieldset groups related controls but has no <legend> to name the group. Add a <legend> as its first child — or, if the group already has a visible caption beside it (or the fieldset is there only to disable its subtree and carries no group box), point aria-labelledby at that caption's id instead, which names the group without rendering a second one.
<fieldset> without a <legend> apps/web/components/apps/ics-feedcalendar/Setup.tsx:61— A fieldset groups related controls but has no <legend> to name the group. Add a <legend> as its first child — or, if the group already has a visible caption beside it (or the fieldset is there only to disable its subtree and carries no group box), point aria-labelledby at that caption's id instead, which names the group without rendering a second one.
<fieldset> without a <legend> apps/web/components/apps/sendgrid/Setup.tsx:79— A fieldset groups related controls but has no <legend> to name the group. Add a <legend> as its first child — or, if the group already has a visible caption beside it (or the fieldset is there only to disable its subtree and carries no group box), point aria-labelledby at that caption's id instead, which names the group without rendering a second one.
<fieldset> without a <legend> apps/web/components/getting-started/steps-views/UserProfile.tsx:152— A fieldset groups related controls but has no <legend> to name the group. Add a <legend> as its first child — or, if the group already has a visible caption beside it (or the fieldset is there only to disable its subtree and carries no group box), point aria-labelledby at that caption's id instead, which names the group without rendering a second one.
Cross-context type BookingReportStatus (web → features) packages/features/bookingReport/repositories/IBookingReportRepository.ts:25— BookingReportStatus (context web) is exposed in features's public surface via ListBookingReportsFilters.status — couples the contexts.
Cross-context type BookingReportStatus (web → features) packages/features/bookingReport/repositories/IBookingReportRepository.ts:41— BookingReportStatus (context web) is exposed in features's public surface via BookingReportWithDetails.status — couples the contexts.
Cross-context type BookingReportStatus (web → features) packages/features/bookingReport/repositories/IBookingReportRepository.ts:117— BookingReportStatus (context web) is exposed in features's public surface via IBookingReportRepository.updateReportStatus — couples the contexts.
Cross-context type BookingReportStatus (web → features) packages/features/bookingReport/repositories/IBookingReportRepository.ts:123— BookingReportStatus (context web) is exposed in features's public surface via IBookingReportRepository.bulkLinkWatchlistWithStatus — couples the contexts.
Cross-context type BookingReportStatus (web → features) packages/features/bookingReport/repositories/IBookingReportRepository.ts:149— BookingReportStatus (context web) is exposed in features's public surface via IBookingReportRepository.dismissReportsByEmail — couples the contexts.
Cross-context type BookingReportStatus (web → features) packages/features/bookingReport/repositories/PrismaBookingReportRepository.ts:212— BookingReportStatus (context web) is exposed in features's public surface via PrismaBookingReportRepository.updateReportStatus — couples the contexts.
Cross-context type BookingReportStatus (web → features) packages/features/bookingReport/repositories/PrismaBookingReportRepository.ts:231— BookingReportStatus (context web) is exposed in features's public surface via PrismaBookingReportRepository.bulkLinkWatchlistWithStatus — couples the contexts.
Cross-context type BookingReportStatus (web → features) packages/features/bookingReport/repositories/PrismaBookingReportRepository.ts:324— BookingReportStatus (context web) is exposed in features's public surface via PrismaBookingReportRepository.dismissReportsByEmail — couples the contexts.
TooManyMethods: UserRepository REDACTED:124— TooManyMethods — 62 methods. The bar is 30 methods; this is 32 over it, 2.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: BookingRepository packages/features/bookings/repositories/BookingRepository.ts:340— TooManyMethods — 58 methods. The bar is 30 methods; this is 28 over it, 1.93× 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: SalesforceCRMService packages/app-store/salesforce/lib/CrmService.ts:114— TooManyMethods — 53 methods. The bar is 30 methods; this is 23 over it, 1.77× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: EventTypeRepository packages/features/eventtypes/repositories/eventTypeRepository.ts:81— TooManyMethods — 35 methods. The bar is 30 methods; this is 5 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.
TooManyMethods: ProfileRepository packages/features/profile/repositories/ProfileRepository.ts:94— 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: UsersRepository apps/api/v2/src/modules/users/users.repository.ts:15— 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: InputEventTypesService_2024_06_14 apps/api/v2/src/platform/event-types/event-types_2024_06_14/services/input-event-types.service.ts:55— 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: SelectedCalendarRepository packages/features/selectedCalendar/repositories/SelectedCalendarRepository.ts:43— TooManyMethods — 31 methods. The bar is 30 methods; this is 1 over it, 1.03× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
Low cohesion: UserRepository (LCOM4 6) REDACTED:124— UserRepository's methods fall into 6 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 6 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: AtomsSchedulesController (LCOM4 4) apps/api/v2/src/modules/atoms/controllers/atoms.schedules.controller.ts:45— AtomsSchedulesController's methods fall into 4 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 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: BookingsController_2024_04_15 (LCOM4 4) apps/api/v2/src/platform/bookings/2024-04-15/controllers/bookings.controller.ts:104— BookingsController_2024_04_15's methods fall into 4 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 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: BillingPortalService (LCOM4 4) packages/app-store/stripepayment/lib/services/base/BillingPortalService.ts:22— BillingPortalService's methods fall into 4 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 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: BookingEmailAndSmsTriggerDevTasker (LCOM4 4) packages/features/bookings/lib/tasker/BookingEmailAndSmsTriggerTasker.ts:5— BookingEmailAndSmsTriggerDevTasker's methods fall into 4 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 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: DistributedTracing (LCOM4 4) packages/lib/tracing/index.ts:16— DistributedTracing's methods fall into 4 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 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: AvailableSlotsService (LCOM4 4) REDACTED:143— AvailableSlotsService's methods fall into 4 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 4 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.
Swallowed exception (caught, then discarded) packages/lib/webstorage.ts:19— `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) packages/lib/webstorage.ts:29— `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) packages/lib/webstorage.ts:50— `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) packages/lib/webstorage.ts:61— `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) packages/features/conferencing/lib/videoClient.ts:171— `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) packages/features/conferencing/lib/videoClient.ts:195— `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) packages/app-store/dub/api/callback.ts:59— `catch (err)` 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.
AC4 · Keyboard semantics· Modal dialog does not manage focus · ×6
Modal dialog does not manage focus apps/web/app/(use-page-wrapper)/payment/[uid]/PaymentPage.tsx:107— This <div role="dialog"> is a modal dialog, but nothing moves focus into it when it opens and nothing keeps focus inside it while it is open, so a keyboard or screen-reader user keeps acting on the content behind it (WCAG 2.4.3). Use a native <dialog> opened with showModal(), a dialog component that traps focus, or move focus to the dialog on open, trap Tab inside it (or make the page behind inert) and return focus to the control that opened it on close.
Modal dialog does not manage focus apps/web/modules/bookings/components/BookingSuccessCard.tsx:38— This <div role="dialog"> is a modal dialog, but nothing moves focus into it when it opens and nothing keeps focus inside it while it is open, so a keyboard or screen-reader user keeps acting on the content behind it (WCAG 2.4.3). Use a native <dialog> opened with showModal(), a dialog component that traps focus, or move focus to the dialog on open, trap Tab inside it (or make the page behind inert) and return focus to the control that opened it on close.
Modal dialog does not manage focus apps/web/modules/bookings/components/DecoyBookingSuccessCard.tsx:38— This <div role="dialog"> is a modal dialog, but nothing moves focus into it when it opens and nothing keeps focus inside it while it is open, so a keyboard or screen-reader user keeps acting on the content behind it (WCAG 2.4.3). Use a native <dialog> opened with showModal(), a dialog component that traps focus, or move focus to the dialog on open, trap Tab inside it (or make the page behind inert) and return focus to the control that opened it on close.
Modal dialog does not manage focus REDACTED:504— This <div role="dialog"> is a modal dialog, but focus is moved into it, but nothing keeps it there: Tab walks out to the page behind, so a keyboard or screen-reader user keeps acting on the content behind it (WCAG 2.4.3). Use a native <dialog> opened with showModal(), a dialog component that traps focus, or move focus to the dialog on open, trap Tab inside it (or make the page behind inert) and return focus to the control that opened it on close.
Modal dialog does not manage focus apps/web/modules/videos/views/videos-meeting-ended-single-view.tsx:25— This <div role="dialog"> is a modal dialog, but nothing moves focus into it when it opens and nothing keeps focus inside it while it is open, so a keyboard or screen-reader user keeps acting on the content behind it (WCAG 2.4.3). Use a native <dialog> opened with showModal(), a dialog component that traps focus, or move focus to the dialog on open, trap Tab inside it (or make the page behind inert) and return focus to the control that opened it on close.
Modal dialog does not manage focus packages/platform/atoms/event-types/payments/PaymentForm.tsx:61— This <div role="dialog"> is a modal dialog, but nothing moves focus into it when it opens and nothing keeps focus inside it while it is open, so a keyboard or screen-reader user keeps acting on the content behind it (WCAG 2.4.3). Use a native <dialog> opened with showModal(), a dialog component that traps focus, or move focus to the dialog on open, trap Tab inside it (or make the page behind inert) and return focus to the control that opened it on close.
Focus outline removed inline apps/web/components/booking/BookingListItem.tsx:909— <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 apps/web/components/booking/BookingListItem.tsx:988— <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 REDACTED:740— <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 apps/web/modules/shell/user-dropdown/ProfileDropdown.tsx:46— <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 packages/app-store/vital/components/AppConfiguration.tsx:132— <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 packages/ui/components/editor/plugins/AddVariablesDropdown.tsx:158— <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).
Deprecated: querystring REDACTED:82— querystring 0.2.1, declared in REDACTED, is marked deprecated by its publisher: "The querystring API is considered Legacy. new code should use the URLSearchParams API instead.". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: supertest REDACTED:110— supertest 6.3.4, declared in REDACTED, is marked deprecated by its publisher: "Please upgrade to supertest v7.1.3+, see release notes at https://github.com/forwardemail/supertest/releases/tag/v7.1.3 - maintenance is supported by Forward Email @ https://forwardemail.net". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: @vercel/edge-config REDACTED:84— @vercel/edge-config 0.1.1, declared in REDACTED, is marked deprecated by its publisher: "This package has been renamed to @vercel/global-config. Install @vercel/global-config instead.". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: @types/stripe REDACTED:181— @types/stripe 8.0.417, declared in REDACTED, is marked deprecated by its publisher: "This is a stub types definition. stripe provides its own type definitions, so you do not need this installed.". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: @faker-js/faker REDACTED:91— @faker-js/faker 9.2.0, declared in REDACTED, is marked deprecated by its publisher: "Please update to a newer version". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: @hubspot/api-client packages/app-store/hubspot/REDACTED:10— @hubspot/api-client 6.0.1, declared in packages/app-store/hubspot/REDACTED, is marked deprecated by its publisher: "Version no longer supported. Upgrade to @latest". Replace it with the package or version that message names, or record why this one must stay.
Cross-context type BookingStatus (trpc → features) packages/features/bookings/repositories/IBookingRepository.ts:23— BookingStatus (context trpc) is exposed in features's public surface via BookingUpdateData.status — couples the contexts.
Cross-context type BookingStatus (trpc → features) packages/features/bookings/repositories/BookingRepository.ts:1849— BookingStatus (context trpc) is exposed in features's public surface via BookingRepository.updateBookingStatus — couples the contexts.
Cross-context type BookingStatus (trpc → features) packages/features/bookings/lib/handleConfirmation.ts:23— BookingStatus (context trpc) is exposed in features's public surface via handleConfirmation.handleConfirmation — couples the contexts.
Cross-context type BookingStatus (trpc → features) packages/features/bookings/lib/service/RegularBookingService.ts:2588— BookingStatus (context trpc) is exposed in features's public surface via RegularBookingService.fireBookingEvents — couples the contexts.
Cross-context type BookingStatus (trpc → features) packages/features/calendars/weeklyview/types/events.ts:10— BookingStatus (context trpc) is exposed in features's public surface via CalendarEvent.options — couples the contexts.
Cross-context type BookingStatus (trpc → features) packages/features/webhooks/lib/factory/base/BaseBookingPayloadBuilder.ts:47— BookingStatus (context trpc) is exposed in features's public surface via BookingPayloadParams.status — couples the contexts.
D12 · Dependency Hygiene· One package at two majors across the workspace · ×5
One package at two majors across the workspace: next — `next` is maintained at 2 different major versions inside this one repository — major 15 in REDACTED; major 16 in REDACTED. Every major carries its own breaking changes, advisories and upgrade path, so the cost of keeping current is paid more than once; and where the packages are installed together, the resolver cannot dedupe them, so both copies ship.
One package at two majors across the workspace: react-easy-crop — `react-easy-crop` is maintained at 2 different major versions inside this one repository — major 3 in REDACTED; major 5 in REDACTED. Every major carries its own breaking changes, advisories and upgrade path, so the cost of keeping current is paid more than once; and where the packages are installed together, the resolver cannot dedupe them, so both copies ship.
One package at two majors across the workspace: stripe — `stripe` is maintained at 2 different major versions inside this one repository — major 9 in REDACTED, packages/app-store/stripepayment/REDACTED, REDACTED; major 15 in REDACTED. Every major carries its own breaking changes, advisories and upgrade path, so the cost of keeping current is paid more than once; and where the packages are installed together, the resolver cannot dedupe them, so both copies ship.
One package at two majors across the workspace: tailwind-merge — `tailwind-merge` is maintained at 2 different major versions inside this one repository — major 1 in packages/platform/atoms/REDACTED, REDACTED; major 3 in packages/coss-ui/REDACTED. Every major carries its own breaking changes, advisories and upgrade path, so the cost of keeping current is paid more than once; and where the packages are installed together, the resolver cannot dedupe them, so both copies ship.
One package at two majors across the workspace: uuid — `uuid` is maintained at 2 different major versions inside this one repository — major 8 in REDACTED, REDACTED, packages/app-store/stripepayment/REDACTED (+3 more); major 11 in REDACTED. Every major carries its own breaking changes, advisories and upgrade path, so the cost of keeping current is paid more than once; and where the packages are installed together, the resolver cannot dedupe them, so both copies ship.
Cross-context type CreateBookingInput (types → v2) apps/api/v2/src/platform/bookings/2024-08-13/controllers/bookings.controller.ts:105— CreateBookingInput (context types) is exposed in v2's public surface via BookingsController_2024_08_13.createBooking — couples the contexts.
Cross-context type CreateBookingInput (types → v2) apps/api/v2/src/platform/bookings/2024-08-13/services/bookings.service.ts:112— CreateBookingInput (context types) is exposed in v2's public surface via BookingsService_2024_08_13.createBooking — couples the contexts.
Cross-context type CreateBookingInput (types → v2) apps/api/v2/src/platform/bookings/2024-08-13/services/bookings.service.ts:188— CreateBookingInput (context types) is exposed in v2's public surface via BookingsService_2024_08_13.getBookedEventType — couples the contexts.
Cross-context type CreateBookingInput (types → v2) apps/api/v2/src/platform/bookings/2024-08-13/services/bookings.service.ts:217— CreateBookingInput (context types) is exposed in v2's public surface via BookingsService_2024_08_13.hasRequiredBookingFieldsResponses — couples the contexts.
Cross-context type CreateBookingInput (types → v2) apps/api/v2/src/platform/bookings/2024-08-13/services/errors.service.ts:10— CreateBookingInput (context types) is exposed in v2's public surface via ErrorsBookingsService_2024_08_13.handleEventTypeToBeBookedNotFound — couples the contexts.
Cross-context type RescheduleBookingInput (types → v2) apps/api/v2/src/platform/bookings/2024-08-13/controllers/bookings.controller.ts:296— RescheduleBookingInput (context types) is exposed in v2's public surface via BookingsController_2024_08_13.rescheduleBooking — couples the contexts.
Cross-context type RescheduleBookingInput (types → v2) apps/api/v2/src/platform/bookings/2024-08-13/services/bookings.service.ts:743— RescheduleBookingInput (context types) is exposed in v2's public surface via BookingsService_2024_08_13.rescheduleBooking — couples the contexts.
Cross-context type RescheduleBookingInput (types → v2) apps/api/v2/src/platform/bookings/2024-08-13/services/bookings.service.ts:890— RescheduleBookingInput (context types) is exposed in v2's public surface via BookingsService_2024_08_13.isRescheduleSeatedBody — couples the contexts.
Cross-context type RescheduleBookingInput (types → v2) apps/api/v2/src/platform/bookings/2024-08-13/services/input.service.ts:515— RescheduleBookingInput (context types) is exposed in v2's public surface via InputBookingsService_2024_08_13.createRescheduleBookingRequest — couples the contexts.
Cross-context type RescheduleBookingInput (types → v2) apps/api/v2/src/platform/bookings/2024-08-13/services/input.service.ts:576— RescheduleBookingInput (context types) is exposed in v2's public surface via InputBookingsService_2024_08_13.isRescheduleSeatedBody — couples the contexts.
Cross-context type PrivateLinkOutput (types → v2) apps/api/v2/src/platform/event-types-private-links/services/private-links.service.ts:20— PrivateLinkOutput (context types) is exposed in v2's public surface via PrivateLinksService.createPrivateLink — couples the contexts.
Cross-context type PrivateLinkOutput (types → v2) apps/api/v2/src/platform/event-types-private-links/services/private-links.service.ts:50— PrivateLinkOutput (context types) is exposed in v2's public surface via PrivateLinksService.getPrivateLinks — couples the contexts.
Cross-context type PrivateLinkOutput (types → v2) apps/api/v2/src/platform/event-types-private-links/services/private-links.service.ts:71— PrivateLinkOutput (context types) is exposed in v2's public surface via PrivateLinksService.updatePrivateLink — couples the contexts.
Cross-context type PrivateLinkOutput (types → v2) apps/api/v2/src/platform/event-types-private-links/services/private-links-output.service.ts:24— PrivateLinkOutput (context types) is exposed in v2's public surface via PrivateLinksOutputService.transformToOutput — couples the contexts.
Cross-context type PrivateLinkOutput (types → v2) apps/api/v2/src/platform/event-types-private-links/services/private-links-output.service.ts:43— PrivateLinkOutput (context types) is exposed in v2's public surface via PrivateLinksOutputService.transformArrayToOutput — couples the contexts.
Cross-context type BlocklistScope (features → web) apps/web/modules/blocklist/components/BlocklistEntryDetailsSheet.tsx:23— BlocklistScope (context features) is exposed in web's public surface via BlocklistEntryDetailsSheetProps.scope — couples the contexts.
Cross-context type BlocklistScope (features → web) apps/web/modules/blocklist/components/BlockedEntriesTable.tsx:20— BlocklistScope (context features) is exposed in web's public surface via BlockedEntriesTableProps.scope — couples the contexts.
Cross-context type BlocklistScope (features → web) apps/web/modules/blocklist/components/BookingReportDetailsModal.tsx:20— BlocklistScope (context features) is exposed in web's public surface via BookingReportDetailsModalProps.scope — couples the contexts.
Cross-context type BlocklistScope (features → web) apps/web/modules/blocklist/components/CreateBlocklistEntryModal.tsx:20— BlocklistScope (context features) is exposed in web's public surface via CreateBlocklistEntryModalProps.scope — couples the contexts.
Cross-context type BlocklistScope (features → web) apps/web/modules/blocklist/components/PendingReportsTable.tsx:20— BlocklistScope (context features) is exposed in web's public surface via PendingReportsTableProps.scope — couples the contexts.
IC1 · Incompleteness & stubs· Guard cannot change the result · ×5
Guard cannot change the result — returns what the code already falls through to apps/web/components/integrations/SubHeadingTitleWithConnections.tsx:6— The guard above `return opts.singular;` also returns `opts.singular`, so no input can make it matter. Implement the distinction that was intended, or delete the guard.
Guard cannot change the result — returns what the code already falls through to apps/web/lib/app-providers-app-dir.tsx:120— The guard above `return RemainingProviders;` also returns `RemainingProviders`, so no input can make it matter. Implement the distinction that was intended, or delete the guard.
Guard cannot change the result — returns what the code already falls through to apps/web/lib/app-providers.tsx:287— The guard above `return RemainingProviders;` also returns `RemainingProviders`, so no input can make it matter. Implement the distinction that was intended, or delete the guard.
Guard cannot change the result — returns what the code already falls through to apps/web/modules/users/components/UserTable/ChangeUserRoleModal.tsx:8— The guard above `return null;` also returns `null`, so no input can make it matter. Implement the distinction that was intended, or delete the guard.
Guard cannot change the result — returns what the code already falls through to apps/web/modules/users/components/UserTable/InviteMemberModal.tsx:25— The guard above `return null;` also returns `null`, so no input can make it matter. Implement the distinction that was intended, or delete the guard.
Outbound HTTP without resilience apps/api/v2/src/modules/conferencing/services/office365-video.service.ts:81— `fetch(` 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 apps/api/v2/src/modules/conferencing/services/office365-video.service.ts:95— `fetch(` 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 apps/api/v2/src/modules/conferencing/services/zoom-video.service.ts:65— `fetch(` 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 apps/api/v2/src/platform/calendars/services/outlook.service.ts:136— `fetch(` 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 apps/api/v2/src/platform/calendars/services/outlook.service.ts:150— `fetch(` 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.
AC2 · Forms & labels· <Select> field component without a label · ×4
<Select> field component without a label apps/web/components/booking/CancelBooking.tsx:53— 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.
<Select> field component without a label apps/web/components/dialog/WrongAssignmentDialog.tsx:196— 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.
<Select> field component without a label apps/web/modules/booking-audit/components/BookingHistory.tsx:121— This UI-library field component has no label / aria-label / aria-labelledby / id — and neither does anything it renders (a name prop is the form-submission key, not a label) — 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.
<Select> field component without a label apps/web/modules/calendars/components/SelectedCalendarsSettingsWebWrapper.tsx:277— This UI-library field component has no label / aria-label / aria-labelledby / id — and neither does anything it renders (a name prop is the form-submission key, not a label) — so it likely renders an unlabelled control. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
AC3 · Page structure· Page without a main landmark · ×4
Page without a main landmark apps/web/app/layout.tsx:108— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
Page without a main landmark apps/web/public/country-flag-icons/3x2/index.html:3— 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 packages/embeds/embed-core/index.html:1— 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 packages/embeds/embed-react/index.html:1— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
Cross-context type CancelBookingInput (types → v2) apps/api/v2/src/platform/bookings/2024-08-13/controllers/bookings.controller.ts:336— CancelBookingInput (context types) is exposed in v2's public surface via BookingsController_2024_08_13.cancelBooking — couples the contexts.
Cross-context type CancelBookingInput (types → v2) apps/api/v2/src/platform/bookings/2024-08-13/services/bookings.service.ts:894— CancelBookingInput (context types) is exposed in v2's public surface via BookingsService_2024_08_13.cancelBooking — couples the contexts.
Cross-context type CancelBookingInput (types → v2) apps/api/v2/src/platform/bookings/2024-08-13/services/input.service.ts:773— CancelBookingInput (context types) is exposed in v2's public surface via InputBookingsService_2024_08_13.createCancelBookingRequest — couples the contexts.
Cross-context type CancelBookingInput (types → v2) apps/api/v2/src/platform/bookings/2024-08-13/services/input.service.ts:814— CancelBookingInput (context types) is exposed in v2's public surface via InputBookingsService_2024_08_13.isCancelSeatedBody — couples the contexts.
Weak hash algorithm apps/web/scripts/copy-app-store-static.js:35— 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+ (`createHash("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 packages/features/auth/lib/verifyCodeUnAuthenticated.ts:17— 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+ (`createHash("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 packages/features/auth/lib/verifyEmail.ts:105— 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+ (`createHash("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 packages/trpc/server/routers/viewer/me/get.handler.ts:122— 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+ (`createHash("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· <TextArea> field component without a label · ×3
<TextArea> field component without a label apps/web/components/booking/CancelBooking.tsx:66— 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.
<TextArea> field component without a label apps/web/components/booking/CancelBooking.tsx:231— 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.
<TextArea> field component without a label apps/web/components/dialog/RescheduleDialog.tsx:51— This UI-library field component has no label / aria-label / aria-labelledby / id — and neither does anything it renders (a name prop is the form-submission key, not a label) — so it likely renders an unlabelled control. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
AC2 · Forms & labels· <DatePicker> field component without a label · ×3
<DatePicker> field component without a label apps/web/components/settings/TravelScheduleModal.tsx:135— This UI-library field component has no label / aria-label / aria-labelledby / id — and neither does anything it renders (a name prop is the form-submission key, not a label) — 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 apps/web/modules/bookings/components/Booker.tsx:436— This UI-library field component has no label / aria-label / aria-labelledby / id — and neither does anything it renders (a name prop is the form-submission key, not a label) — 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 apps/web/modules/bookings/components/Booker.tsx:473— This UI-library field component has no label / aria-label / aria-labelledby / id — and neither does anything it renders (a name prop is the form-submission key, not a label) — so it likely renders an unlabelled control. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
AC3 · Page structure· Data table has no header cells · ×3
Data table has no header cells REDACTED:564— 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 REDACTED:590— 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 REDACTED:619— 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).
Floating npm dependency: @calcom/lib — `@calcom/lib` is declared as `*` in packages/app-store/lyra/REDACTED, which names no releasable version: any published version satisfies it. A production dependency that cannot be resolved to one immutable release makes the build non-reproducible — two installs a day apart can ship different code — and leaves nothing for a vulnerability scanner to match against.
Floating npm dependency: @calcom/prisma — `@calcom/prisma` is declared as `*` in packages/app-store/lyra/REDACTED, which names no releasable version: any published version satisfies it. A production dependency that cannot be resolved to one immutable release makes the build non-reproducible — two installs a day apart can ship different code — and leaves nothing for a vulnerability scanner to match against.
Floating npm dependency: @snyk/protect — `@snyk/protect` is declared as `latest` in REDACTED, which names no releasable version: `latest` is a moving dist-tag, not a version. A production dependency that cannot be resolved to one immutable release makes the build non-reproducible — two installs a day apart can ship different code — and leaves nothing for a vulnerability scanner to match against.
Cross-context type GetSlotsInput_2024_09_04 (types → v2) apps/api/v2/src/modules/slots/slots-2024-09-04/controllers/slots.controller.ts:60— GetSlotsInput_2024_09_04 (context types) is exposed in v2's public surface via SlotsController_2024_09_04.getAvailableSlots — couples the contexts.
Cross-context type GetSlotsInput_2024_09_04 (types → v2) apps/api/v2/src/modules/slots/slots-2024-09-04/services/slots-input.service.ts:47— GetSlotsInput_2024_09_04 (context types) is exposed in v2's public surface via SlotsInputService_2024_09_04.transformGetSlotsQuery — couples the contexts.
Cross-context type GetSlotsInput_2024_09_04 (types → v2) apps/api/v2/src/modules/slots/slots-2024-09-04/services/slots.service.ts:85— GetSlotsInput_2024_09_04 (context types) is exposed in v2's public surface via SlotsService_2024_09_04.getAvailableSlots — couples the contexts.
Cross-context type BookerLayoutsInputEnum_2024_06_14 (enums → types) packages/platform/types/event-types/event-types_2024_06_14/inputs/booker-layouts.input.ts:17— BookerLayoutsInputEnum_2024_06_14 (context enums) is exposed in types's public surface via LayoutValidator.validate — couples the contexts.
Cross-context type BookerLayoutsInputEnum_2024_06_14 (enums → types) packages/platform/types/event-types/event-types_2024_06_14/inputs/booker-layouts.input.ts:77— BookerLayoutsInputEnum_2024_06_14 (context enums) is exposed in types's public surface via BookerLayouts_2024_06_14.defaultLayout — couples the contexts.
Cross-context type BookerLayoutsInputEnum_2024_06_14 (enums → types) packages/platform/types/event-types/event-types_2024_06_14/inputs/booker-layouts.input.ts:82— BookerLayoutsInputEnum_2024_06_14 (context enums) is exposed in types's public surface via BookerLayouts_2024_06_14.enabledLayouts — couples the contexts.
IC1 · Incompleteness & stubs· Both branches are identical · ×3
Both branches are identical — the condition decides nothing apps/web/components/PageWrapperAppDir.tsx:29— 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 apps/web/components/ui/UsernameAvailability/PremiumTextfield.tsx:247— 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 apps/web/modules/settings/my-account/profile-view.tsx:631— 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.
Hollow method — returns a constant without doing the work packages/app-store/delegationCredential.ts:138— `getFirstDelegationConferencingCredential` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in.
Hollow method — returns a constant without doing the work packages/app-store/delegationCredential.ts:144— `getFirstDelegationConferencingCredentialAppLocation` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in.
Hollow method — returns a constant without doing the work packages/app-store/delegationCredential.ts:150— `findUniqueDelegationCalendarCredential` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in.
P12 · CI test-gate honesty· Workspace package's tests never run by CI · ×3
Workspace package's tests never run by CI REDACTED:1— `packages/lib` is a workspace package with 372 test(s) in 43 file(s) (e.g. `packages/lib/CalEventParser.test.ts`, `packages/lib/CalendarService.test.ts`), but no CI command runs them — no step names the package and no workspace-wide command reaches it, so its tests gate nothing. Run its tests in CI, or delete them.
Workspace package's tests never run by CI packages/platform/atoms/REDACTED:16— `packages/platform/atoms` is a workspace package with 23 test(s) in 3 file(s) (e.g. `packages/platform/atoms/event-types/__tests__/EventTypeListItem.test.tsx`, `packages/platform/atoms/event-types/__tests__/formatEventTypeDuration.test.ts`), but no CI command runs them — no step names the package and no workspace-wide command reaches it, so its tests gate nothing. Run its tests in CI, or delete them.
Workspace package's tests never run by CI packages/platform/utils/REDACTED:8— `packages/platform/utils` is a workspace package with 8 test(s) in 1 file(s) (e.g. `packages/platform/utils/tests/permissions.test.ts`), but no CI command runs them — no step names the package and no workspace-wide command reaches it, so its tests gate nothing. Run its tests in CI, or delete them.
Dead file (~240 LoC) apps/api/v2/src/modules/oauth-clients/controllers/oauth-flow/oauth-flow.controller.e2e-spec.ts— no import path from any entry point (919 application, 89 tooling, 646 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~240 LoC) apps/web/modules/users/components/UserTable/UserTableActions.tsx— no import path from any entry point (919 application, 89 tooling, 646 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/web/modules/users/components/UserTable/UserListTable.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 (~240 LoC) packages/features/booking-audit/lib/service/BookingAuditProducerService.interface.ts— no import path from any entry point (919 application, 89 tooling, 646 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (packages/features/booking-audit/di/BookingAuditProducerService.container.ts, packages/features/booking-audit/lib/service/BookingAuditTaskerProducerService.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 (~192 LoC) apps/web/modules/filters/components/TeamsFilter.tsx— no import path from any entry point (919 application, 89 tooling, 646 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~192 LoC) apps/web/modules/onboarding/components/onboarding-migrate-members-browser-view.tsx— no import path from any entry point (919 application, 89 tooling, 646 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~192 LoC) packages/features/form/components/Select.tsx— no import path from any entry point (919 application, 89 tooling, 646 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/web/components/ui/form/CheckedSelect.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
KeyInput.KeyField (cyclomatic 23) packages/app-store/btcpayserver/components/KeyInput.tsx:49— KeyInput.KeyField has cyclomatic complexity 23 (threshold 15). Of this number, 20 points are the body's own statements and 3 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.
KeyInput.KeyField (cyclomatic 23) packages/app-store/hitpay/components/KeyInput.tsx:49— KeyInput.KeyField has cyclomatic complexity 23 (threshold 15). Of this number, 20 points are the body's own statements and 3 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.
EventTypeAppSettingsInterface.EventTypeAppSettingsInterface (cyclomatic 17) packages/app-store/alby/components/EventTypeAppSettingsInterface.tsx:15— EventTypeAppSettingsInterface.EventTypeAppSettingsInterface has cyclomatic complexity 17 (threshold 15). Of this number, 12 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.
EventTypeAppSettingsInterface.EventTypeAppSettingsInterface (cyclomatic 17) packages/app-store/paypal/components/EventTypeAppSettingsInterface.tsx:22— EventTypeAppSettingsInterface.EventTypeAppSettingsInterface has cyclomatic complexity 17 (threshold 15). Of this number, 10 points are the body's own statements and 7 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.
reschedule.Reschedule (cyclomatic 16) packages/app-store/vital/lib/reschedule.ts:22— reschedule.Reschedule has cyclomatic complexity 16 (threshold 15). 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, 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.
reschedule.Reschedule (cyclomatic 16) packages/app-store/wipemycalother/lib/reschedule.ts:22— reschedule.Reschedule has cyclomatic complexity 16 (threshold 15). 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, 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.
reschedule.Reschedule (cognitive 23) packages/app-store/vital/lib/reschedule.ts:22— reschedule.Reschedule has cognitive complexity 23 (threshold 15). Drivers by points: if/else 6 (12 pts), boolean chains 5, error handling 2 (4 pts), ternaries 1 (2 pts) (nesting depth added 9). Of this number, 14 points are the body's own statements and 9 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.
reschedule.Reschedule (cognitive 23) packages/app-store/wipemycalother/lib/reschedule.ts:22— reschedule.Reschedule has cognitive complexity 23 (threshold 15). Drivers by points: if/else 6 (12 pts), boolean chains 5, error handling 2 (4 pts), ternaries 1 (2 pts) (nesting depth added 9). Of this number, 14 points are the body's own statements and 9 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.
KeyInput.KeyField (cognitive 19) packages/app-store/btcpayserver/components/KeyInput.tsx:49— KeyInput.KeyField has cognitive complexity 19 (threshold 15). Drivers by points: boolean chains 14, if/else 3, ternaries 2. Of this number, 16 points are the body's own statements and 3 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.
KeyInput.KeyField (cognitive 19) packages/app-store/hitpay/components/KeyInput.tsx:49— KeyInput.KeyField has cognitive complexity 19 (threshold 15). Drivers by points: boolean chains 14, if/else 3, ternaries 2. Of this number, 16 points are the body's own statements and 3 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.
getServerSideProps.getServerSideProps (cognitive 16) apps/web/server/lib/[user]/getServerSideProps.ts:78— getServerSideProps.getServerSideProps has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 7, if/else 5, ternaries 4. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
getServerSideProps.getServerSideProps (cognitive 16) apps/web/server/lib/auth/login/getServerSideProps.tsx:11— getServerSideProps.getServerSideProps has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (11 pts), error handling 2 (5 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Cross-context type SlotFormat (enums → v2) apps/api/v2/src/modules/slots/slots-2024-04-15/services/slots-output.service.ts:18— SlotFormat (context enums) is exposed in v2's public surface via SlotsOutputService_2024_04_15.getOutputSlots — couples the contexts.
Cross-context type SlotFormat (enums → v2) apps/api/v2/src/modules/slots/slots-2024-09-04/services/slots-output.service.ts:26— SlotFormat (context enums) is exposed in v2's public surface via SlotsOutputService_2024_09_04.getAvailableSlots — couples the contexts.
Cross-context type IconName (ui → web) apps/web/app/icons/IconGrid.tsx:6— IconName (context ui) is exposed in web's public surface via IconGrid.IconGrid — couples the contexts.
Cross-context type IconName (ui → web) apps/web/modules/onboarding/components/plan-icon.tsx:20— IconName (context ui) is exposed in web's public surface via plan-icon.PlanIcon — couples the contexts.
Cross-context type UserType (features → stripepayment) packages/app-store/stripepayment/lib/customer.ts:34— UserType (context features) is exposed in stripepayment's public surface via customer.getStripeCustomerId — couples the contexts.
Cross-context type UserType (features → stripepayment) packages/app-store/stripepayment/lib/customer.ts:69— UserType (context features) is exposed in stripepayment's public surface via customer.deleteStripeCustomer — couples the contexts.
Cross-context type JsonValue (atoms → features) packages/features/bookings/lib/handleNewBooking/types.ts:33— JsonValue (context atoms) is exposed in features's public surface via IEventTypePaymentCredentialType.key — couples the contexts.
Cross-context type JsonValue (atoms → features) packages/features/bookings/repositories/BookingPaymentRepository.interface.ts:9— JsonValue (context atoms) is exposed in features's public surface via BookingPaymentWithCredentials.booking — couples the contexts.
Cross-context type SlotFormat (enums → types) packages/platform/types/slots/slots-2024-04-15/inputs/index.ts:83— SlotFormat (context enums) is exposed in types's public surface via GetAvailableSlotsInput_2024_04_15.slotFormat — couples the contexts.
Cross-context type SlotFormat (enums → types) packages/platform/types/slots/slots-2024-09-04/inputs/get-slots.input.ts:66— SlotFormat (context enums) is exposed in types's public surface via GetAvailableSlotsInput_2024_09_04.format — couples the contexts.
IC1 · Incompleteness & stubs· Empty method body · ×2
Empty method body — does nothing with its inputs apps/web/modules/data-table/components/segment/SaveFilterSegmentButton.tsx:30— `mutate` 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 apps/web/modules/data-table/components/segment/SaveFilterSegmentButton.tsx:34— `mutate` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it.
Skeleton type — most members are unfinished packages/app-store/alby/lib/PaymentService.ts:17— `AlbyPaymentService` has 6 unfinished members out of 10 declared members (methods and accessors, whether or not each carries a body) — a scaffolded class that was never implemented.
Skeleton type — most members are unfinished packages/app-store/hitpay/lib/PaymentService.ts:26— `HitPayPaymentService` has 6 unfinished members out of 10 declared members (methods and accessors, whether or not each carries a body) — a scaffolded class that was never implemented.
R10 · Code Duplication· Duplicated block with local edits (140 matched lines × 2 locations) · ×2
Duplicated block with local edits (140 matched lines × 2 locations) apps/web/components/security/EnableTwoFactorModal.tsx:31— apps/web/components/security/EnableTwoFactorModal.tsx:31 · apps/web/components/settings/EnableTwoFactorModal.tsx:35 — the two spans are one implementation copied and then locally edited — 913 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 (140 matched lines × 2 locations) packages/coss-ui/src/components/dialog.tsx:11— packages/coss-ui/src/components/dialog.tsx:11 · packages/coss-ui/src/components/sheet.tsx:9 — the two spans are one implementation copied and then locally edited — 532 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.
Dead file (~396 LoC) apps/api/v2/src/app.e2e-spec.ts— no import path from any entry point (919 application, 89 tooling, 646 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~396 LoC) apps/api/v2/src/platform/calendars/controllers/calendars.controller.e2e-spec.ts— no import path from any entry point (919 application, 89 tooling, 646 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~201 LoC) apps/api/v2/src/modules/auth/guards/roles/roles.guard.ts— no import path from any entry point (919 application, 89 tooling, 646 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~201 LoC) apps/web/modules/onboarding/components/onboarding-organization-browser-view.tsx— no import path from any entry point (919 application, 89 tooling, 646 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
AC2 · Forms & labels· <TextField> field component without a label · ×1
<TextField> field component without a label apps/web/modules/apps/apps-view.tsx:41— 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.
AC2 · Forms & labels· <RadioGroup> field component without a label · ×1
<RadioGroup> field component without a label apps/web/modules/data-table/components/segment/SaveFilterSegmentButton.tsx:171— This UI-library field component has no label / aria-label / aria-labelledby / id — and neither does anything it renders (a name prop is the form-submission key, not a label) — so it likely renders an unlabelled control. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
AC3 · Page structure· Heading level jumps from h1 to h3 · ×1
Heading level jumps from h1 to h3 apps/web/app/notFoundClient.tsx:100— Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
AC3 · Page structure· Heading level jumps from h2 to h4 · ×1
Heading level jumps from h2 to h4 apps/web/components/apps/AppPage.tsx:423— Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
AC4 · Keyboard semantics· Link used as a button (placeholder href) · ×1
Link used as a button (placeholder href) apps/web/modules/webhooks/components/WebhookListItem.tsx:108— An <a href="#"> (or javascript:) with a click handler is a button dressed as a link — it announces the wrong role and stops working without JS. Use a <button> for an action.
AC7 · A11y enforcement· Accessibility enforcement below the top rung · ×1
Accessibility enforcement below the top rung — No accessibility enforcement found — your Biome config enables no a11y rules and there's no axe/pa11y/Lighthouse in tests or CI. Start by turning on Biome's own a11y rule group to catch issues at author time. What was searched, so you can tell an absence from a miss: the 881 markup file(s) this pass actually assessed, the linter configuration checked in beside them, and this repository's test and CI files — matched by name against the accessibility checkers this dimension carries. An audit run outside the repository, a hosted scanner, or a check whose name is not one of those, is not seen here.
RegularBookingService.handler (cyclomatic 282) packages/features/bookings/lib/service/RegularBookingService.ts:486— RegularBookingService.handler has cyclomatic complexity 282 (threshold 15). Of this number, 269 points are the body's own statements and 13 belong to 6 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
bookings-single-view.Success (cyclomatic 204) REDACTED:108— bookings-single-view.Success has cyclomatic complexity 204 (threshold 15). Of this number, 167 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.
update.handler.updateHandler (cyclomatic 110) packages/trpc/server/routers/viewer/eventTypes/heavy/update.handler.ts:60— update.handler.updateHandler has cyclomatic complexity 110 (threshold 15). Of this number, 102 points are the body's own statements and 8 belong to 4 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.
next-auth-options.getOptions (cyclomatic 103) packages/features/auth/lib/next-auth-options.ts:374— next-auth-options.getOptions has cyclomatic complexity 103 (threshold 15). Of this number, 93 points are the body's own statements and 10 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.
Booker.BookerComponent (cyclomatic 87) apps/web/modules/bookings/components/Booker.tsx:55— Booker.BookerComponent has cyclomatic complexity 87 (threshold 15). Of this number, 66 points are the body's own statements and 21 belong to 10 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.
EventAdvancedTab.EventAdvancedTab (cyclomatic 83) apps/web/modules/event-types/components/tabs/advanced/EventAdvancedTab.tsx:404— EventAdvancedTab.EventAdvancedTab has cyclomatic complexity 83 (threshold 15). Of this number, 36 points are the body's own statements and 47 belong to 25 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.
signup-view.Signup (cyclomatic 78) apps/web/modules/signup-view.tsx:192— signup-view.Signup has cyclomatic complexity 78 (threshold 15). Of this number, 51 points are the body's own statements and 27 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.
AvailableSlotsService._getAvailableSlots (cyclomatic 73) REDACTED:897— AvailableSlotsService._getAvailableSlots has cyclomatic complexity 73 (threshold 15). Of this number, 53 points are the body's own statements and 20 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.
handleCancelBooking.handler (cyclomatic 66) packages/features/bookings/lib/handleCancelBooking.ts:81— handleCancelBooking.handler has cyclomatic complexity 66 (threshold 15). Of this number, 63 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.
BookingActionsDropdown.BookingActionsDropdown (cyclomatic 63) apps/web/components/booking/actions/BookingActionsDropdown.tsx:63— BookingActionsDropdown.BookingActionsDropdown has cyclomatic complexity 63 (threshold 15). Of this number, 28 points are the body's own statements and 35 belong to 14 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.
store.createBookerStore (cyclomatic 63) packages/features/bookings/Booker/store.ts:441— store.createBookerStore has cyclomatic complexity 63 (threshold 15). Most of this is not in the body itself: 1 of the 63 points is its own statement and the rest belongs to 10 function literals inside it that branch (lines 561, 458, 442, …). 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.
event-types-listing-view.InfiniteEventTypeList (cyclomatic 61) apps/web/modules/event-types/views/event-types-listing-view.tsx:280— event-types-listing-view.InfiniteEventTypeList has cyclomatic complexity 61 (threshold 15). Most of this is not in the body itself: 6 of the 61 points are its own statements and the rest belongs to 13 function items inside it that branch (a function literal at line 540, moveEventType, a function literal at line 481, …). 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.
UserListTable.UserListTableContent (cyclomatic 60) apps/web/modules/users/components/UserTable/UserListTable.tsx:171— UserListTable.UserListTableContent has cyclomatic complexity 60 (threshold 15). Most of this is not in the body itself: 15 of the 60 points are its own statements and the rest belongs to 12 function items inside it that branch (a function literal at line 527, handleDownload, a function literal at line 217, …). 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.
AppPage.AppPage (cyclomatic 58) apps/web/components/apps/AppPage.tsx:66— AppPage.AppPage has cyclomatic complexity 58 (threshold 15). Of this number, 25 points are the body's own statements and 33 belong to 10 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.
getBookingResponsesSchema.superRefineField (cyclomatic 55) packages/features/bookings/lib/getBookingResponsesSchema.ts:88— getBookingResponsesSchema.superRefineField has cyclomatic complexity 55 (threshold 15). Of this number, 53 points are the body's own statements and 2 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.
BookingListItem.BookingListItem (cyclomatic 53) apps/web/components/booking/BookingListItem.tsx:130— BookingListItem.BookingListItem has cyclomatic complexity 53 (threshold 15). Of this number, 49 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.
AvailableTimes.SlotItem (cyclomatic 53) apps/web/modules/bookings/components/AvailableTimes.tsx:79— AvailableTimes.SlotItem has cyclomatic complexity 53 (threshold 15). Of this number, 43 points are the body's own statements and 10 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.
WebhookForm.WebhookForm (cyclomatic 53) apps/web/modules/webhooks/components/WebhookForm.tsx:244— WebhookForm.WebhookForm has cyclomatic complexity 53 (threshold 15). Of this number, 24 points are the body's own statements and 29 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.
bookings-single-view.getServerSideProps.getServerSideProps (cyclomatic 52) apps/web/modules/bookings/views/bookings-single-view.getServerSideProps.tsx:39— bookings-single-view.getServerSideProps.getServerSideProps has cyclomatic complexity 52 (threshold 15). Of this number, 39 points are the body's own statements and 13 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.
onboarding-invite-browser-view.OnboardingInviteBrowserView (cyclomatic 52) apps/web/modules/onboarding/components/onboarding-invite-browser-view.tsx:34— onboarding-invite-browser-view.OnboardingInviteBrowserView has cyclomatic complexity 52 (threshold 15). Of this number, 44 points are the body's own statements and 8 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.
updateProfile.handler.updateProfileHandler (cyclomatic 52) packages/trpc/server/routers/viewer/me/updateProfile.handler.ts:41— updateProfile.handler.updateProfileHandler has cyclomatic complexity 52 (threshold 15). Of this number, 48 points are the body's own statements and 4 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.
MultiplePrivateLinksController.MultiplePrivateLinksController (cyclomatic 50) apps/web/modules/event-types/components/MultiplePrivateLinksController.tsx:24— MultiplePrivateLinksController.MultiplePrivateLinksController has cyclomatic complexity 50 (threshold 15). Most of this is not in the body itself: 9 of the 50 points are its own statements and the rest belongs to 14 function items inside it that branch (a function literal at line 173, a function literal at line 226, updateLinkSettings, …). 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.
BookerPlatformWrapper.BookerPlatformWrapperComponent (cyclomatic 50) packages/platform/atoms/booker/BookerPlatformWrapper.tsx:50— BookerPlatformWrapper.BookerPlatformWrapperComponent has cyclomatic complexity 50 (threshold 15). Of this number, 22 points are the body's own statements and 28 belong to 13 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.
useBookings.useBookings (cyclomatic 49) apps/web/modules/bookings/hooks/useBookings.ts:111— useBookings.useBookings has cyclomatic complexity 49 (threshold 15). Most of this is not in the body itself: 6 of the 49 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 138, 311, 288, …). 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.
AppCreateUpdateForm.AppForm (cyclomatic 49) packages/app-store-cli/src/components/AppCreateUpdateForm.tsx:14— AppCreateUpdateForm.AppForm has cyclomatic complexity 49 (threshold 15). Of this number, 46 points are the body's own statements and 3 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.
Embed.EmbedTypeCodeAndPreviewDialogContent (cyclomatic 48) REDACTED:699— Embed.EmbedTypeCodeAndPreviewDialogContent has cyclomatic complexity 48 (threshold 15). Of this number, 28 points are the body's own statements and 20 belong to 7 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
DatePicker.Days (cyclomatic 47) packages/features/calendars/components/DatePicker.tsx:144— DatePicker.Days has cyclomatic complexity 47 (threshold 15). Most of this is not in the body itself: 12 of the 47 points are its own statements and the rest belongs to 5 function items inside it that branch (a function literal at line 251, isActive, useHandleInitialDateSelection, …). 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.
getPublicEvent.getPublicEvent (cyclomatic 46) packages/features/eventtypes/lib/getPublicEvent.ts:284— getPublicEvent.getPublicEvent has cyclomatic complexity 46 (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.
DataTableSegmentContext.DataTableSegmentProvider (cyclomatic 45) apps/web/modules/data-table/contexts/DataTableSegmentContext.tsx:43— DataTableSegmentContext.DataTableSegmentProvider has cyclomatic complexity 45 (threshold 15). Most of this is not in the body itself: 3 of the 45 points are its own statements and the rest belongs to 9 function literals inside it that branch (lines 253, 131, 225, …). 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.
FormBuilder.FormBuilder (cyclomatic 45) apps/web/modules/event-types/components/tabs/advanced/FormBuilder.tsx:94— FormBuilder.FormBuilder 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 6 function literals inside it that branch (lines 236, 403, 177, …). 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.
getConnectedApps.getConnectedApps (cyclomatic 44) packages/app-store/_utils/getConnectedApps.ts:45— getConnectedApps.getConnectedApps has cyclomatic complexity 44 (threshold 15). Of this number, 16 points are the body's own statements and 28 belong to 13 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.
outOfOfficeCreateOrUpdate.handler.outOfOfficeCreateOrUpdate (cyclomatic 44) packages/trpc/server/routers/viewer/ooo/outOfOfficeCreateOrUpdate.handler.ts:27— outOfOfficeCreateOrUpdate.handler.outOfOfficeCreateOrUpdate has cyclomatic complexity 44 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ToolbarPlugin.ToolbarPlugin (cyclomatic 44) packages/ui/components/editor/plugins/ToolbarPlugin.tsx:243— ToolbarPlugin.ToolbarPlugin 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 18 function items inside it that branch (a function literal at line 323, format, a function literal at line 389, …). 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.
BookingFields.BookingFields (cyclomatic 43) apps/web/modules/bookings/components/BookEventForm/BookingFields.tsx:25— BookingFields.BookingFields has cyclomatic complexity 43 (threshold 15). Most of this is not in the body itself: 2 of the 43 points are its own statements and the rest belongs to 10 function items inside it that branch (a function literal at line 127, getFieldWithDirectPricing, syncPhoneFields, …). 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.
ApiAuthStrategy.authenticate (cyclomatic 42) apps/api/v2/src/modules/auth/strategies/api-auth/api-auth.strategy.ts:55— ApiAuthStrategy.authenticate has cyclomatic complexity 42 (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.
CancelBooking.CancelBooking (cyclomatic 42) apps/web/components/booking/CancelBooking.tsx:118— CancelBooking.CancelBooking has cyclomatic complexity 42 (threshold 15). Of this number, 28 points are the body's own statements and 14 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.
Locations.Locations (cyclomatic 42) apps/web/modules/event-types/components/locations/Locations.tsx:85— Locations.Locations has cyclomatic complexity 42 (threshold 15). Of this number, 18 points are the body's own statements and 24 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.
UserAvailabilityService._getUserAvailability (cyclomatic 42) packages/features/availability/lib/getUserAvailability.ts:361— UserAvailabilityService._getUserAvailability has cyclomatic complexity 42 (threshold 15). Of this number, 41 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
seed-app-store.main (cyclomatic 42) scripts/seed-app-store.ts:94— seed-app-store.main has cyclomatic complexity 42 (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.
AppCard.AppCard (cyclomatic 41) apps/web/modules/apps/components/AppCard.tsx:32— AppCard.AppCard has cyclomatic complexity 41 (threshold 15). Of this number, 29 points are the body's own statements and 12 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.
login-view.Login (cyclomatic 41) apps/web/modules/auth/login-view.tsx:104— login-view.Login has cyclomatic complexity 41 (threshold 15). Of this number, 34 points are the body's own statements and 7 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.
WriteToObjectSettings.WriteToObjectSettings (cyclomatic 41) packages/app-store/_components/crm/WriteToObjectSettings.tsx:22— WriteToObjectSettings.WriteToObjectSettings has cyclomatic complexity 41 (threshold 15). Most of this is not in the body itself: 9 of the 41 points are its own statements and the rest belongs to 13 function items inside it that branch (a function literal at line 147, saveEditing, a function literal at line 371, …). 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.
AvailableSlotsService._getBusyTimesFromLimitsForUsers (cyclomatic 41) REDACTED:379— AvailableSlotsService._getBusyTimesFromLimitsForUsers has cyclomatic complexity 41 (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.
Setup.BTCPaySetupPage (cyclomatic 40) apps/web/components/apps/btcpayserver/Setup.tsx:73— Setup.BTCPaySetupPage has cyclomatic complexity 40 (threshold 15). Of this number, 21 points are the body's own statements and 19 belong to 4 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.
PremiumTextfield.PremiumTextfield (cyclomatic 40) apps/web/components/ui/UsernameAvailability/PremiumTextfield.tsx:55— PremiumTextfield.PremiumTextfield has cyclomatic complexity 40 (threshold 15). Of this number, 26 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.
NavigationItem.NavigationItem (cyclomatic 40) apps/web/modules/shell/navigation/NavigationItem.tsx:74— NavigationItem.NavigationItem has cyclomatic complexity 40 (threshold 15). Of this number, 35 points are the body's own statements and 5 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.
WriteToObjectSettings.WriteToObjectSettings (cyclomatic 40) packages/app-store/salesforce/components/components/WriteToObjectSettings.tsx:22— WriteToObjectSettings.WriteToObjectSettings has cyclomatic complexity 40 (threshold 15). Most of this is not in the body itself: 9 of the 40 points are its own statements and the rest belongs to 13 function items inside it that branch (a function literal at line 165, saveEditing, a function literal at line 389, …). 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.
SalesforceCRMService.getContacts (cyclomatic 40) packages/app-store/salesforce/lib/CrmService.ts:539— SalesforceCRMService.getContacts has cyclomatic complexity 40 (threshold 15). Of this number, 32 points are the body's own statements and 8 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.
BookingsService_2024_08_13.hasRequiredBookingFieldsResponses (cyclomatic 38) apps/api/v2/src/platform/bookings/2024-08-13/services/bookings.service.ts:217— BookingsService_2024_08_13.hasRequiredBookingFieldsResponses has cyclomatic complexity 38 (threshold 15). Of this number, 37 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.
CreateOrEditOutOfOfficeModal.CreateOrEditOutOfOfficeEntryModal (cyclomatic 38) apps/web/modules/settings/outOfOffice/CreateOrEditOutOfOfficeModal.tsx:32— CreateOrEditOutOfOfficeModal.CreateOrEditOutOfOfficeEntryModal has cyclomatic complexity 38 (threshold 15). Of this number, 20 points are the body's own statements and 18 belong to 14 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.
getEventTypeById.getEventTypeById (cyclomatic 38) packages/features/eventtypes/lib/getEventTypeById.ts:38— getEventTypeById.getEventTypeById has cyclomatic complexity 38 (threshold 15). Of this number, 35 points are the body's own statements and 3 belong to 2 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
calcomSignupHandler.handler (cyclomatic 37) apps/web/app/api/auth/signup/handlers/calcomSignupHandler.ts:55— calcomSignupHandler.handler has cyclomatic complexity 37 (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.
OAuthClientDetailsDialog.OAuthClientDetailsDialog (cyclomatic 37) apps/web/modules/settings/oauth/view/OAuthClientDetailsDialog.tsx:44— OAuthClientDetailsDialog.OAuthClientDetailsDialog has cyclomatic complexity 37 (threshold 15). Most of this is not in the body itself: 15 of the 37 points are its own statements and the rest belongs to 8 function items inside it that branch (a function literal at line 143, a function literal at line 211, a function literal at line 101, …). 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.
confirm.handler.confirmHandler (cyclomatic 37) packages/trpc/server/routers/viewer/bookings/confirm.handler.ts:51— confirm.handler.confirmHandler has cyclomatic complexity 37 (threshold 15). Of this number, 36 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
step-view.OnboardingPage (cyclomatic 36) apps/web/modules/apps/installation/[[...step]]/step-view.tsx:103— step-view.OnboardingPage has cyclomatic complexity 36 (threshold 15). Most of this is not in the body itself: 11 of the 36 points are its own statements and the rest belongs to 9 function items inside it that branch (a function literal at line 188, a function literal at line 247, 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.
EventAvailabilityTab.EventTypeSchedule (cyclomatic 36) apps/web/modules/event-types/components/tabs/availability/EventAvailabilityTab.tsx:431— EventAvailabilityTab.EventTypeSchedule has cyclomatic complexity 36 (threshold 15). Of this number, 25 points are the body's own statements and 11 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.
SalesforceGraphQLClient.GetAccountRecordsForRRSkip (cyclomatic 36) packages/app-store/salesforce/lib/graphql/SalesforceGraphQLClient.ts:65— SalesforceGraphQLClient.GetAccountRecordsForRRSkip has cyclomatic complexity 36 (threshold 15). Of this number, 31 points are the body's own statements and 5 belong to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ReassignDialog.ReassignDialog (cyclomatic 35) apps/web/components/dialog/ReassignDialog.tsx:63— ReassignDialog.ReassignDialog has cyclomatic complexity 35 (threshold 15). Of this number, 23 points are the body's own statements and 12 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.
EventLimitsTab.EventLimitsTab (cyclomatic 35) packages/features/eventtypes/components/tabs/limits/EventLimitsTab.tsx:400— EventLimitsTab.EventLimitsTab has cyclomatic complexity 35 (threshold 15). Most of this is not in the body itself: 3 of the 35 points are its own statements and the rest belongs to 16 function items inside it that branch (hasTeamLimits, a function literal at line 781, a function literal at line 626, …). 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.
getEventTypesByViewer.getEventTypesByViewer (cyclomatic 35) packages/features/eventtypes/lib/getEventTypesByViewer.ts:46— getEventTypesByViewer.getEventTypesByViewer has cyclomatic complexity 35 (threshold 15). Most of this is not in the body itself: 13 of the 35 points are its own statements and the rest belongs to 7 function items inside it that branch (a function literal at line 261, mapEventType, filterBySchedulingTypes, …). 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.
FilterSegmentSelect.FilterSegmentSelect (cyclomatic 34) apps/web/modules/data-table/components/segment/FilterSegmentSelect.tsx:40— FilterSegmentSelect.FilterSegmentSelect has cyclomatic complexity 34 (threshold 15). Most of this is not in the body itself: 9 of the 34 points are its own statements and the rest belongs to 7 function literals inside it that branch (lines 174, 88, 193, …). 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.
EventSetupTab.EventSetupTab (cyclomatic 34) apps/web/modules/event-types/components/tabs/setup/EventSetupTab.tsx:66— EventSetupTab.EventSetupTab has cyclomatic complexity 34 (threshold 15). Of this number, 25 points are the body's own statements and 9 belong to 5 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.
TimezoneSelectComponent.TimezoneSelectComponent (cyclomatic 34) packages/features/timezone/components/TimezoneSelectComponent.tsx:22— TimezoneSelectComponent.TimezoneSelectComponent has cyclomatic complexity 34 (threshold 15). Most of this is not in the body itself: 1 of the 34 points is its own statement and the rest belongs to 17 function literals inside it that branch (lines 137, 127, 64, …). 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.
booking-fields.transformBookingFieldsInternalToApi (cyclomatic 33) apps/api/v2/src/platform/event-types/event-types_2024_06_14/transformers/internal-to-api/booking-fields.ts:29— booking-fields.transformBookingFieldsInternalToApi has cyclomatic complexity 33 (threshold 15). Most of this is not in the body itself: 1 of the 33 points is its own statement and the rest belongs to one function literal inside it that branches (line 32). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
getServerSideProps.getServerSideProps (cyclomatic 33) apps/web/lib/signup/getServerSideProps.tsx:23— getServerSideProps.getServerSideProps has cyclomatic complexity 33 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
authorize-view.Authorize (cyclomatic 33) apps/web/modules/auth/oauth2/authorize-view.tsx:19— authorize-view.Authorize has cyclomatic complexity 33 (threshold 15). Of this number, 17 points are the body's own statements and 16 belong to 7 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.
EventMeta.EventMeta (cyclomatic 33) apps/web/modules/bookings/components/EventMeta.tsx:46— EventMeta.EventMeta has cyclomatic complexity 33 (threshold 15). Of this number, 29 points are the body's own statements and 4 belong to 2 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.
server.makeWhereClause (cyclomatic 33) packages/features/data-table/lib/server.ts:29— server.makeWhereClause has cyclomatic complexity 33 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
AvailabilitySettings.AvailabilitySettings (cyclomatic 33) packages/platform/atoms/availability/AvailabilitySettings.tsx:297— AvailabilitySettings.AvailabilitySettings has cyclomatic complexity 33 (threshold 15). Of this number, 20 points are the body's own statements and 13 belong to 8 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.
DateRangeFilter.DateRangeFilter (cyclomatic 32) apps/web/modules/data-table/components/filters/DateRangeFilter.tsx:44— DateRangeFilter.DateRangeFilter has cyclomatic complexity 32 (threshold 15). Of this number, 22 points are the body's own statements and 10 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.
FormBuilder.FieldEditDialog (cyclomatic 32) apps/web/modules/event-types/components/tabs/advanced/FormBuilder.tsx:596— FormBuilder.FieldEditDialog has cyclomatic complexity 32 (threshold 15). Most of this is not in the body itself: 4 of the 32 points are its own statements and the rest belongs to 8 function literals inside it that branch (lines 674, 747, 768, …). 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.
profile-view.ProfileView (cyclomatic 32) apps/web/modules/settings/my-account/profile-view.tsx:68— profile-view.ProfileView has cyclomatic complexity 32 (threshold 15). Of this number, 20 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.
BaseScheduledEmail.BaseScheduledEmail (cyclomatic 32) packages/emails/src/templates/BaseScheduledEmail.tsx:18— BaseScheduledEmail.BaseScheduledEmail has cyclomatic complexity 32 (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.
handlePayment.handlePayment (cyclomatic 32) packages/features/bookings/lib/handlePayment.ts:16— handlePayment.handlePayment has cyclomatic complexity 32 (threshold 15). Most of this is not in the body itself: 13 of the 32 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 85, 152). 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.
BaseCalendarService.getAvailability (cyclomatic 32) packages/lib/CalendarService.ts:655— BaseCalendarService.getAvailability has cyclomatic complexity 32 (threshold 15). Most of this is not in the body itself: 2 of the 32 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 681, 670). 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.
AddVariablesDropdown.AddVariablesDropdown (cyclomatic 32) packages/ui/components/editor/plugins/AddVariablesDropdown.tsx:19— AddVariablesDropdown.AddVariablesDropdown has cyclomatic complexity 32 (threshold 15). Most of this is not in the body itself: 5 of the 32 points are its own statements and the rest belongs to 8 function items inside it that branch (handleKeyDown, a function literal at line 28, handleOnOpen, …). 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.
BookEventForm.BookEventForm (cyclomatic 31) apps/web/modules/bookings/components/BookEventForm/BookEventForm.tsx:46— BookEventForm.BookEventForm has cyclomatic complexity 31 (threshold 15). Of this number, 26 points are the body's own statements and 5 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.
UserForm.UserForm (cyclomatic 31) apps/web/modules/users/components/UserForm.tsx:64— UserForm.UserForm has cyclomatic complexity 31 (threshold 15). Of this number, 16 points are the body's own statements and 15 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.
general-view.GeneralView (cyclomatic 30) apps/web/modules/settings/my-account/general-view.tsx:51— general-view.GeneralView has cyclomatic complexity 30 (threshold 15). Most of this is not in the body itself: 12 of the 30 points are its own statements and the rest belongs to 11 function literals inside it that branch (lines 93, 225, 63, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
getBookingResponsesSchema.preprocess (cyclomatic 30) packages/features/bookings/lib/getBookingResponsesSchema.ts:379— getBookingResponsesSchema.preprocess has cyclomatic complexity 30 (threshold 15). Most of this is not in the body itself: 2 of the 30 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 434, 401, 396). 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.
handleDeleteCredential.handleDeleteCredential (cyclomatic 30) packages/features/credentials/handleDeleteCredential.ts:42— handleDeleteCredential.handleDeleteCredential has cyclomatic complexity 30 (threshold 15). Of this number, 23 points are the body's own statements and 7 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.
selfHostedHandler.handler (cyclomatic 29) apps/web/app/api/auth/signup/handlers/selfHostedHandler.ts:26— selfHostedHandler.handler 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.
Event.Event (cyclomatic 29) apps/web/modules/calendars/weeklyview/components/event/Event.tsx:60— Event.Event has cyclomatic complexity 29 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
TextField.InputField (cyclomatic 29) packages/ui/components/form/inputs/TextField.tsx:103— TextField.InputField has cyclomatic complexity 29 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
booking-fields.getBaseProperties (cyclomatic 28) apps/api/v2/src/platform/event-types/event-types_2024_06_14/transformers/api-to-internal/booking-fields.ts:53— booking-fields.getBaseProperties has cyclomatic complexity 28 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
bookingActions.isActionDisabled (cyclomatic 28) apps/web/components/booking/actions/bookingActions.ts:229— bookingActions.isActionDisabled has cyclomatic complexity 28 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
DataTable.DataTableBody (cyclomatic 28) apps/web/modules/data-table/components/DataTable.tsx:297— DataTable.DataTableBody has cyclomatic complexity 28 (threshold 15). Most of this is not in the body itself: 6 of the 28 points are its own statements and the rest belongs to 5 function literals inside it that branch (lines 366, 319, 401, …). 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.
SaveFilterSegmentButton.SaveFilterSegmentButton (cyclomatic 28) apps/web/modules/data-table/components/segment/SaveFilterSegmentButton.tsx:28— SaveFilterSegmentButton.SaveFilterSegmentButton has cyclomatic complexity 28 (threshold 15). Most of this is not in the body itself: 11 of the 28 points are its own statements and the rest belongs to 4 function items inside it that branch (onSubmit, a function literal at line 74, handleOpenChange, …). 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.
EventTypeLayout.EventTypeSingleLayout (cyclomatic 28) apps/web/modules/event-types/components/EventTypeLayout.tsx:52— EventTypeLayout.EventTypeSingleLayout 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.
useSchedule.useSchedule (cyclomatic 28) apps/web/modules/schedules/hooks/useSchedule.ts:51— useSchedule.useSchedule has cyclomatic complexity 28 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
EventTypeAppSettingsInterface.EventTypeAppSettingsInterface (cyclomatic 28) packages/app-store/stripepayment/components/EventTypeAppSettingsInterface.tsx:24— EventTypeAppSettingsInterface.EventTypeAppSettingsInterface has cyclomatic complexity 28 (threshold 15). Of this number, 19 points are the body's own statements and 9 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.
bookingScenario.mockCalendar (cyclomatic 28) REDACTED:1662— bookingScenario.mockCalendar has cyclomatic complexity 28 (threshold 15). Most of this is not in the body itself: 2 of the 28 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 1720, 1791, 1838, …). 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.
Setup.HitPaySetupPage (cyclomatic 27) apps/web/components/apps/hitpay/Setup.tsx:71— Setup.HitPaySetupPage has cyclomatic complexity 27 (threshold 15). Of this number, 15 points are the body's own statements and 12 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.
Members.EventMembers (cyclomatic 27) apps/web/modules/bookings/components/event-meta/Members.tsx:24— Members.EventMembers has cyclomatic complexity 27 (threshold 15). Of this number, 22 points are the body's own statements and 5 belong to one function literal inside it that branches. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
build.generateFiles (cyclomatic 27) packages/app-store-cli/src/build.ts:45— build.generateFiles has cyclomatic complexity 27 (threshold 15). Most of this is not in the body itself: 4 of the 27 points are its own statements and the rest belongs to 7 function items inside it that branch (forEachAppDir, a function literal at line 55, a function literal at line 175, …). 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.
ICSFeedCalendarService.getAvailability (cyclomatic 27) packages/app-store/ics-feedcalendar/lib/CalendarService.ts:139— ICSFeedCalendarService.getAvailability has cyclomatic complexity 27 (threshold 15). Most of this is not in the body itself: 2 of the 27 points are its own statements and the rest belongs to one function literal inside it that branches (line 152). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
next-auth-options.authorizeCredentials (cyclomatic 27) packages/features/auth/lib/next-auth-options.ts:151— next-auth-options.authorizeCredentials has cyclomatic complexity 27 (threshold 15). Of this number, 21 points are the body's own statements and 6 belong to one function item inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
EventManager.create (cyclomatic 27) packages/features/bookings/lib/EventManager.ts:287— EventManager.create has cyclomatic complexity 27 (threshold 15). Of this number, 17 points are the body's own statements and 10 belong to one function literal inside it that branches. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
ScheduleComponent.LazySelect (cyclomatic 27) packages/features/schedules/components/ScheduleComponent.tsx:423— ScheduleComponent.LazySelect has cyclomatic complexity 27 (threshold 15). Most of this is not in the body itself: 5 of the 27 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 451, 483, 537). 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.
AvailableSlotsService.calculateHostsAndAvailabilities (cyclomatic 27) REDACTED:678— AvailableSlotsService.calculateHostsAndAvailabilities has cyclomatic complexity 27 (threshold 15). Of this number, 24 points are the body's own statements and 3 belong to 2 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.
EditLocationDialog.EditLocationDialog (cyclomatic 26) apps/web/components/dialog/EditLocationDialog.tsx:82— EditLocationDialog.EditLocationDialog has cyclomatic complexity 26 (threshold 15). 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 literals inside it that branch (lines 115, 186, 97, …). 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.
HostLocations.HostLocationRow (cyclomatic 26) apps/web/modules/event-types/components/locations/HostLocations.tsx:256— HostLocations.HostLocationRow has cyclomatic complexity 26 (threshold 15). Of this number, 13 points are the body's own statements and 13 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.
personal-settings-view.PersonalSettingsView (cyclomatic 26) apps/web/modules/onboarding/personal/settings/personal-settings-view.tsx:29— personal-settings-view.PersonalSettingsView has cyclomatic complexity 26 (threshold 15). Of this number, 19 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.
OutOfOfficeEntriesList.OutOfOfficeEntriesListContent (cyclomatic 26) apps/web/modules/settings/outOfOffice/OutOfOfficeEntriesList.tsx:96— OutOfOfficeEntriesList.OutOfOfficeEntriesListContent has cyclomatic complexity 26 (threshold 15). Most of this is not in the body itself: 2 of the 26 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 222, 172, 236, …). 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.
WebhookListItem.WebhookListItem (cyclomatic 26) apps/web/modules/webhooks/components/WebhookListItem.tsx:45— WebhookListItem.WebhookListItem has cyclomatic complexity 26 (threshold 15). Of this number, 24 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
BusyTimesService._getBusyTimes (cyclomatic 26) packages/features/busyTimes/services/getBusyTimes.ts:29— BusyTimesService._getBusyTimes has cyclomatic complexity 26 (threshold 15). Most of this is not in the body itself: 12 of the 26 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 132, 264). 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.
requestReschedule.handler.requestRescheduleHandler (cyclomatic 26) packages/trpc/server/routers/viewer/bookings/requestReschedule.handler.ts:47— requestReschedule.handler.requestRescheduleHandler has cyclomatic complexity 26 (threshold 15). Of this number, 19 points are the body's own statements and 7 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.
FileUploader.FileUploader (cyclomatic 26) packages/ui/components/file-uploader/FileUploader.tsx:72— FileUploader.FileUploader has cyclomatic complexity 26 (threshold 15). Most of this is not in the body itself: 9 of the 26 points are its own statements and the rest belongs to 4 function items inside it that branch (a function literal at line 130, validateFile, getFileIcon, …). 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.
EventWebhooksTab.EventWebhooksTab (cyclomatic 25) apps/web/modules/event-types/components/tabs/webhooks/EventWebhooksTab.tsx:22— EventWebhooksTab.EventWebhooksTab has cyclomatic complexity 25 (threshold 15). Of this number, 19 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.
password-view.PasswordView (cyclomatic 25) apps/web/modules/settings/security/password-view.tsx:51— password-view.PasswordView has cyclomatic complexity 25 (threshold 15). Of this number, 16 points are the body's own statements and 9 belong to 5 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.
GoogleCalendarService.createEvent (cyclomatic 25) packages/app-store/googlecalendar/lib/CalendarService.ts:180— GoogleCalendarService.createEvent has cyclomatic complexity 25 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
SalesforceCRMService.createContacts (cyclomatic 25) packages/app-store/salesforce/lib/CrmService.ts:754— SalesforceCRMService.createContacts has cyclomatic complexity 25 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
bookingSuccessRedirect.getBookingRedirectExtraParams (cyclomatic 25) packages/features/bookings/lib/bookingSuccessRedirect.ts:77— bookingSuccessRedirect.getBookingRedirectExtraParams has cyclomatic complexity 25 (threshold 15). Most of this is not in the body itself: 4 of the 25 points are its own statements and the rest belongs to 6 function items inside it that branch (extractAttendeesAndGuests, extractResponseDetails, 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.
eventNaming.getEventName (cyclomatic 25) packages/features/eventtypes/lib/eventNaming.ts:31— eventNaming.getEventName has cyclomatic complexity 25 (threshold 15). Of this number, 15 points are the body's own statements and 10 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.
slots.buildSlotsWithDateRanges (cyclomatic 25) packages/features/schedules/lib/slots.ts:71— slots.buildSlotsWithDateRanges has cyclomatic complexity 25 (threshold 15). Most of this is not in the body itself: 5 of the 25 points are its own statements and the rest belongs to one function literal inside it that branches (line 127). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
BookingLimitsCountValidator.validate (cyclomatic 25) packages/platform/types/event-types/event-types_2024_06_14/inputs/booking-limits-count.input.ts:65— BookingLimitsCountValidator.validate 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.
BookingLimitsDurationValidator.validate (cyclomatic 25) packages/platform/types/event-types/event-types_2024_06_14/inputs/booking-limits-duration.input.ts:56— BookingLimitsDurationValidator.validate 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.
duplicate.handler.duplicateHandler (cyclomatic 25) packages/trpc/server/routers/viewer/eventTypes/heavy/duplicate.handler.ts:20— duplicate.handler.duplicateHandler has cyclomatic complexity 25 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
TravelScheduleModal.TravelScheduleModal (cyclomatic 24) apps/web/components/settings/TravelScheduleModal.tsx:31— TravelScheduleModal.TravelScheduleModal has cyclomatic complexity 24 (threshold 15). Most of this is not in the body itself: 6 of the 24 points are its own statements and the rest belongs to 4 function items inside it that branch (isOverlapping, a function literal at line 153, createNewSchedule, …). 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.
AvailableTimeSlots.AvailableTimeSlots (cyclomatic 24) apps/web/modules/bookings/components/AvailableTimeSlots.tsx:67— AvailableTimeSlots.AvailableTimeSlots has cyclomatic complexity 24 (threshold 15). Of this number, 13 points are the body's own statements and 11 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.
BookingDetailsSheet.BookingDetailsSheetInner (cyclomatic 24) apps/web/modules/bookings/components/BookingDetailsSheet.tsx:141— BookingDetailsSheet.BookingDetailsSheetInner has cyclomatic complexity 24 (threshold 15). Of this number, 13 points are the body's own statements and 11 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.
EventManager.reschedule (cyclomatic 24) packages/features/bookings/lib/EventManager.ts:615— EventManager.reschedule has cyclomatic complexity 24 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
EventManager.createAllCalendarEvents (cyclomatic 24) packages/features/bookings/lib/EventManager.ts:873— EventManager.createAllCalendarEvents has cyclomatic complexity 24 (threshold 15). Of this number, 16 points are the body's own statements and 8 belong to 4 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ScheduleComponent.CopyTimes (cyclomatic 24) packages/features/schedules/components/ScheduleComponent.tsx:661— ScheduleComponent.CopyTimes has cyclomatic complexity 24 (threshold 15). Most of this is not in the body itself: 1 of the 24 points is its own statement and the rest belongs to 8 function items inside it that branch (handleKeyDown, a function literal at line 742, a function literal at line 718, …). 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.
ServerTrans.parseArrayComponents (cyclomatic 24) packages/lib/components/ServerTrans.tsx:69— ServerTrans.parseArrayComponents has cyclomatic complexity 24 (threshold 15). Most of this is not in the body itself: 2 of the 24 points are its own statements and the rest belongs to 2 function items inside it that branch (parseContent, getTextBetweenTags). 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.
useEventTypeForm.useEventTypeForm.handleSubmit (cyclomatic 24) packages/platform/atoms/event-types/hooks/useEventTypeForm.ts:287— useEventTypeForm.useEventTypeForm.handleSubmit has cyclomatic complexity 24 (threshold 15). Of this number, 23 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.
create.handler.createHandler (cyclomatic 24) packages/trpc/server/routers/viewer/eventTypes/heavy/create.handler.ts:45— create.handler.createHandler has cyclomatic complexity 24 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
seed.main (cyclomatic 24) REDACTED:634— seed.main has cyclomatic complexity 24 (threshold 15). Of this number, 23 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.
RolesGuard.checkUserRoleAccess (cyclomatic 23) apps/api/v2/src/modules/auth/guards/roles/roles.guard.ts:53— RolesGuard.checkUserRoleAccess 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.
PaymentPage.PaymentPage (cyclomatic 23) apps/web/app/(use-page-wrapper)/payment/[uid]/PaymentPage.tsx:63— PaymentPage.PaymentPage has cyclomatic complexity 23 (threshold 15). Of this number, 20 points are the body's own statements and 3 belong to 2 function literals inside it that branch. To reduce it, 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.
notification-sound-handler.NotificationSoundHandler (cyclomatic 23) apps/web/components/notification-sound-handler.tsx:5— notification-sound-handler.NotificationSoundHandler has cyclomatic complexity 23 (threshold 15). Most of this is not in the body itself: 1 of the 23 points is its own statement and the rest belongs to 8 function items inside it that branch (playSound, initializeAudioSystem, 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.
getServerSideProps.getServerSideProps (cyclomatic 23) apps/web/lib/video/[uid]/getServerSideProps.ts:121— getServerSideProps.getServerSideProps has cyclomatic complexity 23 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
EventAppsTab.EventAppsTab (cyclomatic 23) apps/web/modules/event-types/components/tabs/apps/EventAppsTab.tsx:19— EventAppsTab.EventAppsTab has cyclomatic complexity 23 (threshold 15). Of this number, 18 points are the body's own statements and 5 belong to 3 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.
appearance-view.AppearanceView (cyclomatic 23) apps/web/modules/settings/my-account/appearance-view.tsx:51— appearance-view.AppearanceView has cyclomatic complexity 23 (threshold 15). Of this number, 12 points are the body's own statements and 11 belong to 9 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.
useAddAppMutation.useAddAppMutation (cyclomatic 23) packages/app-store/_utils/useAddAppMutation.ts:28— useAddAppMutation.useAddAppMutation has cyclomatic complexity 23 (threshold 15). Most of this is not in the body itself: 1 of the 23 points is its own statement and the rest belongs to one function literal inside it that branches (line 46). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
CalendarEventBuilder.fromBooking (cyclomatic 23) packages/features/CalendarEventBuilder.ts:97— CalendarEventBuilder.fromBooking has cyclomatic complexity 23 (threshold 15). Of this number, 18 points are the body's own statements and 5 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.
getAllCredentials.getAllCredentialsIncludeServiceAccountKey (cyclomatic 23) packages/features/bookings/lib/getAllCredentialsForUsersOnEvent/getAllCredentials.ts:22— getAllCredentials.getAllCredentialsIncludeServiceAccountKey has cyclomatic complexity 23 (threshold 15). Of this number, 17 points are the body's own statements and 6 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.
BaseCalProvider.BaseCalProvider (cyclomatic 23) packages/platform/atoms/cal-provider/BaseCalProvider.tsx:54— BaseCalProvider.BaseCalProvider has cyclomatic complexity 23 (threshold 15). Of this number, 12 points are the body's own statements and 11 belong to 4 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.
EventTypePlatformWrapper.EventType (cyclomatic 23) packages/platform/atoms/event-types/wrappers/EventTypePlatformWrapper.tsx:74— EventTypePlatformWrapper.EventType has cyclomatic complexity 23 (threshold 15). Most of this is not in the body itself: 9 of the 23 points are its own statements and the rest belongs to 9 function items inside it that branch (onDelete, a function literal at line 124, a function literal at line 144, …). 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.
get.handler.getBookings (cyclomatic 23) packages/trpc/server/routers/viewer/bookings/get.handler.ts:93— get.handler.getBookings has cyclomatic complexity 23 (threshold 15). Of this number, 15 points are the body's own statements and 8 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.
ToolbarPlugin.FloatingLinkEditor (cyclomatic 23) packages/ui/components/editor/plugins/ToolbarPlugin.tsx:85— ToolbarPlugin.FloatingLinkEditor 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 3 function literals inside it that branch (lines 95, 190, 174). 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.
SettingsLayoutAppDirClient.useTabs (cyclomatic 22) apps/web/app/(use-page-wrapper)/settings/(settings-layout)/SettingsLayoutAppDirClient.tsx:270— SettingsLayoutAppDirClient.useTabs has cyclomatic complexity 22 (threshold 15). Most of this is not in the body itself: 1 of the 22 points is its own statement and the rest belongs to 4 function literals inside it that branch (lines 285, 369, 295, …). 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.
BookingReportDetailsModal.BookingReportDetailsModal (cyclomatic 22) apps/web/modules/blocklist/components/BookingReportDetailsModal.tsx:30— BookingReportDetailsModal.BookingReportDetailsModal has cyclomatic complexity 22 (threshold 15). Of this number, 18 points are the body's own statements and 4 belong to 4 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.
event-types-listing-view.Item (cyclomatic 22) apps/web/modules/event-types/views/event-types-listing-view.tsx:170— event-types-listing-view.Item has cyclomatic complexity 22 (threshold 15). Of this number, 16 points are the body's own statements and 6 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.
Cal.getNextActionForModal (cyclomatic 22) REDACTED:573— Cal.getNextActionForModal has cyclomatic complexity 22 (threshold 15). Most of this is not in the body itself: 9 of the 22 points are its own statements and the rest belongs to 3 function items inside it that branch (getActionToTake, a function literal at line 690, isSameEmbedConfig). 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.
useBookerLayout.useBookerLayout (cyclomatic 22) packages/features/bookings/Booker/hooks/useBookerLayout.ts:22— useBookerLayout.useBookerLayout has cyclomatic complexity 22 (threshold 15). Of this number, 12 points are the body's own statements and 10 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.
createBooking.buildNewBookingData (cyclomatic 22) packages/features/bookings/lib/handleNewBooking/createBooking.ts:168— createBooking.buildNewBookingData has cyclomatic complexity 22 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
ensureAvailableUsers._ensureAvailableUsers (cyclomatic 22) packages/features/bookings/lib/handleNewBooking/ensureAvailableUsers.ts:57— ensureAvailableUsers._ensureAvailableUsers has cyclomatic complexity 22 (threshold 15). Of this number, 17 points are the body's own statements and 5 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.
DateOverrideInputDialog.DateOverrideForm (cyclomatic 22) packages/features/schedules/components/DateOverrideInputDialog.tsx:22— DateOverrideInputDialog.DateOverrideForm has cyclomatic complexity 22 (threshold 15). Of this number, 14 points are the body's own statements and 8 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.
createCRMEvent.createCRMEvent (cyclomatic 22) packages/features/tasker/tasks/crm/createCRMEvent.ts:41— createCRMEvent.createCRMEvent has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
InputBookingFieldValidator_2024_06_14.validate (cyclomatic 22) REDACTED:936— InputBookingFieldValidator_2024_06_14.validate has cyclomatic complexity 22 (threshold 15). Of this number, 21 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
seed.createOrganizationAndAddMembersAndTeams (cyclomatic 22) REDACTED:113— seed.createOrganizationAndAddMembersAndTeams has cyclomatic complexity 22 (threshold 15). Of this number, 15 points are the body's own statements and 7 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.
SlotsService_2024_09_04.reserveSlot (cyclomatic 21) apps/api/v2/src/modules/slots/slots-2024-09-04/services/slots.service.ts:95— SlotsService_2024_09_04.reserveSlot has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
route.handler (cyclomatic 21) apps/web/app/api/auth/two-factor/totp/disable/route.ts:18— route.handler has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
getServerSideProps.getServerSideProps (cyclomatic 21) apps/web/lib/reschedule/[uid]/getServerSideProps.ts:24— getServerSideProps.getServerSideProps has cyclomatic complexity 21 (threshold 15). Of this number, 20 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body: 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.
BookingHistory.BookingLogsTimeline (cyclomatic 21) apps/web/modules/booking-audit/components/BookingHistory.tsx:237— BookingHistory.BookingLogsTimeline has cyclomatic complexity 21 (threshold 15). Most of this is not in the body itself: 2 of the 21 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 271, 243). 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.
Duration.EventDuration (cyclomatic 21) apps/web/modules/bookings/components/event-meta/Duration.tsx:40— Duration.EventDuration has cyclomatic complexity 21 (threshold 15). Most of this is not in the body itself: 10 of the 21 points are its own statements and the rest belongs to 6 function items inside it that branch (a function literal at line 71, a function literal at line 78, a function literal at line 120, …). 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.
DisableReschedulingController.DisableReschedulingController (cyclomatic 21) apps/web/modules/event-types/components/tabs/advanced/DisableReschedulingController.tsx:32— DisableReschedulingController.DisableReschedulingController 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 literals inside it that branch (lines 70, 117, 53, …). 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.
Shell.ShellMain (cyclomatic 21) apps/web/modules/shell/Shell.tsx:126— Shell.ShellMain has cyclomatic complexity 21 (threshold 15). Of this number, 20 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, 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.
users-public-view.UserPage (cyclomatic 21) REDACTED:24— users-public-view.UserPage 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.
EventTypeAppSettingsInterface.EventTypeAppSettingsInterface (cyclomatic 21) packages/app-store/btcpayserver/components/EventTypeAppSettingsInterface.tsx:18— EventTypeAppSettingsInterface.EventTypeAppSettingsInterface has cyclomatic complexity 21 (threshold 15). Of this number, 17 points are the body's own statements and 4 belong to 3 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.
SearchDialog.SearchDialog (cyclomatic 21) packages/app-store/giphy/components/SearchDialog.tsx:24— SearchDialog.SearchDialog 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 4 function items inside it that branch (getGiphyByUrl, searchGiphy, handleFormSubmit, …). 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.
webhook.handler (cyclomatic 21) packages/app-store/vital/api/webhook.ts:40— webhook.handler has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
useInitialFormValues.useInitialFormValues (cyclomatic 21) packages/features/bookings/Booker/hooks/useInitialFormValues.ts:55— useInitialFormValues.useInitialFormValues has cyclomatic complexity 21 (threshold 15). Most of this is not in the body itself: 1 of the 21 points is its own statement and the rest belongs to 3 function literals inside it that branch (lines 118, 88, 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.
date-ranges.processWorkingHours (cyclomatic 21) packages/features/schedules/lib/date-ranges.ts:32— date-ranges.processWorkingHours has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
reportBooking.handler.reportBookingHandler (cyclomatic 21) packages/trpc/server/routers/viewer/bookings/reportBooking.handler.ts:24— reportBooking.handler.reportBookingHandler has cyclomatic complexity 21 (threshold 15). Of this number, 20 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, 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.
Select.Select (cyclomatic 21) packages/ui/components/form/select/Select.tsx:14— Select.Select has cyclomatic complexity 21 (threshold 15). Most of this is not in the body itself: 3 of the 21 points are its own statements and the rest belongs to 7 function literals inside it that branch (lines 71, 53, 61, …). 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.
Button.Button (cyclomatic 21) packages/ui/components/button/Button.tsx:221— Button.Button 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.
EventTypesAtomService.getEventTypesAppIntegration (cyclomatic 20) apps/api/v2/src/modules/atoms/services/event-types-atom.service.ts:192— EventTypesAtomService.getEventTypesAppIntegration has cyclomatic complexity 20 (threshold 15). Most of this is not in the body itself: 5 of the 20 points are its own statements and the rest belongs to 7 function literals inside it that branch (lines 247, 203, 215, …). 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.
BlocklistEntryDetailsSheet.BlocklistEntryDetailsSheet (cyclomatic 20) apps/web/modules/blocklist/components/BlocklistEntryDetailsSheet.tsx:32— BlocklistEntryDetailsSheet.BlocklistEntryDetailsSheet has cyclomatic complexity 20 (threshold 15). Of this number, 16 points are the body's own statements and 4 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.
videos-single-view.LogInOverlay (cyclomatic 20) REDACTED:310— videos-single-view.LogInOverlay 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 4 function literals inside it that branch (lines 331, 419, 428, …). 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.
SalesforceCRMService.buildRecordUpdatePayload (cyclomatic 20) packages/app-store/salesforce/lib/CrmService.ts:1365— SalesforceCRMService.buildRecordUpdatePayload has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ManageLink.ManageLink (cyclomatic 20) packages/emails/src/components/ManageLink.tsx:4— ManageLink.ManageLink 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.
cancelAttendeeSeat.cancelAttendeeSeat (cyclomatic 20) packages/features/bookings/lib/handleSeats/cancel/cancelAttendeeSeat.ts:23— cancelAttendeeSeat.cancelAttendeeSeat has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
handleConfirmation.handleConfirmation (cyclomatic 20) packages/features/bookings/lib/handleConfirmation.ts:23— handleConfirmation.handleConfirmation has cyclomatic complexity 20 (threshold 15). Of this number, 19 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, 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.
loadAndValidateUsers._loadAndValidateUsers (cyclomatic 20) packages/features/bookings/lib/handleNewBooking/loadAndValidateUsers.ts:71— loadAndValidateUsers._loadAndValidateUsers has cyclomatic complexity 20 (threshold 15). Of this number, 19 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, 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.
scheduleTrigger.listBookings (cyclomatic 20) packages/features/webhooks/lib/scheduleTrigger.ts:182— scheduleTrigger.listBookings has cyclomatic complexity 20 (threshold 15). Of this number, 17 points are the body's own statements and 3 belong to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
AvailabilitySettingsPlatformWrapper.AvailabilitySettingsPlatformWrapper (cyclomatic 20) packages/platform/atoms/availability/wrappers/AvailabilitySettingsPlatformWrapper.tsx:44— AvailabilitySettingsPlatformWrapper.AvailabilitySettingsPlatformWrapper has cyclomatic complexity 20 (threshold 15). Most of this is not in the body itself: 8 of the 20 points are its own statements and the rest belongs to 7 function items inside it that branch (a function literal at line 153, a function literal at line 164, handleUpdate, …). 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.
useHandleBookEvent.useHandleBookEvent::handleBookEvent (cyclomatic 20) packages/platform/atoms/hooks/bookings/useHandleBookEvent.ts:67— useHandleBookEvent.useHandleBookEvent::handleBookEvent has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ConferencingAppsViewPlatformWrapper.ConferencingAppsViewPlatformWrapper (cyclomatic 20) packages/platform/atoms/connect/conferencing-apps/ConferencingAppsViewPlatformWrapper.tsx:89— ConferencingAppsViewPlatformWrapper.ConferencingAppsViewPlatformWrapper has cyclomatic complexity 20 (threshold 15). 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 (AddConferencingButtonPlatform, showToast, handleRemoveApp, …). 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.
updateClient.handler.updateClientHandler (cyclomatic 20) packages/trpc/server/routers/viewer/oAuth/updateClient.handler.ts:15— updateClient.handler.updateClientHandler 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.
route.postHandler (cyclomatic 19) apps/web/app/api/recorded-daily-video/route.ts:54— route.postHandler has cyclomatic complexity 19 (threshold 15). Of this number, 18 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.
ConnectCalendars.ConnectedCalendars (cyclomatic 19) apps/web/components/getting-started/steps-views/ConnectCalendars.tsx:17— ConnectCalendars.ConnectedCalendars has cyclomatic complexity 19 (threshold 15). Of this number, 17 points are the body's own statements and 2 belong to 2 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.
verify-view.Verify (cyclomatic 19) apps/web/modules/auth/verify-view.tsx:114— verify-view.Verify has cyclomatic complexity 19 (threshold 15). Of this number, 14 points are the body's own statements and 5 belong to 4 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.
CreateBlocklistEntryModal.CreateBlocklistEntryModal (cyclomatic 19) apps/web/modules/blocklist/components/CreateBlocklistEntryModal.tsx:25— CreateBlocklistEntryModal.CreateBlocklistEntryModal has cyclomatic complexity 19 (threshold 15). Of this number, 10 points are the body's own statements and 9 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.
BookerWebWrapper.BookerWebWrapperComponent (cyclomatic 19) apps/web/modules/bookings/components/BookerWebWrapper.tsx:41— BookerWebWrapper.BookerWebWrapperComponent has cyclomatic complexity 19 (threshold 15). Of this number, 12 points are the body's own statements and 7 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.
EventList.EventList (cyclomatic 19) apps/web/modules/calendars/weeklyview/components/event/EventList.tsx:16— EventList.EventList 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 6 function literals inside it that branch (lines 93, 30, 46, …). 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.
DataTableWrapper.DataTableWrapper (cyclomatic 19) apps/web/modules/data-table/components/DataTableWrapper.tsx:47— DataTableWrapper.DataTableWrapper 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.
AssignFeatureSheet.AssignFeatureSheet (cyclomatic 19) apps/web/modules/feature-flags/components/AssignFeatureSheet.tsx:31— AssignFeatureSheet.AssignFeatureSheet has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 7 of the 19 points are its own statements and the rest belongs to 3 function items inside it that branch (a function literal at line 124, a function literal at line 52, handleToggleTeam). 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.
UserDropdown.UserDropdown (cyclomatic 19) apps/web/modules/shell/user-dropdown/UserDropdown.tsx:51— UserDropdown.UserDropdown has cyclomatic complexity 19 (threshold 15). 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, 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.
callback.handler (cyclomatic 19) REDACTED:18— callback.handler 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.
link.handleLinkStep (cyclomatic 19) packages/app-store/intercom/lib/configure/link.ts:16— link.handleLinkStep has cyclomatic complexity 19 (threshold 15). Of this number, 15 points are the body's own statements and 4 belong to one function literal inside it that branches. To reduce it, split the body: 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.
deleteRecordings.getAllRecordingsOlderThan6Months (cyclomatic 19) packages/app-store/dailyvideo/lib/scripts/deleteRecordings.ts:29— deleteRecordings.getAllRecordingsOlderThan6Months 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.
Header.Header (cyclomatic 19) packages/features/bookings/components/Header.tsx:22— Header.Header has cyclomatic complexity 19 (threshold 15). Of this number, 10 points are the body's own statements and 9 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.
EventManager.updateAllCalendarEvents (cyclomatic 19) packages/features/bookings/lib/EventManager.ts:1100— EventManager.updateAllCalendarEvents has cyclomatic complexity 19 (threshold 15). Of this number, 17 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, 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.
determineReschedulePreventionRedirect.determineReschedulePreventionRedirect (cyclomatic 19) packages/features/bookings/lib/reschedule/determineReschedulePreventionRedirect.ts:69— determineReschedulePreventionRedirect.determineReschedulePreventionRedirect 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.
EventTypeRepository.getEventTypeList (cyclomatic 19) packages/features/eventtypes/repositories/eventTypeRepository.ts:1746— EventTypeRepository.getEventTypeList 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.
scheduleTrigger.addSubscription (cyclomatic 19) packages/features/webhooks/lib/scheduleTrigger.ts:30— scheduleTrigger.addSubscription 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.
DateRangePicker.DatePickerWithRange (cyclomatic 19) packages/ui/components/form/date-range-picker/DateRangePicker.tsx:26— DateRangePicker.DatePickerWithRange has cyclomatic complexity 19 (threshold 15). Of this number, 10 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.
InputBookingsService_2024_08_13.transformInputCreateRecurringBooking (cyclomatic 18) apps/api/v2/src/platform/bookings/2024-08-13/services/input.service.ts:422— InputBookingsService_2024_08_13.transformInputCreateRecurringBooking has cyclomatic complexity 18 (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.
getThemeProviderProps.getThemeProviderProps (cyclomatic 18) apps/web/lib/getThemeProviderProps.ts:74— getThemeProviderProps.getThemeProviderProps 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.
Occurences.EventOccurences (cyclomatic 18) apps/web/modules/bookings/components/event-meta/Occurences.tsx:16— Occurences.EventOccurences has cyclomatic complexity 18 (threshold 15). Of this number, 11 points are the body's own statements and 7 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.
DataTable.DataTable (cyclomatic 18) apps/web/modules/data-table/components/DataTable.tsx:55— DataTable.DataTable 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 2 function literals inside it that branch (lines 162, 94). 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.
DataTable.TableHeadLabel (cyclomatic 18) apps/web/modules/data-table/components/DataTable.tsx:446— DataTable.TableHeadLabel has cyclomatic complexity 18 (threshold 15). Of this number, 16 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Embed.EmailEmbed (cyclomatic 18) REDACTED:245— Embed.EmailEmbed has cyclomatic complexity 18 (threshold 15). Of this number, 11 points are the body's own statements and 7 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.
FormBuilder.VariantFields (cyclomatic 18) apps/web/modules/event-types/components/tabs/advanced/FormBuilder.tsx:955— FormBuilder.VariantFields has cyclomatic complexity 18 (threshold 15). Of this number, 10 points are the body's own statements and 8 belong to 2 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.
TeamsFilter.TeamsFilter (cyclomatic 18) apps/web/modules/filters/components/TeamsFilter.tsx:22— TeamsFilter.TeamsFilter 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 (getCheckedOptionsNames, a function literal at line 92, a function literal at line 113). 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.
BookerLayoutSelector.BookerLayoutFields (cyclomatic 18) apps/web/modules/settings/components/BookerLayoutSelector.tsx:115— BookerLayoutSelector.BookerLayoutFields has cyclomatic complexity 18 (threshold 15). Of this number, 12 points are the body's own statements and 6 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.
holidays-view.HolidaysView (cyclomatic 18) apps/web/modules/settings/my-account/holidays-view.tsx:171— holidays-view.HolidaysView has cyclomatic complexity 18 (threshold 15). Of this number, 15 points are the body's own statements and 3 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.
profile-view.ProfileForm (cyclomatic 18) apps/web/modules/settings/my-account/profile-view.tsx:486— profile-view.ProfileForm 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 6 function items inside it that branch (getUpdatedFormValues, a function literal at line 570, a function literal at line 615, …). 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.
videos-single-view.JoinCall (cyclomatic 18) REDACTED:30— videos-single-view.JoinCall 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 literals inside it that branch (lines 65, 130, 147). 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.
getServerSideProps.getServerSideProps (cyclomatic 18) apps/web/server/lib/[user]/getServerSideProps.ts:78— getServerSideProps.getServerSideProps has cyclomatic complexity 18 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
handlePaymentSuccess.handlePaymentSuccess (cyclomatic 18) packages/app-store/_utils/payments/handlePaymentSuccess.ts:29— handlePaymentSuccess.handlePaymentSuccess has cyclomatic complexity 18 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
callback.getHandler (cyclomatic 18) REDACTED:26— callback.getHandler 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.
embed-iframe.main (cyclomatic 18) REDACTED:522— embed-iframe.main 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 4 function literals inside it that branch (lines 570, 559, 593, …). 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.
processPaymentRefund.processPaymentRefund (cyclomatic 18) packages/features/bookings/lib/payment/processPaymentRefund.ts:9— processPaymentRefund.processPaymentRefund has cyclomatic complexity 18 (threshold 15). Of this number, 16 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, 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.
utils.textFilter (cyclomatic 18) packages/features/data-table/lib/utils.ts:18— utils.textFilter has cyclomatic complexity 18 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
useShouldBeDisabledDueToPrefill.useShouldBeDisabledDueToPrefill (cyclomatic 18) packages/features/form-builder/useShouldBeDisabledDueToPrefill.tsx:45— useShouldBeDisabledDueToPrefill.useShouldBeDisabledDueToPrefill has cyclomatic complexity 18 (threshold 15). Of this number, 14 points are the body's own statements and 4 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.
imageUtils.detectContentType (cyclomatic 18) packages/lib/server/imageUtils.ts:46— imageUtils.detectContentType has cyclomatic complexity 18 (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.
getServerErrorFromUnknown.getServerErrorFromUnknown (cyclomatic 18) packages/lib/server/getServerErrorFromUnknown.ts:53— getServerErrorFromUnknown.getServerErrorFromUnknown 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 is NOT this file's highest cyclomatic complexity: getServerErrorFromUnknown.getHttpStatusCode (cyclomatic 34) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded method is counted neither in this dimension's figures nor in its score.
useEventTypeForm.useEventTypeForm.defaultValues (cyclomatic 18) packages/platform/atoms/event-types/hooks/useEventTypeForm.ts:42— useEventTypeForm.useEventTypeForm.defaultValues 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.
expects.expectSuccessfulBookingCreationEmails (cyclomatic 18) packages/testing/src/lib/bookingScenario/expects.ts:454— expects.expectSuccessfulBookingCreationEmails has cyclomatic complexity 18 (threshold 15). Of this number, 12 points are the body's own statements and 6 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.
connectAndJoin.handler.Handler (cyclomatic 18) packages/trpc/server/routers/loggedInViewer/connectAndJoin.handler.ts:27— connectAndJoin.handler.Handler has cyclomatic complexity 18 (threshold 15). Of this number, 17 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, 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.
getEventTypesFromGroup.handler.getEventTypesFromGroup (cyclomatic 18) packages/trpc/server/routers/viewer/eventTypes/getEventTypesFromGroup.handler.ts:26— getEventTypesFromGroup.handler.getEventTypesFromGroup has cyclomatic complexity 18 (threshold 15). Of this number, 17 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, 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.
MultiOptionInput.MultiOptionInput (cyclomatic 18) packages/ui/components/form/inputs/MultiOptionInput.tsx:81— MultiOptionInput.MultiOptionInput has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 3 of the 18 points are its own statements and the rest belongs to 6 function items inside it that branch (a function literal at line 206, a function literal at line 135, handlePasteInOptionAtIndex, …). 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.
InputEventTypesService_2024_06_14.transformInputUpdateEventType (cyclomatic 17) apps/api/v2/src/platform/event-types/event-types_2024_06_14/services/input-event-types.service.ts:209— InputEventTypesService_2024_06_14.transformInputUpdateEventType 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.
bookingActions.getActionLabel (cyclomatic 17) apps/web/components/booking/actions/bookingActions.ts:280— bookingActions.getActionLabel 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.
BookingListItem.Attendee (cyclomatic 17) apps/web/components/booking/BookingListItem.tsx:752— BookingListItem.Attendee has cyclomatic complexity 17 (threshold 15). Of this number, 15 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.
getServerSideProps.getServerSideProps (cyclomatic 17) apps/web/lib/apps/installation/[[...step]]/getServerSideProps.ts:496— getServerSideProps.getServerSideProps has cyclomatic complexity 17 (threshold 15). Of this number, 16 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
ApiKeyDialogForm.ApiKeyDialogForm (cyclomatic 17) apps/web/modules/api-keys/api-keys/components/ApiKeyDialogForm.tsx:21— ApiKeyDialogForm.ApiKeyDialogForm has cyclomatic complexity 17 (threshold 15). Of this number, 12 points are the body's own statements and 5 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.
index.DateValues (cyclomatic 17) apps/web/modules/calendars/weeklyview/components/DateValues/index.tsx:17— index.DateValues 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 3 function items inside it that branch (getTimezoneDisplay, a function literal at line 90, 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.
EventTypeDescription.EventTypeDescription (cyclomatic 17) REDACTED:31— EventTypeDescription.EventTypeDescription 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.
RequiresConfirmationController.RequiresConfirmationController (cyclomatic 17) apps/web/modules/event-types/components/tabs/advanced/RequiresConfirmationController.tsx:42— RequiresConfirmationController.RequiresConfirmationController has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 1 of the 17 points is its own statement and the rest belongs to 4 function literals inside it that branch (lines 86, 129, 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.
EventTypeWebWrapper.EventTypeWeb (cyclomatic 17) apps/web/modules/event-types/components/EventTypeWebWrapper.tsx:105— EventTypeWebWrapper.EventTypeWeb 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 5 function literals inside it that branch (lines 150, 128, 312, …). 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.
FormBuilderField.ComponentForField (cyclomatic 17) REDACTED:242— FormBuilderField.ComponentForField 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.
FieldRulesSettings.FieldRulesSettings (cyclomatic 17) packages/app-store/salesforce/components/components/FieldRulesSettings.tsx:14— FieldRulesSettings.FieldRulesSettings has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 2 of the 17 points are its own statements and the rest belongs to 7 function items inside it that branch (a function literal at line 82, saveEditing, a function literal at line 91, …). 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.
EventTypeAppCardInterface.EventTypeAppCard (cyclomatic 17) packages/app-store/salesforce/components/EventTypeAppCardInterface.tsx:24— EventTypeAppCardInterface.EventTypeAppCard has cyclomatic complexity 17 (threshold 15). Of this number, 13 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.
Office365CalendarService.translateEvent (cyclomatic 17) packages/app-store/office365calendar/lib/CalendarService.ts:485— Office365CalendarService.translateEvent has cyclomatic complexity 17 (threshold 15). Of this number, 15 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
webhook.handler (cyclomatic 17) packages/app-store/btcpayserver/api/webhook.ts:44— webhook.handler 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.
UserAvailabilityService.getTimezoneFromDelegatedCalendars (cyclomatic 17) packages/features/availability/lib/getUserAvailability.ts:232— UserAvailabilityService.getTimezoneFromDelegatedCalendars 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, 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.
CreateEventTypeForm.CreateEventTypeForm (cyclomatic 17) packages/features/eventtypes/components/CreateEventTypeForm.tsx:21— CreateEventTypeForm.CreateEventTypeForm has cyclomatic complexity 17 (threshold 15). Of this number, 15 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
scheduleTrigger.deleteSubscription (cyclomatic 17) packages/features/webhooks/lib/scheduleTrigger.ts:132— scheduleTrigger.deleteSubscription 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.
isPasswordValid.isPasswordValid (cyclomatic 17) packages/lib/auth/isPasswordValid.ts:7— isPasswordValid.isPasswordValid 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.
useEventTypeForm.useEventTypeForm.getDirtyFields::isFieldDirty (cyclomatic 17) packages/platform/atoms/event-types/hooks/useEventTypeForm.ts:223— useEventTypeForm.useEventTypeForm.getDirtyFields::isFieldDirty 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.
zod-utils.isPasswordValid (cyclomatic 17) packages/prisma/zod-utils.ts:46— zod-utils.isPasswordValid 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.
Checkbox.CheckboxField (cyclomatic 17) REDACTED:41— Checkbox.CheckboxField 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.
Card.Card (cyclomatic 17) packages/ui/components/card/Card.tsx:148— Card.Card 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.
VerticalTabItem.VerticalTabItem (cyclomatic 17) packages/ui/components/navigation/tabs/VerticalTabItem.tsx:37— VerticalTabItem.VerticalTabItem has cyclomatic complexity 17 (threshold 15). Of this number, 15 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.
DestinationCalendarsService.updateDestinationCalendars (cyclomatic 16) apps/api/v2/src/modules/destination-calendars/services/destination-calendars.service.ts:15— DestinationCalendarsService.updateDestinationCalendars has cyclomatic complexity 16 (threshold 15). Of this number, 11 points are the body's own statements and 5 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.
AppleCalendarService.saveCalendarCredentials (cyclomatic 16) apps/api/v2/src/platform/calendars/services/apple-calendar.service.ts:62— AppleCalendarService.saveCalendarCredentials has cyclomatic complexity 16 (threshold 15). Of this number, 13 points are the body's own statements and 3 belong to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ShellMainAppDir.ShellMainAppDir (cyclomatic 16) apps/web/app/(use-page-wrapper)/(main-nav)/ShellMainAppDir.tsx:8— ShellMainAppDir.ShellMainAppDir 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.
EnableTwoFactorModal.EnableTwoFactorModal (cyclomatic 16) apps/web/components/settings/EnableTwoFactorModal.tsx:56— EnableTwoFactorModal.EnableTwoFactorModal has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 6 of the 16 points are its own statements and the rest belongs to 3 function items inside it that branch (handleSetup, handleEnable, a function literal at line 161). 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.
useBookingListData.useBookingListData (cyclomatic 16) apps/web/modules/bookings/hooks/useBookingListData.ts:19— useBookingListData.useBookingListData has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 1 of the 16 points is its own statement and the rest belongs to 6 function literals inside it that branch (lines 53, 109, 31, …). 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.
bookings-single-view.RecurringBookings (cyclomatic 16) REDACTED:1219— bookings-single-view.RecurringBookings has cyclomatic complexity 16 (threshold 15). Of this number, 13 points are the body's own statements and 3 belong to 3 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.
DuplicateDialog.DuplicateDialog (cyclomatic 16) apps/web/modules/event-types/components/DuplicateDialog.tsx:37— DuplicateDialog.DuplicateDialog 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 4 function literals inside it that branch (lines 92, 60, 132, …). 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.
onboarding-view.OnboardingView (cyclomatic 16) apps/web/modules/onboarding/getting-started/onboarding-view.tsx:23— onboarding-view.OnboardingView has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 5 of the 16 points are its own statements and the rest belongs to 6 function items inside it that branch (getDirection, a function literal at line 77, a function literal at line 40, …). 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.
EventTypesList.EventTypesList (cyclomatic 16) apps/web/modules/users/components/UserTable/BulkActions/EventTypesList.tsx:29— EventTypesList.EventTypesList has cyclomatic complexity 16 (threshold 15). Of this number, 8 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.
PlatformManagedUsersTable.UserListTableContent (cyclomatic 16) apps/web/modules/users/components/UserTable/PlatformManagedUsersTable.tsx:69— PlatformManagedUsersTable.UserListTableContent 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 4 function items inside it that branch (reducer, a function literal at line 122, a function literal at line 157, …). 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.
UserTableActions.TableActions (cyclomatic 16) apps/web/modules/users/components/UserTable/UserTableActions.tsx:20— UserTableActions.TableActions 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.
AppCard.AppCard (cyclomatic 16) packages/app-store/_components/AppCard.tsx:17— AppCard.AppCard has cyclomatic complexity 16 (threshold 15). 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.
HitPayPaymentService.create (cyclomatic 16) packages/app-store/hitpay/lib/PaymentService.ts:38— HitPayPaymentService.create 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.
HubspotCalendarService.getFieldValue (cyclomatic 16) packages/app-store/hubspot/lib/CrmService.ts:176— HubspotCalendarService.getFieldValue 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.
callback.getHandler (cyclomatic 16) packages/app-store/googlecalendar/api/callback.ts:26— callback.getHandler 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.
utils.keepParentInformedAboutDimensionChanges (cyclomatic 16) packages/embeds/embed-core/src/embed-iframe/lib/utils.ts:63— utils.keepParentInformedAboutDimensionChanges has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 1 of the 16 points is its own statement and the rest belongs to one function literal inside it that branches (line 68). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
AppList.AppList (cyclomatic 16) packages/features/apps/components/AppList.tsx:53— AppList.AppList 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 4 function items inside it that branch (ChildAppCard, a function literal at line 152, a function literal at line 110, …). 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.
handleSeats.handleSeats (cyclomatic 16) packages/features/bookings/lib/handleSeats/handleSeats.ts:13— handleSeats.handleSeats 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.
CalendarSubscriptionService.processEvents (cyclomatic 16) packages/features/calendar-subscription/lib/CalendarSubscriptionService.ts:228— CalendarSubscriptionService.processEvents 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.
ssrfProtection.validateUrlCore (cyclomatic 16) packages/lib/ssrfProtection.ts:108— ssrfProtection.validateUrlCore 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.
AppleConnect.AppleConnect (cyclomatic 16) packages/platform/atoms/connect/apple/AppleConnect.tsx:30— AppleConnect.AppleConnect has cyclomatic complexity 16 (threshold 15). Of this number, 14 points are the body's own statements and 2 belong to 2 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.
toggle.handler.toggleHandler (cyclomatic 16) packages/trpc/server/routers/viewer/apps/toggle.handler.ts:20— toggle.handler.toggleHandler has cyclomatic complexity 16 (threshold 15). Of this number, 10 points are the body's own statements and 6 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.
HintOrErrors.HintsOrErrors (cyclomatic 16) packages/ui/components/form/inputs/HintOrErrors.tsx:13— HintOrErrors.HintsOrErrors has cyclomatic complexity 16 (threshold 15). 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, 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.
RegularBookingService.handler (cognitive 453) packages/features/bookings/lib/service/RegularBookingService.ts:486— RegularBookingService.handler has cognitive complexity 453 (threshold 15). Drivers by points: if/else 106 (220 pts), ternaries 57 (94 pts), boolean chains 91, loops 8 (28 pts), error handling 9 (20 pts) (nesting depth added 182). Of this number, 438 points are the body's own statements and 15 belong to 6 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
next-auth-options.getOptions (cognitive 191) packages/features/auth/lib/next-auth-options.ts:374— next-auth-options.getOptions has cognitive complexity 191 (threshold 15). Drivers by points: if/else 72 (148 pts), boolean chains 25, error handling 3 (9 pts), ternaries 5 (9 pts) (nesting depth added 86). Of this number, 178 points are the body's own statements and 13 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.
AvailableSlotsService._getBusyTimesFromLimitsForUsers (cognitive 153) REDACTED:379— AvailableSlotsService._getBusyTimesFromLimitsForUsers has cognitive complexity 153 (threshold 15). Drivers by points: if/else 24 (107 pts), loops 11 (36 pts), error handling 1 (6 pts), boolean chains 4 (nesting depth added 113). 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.
bookings-single-view.Success (cognitive 139) REDACTED:108— bookings-single-view.Success has cognitive complexity 139 (threshold 15). Drivers by points: boolean chains 92, if/else 20 (24 pts), ternaries 20 (23 pts) (nesting depth added 7). Of this number, 104 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.
update.handler.updateHandler (cognitive 121) packages/trpc/server/routers/viewer/eventTypes/heavy/update.handler.ts:60— update.handler.updateHandler has cognitive complexity 121 (threshold 15). Drivers by points: if/else 54 (75 pts), boolean chains 32, ternaries 8, error handling 2 (3 pts), loops 2 (3 pts) (nesting depth added 23). Of this number, 114 points are the body's own statements and 7 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.
AvailableSlotsService._getAvailableSlots (cognitive 99) REDACTED:897— AvailableSlotsService._getAvailableSlots has cognitive complexity 99 (threshold 15). Drivers by points: if/else 28 (48 pts), boolean chains 27, ternaries 12 (19 pts), error handling 2 (4 pts), loops 1 (nesting depth added 29). Of this number, 71 points are the body's own statements and 28 belong to 9 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.
getBookingResponsesSchema.superRefineField (cognitive 88) packages/features/bookings/lib/getBookingResponsesSchema.ts:88— getBookingResponsesSchema.superRefineField has cognitive complexity 88 (threshold 15). Drivers by points: if/else 31 (67 pts), boolean chains 18, ternaries 3 (nesting depth added 36). Of this number, 85 points are the body's own statements and 3 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.
EventAdvancedTab.EventAdvancedTab (cognitive 80) apps/web/modules/event-types/components/tabs/advanced/EventAdvancedTab.tsx:404— EventAdvancedTab.EventAdvancedTab has cognitive complexity 80 (threshold 15). Drivers by points: boolean chains 51, ternaries 16 (20 pts), if/else 9 (nesting depth added 4). Of this number, 34 points are the body's own statements and 46 belong to 25 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.
handleCancelBooking.handler (cognitive 77) packages/features/bookings/lib/handleCancelBooking.ts:81— handleCancelBooking.handler has cognitive complexity 77 (threshold 15). Drivers by points: if/else 20 (26 pts), boolean chains 24, ternaries 9 (13 pts), error handling 7 (12 pts), loops 2 (nesting depth added 15). Of this number, 73 points are the body's own statements and 4 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.
WriteToObjectSettings.WriteToObjectSettings (cognitive 74) packages/app-store/salesforce/components/components/WriteToObjectSettings.tsx:22— WriteToObjectSettings.WriteToObjectSettings has cognitive complexity 74 (threshold 15). Drivers by points: if/else 14 (33 pts), ternaries 14 (32 pts), boolean chains 9 (nesting depth added 37). Most of this is not in the body itself: 9 of the 74 points are its own statements and the rest belongs to 13 function items inside it that branch (a function literal at line 165, saveEditing, a function literal at line 389, …). 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.
SalesforceGraphQLClient.GetAccountRecordsForRRSkip (cognitive 73) packages/app-store/salesforce/lib/graphql/SalesforceGraphQLClient.ts:65— SalesforceGraphQLClient.GetAccountRecordsForRRSkip has cognitive complexity 73 (threshold 15). Drivers by points: if/else 25 (59 pts), loops 4 (8 pts), boolean chains 4, ternaries 2 (nesting depth added 38). Of this number, 63 points are the body's own statements and 10 belong to one function literal inside it that branches. To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
Booker.BookerComponent (cognitive 72) apps/web/modules/bookings/components/Booker.tsx:55— Booker.BookerComponent has cognitive complexity 72 (threshold 15). Drivers by points: boolean chains 42, if/else 15 (16 pts), ternaries 12 (14 pts) (nesting depth added 3). Of this number, 54 points are the body's own statements and 18 belong to 10 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.
EventManager.createAllCalendarEvents (cognitive 72) packages/features/bookings/lib/EventManager.ts:873— EventManager.createAllCalendarEvents has cognitive complexity 72 (threshold 15). Drivers by points: if/else 25 (66 pts), boolean chains 4, loops 1 (2 pts) (nesting depth added 42). Of this number, 50 points are the body's own statements and 22 belong to 4 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.
updateProfile.handler.updateProfileHandler (cognitive 71) packages/trpc/server/routers/viewer/me/updateProfile.handler.ts:41— updateProfile.handler.updateProfileHandler has cognitive complexity 71 (threshold 15). Drivers by points: if/else 31 (50 pts), boolean chains 19, error handling 1, ternaries 1 (nesting depth added 19). Of this number, 65 points are the body's own statements and 6 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.
calcomSignupHandler.handler (cognitive 70) apps/web/app/api/auth/signup/handlers/calcomSignupHandler.ts:55— calcomSignupHandler.handler has cognitive complexity 70 (threshold 15). Drivers by points: if/else 24 (51 pts), boolean chains 11, error handling 2 (5 pts), ternaries 1 (3 pts) (nesting depth added 32). 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.
BookingActionsDropdown.BookingActionsDropdown (cognitive 70) apps/web/components/booking/actions/BookingActionsDropdown.tsx:63— BookingActionsDropdown.BookingActionsDropdown has cognitive complexity 70 (threshold 15). Drivers by points: ternaries 21 (34 pts), boolean chains 26, if/else 5 (9 pts), error handling 1 (nesting depth added 17). Of this number, 24 points are the body's own statements and 46 belong to 14 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.
handleDeleteCredential.handleDeleteCredential (cognitive 69) packages/features/credentials/handleDeleteCredential.ts:42— handleDeleteCredential.handleDeleteCredential has cognitive complexity 69 (threshold 15). Drivers by points: if/else 16 (33 pts), ternaries 7 (22 pts), loops 3 (9 pts), boolean chains 3, error handling 1 (2 pts) (nesting depth added 39). Of this number, 37 points are the body's own statements and 32 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.
WriteToObjectSettings.WriteToObjectSettings (cognitive 68) packages/app-store/_components/crm/WriteToObjectSettings.tsx:22— WriteToObjectSettings.WriteToObjectSettings has cognitive complexity 68 (threshold 15). Drivers by points: if/else 12 (28 pts), ternaries 11 (28 pts), boolean chains 12 (nesting depth added 33). Most of this is not in the body itself: 9 of the 68 points are its own statements and the rest belongs to 13 function items inside it that branch (a function literal at line 147, saveEditing, a function literal at line 371, …). 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.
selfHostedHandler.handler (cognitive 64) apps/web/app/api/auth/signup/handlers/selfHostedHandler.ts:26— selfHostedHandler.handler has cognitive complexity 64 (threshold 15). Drivers by points: if/else 20 (49 pts), boolean chains 7, error handling 2 (5 pts), ternaries 1 (3 pts) (nesting depth added 34). 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.
BookingsService_2024_08_13.hasRequiredBookingFieldsResponses (cognitive 62) apps/api/v2/src/platform/bookings/2024-08-13/services/bookings.service.ts:217— BookingsService_2024_08_13.hasRequiredBookingFieldsResponses has cognitive complexity 62 (threshold 15). Drivers by points: if/else 14 (48 pts), boolean chains 10, match/switch 1 (3 pts), loops 1 (nesting depth added 36). Of this number, 61 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Embed.EmbedTypeCodeAndPreviewDialogContent (cognitive 59) REDACTED:699— Embed.EmbedTypeCodeAndPreviewDialogContent has cognitive complexity 59 (threshold 15). Drivers by points: ternaries 16 (25 pts), if/else 16 (21 pts), boolean chains 13 (nesting depth added 14). Of this number, 32 points are the body's own statements and 27 belong to 7 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.
event-types-listing-view.InfiniteEventTypeList (cognitive 59) apps/web/modules/event-types/views/event-types-listing-view.tsx:280— event-types-listing-view.InfiniteEventTypeList has cognitive complexity 59 (threshold 15). Drivers by points: boolean chains 21, if/else 16 (20 pts), ternaries 12 (18 pts) (nesting depth added 10). Most of this is not in the body itself: 9 of the 59 points are its own statements and the rest belongs to 13 function items inside it that branch (a function literal at line 540, moveEventType, a function literal at line 481, …). 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.
MultiplePrivateLinksController.MultiplePrivateLinksController (cognitive 56) apps/web/modules/event-types/components/MultiplePrivateLinksController.tsx:24— MultiplePrivateLinksController.MultiplePrivateLinksController has cognitive complexity 56 (threshold 15). Drivers by points: if/else 18 (21 pts), ternaries 12 (19 pts), boolean chains 16 (nesting depth added 10). Most of this is not in the body itself: 8 of the 56 points are its own statements and the rest belongs to 14 function items inside it that branch (a function literal at line 226, a function literal at line 173, updateLinkSettings, …). 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.
build.generateFiles (cognitive 56) packages/app-store-cli/src/build.ts:45— build.generateFiles has cognitive complexity 56 (threshold 15). Drivers by points: if/else 30 (45 pts), ternaries 1 (4 pts), boolean chains 3, error handling 1 (3 pts), loops 1 (nesting depth added 20). Most of this is not in the body itself: 6 of the 56 points are its own statements and the rest belongs to 7 function items inside it that branch (forEachAppDir, a function literal at line 55, a function literal at line 175, …). 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.
SalesforceCRMService.createContacts (cognitive 56) packages/app-store/salesforce/lib/CrmService.ts:754— SalesforceCRMService.createContacts has cognitive complexity 56 (threshold 15). Drivers by points: if/else 19 (44 pts), boolean chains 4, error handling 1 (4 pts), loops 1 (3 pts), ternaries 1 (nesting depth added 30). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
outOfOfficeCreateOrUpdate.handler.outOfOfficeCreateOrUpdate (cognitive 56) packages/trpc/server/routers/viewer/ooo/outOfOfficeCreateOrUpdate.handler.ts:27— outOfOfficeCreateOrUpdate.handler.outOfOfficeCreateOrUpdate has cognitive complexity 56 (threshold 15). Drivers by points: if/else 19 (27 pts), boolean chains 15, ternaries 8 (14 pts) (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ToolbarPlugin.ToolbarPlugin (cognitive 56) packages/ui/components/editor/plugins/ToolbarPlugin.tsx:243— ToolbarPlugin.ToolbarPlugin has cognitive complexity 56 (threshold 15). Drivers by points: if/else 25 (35 pts), ternaries 3 (10 pts), boolean chains 8, error handling 1 (2 pts), match/switch 1 (nesting depth added 18). Most of this is not in the body itself: 8 of the 56 points are its own statements and the rest belongs to 18 function items inside it that branch (a function literal at line 323, formatBulletList, formatNumberedList, …). 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.
WebhookForm.WebhookForm (cognitive 55) apps/web/modules/webhooks/components/WebhookForm.tsx:244— WebhookForm.WebhookForm has cognitive complexity 55 (threshold 15). Drivers by points: boolean chains 26, if/else 13 (17 pts), ternaries 7 (9 pts), loops 1 (2 pts), error handling 1 (nesting depth added 7). Of this number, 25 points are the body's own statements and 30 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.
useBookings.useBookings (cognitive 54) apps/web/modules/bookings/hooks/useBookings.ts:111— useBookings.useBookings has cognitive complexity 54 (threshold 15). Drivers by points: boolean chains 25, if/else 17 (20 pts), ternaries 8 (9 pts) (nesting depth added 4). Most of this is not in the body itself: 5 of the 54 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 138, 311, 288, …). 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.
bookings-single-view.getServerSideProps.getServerSideProps (cognitive 53) apps/web/modules/bookings/views/bookings-single-view.getServerSideProps.tsx:39— bookings-single-view.getServerSideProps.getServerSideProps has cognitive complexity 53 (threshold 15). Drivers by points: if/else 19 (24 pts), boolean chains 20, ternaries 7, loops 1 (2 pts) (nesting depth added 6). Of this number, 41 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.
OAuthClientDetailsDialog.OAuthClientDetailsDialog (cognitive 53) apps/web/modules/settings/oauth/view/OAuthClientDetailsDialog.tsx:44— OAuthClientDetailsDialog.OAuthClientDetailsDialog has cognitive complexity 53 (threshold 15). Drivers by points: ternaries 12 (24 pts), if/else 10 (16 pts), boolean chains 13 (nesting depth added 18). Of this number, 24 points are the body's own statements and 29 belong to 8 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.
getPublicEvent.getPublicEvent (cognitive 52) packages/features/eventtypes/lib/getPublicEvent.ts:284— getPublicEvent.getPublicEvent has cognitive complexity 52 (threshold 15). Drivers by points: boolean chains 19, if/else 13 (18 pts), ternaries 11 (15 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
NavigationItem.NavigationItem (cognitive 51) apps/web/modules/shell/navigation/NavigationItem.tsx:74— NavigationItem.NavigationItem has cognitive complexity 51 (threshold 15). Drivers by points: ternaries 14 (31 pts), boolean chains 16, if/else 3 (4 pts) (nesting depth added 18). Of this number, 38 points are the body's own statements and 13 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.
store.createBookerStore (cognitive 51) packages/features/bookings/Booker/store.ts:441— store.createBookerStore has cognitive complexity 51 (threshold 15). Drivers by points: boolean chains 25, if/else 22 (25 pts), ternaries 1 (nesting depth added 3). None of this is in the body itself: all 51 points belong to 10 function literals inside it that branch (lines 458, 561, 485, …). 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.
AppCreateUpdateForm.AppForm (cognitive 50) packages/app-store-cli/src/components/AppCreateUpdateForm.tsx:14— AppCreateUpdateForm.AppForm has cognitive complexity 50 (threshold 15). Drivers by points: boolean chains 19, if/else 13 (18 pts), ternaries 8 (11 pts), error handling 1 (2 pts) (nesting depth added 9). Of this number, 46 points are the body's own statements and 4 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ApiAuthStrategy.authenticate (cognitive 49) apps/api/v2/src/modules/auth/strategies/api-auth/api-auth.strategy.ts:55— ApiAuthStrategy.authenticate has cognitive complexity 49 (threshold 15). Drivers by points: if/else 13 (28 pts), boolean chains 16, error handling 2 (4 pts), ternaries 1 (nesting depth added 17). 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.
AppPage.AppPage (cognitive 48) apps/web/components/apps/AppPage.tsx:66— AppPage.AppPage has cognitive complexity 48 (threshold 15). Drivers by points: boolean chains 29, if/else 13 (15 pts), ternaries 3, loops 1 (nesting depth added 2). Of this number, 19 points are the body's own statements and 29 belong to 10 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.
UserListTable.UserListTableContent (cognitive 48) apps/web/modules/users/components/UserTable/UserListTable.tsx:171— UserListTable.UserListTableContent has cognitive complexity 48 (threshold 15). Drivers by points: boolean chains 29, if/else 12 (15 pts), match/switch 1 (2 pts), error handling 1, loops 1 (nesting depth added 4). Most of this is not in the body itself: 13 of the 48 points are its own statements and the rest belongs to 12 function items inside it that branch (handleDownload, a function literal at line 527, a function literal at line 585, …). 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.
SalesforceCRMService.getContacts (cognitive 48) packages/app-store/salesforce/lib/CrmService.ts:539— SalesforceCRMService.getContacts has cognitive complexity 48 (threshold 15). Drivers by points: if/else 16 (25 pts), boolean chains 14, ternaries 5 (6 pts), error handling 2 (3 pts) (nesting depth added 11). Of this number, 40 points are the body's own statements and 8 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.
getConnectedApps.getConnectedApps (cognitive 47) packages/app-store/_utils/getConnectedApps.ts:45— getConnectedApps.getConnectedApps has cognitive complexity 47 (threshold 15). Drivers by points: if/else 17 (27 pts), boolean chains 15, ternaries 3 (5 pts) (nesting depth added 12). Of this number, 19 points are the body's own statements and 28 belong to 13 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.
ScheduleComponent.LazySelect (cognitive 47) packages/features/schedules/components/ScheduleComponent.tsx:423— ScheduleComponent.LazySelect has cognitive complexity 47 (threshold 15). Drivers by points: if/else 14 (23 pts), ternaries 4 (15 pts), boolean chains 9 (nesting depth added 20). Most of this is not in the body itself: 2 of the 47 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 451, 483, 537). 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.
BookingFields.BookingFields (cognitive 46) apps/web/modules/bookings/components/BookEventForm/BookingFields.tsx:25— BookingFields.BookingFields has cognitive complexity 46 (threshold 15). Drivers by points: if/else 23 (30 pts), boolean chains 13, ternaries 3 (nesting depth added 7). Most of this is not in the body itself: 1 of the 46 points is its own statement and the rest belongs to 10 function items inside it that branch (a function literal at line 127, getFieldWithDirectPricing, syncPhoneFields, …). 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.
EventManager.reschedule (cognitive 46) packages/features/bookings/lib/EventManager.ts:615— EventManager.reschedule has cognitive complexity 46 (threshold 15). Drivers by points: if/else 16 (32 pts), ternaries 3 (10 pts), boolean chains 4 (nesting depth added 23). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
date-ranges.processWorkingHours (cognitive 46) packages/features/schedules/lib/date-ranges.ts:32— date-ranges.processWorkingHours has cognitive complexity 46 (threshold 15). Drivers by points: if/else 14 (36 pts), loops 3 (6 pts), boolean chains 4 (nesting depth added 25). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
BaseCalendarService.getAvailability (cognitive 45) packages/lib/CalendarService.ts:655— BaseCalendarService.getAvailability has cognitive complexity 45 (threshold 15). Drivers by points: if/else 15 (27 pts), error handling 3 (7 pts), boolean chains 6, ternaries 3, loops 1 (2 pts) (nesting depth added 17). Most of this is not in the body itself: 1 of the 45 points is its own statement and the rest belongs to 2 function literals inside it that branch (lines 681, 670). 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.
BookerPlatformWrapper.BookerPlatformWrapperComponent (cognitive 45) packages/platform/atoms/booker/BookerPlatformWrapper.tsx:50— BookerPlatformWrapper.BookerPlatformWrapperComponent has cognitive complexity 45 (threshold 15). Drivers by points: if/else 16, boolean chains 15, ternaries 13 (14 pts) (nesting depth added 1). Of this number, 17 points are the body's own statements and 28 belong to 13 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.
UserAvailabilityService._getUserAvailability (cognitive 44) packages/features/availability/lib/getUserAvailability.ts:361— UserAvailabilityService._getUserAvailability has cognitive complexity 44 (threshold 15). Drivers by points: if/else 17 (22 pts), boolean chains 16, loops 2 (3 pts), ternaries 2, error handling 1 (nesting depth added 6). Of this number, 42 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, split the body: 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.
BookingListItem.BookingListItem (cognitive 43) apps/web/components/booking/BookingListItem.tsx:130— BookingListItem.BookingListItem has cognitive complexity 43 (threshold 15). Drivers by points: boolean chains 37, ternaries 4 (5 pts), if/else 1 (nesting depth added 1). Of this number, 39 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.
DatePicker.Days (cognitive 43) packages/features/calendars/components/DatePicker.tsx:144— DatePicker.Days has cognitive complexity 43 (threshold 15). Drivers by points: boolean chains 14, if/else 12 (13 pts), ternaries 7 (10 pts), loops 3 (6 pts) (nesting depth added 7). Most of this is not in the body itself: 10 of the 43 points are its own statements and the rest belongs to 5 function items inside it that branch (a function literal at line 251, useHandleInitialDateSelection, isActive, …). 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.
getEventTypeById.getEventTypeById (cognitive 43) packages/features/eventtypes/lib/getEventTypeById.ts:38— getEventTypeById.getEventTypeById has cognitive complexity 43 (threshold 15). Drivers by points: boolean chains 18, if/else 10 (14 pts), ternaries 6 (8 pts), loops 3 (nesting depth added 6). Of this number, 40 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.
useEventTypeForm.useEventTypeForm.getDirtyFields::isFieldDirty (cognitive 43) packages/platform/atoms/event-types/hooks/useEventTypeForm.ts:223— useEventTypeForm.useEventTypeForm.getDirtyFields::isFieldDirty has cognitive complexity 43 (threshold 15). Drivers by points: if/else 11 (33 pts), loops 3 (8 pts), boolean chains 2 (nesting depth added 27). 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.
confirm.handler.confirmHandler (cognitive 43) packages/trpc/server/routers/viewer/bookings/confirm.handler.ts:51— confirm.handler.confirmHandler has cognitive complexity 43 (threshold 15). Drivers by points: if/else 14 (19 pts), boolean chains 13, ternaries 9 (11 pts) (nesting depth added 7). Of this number, 42 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, 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.
cancelAttendeeSeat.cancelAttendeeSeat (cognitive 42) packages/features/bookings/lib/handleSeats/cancel/cancelAttendeeSeat.ts:23— cancelAttendeeSeat.cancelAttendeeSeat has cognitive complexity 42 (threshold 15). Drivers by points: if/else 11 (33 pts), boolean chains 4, error handling 1 (2 pts), loops 1 (2 pts), ternaries 1 (nesting depth added 24). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
getBookingResponsesSchema.preprocess (cognitive 42) packages/features/bookings/lib/getBookingResponsesSchema.ts:379— getBookingResponsesSchema.preprocess has cognitive complexity 42 (threshold 15). Drivers by points: if/else 12 (19 pts), ternaries 5 (10 pts), boolean chains 9, error handling 2 (3 pts), loops 1 (nesting depth added 13). Most of this is not in the body itself: 1 of the 42 points is its own statement and the rest belongs to 3 function literals inside it that branch (lines 434, 401, 396). 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.
handlePayment.handlePayment (cognitive 42) packages/features/bookings/lib/handlePayment.ts:16— handlePayment.handlePayment has cognitive complexity 42 (threshold 15). Drivers by points: if/else 12 (18 pts), boolean chains 11, ternaries 3 (10 pts), match/switch 1 (2 pts), error handling 1 (nesting depth added 14). Most of this is not in the body itself: 13 of the 42 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 85, 152). 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.
ICSFeedCalendarService.getAvailability (cognitive 41) packages/app-store/ics-feedcalendar/lib/CalendarService.ts:139— ICSFeedCalendarService.getAvailability has cognitive complexity 41 (threshold 15). Drivers by points: if/else 13 (25 pts), error handling 2 (6 pts), boolean chains 5, ternaries 3, loops 1 (2 pts) (nesting depth added 17). Most of this is not in the body itself: 1 of the 41 points is its own statement and the rest belongs to one function literal inside it that branches (line 152). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
BusyTimesService._getBusyTimes (cognitive 41) packages/features/busyTimes/services/getBusyTimes.ts:29— BusyTimesService._getBusyTimes has cognitive complexity 41 (threshold 15). Drivers by points: if/else 14 (27 pts), boolean chains 12, ternaries 2 (nesting depth added 13). Of this number, 22 points are the body's own statements and 19 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.
deleteRecordings.getAllRecordingsOlderThan6Months (cognitive 40) packages/app-store/dailyvideo/lib/scripts/deleteRecordings.ts:29— deleteRecordings.getAllRecordingsOlderThan6Months has cognitive complexity 40 (threshold 15). Drivers by points: if/else 13 (31 pts), boolean chains 3, error handling 1 (3 pts), loops 2 (3 pts) (nesting depth added 21). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Setup.BTCPaySetupPage (cognitive 39) apps/web/components/apps/btcpayserver/Setup.tsx:73— Setup.BTCPaySetupPage has cognitive complexity 39 (threshold 15). Drivers by points: boolean chains 18, if/else 10 (12 pts), ternaries 4 (7 pts), error handling 2 (nesting depth added 5). Of this number, 19 points are the body's own statements and 20 belong to 4 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DataTableSegmentContext.DataTableSegmentProvider (cognitive 39) apps/web/modules/data-table/contexts/DataTableSegmentContext.tsx:43— DataTableSegmentContext.DataTableSegmentProvider has cognitive complexity 39 (threshold 15). Drivers by points: if/else 23 (27 pts), boolean chains 10, ternaries 2 (nesting depth added 4). Most of this is not in the body itself: 2 of the 39 points are its own statements and the rest belongs to 9 function literals inside it that branch (lines 225, 131, 101, …). 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.
signup-view.Signup (cognitive 39) apps/web/modules/signup-view.tsx:192— signup-view.Signup has cognitive complexity 39 (threshold 15). Drivers by points: boolean chains 31, if/else 10 (18 pts), ternaries 11 (17 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 (signup-view.Signup::signUp) 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.
webhook.handler (cognitive 39) packages/app-store/vital/api/webhook.ts:40— webhook.handler has cognitive complexity 39 (threshold 15). Drivers by points: if/else 12 (26 pts), error handling 3 (7 pts), boolean chains 4, ternaries 1 (2 pts) (nesting depth added 19). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
step-view.OnboardingPage (cognitive 38) apps/web/modules/apps/installation/[[...step]]/step-view.tsx:103— step-view.OnboardingPage has cognitive complexity 38 (threshold 15). Drivers by points: if/else 13 (19 pts), boolean chains 13, ternaries 4, error handling 1, loops 1 (nesting depth added 6). Most of this is not in the body itself: 7 of the 38 points are its own statements and the rest belongs to 9 function items inside it that branch (a function literal at line 247, a function literal at line 188, 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.
EventSetupTab.EventSetupTab (cognitive 38) apps/web/modules/event-types/components/tabs/setup/EventSetupTab.tsx:66— EventSetupTab.EventSetupTab has cognitive complexity 38 (threshold 15). Drivers by points: boolean chains 14, ternaries 10 (14 pts), if/else 5 (10 pts) (nesting depth added 9). Of this number, 24 points are the body's own statements and 14 belong to 5 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.
Locations.Locations (cognitive 38) apps/web/modules/event-types/components/locations/Locations.tsx:85— Locations.Locations has cognitive complexity 38 (threshold 15). Drivers by points: boolean chains 21, if/else 6 (9 pts), ternaries 5 (8 pts) (nesting depth added 6). Most of this is not in the body itself: 12 of the 38 points are its own statements and the rest belongs to 6 function literals inside it that branch (lines 194, 171, 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.
slots.buildSlotsWithDateRanges (cognitive 38) packages/features/schedules/lib/slots.ts:71— slots.buildSlotsWithDateRanges has cognitive complexity 38 (threshold 15). Drivers by points: if/else 11 (23 pts), boolean chains 7, loops 3 (4 pts), ternaries 2 (4 pts) (nesting depth added 15). Most of this is not in the body itself: 4 of the 38 points are its own statements and the rest belongs to one function literal inside it that branches (line 127). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
TimezoneSelectComponent.TimezoneSelectComponent (cognitive 38) packages/features/timezone/components/TimezoneSelectComponent.tsx:22— TimezoneSelectComponent.TimezoneSelectComponent has cognitive complexity 38 (threshold 15). Drivers by points: boolean chains 18, ternaries 12 (17 pts), if/else 3 (nesting depth added 5). None of this is in the body itself: all 38 points belong to 17 function literals inside it that branch (lines 137, 105, 127, …). 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.
AddVariablesDropdown.AddVariablesDropdown (cognitive 38) packages/ui/components/editor/plugins/AddVariablesDropdown.tsx:19— AddVariablesDropdown.AddVariablesDropdown has cognitive complexity 38 (threshold 15). Drivers by points: if/else 12 (20 pts), ternaries 7 (11 pts), boolean chains 6, match/switch 1 (nesting depth added 12). Most of this is not in the body itself: 6 of the 38 points are its own statements and the rest belongs to 8 function items inside it that branch (a function literal at line 28, handleKeyDown, handleOnOpen, …). 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.
booking-fields.getBaseProperties (cognitive 37) apps/api/v2/src/platform/event-types/event-types_2024_06_14/transformers/api-to-internal/booking-fields.ts:53— booking-fields.getBaseProperties has cognitive complexity 37 (threshold 15). Drivers by points: if/else 16 (20 pts), ternaries 7 (13 pts), boolean chains 4 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
onboarding-invite-browser-view.OnboardingInviteBrowserView (cognitive 37) apps/web/modules/onboarding/components/onboarding-invite-browser-view.tsx:34— onboarding-invite-browser-view.OnboardingInviteBrowserView has cognitive complexity 37 (threshold 15). Drivers by points: boolean chains 25, ternaries 6, if/else 4, loops 2. Of this number, 31 points are the body's own statements and 6 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.
seed-app-store.main (cognitive 37) scripts/seed-app-store.ts:94— seed-app-store.main has cognitive complexity 37 (threshold 15). Drivers by points: if/else 17 (19 pts), boolean chains 16, error handling 1, loops 1 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
AppCard.AppCard (cognitive 36) apps/web/modules/apps/components/AppCard.tsx:32— AppCard.AppCard has cognitive complexity 36 (threshold 15). Drivers by points: boolean chains 23, if/else 7 (8 pts), ternaries 5 (nesting depth added 1). Of this number, 24 points are the body's own statements and 12 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.
GoogleCalendarService.createEvent (cognitive 36) packages/app-store/googlecalendar/lib/CalendarService.ts:180— GoogleCalendarService.createEvent has cognitive complexity 36 (threshold 15). Drivers by points: if/else 13 (23 pts), boolean chains 8, loops 1 (3 pts), error handling 1, ternaries 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
next-auth-options.authorizeCredentials (cognitive 36) packages/features/auth/lib/next-auth-options.ts:151— next-auth-options.authorizeCredentials has cognitive complexity 36 (threshold 15). Drivers by points: if/else 24 (33 pts), boolean chains 3 (nesting depth added 9). Of this number, 30 points are the body's own statements and 6 belong to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
getBusyTimesFromLimits._getBusyTimesFromDurationLimits (cognitive 36) packages/features/busyTimes/lib/getBusyTimesFromLimits.ts:166— getBusyTimesFromLimits._getBusyTimesFromDurationLimits has cognitive complexity 36 (threshold 15). Drivers by points: if/else 8 (28 pts), loops 3 (6 pts), boolean chains 2 (nesting depth added 23). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ServerTrans.parseArrayComponents::parseContent (cognitive 36) packages/lib/components/ServerTrans.tsx:74— ServerTrans.parseArrayComponents::parseContent has cognitive complexity 36 (threshold 15). Drivers by points: if/else 9 (27 pts), boolean chains 5, loops 2 (4 pts) (nesting depth added 20). 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.
PremiumTextfield.PremiumTextfield (cognitive 35) apps/web/components/ui/UsernameAvailability/PremiumTextfield.tsx:55— PremiumTextfield.PremiumTextfield has cognitive complexity 35 (threshold 15). Drivers by points: boolean chains 17, ternaries 10, if/else 7 (8 pts) (nesting depth added 1). Of this number, 22 points are the body's own statements and 13 belong to 8 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.
EventAvailabilityTab.EventTypeSchedule (cognitive 35) apps/web/modules/event-types/components/tabs/availability/EventAvailabilityTab.tsx:431— EventAvailabilityTab.EventTypeSchedule has cognitive complexity 35 (threshold 15). Drivers by points: if/else 12 (15 pts), boolean chains 13, ternaries 6 (7 pts) (nesting depth added 4). Of this number, 22 points are the body's own statements and 13 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, 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.
getBusyTimesFromLimits._getBusyTimesFromBookingLimits (cognitive 35) packages/features/busyTimes/lib/getBusyTimesFromLimits.ts:74— getBusyTimesFromLimits._getBusyTimesFromBookingLimits has cognitive complexity 35 (threshold 15). Drivers by points: if/else 6 (21 pts), loops 3 (6 pts), error handling 1 (4 pts), ternaries 1 (3 pts), boolean chains 1 (nesting depth added 23). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
RolesGuard.checkUserRoleAccess (cognitive 34) apps/api/v2/src/modules/auth/guards/roles/roles.guard.ts:53— RolesGuard.checkUserRoleAccess has cognitive complexity 34 (threshold 15). Drivers by points: if/else 18 (29 pts), boolean chains 5 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
EventLimitsTab.EventLimitsTab (cognitive 34) packages/features/eventtypes/components/tabs/limits/EventLimitsTab.tsx:400— EventLimitsTab.EventLimitsTab has cognitive complexity 34 (threshold 15). Drivers by points: boolean chains 19, if/else 11 (12 pts), ternaries 3 (nesting depth added 1). Most of this is not in the body itself: 2 of the 34 points are its own statements and the rest belongs to 16 function items inside it that branch (hasTeamLimits, a function literal at line 781, a function literal at line 626, …). 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.
ReassignDialog.ReassignDialog (cognitive 33) apps/web/components/dialog/ReassignDialog.tsx:63— ReassignDialog.ReassignDialog has cognitive complexity 33 (threshold 15). Drivers by points: if/else 10 (14 pts), ternaries 10, boolean chains 9 (nesting depth added 4). Of this number, 17 points are the body's own statements and 16 belong to 6 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.
login-view.Login (cognitive 33) apps/web/modules/auth/login-view.tsx:104— login-view.Login has cognitive complexity 33 (threshold 15). Drivers by points: boolean chains 22, if/else 8, ternaries 3. Of this number, 26 points are the body's own statements and 7 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.
FilterSegmentSelect.FilterSegmentSelect (cognitive 33) apps/web/modules/data-table/components/segment/FilterSegmentSelect.tsx:40— FilterSegmentSelect.FilterSegmentSelect has cognitive complexity 33 (threshold 15). Drivers by points: boolean chains 16, if/else 15 (16 pts), ternaries 1 (nesting depth added 1). Most of this is not in the body itself: 7 of the 33 points are its own statements and the rest belongs to 7 function literals inside it that branch (lines 88, 174, 193, …). 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.
appearance-view.AppearanceView (cognitive 33) apps/web/modules/settings/my-account/appearance-view.tsx:51— appearance-view.AppearanceView has cognitive complexity 33 (threshold 15). Drivers by points: if/else 11 (16 pts), boolean chains 10, ternaries 4 (7 pts) (nesting depth added 8). Most of this is not in the body itself: 11 of the 33 points are its own statements and the rest belongs to 9 function literals inside it that branch (lines 268, 142, 220, …). 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.
ToolbarPlugin.FloatingLinkEditor (cognitive 33) packages/ui/components/editor/plugins/ToolbarPlugin.tsx:85— ToolbarPlugin.FloatingLinkEditor has cognitive complexity 33 (threshold 15). Drivers by points: if/else 15 (24 pts), boolean chains 5, loops 1 (3 pts), ternaries 1 (nesting depth added 11). Most of this is not in the body itself: 1 of the 33 points is its own statement and the rest belongs to 3 function literals inside it that branch (lines 95, 190, 174). 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.
seed.createOrganizationAndAddMembersAndTeams (cognitive 33) REDACTED:113— seed.createOrganizationAndAddMembersAndTeams has cognitive complexity 33 (threshold 15). Drivers by points: if/else 5 (13 pts), loops 8 (10 pts), boolean chains 5, ternaries 2 (3 pts), error handling 1 (2 pts) (nesting depth added 12). Of this number, 19 points are the body's own statements and 14 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.
getServerSideProps.getServerSideProps (cognitive 32) apps/web/lib/signup/getServerSideProps.tsx:23— getServerSideProps.getServerSideProps has cognitive complexity 32 (threshold 15). Drivers by points: boolean chains 12, ternaries 8 (11 pts), if/else 8 (9 pts) (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.
BookEventForm.BookEventForm (cognitive 32) apps/web/modules/bookings/components/BookEventForm/BookEventForm.tsx:46— BookEventForm.BookEventForm has cognitive complexity 32 (threshold 15). Drivers by points: boolean chains 14, ternaries 7 (12 pts), if/else 6 (nesting depth added 5). Of this number, 28 points are the body's own statements and 4 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
FormBuilder.FormBuilder (cognitive 32) apps/web/modules/event-types/components/tabs/advanced/FormBuilder.tsx:94— FormBuilder.FormBuilder has cognitive complexity 32 (threshold 15). Drivers by points: boolean chains 20, ternaries 5 (7 pts), if/else 5 (nesting depth added 2). Most of this is not in the body itself: 8 of the 32 points are its own statements and the rest belongs to 6 function literals inside it that branch (lines 236, 279, 330, …). 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.
FormBuilder.FieldEditDialog (cognitive 32) apps/web/modules/event-types/components/tabs/advanced/FormBuilder.tsx:596— FormBuilder.FieldEditDialog has cognitive complexity 32 (threshold 15). Drivers by points: boolean chains 15, ternaries 6 (11 pts), if/else 5 (6 pts) (nesting depth added 6). Most of this is not in the body itself: 3 of the 32 points are its own statements and the rest belongs to 8 function literals inside it that branch (lines 674, 802, 619, …). 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.
profile-view.ProfileView (cognitive 32) apps/web/modules/settings/my-account/profile-view.tsx:68— profile-view.ProfileView has cognitive complexity 32 (threshold 15). Drivers by points: boolean chains 18, if/else 13, match/switch 1. Most of this is not in the body itself: 15 of the 32 points are its own statements and the rest belongs to 9 function items inside it that branch (a function literal at line 74, a function literal at line 271, onDeleteMeSuccessMutation, …). 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.
server.getLocationGroupedOptions (cognitive 32) packages/app-store/server.ts:13— server.getLocationGroupedOptions has cognitive complexity 32 (threshold 15). Drivers by points: if/else 13 (20 pts), ternaries 3 (8 pts), loops 2 (3 pts), boolean chains 1 (nesting depth added 13). Most of this is not in the body itself: 8 of the 32 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 88, 123). 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.
server.makeWhereClause (cognitive 32) packages/features/data-table/lib/server.ts:29— server.makeWhereClause has cognitive complexity 32 (threshold 15). Drivers by points: ternaries 7 (16 pts), if/else 6 (7 pts), boolean chains 5, match/switch 2 (4 pts) (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AvailabilitySettings.AvailabilitySettings (cognitive 32) packages/platform/atoms/availability/AvailabilitySettings.tsx:297— AvailabilitySettings.AvailabilitySettings has cognitive complexity 32 (threshold 15). Drivers by points: boolean chains 15, ternaries 9, if/else 5, error handling 2 (3 pts) (nesting depth added 1). Of this number, 17 points are the body's own statements and 15 belong to 8 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.
useEventTypeForm.useEventTypeForm.handleSubmit (cognitive 32) packages/platform/atoms/event-types/hooks/useEventTypeForm.ts:287— useEventTypeForm.useEventTypeForm.handleSubmit has cognitive complexity 32 (threshold 15). Drivers by points: if/else 16 (24 pts), boolean chains 5, ternaries 3 (nesting depth added 8). Of this number, 31 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
EditLocationDialog.EditLocationDialog (cognitive 31) apps/web/components/dialog/EditLocationDialog.tsx:82— EditLocationDialog.EditLocationDialog has cognitive complexity 31 (threshold 15). Drivers by points: if/else 16 (19 pts), boolean chains 6, ternaries 2 (5 pts), error handling 1 (nesting depth added 6). Most of this is not in the body itself: 1 of the 31 points is its own statement and the rest belongs to 9 function literals inside it that branch (lines 186, 115, 97, …). 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.
CreateOrEditOutOfOfficeModal.CreateOrEditOutOfOfficeEntryModal (cognitive 31) apps/web/modules/settings/outOfOffice/CreateOrEditOutOfOfficeModal.tsx:32— CreateOrEditOutOfOfficeModal.CreateOrEditOutOfOfficeEntryModal has cognitive complexity 31 (threshold 15). Drivers by points: boolean chains 16, ternaries 8, if/else 7. Of this number, 18 points are the body's own statements and 13 belong to 14 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.
lastAttendeeDeleteBooking.lastAttendeeDeleteBooking (cognitive 31) packages/features/bookings/lib/handleSeats/lib/lastAttendeeDeleteBooking.ts:14— lastAttendeeDeleteBooking.lastAttendeeDeleteBooking has cognitive complexity 31 (threshold 15). Drivers by points: if/else 6 (24 pts), boolean chains 4, loops 1 (2 pts), ternaries 1 (nesting depth added 19). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
duplicate.handler.duplicateHandler (cognitive 31) packages/trpc/server/routers/viewer/eventTypes/heavy/duplicate.handler.ts:20— duplicate.handler.duplicateHandler has cognitive complexity 31 (threshold 15). Drivers by points: if/else 12 (19 pts), ternaries 7, boolean chains 4, error handling 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SettingsLayoutAppDirClient.useTabs (cognitive 30) apps/web/app/(use-page-wrapper)/settings/(settings-layout)/SettingsLayoutAppDirClient.tsx:270— SettingsLayoutAppDirClient.useTabs has cognitive complexity 30 (threshold 15). Drivers by points: if/else 14 (24 pts), boolean chains 6 (nesting depth added 10). None of this is in the body itself: all 30 points belong to 4 function literals inside it that branch (lines 285, 369, 295, …). 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.
route.postHandler (cognitive 30) apps/web/app/api/recorded-daily-video/route.ts:54— route.postHandler has cognitive complexity 30 (threshold 15). Drivers by points: if/else 17 (27 pts), boolean chains 2, error handling 1 (nesting depth added 10). Of this number, 28 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
authorize-view.Authorize (cognitive 30) apps/web/modules/auth/oauth2/authorize-view.tsx:19— authorize-view.Authorize has cognitive complexity 30 (threshold 15). Drivers by points: boolean chains 15, if/else 10 (11 pts), ternaries 4 (nesting depth added 1). Most of this is not in the body itself: 14 of the 30 points are its own statements and the rest belongs to 7 function literals inside it that branch (lines 94, 107, 260, …). 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.
DateRangeFilter.DateRangeFilter (cognitive 30) apps/web/modules/data-table/components/filters/DateRangeFilter.tsx:44— DateRangeFilter.DateRangeFilter has cognitive complexity 30 (threshold 15). Drivers by points: boolean chains 14, if/else 8, ternaries 7 (8 pts) (nesting depth added 1). Of this number, 19 points are the body's own statements and 11 belong to 5 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.
SalesforceCRMService.buildRecordUpdatePayload (cognitive 30) packages/app-store/salesforce/lib/CrmService.ts:1365— SalesforceCRMService.buildRecordUpdatePayload has cognitive complexity 30 (threshold 15). Drivers by points: if/else 12 (25 pts), boolean chains 4, loops 1 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
EventManager.create (cognitive 30) packages/features/bookings/lib/EventManager.ts:287— EventManager.create has cognitive complexity 30 (threshold 15). Drivers by points: if/else 11 (16 pts), ternaries 8, boolean chains 6 (nesting depth added 5). Of this number, 21 points are the body's own statements and 9 belong to one function literal inside it that branches. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
ensureAvailableUsers._ensureAvailableUsers (cognitive 30) packages/features/bookings/lib/handleNewBooking/ensureAvailableUsers.ts:57— ensureAvailableUsers._ensureAvailableUsers has cognitive complexity 30 (threshold 15). Drivers by points: ternaries 7 (12 pts), if/else 8 (11 pts), boolean chains 4, error handling 2 (3 pts) (nesting depth added 9). Of this number, 23 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.
eventNaming.getEventName (cognitive 30) packages/features/eventtypes/lib/eventNaming.ts:31— eventNaming.getEventName has cognitive complexity 30 (threshold 15). Drivers by points: if/else 11 (15 pts), boolean chains 9, ternaries 3 (6 pts) (nesting depth added 7). Most of this is not in the body itself: 13 of the 30 points are its own statements and the rest belongs to one function literal inside it that branches (line 83). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
scheduleTrigger.addSubscription (cognitive 30) packages/features/webhooks/lib/scheduleTrigger.ts:30— scheduleTrigger.addSubscription has cognitive complexity 30 (threshold 15). Drivers by points: ternaries 9 (18 pts), boolean chains 5, if/else 3 (4 pts), loops 1 (2 pts), error handling 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
get.handler.getBookings (cognitive 30) packages/trpc/server/routers/viewer/bookings/get.handler.ts:93— get.handler.getBookings has cognitive complexity 30 (threshold 15). Drivers by points: if/else 12 (20 pts), boolean chains 8, ternaries 2 (nesting depth added 8). Of this number, 22 points are the body's own statements and 8 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.
FileUploader.FileUploader (cognitive 30) packages/ui/components/file-uploader/FileUploader.tsx:72— FileUploader.FileUploader has cognitive complexity 30 (threshold 15). Drivers by points: ternaries 8 (12 pts), if/else 9 (10 pts), boolean chains 5, error handling 1 (2 pts), loops 1 (nesting depth added 6). Most of this is not in the body itself: 8 of the 30 points are its own statements and the rest belongs to 4 function items inside it that branch (a function literal at line 130, validateFile, getFileIcon, …). 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.
EventTypesAtomService.getEventTypesAppIntegration (cognitive 29) apps/api/v2/src/modules/atoms/services/event-types-atom.service.ts:192— EventTypesAtomService.getEventTypesAppIntegration has cognitive complexity 29 (threshold 15). Drivers by points: if/else 10 (18 pts), boolean chains 8, ternaries 2 (3 pts) (nesting depth added 9). Most of this is not in the body itself: 9 of the 29 points are its own statements and the rest belongs to 7 function literals inside it that branch (lines 247, 203, 215, …). 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.
route.handler (cognitive 29) apps/web/app/api/auth/two-factor/totp/disable/route.ts:18— route.handler has cognitive complexity 29 (threshold 15). Drivers by points: if/else 17 (26 pts), boolean chains 3 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AvailableTimes.SlotItem (cognitive 29) apps/web/modules/bookings/components/AvailableTimes.tsx:79— AvailableTimes.SlotItem has cognitive complexity 29 (threshold 15). Drivers by points: boolean chains 23, if/else 3, ternaries 2 (3 pts) (nesting depth added 1). Of this number, 24 points are the body's own statements and 5 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.
SaveFilterSegmentButton.SaveFilterSegmentButton (cognitive 29) apps/web/modules/data-table/components/segment/SaveFilterSegmentButton.tsx:28— SaveFilterSegmentButton.SaveFilterSegmentButton has cognitive complexity 29 (threshold 15). Drivers by points: boolean chains 12, if/else 10 (12 pts), ternaries 4 (5 pts) (nesting depth added 3). Most of this is not in the body itself: 7 of the 29 points are its own statements and the rest belongs to 4 function items inside it that branch (onSubmit, handleOpenChange, 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.
callback.handler (cognitive 29) REDACTED:18— callback.handler has cognitive complexity 29 (threshold 15). Drivers by points: if/else 15 (24 pts), boolean chains 2, error handling 1 (2 pts), loops 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
VideoApiAdapter.hasInvalidConsecutiveChars (cognitive 29) packages/app-store/zoomvideo/lib/VideoApiAdapter.ts:81— VideoApiAdapter.hasInvalidConsecutiveChars has cognitive complexity 29 (threshold 15). Drivers by points: if/else 11 (22 pts), loops 5 (6 pts), boolean chains 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
scheduleTrigger.listBookings (cognitive 29) packages/features/webhooks/lib/scheduleTrigger.ts:182— scheduleTrigger.listBookings has cognitive complexity 29 (threshold 15). Drivers by points: ternaries 10 (19 pts), boolean chains 6, if/else 3, error handling 1 (nesting depth added 9). Of this number, 26 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.
SlotsService_2024_09_04.reserveSlot (cognitive 28) apps/api/v2/src/modules/slots/slots-2024-09-04/services/slots.service.ts:95— SlotsService_2024_09_04.reserveSlot has cognitive complexity 28 (threshold 15). Drivers by points: if/else 16 (22 pts), boolean chains 4, error handling 1 (2 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
UserForm.UserForm (cognitive 28) apps/web/modules/users/components/UserForm.tsx:64— UserForm.UserForm has cognitive complexity 28 (threshold 15). Drivers by points: boolean chains 25, if/else 3. Of this number, 15 points are the body's own statements and 13 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.
booking-fields.transformBookingFieldsInternalToApi (cognitive 27) apps/api/v2/src/platform/event-types/event-types_2024_06_14/transformers/internal-to-api/booking-fields.ts:29— booking-fields.transformBookingFieldsInternalToApi has cognitive complexity 27 (threshold 15). Drivers by points: ternaries 4 (12 pts), boolean chains 6, if/else 3 (5 pts), match/switch 2 (4 pts) (nesting depth added 12). None of this is in the body itself: all 27 points belong to one function literal inside it that branches (line 32). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
Setup.HitPaySetupPage (cognitive 27) apps/web/components/apps/hitpay/Setup.tsx:71— Setup.HitPaySetupPage has cognitive complexity 27 (threshold 15). Drivers by points: boolean chains 13, if/else 6 (7 pts), ternaries 5 (6 pts), error handling 1 (nesting depth added 2). Of this number, 14 points are the body's own statements and 13 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.
DataTable.DataTableBody (cognitive 27) apps/web/modules/data-table/components/DataTable.tsx:297— DataTable.DataTableBody has cognitive complexity 27 (threshold 15). Drivers by points: boolean chains 14, ternaries 7 (8 pts), if/else 5 (nesting depth added 1). Most of this is not in the body itself: 5 of the 27 points are its own statements and the rest belongs to 5 function literals inside it that branch (lines 366, 319, 418, …). 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.
callback.getHandler (cognitive 27) packages/app-store/googlecalendar/api/callback.ts:26— callback.getHandler has cognitive complexity 27 (threshold 15). Drivers by points: if/else 12 (23 pts), boolean chains 2, error handling 1 (2 pts) (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CalApi.__modal (cognitive 27) REDACTED:1145— CalApi.__modal has cognitive complexity 27 (threshold 15). Drivers by points: if/else 11 (19 pts), ternaries 2 (5 pts), boolean chains 3 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
EventManager.updateAllCalendarEvents (cognitive 27) packages/features/bookings/lib/EventManager.ts:1100— EventManager.updateAllCalendarEvents has cognitive complexity 27 (threshold 15). Drivers by points: if/else 10 (19 pts), loops 2 (4 pts), boolean chains 3, error handling 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
createCRMEvent.createCRMEvent (cognitive 27) packages/features/tasker/tasks/crm/createCRMEvent.ts:41— createCRMEvent.createCRMEvent has cognitive complexity 27 (threshold 15). Drivers by points: if/else 12 (18 pts), boolean chains 3, error handling 2 (3 pts), loops 3 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MultiSelectCheckboxes.MultiSelectCheckboxes (cognitive 27) packages/ui/components/form/checkbox/MultiSelectCheckboxes.tsx:75— MultiSelectCheckboxes.MultiSelectCheckboxes has cognitive complexity 27 (threshold 15). Drivers by points: if/else 10 (22 pts), ternaries 3, boolean chains 2 (nesting depth added 12). Most of this is not in the body itself: 3 of the 27 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 99, 86). 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.
handleConfirmation.handleConfirmation (cognitive 26) packages/features/bookings/lib/handleConfirmation.ts:23— handleConfirmation.handleConfirmation has cognitive complexity 26 (threshold 15). Drivers by points: boolean chains 8, if/else 6 (8 pts), ternaries 5 (7 pts), error handling 2 (3 pts) (nesting depth added 5). Of this number, 24 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.
scheduleTrigger.deleteSubscription (cognitive 26) packages/features/webhooks/lib/scheduleTrigger.ts:132— scheduleTrigger.deleteSubscription has cognitive complexity 26 (threshold 15). Drivers by points: ternaries 9 (18 pts), boolean chains 4, if/else 3, error handling 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
InputBookingFieldValidator_2024_06_14.validate (cognitive 26) REDACTED:936— InputBookingFieldValidator_2024_06_14.validate has cognitive complexity 26 (threshold 15). Drivers by points: if/else 8 (14 pts), boolean chains 6, ternaries 2 (5 pts), loops 1 (nesting depth added 9). Of this number, 25 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
requestReschedule.handler.requestRescheduleHandler (cognitive 26) packages/trpc/server/routers/viewer/bookings/requestReschedule.handler.ts:47— requestReschedule.handler.requestRescheduleHandler has cognitive complexity 26 (threshold 15). Drivers by points: boolean chains 10, if/else 10, ternaries 6. Of this number, 19 points are the body's own statements and 7 belong to 2 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.
reportBooking.handler.reportBookingHandler (cognitive 26) packages/trpc/server/routers/viewer/bookings/reportBooking.handler.ts:24— reportBooking.handler.reportBookingHandler has cognitive complexity 26 (threshold 15). Drivers by points: ternaries 6 (11 pts), if/else 6, boolean chains 4, error handling 2 (4 pts), loops 1 (nesting depth added 7). Of this number, 25 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CancelBooking.CancelBooking (cognitive 25) apps/web/components/booking/CancelBooking.tsx:118— CancelBooking.CancelBooking has cognitive complexity 25 (threshold 15). Drivers by points: boolean chains 17, if/else 5, ternaries 3. Of this number, 17 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.
TravelScheduleModal.TravelScheduleModal::isOverlapping (cognitive 25) apps/web/components/settings/TravelScheduleModal.tsx:49— TravelScheduleModal.TravelScheduleModal::isOverlapping has cognitive complexity 25 (threshold 15). Drivers by points: if/else 6 (17 pts), boolean chains 4, ternaries 2 (3 pts), loops 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
EventMeta.EventMeta (cognitive 25) apps/web/modules/bookings/components/EventMeta.tsx:46— EventMeta.EventMeta has cognitive complexity 25 (threshold 15). Drivers by points: boolean chains 17, if/else 3 (4 pts), ternaries 3 (4 pts) (nesting depth added 2). Of this number, 20 points are the body's own statements and 5 belong to 2 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.
general-view.GeneralView (cognitive 25) apps/web/modules/settings/my-account/general-view.tsx:51— general-view.GeneralView has cognitive complexity 25 (threshold 15). Drivers by points: boolean chains 20, if/else 4, ternaries 1. Most of this is not in the body itself: 11 of the 25 points are its own statements and the rest belongs to 11 function literals inside it that branch (lines 93, 63, 200, …). 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.
password-view.PasswordView (cognitive 25) apps/web/modules/settings/security/password-view.tsx:51— password-view.PasswordView has cognitive complexity 25 (threshold 15). Drivers by points: if/else 7 (10 pts), boolean chains 8, ternaries 5 (7 pts) (nesting depth added 5). Of this number, 13 points are the body's own statements and 12 belong to 5 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.
useAddAppMutation.useAddAppMutation (cognitive 25) packages/app-store/_utils/useAddAppMutation.ts:28— useAddAppMutation.useAddAppMutation has cognitive complexity 25 (threshold 15). Drivers by points: boolean chains 11, if/else 9, ternaries 4 (5 pts) (nesting depth added 1). None of this is in the body itself: all 25 points belong to one function literal inside it that branches (line 46). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
BaseScheduledEmail.BaseScheduledEmail (cognitive 25) packages/emails/src/templates/BaseScheduledEmail.tsx:18— BaseScheduledEmail.BaseScheduledEmail has cognitive complexity 25 (threshold 15). Drivers by points: boolean chains 20, ternaries 3 (4 pts), if/else 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.
RecurringBookingService.handleNewRecurringBooking (cognitive 25) packages/features/bookings/lib/service/RecurringBookingService.ts:11— RecurringBookingService.handleNewRecurringBooking has cognitive complexity 25 (threshold 15). Drivers by points: if/else 4 (11 pts), ternaries 3 (6 pts), loops 2 (5 pts), boolean chains 3 (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.
EventTypePlatformWrapper.EventType (cognitive 25) packages/platform/atoms/event-types/wrappers/EventTypePlatformWrapper.tsx:74— EventTypePlatformWrapper.EventType has cognitive complexity 25 (threshold 15). Drivers by points: if/else 12, ternaries 9, boolean chains 2, error handling 1 (2 pts) (nesting depth added 1). Most of this is not in the body itself: 8 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 178, onDelete, a function literal at line 124, …). 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.
create.handler.createHandler (cognitive 25) packages/trpc/server/routers/viewer/eventTypes/heavy/create.handler.ts:45— create.handler.createHandler has cognitive complexity 25 (threshold 15). Drivers by points: if/else 8 (13 pts), boolean chains 7, ternaries 4, error handling 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Select.Select (cognitive 25) packages/ui/components/form/select/Select.tsx:14— Select.Select has cognitive complexity 25 (threshold 15). Drivers by points: ternaries 11 (18 pts), boolean chains 7 (nesting depth added 7). Most of this is not in the body itself: 1 of the 25 points is its own statement and the rest belongs to 7 function literals inside it that branch (lines 71, 107, 53, …). 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.
notification-sound-handler.NotificationSoundHandler (cognitive 24) apps/web/components/notification-sound-handler.tsx:5— notification-sound-handler.NotificationSoundHandler has cognitive complexity 24 (threshold 15). Drivers by points: if/else 16 (18 pts), boolean chains 4, error handling 2 (nesting depth added 2). None of this is in the body itself: all 24 points belong to 8 function items inside it that branch (playSound, initializeAudioSystem, 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.
BlocklistEntryDetailsSheet.BlocklistEntryDetailsSheet (cognitive 24) apps/web/modules/blocklist/components/BlocklistEntryDetailsSheet.tsx:32— BlocklistEntryDetailsSheet.BlocklistEntryDetailsSheet has cognitive complexity 24 (threshold 15). Drivers by points: ternaries 8 (17 pts), boolean chains 6, if/else 1 (nesting depth added 9). Of this number, 21 points are the body's own statements and 3 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.
Event.Event (cognitive 24) apps/web/modules/calendars/weeklyview/components/event/Event.tsx:60— Event.Event has cognitive complexity 24 (threshold 15). Drivers by points: boolean chains 16, ternaries 7 (8 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.
signup-view.Signup::signUp (cognitive 24) apps/web/modules/signup-view.tsx:240— signup-view.Signup::signUp has cognitive complexity 24 (threshold 15). Drivers by points: if/else 8 (16 pts), ternaries 4 (7 pts), error handling 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (signup-view.Signup) 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.
videos-single-view.LogInOverlay (cognitive 24) REDACTED:310— videos-single-view.LogInOverlay has cognitive complexity 24 (threshold 15). Drivers by points: if/else 11 (15 pts), boolean chains 6, ternaries 1 (2 pts), error handling 1 (nesting depth added 5). Most of this is not in the body itself: 2 of the 24 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 331, 419, 428, …). 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.
EventTypeAppCardInterface.EventTypeAppCard (cognitive 24) packages/app-store/salesforce/components/EventTypeAppCardInterface.tsx:24— EventTypeAppCardInterface.EventTypeAppCard has cognitive complexity 24 (threshold 15). Drivers by points: ternaries 10 (14 pts), if/else 4 (8 pts), boolean chains 2 (nesting depth added 8). Of this number, 16 points are the body's own statements and 8 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.
callback.getHandler (cognitive 24) REDACTED:26— callback.getHandler has cognitive complexity 24 (threshold 15). Drivers by points: if/else 10 (15 pts), boolean chains 7, error handling 1 (2 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
bookingSuccessRedirect.getBookingRedirectExtraParams (cognitive 24) packages/features/bookings/lib/bookingSuccessRedirect.ts:77— bookingSuccessRedirect.getBookingRedirectExtraParams has cognitive complexity 24 (threshold 15). Drivers by points: if/else 13, boolean chains 10, ternaries 1. Most of this is not in the body itself: 3 of the 24 points are its own statements and the rest belongs to 6 function items inside it that branch (extractAttendeesAndGuests, extractResponseDetails, 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.
createBooking.buildNewBookingData (cognitive 24) packages/features/bookings/lib/handleNewBooking/createBooking.ts:168— createBooking.buildNewBookingData has cognitive complexity 24 (threshold 15). Drivers by points: if/else 6 (10 pts), ternaries 8, boolean chains 6 (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.
CreateEventTypeForm.CreateEventTypeForm (cognitive 24) packages/features/eventtypes/components/CreateEventTypeForm.tsx:21— CreateEventTypeForm.CreateEventTypeForm has cognitive complexity 24 (threshold 15). Drivers by points: ternaries 9 (19 pts), boolean chains 4, if/else 1 (nesting depth added 10). Of this number, 22 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
getEventTypesByViewer.getEventTypesByViewer (cognitive 24) packages/features/eventtypes/lib/getEventTypesByViewer.ts:46— getEventTypesByViewer.getEventTypesByViewer has cognitive complexity 24 (threshold 15). Drivers by points: boolean chains 12, if/else 8, ternaries 4. Most of this is not in the body itself: 11 of the 24 points are its own statements and the rest belongs to 7 function items inside it that branch (mapEventType, a function literal at line 157, filterByTeamIds, …). 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.
ScheduleComponent.CopyTimes (cognitive 24) packages/features/schedules/components/ScheduleComponent.tsx:661— ScheduleComponent.CopyTimes has cognitive complexity 24 (threshold 15). Drivers by points: if/else 15 (17 pts), boolean chains 7 (nesting depth added 2). None of this is in the body itself: all 24 points belong to 8 function items inside it that branch (handleKeyDown, a function literal at line 742, a function literal at line 718, …). 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.
useHandleBookEvent.useHandleBookEvent::handleBookEvent (cognitive 24) packages/platform/atoms/hooks/bookings/useHandleBookEvent.ts:67— useHandleBookEvent.useHandleBookEvent::handleBookEvent has cognitive complexity 24 (threshold 15). Drivers by points: boolean chains 10, ternaries 4 (8 pts), if/else 4 (6 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
bookingScenario.mockCalendar (cognitive 24) REDACTED:1662— bookingScenario.mockCalendar has cognitive complexity 24 (threshold 15). Drivers by points: boolean chains 16, if/else 6, ternaries 2. Most of this is not in the body itself: 1 of the 24 points is its own statement and the rest belongs to 4 function literals inside it that branch (lines 1720, 1791, 1838, …). 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.
TextField.InputField (cognitive 24) packages/ui/components/form/inputs/TextField.tsx:103— TextField.InputField has cognitive complexity 24 (threshold 15). Drivers by points: boolean chains 20, ternaries 3 (4 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.
seed.main (cognitive 24) REDACTED:634— seed.main has cognitive complexity 24 (threshold 15). Drivers by points: boolean chains 19, ternaries 2 (3 pts), if/else 2 (nesting depth added 1). Of this number, 23 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.
getServerSideProps.getServerSideProps (cognitive 23) apps/web/lib/reschedule/[uid]/getServerSideProps.ts:24— getServerSideProps.getServerSideProps has cognitive complexity 23 (threshold 15). Drivers by points: if/else 10 (13 pts), boolean chains 6, ternaries 4 (nesting depth added 3). Of this number, 21 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
Members.EventMembers (cognitive 23) apps/web/modules/bookings/components/event-meta/Members.tsx:24— Members.EventMembers has cognitive complexity 23 (threshold 15). Drivers by points: boolean chains 12, ternaries 6 (9 pts), if/else 2 (nesting depth added 3). Of this number, 19 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.
Embed.EmailEmbed (cognitive 23) REDACTED:245— Embed.EmailEmbed has cognitive complexity 23 (threshold 15). Drivers by points: if/else 9 (12 pts), ternaries 6 (9 pts), boolean chains 2 (nesting depth added 6). Most of this is not in the body itself: 11 of the 23 points are its own statements and the rest belongs to 2 function items inside it that branch (handleSlotClick, a function literal at line 392). 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.
EventTypeLayout.EventTypeSingleLayout (cognitive 23) apps/web/modules/event-types/components/EventTypeLayout.tsx:52— EventTypeLayout.EventTypeSingleLayout has cognitive complexity 23 (threshold 15). Drivers by points: boolean chains 14, ternaries 8 (9 pts) (nesting depth added 1). 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.
AssignFeatureSheet.AssignFeatureSheet (cognitive 23) apps/web/modules/feature-flags/components/AssignFeatureSheet.tsx:31— AssignFeatureSheet.AssignFeatureSheet has cognitive complexity 23 (threshold 15). Drivers by points: boolean chains 10, ternaries 4 (10 pts), if/else 3 (nesting depth added 6). Most of this is not in the body itself: 7 of the 23 points are its own statements and the rest belongs to 3 function items inside it that branch (a function literal at line 124, handleToggleTeam, a function literal at line 52). 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.
proxy.sanitizeRequestHeaders (cognitive 23) apps/web/proxy.ts:25— proxy.sanitizeRequestHeaders has cognitive complexity 23 (threshold 15). Drivers by points: if/else 6 (14 pts), error handling 1 (4 pts), loops 2 (4 pts), boolean chains 1 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CalendarEventBuilder.fromBooking (cognitive 23) packages/features/CalendarEventBuilder.ts:97— CalendarEventBuilder.fromBooking has cognitive complexity 23 (threshold 15). Drivers by points: if/else 8 (9 pts), boolean chains 7, ternaries 7 (nesting depth added 1). Of this number, 18 points are the body's own statements and 5 belong to 2 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.
determineReschedulePreventionRedirect.determineReschedulePreventionRedirect (cognitive 23) packages/features/bookings/lib/reschedule/determineReschedulePreventionRedirect.ts:69— determineReschedulePreventionRedirect.determineReschedulePreventionRedirect has cognitive complexity 23 (threshold 15). Drivers by points: if/else 7 (10 pts), boolean chains 7, ternaries 3 (6 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CalendarManager.getConnectedCalendars (cognitive 23) packages/features/calendars/lib/CalendarManager.ts:112— CalendarManager.getConnectedCalendars has cognitive complexity 23 (threshold 15). Drivers by points: if/else 9 (17 pts), boolean chains 3, loops 1 (2 pts), error handling 1 (nesting depth added 9). Most of this is not in the body itself: 10 of the 23 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 130, 158). 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.
util.createWebhookProcedure (cognitive 23) packages/trpc/server/routers/viewer/webhook/util.ts:8— util.createWebhookProcedure has cognitive complexity 23 (threshold 15). Drivers by points: if/else 11 (20 pts), boolean chains 3 (nesting depth added 9). None of this is in the body itself: all 23 points belong to one function literal inside it that branches (line 9). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
AvailableSlotsService.calculateHostsAndAvailabilities (cognitive 23) REDACTED:678— AvailableSlotsService.calculateHostsAndAvailabilities has cognitive complexity 23 (threshold 15). Drivers by points: boolean chains 15, ternaries 5, if/else 3. Of this number, 20 points are the body's own statements and 3 belong to 2 function literals inside it that branch. To reduce it, 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.
route.postHandler (cognitive 22) apps/web/app/api/cron/syncAppMeta/route.ts:20— route.postHandler has cognitive complexity 22 (threshold 15). Drivers by points: if/else 9 (18 pts), boolean chains 3, loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
getServerSideProps.getServerSideProps (cognitive 22) apps/web/lib/video/[uid]/getServerSideProps.ts:121— getServerSideProps.getServerSideProps has cognitive complexity 22 (threshold 15). Drivers by points: ternaries 9, if/else 6 (7 pts), boolean chains 6 (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.
verify-view.Verify (cognitive 22) apps/web/modules/auth/verify-view.tsx:114— verify-view.Verify has cognitive complexity 22 (threshold 15). Drivers by points: ternaries 9 (11 pts), if/else 6 (7 pts), boolean chains 4 (nesting depth added 3). Of this number, 15 points are the body's own statements and 7 belong to 4 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, 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.
AvailableTimeSlots.AvailableTimeSlots (cognitive 22) apps/web/modules/bookings/components/AvailableTimeSlots.tsx:67— AvailableTimeSlots.AvailableTimeSlots has cognitive complexity 22 (threshold 15). Drivers by points: boolean chains 14, if/else 7, ternaries 1. Of this number, 11 points are the body's own statements and 11 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.
Duration.EventDuration (cognitive 22) apps/web/modules/bookings/components/event-meta/Duration.tsx:40— Duration.EventDuration has cognitive complexity 22 (threshold 15). Drivers by points: boolean chains 10, if/else 7, ternaries 3 (5 pts) (nesting depth added 2). Most of this is not in the body itself: 9 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 71, a function literal at line 78, a function literal at line 120, …). 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.
HostLocations.HostLocationRow (cognitive 22) apps/web/modules/event-types/components/locations/HostLocations.tsx:256— HostLocations.HostLocationRow has cognitive complexity 22 (threshold 15). Drivers by points: boolean chains 11, if/else 8, ternaries 3. 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 (a function literal at line 293, handleLocationSelect, 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.
TeamsFilter.TeamsFilter (cognitive 22) apps/web/modules/filters/components/TeamsFilter.tsx:22— TeamsFilter.TeamsFilter has cognitive complexity 22 (threshold 15). Drivers by points: if/else 12 (15 pts), boolean chains 5, ternaries 2 (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 3 function items inside it that branch (a function literal at line 92, getCheckedOptionsNames, a function literal at line 113). 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.
FormBuilderField.ComponentForField (cognitive 22) REDACTED:242— FormBuilderField.ComponentForField has cognitive complexity 22 (threshold 15). Drivers by points: if/else 13 (18 pts), boolean chains 2, ternaries 1 (2 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
UserAvailabilityService.getTimezoneFromDelegatedCalendars (cognitive 22) packages/features/availability/lib/getUserAvailability.ts:232— UserAvailabilityService.getTimezoneFromDelegatedCalendars has cognitive complexity 22 (threshold 15). Drivers by points: if/else 6 (9 pts), error handling 3 (7 pts), boolean chains 5, loops 1 (nesting depth added 7). Of this number, 21 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
getAllCredentials.getAllCredentialsIncludeServiceAccountKey (cognitive 22) packages/features/bookings/lib/getAllCredentialsForUsersOnEvent/getAllCredentials.ts:22— getAllCredentials.getAllCredentialsIncludeServiceAccountKey has cognitive complexity 22 (threshold 15). Drivers by points: if/else 8 (14 pts), boolean chains 6, loops 1, ternaries 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
getConnectedDestinationCalendars.getConnectedDestinationCalendarsAndEnsureDefaultsInDb (cognitive 22) packages/features/calendars/lib/getConnectedDestinationCalendars.ts:275— getConnectedDestinationCalendars.getConnectedDestinationCalendarsAndEnsureDefaultsInDb has cognitive complexity 22 (threshold 15). Drivers by points: if/else 10 (17 pts), boolean chains 5 (nesting depth added 7). Of this number, 14 points are the body's own statements and 8 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ProfileRepository.findByUpIdWithAuth (cognitive 22) packages/features/profile/repositories/ProfileRepository.ts:505— ProfileRepository.findByUpIdWithAuth has cognitive complexity 22 (threshold 15). Drivers by points: if/else 13 (20 pts), boolean chains 2 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
date-ranges.intersect (cognitive 22) packages/features/schedules/lib/date-ranges.ts:354— date-ranges.intersect has cognitive complexity 22 (threshold 15). Drivers by points: if/else 5 (10 pts), ternaries 2 (8 pts), loops 2 (3 pts), boolean chains 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
getServerErrorFromUnknown.getServerErrorFromUnknown (cognitive 22) packages/lib/server/getServerErrorFromUnknown.ts:53— getServerErrorFromUnknown.getServerErrorFromUnknown has cognitive complexity 22 (threshold 15). Drivers by points: ternaries 6 (11 pts), if/else 9, boolean chains 2 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
prepare-local-for-delegation-credentials-testing.main (cognitive 22) scripts/prepare-local-for-delegation-credentials-testing.js:9— prepare-local-for-delegation-credentials-testing.main has cognitive complexity 22 (threshold 15). Drivers by points: if/else 16 (20 pts), boolean chains 1, loops 1 (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
ApiKeyDialogForm.ApiKeyDialogForm (cognitive 21) apps/web/modules/api-keys/api-keys/components/ApiKeyDialogForm.tsx:21— ApiKeyDialogForm.ApiKeyDialogForm has cognitive complexity 21 (threshold 15). Drivers by points: ternaries 5 (9 pts), boolean chains 8, if/else 3 (4 pts) (nesting depth added 5). Of this number, 15 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.
CreateBlocklistEntryModal.CreateBlocklistEntryModal (cognitive 21) apps/web/modules/blocklist/components/CreateBlocklistEntryModal.tsx:25— CreateBlocklistEntryModal.CreateBlocklistEntryModal has cognitive complexity 21 (threshold 15). Drivers by points: if/else 7 (9 pts), boolean chains 6, ternaries 5 (6 pts) (nesting depth added 3). Most of this is not in the body itself: 9 of the 21 points are its own statements and the rest belongs to 4 function items inside it that branch (validateValue, a function literal at line 52, a function literal at line 114, …). 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.
DataTable.TableHeadLabel (cognitive 21) apps/web/modules/data-table/components/DataTable.tsx:446— DataTable.TableHeadLabel has cognitive complexity 21 (threshold 15). Drivers by points: boolean chains 9, ternaries 4 (8 pts), if/else 3 (4 pts) (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
OutOfOfficeEntriesList.OutOfOfficeEntriesListContent (cognitive 21) apps/web/modules/settings/outOfOffice/OutOfOfficeEntriesList.tsx:96— OutOfOfficeEntriesList.OutOfOfficeEntriesListContent has cognitive complexity 21 (threshold 15). Drivers by points: boolean chains 15, ternaries 5 (6 pts) (nesting depth added 1). Most of this is not in the body itself: 1 of the 21 points is its own statement and the rest belongs to 4 function literals inside it that branch (lines 172, 222, 236, …). 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.
SearchDialog.SearchDialog (cognitive 21) packages/app-store/giphy/components/SearchDialog.tsx:24— SearchDialog.SearchDialog has cognitive complexity 21 (threshold 15). Drivers by points: if/else 10 (12 pts), boolean chains 7, ternaries 2 (nesting depth added 2). Most of this is not in the body itself: 4 of the 21 points are its own statements and the rest belongs to 4 function items inside it that branch (searchGiphy, getGiphyByUrl, handleFormSubmit, …). 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.
FieldRulesSettings.FieldRulesSettings (cognitive 21) packages/app-store/salesforce/components/components/FieldRulesSettings.tsx:14— FieldRulesSettings.FieldRulesSettings has cognitive complexity 21 (threshold 15). Drivers by points: ternaries 7 (11 pts), boolean chains 5, if/else 4 (5 pts) (nesting depth added 5). Most of this is not in the body itself: 1 of the 21 points is its own statement and the rest belongs to 7 function items inside it that branch (a function literal at line 82, saveEditing, a function literal at line 91, …). 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.
HubspotCalendarService.getFieldValue (cognitive 21) packages/app-store/hubspot/lib/CrmService.ts:176— HubspotCalendarService.getFieldValue has cognitive complexity 21 (threshold 15). Drivers by points: if/else 10 (18 pts), boolean chains 3 (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.
subscription.handler (cognitive 21) packages/app-store/stripepayment/api/subscription.ts:12— subscription.handler has cognitive complexity 21 (threshold 15). Drivers by points: if/else 9 (17 pts), boolean chains 4 (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.
useBookerLayout.useBookerLayout (cognitive 21) packages/features/bookings/Booker/hooks/useBookerLayout.ts:22— useBookerLayout.useBookerLayout has cognitive complexity 21 (threshold 15). Drivers by points: ternaries 7 (9 pts), boolean chains 7, if/else 4 (5 pts) (nesting depth added 3). Of this number, 13 points are the body's own statements and 8 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.
getCalEventResponses.getCalEventResponses (cognitive 21) packages/features/bookings/lib/getCalEventResponses.ts:15— getCalEventResponses.getCalEventResponses has cognitive complexity 21 (threshold 15). Drivers by points: if/else 9 (15 pts), boolean chains 3, loops 1 (2 pts), ternaries 1 (nesting depth added 7). Of this number, 12 points are the body's own statements and 9 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.
processPaymentRefund.processPaymentRefund (cognitive 21) packages/features/bookings/lib/payment/processPaymentRefund.ts:9— processPaymentRefund.processPaymentRefund has cognitive complexity 21 (threshold 15). Drivers by points: if/else 9 (10 pts), boolean chains 4, ternaries 2 (4 pts), error handling 1 (2 pts), loops 1 (nesting depth added 4). Of this number, 18 points are the body's own statements and 3 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.
DateOverrideInputDialog.DateOverrideForm (cognitive 21) packages/features/schedules/components/DateOverrideInputDialog.tsx:22— DateOverrideInputDialog.DateOverrideForm has cognitive complexity 21 (threshold 15). Drivers by points: if/else 9, ternaries 6 (8 pts), boolean chains 4 (nesting depth added 2). Of this number, 12 points are the body's own statements and 9 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, 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.
CalendarService.buildVTimezone (cognitive 21) packages/lib/CalendarService.ts:238— CalendarService.buildVTimezone has cognitive complexity 21 (threshold 15). Drivers by points: if/else 10 (16 pts), ternaries 3 (5 pts) (nesting depth added 8). Of this number, 20 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, 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.
AvailabilitySettingsPlatformWrapper.AvailabilitySettingsPlatformWrapper (cognitive 21) packages/platform/atoms/availability/wrappers/AvailabilitySettingsPlatformWrapper.tsx:44— AvailabilitySettingsPlatformWrapper.AvailabilitySettingsPlatformWrapper has cognitive complexity 21 (threshold 15). Drivers by points: if/else 12, boolean chains 5, ternaries 2 (4 pts) (nesting depth added 2). Most of this is not in the body itself: 9 of the 21 points are its own statements and the rest belongs to 7 function items inside it that branch (a function literal at line 153, a function literal at line 164, handleUpdate, …). 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.
expects.expectSuccessfulBookingCreationEmails (cognitive 21) packages/testing/src/lib/bookingScenario/expects.ts:454— expects.expectSuccessfulBookingCreationEmails has cognitive complexity 21 (threshold 15). Drivers by points: ternaries 11 (15 pts), boolean chains 4, if/else 2 (nesting depth added 4). Of this number, 11 points are the body's own statements and 10 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.
route.handler (cognitive 20) apps/web/app/api/social/og/image/route.tsx:34— route.handler has cognitive complexity 20 (threshold 15). Drivers by points: if/else 6 (12 pts), error handling 4 (7 pts), match/switch 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
getThemeProviderProps.getThemeProviderProps (cognitive 20) apps/web/lib/getThemeProviderProps.ts:74— getThemeProviderProps.getThemeProviderProps has cognitive complexity 20 (threshold 15). Drivers by points: ternaries 9 (13 pts), boolean chains 5, if/else 2 (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.
BookingDetailsSheet.BookingDetailsSheetInner (cognitive 20) apps/web/modules/bookings/components/BookingDetailsSheet.tsx:141— BookingDetailsSheet.BookingDetailsSheetInner has cognitive complexity 20 (threshold 15). Drivers by points: boolean chains 14, ternaries 3, if/else 2, match/switch 1. Of this number, 12 points are the body's own statements and 8 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.
EventAppsTab.EventAppsTab (cognitive 20) apps/web/modules/event-types/components/tabs/apps/EventAppsTab.tsx:19— EventAppsTab.EventAppsTab has cognitive complexity 20 (threshold 15). Drivers by points: boolean chains 11, if/else 3 (4 pts), ternaries 3 (4 pts), loops 1 (nesting depth added 2). Of this number, 14 points are the body's own statements and 6 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.
event-types-listing-view.Item (cognitive 20) apps/web/modules/event-types/views/event-types-listing-view.tsx:170— event-types-listing-view.Item has cognitive complexity 20 (threshold 15). Drivers by points: boolean chains 15, ternaries 4 (5 pts) (nesting depth added 1). Of this number, 15 points are the body's own statements and 5 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.
useSchedule.useSchedule (cognitive 20) apps/web/modules/schedules/hooks/useSchedule.ts:51— useSchedule.useSchedule has cognitive complexity 20 (threshold 15). Drivers by points: boolean chains 8, ternaries 8, if/else 3 (4 pts) (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
HitPayPaymentService.create (cognitive 20) packages/app-store/hitpay/lib/PaymentService.ts:38— HitPayPaymentService.create has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (11 pts), boolean chains 4, error handling 2 (3 pts), ternaries 2 (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
handlePaymentSuccess.handlePaymentSuccess (cognitive 20) packages/app-store/_utils/payments/handlePaymentSuccess.ts:29— handlePaymentSuccess.handlePaymentSuccess has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (8 pts), ternaries 5 (6 pts), boolean chains 4, error handling 2 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
deleteRecordings.deleteRecordingsFromJson (cognitive 20) packages/app-store/dailyvideo/lib/scripts/deleteRecordings.ts:311— deleteRecordings.deleteRecordingsFromJson has cognitive complexity 20 (threshold 15). Drivers by points: if/else 9 (16 pts), loops 2 (3 pts), error handling 1 (nesting depth added 8). Of this number, 13 points are the body's own statements and 7 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.
TeamInviteEmail.TeamInviteEmail (cognitive 20) packages/emails/src/templates/TeamInviteEmail.tsx:24— TeamInviteEmail.TeamInviteEmail has cognitive complexity 20 (threshold 15). Drivers by points: ternaries 9 (14 pts), if/else 5 (6 pts) (nesting depth added 6). Most of this is not in the body itself: 4 of the 20 points are its own statements and the rest belongs to 2 function items inside it that branch (getContent, getHeading). 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.
email-manager.sendAddGuestsEmailsAndSMS (cognitive 20) packages/emails/email-manager.ts:693— email-manager.sendAddGuestsEmailsAndSMS has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (16 pts), loops 2 (4 pts) (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
autoLock.handleAutoLock (cognitive 20) REDACTED:33— autoLock.handleAutoLock has cognitive complexity 20 (threshold 15). Drivers by points: ternaries 4 (8 pts), if/else 4 (7 pts), boolean chains 3, error handling 1 (2 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
OrganizationBlockingService.areBlocked (cognitive 20) packages/features/watchlist/lib/service/OrganizationBlockingService.ts:66— OrganizationBlockingService.areBlocked has cognitive complexity 20 (threshold 15). Drivers by points: if/else 6 (11 pts), loops 5 (7 pts), boolean chains 2 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
BaseCalendarService.updateEvent (cognitive 20) packages/lib/CalendarService.ts:506— BaseCalendarService.updateEvent has cognitive complexity 20 (threshold 15). Drivers by points: ternaries 8 (15 pts), if/else 3, boolean chains 1, error handling 1 (nesting depth added 7). Most of this is not in the body itself: 7 of the 20 points are its own statements and the rest belongs to one function literal inside it that branches (line 559). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
useOAuthFlow.useOAuthFlow (cognitive 20) packages/platform/atoms/hooks/useOAuthFlow.ts:23— useOAuthFlow.useOAuthFlow has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (14 pts), boolean chains 5, ternaries 1 (nesting depth added 6). None of this is in the body itself: all 20 points belong to 5 function literals inside it that branch (lines 77, 39, 36, …). 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.
useTabsNavigations.useTabsNavigations.tabsNavigation (cognitive 20) packages/platform/atoms/event-types/hooks/useTabsNavigations.tsx:65— useTabsNavigations.useTabsNavigations.tabsNavigation has cognitive complexity 20 (threshold 15). Drivers by points: ternaries 5 (12 pts), if/else 4 (5 pts), boolean chains 3 (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.
setSMSLockState.handler.setSMSLockState (cognitive 20) packages/trpc/server/routers/viewer/admin/setSMSLockState.handler.ts:16— setSMSLockState.handler.setSMSLockState has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (12 pts), ternaries 4 (8 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
toggle.handler.toggleHandler (cognitive 20) packages/trpc/server/routers/viewer/apps/toggle.handler.ts:20— toggle.handler.toggleHandler has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (14 pts), boolean chains 6 (nesting depth added 7). Most of this is not in the body itself: 8 of the 20 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 79, 144). 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.
HintOrErrors.HintsOrErrors (cognitive 20) packages/ui/components/form/inputs/HintOrErrors.tsx:13— HintOrErrors.HintsOrErrors has cognitive complexity 20 (threshold 15). Drivers by points: ternaries 6 (12 pts), if/else 5, boolean chains 3 (nesting depth added 6). Most of this is not in the body itself: 7 of the 20 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 48, 100). 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.
route.postHandler (cognitive 19) apps/web/app/api/cron/changeTimeZone/route.ts:24— route.postHandler has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (15 pts), boolean chains 2, loops 2 (nesting depth added 7). Of this number, 18 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
FormBuilderField.getAndUpdateNormalizedValues (cognitive 19) REDACTED:194— FormBuilderField.getAndUpdateNormalizedValues has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (12 pts), boolean chains 7 (nesting depth added 5). Of this number, 17 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
EventTypeAppSettingsInterface.EventTypeAppSettingsInterface (cognitive 19) packages/app-store/stripepayment/components/EventTypeAppSettingsInterface.tsx:24— EventTypeAppSettingsInterface.EventTypeAppSettingsInterface has cognitive complexity 19 (threshold 15). Drivers by points: boolean chains 13, if/else 4 (6 pts) (nesting depth added 2). Of this number, 13 points are the body's own statements and 6 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.
get.handler (cognitive 19) packages/app-store/intercom/api/get.ts:5— get.handler has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (15 pts), error handling 1 (3 pts), boolean chains 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
embed.validate (cognitive 19) REDACTED:108— embed.validate has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (13 pts), boolean chains 5, loops 1 (nesting depth added 5). Of this number, 16 points are the body's own statements and 3 belong to 2 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.
loadAndValidateUsers._loadAndValidateUsers (cognitive 19) packages/features/bookings/lib/handleNewBooking/loadAndValidateUsers.ts:71— loadAndValidateUsers._loadAndValidateUsers has cognitive complexity 19 (threshold 15). Drivers by points: if/else 11 (12 pts), boolean chains 7 (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.
Memoize.Memoize (cognitive 19) packages/features/cache/decorators/Memoize.ts:15— Memoize.Memoize has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (9 pts), ternaries 2 (5 pts), error handling 2 (3 pts), boolean chains 2 (nesting depth added 7). None of this is in the body itself: all 19 points belong to 2 function literals inside it that branch (lines 27, 16). 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.
useShouldBeDisabledDueToPrefill.useShouldBeDisabledDueToPrefill (cognitive 19) packages/features/form-builder/useShouldBeDisabledDueToPrefill.tsx:45— useShouldBeDisabledDueToPrefill.useShouldBeDisabledDueToPrefill has cognitive complexity 19 (threshold 15). Drivers by points: if/else 10 (13 pts), boolean chains 6 (nesting depth added 3). Of this number, 16 points are the body's own statements and 3 belong to 2 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.
GlobalBlockingService.areBlocked (cognitive 19) packages/features/watchlist/lib/service/GlobalBlockingService.ts:67— GlobalBlockingService.areBlocked has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (11 pts), loops 5 (7 pts), boolean chains 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
BaseCalProvider.BaseCalProvider (cognitive 19) packages/platform/atoms/cal-provider/BaseCalProvider.tsx:54— BaseCalProvider.BaseCalProvider has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (11 pts), boolean chains 6, ternaries 2 (nesting depth added 3). Most of this is not in the body itself: 5 of the 19 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 119, 142, 84, …). 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.
StripePaymentForm.StripePaymentComponent (cognitive 19) packages/platform/atoms/event-types/payments/StripePaymentForm.tsx:8— StripePaymentForm.StripePaymentComponent has cognitive complexity 19 (threshold 15). Drivers by points: if/else 10 (15 pts), boolean chains 4 (nesting depth added 5). None of this is in the body itself: all 19 points belong to one function literal inside it that branches (line 28). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
BookingLimitsCountValidator.validate (cognitive 19) packages/platform/types/event-types/event-types_2024_06_14/inputs/booking-limits-count.input.ts:65— BookingLimitsCountValidator.validate has cognitive complexity 19 (threshold 15). Drivers by points: boolean chains 14, if/else 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.
BookingLimitsDurationValidator.validate (cognitive 19) packages/platform/types/event-types/event-types_2024_06_14/inputs/booking-limits-duration.input.ts:56— BookingLimitsDurationValidator.validate has cognitive complexity 19 (threshold 15). Drivers by points: boolean chains 14, if/else 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.
updateClient.handler.updateClientHandler (cognitive 19) packages/trpc/server/routers/viewer/oAuth/updateClient.handler.ts:15— updateClient.handler.updateClientHandler has cognitive complexity 19 (threshold 15). Drivers by points: if/else 12 (13 pts), boolean chains 6 (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.
QualifiedHostsService.findQualifiedHostsWithDelegationCredentials (cognitive 18) apps/api/v2/src/lib/services/qualified-hosts.service.ts:23— QualifiedHostsService.findQualifiedHostsWithDelegationCredentials has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (15 pts), loops 1 (2 pts), boolean chains 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
EventTypesAtomService.getPublicEventTypeForAtoms (cognitive 18) apps/api/v2/src/modules/atoms/services/event-types-atom.service.ts:363— EventTypesAtomService.getPublicEventTypeForAtoms has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (15 pts), boolean chains 1, error handling 1, ternaries 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AppleCalendarService.saveCalendarCredentials (cognitive 18) apps/api/v2/src/platform/calendars/services/apple-calendar.service.ts:62— AppleCalendarService.saveCalendarCredentials has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (11 pts), boolean chains 6, error handling 1 (nesting depth added 5). Of this number, 12 points are the body's own statements and 6 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.
Setup.MakeSetup (cognitive 18) apps/web/components/apps/make/Setup.tsx:17— Setup.MakeSetup has cognitive complexity 18 (threshold 15). Drivers by points: ternaries 5 (11 pts), if/else 3 (4 pts), boolean chains 3 (nesting depth added 7). Of this number, 9 points are the body's own statements and 9 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.
EnableTwoFactorModal.EnableTwoFactorModal (cognitive 18) apps/web/components/settings/EnableTwoFactorModal.tsx:56— EnableTwoFactorModal.EnableTwoFactorModal has cognitive complexity 18 (threshold 15). Drivers by points: if/else 10 (11 pts), boolean chains 3, error handling 2, ternaries 2 (nesting depth added 1). Most of this is not in the body itself: 5 of the 18 points are its own statements and the rest belongs to 3 function items inside it that branch (handleSetup, handleEnable, a function literal at line 161). 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.
app-providers.getThemeProviderProps (cognitive 18) apps/web/lib/app-providers.tsx:186— app-providers.getThemeProviderProps has cognitive complexity 18 (threshold 15). Drivers by points: ternaries 7 (11 pts), if/else 4 (5 pts), boolean chains 2 (nesting depth added 5). Of this number, 17 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
getServerSideProps.getServerSideProps (cognitive 18) apps/web/lib/apps/installation/[[...step]]/getServerSideProps.ts:496— getServerSideProps.getServerSideProps has cognitive complexity 18 (threshold 15). Drivers by points: if/else 10 (12 pts), boolean chains 5, error handling 1 (nesting depth added 2). Of this number, 17 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body: 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.
BookingHistory.BookingLogsTimeline (cognitive 18) apps/web/modules/booking-audit/components/BookingHistory.tsx:237— BookingHistory.BookingLogsTimeline has cognitive complexity 18 (threshold 15). Drivers by points: boolean chains 11, ternaries 4, if/else 3. Most of this is not in the body itself: 1 of the 18 points is its own statement and the rest belongs to 2 function literals inside it that branch (lines 271, 243). 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.
BookerWebWrapper.BookerWebWrapperComponent (cognitive 18) apps/web/modules/bookings/components/BookerWebWrapper.tsx:41— BookerWebWrapper.BookerWebWrapperComponent has cognitive complexity 18 (threshold 15). Drivers by points: ternaries 8, boolean chains 5, if/else 5. Of this number, 11 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.
usePaymentStatus.usePaymentStatus (cognitive 18) apps/web/modules/bookings/hooks/usePaymentStatus.ts:27— usePaymentStatus.usePaymentStatus has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (13 pts), boolean chains 5 (nesting depth added 5). None of this is in the body itself: all 18 points belong to one function literal inside it that branches (line 38). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
FormBuilder.VariantFields (cognitive 18) apps/web/modules/event-types/components/tabs/advanced/FormBuilder.tsx:955— FormBuilder.VariantFields has cognitive complexity 18 (threshold 15). Drivers by points: boolean chains 10, ternaries 4 (5 pts), if/else 3 (nesting depth added 1). Of this number, 9 points are the body's own statements and 9 belong to 2 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.
RequiresConfirmationController.RequiresConfirmationController (cognitive 18) apps/web/modules/event-types/components/tabs/advanced/RequiresConfirmationController.tsx:42— RequiresConfirmationController.RequiresConfirmationController has cognitive complexity 18 (threshold 15). Drivers by points: boolean chains 9, if/else 5, ternaries 3 (4 pts) (nesting depth added 1). None of this is in the body itself: all 18 points belong to 4 function literals inside it that branch (lines 86, 129, 110, …). 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.
personal-settings-view.PersonalSettingsView (cognitive 18) apps/web/modules/onboarding/personal/settings/personal-settings-view.tsx:29— personal-settings-view.PersonalSettingsView has cognitive complexity 18 (threshold 15). Drivers by points: boolean chains 14, if/else 4. Of this number, 12 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.
users-public-view.UserPage (cognitive 18) REDACTED:24— users-public-view.UserPage has cognitive complexity 18 (threshold 15). Drivers by points: boolean chains 11, ternaries 6, if/else 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.
DeleteForm.DeleteForm (cognitive 18) packages/app-store-cli/src/components/DeleteForm.tsx:9— DeleteForm.DeleteForm has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (10 pts), ternaries 4 (8 pts) (nesting depth added 5). Of this number, 13 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.
Office365CalendarService.translateEvent (cognitive 18) packages/app-store/office365calendar/lib/CalendarService.ts:485— Office365CalendarService.translateEvent has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (7 pts), ternaries 7, boolean chains 4 (nesting depth added 1). Of this number, 16 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, 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.
add.handler (cognitive 18) packages/app-store/caldavcalendar/api/add.ts:10— add.handler has cognitive complexity 18 (threshold 15). Drivers by points: if/else 4 (9 pts), ternaries 1 (5 pts), boolean chains 2, error handling 1 (2 pts) (nesting depth added 10). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
link.handleLinkStep (cognitive 18) packages/app-store/intercom/lib/configure/link.ts:16— link.handleLinkStep has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7, ternaries 7, boolean chains 4. Of this number, 14 points are the body's own statements and 4 belong to one function literal inside it that branches. To reduce it, split the body: 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.
Cal.getNextActionForModal (cognitive 18) REDACTED:573— Cal.getNextActionForModal has cognitive complexity 18 (threshold 15). Drivers by points: boolean chains 8, if/else 7, ternaries 3. 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 (getActionToTake, a function literal at line 690, isSameEmbedConfig). 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 18) packages/features/bookings/components/Header.tsx:22— Header.Header has cognitive complexity 18 (threshold 15). Drivers by points: ternaries 7 (8 pts), boolean chains 7, if/else 3 (nesting depth added 1). Of this number, 10 points are the body's own statements and 8 belong to 6 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.
BookingRepository.buildWhereClauseForActiveBookings (cognitive 18) packages/features/bookings/repositories/BookingRepository.ts:111— BookingRepository.buildWhereClauseForActiveBookings has cognitive complexity 18 (threshold 15). Drivers by points: ternaries 8 (17 pts), boolean chains 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
getBookingResponsesSchema.preprocessField (cognitive 18) packages/features/bookings/lib/getBookingResponsesSchema.ts:31— getBookingResponsesSchema.preprocessField has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (8 pts), boolean chains 4, ternaries 2 (4 pts), error handling 1 (2 pts) (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
computeEffectiveState.computeEffectiveStateAcrossTeams (cognitive 18) packages/features/feature-opt-in/lib/computeEffectiveState.ts:36— computeEffectiveState.computeEffectiveStateAcrossTeams has cognitive complexity 18 (threshold 15). Drivers by points: if/else 10 (14 pts), boolean chains 4 (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.
connectAndJoin.handler.Handler (cognitive 18) packages/trpc/server/routers/loggedInViewer/connectAndJoin.handler.ts:27— connectAndJoin.handler.Handler has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7, boolean chains 6, ternaries 4 (5 pts) (nesting depth added 1). Of this number, 17 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body: 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.
deleteMe.handler.deleteMeHandler (cognitive 18) packages/trpc/server/routers/viewer/me/deleteMe.handler.ts:21— deleteMe.handler.deleteMeHandler has cognitive complexity 18 (threshold 15). Drivers by points: if/else 12 (17 pts), boolean chains 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MultiOptionInput.MultiOptionInput (cognitive 18) packages/ui/components/form/inputs/MultiOptionInput.tsx:81— MultiOptionInput.MultiOptionInput has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (8 pts), boolean chains 5, ternaries 3 (5 pts) (nesting depth added 3). Most of this is not in the body itself: 2 of the 18 points are its own statements and the rest belongs to 6 function items inside it that branch (a function literal at line 206, a function literal at line 135, handlePasteInOptionAtIndex, …). 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.
DateRangePicker.DatePickerWithRange (cognitive 18) packages/ui/components/form/date-range-picker/DateRangePicker.tsx:26— DateRangePicker.DatePickerWithRange has cognitive complexity 18 (threshold 15). Drivers by points: ternaries 6 (7 pts), if/else 6, boolean chains 5 (nesting depth added 1). Of this number, 10 points are the body's own statements and 8 belong to 3 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.
seed-utils.createUserAndEventType (cognitive 18) REDACTED:12— seed-utils.createUserAndEventType has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (10 pts), loops 3 (5 pts), boolean chains 2, ternaries 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
seed-utils.seedAttributes (cognitive 18) REDACTED:290— seed-utils.seedAttributes has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (7 pts), loops 3 (7 pts), boolean chains 2, ternaries 1 (2 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ErrorsBookingsService_2024_08_13.handleBookingError (cognitive 17) apps/api/v2/src/platform/bookings/2024-08-13/services/errors.service.ts:34— ErrorsBookingsService_2024_08_13.handleBookingError has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (14 pts), ternaries 1 (3 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PaymentPage.PaymentPage (cognitive 17) apps/web/app/(use-page-wrapper)/payment/[uid]/PaymentPage.tsx:63— PaymentPage.PaymentPage has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 10, ternaries 4, if/else 2 (3 pts) (nesting depth added 1). Of this number, 13 points are the body's own statements and 4 belong to 2 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.
route.postHandler (cognitive 17) apps/web/app/api/cron/bookingReminder/route.ts:16— route.postHandler has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 7, if/else 2 (4 pts), loops 2 (3 pts), ternaries 1 (3 pts) (nesting depth added 5). Of this number, 15 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.
bookingActions.getActionLabel (cognitive 17) apps/web/components/booking/actions/bookingActions.ts:280— bookingActions.getActionLabel has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 5 (10 pts), boolean chains 6, match/switch 1 (nesting depth added 5). 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.
getServerSideProps.getUserPageProps (cognitive 17) apps/web/lib/d/[link]/[slug]/getServerSideProps.tsx:22— getServerSideProps.getUserPageProps has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (11 pts), ternaries 2 (3 pts), boolean chains 2, 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.
EventList.EventList (cognitive 17) apps/web/modules/calendars/weeklyview/components/event/EventList.tsx:16— EventList.EventList has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 6, if/else 6, ternaries 5. Most of this is not in the body itself: 1 of the 17 points is its own statement and the rest belongs to 6 function literals inside it that branch (lines 93, 30, 46, …). 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.
holidays-view.HolidaysView (cognitive 17) apps/web/modules/settings/my-account/holidays-view.tsx:171— holidays-view.HolidaysView 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, 14 points are the body's own statements and 3 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.
NavigationItem.MobileNavigationMoreItem (cognitive 17) apps/web/modules/shell/navigation/NavigationItem.tsx:305— NavigationItem.MobileNavigationMoreItem has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 6 (10 pts), boolean chains 6, if/else 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.
UserDropdown.UserDropdown (cognitive 17) apps/web/modules/shell/user-dropdown/UserDropdown.tsx:51— UserDropdown.UserDropdown has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (8 pts), ternaries 5, boolean chains 4 (nesting depth added 1). Most of this is not in the body itself: 8 of the 17 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 93, 55, 58, …). 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.
EventTypeAppSettingsInterface.EventTypeAppSettingsInterface (cognitive 17) packages/app-store/paypal/components/EventTypeAppSettingsInterface.tsx:22— EventTypeAppSettingsInterface.EventTypeAppSettingsInterface has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (10 pts), boolean chains 4, ternaries 3 (nesting depth added 2). 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 literals inside it that branch (lines 45, 79, 99, …). 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.
OAuthManager.refreshOAuthToken (cognitive 17) packages/app-store/_utils/oauth/OAuthManager.ts:472— OAuthManager.refreshOAuthToken has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (10 pts), error handling 2 (4 pts), boolean chains 3 (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
GoogleCalendarService.fetchBusyEventsWithTitles (cognitive 17) packages/app-store/googlecalendar/lib/CalendarService.ts:733— GoogleCalendarService.fetchBusyEventsWithTitles has cognitive complexity 17 (threshold 15). Drivers by points: if/else 3 (9 pts), loops 2 (3 pts), ternaries 1 (3 pts), boolean chains 2 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
StripePaymentService.chargeCard (cognitive 17) packages/app-store/stripepayment/lib/PaymentService.ts:227— StripePaymentService.chargeCard has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (12 pts), loops 1 (3 pts), boolean chains 1, 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.
getEnabledAppsFromCredentials.getEnabledAppsFromCredentials (cognitive 17) packages/app-store/_utils/getEnabledAppsFromCredentials.ts:18— getEnabledAppsFromCredentials.getEnabledAppsFromCredentials has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (12 pts), boolean chains 3, loops 1 (2 pts) (nesting depth added 7). Of this number, 15 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.
deleteRecordings.deleteRecording (cognitive 17) packages/app-store/dailyvideo/lib/scripts/deleteRecordings.ts:243— deleteRecordings.deleteRecording has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (12 pts), boolean chains 2, error handling 1 (2 pts), loops 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.
embed-iframe.main (cognitive 17) REDACTED:522— embed-iframe.main has cognitive complexity 17 (threshold 15). Drivers by points: if/else 10, boolean chains 6, ternaries 1. Most of this is not in the body itself: 7 of the 17 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 570, 559, 593, …). 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.
handleSeats.handleSeats (cognitive 17) packages/features/bookings/lib/handleSeats/handleSeats.ts:13— handleSeats.handleSeats has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7, boolean chains 6, ternaries 2 (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, 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.
handleNoShowFee.handleNoShowFee (cognitive 17) packages/features/bookings/lib/payment/handleNoShowFee.ts:19— handleNoShowFee.handleNoShowFee has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (7 pts), ternaries 3 (5 pts), boolean chains 4, error handling 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.
GoogleCalendarSubscriptionAdapter.parseEvents (cognitive 17) packages/features/calendar-subscription/adapters/GoogleCalendarSubscription.adapter.ts:154— GoogleCalendarSubscriptionAdapter.parseEvents has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 9 (12 pts), boolean chains 5 (nesting depth added 3). None of this is in the body itself: all 17 points belong to 3 function items inside it that branch (a function literal at line 170, filterEventsByDateRange, filterEventsWithoutId). 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.
DatePicker.Day (cognitive 17) packages/features/calendars/components/DatePicker.tsx:56— DatePicker.Day has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 6 (11 pts), boolean chains 6 (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.
RecurringEventController.RecurringEventController (cognitive 17) packages/features/eventtypes/components/tabs/recurring/RecurringEventController.tsx:39— RecurringEventController.RecurringEventController has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 7, ternaries 4 (7 pts), if/else 2 (3 pts) (nesting depth added 4). Of this number, 12 points are the body's own statements and 5 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.
date-ranges.subtract (cognitive 17) packages/features/schedules/lib/date-ranges.ts:423— date-ranges.subtract has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (14 pts), loops 2 (3 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
defaultResponder.defaultResponder (cognitive 17) packages/lib/server/defaultResponder.ts:20— defaultResponder.defaultResponder has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (8 pts), boolean chains 6, ternaries 2, error handling 1 (nesting depth added 2). None of this is in the body itself: all 17 points belong to one function literal inside it that branches (line 25). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
ssrfProtection.validateUrlCore (cognitive 17) packages/lib/ssrfProtection.ts:108— ssrfProtection.validateUrlCore has cognitive complexity 17 (threshold 15). Drivers by points: if/else 11 (13 pts), boolean chains 3, error handling 1 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
useEventTypeForm.useEventTypeForm.defaultValues (cognitive 17) packages/platform/atoms/event-types/hooks/useEventTypeForm.ts:42— useEventTypeForm.useEventTypeForm.defaultValues 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.
BookingsService_2024_08_13.getBooking (cognitive 16) apps/api/v2/src/platform/bookings/2024-08-13/services/bookings.service.ts:554— BookingsService_2024_08_13.getBooking has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (9 pts), boolean chains 6, 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.
InputBookingsService_2024_08_13.transformLocation (cognitive 16) apps/api/v2/src/platform/bookings/2024-08-13/services/input.service.ts:282— InputBookingsService_2024_08_13.transformLocation has cognitive complexity 16 (threshold 15). Drivers by points: if/else 12 (15 pts), boolean chains 1 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
InputBookingsService_2024_08_13.transformInputCreateRecurringBooking (cognitive 16) apps/api/v2/src/platform/bookings/2024-08-13/services/input.service.ts:422— InputBookingsService_2024_08_13.transformInputCreateRecurringBooking has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 8, ternaries 3, if/else 2, match/switch 1 (2 pts), loops 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.
InputEventTypesService_2024_06_14.transformInputUpdateEventType (cognitive 16) apps/api/v2/src/platform/event-types/event-types_2024_06_14/services/input-event-types.service.ts:209— InputEventTypesService_2024_06_14.transformInputUpdateEventType has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 16. 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.
locations.transformLocationsInternalToApi (cognitive 16) apps/api/v2/src/platform/event-types/event-types_2024_06_14/transformers/internal-to-api/locations.ts:49— locations.transformLocationsInternalToApi has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (13 pts), match/switch 1 (2 pts), loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Setup.SendgridSetup (cognitive 16) apps/web/components/apps/sendgrid/Setup.tsx:18— Setup.SendgridSetup has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 7 (10 pts), if/else 6 (nesting depth added 3). Of this number, 10 points are the body's own statements and 6 belong to 3 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, 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.
verify-email.handler (cognitive 16) apps/web/lib/pages/auth/verify-email.ts:28— verify-email.handler has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (13 pts), boolean chains 2, ternaries 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
BookingReportDetailsModal.BookingReportDetailsModal (cognitive 16) apps/web/modules/blocklist/components/BookingReportDetailsModal.tsx:30— BookingReportDetailsModal.BookingReportDetailsModal has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 11, if/else 4, ternaries 1. Of this number, 12 points are the body's own statements and 4 belong to 4 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.
Occurences.EventOccurences (cognitive 16) apps/web/modules/bookings/components/event-meta/Occurences.tsx:16— Occurences.EventOccurences has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 9, if/else 7. Of this number, 9 points are the body's own statements and 7 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.
useBookingListData.useBookingListData (cognitive 16) apps/web/modules/bookings/hooks/useBookingListData.ts:19— useBookingListData.useBookingListData has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (11 pts), boolean chains 3, loops 1, ternaries 1 (nesting depth added 3). None of this is in the body itself: all 16 points belong to 6 function literals inside it that branch (lines 53, 31, 109, …). 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.
connect-and-join-view.ConnectAndJoin (cognitive 16) apps/web/modules/connect-and-join/connect-and-join-view.tsx:19— connect-and-join-view.ConnectAndJoin has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6, ternaries 3 (6 pts), boolean chains 4 (nesting depth added 3). Of this number, 10 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.
DataTableWrapper.DataTableWrapper (cognitive 16) apps/web/modules/data-table/components/DataTableWrapper.tsx:47— DataTableWrapper.DataTableWrapper has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 10, if/else 3, ternaries 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.
EventTypeWebWrapper.EventTypeWeb (cognitive 16) apps/web/modules/event-types/components/EventTypeWebWrapper.tsx:105— EventTypeWebWrapper.EventTypeWeb has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8, boolean chains 4, ternaries 4. Most of this is not in the body itself: 4 of the 16 points are its own statements and the rest belongs to 5 function literals inside it that branch (lines 150, 128, 312, …). 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.
LargeCalendar.LargeCalendar (cognitive 16) apps/web/modules/troubleshooter/components/LargeCalendar.tsx:13— LargeCalendar.LargeCalendar has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 6, if/else 4 (6 pts), ternaries 4 (nesting depth added 2). Most of this is not in the body itself: 6 of the 16 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 69, 58, 88). 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.
CreateNewWebhookButton.CreateNewWebhookButton (cognitive 16) apps/web/modules/webhooks/components/CreateNewWebhookButton.tsx:21— CreateNewWebhookButton.CreateNewWebhookButton has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 6 (8 pts), boolean chains 4, if/else 4 (nesting depth added 2). Most of this is not in the body itself: 6 of the 16 points are its own statements and the rest belongs to 4 function items inside it that branch (handleSelect, a function literal at line 74, a function literal at line 37, …). 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.
WebhookListItem.WebhookListItem (cognitive 16) apps/web/modules/webhooks/components/WebhookListItem.tsx:45— WebhookListItem.WebhookListItem has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 10, ternaries 3 (4 pts), if/else 2 (nesting depth added 1). 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.
getServerSideProps.getUserPageProps (cognitive 16) apps/web/server/lib/[user]/[type]/getServerSideProps.ts:212— getServerSideProps.getUserPageProps has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (9 pts), ternaries 6 (7 pts) (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
webhook.handler (cognitive 16) packages/app-store/btcpayserver/api/webhook.ts:44— webhook.handler has cognitive complexity 16 (threshold 15). Drivers by points: if/else 11, boolean chains 2, ternaries 1 (2 pts), error handling 1 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
ManageLink.ManageLink (cognitive 16) packages/emails/src/components/ManageLink.tsx:4— ManageLink.ManageLink has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 15, if/else 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.
email-manager.sendRoundRobinRescheduledEmailsAndSMS (cognitive 16) packages/emails/email-manager.ts:165— email-manager.sendRoundRobinRescheduledEmailsAndSMS has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (13 pts), boolean chains 2, loops 1 (nesting depth added 8). 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, 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.
CalApi.preload (cognitive 16) REDACTED:1353— CalApi.preload has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (9 pts), boolean chains 4, ternaries 1 (3 pts) (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.
get-booking.getBookingForReschedule (cognitive 16) packages/features/bookings/lib/get-booking.ts:126— get-booking.getBookingForReschedule has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (9 pts), boolean chains 4, ternaries 2 (3 pts) (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.
useInitialFormValues.useInitialFormValues (cognitive 16) packages/features/bookings/Booker/hooks/useInitialFormValues.ts:55— useInitialFormValues.useInitialFormValues has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 6, if/else 6, ternaries 4. None of this is in the body itself: all 16 points belong to 3 function literals inside it that branch (lines 88, 118, 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.
EventManager.updateLocation (cognitive 16) packages/features/bookings/lib/EventManager.ts:418— EventManager.updateLocation has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (11 pts), ternaries 3, boolean chains 2 (nesting depth added 4). Of this number, 11 points are the body's own statements and 5 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
getBookingFields.ensureBookingInputsHaveSystemFields (cognitive 16) packages/features/bookings/lib/getBookingFields.ts:62— getBookingFields.ensureBookingInputsHaveSystemFields has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (7 pts), boolean chains 5, loops 2, ternaries 1 (2 pts) (nesting depth added 3). Of this number, 11 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.
createNewSeat.createNewSeat (cognitive 16) packages/features/bookings/lib/handleSeats/create/createNewSeat.ts:116— createNewSeat.createNewSeat has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (9 pts), ternaries 2 (4 pts), boolean chains 3 (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.
moveSeatedBookingToNewTimeSlot.moveSeatedBookingToNewTimeSlot (cognitive 16) packages/features/bookings/lib/handleSeats/reschedule/owner/moveSeatedBookingToNewTimeSlot.ts:45— moveSeatedBookingToNewTimeSlot.moveSeatedBookingToNewTimeSlot has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (8 pts), ternaries 2 (5 pts), boolean chains 3 (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.
BookingAccessService.doesUserIdHaveAccessToBooking (cognitive 16) packages/features/bookings/services/BookingAccessService.ts:56— BookingAccessService.doesUserIdHaveAccessToBooking has cognitive complexity 16 (threshold 15). Drivers by points: if/else 10 (12 pts), ternaries 2 (3 pts), loops 1 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
getCalendarsEvents.getCalendarsEvents (cognitive 16) packages/features/calendars/lib/getCalendarsEvents.ts:91— getCalendarsEvents.getCalendarsEvents has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 4 (7 pts), if/else 5 (6 pts), boolean chains 2, error handling 1 (nesting depth added 4). None of this is in the body itself: all 16 points belong to 3 function literals inside it that branch (lines 139, 104, 154). 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.
EventTypeRepository.getEventTypeList (cognitive 16) packages/features/eventtypes/repositories/eventTypeRepository.ts:1746— EventTypeRepository.getEventTypeList has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (10 pts), boolean chains 6 (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.
CloseComeUtils.getCustomFieldsIds (cognitive 16) packages/lib/CloseComeUtils.ts:90— CloseComeUtils.getCustomFieldsIds has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (13 pts), boolean chains 2, ternaries 1 (nesting depth added 4). Most of this is not in the body itself: 3 of the 16 points are its own statements and the rest belongs to one function literal inside it that branches (line 112). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
availability.getWorkingHours (cognitive 16) packages/lib/availability.ts:61— availability.getWorkingHours has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (12 pts), boolean chains 2, ternaries 1 (2 pts) (nesting depth added 4). Most of this is not in the body itself: 1 of the 16 points is its own statement and the rest belongs to 2 function literals inside it that branch (lines 75, 104). 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.
ConferencingAppsViewPlatformWrapper.ConferencingAppsViewPlatformWrapper (cognitive 16) packages/platform/atoms/connect/conferencing-apps/ConferencingAppsViewPlatformWrapper.tsx:89— ConferencingAppsViewPlatformWrapper.ConferencingAppsViewPlatformWrapper has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 8, ternaries 3 (6 pts), if/else 2 (nesting depth added 3). 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 (AddConferencingButtonPlatform, showToast, handleRemoveApp, …). 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.
bookingScenario.addHostsToDb (cognitive 16) REDACTED:316— bookingScenario.addHostsToDb has cognitive complexity 16 (threshold 15). Drivers by points: if/else 3 (7 pts), ternaries 2 (6 pts), loops 2 (3 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D23 · Boundary Type-Coupling· Cross-context type Status (types → v2) · ×1
Cross-context type Status (types → v2) apps/api/v2/src/platform/bookings/2024-04-15/outputs/get-bookings.output.ts:222— Status (context types) is exposed in v2's public surface via GetBookingsDataEntry.status — couples the contexts.
Cross-context type BookingInputLocation_2024_08_13 (types → v2) apps/api/v2/src/platform/bookings/2024-08-13/services/input.service.ts:282— BookingInputLocation_2024_08_13 (context types) is exposed in v2's public surface via InputBookingsService_2024_08_13.transformLocation — couples the contexts.
Cross-context type UpdateBookingInputLocation_2024_08_13 (types → v2) apps/api/v2/src/platform/bookings/2024-08-13/services/input.service.ts:282— UpdateBookingInputLocation_2024_08_13 (context types) is exposed in v2's public surface via InputBookingsService_2024_08_13.transformLocation — couples the contexts.
Cross-context type InputBookingField_2024_06_14 (types → v2) apps/api/v2/src/platform/event-types/event-types_2024_06_14/services/input-event-types.service.ts:304— InputBookingField_2024_06_14 (context types) is exposed in v2's public surface via InputEventTypesService_2024_06_14.getBookingFieldsWithGuestsToggled — couples the contexts.
Cross-context type OutputBookingField_2024_06_14 (types → v2) apps/api/v2/src/platform/event-types/event-types_2024_06_14/transformers/internal-to-api/booking-fields.ts:29— OutputBookingField_2024_06_14 (context types) is exposed in v2's public surface via booking-fields.transformBookingFieldsInternalToApi — couples the contexts.
Cross-context type BookingWindow_2024_06_14 (types → v2) apps/api/v2/src/platform/event-types/event-types_2024_06_14/transformers/internal-to-api/future-booking-limits.ts:14— BookingWindow_2024_06_14 (context types) is exposed in v2's public surface via future-booking-limits.transformFutureBookingLimitsInternalToApi — couples the contexts.
Cross-context type ConfirmationPolicy_2024_06_14 (types → v2) apps/api/v2/src/platform/event-types/event-types_2024_06_14/transformers/internal-to-api/requires-confirmation.ts:4— ConfirmationPolicy_2024_06_14 (context types) is exposed in v2's public surface via requires-confirmation.transformRequiresConfirmationInternalToApi — couples the contexts.
Cross-context type InputLocation_2024_06_14 (types → v2) apps/api/v2/src/platform/event-types/event-types_2024_06_14/transformers/api-to-internal/locations.ts:81— InputLocation_2024_06_14 (context types) is exposed in v2's public surface via locations.transformLocationsApiToInternal — couples the contexts.
Cross-context type InputTeamLocation_2024_06_14 (types → v2) apps/api/v2/src/platform/event-types/event-types_2024_06_14/transformers/api-to-internal/locations.ts:85— InputTeamLocation_2024_06_14 (context types) is exposed in v2's public surface via locations.transformTeamLocationsApiToInternal — couples the contexts.
Cross-context type DataTableRow (features → web) apps/web/modules/bookings/types.ts:35— DataTableRow (context features) is exposed in web's public surface via RowData.RowData — couples the contexts.
Cross-context type CombinedFilterSegment (features → web) apps/web/modules/data-table/components/segment/DuplicateSegmentDialog.tsx:17— CombinedFilterSegment (context features) is exposed in web's public surface via DuplicateSegmentDialog.DuplicateSegmentDialog — couples the contexts.
Cross-context type SegmentIdentifier (features → web) apps/web/modules/data-table/hooks/useSegments.ts:15— SegmentIdentifier (context features) is exposed in web's public surface via useSegments.useSegments.setPreference — couples the contexts.
Cross-context type EventLocationType (app-store → web) apps/web/modules/event-types/components/locations/LocationInput.tsx:12— EventLocationType (context app-store) is exposed in web's public surface via LocationInput.LocationInput — couples the contexts.
Cross-context type BookingStatus (trpc → app-store) packages/app-store/locations.ts:467— BookingStatus (context trpc) is exposed in app-store's public surface via locations.getSuccessPageLocationMessage — couples the contexts.
Cross-context type UserType (features → app-store) packages/app-store/_utils/stripe.ts:34— UserType (context features) is exposed in app-store's public surface via stripe.getStripeCustomerId — couples the contexts.
Cross-context type JsonValue (atoms → salesforce) packages/app-store/salesforce/lib/eventTypeService.ts:23— JsonValue (context atoms) is exposed in salesforce's public surface via EventTypeService.getEventTypeAppDataFromMetadata — couples the contexts.
Cross-context type EventLocationType (app-store → features) packages/features/apps/components/AppSetDefaultLinkDialog.tsx:28— EventLocationType (context app-store) is exposed in features's public surface via AppSetDefaultLinkDialog.AppSetDefaultLinkDialog — couples the contexts.
Cross-context type CancelBookingInput (types → features) packages/features/bookings/lib/handleCancelBooking.ts:81— CancelBookingInput (context types) is exposed in features's public surface via handleCancelBooking.handler — couples the contexts.
Cross-context type JsonValue (atoms → lib) packages/lib/server/serviceAccountKey.ts:38— JsonValue (context atoms) is exposed in lib's public surface via serviceAccountKey.decryptServiceAccountKey — couples the contexts.
Cross-context type NoticeThresholdUnitEnum (enums → types) packages/platform/types/event-types/event-types_2024_06_14/inputs/confirmation-policy.input.ts:13— NoticeThresholdUnitEnum (context enums) is exposed in types's public surface via NoticeThreshold_2024_06_14.unit — couples the contexts.
Cross-context type ConfirmationPolicyEnum (enums → types) packages/platform/types/event-types/event-types_2024_06_14/inputs/confirmation-policy.input.ts:30— ConfirmationPolicyEnum (context enums) is exposed in types's public surface via BaseConfirmationPolicy_2024_06_14.type — couples the contexts.
Cross-context type FrequencyInput (enums → types) packages/platform/types/event-types/event-types_2024_06_14/inputs/recurrence.input.ts:21— FrequencyInput (context enums) is exposed in types's public surface via Recurrence_2024_06_14.frequency — couples the contexts.
Cross-context type WeekDay (v2 → types) packages/platform/types/schedules/schedules-2024-06-11/inputs/create-schedule.input.ts:19— WeekDay (context v2) is exposed in types's public surface via ScheduleAvailabilityInput_2024_06_11.days — couples the contexts.
Cross-context type Action (atoms → ui) packages/ui/components/card/FormCard.tsx:93— Action (context atoms) is exposed in ui's public surface via FormCard.FormCard — couples the contexts.
IC1 · Incompleteness & stubs· Markup wires an event to an empty handler · ×1
Markup wires an event to an empty handler apps/web/modules/feature-flags/components/AssignFeatureSheet.tsx:176— `onCheckedChange` 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.
No DR/backup evidence — A persistence guard (data volume / purge-protection) was found, but no backup, geo-recovery or RTO/RPO controls were evidenced — a volume that survives a container recreate is not a tested restore from catastrophic loss.
Duplication concentrated across 83 sibling directories (167 clone groups) packages/app-store/_components/crm/WriteToObjectSettings.tsx:4— 167 duplicated blocks under packages/app-store/ have copies in at least two of the sibling directories _components, _lib, _utils, alby, applecalendar, attio (+77 more sibling(s) not listed) — 139 of them are reported below, and 28 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 167 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 167 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 167 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
Duplication concentrated across 3 sibling directories (114 clone groups) apps/api/v2/src/modules/atoms/services/event-types-atom.service.ts:196— 114 duplicated blocks under the repository root have copies in at least two of the sibling directories apps, packages, scripts — 69 of them are reported below, and 45 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 114 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 114 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 114 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
Duplication concentrated across 10 sibling directories (80 clone groups) packages/features/calendars/components/DestinationCalendarSelector.tsx:156— 80 duplicated blocks under packages/ have copies in at least two of the sibling directories app-store, emails, embeds, features, lib, platform (+4 more sibling(s) not listed) — 48 of them are reported below, and 32 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 80 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 80 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 80 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
Duplication concentrated across 24 sibling directories (62 clone groups) packages/features/bookingReference/repositories/BookingReferenceRepository.integration-test.ts:29— 62 duplicated blocks under packages/features/ have copies in at least two of the sibling directories availability, booking-audit, bookingReference, bookings, busyTimes, calendars (+18 more sibling(s) not listed) — 17 of them are reported below, and 45 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 62 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 62 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 62 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
Duplication concentrated across 4 sibling directories (47 clone groups) apps/api/v2/src/modules/teams/event-types/services/output-team-event-types.service.ts:26— 47 duplicated blocks under apps/api/v2/src/ have copies in at least two of the sibling directories lib, middleware, modules, platform — 19 of them are reported below, and 28 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 47 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 47 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 47 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
Duplication concentrated across 17 sibling directories (35 clone groups) apps/api/v2/src/modules/destination-calendars/outputs/destination-calendars.output.ts:7— 35 duplicated blocks under apps/api/v2/src/modules/ have copies in at least two of the sibling directories api-keys, atoms, auth, cal-unified-calendars, conferencing, deployments (+11 more sibling(s) not listed) — 18 of them are reported below, and 17 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 35 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 35 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 35 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
Duplication concentrated across 21 sibling directories (26 clone groups) packages/trpc/server/routers/viewer/apps/_router.tsx:51— 26 duplicated blocks under packages/trpc/server/routers/viewer/ have copies in at least two of the sibling directories admin, apiKeys, apps, auth, availability, bookings (+15 more sibling(s) not listed) — 13 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 26 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 26 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 26 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
Duplication concentrated across 7 sibling directories (24 clone groups) apps/api/v2/src/platform/bookings/2024-04-15/outputs/get-bookings.output.ts:30— 24 duplicated blocks under apps/api/v2/src/platform/ have copies in at least two of the sibling directories bookings, calendars, event-types, event-types-private-links, gcal, me (+1 more sibling(s) not listed) — 11 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 24 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 24 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 24 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
Duplication concentrated across 14 sibling directories (24 clone groups) apps/web/modules/settings/my-account/general-view.tsx:85— 24 duplicated blocks under apps/web/modules/ have copies in at least two of the sibling directories apps, auth, blocklist, bookings, calendar-view, data-table (+8 more sibling(s) not listed) — 15 of them are reported below, and 9 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 24 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 24 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 24 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
Duplication concentrated across 4 sibling directories (22 clone groups) apps/web/components/getting-started/steps-views/UserProfile.tsx:130— 22 duplicated blocks under apps/web/ have copies in at least two of the sibling directories app, components, lib, modules — 15 of them are reported below, and 7 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 22 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 22 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 22 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
Duplication concentrated across 5 sibling directories (15 clone groups) packages/platform/atoms/connect/conferencing-apps/hooks/useConnect.ts:32— 15 duplicated blocks under packages/platform/atoms/ have copies in at least two of the sibling directories availability, connect, event-types, hooks, list-schedules — 11 of them are reported below, and 4 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 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.
Duplication concentrated across 11 sibling directories (14 clone groups) apps/web/app/(use-page-wrapper)/availability/[schedule]/page.tsx:10— 14 duplicated blocks under apps/web/app/(use-page-wrapper)/ have copies in at least two of the sibling directories (main-nav), apps, auth, availability, event-types, getting-started (+5 more sibling(s) not listed) — 9 of them are reported below, and 5 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 14 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 14 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 14 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
Duplication concentrated across 11 sibling directories (13 clone groups) apps/web/components/apps/btcpayserver/Setup.tsx:33— 13 duplicated blocks under apps/web/components/apps/ have copies in at least two of the sibling directories alby, applecalendar, btcpayserver, caldavcalendar, exchange2013calendar, exchange2016calendar (+5 more sibling(s) not listed) — 11 of them are reported below, and 2 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 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.
Duplication concentrated across 5 sibling directories (10 clone groups) apps/api/v2/src/modules/auth/decorators/get-optional-user/get-optional-user.decorator.ts:7— 10 duplicated blocks under apps/api/v2/src/modules/auth/decorators/ have copies in at least two of the sibling directories get-membership, get-optional-user, get-org, get-team, get-user — 1 of them are reported below, and 9 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.
Duplication concentrated across 6 sibling directories (9 clone groups) packages/platform/atoms/hooks/calendars/useDeleteCalendarCredentials.ts:49— 9 duplicated blocks under packages/platform/atoms/hooks/ have copies in at least two of the sibling directories bookings, calendars, connect, organizations, schedules, stripe — 4 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 9 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 9 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 9 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
Duplication concentrated across 3 sibling directories (8 clone groups) packages/trpc/server/routers/loggedInViewer/_router.tsx:35— 8 duplicated blocks under packages/trpc/server/routers/ have copies in at least two of the sibling directories loggedInViewer, publicViewer, viewer — 2 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 8 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 8 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 8 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
Duplication concentrated across 6 sibling directories (7 clone groups) packages/features/webhooks/lib/dto/types.ts:220— 7 duplicated blocks under packages/features/webhooks/lib/ have copies in at least two of the sibling directories dto, factory, infrastructure, interface, service, types — 2 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 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.
Duplication concentrated across 2 sibling directories (7 clone groups) packages/platform/types/event-types/event-types_2024_06_14/inputs/locations.input.ts:244— 7 duplicated blocks under packages/platform/types/event-types/event-types_2024_06_14/ have copies in at least two of the sibling directories inputs, outputs — 4 of them are reported below, and 3 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 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.
Duplication concentrated across 4 sibling directories (5 clone groups) apps/web/modules/settings/admin/oauth-clients-admin-view.tsx:18— 5 duplicated blocks under apps/web/modules/settings/ have copies in at least two of the sibling directories admin, developer, my-account, oauth — 3 of them are reported below, and 2 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 5 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 5 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 5 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
Duplication concentrated across 3 sibling directories (5 clone groups) packages/platform/types/bookings/2024-08-13/inputs/location.input.ts:16— 5 duplicated blocks under packages/platform/types/ have copies in at least two of the sibling directories bookings, event-types, slots — 3 of them are reported below, and 2 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 5 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 5 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 5 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
R10 · Code Duplication· Duplicated block with local edits (411 matched lines × 2 locations) · ×1
Duplicated block with local edits (411 matched lines × 2 locations) packages/platform/types/event-types/event-types_2024_06_14/inputs/create-event-type.input.ts:209— packages/platform/types/event-types/event-types_2024_06_14/inputs/create-event-type.input.ts:209 · packages/platform/types/event-types/event-types_2024_06_14/inputs/update-event-type.input.ts:142 — the two spans are one implementation copied and then locally edited — 1969 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.
Wholesale file copy (306 identical lines × 2 files) packages/app-store/_components/crm/WriteToObjectSettings.tsx:4— packages/app-store/_components/crm/WriteToObjectSettings.tsx:4 · packages/app-store/salesforce/components/components/WriteToObjectSettings.tsx:4 — these 2 files are line-for-line copies of one another — 306 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.
Wholesale file copy (255 identical lines × 2 files) packages/app-store/feishucalendar/lib/CalendarService.ts:1— packages/app-store/feishucalendar/lib/CalendarService.ts:1 · packages/app-store/larkcalendar/lib/CalendarService.ts:1 — these 2 files are line-for-line copies of one another — 255 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 (195 matched lines × 2 locations) · ×1
Duplicated block with local edits (195 matched lines × 2 locations) packages/coss-ui/src/components/autocomplete.tsx:14— packages/coss-ui/src/components/autocomplete.tsx:14 · packages/coss-ui/src/components/combobox.tsx:57 — 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.
Duplicated block (178 lines × 2 locations) packages/features/eventtypes/repositories/eventTypeRepository.ts:541— packages/features/eventtypes/repositories/eventTypeRepository.ts:541 · packages/features/eventtypes/repositories/eventTypeRepository.ts:821 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication· Duplicated block with local edits (174 matched lines × 2 locations) · ×1
Duplicated block with local edits (174 matched lines × 2 locations) apps/web/components/apps/btcpayserver/Setup.tsx:33— apps/web/components/apps/btcpayserver/Setup.tsx:33 · apps/web/components/apps/hitpay/Setup.tsx:29 — the two spans are one implementation copied and then locally edited — 988 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 (167 lines × 2 locations) scripts/seed-performance-testing.ts:72— scripts/seed-performance-testing.ts:72 · REDACTED:732 — the 2 copies are spread across 2 files, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases.
R10 · Code Duplication· Duplicated block with local edits (149 matched lines × 2 locations) · ×1
Duplicated block with local edits (149 matched lines × 2 locations) apps/web/components/ui/UsernameAvailability/PremiumTextfield.tsx:31— apps/web/components/ui/UsernameAvailability/PremiumTextfield.tsx:31 · apps/web/components/ui/UsernameAvailability/UsernameTextfield.tsx:22 — the two spans are one implementation copied and then locally edited — 743 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 (147 matched lines × 2 locations) · ×1
Duplicated block with local edits (147 matched lines × 2 locations) packages/ui/components/image-uploader/BannerUploader.tsx:26— packages/ui/components/image-uploader/BannerUploader.tsx:26 · packages/ui/components/image-uploader/ImageUploader.tsx:28 — the two spans are one implementation copied and then locally edited — 816 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 (144 matched lines × 2 locations) · ×1
Duplicated block with local edits (144 matched lines × 2 locations) apps/web/components/apps/alby/AlbyPaymentComponent.tsx:16— apps/web/components/apps/alby/AlbyPaymentComponent.tsx:16 · apps/web/components/apps/btcpayserver/BtcpayPaymentComponent.tsx:14 — the two spans are one implementation copied and then locally edited — 798 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.
Wholesale file copy (140 identical lines × 2 files) packages/app-store/exchange2013calendar/lib/CalendarService.ts:21— packages/app-store/exchange2013calendar/lib/CalendarService.ts:21 · packages/app-store/exchange2016calendar/lib/CalendarService.ts:21 — these 2 files are line-for-line copies of one another — 140 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.
Wholesale file copy (130 identical lines × 2 files) packages/app-store/vital/lib/reschedule.ts:1— packages/app-store/vital/lib/reschedule.ts:1 · packages/app-store/wipemycalother/lib/reschedule.ts:1 — these 2 files are line-for-line copies of one another — 130 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.
Wholesale file copy (120 identical lines × 2 files) packages/app-store/btcpayserver/components/KeyInput.tsx:3— packages/app-store/btcpayserver/components/KeyInput.tsx:3 · packages/app-store/hitpay/components/KeyInput.tsx:3 — these 2 files are line-for-line copies of one another — 120 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.
Wholesale file copy (110 identical lines × 2 files) packages/app-store/feishucalendar/types/FeishuCalendar.ts:2— packages/app-store/feishucalendar/types/FeishuCalendar.ts:2 · packages/app-store/larkcalendar/types/LarkCalendar.ts:2 — these 2 files are line-for-line copies of one another — 110 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 (103 matched lines × 2 locations) · ×1
Duplicated block with local edits (103 matched lines × 2 locations) apps/web/modules/apps/components/ConferencingAppsViewWebWrapper.tsx:72— apps/web/modules/apps/components/ConferencingAppsViewWebWrapper.tsx:72 · apps/web/modules/apps/installed/[category]/installed-category-view.tsx:64 — the two spans are one implementation copied and then locally edited — 476 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 (100 matched lines × 2 locations) · ×1
Duplicated block with local edits (100 matched lines × 2 locations) packages/features/bookingReference/repositories/BookingReferenceRepository.integration-test.ts:29— packages/features/bookingReference/repositories/BookingReferenceRepository.integration-test.ts:29 · packages/features/credentials/handleDeleteCredential.integration-test.ts:69 — the two spans are one implementation copied and then locally edited — 504 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 (97 matched lines × 2 locations) · ×1
Duplicated block with local edits (97 matched lines × 2 locations) apps/api/v2/src/platform/event-types/event-types_2024_04_15/services/event-types.service.ts:58— apps/api/v2/src/platform/event-types/event-types_2024_04_15/services/event-types.service.ts:58 · apps/api/v2/src/platform/event-types/event-types_2024_06_14/services/event-types.service.ts:166 — the two spans are one implementation copied and then locally edited — 621 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.
Wholesale file copy (95 identical lines × 2 files) packages/app-store/feishucalendar/lib/AppAccessToken.ts:1— packages/app-store/feishucalendar/lib/AppAccessToken.ts:1 · packages/app-store/larkcalendar/lib/AppAccessToken.ts:1 — these 2 files are line-for-line copies of one another — 95 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.
Complex function handler (cyclomatic 313, cognitive 494) packages/features/bookings/lib/service/RegularBookingService.ts:486— handler has cyclomatic complexity 313 and cognitive complexity 494; 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.
Complex function Success (cyclomatic 169, cognitive 127) REDACTED:108— Success has cyclomatic complexity 169 and cognitive complexity 127; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function updateHandler (cyclomatic 105, cognitive 120) packages/trpc/server/routers/viewer/eventTypes/heavy/update.handler.ts:60— updateHandler has cyclomatic complexity 105 and cognitive complexity 120; 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.
Complex function handler (cyclomatic 71, cognitive 78) packages/features/bookings/lib/handleCancelBooking.ts:81— handler has cyclomatic complexity 71 and cognitive complexity 78; 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.
Complex function (anonymous) (cyclomatic 66, cognitive 53) apps/web/modules/bookings/components/Booker.tsx:91— (anonymous) has cyclomatic complexity 66 and cognitive complexity 53; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function _getAvailableSlots (cyclomatic 59, cognitive 80) REDACTED:897— _getAvailableSlots has cyclomatic complexity 59 and cognitive complexity 80; 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.
Complex function signIn (cyclomatic 58, cognitive 120) packages/features/auth/lib/next-auth-options.ts:788— signIn has cyclomatic complexity 58 and cognitive complexity 120; 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.
Complex function superRefineField (cyclomatic 54, cognitive 90) packages/features/bookings/lib/getBookingResponsesSchema.ts:88— superRefineField has cyclomatic complexity 54 and cognitive complexity 90; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function getPublicEvent (cyclomatic 51, cognitive 57) packages/features/eventtypes/lib/getPublicEvent.ts:284— getPublicEvent has cyclomatic complexity 51 and cognitive complexity 57; 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.
Complex function confirmHandler (cyclomatic 51, cognitive 54) packages/trpc/server/routers/viewer/bookings/confirm.handler.ts:51— confirmHandler has cyclomatic complexity 51 and cognitive complexity 54; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function updateProfileHandler (cyclomatic 50, cognitive 67) packages/trpc/server/routers/viewer/me/updateProfile.handler.ts:41— updateProfileHandler has cyclomatic complexity 50 and cognitive complexity 67; 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.
Complex function getServerSideProps (cyclomatic 49, cognitive 50) apps/web/modules/bookings/views/bookings-single-view.getServerSideProps.tsx:39— getServerSideProps has cyclomatic complexity 49 and cognitive complexity 50; 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.
Complex function BookingListItem (cyclomatic 49, cognitive 39) apps/web/components/booking/BookingListItem.tsx:130— BookingListItem has cyclomatic complexity 49 and cognitive complexity 39; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function outOfOfficeCreateOrUpdate (cyclomatic 48, cognitive 60) packages/trpc/server/routers/viewer/ooo/outOfOfficeCreateOrUpdate.handler.ts:27— outOfOfficeCreateOrUpdate has cyclomatic complexity 48 and cognitive complexity 60; 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.
Complex function _getUserAvailability (cyclomatic 47, cognitive 51) packages/features/availability/lib/getUserAvailability.ts:361— _getUserAvailability has cyclomatic complexity 47 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 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.
Complex function Signup (cyclomatic 47, cognitive 39) apps/web/modules/signup-view.tsx:192— Signup has cyclomatic complexity 47 and cognitive complexity 39; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function REDACTED (cyclomatic 46, cognitive 60) packages/features/auth/lib/next-auth-options.ts:418— REDACTED has cyclomatic complexity 46 and cognitive complexity 60; 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.
Complex function AppForm (cyclomatic 46, cognitive 54) packages/app-store-cli/src/components/AppCreateUpdateForm.tsx:14— AppForm has cyclomatic complexity 46 and cognitive complexity 54; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function BookerPlatformWrapperComponent (cyclomatic 45, cognitive 39) packages/platform/atoms/booker/BookerPlatformWrapper.tsx:50— BookerPlatformWrapperComponent has cyclomatic complexity 45 and cognitive complexity 39; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function _getBusyTimesFromLimitsForUsers (cyclomatic 43, cognitive 155) REDACTED:379— _getBusyTimesFromLimitsForUsers has cyclomatic complexity 43 and cognitive complexity 155; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R3 · Large Files· apps/api/v2/src/platform/event-types/event-types_2024_06_14/controllers/event-types.controller.e2e-spec.ts · ×1
apps/api/v2/src/platform/event-types/event-types_2024_06_14/controllers/event-types.controller.e2e-spec.ts: 2902 lines of code apps/api/v2/src/platform/event-types/event-types_2024_06_14/controllers/event-types.controller.e2e-spec.ts:1— apps/api/v2/src/platform/event-types/event-types_2024_06_14/controllers/event-types.controller.e2e-spec.ts has 2902 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· packages/features/bookings/lib/service/RegularBookingService.ts · ×1
packages/features/bookings/lib/service/RegularBookingService.ts: 2455 lines of code packages/features/bookings/lib/service/RegularBookingService.ts:1— packages/features/bookings/lib/service/RegularBookingService.ts has 2455 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: 2284 lines of code REDACTED:1— REDACTED has 2284 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· packages/features/bookings/repositories/BookingRepository.ts · ×1
packages/features/bookings/repositories/BookingRepository.ts: 2061 lines of code packages/features/bookings/repositories/BookingRepository.ts:1— packages/features/bookings/repositories/BookingRepository.ts has 2061 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· packages/features/eventtypes/repositories/eventTypeRepository.ts · ×1
packages/features/eventtypes/repositories/eventTypeRepository.ts: 1797 lines of code packages/features/eventtypes/repositories/eventTypeRepository.ts:1— packages/features/eventtypes/repositories/eventTypeRepository.ts has 1797 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· packages/app-store/salesforce/lib/CrmService.ts · ×1
packages/app-store/salesforce/lib/CrmService.ts: 1714 lines of code packages/app-store/salesforce/lib/CrmService.ts:1— packages/app-store/salesforce/lib/CrmService.ts has 1714 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: 1549 lines of code REDACTED:1— REDACTED has 1549 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: 1507 lines of code REDACTED:1— REDACTED has 1507 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/web/modules/event-types/components/tabs/advanced/EventAdvancedTab.tsx · ×1
apps/web/modules/event-types/components/tabs/advanced/EventAdvancedTab.tsx: 1476 lines of code apps/web/modules/event-types/components/tabs/advanced/EventAdvancedTab.tsx:1— apps/web/modules/event-types/components/tabs/advanced/EventAdvancedTab.tsx has 1476 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: 1412 lines of code REDACTED:1— REDACTED has 1412 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: 1320 lines of code REDACTED:1— REDACTED has 1320 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· packages/testing/src/lib/bookingScenario/expects.ts · ×1
packages/testing/src/lib/bookingScenario/expects.ts: 1276 lines of code packages/testing/src/lib/bookingScenario/expects.ts:1— packages/testing/src/lib/bookingScenario/expects.ts has 1276 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: 1275 lines of code REDACTED:1— REDACTED has 1275 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: 1270 lines of code REDACTED:1— REDACTED has 1270 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· packages/features/bookings/lib/EventManager.ts · ×1
packages/features/bookings/lib/EventManager.ts: 1207 lines of code packages/features/bookings/lib/EventManager.ts:1— packages/features/bookings/lib/EventManager.ts has 1207 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· packages/features/auth/lib/next-auth-options.ts · ×1
packages/features/auth/lib/next-auth-options.ts: 1139 lines of code packages/features/auth/lib/next-auth-options.ts:1— packages/features/auth/lib/next-auth-options.ts has 1139 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/api/v2/src/platform/bookings/2024-08-13/services/bookings.service.ts · ×1
apps/api/v2/src/platform/bookings/2024-08-13/services/bookings.service.ts: 1088 lines of code apps/api/v2/src/platform/bookings/2024-08-13/services/bookings.service.ts:1— apps/api/v2/src/platform/bookings/2024-08-13/services/bookings.service.ts has 1088 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/web/components/booking/BookingListItem.tsx · ×1
apps/web/components/booking/BookingListItem.tsx: 1086 lines of code apps/web/components/booking/BookingListItem.tsx:1— apps/web/components/booking/BookingListItem.tsx has 1086 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· packages/trpc/server/routers/viewer/bookings/get.handler.ts · ×1
packages/trpc/server/routers/viewer/bookings/get.handler.ts: 1061 lines of code packages/trpc/server/routers/viewer/bookings/get.handler.ts:1— packages/trpc/server/routers/viewer/bookings/get.handler.ts has 1061 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· packages/features/eventtypes/components/tabs/limits/EventLimitsTab.tsx · ×1
packages/features/eventtypes/components/tabs/limits/EventLimitsTab.tsx: 1051 lines of code packages/features/eventtypes/components/tabs/limits/EventLimitsTab.tsx:1— packages/features/eventtypes/components/tabs/limits/EventLimitsTab.tsx has 1051 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/web/modules/event-types/components/tabs/advanced/FormBuilder.tsx · ×1
apps/web/modules/event-types/components/tabs/advanced/FormBuilder.tsx: 1024 lines of code apps/web/modules/event-types/components/tabs/advanced/FormBuilder.tsx:1— apps/web/modules/event-types/components/tabs/advanced/FormBuilder.tsx has 1024 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/web/modules/event-types/views/event-types-listing-view.tsx · ×1
apps/web/modules/event-types/views/event-types-listing-view.tsx: 999 lines of code apps/web/modules/event-types/views/event-types-listing-view.tsx:1— apps/web/modules/event-types/views/event-types-listing-view.tsx has 999 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· apps/web/modules/bookings/components/BookingDetailsSheet.tsx · ×1
apps/web/modules/bookings/components/BookingDetailsSheet.tsx: 987 lines of code apps/web/modules/bookings/components/BookingDetailsSheet.tsx:1— apps/web/modules/bookings/components/BookingDetailsSheet.tsx has 987 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· packages/prisma/zod-utils.ts · ×1
packages/prisma/zod-utils.ts: 980 lines of code packages/prisma/zod-utils.ts:1— packages/prisma/zod-utils.ts has 980 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· packages/features/flags/features.repository.integration-test.ts · ×1
packages/features/flags/features.repository.integration-test.ts: 976 lines of code packages/features/flags/features.repository.integration-test.ts:1— packages/features/flags/features.repository.integration-test.ts has 976 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· packages/features/profile/repositories/ProfileRepository.ts · ×1
packages/features/profile/repositories/ProfileRepository.ts: 976 lines of code packages/features/profile/repositories/ProfileRepository.ts:1— packages/features/profile/repositories/ProfileRepository.ts has 976 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· packages/lib/CalendarService.ts · ×1
packages/lib/CalendarService.ts: 907 lines of code packages/lib/CalendarService.ts:1— packages/lib/CalendarService.ts has 907 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· packages/app-store/googlecalendar/lib/CalendarService.ts · ×1
packages/app-store/googlecalendar/lib/CalendarService.ts: 885 lines of code packages/app-store/googlecalendar/lib/CalendarService.ts:1— packages/app-store/googlecalendar/lib/CalendarService.ts has 885 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: 870 lines of code REDACTED:1— REDACTED has 870 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/web/modules/event-types/components/tabs/availability/EventAvailabilityTab.tsx · ×1
apps/web/modules/event-types/components/tabs/availability/EventAvailabilityTab.tsx: 844 lines of code apps/web/modules/event-types/components/tabs/availability/EventAvailabilityTab.tsx:1— apps/web/modules/event-types/components/tabs/availability/EventAvailabilityTab.tsx has 844 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/web/modules/signup-view.tsx · ×1
apps/web/modules/signup-view.tsx: 818 lines of code apps/web/modules/signup-view.tsx:1— apps/web/modules/signup-view.tsx has 818 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/web/modules/event-types/components/locations/HostLocations.tsx · ×1
apps/web/modules/event-types/components/locations/HostLocations.tsx: 793 lines of code apps/web/modules/event-types/components/locations/HostLocations.tsx:1— apps/web/modules/event-types/components/locations/HostLocations.tsx has 793 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· packages/features/bookings/lib/getLuckyUser.ts · ×1
packages/features/bookings/lib/getLuckyUser.ts: 786 lines of code packages/features/bookings/lib/getLuckyUser.ts:1— packages/features/bookings/lib/getLuckyUser.ts has 786 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· packages/features/feature-opt-in/services/FeatureOptInService.integration-test.ts · ×1
packages/features/feature-opt-in/services/FeatureOptInService.integration-test.ts: 785 lines of code packages/features/feature-opt-in/services/FeatureOptInService.integration-test.ts:1— packages/features/feature-opt-in/services/FeatureOptInService.integration-test.ts has 785 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/api/v2/src/platform/bookings/2024-08-13/services/input.service.ts · ×1
apps/api/v2/src/platform/bookings/2024-08-13/services/input.service.ts: 783 lines of code apps/api/v2/src/platform/bookings/2024-08-13/services/input.service.ts:1— apps/api/v2/src/platform/bookings/2024-08-13/services/input.service.ts has 783 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· packages/features/availability/lib/getUserAvailability.ts · ×1
packages/features/availability/lib/getUserAvailability.ts: 778 lines of code packages/features/availability/lib/getUserAvailability.ts:1— packages/features/availability/lib/getUserAvailability.ts 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· packages/features/bookings/Booker/store.ts · ×1
packages/features/bookings/Booker/store.ts: 756 lines of code packages/features/bookings/Booker/store.ts:1— packages/features/bookings/Booker/store.ts has 756 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· packages/platform/atoms/availability/AvailabilitySettings.tsx · ×1
packages/platform/atoms/availability/AvailabilitySettings.tsx: 754 lines of code packages/platform/atoms/availability/AvailabilitySettings.tsx:1— packages/platform/atoms/availability/AvailabilitySettings.tsx has 754 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/web/playwright/manage-booking-questions.e2e.ts · ×1
apps/web/playwright/manage-booking-questions.e2e.ts: 751 lines of code apps/web/playwright/manage-booking-questions.e2e.ts:1— apps/web/playwright/manage-booking-questions.e2e.ts 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· apps/web/modules/users/components/UserTable/UserListTable.tsx · ×1
apps/web/modules/users/components/UserTable/UserListTable.tsx: 750 lines of code apps/web/modules/users/components/UserTable/UserListTable.tsx:1— apps/web/modules/users/components/UserTable/UserListTable.tsx has 750 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
Dead file (~4768 LoC) packages/features/watchlist/lib/freeEmailDomainCheck/freeEmailDomains.ts— no import path from any entry point (919 application, 89 tooling, 646 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~3192 LoC) apps/api/v2/src/platform/event-types/event-types_2024_06_14/controllers/event-types.controller.e2e-spec.ts— no import path from any entry point (919 application, 89 tooling, 646 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~789 LoC) apps/web/modules/users/components/UserTable/UserListTable.tsx— no import path from any entry point (919 application, 89 tooling, 646 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~698 LoC) apps/api/v2/src/modules/slots/slots-2024-04-15/controllers/slots.controller.e2e-spec.ts— no import path from any entry point (919 application, 89 tooling, 646 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~677 LoC) apps/api/v2/src/modules/auth/oauth2/controllers/oauth2.controller.e2e-spec.ts— no import path from any entry point (919 application, 89 tooling, 646 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~631 LoC) apps/api/v2/src/platform/bookings/2024-04-15/controllers/bookings.controller.e2e-spec.ts— no import path from any entry point (919 application, 89 tooling, 646 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~525 LoC) scripts/seed-booking-audit.ts— no import path from any entry point (919 application, 89 tooling, 646 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~485 LoC) packages/features/booking-audit/lib/service/BookingAuditTaskerProducerService.ts— no import path from any entry point (919 application, 89 tooling, 646 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/features/booking-audit/di/BookingAuditTaskerProducerService.module.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 (~442 LoC) apps/api/v2/src/platform/event-types/event-types_2024_04_15/controllers/event-types.controller.e2e-spec.ts— no import path from any entry point (919 application, 89 tooling, 646 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~370 LoC) apps/api/v2/src/modules/auth/strategies/api-auth/api-auth.strategy.e2e-spec.ts— no import path from any entry point (919 application, 89 tooling, 646 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~360 LoC) apps/api/v2/src/modules/oauth-clients/controllers/oauth-clients/oauth-clients.controller.e2e-spec.ts— no import path from any entry point (919 application, 89 tooling, 646 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~309 LoC) apps/web/modules/users/components/UserTable/PlatformManagedUsersTable.tsx— no import path from any entry point (919 application, 89 tooling, 646 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~294 LoC) apps/api/v2/src/modules/event-types/controllers/event-types-webhooks.controller.e2e-spec.ts— no import path from any entry point (919 application, 89 tooling, 646 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~283 LoC) apps/web/modules/onboarding/components/onboarding-invite-browser-view.tsx— no import path from any entry point (919 application, 89 tooling, 646 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~281 LoC) apps/api/v2/src/modules/oauth-clients/controllers/oauth-client-webhooks/oauth-client-webhooks.controller.e2e-spec.ts— no import path from any entry point (919 application, 89 tooling, 646 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~266 LoC) apps/api/v2/src/platform/schedules/schedules_2024_06_11/controllers/schedules.controller.e2e-spec.ts— no import path from any entry point (919 application, 89 tooling, 646 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~264 LoC) packages/ui/components/address/fields.tsx— no import path from any entry point (919 application, 89 tooling, 646 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~263 LoC) apps/api/v2/src/modules/users/outputs/get-users.output.ts— no import path from any entry point (919 application, 89 tooling, 646 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~238 LoC) packages/lib/domainManager/deploymentServices/cloudflare.ts— no import path from any entry point (919 application, 89 tooling, 646 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/lib/domainManager/organization.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 (~236 LoC) apps/web/modules/users/components/UserTable/BulkActions/EventTypesList.tsx— no import path from any entry point (919 application, 89 tooling, 646 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/web/modules/users/components/UserTable/UserListTable.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 (~222 LoC) apps/web/components/security/EnableTwoFactorModal.tsx— no import path from any entry point (919 application, 89 tooling, 646 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/web/components/security/TwoFactorAuthSection.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 (~221 LoC) apps/api/v2/src/platform/schedules/schedules_2024_04_15/controllers/schedules.controller.e2e-spec.ts— no import path from any entry point (919 application, 89 tooling, 646 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~216 LoC) apps/api/v2/src/platform/me/me.controller.e2e-spec.ts— no import path from any entry point (919 application, 89 tooling, 646 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~215 LoC) apps/web/modules/users/components/UserTable/EditSheet/EditUserForm.tsx— no import path from any entry point (919 application, 89 tooling, 646 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/web/modules/users/components/UserTable/EditSheet/EditUserSheet.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 (~206 LoC) vitest.workspace.ts— no import path from any entry point (919 application, 89 tooling, 646 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~194 LoC) apps/api/v2/src/modules/destination-calendars/controllers/destination-calendars.controller.e2e-spec.ts— no import path from any entry point (919 application, 89 tooling, 646 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
Unlisted import 'tslog' apps/api/v2/src/lib/logger.bridge.ts:2— Imported only as a TYPE and declared in no reachable REDACTED. The import is erased at compile time, so nothing is installed and no runtime resolution depends on it — but type-checking a clean clone will fail. Declare the typings it resolves through (or the package itself) in the owning REDACTED.
Unlisted import 'express' apps/web/app/WithEmbedSSR.test.ts:1— Imported only as a TYPE and declared in no reachable REDACTED. The import is erased at compile time, so nothing is installed and no runtime resolution depends on it — but type-checking a clean clone will fail. Declare the typings it resolves through (or the package itself) in the owning REDACTED.
Unlisted import 'satori' apps/web/app/api/social/og/image/route.tsx:3— Imported only as a TYPE and declared in no reachable REDACTED. The import is erased at compile time, so nothing is installed and no runtime resolution depends on it — but type-checking a clean clone will fail. Declare the typings it resolves through (or the package itself) in the owning REDACTED.
Unused dependency '@snaplet/copycat' — Declared in the root REDACTED 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.
Unused dependency 'next-router-mock' — Declared in the root REDACTED 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.
Unused dependency 'node-gyp' — Declared in the root REDACTED 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.
Third-party script without Subresource Integrity apps/web/app/layout.tsx:124— `//unpkg.com/react-grab/dist/index.global.js` is executed by this page with no Subresource Integrity. Whoever can answer that request — the CDN, anyone who compromises it, anyone on the network path — runs arbitrary script in this page's origin, with its session. The URL also names no version, so it resolves to whatever that origin serves at fetch time — the executed bytes can change with nobody touching this repository. 8 such include(s) across the repository's markup.
X17 · Uncapped recursion over a caller-supplied document· Recursive walk over a caller-supplied document has no depth cap · ×1
Recursive walk over a caller-supplied document has no depth cap packages/lib/isEqual.ts:9— `isEqual` is exported and takes `value: unknown` from its caller, and it calls itself at line 9 (`isEqual`) with a piece of `value` (and at line 21) — and nowhere in `isEqual` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame 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. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `isEqual` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
Orphaned file REDACTED:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file apps/api/v2/src/platform/bookings/2024-08-13/services/bookings.service.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 packages/features/auth/lib/next-auth-options.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 apps/web/components/booking/BookingListItem.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 packages/testing/src/lib/bookingScenario/expects.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 packages/trpc/server/routers/viewer/bookings/get.handler.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 packages/lib/CalendarService.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 apps/web/modules/signup-view.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 REDACTED:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/app-store/googlecalendar/lib/CalendarService.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 packages/prisma/zod-utils.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 apps/web/modules/bookings/components/BookingDetailsSheet.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 apps/web/modules/event-types/components/tabs/availability/EventAvailabilityTab.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 apps/api/v2/src/platform/bookings/2024-08-13/services/input.service.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 packages/features/availability/lib/getUserAvailability.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 packages/app-store/office365calendar/lib/CalendarService.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 packages/platform/atoms/availability/AvailabilitySettings.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 apps/web/modules/event-types/components/locations/HostLocations.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 packages/emails/email-manager.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 apps/web/modules/users/components/UserTable/UserListTable.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 packages/app-store/salesforce/src/gql/types.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 apps/web/modules/bookings/components/Booker.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 packages/features/profile/repositories/ProfileRepository.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 apps/api/v2/src/platform/bookings/2024-08-13/controllers/bookings.controller.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 apps/api/v2/src/platform/event-types/event-types_2024_06_14/services/input-event-types.service.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.
Mock-dominated test: updates editor content when updateTemplate prop changes packages/ui/components/editor/plugins/ToolbarPlugin.test.tsx:177— This test sets up 3 test doubles (for example `vi.fn`) against 0 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: initializes editor with provided text packages/ui/components/editor/plugins/ToolbarPlugin.test.tsx:227— This test sets up 3 test doubles (for example `vi.fn`) against 0 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: should handle TRPC errors correctly packages/trpc/server/createNextApiHandler.test.ts:134— This test sets up 3 test doubles (for example `vi.mock/jest.mock of an imported module`) against 1 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: should handle internal server errors correctly packages/trpc/server/createNextApiHandler.test.ts:147— This test sets up 3 test doubles (for example `vi.mock/jest.mock of an imported module`) against 2 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: should not log client errors packages/trpc/server/createNextApiHandler.test.ts:165— This test sets up 3 test doubles (for example `vi.mock/jest.mock of an imported module`) against 1 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: should successfully set destination calendar with DelegationCredential credentials packages/trpc/server/routers/viewer/calendars/setDestinationCalendar.handler.test.ts:105— This test sets up 3 test doubles (for example `vi.mock/jest.mock of an imported module`) against 0 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: should execute query via kysely when no userIds filter is provided packages/trpc/server/routers/viewer/bookings/get.handler.test.ts:207— This test sets up 4 test doubles (for example `vi.fn`) against 0 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: should NOT fetch user IDs when no userIds filter is provided packages/trpc/server/routers/viewer/bookings/get.handler.test.ts:225— This test sets up 4 test doubles (for example `vi.fn`) against 0 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: should use unionAll for combining booking queries packages/trpc/server/routers/viewer/bookings/get.handler.test.ts:243— This test sets up 3 test doubles (for example `vi.fn`) against 0 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: should apply DISTINCT on the outer select packages/trpc/server/routers/viewer/bookings/get.handler.test.ts:260— This test sets up 3 test doubles (for example `vi.fn`) against 0 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: should use cancelSubsequentBookings for recurring events packages/trpc/server/routers/viewer/bookings/reportBooking.handler.test.ts:278— This test sets up 3 test doubles (for example `vi.mock/jest.mock of an imported module`) against 1 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: should pass seatReferenceUid for seated events packages/trpc/server/routers/viewer/bookings/reportBooking.handler.test.ts:313— This test sets up 3 test doubles (for example `vi.mock/jest.mock of an imported module`) against 1 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: should send webhook with correct payload structure packages/trpc/server/routers/viewer/bookings/reportWrongAssignment.handler.test.ts:243— This test sets up 3 test doubles (for example `vi.mock/jest.mock of an imported module`) against 0 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: should persist report to database with all fields packages/trpc/server/routers/viewer/bookings/reportWrongAssignment.handler.test.ts:331— This test sets up 3 test doubles (for example `a double assigned in a shared setup`) against 0 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: should persist report with null optional fields packages/trpc/server/routers/viewer/bookings/reportWrongAssignment.handler.test.ts:353— This test sets up 3 test doubles (for example `a double assigned in a shared setup`) against 0 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: should handle booking without assignmentReason packages/trpc/server/routers/viewer/bookings/reportWrongAssignment.handler.test.ts:427— This test sets up 3 test doubles (for example `vi.mock/jest.mock of an imported module`) against 0 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: should handle booking without eventType packages/trpc/server/routers/viewer/bookings/reportWrongAssignment.handler.test.ts:474— This test sets up 3 test doubles (for example `vi.mock/jest.mock of an imported module`) against 0 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: should handle booking without attendees packages/trpc/server/routers/viewer/bookings/reportWrongAssignment.handler.test.ts:506— This test sets up 3 test doubles (for example `vi.mock/jest.mock of an imported module`) against 0 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: should send verification email even when no watchlist entry exists packages/trpc/server/routers/viewer/admin/lockUserAccount.handler.test.ts:79— This test sets up 3 test doubles (for example `a double assigned in a shared setup`) against 0 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: should log dispatch information with args packages/lib/tasker/Tasker.test.ts:249— This test sets up 7 test doubles (for example `vi.fn`) against 2 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: should log warning about missing env vars packages/lib/tasker/Tasker.test.ts:367— This test sets up 7 test doubles (for example `vi.fn`) against 2 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: should log error details when async tasker fails packages/lib/tasker/Tasker.test.ts:409— This test sets up 7 test doubles (for example `vi.fn`) against 2 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: should call res.json when response is still writable and result is not null packages/lib/server/defaultResponder.test.ts:20— This test sets up 3 test doubles (for example `vi.fn`) against 0 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: should not call res.json when response is not writable packages/lib/server/defaultResponder.test.ts:32— This test sets up 3 test doubles (for example `vi.fn`) against 0 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: should respond with status code 409 for NoAvailableUsersFound packages/lib/server/defaultResponder.test.ts:43— This test sets up 4 test doubles (for example `vi.fn`) against 1 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Deprecated: @graphql-tools/prisma-loader REDACTED:5542— @graphql-tools/prisma-loader 8.0.17 is resolved in REDACTED and is marked deprecated by its publisher: "This package was intended to be used with an older versions of Prisma.\nThe newer versions of Prisma has a different approach to GraphQL integration.\nTherefore, this package is no longer needed and has been deprecated and removed.\nLearn more: https://www.prisma.io/graphql". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @npmcli/move-file REDACTED:8684— @npmcli/move-file 1.1.2 is resolved in REDACTED and is marked deprecated by its publisher: "This functionality has been moved to @npmcli/fs". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @npmcli/move-file REDACTED:8694— @npmcli/move-file 2.0.1 is resolved in REDACTED and is marked deprecated by its publisher: "This functionality has been moved to @npmcli/fs". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @oclif/screen REDACTED:8901— @oclif/screen 3.0.8 is resolved in REDACTED and is marked deprecated by its publisher: "Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @opentelemetry/sdk-trace-base REDACTED:10252— @opentelemetry/sdk-trace-base 2.0.1 is resolved in REDACTED and is marked deprecated by its publisher: "Use @opentelemetry/sdk-trace package". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @opentelemetry/sdk-trace-base REDACTED:10265— @opentelemetry/sdk-trace-base 2.3.0 is resolved in REDACTED and is marked deprecated by its publisher: "Use @opentelemetry/sdk-trace package". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @opentelemetry/sdk-trace-node REDACTED:10278— @opentelemetry/sdk-trace-node 2.0.1 is resolved in REDACTED and is marked deprecated by its publisher: "Use @opentelemetry/sdk-trace package". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @opentelemetry/sdk-trace-web REDACTED:10291— @opentelemetry/sdk-trace-web 2.0.1 is resolved in REDACTED and is marked deprecated by its publisher: "Use @opentelemetry/sdk-trace package". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @otplib/plugin-crypto REDACTED:10360— @otplib/plugin-crypto 12.0.1 is resolved in REDACTED and is marked deprecated by its publisher: "Please upgrade to v13 of otplib. Refer to otplib docs for migration paths". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @otplib/plugin-thirty-two REDACTED:10369— @otplib/plugin-thirty-two 12.0.1 is resolved in REDACTED and is marked deprecated by its publisher: "Please upgrade to v13 of otplib. Refer to otplib docs for migration paths". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @otplib/preset-default REDACTED:10379— @otplib/preset-default 12.0.1 is resolved in REDACTED and is marked deprecated by its publisher: "Please upgrade to v13 of otplib. Refer to otplib docs for migration paths". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @ungap/structured-clone REDACTED:17288— @ungap/structured-clone 1.3.0 is resolved in REDACTED and is marked deprecated by its publisher: "Potential CWE-502 - Update to 1.3.1 or higher". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @xmldom/xmldom REDACTED:17884— @xmldom/xmldom 0.8.12 is resolved in REDACTED and is marked deprecated by its publisher: "this version has critical issues, please update to the latest version". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @xmldom/xmldom REDACTED:17891— @xmldom/xmldom 0.9.9 is resolved in REDACTED and is marked deprecated by its publisher: "this version has critical issues, please update to the latest version". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: abab REDACTED:17930— abab 2.0.6 is resolved in REDACTED and is marked deprecated by its publisher: "Use your platform's native atob() and btoa() methods instead". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: are-we-there-yet REDACTED:18358— are-we-there-yet 3.0.1 is resolved in REDACTED and is marked deprecated by its publisher: "This package is no longer supported.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: cron-parser REDACTED:20953— cron-parser 3.5.0 is resolved in REDACTED and is marked deprecated by its publisher: "v3 is no longer maintained, upgrade to v5". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: cron-parser REDACTED:20963— cron-parser 4.9.0 is resolved in REDACTED and is marked deprecated by its publisher: "v4 is no longer maintained, upgrade to v5". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: crypto REDACTED:21049— crypto 1.0.1 is resolved in REDACTED and is marked deprecated by its publisher: "This package is no longer supported. It's now a built-in Node module. If you've depended on crypto, you should switch to the one that's built-in.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: domexception REDACTED:22355— domexception 4.0.0 is resolved in REDACTED and is marked deprecated by its publisher: "Use your platform's native DOMException instead". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: formidable REDACTED:24410— formidable 2.1.3 is resolved in REDACTED and is marked deprecated by its publisher: "ATTENTION: please upgrade to v3! The v1 and v2 versions are pretty old and deprecated". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: gauge REDACTED:24672— gauge 4.0.4 is resolved in REDACTED and is marked deprecated by its publisher: "This package is no longer supported.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: glob REDACTED:24971— glob 10.3.1 is resolved in REDACTED and is marked deprecated by its publisher: "Old versions of glob are not supported, and contain widely publicized security vulnerabilities, which have been fixed in the current version. Please update. Support for old versions may be purchased (at exorbitant rates) by contacting i@izs.me". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: glob REDACTED:24986— glob 10.3.10 is resolved in REDACTED and is marked deprecated by its publisher: "Old versions of glob are not supported, and contain widely publicized security vulnerabilities, which have been fixed in the current version. Please update. Support for old versions may be purchased (at exorbitant rates) by contacting i@izs.me". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: glob REDACTED:25017— glob 11.1.0 is resolved in REDACTED and is marked deprecated by its publisher: "Old versions of glob are not supported, and contain widely publicized security vulnerabilities, which have been fixed in the current version. Please update. Support for old versions may be purchased (at exorbitant rates) by contacting i@izs.me". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Interpolated log message defeats structured logging packages/lib/CalendarService.ts:649— `error` at line 649 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.error({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.error('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way.
Interpolated log message defeats structured logging packages/lib/CalendarService.ts:742— `warn` at line 742 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.warn({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.warn('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way.
Interpolated log message defeats structured logging packages/lib/getIP.ts:54— `warn` at line 54 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.warn({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.warn('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way.
Interpolated log message defeats structured logging packages/lib/perf.ts:8— `debug` at line 8 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.debug({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.debug('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way.
Interpolated log message defeats structured logging packages/lib/sentryWrapper.ts:156— `debug` at line 156 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.debug({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.debug('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way.
Interpolated log message defeats structured logging packages/lib/isOutOfBounds.tsx:210— `silly` at line 210 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.silly({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.silly('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way.
Interpolated log message defeats structured logging packages/lib/tasker/Tasker.ts:47— `info` at line 47 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.info({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.info('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way.
Interpolated log message defeats structured logging packages/lib/tasker/Tasker.ts:56— `info` at line 56 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.info({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.info('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way.
Interpolated log message defeats structured logging packages/lib/tasker/Tasker.ts:66— `error` at line 66 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.error({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.error('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way.
Interpolated log message defeats structured logging packages/lib/tasker/Tasker.ts:75— `warn` at line 75 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.warn({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.warn('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way.
Interpolated log message defeats structured logging packages/lib/tasker/Tasker.ts:81— `error` at line 81 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.error({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.error('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way.
Interpolated log message defeats structured logging packages/lib/server/defaultResponder.ts:56— `error` at line 56 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.error({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.error('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way.
Interpolated log message defeats structured logging packages/lib/server/service/lingoDotDev.ts:42— `error` at line 42 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.error({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.error('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way.
Interpolated log message defeats structured logging packages/lib/server/service/lingoDotDev.ts:73— `error` at line 73 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.error({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.error('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way.
Interpolated log message defeats structured logging packages/lib/server/service/lingoDotDev.ts:106— `error` at line 106 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.error({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.error('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way.
Interpolated log message defeats structured logging packages/lib/domainManager/organization.ts:55— `error` at line 55 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.error({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.error('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way.
Interpolated log message defeats structured logging packages/lib/domainManager/deploymentServices/cloudflare.ts:41— `info` at line 41 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.info({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.info('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way.
Interpolated log message defeats structured logging packages/lib/domainManager/deploymentServices/cloudflare.ts:59— `info` at line 59 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.info({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.info('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way.
Interpolated log message defeats structured logging packages/lib/domainManager/deploymentServices/cloudflare.ts:74— `info` at line 74 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.info({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.info('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way.
Interpolated log message defeats structured logging packages/lib/domainManager/deploymentServices/cloudflare.ts:79— `info` at line 79 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.info({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.info('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way.
Interpolated log message defeats structured logging packages/lib/domainManager/deploymentServices/cloudflare.ts:85— `info` at line 85 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.info({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.info('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way.
Interpolated log message defeats structured logging packages/lib/domainManager/deploymentServices/cloudflare.ts:87— `info` at line 87 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.info({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.info('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way.
Interpolated log message defeats structured logging packages/lib/domainManager/deploymentServices/cloudflare.ts:155— `info` at line 155 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.info({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.info('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way.
Interpolated log message defeats structured logging packages/lib/domainManager/deploymentServices/cloudflare.ts:158— `error` at line 158 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.error({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.error('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way.
Interpolated log message defeats structured logging packages/lib/domainManager/deploymentServices/cloudflare.ts:170— `info` at line 170 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.info({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.info('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way.
+ 15 more in this group — see findings.md.
P2 · Observability· Console output used as the logging channel · ×39
Console output used as the logging channel apps/api/v2/src/swagger/copy-swagger-module.ts:23— `apps/api/v2/src/swagger/copy-swagger-module.ts` reports through `console.*` at line 23 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel apps/api/v2/src/swagger/generate-swagger-script.ts:9— `apps/api/v2/src/swagger/generate-swagger-script.ts` reports through `console.*` at line 9 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 apps/api/v2/src/swagger/generate-swagger-script.ts:13— `apps/api/v2/src/swagger/generate-swagger-script.ts` reports through `console.*` at line 13 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 apps/api/v2/src/swagger/generate-swagger-script.ts:24— `apps/api/v2/src/swagger/generate-swagger-script.ts` reports through `console.*` at line 24 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel apps/api/v2/src/modules/stripe/utils/getReturnToValueFromQueryState.ts:6— `apps/api/v2/src/modules/stripe/utils/getReturnToValueFromQueryState.ts` reports through `console.*` at line 6 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 apps/api/v2/src/modules/stripe/utils/getReturnToValueFromQueryState.ts:16— `apps/api/v2/src/modules/stripe/utils/getReturnToValueFromQueryState.ts` reports through `console.*` at line 16 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 apps/api/v2/src/modules/stripe/controllers/stripe.controller.ts:142— `apps/api/v2/src/modules/stripe/controllers/stripe.controller.ts` 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 apps/api/v2/src/modules/slots/slots-2024-04-15/workers/slots.worker.ts:30— `apps/api/v2/src/modules/slots/slots-2024-04-15/workers/slots.worker.ts` reports through `console.*` at line 30 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 apps/web/cron-tester.ts:16— `apps/web/cron-tester.ts` reports through `console.*` at line 16 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 apps/web/cron-tester.ts:20— `apps/web/cron-tester.ts` reports through `console.*` at line 20 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 apps/web/cron-tester.ts:36— `apps/web/cron-tester.ts` reports through `console.*` at line 36 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 apps/web/getNextjsOrgRewriteConfig.ts:40— `apps/web/getNextjsOrgRewriteConfig.ts` reports through `console.*` at line 40 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel apps/web/server/lib/auth/login/getServerSideProps.tsx:65— `apps/web/server/lib/auth/login/getServerSideProps.tsx` reports through `console.*` at line 65 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 apps/web/public/service-worker.js:12— `apps/web/public/service-worker.js` reports through `console.*` at line 12 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 apps/web/public/service-worker.js:53— `apps/web/public/service-worker.js` reports through `console.*` at line 53 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 apps/web/public/service-worker.js:56— `apps/web/public/service-worker.js` reports through `console.*` at line 56 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 apps/web/public/service-worker.js:58— `apps/web/public/service-worker.js` reports through `console.*` at line 58 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 apps/web/public/service-worker.js:100— `apps/web/public/service-worker.js` reports through `console.*` at line 100 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 apps/web/public/service-worker.js:104— `apps/web/public/service-worker.js` reports through `console.*` at line 104 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 apps/web/playwright/lib/next-server.ts:32— `apps/web/playwright/lib/next-server.ts` reports through `console.*` at line 32 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel apps/web/playwright/lib/testUtils.ts:335— `apps/web/playwright/lib/testUtils.ts` reports through `console.*` at line 335 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 apps/web/playwright/lib/testUtils.ts:470— `apps/web/playwright/lib/testUtils.ts` reports through `console.*` at line 470 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 apps/web/playwright/lib/testUtils.ts:476— `apps/web/playwright/lib/testUtils.ts` reports through `console.*` at line 476 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 REDACTED:83— `REDACTED` reports through `console.*` at line 83 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 apps/web/modules/signup-view.tsx:277— `apps/web/modules/signup-view.tsx` reports through `console.*` at line 277 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Outdated (npm): @boxyhq/saml-jackson REDACTED:34— @boxyhq/saml-jackson is pinned at 1.52.2; registry.npmjs.org publishes 26.2.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @getalby/lightning-tools packages/app-store/alby/REDACTED:9— @getalby/lightning-tools is pinned at 5.1.2; registry.npmjs.org publishes 9.0.2 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @getalby/sdk packages/app-store/alby/REDACTED:10— @getalby/sdk is pinned at 4.0.0; registry.npmjs.org publishes 8.1.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @googleapis/admin REDACTED:57— @googleapis/admin is pinned at 23.5.0; registry.npmjs.org publishes 37.0.2 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @googleapis/calendar REDACTED:58— @googleapis/calendar is pinned at 9.7.9; registry.npmjs.org publishes 20.1.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @googleapis/oauth2 REDACTED:59— @googleapis/oauth2 is pinned at 1.0.7; registry.npmjs.org publishes 10.0.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @hookform/resolvers REDACTED:61— @hookform/resolvers is pinned at 2.9.7; registry.npmjs.org publishes 6.0.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @hubspot/api-client packages/app-store/hubspot/REDACTED:10— @hubspot/api-client is pinned at 6.0.1; registry.npmjs.org publishes 14.1.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @nestjs/axios REDACTED:51— @nestjs/axios is pinned at 4.0.0; registry.npmjs.org publishes 12.0.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @nestjs/config REDACTED:54— @nestjs/config is pinned at 3.2.0; registry.npmjs.org publishes 12.0.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @nestjs/swagger REDACTED:59— @nestjs/swagger is pinned at 7.4.2; registry.npmjs.org publishes 12.0.4 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @stripe/react-stripe-js REDACTED:79— @stripe/react-stripe-js is pinned at 1.10.0; registry.npmjs.org publishes 7.0.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @stripe/stripe-js REDACTED:80— @stripe/stripe-js is pinned at 1.35.0; registry.npmjs.org publishes 10.2.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @wojtekmaj/react-daterange-picker REDACTED:97— @wojtekmaj/react-daterange-picker is pinned at 3.4.0; registry.npmjs.org publishes 7.1.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): downshift REDACTED:103— downshift is pinned at 6.1.9; registry.npmjs.org publishes 9.4.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): entities REDACTED:94— entities is pinned at 4.5.0; registry.npmjs.org publishes 8.1.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): framer-motion REDACTED:33— framer-motion is pinned at 10.12.8; registry.npmjs.org publishes 14.6.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): googleapis REDACTED:73— googleapis is pinned at 84.0.0; registry.npmjs.org publishes 188.0.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): i18next REDACTED:96— i18next is pinned at 23.2.3; registry.npmjs.org publishes 26.5.11 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): ink packages/app-store-cli/REDACTED:22— ink is pinned at 3.2.0; registry.npmjs.org publishes 8.0.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): jsdom REDACTED:102— jsdom is pinned at 22.0.0; registry.npmjs.org publishes 30.1.3 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): marked packages/platform/atoms/REDACTED:92— marked is pinned at 15.0.6; registry.npmjs.org publishes 18.1.2 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): meow packages/app-store-cli/REDACTED:25— meow is pinned at 9.0.0; registry.npmjs.org publishes 14.1.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): nodemailer REDACTED:116— nodemailer is pinned at 7.0.12; registry.npmjs.org publishes 10.2.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): react-i18next REDACTED:128— react-i18next is pinned at 12.3.1; registry.npmjs.org publishes 17.1.9 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Duplicated predicate apps/web/modules/calendars/components/SelectedCalendarsSettingsWebWrapper.tsx:58— `!!connectedCalendar.calendars && connectedCalendar.calendars.length > 0` appears character-identically in 2 files — apps/web/modules/calendars/components/SelectedCalendarsSettingsWebWrapper.tsx, packages/platform/atoms/selected-calendars/wrappers/SelectedCalendarsSettingsPlatformWrapper.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 apps/web/components/apps/alby/Setup.tsx:74— `!!integrations.data && integrations.isSuccess && !!credentialId` appears character-identically in 4 files — apps/web/components/apps/alby/Setup.tsx, apps/web/components/apps/btcpayserver/Setup.tsx, apps/web/components/apps/hitpay/Setup.tsx, apps/web/components/apps/paypal/Setup.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 apps/api/v2/src/modules/atoms/services/event-types-atom.service.ts:303— `!!userCredentialIds.length || !!teams.length || app.isGlobal` appears character-identically in 2 files — apps/api/v2/src/modules/atoms/services/event-types-atom.service.ts, packages/app-store/_utils/getConnectedApps.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 apps/web/components/booking/BookingListItem.tsx:174— `!!userEmail && seat.attendee?.email === userEmail` appears character-identically in 2 files — apps/web/components/booking/BookingListItem.tsx, apps/web/components/booking/actions/BookingActionsDropdown.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 apps/api/v2/src/modules/event-types/guards/event-type-ownership.guard.ts:31— `!Number.isInteger(eventTypeId) || eventTypeId <= 0` appears character-identically in 2 files — apps/api/v2/src/modules/event-types/guards/event-type-ownership.guard.ts, packages/features/bot-detection/BotDetectionService.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 apps/web/modules/event-types/components/tabs/advanced/EventAdvancedTab.tsx:597— `!Number.isNaN(paymentAppData.price) && paymentAppData.price > 0` appears character-identically in 2 files — apps/web/modules/event-types/components/tabs/advanced/EventAdvancedTab.tsx, packages/features/bookings/lib/service/RegularBookingService.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate REDACTED:37— `!accountsServer || typeof accountsServer !== "string"` appears character-identically in 2 files — REDACTED, REDACTED. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate apps/web/components/booking/BookingListItem.tsx:220— `!booking.location || booking.location === "integrations:daily" || (typeof booking.location === "string" && booking.location.trim() === "")` appears character-identically in 2 files — apps/web/components/booking/BookingListItem.tsx, apps/web/components/booking/actions/BookingActionsDropdown.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 apps/web/components/apps/DestinationCalendarSettingsWebWrapper.tsx:37— `!calendars.data?.connectedCalendars || calendars.data.connectedCalendars.length < 1` appears character-identically in 2 files — apps/web/components/apps/DestinationCalendarSettingsWebWrapper.tsx, packages/platform/atoms/destination-calendar/wrappers/DestinationCalendarSettingsPlatformWrapper.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 packages/app-store/closecom/api/_getAdd.ts:16— `!client_id || typeof client_id !== "string"` appears character-identically in 3 files — packages/app-store/closecom/api/_getAdd.ts, packages/app-store/closecom/api/callback.ts, packages/trpc/server/routers/viewer/googleWorkspace/googleWorkspace.handler.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 packages/app-store/closecom/api/callback.ts:40— `!client_secret || typeof client_secret !== "string"` appears character-identically in 2 files — packages/app-store/closecom/api/callback.ts, packages/trpc/server/routers/viewer/googleWorkspace/googleWorkspace.handler.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 packages/app-store/office365calendar/lib/CalendarService.ts:200— `!delegationCredentialClientId || !delegationCredentialClientSecret` appears character-identically in 2 files — packages/app-store/office365calendar/lib/CalendarService.ts, packages/app-store/office365video/lib/VideoApiAdapter.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 packages/features/bookings/lib/handleNewBooking/ensureAvailableUsers.ts:174— `!eventType.useBookerTimezone && !restrictionSchedule.timeZone` appears character-identically in 2 files — packages/features/bookings/lib/handleNewBooking/ensureAvailableUsers.ts, REDACTED. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate packages/app-store/feishucalendar/common.ts:11— `!expiryDate || expiryDate < Math.round(Number(new Date()) / 1000)` appears character-identically in 2 files — packages/app-store/feishucalendar/common.ts, packages/app-store/larkcalendar/common.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 packages/app-store/hubspot/lib/CrmService.ts:213— `!fieldValue.startsWith("{") && !fieldValue.endsWith("}")` appears character-identically in 2 files — packages/app-store/hubspot/lib/CrmService.ts, packages/app-store/salesforce/lib/CrmService.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 apps/web/components/booking/BookingListItem.tsx:184— `!forcedTheme && resolvedTheme === "dark"` appears character-identically in 4 files — apps/web/components/booking/BookingListItem.tsx, apps/web/modules/bookings/components/BookingCalendarView.tsx, apps/web/modules/event-types/views/event-types-listing-view.tsx, packages/features/form/components/Select.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 packages/ui/components/image-uploader/BannerUploader.tsx:158— `!imageSrc || checkIfItFallbackImage(imageSrc)` appears character-identically in 2 files — packages/ui/components/image-uploader/BannerUploader.tsx, packages/ui/components/image-uploader/ImageUploader.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 packages/features/schedules/repositories/ScheduleRepository.ts:119— `!isCurrentUserPartOfTeam && !isCurrentUserOwner` appears character-identically in 2 files — packages/features/schedules/repositories/ScheduleRepository.ts, packages/trpc/server/routers/viewer/availability/schedule/getAllSchedulesByUserId.handler.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 packages/features/cache/decorators/Memoize.ts:23— `!originalMethod || typeof originalMethod !== "function"` appears character-identically in 2 files — packages/features/cache/decorators/Memoize.ts, packages/features/cache/decorators/Unmemoize.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 packages/app-store/alby/components/EventTypeAppCardInterface.tsx:32— `!requirePayment && otherPaymentAppEnabled` appears character-identically in 5 files — packages/app-store/alby/components/EventTypeAppCardInterface.tsx, packages/app-store/btcpayserver/components/EventTypeAppCardInterface.tsx, packages/app-store/hitpay/components/EventTypeAppCardInterface.tsx, packages/app-store/paypal/components/EventTypeAppCardInterface.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 packages/app-store/googlecalendar/lib/CalendarAuth.ts:221— `!response.ok || (response.status < 200 && response.status >= 300)` appears character-identically in 3 files — packages/app-store/googlecalendar/lib/CalendarAuth.ts, packages/app-store/nextcloudtalk/lib/VideoApiAdapter.ts, packages/app-store/webex/lib/VideoApiAdapter.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 packages/app-store/_utils/oauth/OAuthManager.ts:236— `!response.ok || response.status < 200 || response.status >= 300` appears character-identically in 2 files — packages/app-store/_utils/oauth/OAuthManager.ts, packages/lib/errors.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 apps/web/lib/QueryCell.tsx:64— `"empty" in opts && (query.data == null || (Array.isArray(query.data) && query.data.length === 0))` appears character-identically in 2 files — apps/web/lib/QueryCell.tsx, packages/trpc/components/QueryCell.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 packages/features/eventtypes/repositories/eventTypeRepository.ts:191— `"id" in lookupTarget && lookupTarget.id !== undefined` appears character-identically in 2 files — packages/features/eventtypes/repositories/eventTypeRepository.ts, packages/features/membership/repositories/MembershipRepository.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 apps/api/v2/src/platform/event-types/event-types_2024_06_14/services/input-event-types.service.ts:315— `"slug" in field && field.slug === "guests"` appears character-identically in 2 files — apps/api/v2/src/platform/event-types/event-types_2024_06_14/services/input-event-types.service.ts, apps/api/v2/src/platform/event-types/event-types_2024_06_14/transformers/api-to-internal/booking-fields.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.
X23 · Unguarded diagnostic materialisation· Diagnostic log message is built whether or not it is wanted · ×15
Diagnostic log message is built whether or not it is wanted REDACTED:710— `debug` at line 710 is called with an argument built by `usersWithCredentials.map((user) => user.email)` (line 711), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch.
Diagnostic log message is built whether or not it is wanted packages/features/calendars/lib/getCalendarsEvents.ts:177— `debug` at line 177 is called with an argument built by `passedSelectedCalendars.map(getPiiFreeSelectedCalendar)` (line 181), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch.
Diagnostic log message is built whether or not it is wanted packages/features/calendars/lib/getCalendarsEvents.ts:222— `debug` at line 222 is called with an argument built by `calendarCredentials.map(getPiiFreeCredential)` (line 225), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch.
Diagnostic log message is built whether or not it is wanted packages/features/calendar-subscription/lib/cache/CalendarCacheWrapper.ts:58— `debug` at line 58 is called with an argument built by `selectedCalendars.map((c) => c.id)` (line 61), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch.
Diagnostic log message is built whether or not it is wanted packages/features/calendar-subscription/lib/cache/CalendarCacheWrapper.ts:145— `debug` at line 145 is called with an argument built by `selectedCalendars.map((c) => c.id)` (line 148), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch.
Diagnostic log message is built whether or not it is wanted packages/features/busyTimes/services/getBusyTimes.ts:185— `debug` at line 185 is called with an argument built by `bookings?.map((booking) => getPiiFreeBooking(booking))` (line 188), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch.
Diagnostic log message is built whether or not it is wanted packages/features/bookings/lib/getLuckyUser.ts:424— `debug` at line 424 is called with an argument built by `usersWithMaxShortfall.map((user) => user.email)` (line 428), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch.
Diagnostic log message is built whether or not it is wanted packages/features/bookings/lib/service/RegularBookingService.ts:952— `debug` at line 952 is called with an argument built by `qualifiedRRUsers.map((user) => user.id)` (line 955), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch.
Diagnostic log message is built whether or not it is wanted packages/features/bookings/lib/service/RegularBookingService.ts:980— `debug` at line 980 is called with an argument built by `qualifiedRRUsers.map((user) => user.id)` (line 983), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch.
Diagnostic log message is built whether or not it is wanted packages/features/bookings/lib/service/RegularBookingService.ts:1009— `debug` at line 1009 is called with an argument built by `availableUsers.map((user) => user.id)` (line 1012), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch.
Diagnostic log message is built whether or not it is wanted packages/features/bookings/lib/service/RegularBookingService.ts:1692— `debug` at line 1692 is called with an argument built by `attendeesList.map((guest) => ({ timeZone : guest.timeZone }))` (line 1696), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch.
Diagnostic log message is built whether or not it is wanted packages/features/bookings/lib/handleNewBooking/loadAndValidateUsers.ts:212— `debug` at line 212 is called with an argument built by `users.map(getPiiFreeUser)` (line 215), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch.
Diagnostic log message is built whether or not it is wanted packages/features/booking-audit/lib/service/BookingAuditTaskConsumer.ts:282— `debug` at line 282 is called with an argument built by `bookingUids.join(",")` (line 283), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch.
Diagnostic log message is built whether or not it is wanted packages/features/booking-audit/lib/service/BookingAuditTaskConsumer.ts:294— `debug` at line 294 is called with an argument built by `bookingUids.join(",")` (line 295), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch.
Diagnostic log message is built whether or not it is wanted apps/web/pages/_error.tsx:86— `debug` at line 86 is called with an argument built by `JSON.stringify(err)` (line 86), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch.
Silent fallback default in catch apps/api/v2/src/lib/logger.bridge.ts:134— `formatArgsAsString` swallows every exception into `return "[Unserializable Object]"` — 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 apps/web/pages/_document.tsx:44— `render` swallows every exception into `return false` — 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 packages/app-store-cli/src/utils/getApp.ts:20— `getApp` 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 packages/app-store/ics-feedcalendar/lib/CalendarService.ts:29— `getTravelDurationInSeconds` swallows every exception into `return 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 handler or in the docstring, and the row stops firing.
Silent fallback default in catch packages/lib/recentImpersonations.ts:16— `getRecentImpersonations` 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 packages/lib/triggerDevLogger.ts:69— `formatArgsAsString` swallows every exception into `return "[Unserializable Object]"` — 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 packages/prisma/extensions/exclude-locked-users.ts:30— `safeJSONStringify` 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.
Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 20 significant file(s) lose their only recent owner: apps/web/modules/booking-audit/components/BookingHistory.tsx, packages/features/booking-audit/lib/service/BookingAuditTaskConsumer.ts, packages/features/booking-audit/lib/service/BookingAuditTaskerProducerService.ts, packages/features/booking-audit/lib/service/BookingAuditViewerService.ts, scripts/seed-booking-audit.ts, packages/features/booking-audit/lib/service/BookingAuditProducerService.interface.ts, packages/features/booking-audit/lib/actions/NoShowUpdatedAuditActionService.ts, packages/features/booking-audit/lib/actions/RescheduledAuditActionService.ts (+12 more). Pair on, review, or document these before any departure.
Off-boarding risk: anonymized user #2 — If anonymized user #2 becomes unavailable, 8 significant file(s) lose their only recent owner: packages/coss-ui/src/icons.tsx, packages/features/feature-opt-in/services/FeatureOptInService.ts, apps/web/modules/bookings/components/BookingCalendarContainer.tsx, apps/web/modules/data-table/hooks/useColumnResizing.ts, packages/features/feature-opt-in/config.ts, apps/web/modules/bookings/hooks/useBookingListColumns.tsx, packages/ui/components/card/PanelCard.tsx, packages/features/feature-opt-in/services/IFeatureOptInService.ts. Pair on, review, or document these before any departure.
Off-boarding risk: anonymized user #3 — If anonymized user #3 becomes unavailable, 6 significant file(s) lose their only recent owner: apps/api/v2/src/platform/bookings/2024-08-13/controllers/booking-attendees.controller.ts, apps/api/v2/src/platform/bookings/2024-08-13/services/booking-attendees.service.ts, packages/platform/types/bookings/2024-08-13/inputs/update-location.input.ts, packages/features/bookings/services/BookingAttendeesService.ts, apps/api/v2/src/platform/bookings/2024-08-13/controllers/booking-location.controller.ts, packages/platform/atoms/hooks/connect/useConnect.ts. Pair on, review, or document these before any departure.
Off-boarding risk: anonymized user #4 — If anonymized user #4 becomes unavailable, 7 significant file(s) lose their only recent owner: apps/web/modules/onboarding/getting-started/onboarding-view.tsx, apps/web/modules/onboarding/components/onboarding-organization-browser-view.tsx, apps/web/modules/onboarding/personal/calendar/personal-calendar-view.tsx, apps/web/modules/onboarding/components/plan-icon.tsx, apps/web/modules/onboarding/hooks/useSubmitOnboarding.ts, apps/web/modules/settings/my-account/components/CompanyEmailOrganizationBanner.tsx, packages/features/auth/lib/onboardingUtils.ts. Pair on, review, or document these before any departure.
README/code drift agents/README.md:66— agents/README.md links to `rules/patterns-workflow-triggers.md`, but `agents/rules/patterns-workflow-triggers.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, 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 packages/features/booking-audit/README.md:25— packages/features/booking-audit/README.md names UUID 7, but the manifest declares `uuid` 8.3.2. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, 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 specs/_templates/docs/README.md:13— specs/_templates/docs/README.md links to `./screenshots/step-1.png`, but `specs/_templates/docs/screenshots/step-1.png` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, 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 specs/_templates/docs/README.md:19— specs/_templates/docs/README.md links to `./screenshots/step-2.png`, but `specs/_templates/docs/screenshots/step-2.png` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, 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.
D34 · Knowledge Freshness· Most significant orphaned file · ×3
Most significant orphaned file packages/app-store/salesforce/lib/CrmService.ts:1— One of the orphaned files carrying the most lost knowledge — ranked by size weighted by the file's role in the codebase, the same weighting behind the score above, so core code outranks equally large plumbing. A reasonable place to start a read-through before the aggregate risk above bites.
Most significant orphaned file REDACTED:1— One of the orphaned files carrying the most lost knowledge — ranked by size weighted by the file's role in the codebase, the same weighting behind the score above, so core code outranks equally large plumbing. A reasonable place to start a read-through before the aggregate risk above bites.
Most significant orphaned file packages/features/bookings/lib/EventManager.ts:1— One of the orphaned files carrying the most lost knowledge — ranked by size weighted by the file's role in the codebase, the same weighting behind the score above, so core code outranks equally large plumbing. A reasonable place to start a read-through before the aggregate risk above bites.
Fat interface: BookingAuditProducerService (18 required operations) packages/features/booking-audit/lib/service/BookingAuditProducerService.interface.ts:32— `BookingAuditProducerService` declares 18 required operations: `queueCreatedAudit`, `queueRescheduledAudit`, `queueAcceptedAudit`, `queueCancelledAudit`, `queueRescheduleRequestedAudit`, `queueAttendeeAddedAudit`, `queueNoShowUpdatedAudit`, `queueRejectedAudit`, `queueAttendeeRemovedAudit`, `queueReassignmentAudit`, `queueLocationChangedAudit`, `queueSeatBookedAudit`, `queueSeatRescheduledAudit`, `queueBulkAcceptedAudit`, `queueBulkCancelledAudit`, `queueBulkCreatedAudit`, `queueBulkRescheduledAudit`, `queueBulkRejectedAudit`. Counted over its REQUIRED operations — a method signature or a function-typed property with no `?`, once per signature; optional members and data properties are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
Fat interface: IBookingReportRepository (18 required operations) packages/features/bookingReport/repositories/IBookingReportRepository.ts:84— `IBookingReportRepository` declares 18 required operations: `createReport`, `findAllReportedBookings`, `findGroupedReportedBookings`, `findReportsByIds`, `linkWatchlistToReport`, `updateReportStatus`, `bulkLinkWatchlistWithStatus`, `bulkLinkGlobalWatchlistWithSystemStatus`, `countPendingReports`, `updateSystemReportStatus`, `bulkUpdateSystemReportStatus`, `countSystemPendingReports`, `dismissReportsByEmail`, `dismissSystemReportsByEmail`, `findPendingReportsByEmail`, `findPendingReportsByDomain`, `findPendingSystemReportsByEmail`, `findPendingSystemReportsByDomain`. Counted over its REQUIRED operations — a method signature or a function-typed property with no `?`, once per signature; optional members and data properties are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
Partial audit-trail evidence — An audit mechanism is present, but the trail is not yet complete — missing: an ORM write hook every change flows through (a TypeORM/MikroORM subscriber, a Sequelize or Mongoose hook, Prisma middleware or a query extension, or an event-store append), per-model coverage (@Audited, or a change-history plugin such as mongoose-history or sequelize-paper-trail applied to each model).
D16 · Bus Factor· Further sole-owners (lower concentration) · ×1
Further sole-owners (lower concentration) — 10 other contributor(s) are each the sole owner of a small amount of code below the off-boarding threshold — folded into the bus-factor score and metrics (56 single-owned of 1267 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; 1267 of the 4311 production source files in this repository met that bar). They are anonymized user #5 (2 file(s)), anonymized user #6 (2 file(s)), anonymized user #7 (2 file(s)), anonymized user #8 (2 file(s)), anonymized user #9 (2 file(s)), anonymized user #10 (1 file(s)) (+4 more) — spread or document their files in the same way, at lower priority than the named off-boarding risks above. The files folded here: packages/app-store/salesforce/lib/graphql/SalesforceGraphQLClient.ts, packages/app-store/salesforce/zod.ts, packages/app-store/webex/lib/VideoApiAdapter.ts, packages/trpc/server/routers/viewer/googleWorkspace/googleWorkspace.handler.ts, packages/features/calendar-subscription/lib/CalendarSubscriptionService.ts, packages/features/calendar-subscription/adapters/GoogleCalendarSubscription.adapter.ts, packages/features/bookingReport/repositories/PrismaBookingReportRepository.ts, packages/features/bookingReport/repositories/IBookingReportRepository.ts (+7 more).
ADR Context section is empty specs/_templates/decisions.md:5— specs/_templates/decisions.md:5 heads a Context section with nothing under it but a placeholder. A decision record states the context that forced it, the decision and its consequences; write what this one's context are.
ADR Decision section is empty specs/_templates/decisions.md:14— specs/_templates/decisions.md:14 heads a Decision section with nothing under it but a placeholder. A decision record states the context that forced it, the decision and its consequences; write what this one's decision are.
ADR Consequences section is empty specs/_templates/decisions.md:18— specs/_templates/decisions.md:18 heads a Consequences section with nothing under it but a placeholder. A decision record states the context that forced it, the decision and its consequences; write what this one's consequences are.
D26 · Project Cohesion· Projects may be oversized for their cohesion · ×1
Projects may be oversized for their cohesion — 10 of 111 project(s) overshoot their size bounds, lowering Project Cohesion to 8.3/10. The most over is `apps/web` (84613 LoC, 839 module-visible types across 320 directories). Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
D28 · Secrets (history)· Rotate the exposed credentials · ×1
Concentrated knowledge decay — 1188 of 1267 significant files have no living knowledge, while the repository is still being changed at a low rate (23 commit(s) in the last 90 days) — so this is one repo-wide knowledge-decay state, not 1188 separate risks. Counted over 1267 of the 4311 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over. The code moved on without the people who understood these files: document them or schedule a read-through before the next change lands in them.
M2 · Architecture documentation· ADRs not easily discoverable · ×1
ADRs not easily discoverable — 3 ADR-shaped document(s) detected by content — `SPEC-WORKFLOW.md`, `specs/_templates/decisions.md`, `specs/cancellation-reason-requirement/decisions.md`. They are not under a conventional ADR folder (docs/adr/) and are not named NNNN-title.md, and this check found them by their decision signature rather than by where they live — so a reader who does not already know these paths has no route to them. Detected by content signature only: records kept outside the repository, or written without a Status/Decision/Consequences shape, are not visible to this check and are not counted here.
Logging is not universal — Only 42/48 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `apps/api`, `apps/docs`, `example-apps/credential-sync`, `packages/app-store-cli`, `packages/platform/examples/base` and 1 more.
No SAST — No static application security testing detected. For this repository's stack, add CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security as a CI step. What was searched, so you can tell an absence from a miss: the 126685 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
R8 · Dependency Hygiene· Type-only dependency '@microsoft/microsoft-graph-types-beta' in production deps · ×1
Type-only dependency '@microsoft/microsoft-graph-types-beta' in production deps apps/api/v2/src/platform/calendars/services/outlook.service.ts:7— Every import is type-only — move it to devDependencies.
R8 · Dependency Hygiene· Test-only dependency 'bcryptjs' in production deps · ×1
Test-only dependency 'bcryptjs' in production deps REDACTED:90— Only test files import it (first: apps/web/playwright/fixtures/users.ts:14) — move it to devDependencies.
No app-layer HTTPS enforcement detected apps/api/index.js:18— `http(…).listen(…)` serves plain HTTP on a network address, and nothing in its package enforces HTTPS: no TLS served (`https.createServer`, Fastify `https`, Nest `httpsOptions`), no redirect of plain requests to `https://`, no `Strict-Transport-Security` (helmet sends it by default), and no TLS-terminating proxy configuration committed beside it — so a browser may talk to it in clear text. (−2.0 on this card.)
X2 · Cancellation propagation· Not all async functions that make a request accept an AbortSignal · ×1
Not all async functions that make a request accept an AbortSignal — Only 17/113 async functions that make a cancellable request (fetch, axios, ky, ofetch) 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 — 2/26 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.
Null assertions (`!`) reduce the strict null checking score — ~3.2 `!` null assertions per 1k TypeScript source lines — 1185 assertion(s) across the 365094 source line(s) of the 4247 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: REDACTED (60), packages/platform/types/event-types/event-types_2024_06_14/outputs/booking-fields.output.ts (53), apps/api/v2/src/platform/event-types/event-types_2024_04_15/outputs/get-event-type-public.output.ts (51). Each one tells the compiler to trust the author about null, suppressing the very diagnostic `strictNullChecks` exists to produce.
Outdated (npm): @axiomhq/winston — @axiomhq/winston is pinned at 1.2.0; registry.npmjs.org publishes 2.0.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @base-ui/react — @base-ui/react is pinned at 1.0.0; registry.npmjs.org publishes 1.9.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @daily-co/daily-js — @daily-co/daily-js is pinned at 0.83.1; registry.npmjs.org publishes 0.94.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @daily-co/daily-react — @daily-co/daily-react is pinned at 0.23.2; registry.npmjs.org publishes 0.26.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @dub/analytics — @dub/analytics is pinned at 0.0.27; registry.npmjs.org publishes 0.0.32 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @dub/embed-core — @dub/embed-core is pinned at 0.0.18; registry.npmjs.org publishes 0.0.19 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @dub/embed-react — @dub/embed-react is pinned at 0.0.18; registry.npmjs.org publishes 0.0.19 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @evyweb/ioctopus — @evyweb/ioctopus is pinned at 1.2.0; registry.npmjs.org publishes 1.4.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @formbricks/js — @formbricks/js is pinned at 4.3.0; registry.npmjs.org publishes 5.1.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @glidejs/glide — @glidejs/glide is pinned at 3.5.2; registry.npmjs.org publishes 3.7.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @hookform/error-message — @hookform/error-message is pinned at 2.0.0; registry.npmjs.org publishes 2.0.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @jetstreamapp/soql-parser-js — @jetstreamapp/soql-parser-js is pinned at 6.1.0; registry.npmjs.org publishes 8.1.2 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @jsforce/jsforce-node — @jsforce/jsforce-node is pinned at 3.10.10; registry.npmjs.org publishes 3.12.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @lexical/code — @lexical/code is pinned at 0.9.0; registry.npmjs.org publishes 0.52.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @lexical/html — @lexical/html is pinned at 0.9.0; registry.npmjs.org publishes 0.52.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @lexical/link — @lexical/link is pinned at 0.9.0; registry.npmjs.org publishes 0.52.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @lexical/list — @lexical/list is pinned at 0.9.0; registry.npmjs.org publishes 0.52.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @lexical/markdown — @lexical/markdown is pinned at 0.9.0; registry.npmjs.org publishes 0.52.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @lexical/react — @lexical/react is pinned at 0.9.0; registry.npmjs.org publishes 0.52.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @lexical/rich-text — @lexical/rich-text is pinned at 0.9.0; registry.npmjs.org publishes 0.52.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @lexical/selection — @lexical/selection is pinned at 0.9.0; registry.npmjs.org publishes 0.52.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @lexical/table — @lexical/table is pinned at 0.9.0; registry.npmjs.org publishes 0.52.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @lexical/utils — @lexical/utils is pinned at 0.9.0; registry.npmjs.org publishes 0.52.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @microsoft/microsoft-graph-types-beta — @microsoft/microsoft-graph-types-beta is pinned at 0.42.0-preview; registry.npmjs.org publishes 0.44.0-preview as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @nest-lab/throttler-storage-redis — @nest-lab/throttler-storage-redis is pinned at 1.0.0; registry.npmjs.org publishes 1.2.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Skipped (documented): (unnamed test) packages/features/bookings/lib/handleNewBooking/test/booking-limits.test.ts:298— Skipped with a documented reason — a deferral, not lazy debt: switched off by test.skipIf
Skipped (documented): CRM calendar events creation verification packages/features/bookings/lib/handleNewBooking/test/fresh-booking.test.ts:3861— Skipped with a documented reason — a deferral, not lazy debt: declared with test.todo — a placeholder that registers a name and runs nothing
Skipped (documented): Managed Event Type booking packages/features/bookings/lib/handleNewBooking/test/managed-event-type-booking.test.ts:10— Skipped with a documented reason — a deferral, not lazy debt: declared with test.todo — a placeholder that registers a name and runs nothing
Skipped (documented): Verify that the email should go to organizer as well as the team members apps/web/test/handlers/requestReschedule.test.ts:379— Skipped with a documented reason — a deferral, not lazy debt: declared with test.todo — a placeholder that registers a name and runs nothing
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.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
Run 01a17920-a3e8-720d-bc38-a0100996584c · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 440 · Warnings: 2215 · Recommendations: 1514 · Info: 181 — Appendix A · all findings · full markdown report.
Generated by Watchdog — deterministic code-health analysis. 26-10-2026 @ 16:52 UTC.
Downloadable artifacts
Machine-readable and reproducible from this commit + frozen rubric — drop them straight into a contract appendix, a CRA dossier, or a downstream SCA / VEX tool.