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

amruthpillai/reactive-resume

Measured 14 November 2026, 11:50 UTC, at code version e09a4a8

CAI score 47out of 100 Weak
CriticalWeakAdequateStrongExemplary
Up 3 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: 233,178 lines of product code in 25 projects, tests not counted · Estimated rebuild effort: about 2.2 person-years · Weakest lens: Architecture, 41

Findings by how serious they are

89 critical 1903 serious 118 minor

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

This survey was produced by

Assert small markCanine Code Analyzer
Producer
Canine Development
Analyzer
Canine Code Analyzer engine 1.0.0
Measured
14 November 2026, 11:50 UTC

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

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

85of 85 dimensions measured by tools.
2093of 2110 findings point to an exact file and line, so you can open each one in the code. The other 17 concern the repository as a whole, such as missing documentation.
85dimensions across 7 lenses, read from 233,178 lines of product code in 25 projects.
Chapters

Executive summary

amruthpillai/reactive-resume falls short of our standard for production, in part because it has loops of files that import each other. It scores 47 out of 100 and is rated Weak, and 77 of its 89 critical findings are security problems.

Architecture, at 41, is the weakest lens and counts most in the score. The best first step is separating the feature slices, worth about 5 points. Breaking the import cycles comes next, worth about 4 points. Raising Architecture to 70 would lift the score to about 53.

Sixty pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Seven secrets can leak from the build pipeline, and five settings leave the servers or containers unsafe. Pinning each tool to an exact version, limiting each secret to its own step and correcting the unsafe settings would close these risks. Fixing the weaknesses the scanner points to would fix the two security weaknesses in the code, and setting a waiting period for automatic updates would deal with the automatic dependency update that takes a new release at once. The four loops of files that import each other need breaking.

The product code is 233,178 lines, about €330,000 to rebuild.

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

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

If Architecture rose from 41 to 70, the lowest score rated Strong, the score would rise from 47 to about 53.

Code composition: what the lines of code are
Product code 72%Tests 28%
New since the last survey: 1383 findings

These 1383 critical or serious findings weren't in the previous survey, on 26 October 2026. The first 100 are listed here, and the findings file in the download package lists them all.

  • Cyclomatic Complexity · ai-consent.authorizeAiRequest (cyclomatic 129) apps/web/src/libs/orpc/ai-consent.ts
  • Cyclomatic Complexity · screen.TodayScreen (cyclomatic 88) apps/mobile/src/features/today/screen.tsx
  • Cyclomatic Complexity · offer-entry.OfferForm (cyclomatic 87) apps/web/src/features/career/offer-entry.tsx
  • Cyclomatic Complexity · pdf-lines.importLines (cyclomatic 84) packages/import/src/pdf-lines.ts
  • Cyclomatic Complexity · prepare-review.ReviewForm (cyclomatic 77) apps/web/src/features/career/workspace/prepare-review.tsx
  • Cyclomatic Complexity · new-document-dialog.NewDocument (cyclomatic 71) apps/web/src/features/documents/new-document-dialog.tsx
  • Cyclomatic Complexity · DescriptionScreen.DescriptionScreen (cyclomatic 68) apps/mobile/src/features/builder/description/DescriptionScreen.tsx
  • Cyclomatic Complexity · trash-page.TrashPage (cyclomatic 68) apps/web/src/features/trash/trash-page.tsx
  • Cyclomatic Complexity · offers.ScopedOffersScreen (cyclomatic 67) apps/mobile/src/features/career/offers.tsx
  • Cyclomatic Complexity · answer-library.AnswerLibrary (cyclomatic 67) apps/web/src/features/career/workspace/answer-library.tsx
  • Cyclomatic Complexity · page-canvas.ResumePageCanvas (cyclomatic 65) apps/web/src/routes/builder/$resumeId/-components/page-canvas.tsx
  • Cyclomatic Complexity · preparation.Preparation (cyclomatic 61) apps/web/src/features/career/workspace/preparation.tsx
  • Cyclomatic Complexity · pdf-lines.headingTest::test (cyclomatic 61) packages/import/src/pdf-lines.ts
  • Cyclomatic Complexity · actions.ScopedDocumentActionsScreen (cyclomatic 55) apps/mobile/src/features/documents/actions.tsx
  • Cyclomatic Complexity · pdf-lines.orderExperienceHeaders (cyclomatic 55) packages/import/src/pdf-lines.ts
  • Cyclomatic Complexity · SignInScreen.SignInScreen (cyclomatic 54) apps/mobile/src/features/auth/SignInScreen.tsx
  • Cyclomatic Complexity · import.ScopedImportScreen (cyclomatic 54) apps/mobile/src/features/documents/import.tsx
  • Cyclomatic Complexity · csv.mapCsvToApplications (cyclomatic 54) packages/schema/src/applications/csv.ts
  • Cyclomatic Complexity · schedules.ScheduleEditor (cyclomatic 53) apps/mobile/src/features/career/schedules.tsx
  • Cyclomatic Complexity · coach.ScopedCoachScreen (cyclomatic 52) apps/mobile/src/features/career/coach.tsx
  • Cyclomatic Complexity · profile.ApplicationProfile (cyclomatic 52) apps/web/src/features/settings/profile.tsx
  • Cyclomatic Complexity · SaveJobScreen.SaveJobScreen (cyclomatic 51) apps/mobile/src/features/applications/SaveJobScreen.tsx
  • Cyclomatic Complexity · proposals-screen.Proposals (cyclomatic 51) apps/mobile/src/features/builder/assistant/proposals-screen.tsx
  • Cyclomatic Complexity · messages.MessagesTab (cyclomatic 51) apps/web/src/features/career/workspace/messages.tsx
  • Cyclomatic Complexity · preferences.PreferencesContent (cyclomatic 49) apps/mobile/src/features/career/preferences.tsx
  • Cyclomatic Complexity · practise.PractiseTab (cyclomatic 49) apps/web/src/features/career/workspace/practise.tsx
  • Cyclomatic Complexity · proposal-list.ProposalItem (cyclomatic 49) apps/web/src/features/resume/editor/proposals/proposal-list.tsx
  • Cyclomatic Complexity · prototype.fillControlledForm (cyclomatic 48) tooling/autofill/prototype.ts
  • Cyclomatic Complexity · linking.parseDeepLink (cyclomatic 47) apps/mobile/src/data/linking.ts
  • Cyclomatic Complexity · overview.ApplicationOverview (cyclomatic 47) apps/web/src/features/career/workspace/overview.tsx
  • Cyclomatic Complexity · pdf-lines.projectSectionFields (cyclomatic 47) packages/import/src/pdf-lines.ts
  • Cyclomatic Complexity · assistant-screen.AssistantScreen (cyclomatic 46) apps/mobile/src/features/builder/assistant/assistant-screen.tsx
  • Cyclomatic Complexity · save-posting.SavePosting (cyclomatic 46) apps/web/src/features/assistant/save-posting.tsx
  • Cyclomatic Complexity · LayoutScreen.LayoutScreen (cyclomatic 45) apps/mobile/src/features/builder/design/LayoutScreen.tsx
  • Cyclomatic Complexity · search.ScopedSearchScreen (cyclomatic 45) apps/mobile/src/features/documents/search.tsx
  • Cyclomatic Complexity · to-html.convertNode (cyclomatic 45) packages/pdf/src/html/to-html.ts
  • Cyclomatic Complexity · store.createDraftStore.open (cyclomatic 44) apps/mobile/src/data/draft/store.ts
  • Cyclomatic Complexity · PrepScreen.PrepScreen (cyclomatic 44) apps/mobile/src/features/workspace/PrepScreen.tsx
  • Cyclomatic Complexity · provider-fields.ProviderFieldsForm (cyclomatic 44) apps/web/src/features/settings/ai/provider-fields.tsx
  • Cyclomatic Complexity · pdf-lines.headingTest (cyclomatic 44) packages/import/src/pdf-lines.ts
  • Cyclomatic Complexity · profile.ProfileDialog (cyclomatic 43) apps/web/src/features/settings/profile.tsx
  • Cyclomatic Complexity · CheckScreen.CheckScreen (cyclomatic 42) apps/mobile/src/features/builder/check/CheckScreen.tsx
  • Cyclomatic Complexity · ApplicationsScreen.ListView (cyclomatic 40) apps/mobile/src/features/applications/ApplicationsScreen.tsx
  • Cyclomatic Complexity · facts.FactsPage (cyclomatic 40) apps/web/src/features/career/knowledge/facts.tsx
  • Cyclomatic Complexity · proposal-list.ChangeSet (cyclomatic 39) apps/web/src/features/resume/editor/proposals/proposal-list.tsx
  • Cyclomatic Complexity · section-view.SectionOptions (cyclomatic 39) apps/web/src/features/resume/editor/write/section-view.tsx
  • Cyclomatic Complexity · coach-sheet.CoachSheetBody (cyclomatic 38) apps/web/src/features/career/workspace/coach-sheet.tsx
  • Cyclomatic Complexity · use-resume-import.useResumeImport.importFile (cyclomatic 38) apps/web/src/features/documents/import/use-resume-import.ts
  • Cyclomatic Complexity · picture-settings.PictureSettings (cyclomatic 38) apps/web/src/features/resume/editor/write/picture-settings.tsx
  • Cyclomatic Complexity · pdf-lines.splitExperienceItems (cyclomatic 38) packages/import/src/pdf-lines.ts
  • Cyclomatic Complexity · fields.TextField (cyclomatic 37) apps/mobile/src/ui/fields.tsx
  • Cyclomatic Complexity · apply.Checklist (cyclomatic 37) apps/web/src/features/career/workspace/apply.tsx
  • Cyclomatic Complexity · design-panel.DesignPanel (cyclomatic 37) apps/web/src/routes/builder/$resumeId/-components/design-panel.tsx
  • Cyclomatic Complexity · preview-screen.PreviewScreen (cyclomatic 36) apps/mobile/src/features/builder/preview/preview-screen.tsx
  • Cyclomatic Complexity · share-screen.ShareScreen (cyclomatic 36) apps/mobile/src/features/builder/share/share-screen.tsx
  • Cyclomatic Complexity · ProviderScreen.ScopedProviderScreen (cyclomatic 36) apps/mobile/src/features/settings/ProviderScreen.tsx
  • Cyclomatic Complexity · guest.invokeGuest (cyclomatic 35) apps/mobile/src/data/guest.ts
  • Cyclomatic Complexity · issues.describe (cyclomatic 35) apps/mobile/src/features/builder/check/issues.ts
  • Cyclomatic Complexity · EntryScreen.EntryScreen (cyclomatic 35) apps/mobile/src/features/builder/entry/EntryScreen.tsx
  • Cyclomatic Complexity · facts.ScopedFactsScreen (cyclomatic 35) apps/mobile/src/features/career/facts.tsx
  • Cyclomatic Complexity · InterviewSheet.InterviewForm (cyclomatic 34) apps/mobile/src/features/applications/InterviewSheet.tsx
  • Cyclomatic Complexity · letter-screen.LetterScreen (cyclomatic 34) apps/mobile/src/features/letters/letter-screen.tsx
  • Cyclomatic Complexity · improve.ImprovePanel (cyclomatic 34) apps/web/src/features/resume/editor/write/improve.tsx
  • Cyclomatic Complexity · trash.ScopedTrashScreen (cyclomatic 33) apps/mobile/src/features/documents/trash.tsx
  • Cyclomatic Complexity · contacts.ContactList (cyclomatic 33) apps/web/src/features/applications/components/detail/contacts.tsx
  • Cyclomatic Complexity · application-packet.PacketForm (cyclomatic 33) apps/web/src/features/career/workspace/application-packet.tsx
  • Cyclomatic Complexity · writing-tab.WritingTab (cyclomatic 33) apps/web/src/features/resume/editor/check/writing-tab.tsx
  • Cyclomatic Complexity · pdf-lines.wrappedRightCell (cyclomatic 33) packages/import/src/pdf-lines.ts
  • Cyclomatic Complexity · store.createDraftStore.flush (cyclomatic 32) apps/mobile/src/data/draft/store.ts
  • Cyclomatic Complexity · library.ScopedLibraryScreen (cyclomatic 32) apps/mobile/src/features/documents/library.tsx
  • Cyclomatic Complexity · resume-facts.ReviewResumeFacts (cyclomatic 32) apps/web/src/features/career/knowledge/resume-facts.tsx
  • Cyclomatic Complexity · offers.useCells.<returned closure> (cyclomatic 32) apps/web/src/features/career/offers.tsx
  • Cyclomatic Complexity · pdf-lines.educationRecords (cyclomatic 32) packages/import/src/pdf-lines.ts
  • Cyclomatic Complexity · store.createDraftStore.writeMetadata (cyclomatic 31) apps/mobile/src/data/draft/store.ts
  • Cyclomatic Complexity · menu-screen.ResumeMenu (cyclomatic 31) apps/mobile/src/features/builder/menu/menu-screen.tsx
  • Cyclomatic Complexity · Recorder.Recorder (cyclomatic 31) apps/mobile/src/features/workspace/Recorder.tsx
  • Cyclomatic Complexity · BottomSheet.BottomSheet (cyclomatic 31) apps/mobile/src/ui/BottomSheet.tsx
  • Cyclomatic Complexity · today.SchedulesPanel (cyclomatic 31) apps/web/src/features/career/today.tsx
  • Cyclomatic Complexity · write-panel.BodySection (cyclomatic 31) apps/web/src/routes/builder/letter/-components/write-panel.tsx
  • Cyclomatic Complexity · proposal-applications.saveProposalApplications (cyclomatic 31) packages/api/src/features/agent/proposal-applications.ts
  • Cyclomatic Complexity · resume.PublicResumeScreen (cyclomatic 30) apps/mobile/src/features/public/resume.tsx
  • Cyclomatic Complexity · messages.ReplyCard (cyclomatic 30) apps/web/src/features/career/workspace/messages.tsx
  • Cyclomatic Complexity · files.isValidFontFile (cyclomatic 30) packages/fonts/src/files.ts
  • Cyclomatic Complexity · pdf-lines.bodyColumns (cyclomatic 30) packages/import/src/pdf-lines.ts
  • Cyclomatic Complexity · check.checkDocs (cyclomatic 30) tooling/docs/check.mjs
  • Cyclomatic Complexity · ai-consent.authorizeAiRequest.result (cyclomatic 29) apps/mobile/src/api/ai-consent.ts
  • Cyclomatic Complexity · FitScreen.FitScreen (cyclomatic 29) apps/mobile/src/features/workspace/FitScreen.tsx
  • Cyclomatic Complexity · BoardDrag.BoardDrag (cyclomatic 29) apps/mobile/src/ui/BoardDrag.tsx
  • Cyclomatic Complexity · config.linkAnonymousAccount (cyclomatic 29) packages/auth/src/config.ts
  • Cyclomatic Complexity · use-application-actions.useMoveWithUndo.<returned closure> (cyclomatic 28) apps/web/src/features/applications/use-application-actions.ts
  • Cyclomatic Complexity · manage-lanes-sheet.ManageLanesSheet (cyclomatic 28) apps/web/src/features/applications/components/manage-lanes-sheet.tsx
  • Cyclomatic Complexity · question-card.QuestionCard (cyclomatic 28) apps/web/src/features/assistant/question-card.tsx
  • Cyclomatic Complexity · debrief.DebriefTab (cyclomatic 28) apps/web/src/features/career/workspace/debrief.tsx
  • Cyclomatic Complexity · chrome.usePageScale (cyclomatic 28) apps/web/src/features/resume/editor/chrome.tsx
  • Cyclomatic Complexity · letter-bar.LetterSaveStatus (cyclomatic 28) apps/web/src/routes/builder/letter/-components/letter-bar.tsx
  • Cyclomatic Complexity · pdf-lines.foldStackedHeaders (cyclomatic 28) packages/import/src/pdf-lines.ts
  • Cyclomatic Complexity · next-step.getNextStep (cyclomatic 28) packages/schema/src/applications/next-step.ts
  • Cyclomatic Complexity · ReorderList.ReorderList (cyclomatic 27) apps/mobile/src/ui/ReorderList.tsx
  • Cyclomatic Complexity · rows.ListRow (cyclomatic 27) apps/mobile/src/ui/rows.tsx
  • Cyclomatic Complexity · next-step.describeNextStep (cyclomatic 27) apps/web/src/features/applications/next-step.ts

We compare 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: 2479 findings

These 2479 critical or serious findings were in the previous survey, on 26 October 2026, and are gone from this one. The first 100 are listed here.

  • Cyclomatic Complexity · add-sheet.AddApplicationSheet (cyclomatic 122) apps/mobile/src/features/applications/add-sheet.tsx
  • Cyclomatic Complexity · new-document.NewDocument (cyclomatic 78) apps/mobile/src/features/documents/new-document.tsx
  • Cyclomatic Complexity · library.DocumentsLibrary (cyclomatic 75) apps/mobile/src/features/documents/library.tsx
  • Cyclomatic Complexity · practise.Session (cyclomatic 72) apps/mobile/src/features/workspace/tabs/practise.tsx
  • Cyclomatic Complexity · list-screen.ApplicationsList (cyclomatic 71) apps/mobile/src/features/applications/list-screen.tsx
  • Cyclomatic Complexity · parse.parseDeepLink (cyclomatic 68) apps/mobile/src/linking/parse.ts
  • Cyclomatic Complexity · provider-editor.ProviderForm (cyclomatic 60) apps/mobile/src/features/ai/provider-editor.tsx
  • Cyclomatic Complexity · chat-view.Conversation (cyclomatic 58) apps/mobile/src/features/assistant/chat-view.tsx
  • Cyclomatic Complexity · board-screen.Board (cyclomatic 55) apps/mobile/src/features/applications-board/board-screen.tsx
  • Cyclomatic Complexity · today.TodayScreen (cyclomatic 55) apps/mobile/src/features/career/today.tsx
  • Cyclomatic Complexity · link.LinkTab (cyclomatic 53) apps/mobile/src/features/share/link.tsx
  • Cyclomatic Complexity · interview-sheet.InterviewForm (cyclomatic 51) apps/mobile/src/features/application-detail/interview-sheet.tsx
  • Cyclomatic Complexity · html.parseRichText (cyclomatic 47) apps/mobile/src/features/public/html.ts
  • Cyclomatic Complexity · layout.ListRow (cyclomatic 46) apps/mobile/src/ui/layout.tsx
  • Cyclomatic Complexity · search-screen.SearchScreen (cyclomatic 46) apps/mobile/src/features/search/search-screen.tsx
  • Cyclomatic Complexity · shell.ContextColumn (cyclomatic 46) apps/web/src/features/career/workspace/shell.tsx
  • Cyclomatic Complexity · web-access.WebAccessSettings (cyclomatic 44) apps/mobile/src/features/ai/web-access.tsx
  • Cyclomatic Complexity · document-sheets.DocumentSheets (cyclomatic 44) apps/mobile/src/features/documents/document-sheets.tsx
  • Cyclomatic Complexity · page.ResumePage (cyclomatic 44) apps/mobile/src/preview/page.tsx
  • Cyclomatic Complexity · messages.ToolPartView (cyclomatic 42) apps/mobile/src/features/assistant/messages.tsx
  • Cyclomatic Complexity · index.DocumentMenu (cyclomatic 41) apps/mobile/src/features/document-menu/index.tsx
  • Cyclomatic Complexity · history.HistoryPanel (cyclomatic 41) apps/mobile/src/features/history/history.tsx
  • Cyclomatic Complexity · section-sheet.SectionSheet (cyclomatic 41) apps/mobile/src/features/write/section-sheet.tsx
  • Cyclomatic Complexity · offers.OfferCard (cyclomatic 39) apps/mobile/src/features/career/offers.tsx
  • Cyclomatic Complexity · page-canvas.PageCanvas (cyclomatic 39) apps/web/src/routes/builder/$resumeId/-components/page-canvas.tsx
  • Cyclomatic Complexity · assistant-screen.DocumentAssistantScreen (cyclomatic 38) apps/mobile/src/features/assistant/assistant-screen.tsx
  • Cyclomatic Complexity · design-pane.DesignPane (cyclomatic 37) apps/mobile/src/features/design/design-pane.tsx
  • Cyclomatic Complexity · import-file.importDocument (cyclomatic 37) apps/mobile/src/features/documents/import-file.ts
  • Cyclomatic Complexity · outline.Outline (cyclomatic 37) apps/mobile/src/features/write/outline.tsx
  • Cyclomatic Complexity · chat-view.Composer (cyclomatic 36) apps/mobile/src/features/assistant/chat-view.tsx
  • Cyclomatic Complexity · today.Schedules (cyclomatic 36) apps/web/src/features/career/today.tsx
  • Cyclomatic Complexity · layout-screen.LayoutScreen (cyclomatic 35) apps/mobile/src/features/design/layout-screen.tsx
  • Cyclomatic Complexity · share.LetterHistory (cyclomatic 34) apps/mobile/src/features/letters/share.tsx
  • Cyclomatic Complexity · calendar-screen.ApplicationCalendar (cyclomatic 32) apps/mobile/src/features/applications-board/calendar-screen.tsx
  • Cyclomatic Complexity · preferences.Preferences (cyclomatic 32) apps/mobile/src/features/career/preferences.tsx
  • Cyclomatic Complexity · parser.Parser (cyclomatic 32) apps/mobile/src/features/check/parser.tsx
  • Cyclomatic Complexity · apply.AnswerCard (cyclomatic 32) apps/mobile/src/features/workspace/tabs/apply.tsx
  • Cyclomatic Complexity · messages.ProposalCard (cyclomatic 32) apps/mobile/src/features/workspace/tabs/messages.tsx
  • Cyclomatic Complexity · compare-resume.hasDuplicateJsonMembers (cyclomatic 31) tooling/recovery/compare-resume.ts
  • Cyclomatic Complexity · store.createDraftStore.open (cyclomatic 30) apps/mobile/src/draft/store.ts
  • Cyclomatic Complexity · issues.describeFinding (cyclomatic 30) apps/mobile/src/features/check/issues.ts
  • Cyclomatic Complexity · writing.Writing (cyclomatic 30) apps/mobile/src/features/check/writing.tsx
  • Cyclomatic Complexity · library.DocumentItem (cyclomatic 30) apps/mobile/src/features/documents/library.tsx
  • Cyclomatic Complexity · share.LetterDownload (cyclomatic 30) apps/mobile/src/features/letters/share.tsx
  • Cyclomatic Complexity · entry-card.EntryCard (cyclomatic 30) apps/web/src/features/resume/editor/write/entry-card.tsx
  • Cyclomatic Complexity · overlays.Sheet (cyclomatic 29) apps/mobile/src/ui/overlays.tsx
  • Cyclomatic Complexity · sections.NextStepCard (cyclomatic 29) apps/mobile/src/features/application-detail/sections.tsx
  • Cyclomatic Complexity · schedule-sheet.ScheduleForm (cyclomatic 29) apps/mobile/src/features/career/schedule-sheet.tsx
  • Cyclomatic Complexity · screen.CheckScreen (cyclomatic 29) apps/mobile/src/features/check/screen.tsx
  • Cyclomatic Complexity · builder-chrome.Frame (cyclomatic 29) apps/mobile/src/shell/builder-chrome.tsx
  • Cyclomatic Complexity · picture-screen.PictureScreen (cyclomatic 28) apps/mobile/src/features/write/picture-screen.tsx
  • Cyclomatic Complexity · store.createDraftStore.flush (cyclomatic 27) apps/mobile/src/draft/store.ts
  • Cyclomatic Complexity · public-resume.PublicResume (cyclomatic 27) apps/mobile/src/features/public/public-resume.tsx
  • Cyclomatic Complexity · shell.WorkspaceScreen (cyclomatic 27) apps/mobile/src/features/workspace/shell.tsx
  • Cyclomatic Complexity · offers.ComparisonTable (cyclomatic 27) apps/web/src/features/career/offers.tsx
  • Cyclomatic Complexity · csv.mapCsvToApplications (cyclomatic 26) apps/web/src/features/applications/csv.ts
  • Cyclomatic Complexity · markdown.parseBlocks (cyclomatic 25) apps/mobile/src/features/assistant/markdown.tsx
  • Cyclomatic Complexity · coach-screen.CoachScreen (cyclomatic 25) apps/mobile/src/features/assistant/coach-screen.tsx
  • Cyclomatic Complexity · offers.useCells (cyclomatic 25) apps/web/src/features/career/offers.tsx
  • Cyclomatic Complexity · section-row.SectionMenu (cyclomatic 25) apps/web/src/features/resume/editor/write/section-row.tsx
  • Cyclomatic Complexity · document.useLetterAssistantDocument (cyclomatic 24) apps/mobile/src/features/assistant/document.ts
  • Cyclomatic Complexity · resume-reflow.EntryView (cyclomatic 24) apps/web/src/features/resume/public/resume-reflow.tsx
  • Cyclomatic Complexity · date-field.WallClockField (cyclomatic 23) apps/mobile/src/features/application-detail/date-field.tsx
  • Cyclomatic Complexity · facts.Facts (cyclomatic 23) apps/mobile/src/features/career/facts.tsx
  • Cyclomatic Complexity · thumbnail.Thumbnail (cyclomatic 23) apps/mobile/src/features/documents/thumbnail.tsx
  • Cyclomatic Complexity · download.DownloadTab (cyclomatic 23) apps/mobile/src/features/share/download.tsx
  • Cyclomatic Complexity · pdf-viewer.PdfViewer (cyclomatic 23) apps/web/src/features/resume/public/pdf-viewer.tsx
  • Cyclomatic Complexity · fetch-prebuilt.main (cyclomatic 23) packages/forme-native/scripts/fetch-prebuilt.mjs
  • Cyclomatic Complexity · preferences.PreferencesScreen (cyclomatic 22) apps/mobile/app/(tabs)/settings/preferences.tsx
  • Cyclomatic Complexity · button.Button (cyclomatic 22) apps/mobile/src/ui/button.tsx
  • Cyclomatic Complexity · host.server (cyclomatic 22) apps/mobile/scripts/parity/host.mts
  • Cyclomatic Complexity · provider-list.ProviderRow (cyclomatic 22) apps/mobile/src/features/ai/provider-list.tsx
  • Cyclomatic Complexity · page.CheckPage (cyclomatic 22) apps/mobile/src/features/check/page.tsx
  • Cyclomatic Complexity · checker.AtsChecker (cyclomatic 21) apps/mobile/src/features/ats-checker/checker.tsx
  • Cyclomatic Complexity · public-resume.PublicResumePage (cyclomatic 21) apps/web/src/features/resume/public/public-resume.tsx
  • Cyclomatic Complexity · job-match.JobMatch (cyclomatic 20) apps/mobile/src/features/check/job-match.tsx
  • Cyclomatic Complexity · use-review-prompt.useReviewPrompt (cyclomatic 20) apps/mobile/src/features/reviews/use-review-prompt.ts
  • Cyclomatic Complexity · model.resolveDrop (cyclomatic 20) apps/mobile/src/features/write/model.ts
  • Cyclomatic Complexity · today.NeedsYou (cyclomatic 20) apps/web/src/features/career/today.tsx
  • Cyclomatic Complexity · layout.Banner (cyclomatic 19) apps/mobile/src/ui/layout.tsx
  • Cyclomatic Complexity · checker.Result (cyclomatic 19) apps/mobile/src/features/ats-checker/checker.tsx
  • Cyclomatic Complexity · outline.SectionRow (cyclomatic 19) apps/mobile/src/features/write/outline.tsx
  • Cyclomatic Complexity · new-document-dialog.useResumeImport.importFile (cyclomatic 19) apps/web/src/features/documents/new-document-dialog.tsx
  • Cyclomatic Complexity · section-row.SectionRow (cyclomatic 19) apps/web/src/features/resume/editor/write/section-row.tsx
  • Cyclomatic Complexity · catalog.loadModelSuggestions (cyclomatic 18) apps/mobile/src/features/ai/catalog.ts
  • Cyclomatic Complexity · schedule-sheet.ScheduleForm::save (cyclomatic 18) apps/mobile/src/features/career/schedule-sheet.tsx
  • Cyclomatic Complexity · profile.ProfileField (cyclomatic 18) apps/mobile/src/features/settings/profile.tsx
  • Cyclomatic Complexity · profile.ProfileEditor (cyclomatic 18) apps/mobile/src/features/settings/profile.tsx
  • Cyclomatic Complexity · download.DownloadTab::download (cyclomatic 18) apps/mobile/src/features/share/download.tsx
  • Cyclomatic Complexity · state.createAutosave.send (cyclomatic 18) apps/mobile/src/features/workspace/state.ts
  • Cyclomatic Complexity · shell.TabBadges (cyclomatic 18) apps/mobile/src/features/workspace/shell.tsx
  • Cyclomatic Complexity · debrief.DebriefForm (cyclomatic 18) apps/mobile/src/features/workspace/tabs/debrief.tsx
  • Cyclomatic Complexity · open.redirectSystemPath (cyclomatic 18) apps/mobile/src/linking/open.ts
  • Cyclomatic Complexity · app-tabs.SidebarItem (cyclomatic 18) apps/mobile/src/shell/app-tabs.tsx
  • Cyclomatic Complexity · link-tab.AddressField (cyclomatic 18) apps/web/src/features/resume/share/link-tab.tsx
  • Cyclomatic Complexity · config.verifyOAuthToken (cyclomatic 18) packages/auth/src/config.ts
  • Cyclomatic Complexity · compare-resume.parseRequest (cyclomatic 18) tooling/recovery/compare-resume.ts
  • Cyclomatic Complexity · overlays.DialogAction (cyclomatic 17) apps/mobile/src/ui/overlays.tsx
  • Cyclomatic Complexity · document.useResumeAssistantDocument (cyclomatic 17) apps/mobile/src/features/assistant/document.ts
  • Cyclomatic Complexity · job-match.JobMatch::link (cyclomatic 17) apps/mobile/src/features/check/job-match.tsx
Rebuild cost: about €330,000 · Estimate
Cost to rebuild€110,000 to €540,000, for 1,801 to 5,714 hours of work, about 2.2 person-years for 1 to 5 engineers
Difficulty of the problemStandard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor×0.7 at a score of 47. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
SizeLarge: 233,178 lines of product code
What it is notNot a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one.

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

Top priorities

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

1
Keep slices independent: share cross-slice needs via an explicit contract/shared-kernel, not direct references between slices.
Raises the score by about 5 points · Medium effort · Slice cohesion
2
Break each cycle by extracting the shared piece into a module both sides can import.
Raises the score by about 4 points · Medium effort · Circular Imports
3
Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion.
Raises the score by about 2 points · Low effort · Project Cohesion

Diagnosis: what the measurements show together

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

Where the investment is most exposed · Value at risk
This code would cost about €330,000 to build again, about 2.2 person-years of work. Its weakest lens is Architecture, at 41 (Weak). Architecture is about whether the structure holds up as the product grows, and when the structure is weak, a change in one place ripples into many others. Because the weakest lens counts most in the score, work on Architecture also moves the score most.
Based on: the rebuild estimate · the Architecture grade · how much each lens counts
What to do: Start with the Architecture actions in Top priorities.
If you do one thing first · First action
Keep slices independent: share cross-slice needs via an explicit contract/shared-kernel, not direct references between slices. Of all the actions in this report, it raises the score most for the work it takes: about 5 points for medium effort. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
What hard-to-read code costs each year · Cost
Four dimensions measure how easy the code is to work in: two measure how tangled its logic is, one how much of it is copied, and one how well each part sticks to a single job. In this codebase they average 4.7 out of 10. Code at that level is slower to change than clean code, and we estimate the extra work at 8% to 19% on every change. The history of the code shows how much it changes: about 7,283,120 lines over the last 90 days, which is about 29,537,098 lines a year. At that pace, the extra work comes to an estimated 6153.6 to 36921.4 engineer-days a year, and it grows as more code changes.
How this is estimated: The number of changed lines is measured from the history of the code. The rest rests on two assumptions of our own: code scoring 8 out of 10 or more adds no extra work, and each point below 8 adds 2.5% to 5.6% to every change, never less than 2% to 5% and never more than 40% to 60% in all; and an engineer changes 150 to 400 lines in a day. The result is a range for planning, not a measurement.
Based on: Cyclomatic Complexity · Cognitive Complexity · Cohesion (LCOM4) · the code's change history
What to do: Start with the files listed under Churn × Complexity Hotspots, which change often and are hard to read, because that is where the extra work is paid most often.

Architecture — module dependency graph

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

arch @reactive-resume/ai ai @reactive-resume/resume resume @reactive-resume/ai->@reactive-resume/resume @reactive-resume/schema schema @reactive-resume/ai->@reactive-resume/schema @reactive-resume/utils utils @reactive-resume/ai->@reactive-resume/utils @reactive-resume/api api @reactive-resume/api->@reactive-resume/ai @reactive-resume/auth auth @reactive-resume/api->@reactive-resume/auth @reactive-resume/db db @reactive-resume/api->@reactive-resume/db @reactive-resume/docx docx @reactive-resume/api->@reactive-resume/docx @reactive-resume/email email @reactive-resume/api->@reactive-resume/email @reactive-resume/env env @reactive-resume/api->@reactive-resume/env @reactive-resume/import import @reactive-resume/api->@reactive-resume/import @reactive-resume/odt odt @reactive-resume/api->@reactive-resume/odt @reactive-resume/pdf pdf @reactive-resume/api->@reactive-resume/pdf @reactive-resume/api->@reactive-resume/resume @reactive-resume/api->@reactive-resume/schema @reactive-resume/api->@reactive-resume/utils @reactive-resume/auth->@reactive-resume/db @reactive-resume/auth->@reactive-resume/email @reactive-resume/auth->@reactive-resume/env @reactive-resume/auth->@reactive-resume/utils @reactive-resume/db->@reactive-resume/env @reactive-resume/db->@reactive-resume/schema @reactive-resume/db->@reactive-resume/utils @reactive-resume/docx->@reactive-resume/resume @reactive-resume/docx->@reactive-resume/schema @reactive-resume/docx->@reactive-resume/utils @reactive-resume/email->@reactive-resume/env @reactive-resume/email->@reactive-resume/utils @reactive-resume/env->@reactive-resume/ai @reactive-resume/env->@reactive-resume/utils @reactive-resume/fonts fonts @reactive-resume/fonts->@reactive-resume/utils @reactive-resume/import->@reactive-resume/resume @reactive-resume/import->@reactive-resume/schema @reactive-resume/import->@reactive-resume/utils @reactive-resume/mcp mcp @reactive-resume/mcp->@reactive-resume/ai @reactive-resume/mcp->@reactive-resume/api @reactive-resume/mcp->@reactive-resume/env @reactive-resume/mcp->@reactive-resume/schema @reactive-resume/odt->@reactive-resume/resume @reactive-resume/odt->@reactive-resume/schema @reactive-resume/odt->@reactive-resume/utils @reactive-resume/pdf->@reactive-resume/fonts @reactive-resume/pdf->@reactive-resume/resume @reactive-resume/pdf->@reactive-resume/schema @reactive-resume/pdf->@reactive-resume/utils @reactive-resume/resume->@reactive-resume/schema @reactive-resume/resume->@reactive-resume/utils @reactive-resume/schema->@reactive-resume/utils @reactive-resume/tooling tooling @reactive-resume/tooling->@reactive-resume/email @reactive-resume/tooling->@reactive-resume/fonts @reactive-resume/tooling->@reactive-resume/import @reactive-resume/tooling->@reactive-resume/pdf @reactive-resume/tooling->@reactive-resume/schema @reactive-resume/tooling->@reactive-resume/utils @reactive-resume/ui ui @reactive-resume/ui->@reactive-resume/utils mobile mobile mobile->@reactive-resume/ai mobile->@reactive-resume/api mobile->@reactive-resume/import mobile->@reactive-resume/pdf mobile->@reactive-resume/resume mobile->@reactive-resume/schema mobile->@reactive-resume/utils server server server->@reactive-resume/api server->@reactive-resume/auth server->@reactive-resume/db server->@reactive-resume/env server->@reactive-resume/mcp server->@reactive-resume/pdf server->@reactive-resume/resume server->@reactive-resume/schema server->@reactive-resume/utils web web web->@reactive-resume/ai web->@reactive-resume/api web->@reactive-resume/auth web->@reactive-resume/docx web->@reactive-resume/fonts web->@reactive-resume/import web->@reactive-resume/odt web->@reactive-resume/pdf web->@reactive-resume/resume web->@reactive-resume/schema web->@reactive-resume/ui web->@reactive-resume/utils __more__ +3 more projects

Architecture: which parts of the code depend on which

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

446 modules, with 153 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; 406 more are left out to keep it readable.

Which modules use which. The module on each row uses the module in each column, and the number counts the pairs of types that connect them. A cell above the diagonal is part of a loop.
uses →1 apps.mobile.src.data.consent2 apps.mobile.src.features.builder.design.TemplateScreen3 apps.mobile.src.features.builder.design.presets4 apps.mobile.src.features.builder.download.export-file5 apps.mobile.src.features.builder.shared.model6 apps.mobile.src.ui.tokens7 apps.web.src.features.homepage.remember8 apps.web.src.features.resume.editor.store9 packages.db.src.client10 packages.fonts.src11 packages.resume.src12 packages.resume.src.ats-pdf.types13 packages.resume.src.ats.types14 packages.resume.src.stylesheet15 packages.schema.src.applications.next-step16 packages.schema.src.applications.stage-baselines17 packages.utils.src.locale18 apps.mobile.src.data19 apps.mobile.src.dev.storyboard20 apps.mobile.src.features.builder.check21 apps.mobile.src.features.builder.shared22 apps.mobile.src.features.public23 apps.mobile.src.features.settings24 apps.mobile.src.features.workspace25 apps.mobile.src.ui26 apps.web.src.features.applications27 apps.web.src.features.assistant28 apps.web.src.features.ats-checker29 apps.web.src.features.career30 apps.web.src.features.letters31 apps.web.src.features.resume.editor32 apps.web.src.features.resume.editor.check33 apps.web.src.features.resume.editor.write34 apps.web.src.libs35 packages.api.src.features.agent36 packages.api.src.features.resume37 packages.api.src.features.storage38 packages.import.src39 packages.resume.src.ats40 packages.utils.src
1 apps.mobile.src.data.consent
2 apps.mobile.src.features.builder.design.TemplateScreen
3 apps.mobile.src.features.builder.design.presets
4 apps.mobile.src.features.builder.download.export-file
5 apps.mobile.src.features.builder.shared.model
6 apps.mobile.src.ui.tokens
7 apps.web.src.features.homepage.remember
8 apps.web.src.features.resume.editor.store
9 packages.db.src.client
10 packages.fonts.src
11 packages.resume.src
12 packages.resume.src.ats-pdf.types
13 packages.resume.src.ats.types
14 packages.resume.src.stylesheet
15 packages.schema.src.applications.next-step
16 packages.schema.src.applications.stage-baselines
17 packages.utils.src.locale
18 apps.mobile.src.data21
19 apps.mobile.src.dev.storyboard1
20 apps.mobile.src.features.builder.check1
21 apps.mobile.src.features.builder.shared4
22 apps.mobile.src.features.public1
23 apps.mobile.src.features.settings2
24 apps.mobile.src.features.workspace1
25 apps.mobile.src.ui2
26 apps.web.src.features.applications1
27 apps.web.src.features.assistant1
28 apps.web.src.features.ats-checker2
29 apps.web.src.features.career1
30 apps.web.src.features.letters1
31 apps.web.src.features.resume.editor1
32 apps.web.src.features.resume.editor.check1
33 apps.web.src.features.resume.editor.write31
34 apps.web.src.libs11
35 packages.api.src.features.agent2
36 packages.api.src.features.resume3
37 packages.api.src.features.storage1
38 packages.import.src1
39 packages.resume.src.ats2
40 packages.utils.src1
Uses a module listed above itPart of a loopThe module itself
1 apps.mobile.src.data.consent2 apps.mobile.src.features.builder.design.TemplateScreen3 apps.mobile.src.features.builder.design.presets4 apps.mobile.src.features.builder.download.export-file5 apps.mobile.src.features.builder.shared.model6 apps.mobile.src.ui.tokens7 apps.web.src.features.homepage.remember8 apps.web.src.features.resume.editor.store9 packages.db.src.client10 packages.fonts.src11 packages.resume.src12 packages.resume.src.ats-pdf.types13 packages.resume.src.ats.types14 packages.resume.src.stylesheet15 packages.schema.src.applications.next-step16 packages.schema.src.applications.stage-baselines17 packages.utils.src.locale18 apps.mobile.src.data19 apps.mobile.src.dev.storyboard20 apps.mobile.src.features.builder.check21 apps.mobile.src.features.builder.shared22 apps.mobile.src.features.public23 apps.mobile.src.features.settings24 apps.mobile.src.features.workspace25 apps.mobile.src.ui26 apps.web.src.features.applications27 apps.web.src.features.assistant28 apps.web.src.features.ats-checker29 apps.web.src.features.career30 apps.web.src.features.letters31 apps.web.src.features.resume.editor32 apps.web.src.features.resume.editor.check33 apps.web.src.features.resume.editor.write34 apps.web.src.libs35 packages.api.src.features.agent36 packages.api.src.features.resume37 packages.api.src.features.storage38 packages.import.src39 packages.resume.src.ats40 packages.utils.srcapps.mobile.src.data.consent1apps.mobile.src.features.builder.design.TemplateScreen2apps.mobile.src.features.builder.design.presets3apps.mobile.src.features.builder.download.export-file4apps.mobile.src.features.builder.shared.model5apps.mobile.src.ui.tokens6apps.web.src.features.homepage.remember7apps.web.src.features.resume.editor.store8packages.db.src.client9packages.fonts.src10packages.resume.src11packages.resume.src.ats-pdf.types12packages.resume.src.ats.types13packages.resume.src.stylesheet14packages.schema.src.applications.next-step15packages.schema.src.applications.stage-baselines16packages.utils.src.locale17apps.mobile.src.data18apps.mobile.src.dev.storyboard19apps.mobile.src.features.builder.check20apps.mobile.src.features.builder.shared21apps.mobile.src.features.public22apps.mobile.src.features.settings23apps.mobile.src.features.workspace24apps.mobile.src.ui25apps.web.src.features.applications26apps.web.src.features.assistant27apps.web.src.features.ats-checker28apps.web.src.features.career29apps.web.src.features.letters30apps.web.src.features.resume.editor31apps.web.src.features.resume.editor.check32apps.web.src.features.resume.editor.write33apps.web.src.libs34packages.api.src.features.agent35packages.api.src.features.resume36packages.api.src.features.storage37packages.import.src38packages.resume.src.ats39packages.utils.src4021114121211211113111231121+406 more modules (most-connected shown)

At a glance — Code Health · 52% · Adequate · gated by D1, D2, X5 ·

At a glance — Architecture · 41% · Weak · gated by R9, AX7 ·

At a glance — Maturity · 85% · Strong ·

At a glance — Readiness · 49% · Weak · gated by P3 ·

At a glance — Security · 56% · Adequate · gated by D29, C1 ·

At a glance — Accessibility · 58% · Adequate · gated by AC4 ·

At a glance — Performance · 60% · Adequate ·

Security & Compliance — OWASP Top-10 mapping

Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).

OWASP categoryFindingsSeverity
A05:2025 — Injection79High / Critical
A03:2025 — Software Supply Chain Failures11High / Critical
A02:2025 — Security Misconfiguration11High / Critical
A07:2025 — Authentication Failures2High / Critical
A01:2025 — Broken Access Control1Medium

Roadmap

Top priorities: Keep slices independent: share cross-slice needs via an explicit contract/shared-kernel, not direct references between slices; Break each cycle by extracting the shared piece into a module both sides can import; Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion.

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

Do thisHelpsEffortDimension
Keep slices independent: share cross-slice needs via an explicit contract/shared-kernel, not direct references between slices.+4.8 ptsMediumSlice cohesion
Break each cycle by extracting the shared piece into a module both sides can import.+4.5 ptsMediumCircular Imports
Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion.+2.1 ptsLowProject Cohesion
Resolve the 5 Off the main sequence finding(s) in Coupling.+1.1 ptsLowCoupling
Fix the listed violations: import through public entries (package exports / slice index), never reach into another layer or package's internals.+1.8 ptsMediumImport Boundaries
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.+1.7 ptsMediumSecurity & performance tooling
Document RTO/RPO and a tested restore procedure (a backup config alone isn't disaster recovery).+1.3 ptsMediumDR & Backup
Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.+1.3 ptsMediumDependency Hygiene

File quality

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

FileScoreBandWorst signal
REDACTED0.7SlopStatic Analysis (SAST): High: REDACTED
REDACTED4.1MixedIaC & Container Security: High IaC: REDACTED
REDACTED4.4MixedStatic Analysis (SAST): High: REDACTED
REDACTED4.4MixedStatic Analysis (SAST): High: REDACTED
REDACTED4.8MixedStatic Analysis (SAST): High: REDACTED
REDACTED4.8MixedIaC & Container Security: High IaC: REDACTED
REDACTED5.1MixedStatic Analysis (SAST): High: REDACTED
REDACTED5.1MixedDependency Vulnerabilities: High CVE: REDACTED
REDACTED5.4MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED5.4MixedDependency Vulnerabilities: Medium CVE: REDACTED
REDACTED5.8MixedStatic Analysis (SAST): High: REDACTED
apps/mobile/src/features/letters/letter-screen.tsx6.9MixedCyclomatic Complexity: letter-screen.LetterScreen (cyclomatic 34)
packages/api/src/features/applications/service.ts6.9MixedCyclomatic Complexity: service.recordSentResume (cyclomatic 24)
apps/web/src/features/career/workspace/messages.tsx7.0MixedCyclomatic Complexity: messages.ProposalCard (cyclomatic 91)
packages/resume/src/stylesheet/cascade.ts7.0MixedCyclomatic Complexity: cascade.resolveStylesheet (cyclomatic 85)
packages/import/src/pdf-lines.ts7.0MixedCyclomatic Complexity: pdf-lines.importLines (cyclomatic 84)
apps/web/src/features/assistant/conversation.tsx7.0MixedCyclomatic Complexity: conversation.Conversation (cyclomatic 71)
apps/web/src/features/career/offers.tsx7.0MixedCyclomatic Complexity: offers.OffersPage (cyclomatic 50)
apps/mobile/src/data/draft/store.ts7.0MixedCyclomatic Complexity: store.createDraftStore.open (cyclomatic 44)
packages/pdf/src/forme/render.ts7.0MixedCyclomatic Complexity: render.renderResumeElement (cyclomatic 42)

How the grades work

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

Critical — 89

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

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

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

Could not be resolved — 7

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

Methodology & how to trust this report

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

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

What we checked — 85 dimensions across the health lenses
D1D2D3D5D6D7D10D12D13D14D15D17D19D20D23D24D26D27D28D29D30D31D32D34D35D36D37D43D44AC1AC2AC3AC4AC5AC6AX10AX3AX5AX6AX7C1C2C4C5GD1IC1M1M2M3M4P1P10P2P3P4P5P6P8PF3R1R10R11R2R3R4R6R7R8R9S1X1X12X13X14X16X17X2X21X24X25X28X29X3X30X5

Each chip is a dimension scored from real signals across architecture, testing, dependencies, security & compliance, documentation, git-history and code quality — in one coherent pass. A surface report typically covers a handful.

How to trust any code-health report — three questions
  1. Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 2093 of 2110 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
  2. Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
  3. Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.

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

Tools & methods

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

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

Every finding is locatable in findings.md. Run 01a1d9e5-235b-7748-86fd-14cf705c82a6.

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

Run transparency — what happened this run

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

  • D7 Architectural Integrity — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. These records DO declare how the decision is enforced; FileSystemAdrInventoryBuilder.ParseEnforcement maps a fixed vocabulary (`prose`, `test`, `analyzer`, `mechanical`, `judgment`, `judgement`, `process`, `not-applicable`) and these values are outside it. Each was therefore treated as Unclassified: counted into the mechanizable set, but excluded from the scored set because nothing claimed it enforceable. That exclusion rests on our word list, not on the repository. Affected ADR(s): .agents/docs/decisions/0004-multi-client-workspaces.md. You can widen what we reach: no action is needed from this repository — the gap is in our parser. The values above are reported so the vocabulary can be added; declaring `enforcement: analyzer`, `test`, `prose` or `not-applicable` alongside your own grading would settle these ADRs immediately.
  • D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: the JavaScript/TypeScript half could not be measured — the dependency install for the repository root failed in the analyzer sandbox (ERR_PNPM_BROKEN_LOCKFILE  The lockfile at "REDACTED" is broken: expected a single document in the stream, but found more), so the suite never ran. Coverage is excluded from the score rather than counted as a near-zero. This is OUR limitation, not a defect in the repo.
  • D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability NOT MEASURED: the JavaScript/TypeScript suite could not be re-run in the analyzer sandbox — the dependency install for the repository root failed in the analyzer sandbox (ERR_PNPM_BROKEN_LOCKFILE  The lockfile at "REDACTED" is broken: expected a single document in the stream, but found more), so the suite never ran. This is OUR limitation, not a defect in the repo — it is excluded from the score.
  • D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability for the vitest suite in the repository root was NOT MEASURED: the dependency install for the repository root failed in the analyzer sandbox (ERR_PNPM_BROKEN_LOCKFILE  The lockfile at "REDACTED" is broken: expected a single document in the stream, but found more), so the suite never ran. This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
  • D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability for the jest suite in apps/mobile/ was NOT MEASURED: the dependency install for apps/mobile/ failed in the analyzer sandbox (ERR_PNPM_BROKEN_LOCKFILE  The lockfile at "REDACTED" is broken: expected a single document in the stream, but found more), so the suite never ran. This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
  • D14 License Compliance — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares package.json, but the licence verdict published here was taken over its gem dependencies. Nothing was read about its npm dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
  • D15 Churn × Complexity Hotspots — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. A hotspot's complexity is meant to be the worst body its churn actually touched. For apps/mobile/src/ui/text.tsx that could not be established — the complexity reader for the file reports no body extents, or the history carries no per-line attribution — so the row quotes the file's worst body, which the counted changes may never have touched. The churn count is unaffected.
  • D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (255 contributor(s) across 7334 commit(s) sampled, automation and bot accounts excluded). One of them holds 89% of the history; the other 254 hold 0% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
  • D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 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.
  • D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository publishes a package — a Claude Code plugin, declared by plugins/reactive-resume/.claude-plugin/plugin.json — so it DOES have an intentionally-exposed surface: the commands, skills, agents and hooks the plugin contributes to its host, which consumers reach by name. D22 collects code-API surfaces (type and member signatures) only, and has no collector for a plugin's contribution surface, so the consistency of that surface was not judged. That is OUR side and it is a COLLECTOR gap, not an environment fault — no change to the scan image can close it.
  • D23 Boundary Type-Coupling — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind measured 0/40 valid on a seeded held-out sample of its rows on 98 C# repositories (docs/plans/deterministic-engine/adjudication/P5c-D23-units.md, "Version 1 ON MAIN"): the noise rows were dependencies on layer folders, shared cores and grouping folders read as contexts. By the pre-registered fallback (PREREGISTRATION v37) it publishes no row until version 4 passes its gate. The candidates are counted here, not reported as findings, and the score does not include them.
  • D24 Comment Value — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
  • D32 Data Compliance (PII/GDPR) — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. `apps/mobile/src/api/client.ts`, `apps/mobile/src/data/auth-options.ts`, `apps/mobile/src/features/applications/ApplicationsScreen.tsx`, `apps/mobile/src/features/applications/model.ts`, `apps/mobile/src/features/builder/description/DescriptionScreen.tsx`, … (+105 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.
  • AX1 Captive dependencies — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads Microsoft.Extensions.DependencyInjection registrations in C# and Spring beans in Java/Kotlin only, and this repository defines its own container in tooling/autofill/fixture.ts, whose lifetimes are not modelled 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.
  • AX7 Slice cohesion — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 608 further occurrence(s) are not listed individually; the score already reflects all 648.
  • AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DockerCompose (REDACTED). compose up failed (exit 17 — an image could not be built) — failed to solve: process "/bin/sh -c pnpm runtime set node ${NODE_VERSION} -g --config.store-dir=/pnpm/runtime-store" did not complete successfully: exit code: 1; runtime evidence skipped.
  • M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
  • R10 Code Duplication — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 498 further occurrence(s) are not listed individually; the score already reflects all 538.
  • R2 Cyclomatic Complexity — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 668 further occurrence(s) are not listed individually; the score already reflects all 708.
  • R3 Large Files — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 97 further occurrence(s) are not listed individually; the score already reflects all 137.
  • R4 Test Coverage — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 174 further occurrence(s) are not listed individually; the score already reflects all 214.
  • R7 Dead Code — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 222 further occurrence(s) are not listed individually; the score already reflects all 262.
  • X10 Duplicated predicate — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 75 further occurrence(s) are not listed individually; the score already reflects all 115.
  • X3 Exception handling — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 65 further occurrence(s) are not listed individually; the score already reflects all 105.
  • X4 Structured logging — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Python, PHP, Dart, Ruby, Scala and Rust source only, and no C# was loaded, and this repository's JavaScript/TypeScript, Python and PHP log through no library that carries a message's values as fields (pino, winston, bunyan, tslog, LogTape, roarr; Python's logging, structlog; PHP's PSR-3 loggers), so its log calls cannot be judged, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.

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

Limitations & what we did not check

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

Per-dimension blind spots

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

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

Dimensions

D1 · Cyclomatic Complexity2.0 / 10Critical✓ Tool-verified

What it measures: How tangled the control flow is — methods with many branches are hard to test and change.

Method: Cyclomatic complexity per method (1 + decision points), computed exhaustively across production source; test projects separated by convention. Deterministic.

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

419 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was add-application-dialog.AddApplicationForm at 140. A further 10 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 ats-messages.getPdfFindingMessage at 78 — they are counted neither in the figure above nor in this dimension's score. 6 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: apps/mobile/src/features/public/ats-messages.ts (ats-messages.getPdfFindingMessage at 78), apps/web/src/features/auth/pages/error.tsx (error.getErrorMessage at 22), packages/utils/src/locale.ts (locale.getLocaleScript at 21), apps/web/src/features/resume/editor/write/entries.tsx (entries.EntryFields at 18), apps/web/src/features/resume/editor/write/model.ts (model.describeEntry at 18), and 1 more not listed here. 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.

add-application-dialog.AddApplicationForm (cyclomatic 140)apps/web/src/features/applications/components/add-application-dialog.tsx:188
ai-consent.authorizeAiRequest (cyclomatic 129)apps/web/src/libs/orpc/ai-consent.ts:13
practise.Session (cyclomatic 121)apps/web/src/features/career/workspace/practise.tsx:373
config.getAuthConfig (cyclomatic 109)packages/auth/src/config.ts:797
ai-consent.authorizeAiRequest (cyclomatic 103)apps/mobile/src/api/ai-consent.ts:16

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

What to do

  1. Bring the 37 bodies over 60 down to 60 or less in Cyclomatic Complexity — start with add-application-dialog.AddApplicationForm (cyclomatic 140), ai-consent.authorizeAiRequest (cyclomatic 129), practise.Session (cyclomatic 121). — 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 37 together lifts Cyclomatic Complexity from 2.0 to about 4.1/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.

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

D2 · Cognitive Complexity2.0 / 10Critical✓ Tool-verified

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

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

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

485 method(s) exceeded the cognitive complexity threshold of 15; the worst was cascade.resolveStylesheet at 204.

values.compileProgram::compileRule (cognitive 48) · ×2packages/resume/src/stylesheet/values.ts:554
pdf-lines.headingTest::test (cognitive 46) · ×2packages/import/src/pdf-lines.ts:636
cascade.resolveStylesheet (cognitive 204)packages/resume/src/stylesheet/cascade.ts:564
screen.TodayScreen (cognitive 193)apps/mobile/src/features/today/screen.tsx:64
practise.Session (cognitive 180)apps/web/src/features/career/workspace/practise.tsx:373

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

What to do

  1. Bring the 51 bodies over 60 down to 60 or less in Cognitive Complexity — start with cascade.resolveStylesheet (cognitive 204), screen.TodayScreen (cognitive 193), practise.Session (cognitive 180). — 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 51 together lifts Cognitive Complexity from 2.0 to about 3.4/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.

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

D3 · God Classes5.5 / 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.

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

274 over-large unit(s) detected — types, modules or files that carry too much.

FunctionTooLong: kit.KitPage · ×209apps/web/src/routes/builder/kit.tsx:221
FileTooLong: agent/service.ts · ×65packages/api/src/features/agent/service.ts

What to do

  1. Resolve the 209 FunctionTooLong finding(s) in God Classes — start with pdf-lines.ts (5), profile.tsx (4), providers.tsx (4). — One of this dimension's main actionable groups (209 warning-level).
  2. Resolve the 65 FileTooLong finding(s) in God Classes — start with service.ts (5), prepare.tsx (2), store.ts (2). — One of this dimension's main actionable groups (65 warning-level).

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

D5 · Coupling8.3 / 10Strong✓ Tool-verified

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

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

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

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

23 production modules (Gradle+npm), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; edges a convention plugin adds from buildSrc or build-logic are not visible there; 5 module(s) off the main sequence.

Off the main sequence: @reactive-resume/utils · ×5

What to do

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

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

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

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

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

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

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

0 of 6 classes have LCOM4 above 3.

✓ On the Gold path — maintain.

Detailed fixes: d6_recommendation.md.

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

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

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

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

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

Detailed fixes: d7_recommendation.md.

D10 · Test Quality10.0 / 10Stronggated by 5 serious findings✓ Tool-verified

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

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

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

7 skipped (3 with a documented reason), 1 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 3402 tests.

Skipped test: (unnamed test) · ×4tests/e2e/specs/assistant.spec.ts:9
No assertions: says which messages Knowledge changes hold back, as the server names themapps/web/src/features/career/coach-chat.test.tsx:461
Mock-dominated test: probes search in the user's first region · ×15packages/api/src/features/web-access/router.test.ts:34
Skipped (documented): (unnamed test) · ×3tests/e2e/fixtures/ai-stub-career.ts:50

What to do

  1. Resolve the 15 Mock-dominated test finding(s) in Test Quality — start with service.test.ts (6), router.test.ts, locale-choices.test.ts. — One of this dimension's main actionable groups (15 recommendation-level).
  2. Resolve the 4 Skipped test finding(s) in Test Quality — start with assistant.spec.ts, font-mirror.spec.ts, guest.spec.ts. — One of this dimension's main actionable groups (4 warning-level).
  3. Resolve the 1 No assertions finding(s) in Test Quality — start with coach-chat.test.tsx. — One of this dimension's main actionable groups (1 warning-level).

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

D12 · Dependency Hygiene10.0 / 10Exemplary✓ Tool-verified

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

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

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

0 outdated direct gem(s), 0 pinning defect(s). 2 declaration(s) graded against rubygems.org, 1 of them against a version resolved in a committed REDACTED. 1 declaration(s) carry a requirement that EXCLUDES the current release; that is a deliberate constraint (a supported-version ceiling or a held-back CI pin) and is counted, not charged. Whether any of these gems is DEPRECATED or YANKED is not graded — rubygems.org publishes no deprecation marker, and a yank removes a version rather than flagging it. Whether any is UNMAINTAINED is not graded either: no registry publishes a maintenance status, and release age does not stand in for one. Whether any is UNUSED is a source question, not a registry one. Known CVEs in this dependency graph are D30's question, read from the manifest there.

✓ On the Gold path — maintain.

Detailed fixes: d12_recommendation.md.

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

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

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

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

REDACTED scan ran and found no leaked secrets. 5 detection(s) were excluded as holding no minted credential in material that runs: a name, reference or comparison rather than a value, a readable phrase or pattern, a value that declares itself fake, or development, test, example, mock or demo material.

✓ On the Gold path — maintain.

Detailed fixes: d13_recommendation.md.

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

What it measures: Whether the licenses of third-party packages are compatible with your policy.

Method: Third-party package licenses resolved from declared package metadata and checked against the configured policy (allow/deny/copyleft). Deterministic; clean = no incompatible license found at metadata depth.

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

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

✓ On the Gold path — maintain.

Detailed fixes: d14_recommendation.md.

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

What it measures: Files that change often and are also complex — the riskiest hotspots.

Method: Per production file churn times cyclomatic complexity over a rolling window, computed from git and Roslyn/JS/Razor analysis. Exhaustive, deterministic per commit date.

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

Top hotspots: apps/web/src/features/applications/components/add-application-dialog.tsx (25×198=4950); packages/auth/src/config.ts (40×109=4360); apps/web/src/features/documents/documents-page.tsx (23×121=2783) Repeated repair below the complexity floor: apps/web/src/features/career/shared.tsx (10 of 14 changes were fixes); apps/web/src/features/applications/components/insights-view.tsx (9 of 17 changes were fixes); apps/server/src/http/auth.ts (9 of 12 changes were fixes)

Hotspot: apps/web/src/features/applications/components/add-application-dialog.tsx · ×215apps/web/src/features/applications/components/add-application-dialog.tsx:188
Repeated repair: apps/web/src/features/career/shared.tsx · ×75apps/web/src/features/career/shared.tsx:119

What to do

  1. Resolve the 215 Hotspot finding(s) in Churn × Complexity Hotspots — start with service.ts (6), offers.tsx (2), coach.tsx (2). — One of this dimension's main actionable groups (215 warning-level).
  2. Resolve the 75 Repeated repair finding(s) in Churn × Complexity Hotspots — start with index.ts (3), auth.ts (2), locale.ts (2). — One of this dimension's main actionable groups (75 warning-level).

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

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

What it measures: Acknowledged debt left in the code — TODOs, dead code, suppressed warnings.

Method: Roslyn syntactic debt markers (suppressions/TODO/FIXME/HACK/empty-catch/commented-code/Obsolete) plus SymbolFinder dead-code analysis; weighted-debt-per-KLoC density deducted 2.0x per unit. Deterministic, exhaustive.

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

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

✓ On the Gold path — maintain.

Detailed fixes: d17_recommendation.md.

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

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

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

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

2 of 2 documentation facets pass in full. 141 document(s) read across 24 unit(s).

✓ On the Gold path — maintain.

Detailed fixes: d19_recommendation.md.

D20 · ADR Quality6.0 / 10Adequate✓ Tool-verified

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

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

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

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

ADR lacks an enforcement field · ×3.agents/docs/decisions/0001-server-rendered-web-pages.md:1detected by adr-integrity
ADR declares no status · ×2.agents/docs/decisions/0004-multi-client-workspaces.md:1detected by adr-integrity
ADR has no Context and Decision section.agents/docs/decisions/0003-both-domains-serve-public-pages.md:1detected by adr-integrity

What to do

  1. Resolve the 3 ADR lacks an enforcement field finding(s) in ADR Quality — start with 0001-server-rendered-web-pages.md, 0003-both-domains-serve-public-pages.md, 0005-background-application-execution.md. — One of this dimension's main actionable groups (3 recommendation-level).
  2. Resolve the 2 ADR declares no status finding(s) in ADR Quality — start with 0004-multi-client-workspaces.md, 0005-background-application-execution.md. — One of this dimension's main actionable groups (2 recommendation-level).
  3. Resolve the 1 ADR has no Context and Decision section finding(s) in ADR Quality — start with 0003-both-domains-serve-public-pages.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.

D23 · Boundary Type-Coupling10.0 / 10Exemplary✓ Tool-verified

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.

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

72 domain type(s) cross context boundaries across 21 contexts; they are measured and withheld (not published, not scored). Contexts: ai, api, auth, db, docx, dsh-plugin, email, env, fonts, import, mcp, mobile and 9 more.

✓ On the Gold path — maintain.

Detailed fixes: d23_recommendation.md.

D24 · Comment Value9.8 9.7 / 10Exemplary✓ Tool-verified

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

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

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

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

redundant comment · ×6apps/mobile/src/features/letters/letter-screen.tsx:46
doc comments repeat the names · ×2packages/resume/src/ats-pdf/types.ts:197

✓ On the Gold path — maintain.

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

D26 · Project Cohesion6.8 / 10Adequate✓ Tool-verified

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

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

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

4 of 25 build units (Bundler, Gradle, npm) flagged as possibly oversized/incoherent.

Projects may be oversized for their cohesion

What to do

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

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

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

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

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

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

0 % of calls cross a namespace and 0 % go through an interface, but 87 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: small — navigation cost is tolerated.

✓ On the Gold path — maintain.

Detailed fixes: d27_recommendation.md.

D28 · Secrets (history)9.0 / 10Adequategated by 1 critical finding✓ Tool-verified

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

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

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

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

REDACTED
REDACTED

What to do

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

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

D29 · Static Analysis (SAST)1.1 / 10Critical✓ Tool-verified

What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.

Method: Polyglot static analysis via semgrep across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.

Coverage: semgrep pattern rules over all files — exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).

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

79 finding(s): 0 critical, 70 high, 9 medium, 0 low. 60 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 121 file(s) — `apps/mobile/src/api/client.ts` (line 26), `apps/mobile/src/data/auth-options.ts` (line 25), `apps/mobile/src/features/applications/ApplicationsScreen.tsx` (line 44), `apps/mobile/src/features/applications/model.ts` (line 25, line 27, line 35, …), `apps/mobile/src/features/builder/description/DescriptionScreen.tsx` (line 35), … (+116 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 2 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

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

What to do

  1. Resolve the 7 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (7). — One of this dimension's main actionable groups (7 issue-level).
  2. Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
  3. No action in Static Analysis (SAST) — all 60 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (60 issue-level, 0 of them charged here).

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

D30 · Dependency Vulnerabilities8.4 / 10Adequategated by 1 critical finding✓ Tool-verified

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

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

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

7 finding(s): 0 critical, 1 high, 5 medium, 1 low.

REDACTED
REDACTED
REDACTED

What to do

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

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

D31 · IaC & Container Security8.0 / 10Adequategated by 5 critical findings✓ Tool-verified

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

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

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

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

REDACTED
REDACTED
REDACTED

What to do

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

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

D32 · Data Compliance (PII/GDPR)9.0 / 10Stronggated by 1 serious finding✓ Tool-verified

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

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

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

1 finding(s): 0 critical, 0 high, 1 medium, 0 low. semgrep could not parse 110 file(s) — `apps/mobile/src/api/client.ts`, `apps/mobile/src/data/auth-options.ts`, `apps/mobile/src/features/applications/ApplicationsScreen.tsx`, `apps/mobile/src/features/applications/model.ts`, `apps/mobile/src/features/builder/description/DescriptionScreen.tsx`, … (+105 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

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

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

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

What it measures: Whether anyone still has living knowledge of each file, or it has been orphaned — last understood long ago by someone now gone quiet. The sibling of the bus factor: D16 asks who owns it, D34 asks whether anyone still knows it.

Method: File orphaning as total living-knowledge decay below one focused-commit's worth within a year, computed per-file from the D16 decay model. Exhaustive, deterministic over fixed history.

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

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

✓ On the Gold path — maintain.

Detailed fixes: d34_recommendation.md.

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

What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.

Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.

Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling. A non-source file is never a coupling PARTICIPANT either: documentation, schemas, config and data files are dropped with the rest, so a code↔docs pair — a command and the reference page that restates it — is not reported however strongly the two co-change; nor is coupling that runs THROUGH a build step or config file.

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

No strong hidden change-coupling between production files.

✓ On the Gold path — maintain.

Detailed fixes: d35_recommendation.md.

D36 · Supply-chain Provenance & Signing7.5 / 10Strong✓ Tool-verified

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

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

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

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

REDACTED
REDACTED
REDACTED
REDACTED

What to do

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

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

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

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

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

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

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

✓ On the Gold path — maintain.

Detailed fixes: d37_recommendation.md.

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

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

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

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

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

✓ On the Gold path — maintain.

Detailed fixes: d43_recommendation.md.

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

What it measures: Whether anyone still ships security patches for the platform this repository RUNS ON — the runtime it pins and the framework majors its own constraints hold it to. Separate from D12 because the question differs: a current Django on an end-of-life Python is perfectly up to date and completely unsupported, and the fix is a migration rather than a version bump. What the repository says it merely SUPPORTS is never charged.

Method: End-of-life PLATFORM read from the repository's own declarations and graded against a FROZEN, dated table of vendor support dates — no network, no feed, no API, so this dimension answers identically inside a closed scan fence. Two subjects: a RUNTIME the project pins (a single or all-end-of-life TargetFramework, a .nvmrc or .python-version, a requires-python CAP) and a FRAMEWORK major a dependency constraint cannot move off (a caret, tilde or exact version; `vue@^2.7.16` pins Vue 2). A FLOOR is deliberately never charged — `requires-python = ">=3.8"` states what a package SUPPORTS, not what it runs on — and a multi-target project is charged only when EVERY target is out of support. Runtime 4.0/product capped 8.0, framework 1.5 capped 4.5. The table is safe to freeze because a statement about support that ended in the past cannot become false: it loses recall as it ages, never precision, and a test asserts every entry predates the freeze date. Disjoint from D31 (a container image's OS layer) and D29 (the toolchain a CI workflow installs). Abstains when the repository declares no platform this pass reads — never scores it clean.

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

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

✓ On the Gold path — maintain.

Detailed fixes: d44_recommendation.md.

Frontend & cross-cutting dimensions

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

AC1 · Text alternatives10.0 / 10Exemplary○ Nothing flagged

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

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

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

AC2 · Forms & labels5.8 / 10Adequate✓ Tool-verified

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

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

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

  • This UI-library field component has no label / aria-label / aria-labelledby / id at this call site, and nothing written inside it here carries one either (a name prop is the form-submission key, not a label; an id, even one the component sets on what it renders, names nothing until a label points at it) — so it likely renders an unlabelled control. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed. (×8) — apps/mobile/src/features/auth/TwoStepScreen.tsx:101, apps/mobile/src/features/builder/description/DescriptionScreen.tsx:355, apps/mobile/src/features/career/stories.tsx:199, …
  • 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. (×7) — apps/mobile/src/features/builder/assistant/assistant-screen.tsx:238, apps/mobile/src/features/builder/share/web-page-screen.tsx:187, apps/mobile/src/features/builder/shared/section-actions.tsx:70, …
  • 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. (×15) — apps/web/src/features/assistant/conversation.tsx:1177, apps/web/src/features/career/knowledge/resume-facts.tsx:210, apps/web/src/features/career/offer-entry.tsx:491, …
  • 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. — apps/web/src/features/career/workspace/fit.tsx:659
  • This <div> carries a click handler, which makes it a control, but it has no text, aria-label or labelled child (the icon-only case), so assistive tech has no name to announce for it. Note that switching it to <button type="button"> — the right fix for its keyboard operability — does not give it a name either: an icon-only button still needs one. Add visible text or an aria-label. — apps/web/src/routes/builder/letter/-components/letter-page.tsx:238

What to do

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

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

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

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

  • No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. (×2) — apps/web/index.html:2, tooling/capture/popup.html:2
  • Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one. — apps/web/src/routes/builder/kit.tsx:638

What to do

  • Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
AC4 · Keyboard semantics3.1 / 10Weak✓ Tool-verified

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

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

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

  • A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler. (×3) — apps/web/src/features/resume/editor/check/check-panel.tsx:174, apps/web/src/features/resume/editor/page-overlay.tsx:84, apps/web/src/routes/builder/letter/-components/letter-page.tsx:238
  • This <section> carries tabIndex={0}, so it is in the tab order and a keyboard user will land on it — but its only behaviour is bound to pointerdown, pointer gestures a keyboard cannot produce, and there is no key handler. The tab stop leads nowhere. Bind the same behaviour to a key handler, or provide an equivalent control elsewhere. Give it a role as well, so assistive tech can announce what it is. — apps/web/src/routes/builder/$resumeId/-components/page-canvas.tsx:155

What to do

  • Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
AC5 · ARIA correctness10.0 / 10Exemplary○ Nothing flagged

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

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

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

AC6 · Visual & motion safety5.3 / 10Adequate✓ Tool-verified

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

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

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

  • `.initial-loader__spinner` moves (`animation: app-spin 0.7s linear infinite`) 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. — apps/web/index.html:90
  • <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). (×8) — apps/web/src/components/calm/filter-bar.tsx:54, apps/web/src/features/career/coach.tsx:781, apps/web/src/features/career/knowledge/preferences.tsx:315, …
  • <textarea> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2). (×3) — apps/web/src/features/applications/components/add-application-dialog.tsx:518, apps/web/src/features/career/knowledge/resume-facts.tsx:222, apps/web/src/features/resume/editor/proposals/proposal-list.tsx:468
  • <select> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2). (×2) — apps/web/src/features/career/knowledge/preferences.tsx:490, apps/web/src/features/career/knowledge/resume-facts.tsx:235
  • <span> moves — its `animate-[toast-fuse_linear_forwards]` 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:. — packages/ui/src/components/toast.tsx:28
  • `[data-pointer] :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/ui/src/styles/globals.css:260
  • `html:active-view-transition-type(page)::view-transition-new(root)` moves (`animation: var(--d2) var(--ease) calc(var(--d2) * 0.7) both vt-page-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. — apps/web/src/index.css:93
  • `html:active-view-transition-type(forward)::view-transition-new(root)` moves (`animation: var(--d2) var(--ease) calc(var(--d2) * 0.7) both vt-push-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. — apps/web/src/index.css:125
  • `html:active-view-transition-type(back)::view-transition-new(root)` moves (`animation: var(--d2) var(--ease) calc(var(--d2) * 0.7) both vt-pop-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. — apps/web/src/index.css:129

What to do

  • Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
AX10 · Code composition4.0 / 10Weak✓ Tool-verified

Other · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified. How each file's role is decided, because the split is only as good as that: a generated name or a build-output tree makes it Generated, a test project makes it Test, and otherwise the file's NAMESPACE and PATH words are matched against fixed vocabularies in a fixed ORDER — domain, then infrastructure, then application — so a file whose words hit two layers is counted under the earlier one. A production file matching none of them counts as application, so that share reads 'application or unclassified' rather than a measured application layer. Roles come from naming convention, never from what the code does. On this repository the split was taken from the source tree on disk rather than from a loaded .NET workspace, so a file's role is decided by its PATH segments alone — no declared namespace was available to add to the evidence — and generated output is excluded from the census entirely rather than counted as a generated share.

Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.

Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.

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

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

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

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

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

Method: Roslyn plus csproj analysis: architecture style detection (DDD, clean, vertical-slice, CQRS) and structure fitness for repo size. Deterministic.

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

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

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

AX7 · Slice cohesion1.0 / 10Critical✓ Tool-verified

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

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

  • `DetailScreen` (slice 'applications') depends on `useSavedItems` from slice 'workspace'. — apps/mobile/src/features/applications/DetailScreen.tsx:106
  • `ConsentScreen` (slice 'auth') depends on `useStoryboardView` from slice 'settings'. — apps/mobile/src/features/auth/ConsentScreen.tsx:37
  • `LetterDesignScreen` (slice 'letters') depends on `useDocumentId` from slice 'builder'. — apps/mobile/src/features/letters/design-screen.tsx:29
  • `LetterDesignScreen` (slice 'letters') depends on `useLetterDocument` from slice 'builder'. — apps/mobile/src/features/letters/design-screen.tsx:31
  • `LetterDesignScreen` (slice 'letters') depends on `useRenderedPage` from slice 'builder'. — apps/mobile/src/features/letters/design-screen.tsx:40
  • `LetterDesignScreen` (slice 'letters') depends on `LetterDocument` from slice 'builder'. — apps/mobile/src/features/letters/design-screen.tsx:81
  • `LetterDesignScreen` (slice 'letters') depends on `DocumentState` from slice 'builder'. — apps/mobile/src/features/letters/design-screen.tsx:115
  • `LetterScreen` (slice 'letters') depends on `useDocumentId` from slice 'builder'. — apps/mobile/src/features/letters/letter-screen.tsx:31
  • `LetterScreen` (slice 'letters') depends on `useLetterDocument` from slice 'builder'. — apps/mobile/src/features/letters/letter-screen.tsx:33
  • `LetterScreen` (slice 'letters') depends on `LetterDocument` from slice 'builder'. — apps/mobile/src/features/letters/letter-screen.tsx:97
  • `LetterScreen` (slice 'letters') depends on `DocumentState` from slice 'builder'. — apps/mobile/src/features/letters/letter-screen.tsx:164
  • `AccountScreen` (slice 'settings') depends on `useAuthOptions` from slice 'auth'. — apps/mobile/src/features/settings/AccountScreen.tsx:27
  • `SettingsScreen` (slice 'settings') depends on `hostOf` from slice 'auth'. — apps/mobile/src/features/settings/SettingsScreen.tsx:145
  • `SignOutDialog` (slice 'settings') depends on `hostOf` from slice 'auth'. — apps/mobile/src/features/settings/SignOutDialog.tsx:124
  • `TodayScreen` (slice 'today') depends on `useOpenDocument` from slice 'documents'. — apps/mobile/src/features/today/screen.tsx:77
  • `TodayScreen` (slice 'today') depends on `AccountAvatar` from slice 'documents'. — apps/mobile/src/features/today/screen.tsx:188
  • `TodayScreen` (slice 'today') depends on `zoneCity` from slice 'settings'. — apps/mobile/src/features/today/screen.tsx:205
  • `TodayScreen` (slice 'today') depends on `CollectionState` from slice 'documents'. — apps/mobile/src/features/today/screen.tsx:214
  • `TodayScreen` (slice 'today') depends on `DocumentPlaceholders` from slice 'documents'. — apps/mobile/src/features/today/screen.tsx:240
  • `ApplyScreen` (slice 'workspace') depends on `stageDate` from slice 'applications'. — apps/mobile/src/features/workspace/ApplyScreen.tsx:46
  • `ApplyScreen` (slice 'workspace') depends on `storyboard` from slice 'applications'. — apps/mobile/src/features/workspace/ApplyScreen.tsx:49
  • `ApplyScreen` (slice 'workspace') depends on `longDay` from slice 'applications'. — apps/mobile/src/features/workspace/ApplyScreen.tsx:66
  • `ApplyScreen` (slice 'workspace') depends on `sentStepHref` from slice 'applications'. — apps/mobile/src/features/workspace/ApplyScreen.tsx:85
  • `ApplyScreen` (slice 'workspace') depends on `dayMonth` from slice 'applications'. — apps/mobile/src/features/workspace/ApplyScreen.tsx:97
  • `ApplyScreen` (slice 'workspace') depends on `clockTime` from slice 'applications'. — apps/mobile/src/features/workspace/ApplyScreen.tsx:97
  • `ApplyScreen` (slice 'workspace') depends on `longWeekday` from slice 'applications'. — apps/mobile/src/features/workspace/ApplyScreen.tsx:138
  • `DebriefScreen` (slice 'workspace') depends on `interviewTitle` from slice 'applications'. — apps/mobile/src/features/workspace/DebriefScreen.tsx:83
  • `itemTitle` (slice 'workspace') depends on `SavedItem` from slice 'applications'. — apps/mobile/src/features/workspace/DebriefScreen.tsx:162
  • `LibraryScreen` (slice 'workspace') depends on `dayMonth` from slice 'applications'. — apps/mobile/src/features/workspace/DebriefScreen.tsx:218
  • `FitScreen` (slice 'workspace') depends on `useBarMenu` from slice 'applications'. — apps/mobile/src/features/workspace/FitScreen.tsx:50
  • `FitScreen` (slice 'workspace') depends on `isoDay` from slice 'applications'. — apps/mobile/src/features/workspace/FitScreen.tsx:77
  • `FitScreen` (slice 'workspace') depends on `clockTime` from slice 'applications'. — apps/mobile/src/features/workspace/FitScreen.tsx:78
  • `FitScreen` (slice 'workspace') depends on `QuietLine` from slice 'applications'. — apps/mobile/src/features/workspace/FitScreen.tsx:115
  • `FitScreen` (slice 'workspace') depends on `FadeIn` from slice 'applications'. — apps/mobile/src/features/workspace/FitScreen.tsx:143
  • `MessagesScreen` (slice 'workspace') depends on `useBarMenu` from slice 'applications'. — apps/mobile/src/features/workspace/MessagesScreen.tsx:50
  • `MessagesScreen` (slice 'workspace') depends on `stageDate` from slice 'applications'. — apps/mobile/src/features/workspace/MessagesScreen.tsx:61
  • `MessagesScreen` (slice 'workspace') depends on `storyboard` from slice 'applications'. — apps/mobile/src/features/workspace/MessagesScreen.tsx:73
  • `MessagesScreen` (slice 'workspace') depends on `dayMonth` from slice 'applications'. — apps/mobile/src/features/workspace/MessagesScreen.tsx:79
  • `MessagesScreen` (slice 'workspace') depends on `FadeIn` from slice 'applications'. — apps/mobile/src/features/workspace/MessagesScreen.tsx:165
  • `MessagesScreen` (slice 'workspace') depends on `ChoiceSheet` from slice 'applications'. — apps/mobile/src/features/workspace/MessagesScreen.tsx:206

What to do

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

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

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

What to do

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

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.

  • Authorization IS enforced here (by route guards, auth middleware or checks that refuse a caller) — this is NOT a claim that endpoints are unprotected. What's missing is a NAMED rule set: who may do what is encoded inline where it is checked, so the rules can't be listed, reviewed or tested apart from the code that applies them. Recommendation, not a defect. — apps/server/src/http/career-jobs.ts:12

What to do

  • Name the access rules — roles/permissions declared once (a @Roles/@Permissions decorator with its guard, a CASL ability, a casbin model, or Supabase CREATE POLICY) and consulted where access is checked, so the rule set is reviewable and testable on its own.
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.

C5 · Data-Subject Rights4.0 / 10Weak✓ Tool-verified

Other · Security — Whether GDPR data-subject requests are supported in code — erasure, export/portability, consent.

Method: Roslyn scan: GDPR data-subject-rights corroboration (erasure/export/consent vocabulary co-occurring with subject-id store crossing or explicit GDPR pattern). Deterministic, gated by PII.

  • Corroborated rights: erasure ✓ · export ✗ · consent ✗. Each tick means this scan found code in the repository implementing that right — a deletion/anonymisation path for erasure, a data-export or portability path for export, and consent state recorded alongside the personal data it authorises. A ✗ therefore means no such code was recognised HERE, not that the right is unsupported: a capability provided by a platform, a manual runbook, or code spelled in a way this scan does not match is not visible to it. Confirm before treating a cross as a gap; where it is one, the right has to be fulfilled manually.

What to do

  • Implement data export/portability for a data subject (a machine-readable export of their personal data).
  • Track GDPR consent (lawful basis) alongside the personal data it authorises.
GD1 · Unfinished & placeholder code10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Unreviewed-generation residue in this repository's JavaScript/TypeScript: functions whose whole body still throws a "not implemented" error, and placeholder text (lorem ipsum, changeme/replace_me…) left in strings and JSX of non-test, non-generated code. Scored as a quality signature, never as a claim about authorship.

Method: Roslyn syntax scan: NotImplementedException throws and placeholder string literals in non-test, non-generated shipped code. Deterministic, code-shape signature.

IC1 · Incompleteness & stubs6.8 / 10Adequate✓ Tool-verified

Other · Code Health — Unfinished work detected by code SHAPE, not keywords, in this repository's JavaScript/TypeScript: functions that only throw a "not implemented" error, functions that take inputs and return a constant or do nothing, async functions that never await, dead `if (false)` branches, and skeleton classes most of whose methods are holes.

Method: Roslyn syntax scan: incompleteness by code shape (constant-returning methods, async-never-await, #if false branches, guards that return what the code already falls through to, tests an earlier guard already decided, comparisons against NaN, skeleton types), not keyword-gated. Deterministic, code-shape heuristic.

  • `onValueChange` is wired to an arrow whose body is empty — the markup attaches a listener that does nothing. Implement the handler, or remove the attribute that wires it. (×5) — apps/mobile/app/(dev)/kit.tsx:224, apps/mobile/app/(dev)/kit.tsx:254, apps/mobile/app/(dev)/kit.tsx:255, …
  • `onSelect` is wired to an arrow whose body is empty — the markup attaches a listener that does nothing. Implement the handler, or remove the attribute that wires it. (×2) — apps/mobile/app/(dev)/kit.tsx:257, apps/mobile/app/(dev)/kit.tsx:258
  • `onPress` 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. (×6) — apps/mobile/app/(dev)/kit.tsx:312, apps/mobile/app/(dev)/kit.tsx:314, apps/mobile/app/(dev)/motion-lab/[lab].tsx:189, …
  • `onNavigate` is wired to an arrow whose body is empty — the markup attaches a listener that does nothing. Implement the handler, or remove the attribute that wires it. (×2) — apps/mobile/app/(dev)/kit.tsx:348, apps/mobile/app/(dev)/kit.tsx:361
  • `onClose` 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/mobile/src/dev/storyboard/backdrop.tsx:119
  • `onSignedOut` 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/mobile/src/dev/storyboard/backdrop.tsx:120
  • `onChange` is wired to an arrow whose body is empty — the markup attaches a listener that does nothing. Implement the handler, or remove the attribute that wires it. — apps/web/src/features/resume/editor/write/section-view.tsx:128
  • `onRemove` 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/src/routes/builder/kit.tsx:310
  • `seed` has an empty body — confirm it's an intentional no-op and not an unfinished method. — apps/mobile/src/dev/storyboard/capture.tsx:36
  • `setNow` has an empty body — confirm it's an intentional no-op and not an unfinished method. — apps/mobile/src/dev/storyboard/capture.tsx:36
  • A bare `eslint-disable` or `@ts-nocheck` with no rule list switches every lint rule or the whole type checker off for the rest of the file — hidden debt. Disable the specific rule on the specific line, with a justification, instead. (×2) — apps/web/src/routeTree.gen.ts:1, apps/web/src/routeTree.gen.ts:3
  • A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something. (×4) — tests/e2e/specs/assistant.spec.ts:9, tests/e2e/specs/font-mirror.spec.ts:10, tests/e2e/specs/guest.spec.ts:5, …

What to do

  • Clear the softer debt: re-enable or delete skipped tests, decide whether each empty function is a deliberate no-op (and say so in a comment), and replace blanket `eslint-disable` / `@ts-nocheck` with targeted, justified suppressions.
M1 · Documentation (README)6.8 / 10Adequate✓ Tool-verified

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

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

What to do

  • Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
M2 · Architecture documentation8.0 / 10Strong✓ Tool-verified

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

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

M3 · Folder & project structure10.0 / 10Exemplary✓ Tool-verified

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

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

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

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

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

P1 · CI/CD gates10.0 / 10Exemplary○ Nothing flagged

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

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

P10 · Library API & versioning10.0 / 10Exemplary○ Nothing flagged

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

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

P2 · Observability7.0 / 10Strong✓ Tool-verified

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

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

  • Only 2/3 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `tooling`.
  • `packages/auth/src/config.ts` reports through `console.*` at line 677 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/auth/src/config.ts:677
  • `packages/auth/src/config.ts` reports through `console.*` at line 699 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/auth/src/config.ts:699
  • `packages/auth/src/rate-limit.ts` reports through `console.*` at line 63 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/auth/src/rate-limit.ts:63

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.
P3 · Security & performance tooling0.0 / 10Critical✓ Tool-verified

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

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

  • No static application security testing detected. For this repository's stack, add 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 6 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. — REDACTED:4
  • `package.json` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — package.json:65

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.
P4 · Deployment & Rollback8.0 / 10Strong✓ Tool-verified

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

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

P5 · DR & Backup4.0 / 10Weak✓ Tool-verified

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

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

What to do

  • Document RTO/RPO and a tested restore procedure (a backup config alone isn't disaster recovery).
  • Enable purge protection / soft-delete (and prevent_destroy on critical resources) so data stores can't be lost to an accidental or malicious delete.
P6 · Release Hygiene10.0 / 10Exemplary✓ Tool-verified

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

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

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

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

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

PF3 · Async & latency hygiene6.0 / 10Adequate✓ Tool-verified

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

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

  • `unzipSync` in `detectImportKind` 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/src/features/resume/import/read-file.ts:79
  • `execFileSync` in `ensureDatabases` 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. — tooling/dev/test-db.mjs:50
  • `spawnSync` 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. — tooling/dev/test-db.mjs:96

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.
R1 · Type Safety9.8 / 10Exemplary✓ Tool-verified

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

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

R10 · Code Duplication7.3 / 10Strong✓ Tool-verified

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

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

  • 77 duplicated blocks under apps/web/src/features/ have copies in at least two of the sibling directories ai, applications, assistant, ats-checker, auth, career (+9 more sibling(s) not listed) — 27 of them are reported below, and 50 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 77 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 77 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 77 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/src/features/assistant/conversation.tsx:1081
  • 52 duplicated blocks under packages/api/src/features/ have copies in at least two of the sibling directories agent, ai-providers, application-profile, applications, auth, career (+5 more sibling(s) not listed) — 17 of them are reported below, and 35 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 52 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 52 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 52 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/api/src/features/cover-letters/versions.ts:27
  • 46 duplicated blocks under packages/pdf/src/templates/ have copies in at least two of the sibling directories azurill, bronzor, chikorita, ditgar, ditto, gengar (+13 more sibling(s) not listed) — 36 of them are reported below, and 10 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 46 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 46 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 46 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — packages/pdf/src/templates/ditgar/DitgarPage.tsx:1
  • 42 duplicated blocks under packages/ have copies in at least two of the sibling directories ai, api, auth, docx, email, env (+7 more sibling(s) not listed) — 20 of them are reported below, and 22 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 42 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 42 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 42 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — packages/docx/src/html-to-docx.ts:54
  • 41 duplicated blocks under apps/web/src/ have copies in at least two of the sibling directories components, dialogs, features, routes — 16 of them are reported below, and 25 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 41 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 41 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 41 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/src/features/resume/editor/save-status.tsx:94
  • 30 duplicated blocks under apps/ have copies in at least two of the sibling directories mobile, web — 23 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 30 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 30 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 30 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/mobile/src/features/builder/check/issues.ts:29
  • 27 duplicated blocks under the repository root have copies in at least two of the sibling directories apps, packages, tooling — 16 of them are reported below, and 11 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 27 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 27 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 27 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/server/src/cloudflare/r2.ts:24
  • 18 duplicated blocks under apps/mobile/src/features/ have copies in at least two of the sibling directories applications, auth, builder, career, documents, letters (+4 more sibling(s) not listed) — 7 of them are reported below, and 11 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 18 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 18 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 18 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/mobile/src/features/career/facts.tsx:12
  • 13 duplicated blocks under apps/mobile/src/features/builder/ have copies in at least two of the sibling directories basics, check, description, design, download, entry (+5 more sibling(s) not listed) — 4 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 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/mobile/src/features/builder/design/LayoutScreen.tsx:72
  • 10 duplicated blocks under apps/web/src/routes/builder/ have copies in at least two of the sibling directories $resumeId, letter — 9 of them are reported below, and 1 is counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 10 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 10 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 10 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — apps/web/src/routes/builder/$resumeId/-components/editor-shell.tsx:54
  • 8 duplicated blocks under apps/mobile/src/ have copies in at least two of the sibling directories data, features, i18n, render, ui — 4 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 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. — apps/mobile/src/i18n/index.ts:23
  • 5 duplicated blocks under apps/web/src/routes/ have copies in at least two of the sibling directories agent, auth, builder, dashboard — 2 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 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/src/routes/agent/$threadId.tsx:51
  • apps/mobile/src/features/builder/check/issues.ts:29 · apps/web/src/features/resume/editor/check/issues.ts:52 — the two spans are one implementation copied and then locally edited — 1270 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/mobile/src/features/builder/check/issues.ts:29
  • packages/pdf/src/templates/ditgar/DitgarPage.tsx:1 · packages/pdf/src/templates/gengar/GengarPage.tsx:1 — these 2 files are line-for-line copies of one another — 206 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/pdf/src/templates/ditgar/DitgarPage.tsx:1
  • packages/pdf/src/templates/lapras/LaprasPage.tsx:17 · packages/pdf/src/templates/onyx/OnyxPage.tsx:17 — 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/pdf/src/templates/lapras/LaprasPage.tsx:17
  • packages/docx/src/html-to-docx.ts:54 · packages/odt/src/html-to-odt.ts:12 — the two spans are one implementation copied and then locally edited — 704 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/docx/src/html-to-docx.ts:54
  • packages/pdf/src/templates/gengar/GengarPage.tsx:83 · packages/pdf/src/templates/pikachu/PikachuPage.tsx:78 — the two spans are one implementation copied and then locally edited — 505 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/pdf/src/templates/gengar/GengarPage.tsx:83
  • apps/web/src/features/career/schedules.tsx:41 · apps/web/src/features/career/today.tsx:1109 — the two spans are one implementation copied and then locally edited — 666 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — apps/web/src/features/career/schedules.tsx:41
  • apps/mobile/src/features/builder/design/presets.ts:25 · apps/web/src/features/resume/editor/design/presets.ts:32 — the two spans are one implementation copied and then locally edited — 823 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/mobile/src/features/builder/design/presets.ts:25
  • apps/web/src/dialogs/auth/disable-two-factor.tsx:30 · apps/web/src/dialogs/auth/set-password.tsx:28 — the two spans are one implementation copied and then locally edited — 462 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/src/dialogs/auth/disable-two-factor.tsx:30
  • apps/web/src/features/assistant/conversation.tsx:1081 · apps/web/src/features/career/coach-thread.tsx:356 — the two spans are one implementation copied and then locally edited — 423 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/src/features/assistant/conversation.tsx:1081
  • apps/web/src/dialogs/auth/change-password.tsx:80 · apps/web/src/dialogs/auth/set-password.tsx:58 — the two spans are one implementation copied and then locally edited — 351 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/src/dialogs/auth/change-password.tsx:80
  • apps/web/src/features/documents/document-card.tsx:248 · apps/web/src/features/documents/document-card.tsx:371 — the two spans are one implementation copied and then locally edited — 347 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — apps/web/src/features/documents/document-card.tsx:248
  • packages/db/src/schema/auth.ts:63 · packages/db/src/schema/auth.ts:400 — the two spans are one implementation copied and then locally edited — 455 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/db/src/schema/auth.ts:63
  • apps/mobile/src/i18n/index.ts:23 · apps/mobile/src/render/letter-words.ts:9 — 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. — apps/mobile/src/i18n/index.ts:23
  • apps/mobile/src/features/workspace/FitScreen.tsx:88 · apps/mobile/src/features/workspace/PrepScreen.tsx:108 — the two spans are one implementation copied and then locally edited — 330 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/mobile/src/features/workspace/FitScreen.tsx:88
  • apps/web/src/features/resume/editor/save-status.tsx:94 · apps/web/src/routes/builder/letter/-components/letter-bar.tsx:323 — the two spans are one implementation copied and then locally edited — 294 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/src/features/resume/editor/save-status.tsx:94
  • packages/pdf/src/templates/porygon/PorygonPage.tsx:33 · packages/pdf/src/templates/scizor/ScizorPage.tsx:33 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — packages/pdf/src/templates/porygon/PorygonPage.tsx:33
  • apps/mobile/src/features/builder/menu/menu-screen.tsx:95 · apps/mobile/src/features/builder/menu/menu-screen.tsx:306 — the two spans are one implementation copied and then locally edited — 472 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — apps/mobile/src/features/builder/menu/menu-screen.tsx:95
  • apps/mobile/src/api/ai-consent.ts:55 · apps/web/src/libs/orpc/ai-consent.ts:44 — the two spans are one implementation copied and then locally edited — 482 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/mobile/src/api/ai-consent.ts:55
  • packages/ui/src/components/dialog.tsx:76 · packages/ui/src/components/sheet.tsx:88 — the two spans are one implementation copied and then locally edited — 216 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/src/components/dialog.tsx:76
  • packages/pdf/src/templates/chikorita/ChikoritaPage.tsx:34 · packages/pdf/src/templates/ditto/DittoPage.tsx:33 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — packages/pdf/src/templates/chikorita/ChikoritaPage.tsx:34
  • apps/web/src/features/auth/pages/login.tsx:220 · apps/web/src/features/auth/pages/register.tsx:236 — the two spans are one implementation copied and then locally edited — 279 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/src/features/auth/pages/login.tsx:220
  • packages/db/src/schema/cover-letter.ts:43 · packages/db/src/schema/resume.ts:53 — the two spans are one implementation copied and then locally edited — 366 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/db/src/schema/cover-letter.ts:43
  • packages/api/src/features/cover-letters/versions.ts:27 · packages/api/src/features/resume/version-history.ts:14 — the two spans are one implementation copied and then locally edited — 335 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/api/src/features/cover-letters/versions.ts:27
  • packages/import/src/linkedin.ts:100 · packages/schema/src/applications/csv.ts:20 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — packages/import/src/linkedin.ts:100
  • packages/pdf/src/templates/kakuna/KakunaPage.tsx:54 · packages/pdf/src/templates/meowth/MeowthPage.tsx:54 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — packages/pdf/src/templates/kakuna/KakunaPage.tsx:54
  • packages/pdf/src/templates/shared/sections.tsx:1101 · packages/pdf/src/templates/shared/sections.tsx:1298 — 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/pdf/src/templates/shared/sections.tsx:1101
  • apps/web/src/features/documents/documents-page.tsx:1043 · apps/web/src/features/documents/import/import-page.tsx:193 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — apps/web/src/features/documents/documents-page.tsx:1043
  • apps/mobile/src/features/builder/menu/menu-screen.tsx:46 · apps/mobile/src/features/builder/menu/menu-screen.tsx:281 — the two spans are one implementation copied and then locally edited — 221 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — apps/mobile/src/features/builder/menu/menu-screen.tsx:46

What to do

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

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

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

  • apps/mobile/src/render/page-renderer.ts:1 reaches into another package with a relative path (../../modules/pdf-pages) — import the package by name instead. — apps/mobile/src/render/page-renderer.ts:1
  • apps/mobile/src/render/page-renderer.ts:8 reaches into another package with a relative path (../../modules/pdf-pages) — import the package by name instead. — apps/mobile/src/render/page-renderer.ts:8
  • packages/pdf/src/browser.tsx:7 imports harfbuzzjs/dist/harfbuzz-subset.wasm?url, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — packages/pdf/src/browser.tsx:7
  • tooling/locales/generate.ts:15 reaches into another package with a relative path (../../packages/pdf/src/section-title-catalog.json) — import the package by name instead. — tooling/locales/generate.ts:15
  • tooling/locales/generate.ts:20 reaches into another package with a relative path (../../packages/schema/src/resume/present-labels.json) — import the package by name instead. — tooling/locales/generate.ts:20
  • tooling/locales/generate.ts:26 reaches into another package with a relative path (../../packages/utils/src/file-name-words.json) — import the package by name instead. — tooling/locales/generate.ts:26
  • tooling/locales/generate.ts:31 reaches into another package with a relative path (../../packages/schema/src/resume/expected-labels.json) — import the package by name instead. — tooling/locales/generate.ts:31
  • tooling/locales/generate.ts:38 reaches into another package with a relative path (../../packages/pdf/src/html/web-page-catalog.json) — import the package by name instead. — tooling/locales/generate.ts:38
  • tooling/locales/generate.ts:45 reaches into another package with a relative path (../../packages/email/src/templates/auth-catalog.json) — import the package by name instead. — tooling/locales/generate.ts:45

What to do

  • Fix the listed violations: import through public entries (package exports / slice index), never reach into another layer or package's internals.
R2 · Cyclomatic Complexity7.0 / 10Strong✓ Tool-verified

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

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

  • fixtureWrite has cyclomatic complexity 219 and cognitive complexity 360; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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/mobile/src/data/fixture-operations.ts:178
  • AddApplicationForm has cyclomatic complexity 145 and cognitive complexity 109; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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/src/features/applications/components/add-application-dialog.tsx:188
  • ScheduleSheet has cyclomatic complexity 112 and cognitive complexity 95; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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/src/features/career/schedule-sheet.tsx:138
  • authorizeAiRequest has cyclomatic complexity 102 and cognitive complexity 85; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — apps/mobile/src/api/ai-consent.ts:16
  • DocumentsPage has cyclomatic complexity 98 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 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/src/features/documents/documents-page.tsx:80
  • (anonymous) has cyclomatic complexity 95 and cognitive complexity 92; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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/src/libs/orpc/ai-consent.ts:73
  • resolveStylesheet has cyclomatic complexity 90 and cognitive complexity 216; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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/resume/src/stylesheet/cascade.ts:564
  • importLines has cyclomatic complexity 88 and cognitive complexity 66; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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/import/src/pdf-lines.ts:1349
  • Session has cyclomatic complexity 79 and cognitive complexity 66; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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/src/features/career/workspace/practise.tsx:373
  • send has cyclomatic complexity 77 and cognitive complexity 84; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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/api/src/features/agent/service.ts:1468
  • convertNode has cyclomatic complexity 69 and cognitive complexity 104; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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/pdf/src/forme/to-forme.tsx:477
  • RouteComponent has cyclomatic complexity 65 and cognitive complexity 48; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — apps/web/src/routes/dashboard/applications/index.tsx:121
  • toFormeStyle has cyclomatic complexity 64 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 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/pdf/src/forme/style.ts:377
  • (anonymous) has cyclomatic complexity 64 and cognitive complexity 85; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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/auth/src/config.ts:874
  • ToolPartView has cyclomatic complexity 63 and cognitive complexity 65; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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/src/features/assistant/conversation.tsx:743
  • TodayScreen has cyclomatic complexity 63 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 sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — apps/mobile/src/features/today/screen.tsx:64
  • generateCareer has cyclomatic complexity 59 and cognitive complexity 63; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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/api/src/features/career/generate.ts:113
  • NewDocument has cyclomatic complexity 58 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 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/src/features/documents/new-document-dialog.tsx:93
  • PractiseTab has cyclomatic complexity 56 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 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/src/features/career/workspace/practise.tsx:122
  • orderExperienceHeaders has cyclomatic complexity 55 and cognitive complexity 70; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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/import/src/pdf-lines.ts:1181
  • (anonymous) has cyclomatic complexity 55 and cognitive complexity 64; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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/mobile/src/dev/storyboard/edges.test.ts:221
  • AssistantPanel has cyclomatic complexity 55 and cognitive complexity 43; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — apps/web/src/features/assistant/assistant-panel.tsx:59
  • OfferForm has cyclomatic complexity 54 and cognitive complexity 48; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — apps/web/src/features/career/offer-entry.tsx:255
  • test has cyclomatic complexity 54 and cognitive complexity 43; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/import/src/pdf-lines.ts:636
  • parseReactiveResumeV4JSON has cyclomatic complexity 53 and cognitive complexity 56; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/import/src/reactive-resume-v4-json.tsx:241
  • CoachPage has cyclomatic complexity 51 and cognitive complexity 49; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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/src/features/career/coach.tsx:115
  • open has cyclomatic complexity 50 and cognitive complexity 61; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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/mobile/src/data/draft/store.ts:239
  • AnswerCard has cyclomatic complexity 50 and cognitive complexity 44; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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/src/features/career/workspace/apply.tsx:490
  • RichTextEditor has cyclomatic complexity 50 and cognitive complexity 29; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — apps/web/src/features/resume/editor/write/rich-text-editor-field.tsx:214
  • headingTest has cyclomatic complexity 49 and cognitive complexity 104; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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/import/src/pdf-lines.ts:207
  • processBlockElement has cyclomatic complexity 49 and cognitive complexity 102; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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/docx/src/html-to-docx.ts:149
  • convertNode has cyclomatic complexity 49 and cognitive complexity 74; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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/pdf/src/html/to-html.ts:290
  • (anonymous) has cyclomatic complexity 49 and cognitive complexity 45; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/api/src/features/resume/service.ts:838
  • SentDocuments has cyclomatic complexity 49 and cognitive complexity 41; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — apps/web/src/features/applications/components/detail/sent-documents.tsx:60
  • ResumePageCanvas has cyclomatic complexity 49 and cognitive complexity 36; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — apps/web/src/routes/builder/$resumeId/-components/page-canvas.tsx:71
  • MessagesTab has cyclomatic complexity 49 and cognitive complexity 35; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — apps/web/src/features/career/workspace/messages.tsx:81
  • Workspace has cyclomatic complexity 47 and cognitive complexity 42; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — apps/web/src/features/career/workspace/shell.tsx:123
  • WebAccessSection has cyclomatic complexity 47 and cognitive complexity 42; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — apps/web/src/features/settings/ai/web-access.tsx:56
  • AnswerLibrary has cyclomatic complexity 47 and cognitive complexity 36; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — apps/web/src/features/career/workspace/answer-library.tsx:49
  • invokeFake has cyclomatic complexity 46 and cognitive complexity 76; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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/mobile/src/data/fixtures.ts:708
R3 · Large Files6.3 / 10Adequate✓ 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.

  • packages/api/src/features/agent/service.ts has 2268 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/api/src/features/agent/service.ts:1
  • packages/import/src/pdf-lines.ts has 2024 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/import/src/pdf-lines.ts:1
  • packages/api/src/features/career/service.ts has 1954 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/api/src/features/career/service.ts:1
  • packages/pdf/src/templates/shared/sections.tsx has 1705 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/pdf/src/templates/shared/sections.tsx:1
  • packages/api/src/features/applications/service.ts 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. — packages/api/src/features/applications/service.ts:1
  • packages/auth/src/config.ts has 1330 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/auth/src/config.ts:1
  • apps/web/src/features/career/workspace/practise.tsx has 1321 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/src/features/career/workspace/practise.tsx:1
  • apps/web/src/features/career/today.tsx has 1303 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/src/features/career/today.tsx:1
  • apps/web/src/features/resume/builder/draft.ts has 1265 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/src/features/resume/builder/draft.ts:1
  • apps/web/src/features/assistant/conversation.tsx has 1261 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/src/features/assistant/conversation.tsx:1
  • apps/web/src/features/career/offers.tsx has 1260 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/src/features/career/offers.tsx:1
  • apps/web/src/routeTree.gen.ts has 1235 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/src/routeTree.gen.ts:1
  • apps/web/src/routes/builder/letter/-components/write-panel.tsx has 1225 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/src/routes/builder/letter/-components/write-panel.tsx:1
  • apps/web/src/features/applications/components/add-application-dialog.tsx has 1149 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/src/features/applications/components/add-application-dialog.tsx:1
  • apps/web/src/routes/builder/kit.tsx has 1147 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/src/routes/builder/kit.tsx:1
  • apps/web/src/features/career/workspace/apply.tsx has 1113 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/src/features/career/workspace/apply.tsx:1
  • apps/web/src/features/documents/documents-page.tsx has 1066 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/src/features/documents/documents-page.tsx:1
  • packages/api/src/features/resume/service.ts has 1065 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/api/src/features/resume/service.ts:1
  • apps/web/src/features/career/coach-chat.tsx has 1053 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/src/features/career/coach-chat.tsx:1
  • apps/web/src/features/career/workspace/messages.tsx has 1017 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/src/features/career/workspace/messages.tsx:1
  • packages/pdf/src/forme/to-forme.tsx has 1006 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/pdf/src/forme/to-forme.tsx:1
  • apps/web/src/features/career/workspace/prepare.tsx has 1004 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/src/features/career/workspace/prepare.tsx:1
  • apps/mobile/src/features/applications/ApplicationsScreen.tsx has 965 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — apps/mobile/src/features/applications/ApplicationsScreen.tsx:1
  • packages/api/src/features/career/jobs.ts has 962 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/api/src/features/career/jobs.ts:1
  • packages/pdf/src/semantic/tree.ts has 957 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/pdf/src/semantic/tree.ts:1
  • apps/web/src/features/documents/new-document-dialog.tsx has 918 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — apps/web/src/features/documents/new-document-dialog.tsx:1
  • apps/mobile/src/data/fixture-operations.ts has 915 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — apps/mobile/src/data/fixture-operations.ts:1
  • apps/web/src/features/applications/components/application-detail-sheet.tsx has 913 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/src/features/applications/components/application-detail-sheet.tsx:1
  • apps/web/src/features/resume/editor/check/job-match.tsx 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. — apps/web/src/features/resume/editor/check/job-match.tsx:1
  • apps/mobile/src/data/fixtures.ts has 867 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — apps/mobile/src/data/fixtures.ts:1
  • apps/web/src/features/resume/share/share-panel.tsx has 865 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/src/features/resume/share/share-panel.tsx:1
  • apps/web/src/features/documents/import/import-page.tsx has 863 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/src/features/documents/import/import-page.tsx:1
  • apps/web/src/features/settings/profile.tsx has 863 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/src/features/settings/profile.tsx:1
  • packages/resume/src/stylesheet/cascade.ts has 848 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/resume/src/stylesheet/cascade.ts:1
  • apps/web/src/features/assistant/assistant-panel.tsx has 846 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/src/features/assistant/assistant-panel.tsx:1
  • apps/web/src/routes/builder/$resumeId/-sidebar/right/sections/layout/pages.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/src/routes/builder/$resumeId/-sidebar/right/sections/layout/pages.tsx:1
  • apps/mobile/src/data/draft/store.ts has 830 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — apps/mobile/src/data/draft/store.ts:1
  • apps/web/src/features/resume/editor/write/picture-settings.tsx has 819 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/src/features/resume/editor/write/picture-settings.tsx:1
  • apps/web/src/features/career/coach.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/src/features/career/coach.tsx:1
  • packages/schema/src/resume/data.ts 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. — packages/schema/src/resume/data.ts:1

What to do

  • Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
R4 · Test Coverage8.6 / 10Strong✓ 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.

  • apps/server/src/static/agent-skills.test.ts:9 imports '../../../../plugins/reactive-resume/skills', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — apps/server/src/static/agent-skills.test.ts:9
  • packages/api/src/features/agent/review.integration.test.ts:100 imports '../../../../../migrations/', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — packages/api/src/features/agent/review.integration.test.ts:100
  • packages/api/src/features/ai-providers/approval.integration.test.ts:148 imports '../../../../../migrations/', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — packages/api/src/features/ai-providers/approval.integration.test.ts:148
  • packages/api/src/features/ai/usage.integration.test.ts:798 imports '../../../../../migrations/', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — packages/api/src/features/ai/usage.integration.test.ts:798
  • packages/api/src/features/applications/lanes.integration.test.ts:59 imports '../../../../../migrations/', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — packages/api/src/features/applications/lanes.integration.test.ts:59
  • packages/api/src/features/applications/trash.integration.test.ts:67 imports '../../../../../migrations/', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — packages/api/src/features/applications/trash.integration.test.ts:67
  • packages/api/src/features/career/jobs.integration.test.ts:113 imports '../../../../../migrations/', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either (2 further unresolvable import(s) in the same file). The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — packages/api/src/features/career/jobs.integration.test.ts:113
  • packages/api/src/features/career/role-recipient.integration.test.ts:143 imports '../../../../../migrations/', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — packages/api/src/features/career/role-recipient.integration.test.ts:143
  • packages/api/src/features/career/role-suggestions.integration.test.ts:47 imports '../../../../../migrations/', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — packages/api/src/features/career/role-suggestions.integration.test.ts:47
  • packages/api/src/features/career/service.integration.test.ts:126 imports '../../../../../migrations/', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — packages/api/src/features/career/service.integration.test.ts:126
  • packages/api/src/features/cover-letters/service.integration.test.ts:46 imports '../../../../../migrations/', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — packages/api/src/features/cover-letters/service.integration.test.ts:46
  • packages/api/src/features/documents/link-reconciliation.integration.test.ts:68 imports '../../../../../migrations/', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — packages/api/src/features/documents/link-reconciliation.integration.test.ts:68
  • packages/api/src/features/documents/listing.integration.test.ts:39 imports '../../../../../migrations/', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — packages/api/src/features/documents/listing.integration.test.ts:39
  • packages/api/src/features/documents/service.integration.test.ts:105 imports '../../../../../migrations/', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — packages/api/src/features/documents/service.integration.test.ts:105
  • packages/api/src/features/feedback/service.integration.test.ts:38 imports '../../../../../migrations/', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — packages/api/src/features/feedback/service.integration.test.ts:38
  • packages/api/src/features/resume/account-link.integration.test.ts:53 imports '../../../../../migrations/', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — packages/api/src/features/resume/account-link.integration.test.ts:53
  • packages/api/src/features/resume/address.integration.test.ts:53 imports '../../../../../migrations/', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — packages/api/src/features/resume/address.integration.test.ts:53
  • packages/api/src/features/web-access/credentials.integration.test.ts:45 imports '../../../../../migrations/', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — packages/api/src/features/web-access/credentials.integration.test.ts:45
  • packages/db/src/migrations.integration.test.ts:14 imports '../../../migrations', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — packages/db/src/migrations.integration.test.ts:14
  • packages/db/src/username-reservation.integration.test.ts:18 imports '../../../migrations/', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — packages/db/src/username-reservation.integration.test.ts:18
  • 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. (×20) — apps/mobile/src/features/applications/ApplicationsScreen.tsx:1, apps/mobile/src/features/today/screen.tsx:1, apps/mobile/app/(dev)/motion-lab/[lab].tsx:1, …

What to do

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

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

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

  • This repository declares test tooling, and the ✓ above records that declaration — but apps/server/src/static/agent-skills.test.ts and 19 other test file(s) in this workspace cannot be loaded at all: it imports a module that names no file in this repository, so the runner throws while collecting it and none of its cases execute. The wiring is present and the suite it points at does not run as written, which is why the tooling tick must not be read as a statement that the tests pass. Fix the unloadable file(s) — each one is reported with its failing import under Test Coverage — then the declared script exercises what it claims to. — apps/server/src/static/agent-skills.test.ts:9
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.

  • Unreachable from the 380 application, 52 tooling and 631 test entry point(s) detected in this repo. Gate removals on `pnpm run build` — an undetected custom entry would make these reachable.
  • no import path from any entry point (380 application, 52 tooling, 631 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/mobile/app/(app)/(tabs)/applications/index.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — apps/mobile/src/features/applications/ApplicationsScreen.tsx
  • no import path from any entry point (380 application, 52 tooling, 631 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/mobile/app/(app)/(tabs)/index.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — apps/mobile/src/features/today/screen.tsx
  • no import path from any entry point (380 application, 52 tooling, 631 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make (×2) — apps/mobile/app/(dev)/motion-lab/[lab].tsx, apps/mobile/app/(dev)/kit.tsx
  • no import path from any entry point (380 application, 52 tooling, 631 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/mobile/app/(app)/builder/[id]/(dock)/check.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/mobile/src/features/builder/check/CheckScreen.tsx
  • no import path from any entry point (380 application, 52 tooling, 631 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (apps/mobile/app/(app)/builder/[id]/section/[section]/[item]/index.tsx, apps/mobile/app/(app)/builder/[id]/section/[section]/new.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/mobile/src/features/builder/entry/EntryScreen.tsx
  • no import path from any entry point (380 application, 52 tooling, 631 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/mobile/app/(app)/applications/[id]/index.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — apps/mobile/src/features/applications/DetailScreen.tsx
  • no import path from any entry point (380 application, 52 tooling, 631 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/mobile/app/(app)/builder/[id]/menu.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/mobile/src/features/builder/menu/menu-screen.tsx
  • no import path from any entry point (380 application, 52 tooling, 631 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/mobile/src/features/settings/TimezoneScreen.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/mobile/src/features/settings/timezones.ts
  • no import path from any entry point (380 application, 52 tooling, 631 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/mobile/app/(app)/applications/[id]/interview.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/mobile/src/features/applications/InterviewSheet.tsx
  • no import path from any entry point (380 application, 52 tooling, 631 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (apps/mobile/app/(app)/builder/[id]/section/[section]/[item]/description.tsx, apps/mobile/app/(app)/builder/[id]/section/[section]/index.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — apps/mobile/src/features/builder/description/DescriptionScreen.tsx
  • no import path from any entry point (380 application, 52 tooling, 631 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (apps/mobile/app/(app)/career/knowledge/preferences.tsx, apps/mobile/app/(app)/career/knowledge/priorities.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/mobile/src/features/career/preferences.tsx
  • no import path from any entry point (380 application, 52 tooling, 631 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/mobile/app/(app)/documents/[id]/actions.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/mobile/src/features/documents/actions.tsx
  • no import path from any entry point (380 application, 52 tooling, 631 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/mobile/src/features/builder/check/CheckScreen.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/mobile/src/features/builder/check/issues.ts
  • no import path from any entry point (380 application, 52 tooling, 631 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/mobile/app/(app)/builder/[id]/assistant/proposals.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/mobile/src/features/builder/assistant/proposals-screen.tsx
  • no import path from any entry point (380 application, 52 tooling, 631 test roots considered), but 3 in-repo import(s) from 3 other file(s) do name it (apps/mobile/app/(app)/career/knowledge/stories/[id].tsx, apps/mobile/app/(app)/career/knowledge/stories/index.tsx, apps/mobile/app/(app)/career/knowledge/stories/new.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/mobile/src/features/career/stories.tsx
  • no import path from any entry point (380 application, 52 tooling, 631 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (apps/mobile/app/(app)/career/schedules/[id].tsx, apps/mobile/app/(app)/career/schedules/index.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — apps/mobile/src/features/career/schedules.tsx
  • no import path from any entry point (380 application, 52 tooling, 631 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/mobile/app/(app)/settings/ai/providers/[id].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/mobile/src/features/settings/ProviderScreen.tsx
  • no import path from any entry point (380 application, 52 tooling, 631 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/mobile/app/(app)/builder/[id]/assistant/index.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — apps/mobile/src/features/builder/assistant/assistant-screen.tsx
  • no import path from any entry point (380 application, 52 tooling, 631 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/mobile/app/(app)/builder/[id]/share/activity.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/mobile/src/features/builder/share/activity-screen.tsx
  • no import path from any entry point (380 application, 52 tooling, 631 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/mobile/app/(app)/applications/[id]/stage.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/mobile/src/features/applications/StageSheet.tsx
  • no import path from any entry point (380 application, 52 tooling, 631 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/mobile/app/(app)/applications/new.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/mobile/src/features/applications/SaveJobScreen.tsx
  • no import path from any entry point (380 application, 52 tooling, 631 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/mobile/app/(app)/builder/[id]/basics.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/mobile/src/features/builder/basics/BasicsScreen.tsx
  • no import path from any entry point (380 application, 52 tooling, 631 test roots considered), but 3 in-repo import(s) from 3 other file(s) do name it (apps/mobile/app/(auth)/forgot-password.tsx, apps/mobile/app/(auth)/register.tsx, apps/mobile/app/(auth)/sign-in.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/mobile/src/features/auth/SignInScreen.tsx
  • no import path from any entry point (380 application, 52 tooling, 631 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/mobile/app/(app)/career/knowledge/facts.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/mobile/src/features/career/facts.tsx
  • no import path from any entry point (380 application, 52 tooling, 631 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/mobile/app/(app)/letter/[id]/(dock)/index.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — apps/mobile/src/features/letters/letter-screen.tsx
  • no import path from any entry point (380 application, 52 tooling, 631 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/mobile/app/(app)/(tabs)/documents/index.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — apps/mobile/src/features/documents/library.tsx
  • no import path from any entry point (380 application, 52 tooling, 631 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/mobile/app/(app)/applications/[id]/prepare.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/mobile/src/features/workspace/PrepScreen.tsx
  • no import path from any entry point (380 application, 52 tooling, 631 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/mobile/app/(app)/builder/[id]/(dock)/share.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/mobile/src/features/builder/share/share-screen.tsx
  • no import path from any entry point (380 application, 52 tooling, 631 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/mobile/app/(app)/applications/[id]/practise.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/mobile/src/features/workspace/PracticeScreen.tsx
  • no import path from any entry point (380 application, 52 tooling, 631 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (apps/mobile/app/(app)/applications/[id]/debrief.tsx, apps/mobile/app/(app)/applications/[id]/library.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/mobile/src/features/workspace/DebriefScreen.tsx
  • no import path from any entry point (380 application, 52 tooling, 631 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/mobile/app/(app)/applications/[id]/messages.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/mobile/src/features/workspace/MessagesScreen.tsx
  • no import path from any entry point (380 application, 52 tooling, 631 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (apps/mobile/app/(app)/builder/[id]/preview.tsx, apps/mobile/app/(app)/builder/[id]/versions/[version].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/mobile/src/features/builder/preview/preview-screen.tsx
  • no import path from any entry point (380 application, 52 tooling, 631 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/mobile/app/(app)/builder/[id]/design/template.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/mobile/src/features/builder/design/TemplateScreen.tsx
  • no import path from any entry point (380 application, 52 tooling, 631 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/mobile/app/(app)/builder/[id]/share/web-page.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — apps/mobile/src/features/builder/share/web-page-screen.tsx
  • no import path from any entry point (380 application, 52 tooling, 631 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/mobile/app/(app)/builder/[id]/(dock)/index.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — apps/mobile/src/features/builder/overview/OverviewScreen.tsx
  • no import path from any entry point (380 application, 52 tooling, 631 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/mobile/app/(app)/builder/[id]/versions/index.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — apps/mobile/src/features/builder/versions/versions-screen.tsx
  • no import path from any entry point (380 application, 52 tooling, 631 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (apps/mobile/app/(app)/builder/[id]/download.tsx, apps/mobile/app/(app)/letter/[id]/(dock)/export.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/mobile/src/features/builder/download/download-screen.tsx
  • no import path from any entry point (380 application, 52 tooling, 631 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/mobile/app/(app)/applications/[id]/fit.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/mobile/src/features/workspace/FitScreen.tsx

What to do

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

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

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

  • Imported but not declared in any reachable package.json — installs work only by hoisting accident. (×2) — tooling/cloudflare/build.mjs:43, tooling/cloudflare/smoke.mjs:122
  • Declared in the root package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
  • Declared in packages/email/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
  • Only test files import it (first: packages/api/src/features/ai/service.docx.test.ts:4) — move it to devDependencies. — packages/api/package.json:72

What to do

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

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

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

  • apps/mobile/src/dev/storyboard/backdrop.tsx → apps/mobile/src/features/settings/SignOutDialog.tsx → apps/mobile/src/ui/index.ts → apps/mobile/src/ui/scaffold.tsx → apps/mobile/src/dev/storyboard/capture.tsx → apps/mobile/src/dev/storyboard/scenarios.ts → REDACTED → apps/mobile/src/dev/storyboard/backdrop.tsx (one verified cycle inside a mutually-dependent group of 12 files) — apps/mobile/src/dev/storyboard/backdrop.tsx:10
  • apps/web/src/features/career/coach-chat.tsx → apps/web/src/features/career/coach-thread.tsx → apps/web/src/features/career/coach-chat.tsx (one verified cycle inside a mutually-dependent group of 4 files) — apps/web/src/features/career/coach-chat.tsx:38
  • apps/web/src/features/career/workspace/fit-local.tsx → apps/web/src/features/career/workspace/fit.tsx → apps/web/src/features/career/workspace/fit-local.tsx — apps/web/src/features/career/workspace/fit-local.tsx:11
  • packages/db/src/schema/applications.ts → packages/db/src/schema/cover-letter.ts → packages/db/src/schema/applications.ts (one verified cycle inside a mutually-dependent group of 3 files) — packages/db/src/schema/applications.ts:13

What to do

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

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

  • `serve(…)` 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/server/src/index.ts:29

What to do

  • 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`.
X1 · Async correctness10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether the code avoids sync-over-async (deadlock-prone blocking on tasks) and async void.

Method: Roslyn syntax scan: async methods scanned for .Wait()/.GetAwaiter().GetResult() and async-void outside event handlers. Deterministic, hard fact per invocation.

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

Other · Code Health — Whether any branch is dead by construction — a switch arm whose label can never equal a case-normalised subject, or an `else if` whose predicate the arm above has already swallowed.

Method: Roslyn syntax + semantics: switch labels compared against the subject's own case normaliser, and if/else-if chains checked for a literal an earlier arm's containment test already swallows. Deterministic, provable per finding. Advisory.

X13 · Undrained process stream10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a child process that has BOTH standard streams redirected drains both — reading one to the end while the other is never read deadlocks once the child fills the unread pipe.

Method: Roslyn syntax + semantics: ProcessStartInfo launches with both streams redirected, checked for a drain of each stream across the enclosing type. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `spawn` imported from `child_process` whose stdout and stderr are both pipes (no options, no `stdio`, or `stdio` of `'pipe'`), bound to a local that never leaves its scope, where exactly one of the two streams is read, the other never, and the child’s `close`/`exit` (or the read stream’s end) is awaited; a shell redirect in the call’s arguments or a `kill` of the child suppresses it. The same rule reads Python’s `subprocess.Popen`, Dart’s `Process.start`, Ruby’s `Open3.popen3`, and Scala’s JDK process starts (`new ProcessBuilder(…).start()` with no `redirectErrorStream`/`redirectError`/`redirectOutput`/`inheritIO`, `Runtime.getRuntime.exec`) where one of `getInputStream`/`getErrorStream` is read and the other never while `waitFor()` is called or the read stream is read to its end. Deterministic, provable per finding. Advisory.

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

Other · Security — Whether a hand-rolled public/private IP check can be walked past — a method that unwraps IPv4-mapped IPv6 but returns the opposite verdict for the same host written as IPv4-compatible, 6to4 or NAT64.

Method: Roslyn syntax + semantics: methods that unwrap IPv4-mapped IPv6 and hand-roll IPv4 range carve-outs, checked for whether the IPv6 branch also accounts for the IPv4-compatible, 6to4 and NAT64 embeddings. Deterministic, provable per finding. Advisory.

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

Other · Code Health — Whether a loop that shortens a string until it fits a length budget has a floor — one with none grinds the value down to the empty string, or past it into a negative-length `Substring`.

Method: Roslyn syntax + semantics: while/do loops whose body's only effect on a string is to drop its last character, checked for whether anything — a direct comparison on the length, a body guard, a break — bounds that length below. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `while`/`do` loop whose body’s one assignment to a value is `x = x.slice(0, -1)` or `x = x.slice|substring|substr(0, x.length - 1)`, driven by a condition that reads `x.length` only as a term of a larger expression — never compared directly, never tested for truthiness, and with no other read of `x` — and whose body has no `break`, `return`, `throw` or `if` naming `x`. Deterministic, provable per finding. Advisory.

X17 · Uncapped recursion over a caller-supplied document1.6 / 10Critical✓ 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.

  • `captureDocument` is exported, takes a document from its caller (line 5) and hands it to `visit`, which calls itself at line 58 (`visit`) with a piece of `node` — and nowhere in `visit` 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 `visit` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — tooling/capture/content.ts:58
  • `estimateTokens` is exported and takes `value: unknown` from its caller, and it calls itself at line 39 (`estimateTokens`) with a piece of `value` (and at line 44) — and nowhere in `estimateTokens` 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 `estimateTokens` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — packages/api/src/features/agent/context.ts:39
  • `entryReview` is exported and takes `entry: Record<string, unknown>` from its caller, and it calls itself at line 27 (`entryReview`) with a piece of `entry` (and at line 35) — and nowhere in `entryReview` 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 `entryReview` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — packages/api/src/features/agent/review.ts:27
  • `detectJsonImportKind` is exported and takes `parsed: unknown` from its caller, and it calls itself at line 37 (`detectJsonImportKind`) with a piece of `parsed` — and nowhere in `detectJsonImportKind` 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 `detectJsonImportKind` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — apps/web/src/features/resume/import/read-file.ts:37
  • `encode` is exported and takes `value: unknown` from its caller, and it calls itself at line 4 (`encode`) with a piece of `value` (and at line 6) — and nowhere in `encode` 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 `encode` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — apps/mobile/src/data/codec.ts:4
  • `decode` is exported and takes `value: unknown` from its caller, and it calls itself at line 10 (`decode`) with a piece of `value` (and at line 14) — and nowhere in `decode` 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 `decode` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — apps/mobile/src/data/codec.ts:10
  • `parseResumeFileJSON` is exported and takes `value: unknown` from its caller, and it calls itself at line 80 (`parseResumeFileJSON`) with a piece of `value` — and nowhere in `parseResumeFileJSON` 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 `parseResumeFileJSON` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — apps/mobile/src/data/import.ts:80

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.
X2 · Cancellation propagation9.4 / 10Exemplary✓ Tool-verified

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

Method: Roslyn scan: every async method (excluding framework-fixed overrides/Blazor handlers) checked for CancellationToken parameter presence. Deterministic, adoption percentage. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same question: every named async function that itself makes a request an AbortSignal can cancel (global `fetch`, axios and its file-local instances, ky, ofetch) counts, and it is compliant when its parameters or body name a signal or it hands one of its own parameters to the request as options; signatures a framework fixes (JSX event handlers, route and lifecycle exports, request-first handlers, `override`, `'use server'` modules, TanStack `mutationFn`) are exempt unless they take a signal. Deterministic, adoption percentage.

  • Only 27/30 async functions that make a cancellable request (fetch, axios, ky, ofetch, got, undici, node:http) accept an AbortSignal or pass one on, so a request keeps running after whatever wanted it has given up — a page navigated away from, an unmounted component, a timed-out job. Take a `signal` (or an options object that carries one) and hand it to the request; where nothing could ever cancel the call, omitting it is a deliberate choice — judge against how the function is used.
  • `fetchText` 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 })`. — tooling/locales/generate-region-zones.mjs:13
  • `fetchSample` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — apps/web/src/features/ats-checker/checker.tsx:164
  • `uiFontFace` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — apps/web/src/features/applications/components/insights-view.tsx:323

What to do

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

Other · Code Health — Whether a `when` guard is free of side effects — a guard that increments a counter or assigns while deciding whether its arm matches applies that change during PATTERN MATCHING, on an arm that may not be selected, and skips it entirely when a short-circuit to its left answers first.

Method: Roslyn syntax: `when` guards on case labels and switch-expression arms, read for a mutation (`++`/`--`/assignment) sitting in a position the guard's own `&&`/`||`/`??`/`?:`/`?.` can skip. Deterministic, provable per finding. Advisory.

X24 · Document value interpolated into markup unescaped5.5 / 10Adequate✓ 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.

  • `escapeXml(href)` is text this program did not author, and it is written into the start of a URL attribute, where it chooses the scheme 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. HTML encoding does not help here — a `javascript:` URL contains nothing it changes; allow only http(s) or a relative path. — apps/server/src/static/seo.ts:82
  • `escapeHtml(href)` is text this program did not author, and it is written into the start of a URL attribute, where it chooses the scheme 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. HTML encoding does not help here — a `javascript:` URL contains nothing it changes; allow only http(s) or a relative path. — apps/server/src/static/web.ts:286
  • `url` is text this program did not author, and it is written into the start of a URL attribute, where it chooses the scheme 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. HTML encoding does not help here — a `javascript:` URL contains nothing it changes; allow only http(s) or a relative path. — apps/server/src/static/web.ts:292
  • `meta.title` 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. — apps/server/src/static/web.ts:360
  • `meta.description` is text this program did not author, and it is written into a quoted attribute value 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. — apps/server/src/static/web.ts:361
  • `serializeJsonLd(structuredData)` 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/src/features/homepage/faq.tsx:210
  • `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. — REDACTED:68
  • `escapeXml(node.href)` is text this program did not author, and it is written into the start of a URL attribute, where it chooses the scheme 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. HTML encoding does not help here — a `javascript:` URL contains nothing it changes; allow only http(s) or a relative path. — REDACTED:83
  • `escapeHtml(downloadUrl)` is text this program did not author, and it is written into the start of a URL attribute, where it chooses the scheme 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. HTML encoding does not help here — a `javascript:` URL contains nothing it changes; allow only http(s) or a relative path. (×2) — packages/pdf/src/html/document.ts:275, packages/pdf/src/html/document.ts:280
  • `escapeHtml(wordDownloadUrl)` is text this program did not author, and it is written into the start of a URL attribute, where it chooses the scheme 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. HTML encoding does not help here — a `javascript:` URL contains nothing it changes; allow only http(s) or a relative path. — packages/pdf/src/html/document.ts:278
  • `escapeHtml(creditUrl)` is text this program did not author, and it is written into the start of a URL attribute, where it chooses the scheme 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. HTML encoding does not help here — a `javascript:` URL contains nothing it changes; allow only http(s) or a relative path. — packages/pdf/src/html/document.ts:291
  • `whitespace` is text this program did not author, and it is written into the text of an element through `insertAdjacentHTML` 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. (×2) — REDACTED:90, REDACTED:99
  • `child.innerHTML` 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:114
  • `kind` 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. — tooling/autofill/lab.ts:17
  • `fixtureForm(kind)` 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. — tooling/autofill/lab.ts:27
  • `OTHER_ORIGIN` is text this program did not author, and it is written into the start of a URL attribute, where it chooses the scheme 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 encoding does not help here — a `javascript:` URL contains nothing it changes; allow only http(s) or a relative path. — tooling/autofill/lab.ts:30
  • `html.replace(/<\/(?:p|div|li|h[1-6]|section)>|<br\s*\/?>/gi,"\n")` 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. — tooling/capture/content.ts:8

What to do

  • Each finding names the expression, the attribute it lands in and the line. Confirm the value's origin from the read this analyzer traced, then escape it at the sink or validate it against the shape the attribute accepts before interpolating.
X25 · Inert configuration knob10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a value the caller is invited to supply is the value the type actually uses — a constructor parameter stored in a private field that nothing ever reads while the default it was given is spelled out a second time at the site that should have read it, a keyed lookup that falls back to a different setting than the one its key names while the same type falls back to the matching one for that same key, or a culture-sensitive parse given no format provider by a type that feeds its own settable culture to the same kind of parse elsewhere, or a number an entry point writes to standard output under the host's culture while the same entry point formats with the invariant culture elsewhere. Either way, every caller who supplies a value silently gets something else.

Method: Roslyn syntax: private instance fields of a non-partial type assigned in a constructor from one of its own parameters with a `??` fallback, checked for whether anything in the type body reads the field and whether that same fallback expression is spelled out again outside the constructor; and `??` fallbacks onto a member access from a lookup call carrying exactly one string literal, grouped by that key across the type and checked for a fallback member whose folded name disagrees with the key while a sibling site for the same key agrees with it. On a repository with no .NET source the first two arms read JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `#x`, `private` or `private` parameter-property instance field filled in the constructor from a parameter (or one member of one) through `??`/`||` or a parameter default, never read anywhere in the file by name, whose constructed default is spelled again in the class body; and `lookup("key") ?? s.member` grouped by key per class, or per module outside every class. The culture arm has no JavaScript counterpart: its parses take no locale. Deterministic, provable per finding. Advisory.

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.

X29 · Per-element action decided by a fixed element10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a decision taken once per element is taken ABOUT that element — a test inside a counted loop that reads a fixed subscript of the very collection its guarded statement indexes by the loop variable applies element zero's answer to all of them, so the elements that differ from it are all handled wrongly, and in the same direction.

Method: Roslyn syntax only, no semantic model: every `for` statement declaring exactly ONE loop variable, and every `if` inside its body that is not under a nested loop or a lambda. A site enters the population when the `if`’s condition never mentions the loop variable while the statement it guards indexes some collection by that variable ALONE (`c[i]`; `c[i + 1]` and `c[i, j]` are outside it). A finding additionally needs the AGREEING TWIN at the same-collection grain: the condition must read THAT SAME collection at a subscript that does not move — written into the condition, or reached through a local declared BEFORE the loop, so an alias bound inside the body is not followed. Both collection expressions must be simple identifiers. On a repository with no .NET source the same rule reads JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `for (let|var|const x = …; …; …)` with one declarator and a braced body, an alias followed only when it is declared before the loop in a block that encloses it and never assigned inside the loop. Deterministic, provable per finding. Advisory.

X3 · Exception handling5.5 / 10Adequate✓ Tool-verified

Other · Code Health — Whether exceptions are handled rather than silently swallowed or rethrown with lost stack traces.

Method: Roslyn syntax scan: every catch clause counted; empty catches and bare rethrows flagged. Population is all catch clauses, not estimated. Deterministic, hard fact.

  • 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. (×21) — tooling/calm/dev.mjs:27, tooling/autofill/lab.ts:52, packages/schema/src/resume/dates.ts:274, …
  • `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it. (×16) — packages/utils/src/deferred-request.ts:58, packages/utils/src/http.ts:108, packages/utils/src/http.ts:124, …
  • `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, or keep only the failure you expect and rethrow the rest (`catch (e) { if (!(e instanceof SyntaxError)) throw e; … }`, or test `e.name`), because a JavaScript catch takes every exception, programming errors included. (×3) — packages/schema/src/resume/period.ts:112, packages/import/src/job-posting.ts:73, packages/api/src/features/auth/export-uploads.ts:41

What to do

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

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

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

X5 · Nullable reference types4.0 / 10Weak✓ Tool-verified

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

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

  • 2/8 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.

What to do

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

WCAG coverage — what static analysis assessed

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

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

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

Reference — by lens

The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.

LensScoreRatingImpact
Code Health52%Adequate — gated by D1, D2, X5Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Architecture41%Weak — gated by R9, AX7Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Maturity85%StrongStrongest area.
Readiness49%Weak — gated by P3Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security56%Adequate — gated by D29, C1Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Accessibility58%Adequate — gated by AC4Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Performance60%AdequateAcceptable, with room to improve.
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 — 20 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 — 40 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
  • X7 Silent fallback defaults — 17 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.

  • C3 Audit Trail — Repo shows no audit-logging mechanism (an audit-log table or model, an ORM write hook that records changes — a TypeORM/MikroORM subscriber, a Sequelize or Mongoose hook, Prisma middleware — or a change-history plugin such as mongoose-history or sequelize-paper-trail) for sensitive changes — absence of evidence is not evidence of a working control. Record an audit trail in code (or document where it lives) so this dimension can be scored.
Not included — 40 check(s) not relevant to this codebase

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

  • AX1 Captive dependencies — not 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
  • AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No class in this Kotlin code is a Spring, JSR-330 or CDI singleton bean. No function in this Python code is served by a threaded web framework (a Flask, Bottle or FastAPI route, a Django or Pyramid view), so no module is shared between request threads. No Swift request handler (a Vapor, Hummingbird, Kitura, Swifter or Perfect route handler, as a method or a registered closure) is declared, so no state is shared between request threads. TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
  • AX4 Dependency direction — not applicable to a vertical-slice architecture (the inward-dependency rule is for layered/clean styles)
  • AX8 Test isolation — no test/production split to check
  • AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
  • AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • AXR1 Runtime accessibility — compose up failed (exit 17 — an image could not be built) — failed to solve: process "/bin/sh -c pnpm runtime set node ${NODE_VERSION} -g --config.store-dir=/pnpm/runtime-store" did not complete successfully: exit code: 1; 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.
  • D11 Test Reliability — Test reliability not measured — JavaScript/TypeScript suite did not run
  • D16 Bus Factor — single-maintainer repository — bus factor is not applicable
  • D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
  • D21 Naming Consistency — N/A — too few peers to establish a naming convention (13519 declarations, no unit with a dominant convention).
  • D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
  • D25 ADR Conformance — None of 2 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.
  • 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.
  • D8 Code Coverage — Coverage not measured — JavaScript/TypeScript suite
  • DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (1 value object(s))
  • ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and this analysis resolves a call's owner only where the receiver's type is written down in the source. Reported as guidance rather than measured
  • 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
  • P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JVM, JavaScript/TypeScript, Python, Swift source, so there is no service whose uptime a failing dependency could take down
  • P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
  • PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for tinybench, mitata, benchmark.js, benny or vitest `bench(...)` calls in files that import them (or `*.bench.*` files), or one of those in a package.json, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
  • PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
  • R5 Dependency Freshness — uses a pnpm lockfile — dependency freshness not measured here; JS/npm CVEs are scored in D30 (Dependency Vulnerabilities), which answers every ecosystem
  • SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X18 Disposal-pattern correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X20 Mistyped argument guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X27 Collection changed while being enumerated — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
  • X4 Structured logging — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.

Appendix A — Findings (grouped)

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

Critical — 89 finding(s)
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • + 35 more in this group — see findings.md.
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D31 · IaC & Container Security · High IaC · ×5
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
R9 · Circular Imports · Import cycle (2 files) · ×3
  • Import cycle (2 files) apps/web/src/features/career/coach-chat.tsx:38 — apps/web/src/features/career/coach-chat.tsx → apps/web/src/features/career/coach-thread.tsx → apps/web/src/features/career/coach-chat.tsx (one verified cycle inside a mutually-dependent group of 4 files)
  • Import cycle (2 files) apps/web/src/features/career/workspace/fit-local.tsx:11 — apps/web/src/features/career/workspace/fit-local.tsx → apps/web/src/features/career/workspace/fit.tsx → apps/web/src/features/career/workspace/fit-local.tsx
  • Import cycle (2 files) packages/db/src/schema/applications.ts:13 — packages/db/src/schema/applications.ts → packages/db/src/schema/cover-letter.ts → packages/db/src/schema/applications.ts (one verified cycle inside a mutually-dependent group of 3 files)
AC4 · Keyboard semantics · Click handler on a non-interactive <div> · ×2
  • Click handler on a non-interactive <div> apps/web/src/features/resume/editor/page-overlay.tsx:84 — 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/src/routes/builder/letter/-components/letter-page.tsx:238 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
AC2 · Forms & labels · <label> that labels no control · ×1
  • <label> that labels no control apps/web/src/features/career/workspace/fit.tsx:659 — 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.
AC2 · Forms & labels · Custom control with no accessible name on <div> · ×1
  • Custom control with no accessible name on <div> apps/web/src/routes/builder/letter/-components/letter-page.tsx:238 — This <div> carries a click handler, which makes it a control, but it has no text, aria-label or labelled child (the icon-only case), so assistive tech has no name to announce for it. Note that switching it to <button type="button"> — the right fix for its keyboard operability — does not give it a name either: an icon-only button still needs one. Add visible text or an aria-label.
AC4 · Keyboard semantics · Click handler on a non-interactive <li> · ×1
  • Click handler on a non-interactive <li> apps/web/src/features/resume/editor/check/check-panel.tsx:174 — 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 · Focusable <section> isn't keyboard-operable · ×1
  • Focusable <section> isn't keyboard-operable apps/web/src/routes/builder/$resumeId/-components/page-canvas.tsx:155 — This <section> carries tabIndex={0}, so it is in the tab order and a keyboard user will land on it — but its only behaviour is bound to pointerdown, pointer gestures a keyboard cannot produce, and there is no key handler. The tab stop leads nowhere. Bind the same behaviour to a key handler, or provide an equivalent control elsewhere. Give it a role as well, so assistive tech can announce what it is.
D28 · Secrets (history) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D30 · Dependency Vulnerabilities · High CVE · ×1
  • REDACTED
R8 · Dependency Hygiene · Unlisted import '@formepdf/core' · ×1
  • Unlisted import '@formepdf/core' tooling/cloudflare/build.mjs:43 — Imported but not declared in any reachable package.json — installs work only by hoisting accident.
R8 · Dependency Hygiene · Unlisted import '@orpc/client' · ×1
  • Unlisted import '@orpc/client' tooling/cloudflare/smoke.mjs:122 — Imported but not declared in any reachable package.json — installs work only by hoisting accident.
R9 · Circular Imports · Import cycle (7 files) · ×1
  • Import cycle (7 files) apps/mobile/src/dev/storyboard/backdrop.tsx:10 — apps/mobile/src/dev/storyboard/backdrop.tsx → apps/mobile/src/features/settings/SignOutDialog.tsx → apps/mobile/src/ui/index.ts → apps/mobile/src/ui/scaffold.tsx → apps/mobile/src/dev/storyboard/capture.tsx → apps/mobile/src/dev/storyboard/scenarios.ts → REDACTED → apps/mobile/src/dev/storyboard/backdrop.tsx (one verified cycle inside a mutually-dependent group of 12 files)
Serious — 1903 finding(s)
D15 · Churn × Complexity Hotspots · Hotspot · ×215
  • Hotspot: apps/web/src/features/applications/components/add-application-dialog.tsx apps/web/src/features/applications/components/add-application-dialog.tsx:188 — apps/web/src/features/applications/components/add-application-dialog.tsx changed 25 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 198 in add-application-dialog.AddApplicationForm at line 188. 16 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 07:52:29 +01:00' --until='2026-11-14 07:52:29 +01:00' --full-history --no-merges -- apps/web/src/features/applications/components/add-application-dialog.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: packages/auth/src/config.ts packages/auth/src/config.ts:797 — packages/auth/src/config.ts changed 40 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 109 in config.getAuthConfig at line 797. 23 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 07:52:29 +01:00' --until='2026-11-14 07:52:29 +01:00' --full-history --no-merges -- packages/auth/src/config.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: apps/web/src/features/documents/documents-page.tsx apps/web/src/features/documents/documents-page.tsx:80 — apps/web/src/features/documents/documents-page.tsx changed 23 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 121 in documents-page.DocumentsPage at line 80. 14 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 07:52:29 +01:00' --until='2026-11-14 07:52:29 +01:00' --full-history --no-merges -- apps/web/src/features/documents/documents-page.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: apps/web/src/routes/dashboard/applications/index.tsx apps/web/src/routes/dashboard/applications/index.tsx:121 — apps/web/src/routes/dashboard/applications/index.tsx changed 31 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 84 in index.RouteComponent at line 121. 12 of those changes were fix/bug commits, and the other 19 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 07:52:29 +01:00' --until='2026-11-14 07:52:29 +01:00' --full-history --no-merges -- apps/web/src/routes/dashboard/applications/index.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: apps/web/src/features/assistant/conversation.tsx apps/web/src/features/assistant/conversation.tsx:102 — apps/web/src/features/assistant/conversation.tsx changed 26 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 71 in conversation.Conversation at line 102. 17 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 07:52:29 +01:00' --until='2026-11-14 07:52:29 +01:00' --full-history --no-merges -- apps/web/src/features/assistant/conversation.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: apps/web/src/features/documents/new-document-dialog.tsx apps/web/src/features/documents/new-document-dialog.tsx:93 — apps/web/src/features/documents/new-document-dialog.tsx changed 26 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 71 in new-document-dialog.NewDocument at line 93. 17 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 07:52:29 +01:00' --until='2026-11-14 07:52:29 +01:00' --full-history --no-merges -- apps/web/src/features/documents/new-document-dialog.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: apps/web/src/features/career/workspace/messages.tsx apps/web/src/features/career/workspace/messages.tsx:625 — apps/web/src/features/career/workspace/messages.tsx changed 20 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 91 in messages.ProposalCard at line 625. 12 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 07:52:29 +01:00' --until='2026-11-14 07:52:29 +01:00' --full-history --no-merges -- apps/web/src/features/career/workspace/messages.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: apps/web/src/features/career/workspace/practise.tsx apps/web/src/features/career/workspace/practise.tsx:373 — apps/web/src/features/career/workspace/practise.tsx changed 13 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 121 in practise.Session at line 373. 10 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 07:52:29 +01:00' --until='2026-11-14 07:52:29 +01:00' --full-history --no-merges -- apps/web/src/features/career/workspace/practise.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: apps/mobile/src/features/career/offers.tsx apps/mobile/src/features/career/offers.tsx:31 — apps/mobile/src/features/career/offers.tsx changed 23 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 67 in offers.ScopedOffersScreen at line 31. 14 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 07:52:29 +01:00' --until='2026-11-14 07:52:29 +01:00' --full-history --no-merges -- apps/mobile/src/features/career/offers.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: apps/web/src/features/career/workspace/apply.tsx apps/web/src/features/career/workspace/apply.tsx:490 — apps/web/src/features/career/workspace/apply.tsx changed 21 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 68 in apply.AnswerCard at line 490. 11 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 07:52:29 +01:00' --until='2026-11-14 07:52:29 +01:00' --full-history --no-merges -- apps/web/src/features/career/workspace/apply.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: apps/web/src/features/career/schedule-sheet.tsx apps/web/src/features/career/schedule-sheet.tsx:138 — apps/web/src/features/career/schedule-sheet.tsx changed 10 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 131 in schedule-sheet.ScheduleSheet at line 138. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 07:52:29 +01:00' --until='2026-11-14 07:52:29 +01:00' --full-history --no-merges -- apps/web/src/features/career/schedule-sheet.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: apps/web/src/features/career/offer-entry.tsx apps/web/src/features/career/offer-entry.tsx:255 — apps/web/src/features/career/offer-entry.tsx changed 15 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 87 in offer-entry.OfferForm at line 255. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 07:52:29 +01:00' --until='2026-11-14 07:52:29 +01:00' --full-history --no-merges -- apps/web/src/features/career/offer-entry.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: apps/web/src/features/career/workspace/shell.tsx apps/web/src/features/career/workspace/shell.tsx:123 — apps/web/src/features/career/workspace/shell.tsx changed 21 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 62 in shell.Workspace at line 123. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 07:52:29 +01:00' --until='2026-11-14 07:52:29 +01:00' --full-history --no-merges -- apps/web/src/features/career/workspace/shell.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: apps/web/src/features/resume/editor/write/rich-text-editor-field.tsx apps/web/src/features/resume/editor/write/rich-text-editor-field.tsx:214 — apps/web/src/features/resume/editor/write/rich-text-editor-field.tsx changed 13 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 94 in rich-text-editor-field.RichTextEditor at line 214. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 07:52:29 +01:00' --until='2026-11-14 07:52:29 +01:00' --full-history --no-merges -- apps/web/src/features/resume/editor/write/rich-text-editor-field.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: apps/web/src/features/assistant/assistant-panel.tsx apps/web/src/features/assistant/assistant-panel.tsx:59 — apps/web/src/features/assistant/assistant-panel.tsx changed 20 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 61 in assistant-panel.AssistantPanel at line 59. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 07:52:29 +01:00' --until='2026-11-14 07:52:29 +01:00' --full-history --no-merges -- apps/web/src/features/assistant/assistant-panel.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: apps/web/src/features/career/coach.tsx apps/web/src/features/career/coach.tsx:115 — apps/web/src/features/career/coach.tsx changed 15 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 79 in coach.CoachPage at line 115. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 07:52:29 +01:00' --until='2026-11-14 07:52:29 +01:00' --full-history --no-merges -- apps/web/src/features/career/coach.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: apps/web/src/features/letters/store.ts apps/web/src/features/letters/store.ts:388 — apps/web/src/features/letters/store.ts changed 12 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 97 in store.useLetterEditorStore at line 388. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 07:52:29 +01:00' --until='2026-11-14 07:52:29 +01:00' --full-history --no-merges -- apps/web/src/features/letters/store.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: apps/mobile/src/data/fixture-operations.ts apps/mobile/src/data/fixture-operations.ts:178 — apps/mobile/src/data/fixture-operations.ts changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 192 in fixture-operations.fixtureWrite at line 178. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 07:52:29 +01:00' --until='2026-11-14 07:52:29 +01:00' --full-history --no-merges -- apps/mobile/src/data/fixture-operations.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: packages/import/src/pdf-lines.ts packages/import/src/pdf-lines.ts:207 — packages/import/src/pdf-lines.ts changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 278 in pdf-lines.headingTest at line 207. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 07:52:29 +01:00' --until='2026-11-14 07:52:29 +01:00' --full-history --no-merges -- packages/import/src/pdf-lines.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: packages/api/src/features/agent/service.ts packages/api/src/features/agent/service.ts:903 — packages/api/src/features/agent/service.ts changed 33 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 33 in service.createAgent at line 903. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 07:52:29 +01:00' --until='2026-11-14 07:52:29 +01:00' --full-history --no-merges -- packages/api/src/features/agent/service.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: apps/web/src/features/applications/components/detail/activity.tsx apps/web/src/features/applications/components/detail/activity.tsx:65 — apps/web/src/features/applications/components/detail/activity.tsx changed 16 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 65 in activity.Activity at line 65. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 07:52:29 +01:00' --until='2026-11-14 07:52:29 +01:00' --full-history --no-merges -- apps/web/src/features/applications/components/detail/activity.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: apps/web/src/features/applications/components/application-detail-sheet.tsx apps/web/src/features/applications/components/application-detail-sheet.tsx:206 — apps/web/src/features/applications/components/application-detail-sheet.tsx changed 28 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 36 in application-detail-sheet.Detail at line 206. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 07:52:29 +01:00' --until='2026-11-14 07:52:29 +01:00' --full-history --no-merges -- apps/web/src/features/applications/components/application-detail-sheet.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: apps/web/src/features/applications/components/import-applications-sheet.tsx apps/web/src/features/applications/components/import-applications-sheet.tsx:86 — apps/web/src/features/applications/components/import-applications-sheet.tsx changed 13 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 75 in import-applications-sheet.ImportApplicationsSheet at line 86. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 07:52:29 +01:00' --until='2026-11-14 07:52:29 +01:00' --full-history --no-merges -- apps/web/src/features/applications/components/import-applications-sheet.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: apps/web/src/routes/builder/$resumeId/-components/page-canvas.tsx apps/web/src/routes/builder/$resumeId/-components/page-canvas.tsx:71 — apps/web/src/routes/builder/$resumeId/-components/page-canvas.tsx changed 14 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 65 in page-canvas.ResumePageCanvas at line 71. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 07:52:29 +01:00' --until='2026-11-14 07:52:29 +01:00' --full-history --no-merges -- apps/web/src/routes/builder/$resumeId/-components/page-canvas.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: apps/web/src/features/applications/components/list-view.tsx apps/web/src/features/applications/components/list-view.tsx:115 — apps/web/src/features/applications/components/list-view.tsx changed 22 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 41 in list-view.ApplicationList at line 115. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 07:52:29 +01:00' --until='2026-11-14 07:52:29 +01:00' --full-history --no-merges -- apps/web/src/features/applications/components/list-view.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • + 190 more in this group — see findings.md.
D3 · God Classes · FunctionTooLong · ×209
  • FunctionTooLong: kit.KitPage apps/web/src/routes/builder/kit.tsx:221 — FunctionTooLong — KitPage runs 880 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 780 over it, 8.80× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: store.createDraftStore apps/mobile/src/data/draft/store.ts:91 — FunctionTooLong — createDraftStore runs 597 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 497 over it, 5.97× 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: practise.Session apps/web/src/features/career/workspace/practise.tsx:373 — FunctionTooLong — Session runs 517 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 417 over it, 5.17× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: pdf-lines.headingTest packages/import/src/pdf-lines.ts:207 — FunctionTooLong — headingTest runs 491 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 391 over it, 4.91× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: answer-library.AnswerLibrary apps/web/src/features/career/workspace/answer-library.tsx:49 — FunctionTooLong — AnswerLibrary runs 463 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 363 over it, 4.63× 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: screen.TodayScreen apps/mobile/src/features/today/screen.tsx:64 — FunctionTooLong — TodayScreen runs 450 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 350 over it, 4.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: prepare-review.ReviewForm apps/web/src/features/career/workspace/prepare-review.tsx:49 — FunctionTooLong — ReviewForm runs 414 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 314 over it, 4.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: interview-dialog.InterviewDialog apps/web/src/features/applications/components/interview-dialog.tsx:160 — FunctionTooLong — InterviewDialog runs 380 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 280 over it, 3.80× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: trash-page.TrashPage apps/web/src/features/trash/trash-page.tsx:81 — FunctionTooLong — TrashPage runs 374 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 274 over it, 3.74× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: index.RouteComponent apps/web/src/routes/dashboard/applications/index.tsx:121 — FunctionTooLong — RouteComponent runs 371 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 271 over it, 3.71× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: coach.CoachPage apps/web/src/features/career/coach.tsx:115 — FunctionTooLong — CoachPage runs 363 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 263 over it, 3.63× 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: config.getAuthConfig packages/auth/src/config.ts:797 — FunctionTooLong — getAuthConfig runs 362 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 262 over it, 3.62× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: messages.ProposalCard apps/web/src/features/career/workspace/messages.tsx:625 — FunctionTooLong — ProposalCard 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: offers.ScopedOffersScreen apps/mobile/src/features/career/offers.tsx:31 — FunctionTooLong — ScopedOffersScreen 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: search.ScopedSearchScreen apps/mobile/src/features/documents/search.tsx:31 — FunctionTooLong — ScopedSearchScreen 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: EntryScreen.EntryScreen apps/mobile/src/features/builder/entry/EntryScreen.tsx:77 — FunctionTooLong — EntryScreen runs 312 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 212 over it, 3.12× 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: ats-messages.getPdfFindingMessage apps/mobile/src/features/public/ats-messages.ts:21 — FunctionTooLong — getPdfFindingMessage 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: preparation.Preparation apps/web/src/features/career/workspace/preparation.tsx:40 — FunctionTooLong — Preparation 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.
  • FunctionTooLong: conversation.Conversation apps/web/src/features/assistant/conversation.tsx:102 — FunctionTooLong — Conversation runs 294 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 194 over it, 2.94× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: actions.ScopedDocumentActionsScreen apps/mobile/src/features/documents/actions.tsx:40 — FunctionTooLong — ScopedDocumentActionsScreen runs 292 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 192 over it, 2.92× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: profile.ProfileDialog apps/web/src/features/settings/profile.tsx:467 — FunctionTooLong — ProfileDialog runs 291 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 191 over it, 2.91× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: import.ScopedImportScreen apps/mobile/src/features/documents/import.tsx:43 — FunctionTooLong — ScopedImportScreen runs 290 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 190 over it, 2.90× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: application-packet.PacketForm apps/web/src/features/career/workspace/application-packet.tsx:55 — FunctionTooLong — PacketForm runs 285 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 185 over it, 2.85× 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: kit.Kit apps/mobile/app/(dev)/kit.tsx:110 — FunctionTooLong — Kit runs 283 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 183 over it, 2.83× 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: activity.Activity apps/web/src/features/applications/components/detail/activity.tsx:65 — FunctionTooLong — Activity runs 283 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 183 over it, 2.83× 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.
  • + 184 more in this group — see findings.md.
D15 · Churn × Complexity Hotspots · Repeated repair · ×75
  • Repeated repair: apps/web/src/features/career/shared.tsx apps/web/src/features/career/shared.tsx:119 — apps/web/src/features/career/shared.tsx changed 14 times in last 90 days and 10 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 9 (its worst body is shared.withUndo at line 119), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(web): keep touch hit areas on their own controls”; “fix: persist contact and interview deletion through exit”; “fix(career): persist workspace answer removal and safe Undo”; “fix: prepare Career deletions before acknowledging Undo”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 07:52:29 +01:00' --until='2026-11-14 07:52:29 +01:00' --full-history --no-merges -- apps/web/src/features/career/shared.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: apps/web/src/features/applications/components/insights-view.tsx apps/web/src/features/applications/components/insights-view.tsx:53 — apps/web/src/features/applications/components/insights-view.tsx changed 17 times in last 90 days and 9 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 14 (its worst body is insights-view.ApplicationInsights at line 53), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix: localize interface numerals and finish deferred layouts”; “fix: complete letter preview fallbacks and label fitting (RX-208)”; “fix: finish deferred application tags, letter previews and Insights styling (RX-208)”; “fix(web): keep 12px labels inside phone cells (RX-204)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 07:52:29 +01:00' --until='2026-11-14 07:52:29 +01:00' --full-history --no-merges -- apps/web/src/features/applications/components/insights-view.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: apps/server/src/http/auth.ts apps/server/src/http/auth.ts:195 — apps/server/src/http/auth.ts changed 12 times in last 90 days and 9 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 15 (its worst body is auth.resumeOAuth at line 195), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix: improve Arabic phone language and account emails (#3793)”; “fix: harden MCP OAuth connections and WebMCP errors (RX-108)”; “fix: bind account writes to the page that rendered them”; “fix: security hardening across auth, API, AI, imports and deployment (#3662)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 07:52:29 +01:00' --until='2026-11-14 07:52:29 +01:00' --full-history --no-merges -- apps/server/src/http/auth.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: apps/web/src/dialogs/resume/index.tsx apps/web/src/dialogs/resume/index.tsx:40 — apps/web/src/dialogs/resume/index.tsx changed 15 times in last 90 days and 8 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 9 (its worst body is index.ResumeDialog at line 40), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix: preserve unfinished document tags and failed rename drafts (#3867)”; “fix(ui): design system, copy and parity polish (RX-142) (#3845)”; “fix(builder): resume builder editing polish (RX-137) (#3837)”; “fix: number document copies and make duplicate names editable (#3836)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 07:52:29 +01:00' --until='2026-11-14 07:52:29 +01:00' --full-history --no-merges -- apps/web/src/dialogs/resume/index.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: apps/web/src/routes/builder/$resumeId/-components/editor-bar.tsx apps/web/src/routes/builder/$resumeId/-components/editor-bar.tsx:85 — apps/web/src/routes/builder/$resumeId/-components/editor-bar.tsx changed 13 times in last 90 days and 8 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 7 (its worst body is editor-bar.ModeTabs at line 85), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix: localize interface numerals and finish deferred layouts”; “fix: keep tablet titles readable beside issue counts”; “fix: retain phone toolbar and node selection keyboard flow”; “fix: preserve focus and compact screen layouts”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 07:52:29 +01:00' --until='2026-11-14 07:52:29 +01:00' --full-history --no-merges -- apps/web/src/routes/builder/$resumeId/-components/editor-bar.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: packages/fonts/src/index.ts packages/fonts/src/index.ts:219 — packages/fonts/src/index.ts changed 12 times in last 90 days and 8 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 8 (its worst body is index.resolveBoldFontWeight at line 219), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(pdf): render Georgian text with a Noto Georgian fallback (#3971)”; “fix(pdf): fall back to Indic, Ethiopic and Khmer fonts automatically (#3788)”; “fix(pdf): load CJK resume previews on slow connections (#3633)”; “fix(pdf): use correct font fallback for Unicode arrows (#3617)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 07:52:29 +01:00' --until='2026-11-14 07:52:29 +01:00' --full-history --no-merges -- packages/fonts/src/index.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: packages/utils/src/locale.ts packages/utils/src/locale.ts:109 — packages/utils/src/locale.ts changed 12 times in last 90 days and 8 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 5 (its worst body is locale.getLanguageName at line 109), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(pdf): render Georgian text with a Noto Georgian fallback (#3971)”; “fix(public): homepage, public pages and sign-in polish (RX-135) (#3833)”; “fix: detect first-visit language without varying shared HTML”; “fix(pdf): fall back to Indic, Ethiopic and Khmer fonts automatically (#3788)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 07:52:29 +01:00' --until='2026-11-14 07:52:29 +01:00' --full-history --no-merges -- packages/utils/src/locale.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: apps/web/src/features/resume/editor/check/check-panel.tsx apps/web/src/features/resume/editor/check/check-panel.tsx:322 — apps/web/src/features/resume/editor/check/check-panel.tsx changed 12 times in last 90 days and 8 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 7 (its worst body is check-panel.DeepCheck at line 322), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix: localize interface numerals and finish deferred layouts”; “fix(web): finish label floor and indicator tokens (RX-204)”; “fix(ui): unslop polish pass across web and mobile (RX-178) (#3851)”; “fix(ui): design system, copy and parity polish (RX-142) (#3845)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 07:52:29 +01:00' --until='2026-11-14 07:52:29 +01:00' --full-history --no-merges -- apps/web/src/features/resume/editor/check/check-panel.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: apps/web/src/features/documents/use-start-document.ts apps/web/src/features/documents/use-start-document.ts:80 — apps/web/src/features/documents/use-start-document.ts changed 10 times in last 90 days and 8 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 5 (its worst body is use-start-document.useStartDocument.startBlank at line 80), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix: complete document language and assistant polish”; “fix: dashboard, document library and settings polish (RX-136) (#3835)”; “fix(public): ATS hand-off, not-found pages and a shorter sign-up path (RX-146) (#3799)”; “fix: complete cover letter and application workflows”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 07:52:29 +01:00' --until='2026-11-14 07:52:29 +01:00' --full-history --no-merges -- apps/web/src/features/documents/use-start-document.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: apps/web/src/features/auth/pages/forgot-password.tsx apps/web/src/features/auth/pages/forgot-password.tsx:34 — apps/web/src/features/auth/pages/forgot-password.tsx changed 13 times in last 90 days and 7 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 13 (its worst body is forgot-password.ForgotPasswordPage at line 34), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix: recover expired sessions and sign-in flows”; “fix: preserve focus and compact screen layouts”; “fix(ui): design system, copy and parity polish (RX-142) (#3845)”; “fix(public): homepage, public pages and sign-in polish (RX-135) (#3833)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 07:52:29 +01:00' --until='2026-11-14 07:52:29 +01:00' --full-history --no-merges -- apps/web/src/features/auth/pages/forgot-password.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: packages/db/src/schema/auth.ts packages/db/src/schema/auth.ts:7 — packages/db/src/schema/auth.ts changed 10 times in last 90 days and 7 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 1 (its worst body is auth.lower at line 7), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix: correctness, performance and docs fixes from a codebase review (#3968)”; “fix: improve Arabic phone language and account emails (#3793)”; “fix: float application bulk actions and enable auth joins (#3675)”; “fix: security hardening across auth, API, AI, imports and deployment (#3662)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 07:52:29 +01:00' --until='2026-11-14 07:52:29 +01:00' --full-history --no-merges -- packages/db/src/schema/auth.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: apps/web/src/features/career/hooks.ts apps/web/src/features/career/hooks.ts:142 — apps/web/src/features/career/hooks.ts changed 9 times in last 90 days and 7 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 7 (its worst body is hooks.useWorkspace.save at line 142), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix: preserve practice recovery and approved background work”; “fix: practice backed stories without an interview”; “fix(applications): interview, contact, calendar and history polish (RX-128) (#3827)”; “fix(career): AI in letters and applications polish (RX-122) (#3820)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 07:52:29 +01:00' --until='2026-11-14 07:52:29 +01:00' --full-history --no-merges -- apps/web/src/features/career/hooks.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: apps/web/src/libs/orpc/client.ts apps/web/src/libs/orpc/client.ts:31 — apps/web/src/libs/orpc/client.ts changed 9 times in last 90 days and 7 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 5 (its worst body is client.headers at line 31), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix: recover expired sessions and sign-in flows”; “fix: add approved provider-native search fallback”; “fix: prepare Career deletions before acknowledging Undo”; “fix: improve senior professional tailoring and tracking”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 07:52:29 +01:00' --until='2026-11-14 07:52:29 +01:00' --full-history --no-merges -- apps/web/src/libs/orpc/client.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: packages/api/src/features/resume/imports.ts packages/api/src/features/resume/imports.ts:65 — packages/api/src/features/resume/imports.ts changed 8 times in last 90 days and 7 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 10 (its worst body is imports.importResumeFile at line 65), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix: address review findings for RX-234”; “fix: preserve import language and recover pending attachments”; “fix: complete document language and assistant polish”; “fix: report incomplete PDF annotation coverage”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 07:52:29 +01:00' --until='2026-11-14 07:52:29 +01:00' --full-history --no-merges -- packages/api/src/features/resume/imports.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: apps/web/src/features/auth/pages/reset-password.tsx apps/web/src/features/auth/pages/reset-password.tsx:30 — apps/web/src/features/auth/pages/reset-password.tsx changed 11 times in last 90 days and 6 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 8 (its worst body is reset-password.ResetPasswordPage at line 30), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix: recover expired sessions and sign-in flows”; “fix(ui): design system, copy and parity polish (RX-142) (#3845)”; “fix(public): homepage, public pages and sign-in polish (RX-135) (#3833)”; “fix(auth): make password reset, email change and recovery honest (RX-105) (#3792)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 07:52:29 +01:00' --until='2026-11-14 07:52:29 +01:00' --full-history --no-merges -- apps/web/src/features/auth/pages/reset-password.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: apps/web/src/features/homepage/design.tsx apps/web/src/features/homepage/design.tsx:48 — apps/web/src/features/homepage/design.tsx changed 11 times in last 90 days and 6 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 11 (its worst body is design.Design at line 48), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(homepage): default design exit progress before measurement (RX-198)”; “fix(homepage): release design link focus during scene exit (RX-198)”; “fix(homepage): tune the design-to-check scroll hand-off (RX-198)”; “fix(a11y): devices, accessibility and localization polish (RX-141) (#3844)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 07:52:29 +01:00' --until='2026-11-14 07:52:29 +01:00' --full-history --no-merges -- apps/web/src/features/homepage/design.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: packages/api/src/features/storage/service.ts packages/api/src/features/storage/service.ts:165 — packages/api/src/features/storage/service.ts changed 10 times in last 90 days and 6 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 11 (its worst body is LocalStorageService.list at line 165), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix: security hardening across auth, API, AI, imports and deployment (#3662)”; “fix(auth): migrate guest uploads and rewrite asset URLs on account linking (#3653)”; “fix(auth): preserve uploads across account link failures”; “fix(storage): prevent prefix deletion when source files cannot be read”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 07:52:29 +01:00' --until='2026-11-14 07:52:29 +01:00' --full-history --no-merges -- packages/api/src/features/storage/service.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: packages/api/src/context.ts packages/api/src/context.ts:81 — packages/api/src/context.ts changed 10 times in last 90 days and 6 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 11 (its worst body is context.resolveAuthenticationFromRequestHeaders at line 81), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “Fix AI provider setup, consent and workflow recovery (RX-98) (#3774)”; “fix: bind each batch item and recover recorded reminder watermarks”; “fix: keep delivered reminders and fence cross-account autosave”; “fix: restore alias startup and mobile usability”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 07:52:29 +01:00' --until='2026-11-14 07:52:29 +01:00' --full-history --no-merges -- packages/api/src/context.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: apps/web/src/features/homepage/header.tsx apps/web/src/features/homepage/header.tsx:27 — apps/web/src/features/homepage/header.tsx changed 9 times in last 90 days and 6 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 13 (its worst body is header.LandingHeader at line 27), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix: share homepage chrome across public marketing pages”; “fix: expose direct homepage sign-in and dashboard paths (#3888)”; “fix: hide cached homepage stars after failed refetch”; “fix(homepage): marketing page design polish (RX-124) (#3823)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 07:52:29 +01:00' --until='2026-11-14 07:52:29 +01:00' --full-history --no-merges -- apps/web/src/features/homepage/header.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: apps/web/src/features/resume/editor/write/basics-card.tsx apps/web/src/features/resume/editor/write/basics-card.tsx:109 — apps/web/src/features/resume/editor/write/basics-card.tsx changed 9 times in last 90 days and 6 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 11 (its worst body is basics-card.CustomFields at line 109), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix: complete builder photo entry and section defaults”; “fix: localize interface numerals and finish deferred layouts”; “fix(builder): resume builder editing polish (RX-137) (#3837)”; “fix(builder): honest toast undo, visible undo/redo, save failures, paste, page fit and RTL (RX-115) (#3794)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 07:52:29 +01:00' --until='2026-11-14 07:52:29 +01:00' --full-history --no-merges -- apps/web/src/features/resume/editor/write/basics-card.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: REDACTED REDACTED:287 — REDACTED changed 9 times in last 90 days and 6 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 15 (its worst body is rich-text-html.projectNormalizedRichTextHtml at line 287), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(builder): honest toast undo, visible undo/redo, save failures, paste, page fit and RTL (RX-115) (#3794)”; “fix(security): resolve reported application vulnerabilities (#3687)”; “fix: security hardening across auth, API, AI, imports and deployment (#3662)”; “fix(editor): avoid unsafe clipboard parsing pattern (#3474)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 07:52:29 +01:00' --until='2026-11-14 07:52:29 +01:00' --full-history --no-merges -- REDACTED`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: apps/web/src/libs/locale.ts apps/web/src/libs/locale.ts:122 — apps/web/src/libs/locale.ts changed 8 times in last 90 days and 6 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 5 (its worst body is locale.getLocale at line 122), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix: restore account language on unconfigured devices”; “fix: dashboard, document library and settings polish (RX-136) (#3835)”; “fix: detect first-visit language without varying shared HTML”; “fix: improve accessibility and locale preferences (RX-118)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 07:52:29 +01:00' --until='2026-11-14 07:52:29 +01:00' --full-history --no-merges -- apps/web/src/libs/locale.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: apps/server/src/rpc/handler.ts apps/server/src/rpc/handler.ts:11 — apps/server/src/rpc/handler.ts changed 8 times in last 90 days and 6 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 4 (its worst body is handler.rpcProcedure at line 11), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix: correctness, performance and docs fixes from a codebase review (#3968)”; “fix: improve Arabic phone language and account emails (#3793)”; “fix: read batch account bindings case-insensitively”; “fix: bind each batch item and recover recorded reminder watermarks”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 07:52:29 +01:00' --until='2026-11-14 07:52:29 +01:00' --full-history --no-merges -- apps/server/src/rpc/handler.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: apps/web/src/libs/orpc/fetch.ts apps/web/src/libs/orpc/fetch.ts:8 — apps/web/src/libs/orpc/fetch.ts changed 8 times in last 90 days and 6 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 14 (its worst body is fetch.rpcFetch at line 8), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix: cancel AI imports and explain missing conversations”; “fix: localize staged upload failures”; “fix: prepare Career deletions before acknowledging Undo”; “fix: dashboard, document library and settings polish (RX-136) (#3835)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 07:52:29 +01:00' --until='2026-11-14 07:52:29 +01:00' --full-history --no-merges -- apps/web/src/libs/orpc/fetch.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: apps/web/src/features/resume/import/pdf-text.ts apps/web/src/features/resume/import/pdf-text.ts:20 — apps/web/src/features/resume/import/pdf-text.ts changed 7 times in last 90 days and 6 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 5 (its worst body is pdf-text.readPdfResume at line 20), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix: report incomplete PDF annotation coverage”; “fix: give readable-text recovery for incomplete PDF imports”; “fix: report incomplete PDF source comparisons accurately”; “fix: close 11 assistant and AI import gaps from the October audit (RX-99) (#3790)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 07:52:29 +01:00' --until='2026-11-14 07:52:29 +01:00' --full-history --no-merges -- apps/web/src/features/resume/import/pdf-text.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • + 50 more in this group — see findings.md.
D3 · God Classes · FileTooLong · ×65
  • FileTooLong: agent/service.ts packages/api/src/features/agent/service.ts — FileTooLong — 1738 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 1238 over it, 3.48× 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: src/pdf-lines.ts packages/import/src/pdf-lines.ts — FileTooLong — 1695 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 1195 over it, 3.39× 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: career/service.ts packages/api/src/features/career/service.ts — FileTooLong — 1588 significant lines (blank, comment-only and punctuation-only lines excluded), about 73% of them inside a single declaration: careerService (570-1979). The bar is 500 significant lines; this is 1088 over it, 3.18× 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: shared/sections.tsx packages/pdf/src/templates/shared/sections.tsx — FileTooLong — 1407 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 907 over it, 2.81× 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: applications/service.ts packages/api/src/features/applications/service.ts — FileTooLong — 1246 significant lines (blank, comment-only and punctuation-only lines excluded), about 60% of them inside a single declaration: applicationService (685-1657). The bar is 500 significant lines; this is 746 over it, 2.49× 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: workspace/practise.tsx apps/web/src/features/career/workspace/practise.tsx — FileTooLong — 1155 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 655 over it, 2.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: career/today.tsx apps/web/src/features/career/today.tsx — FileTooLong — 1096 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 596 over it, 2.19× 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: builder/kit.tsx apps/web/src/routes/builder/kit.tsx — FileTooLong — 1083 significant lines (blank, comment-only and punctuation-only lines excluded), about 81% of them inside a single declaration: KitPage (221-1169). The bar is 500 significant lines; this is 583 over it, 2.17× 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/write-panel.tsx apps/web/src/routes/builder/letter/-components/write-panel.tsx — FileTooLong — 1064 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 564 over it, 2.13× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: career/offers.tsx apps/web/src/features/career/offers.tsx — FileTooLong — 1058 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 558 over it, 2.12× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: assistant/conversation.tsx apps/web/src/features/assistant/conversation.tsx — FileTooLong — 1047 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 547 over it, 2.09× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: components/add-application-dialog.tsx apps/web/src/features/applications/components/add-application-dialog.tsx — FileTooLong — 993 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 493 over it, 1.99× 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: src/config.ts packages/auth/src/config.ts — FileTooLong — 982 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 482 over it, 1.96× 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: builder/draft.ts apps/web/src/features/resume/builder/draft.ts — FileTooLong — 968 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 468 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: workspace/apply.tsx apps/web/src/features/career/workspace/apply.tsx — FileTooLong — 954 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 454 over it, 1.91× 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: documents/documents-page.tsx apps/web/src/features/documents/documents-page.tsx — FileTooLong — 922 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 422 over it, 1.84× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: workspace/prepare.tsx apps/web/src/features/career/workspace/prepare.tsx — FileTooLong — 884 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 384 over it, 1.77× 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: career/coach-chat.tsx apps/web/src/features/career/coach-chat.tsx — FileTooLong — 874 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 374 over it, 1.75× 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: workspace/messages.tsx apps/web/src/features/career/workspace/messages.tsx — FileTooLong — 871 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 371 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: resume/service.ts packages/api/src/features/resume/service.ts — FileTooLong — 854 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 354 over it, 1.71× 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: applications/ApplicationsScreen.tsx apps/mobile/src/features/applications/ApplicationsScreen.tsx — FileTooLong — 841 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 341 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: semantic/tree.ts packages/pdf/src/semantic/tree.ts — FileTooLong — 806 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 306 over it, 1.61× 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: documents/new-document-dialog.tsx apps/web/src/features/documents/new-document-dialog.tsx — FileTooLong — 801 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 301 over it, 1.60× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: components/application-detail-sheet.tsx apps/web/src/features/applications/components/application-detail-sheet.tsx — FileTooLong — 791 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 291 over it, 1.58× 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: forme/to-forme.tsx packages/pdf/src/forme/to-forme.tsx — FileTooLong — 781 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 281 over it, 1.56× 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.
  • + 40 more in this group — see findings.md.
AX7 · Slice cohesion · Cross-slice coupling · ×40
  • Cross-slice coupling: applications → workspace apps/mobile/src/features/applications/DetailScreen.tsx:106 — `DetailScreen` (slice 'applications') depends on `useSavedItems` from slice 'workspace'.
  • Cross-slice coupling: auth → settings apps/mobile/src/features/auth/ConsentScreen.tsx:37 — `ConsentScreen` (slice 'auth') depends on `useStoryboardView` from slice 'settings'.
  • Cross-slice coupling: letters → builder apps/mobile/src/features/letters/design-screen.tsx:29 — `LetterDesignScreen` (slice 'letters') depends on `useDocumentId` from slice 'builder'.
  • Cross-slice coupling: letters → builder apps/mobile/src/features/letters/design-screen.tsx:31 — `LetterDesignScreen` (slice 'letters') depends on `useLetterDocument` from slice 'builder'.
  • Cross-slice coupling: letters → builder apps/mobile/src/features/letters/design-screen.tsx:40 — `LetterDesignScreen` (slice 'letters') depends on `useRenderedPage` from slice 'builder'.
  • Cross-slice coupling: letters → builder apps/mobile/src/features/letters/design-screen.tsx:81 — `LetterDesignScreen` (slice 'letters') depends on `LetterDocument` from slice 'builder'.
  • Cross-slice coupling: letters → builder apps/mobile/src/features/letters/design-screen.tsx:115 — `LetterDesignScreen` (slice 'letters') depends on `DocumentState` from slice 'builder'.
  • Cross-slice coupling: letters → builder apps/mobile/src/features/letters/letter-screen.tsx:31 — `LetterScreen` (slice 'letters') depends on `useDocumentId` from slice 'builder'.
  • Cross-slice coupling: letters → builder apps/mobile/src/features/letters/letter-screen.tsx:33 — `LetterScreen` (slice 'letters') depends on `useLetterDocument` from slice 'builder'.
  • Cross-slice coupling: letters → builder apps/mobile/src/features/letters/letter-screen.tsx:97 — `LetterScreen` (slice 'letters') depends on `LetterDocument` from slice 'builder'.
  • Cross-slice coupling: letters → builder apps/mobile/src/features/letters/letter-screen.tsx:164 — `LetterScreen` (slice 'letters') depends on `DocumentState` from slice 'builder'.
  • Cross-slice coupling: settings → auth apps/mobile/src/features/settings/AccountScreen.tsx:27 — `AccountScreen` (slice 'settings') depends on `useAuthOptions` from slice 'auth'.
  • Cross-slice coupling: settings → auth apps/mobile/src/features/settings/SettingsScreen.tsx:145 — `SettingsScreen` (slice 'settings') depends on `hostOf` from slice 'auth'.
  • Cross-slice coupling: settings → auth apps/mobile/src/features/settings/SignOutDialog.tsx:124 — `SignOutDialog` (slice 'settings') depends on `hostOf` from slice 'auth'.
  • Cross-slice coupling: today → documents apps/mobile/src/features/today/screen.tsx:77 — `TodayScreen` (slice 'today') depends on `useOpenDocument` from slice 'documents'.
  • Cross-slice coupling: today → documents apps/mobile/src/features/today/screen.tsx:188 — `TodayScreen` (slice 'today') depends on `AccountAvatar` from slice 'documents'.
  • Cross-slice coupling: today → settings apps/mobile/src/features/today/screen.tsx:205 — `TodayScreen` (slice 'today') depends on `zoneCity` from slice 'settings'.
  • Cross-slice coupling: today → documents apps/mobile/src/features/today/screen.tsx:214 — `TodayScreen` (slice 'today') depends on `CollectionState` from slice 'documents'.
  • Cross-slice coupling: today → documents apps/mobile/src/features/today/screen.tsx:240 — `TodayScreen` (slice 'today') depends on `DocumentPlaceholders` from slice 'documents'.
  • Cross-slice coupling: workspace → applications apps/mobile/src/features/workspace/ApplyScreen.tsx:46 — `ApplyScreen` (slice 'workspace') depends on `stageDate` from slice 'applications'.
  • Cross-slice coupling: workspace → applications apps/mobile/src/features/workspace/ApplyScreen.tsx:49 — `ApplyScreen` (slice 'workspace') depends on `storyboard` from slice 'applications'.
  • Cross-slice coupling: workspace → applications apps/mobile/src/features/workspace/ApplyScreen.tsx:66 — `ApplyScreen` (slice 'workspace') depends on `longDay` from slice 'applications'.
  • Cross-slice coupling: workspace → applications apps/mobile/src/features/workspace/ApplyScreen.tsx:85 — `ApplyScreen` (slice 'workspace') depends on `sentStepHref` from slice 'applications'.
  • Cross-slice coupling: workspace → applications apps/mobile/src/features/workspace/ApplyScreen.tsx:97 — `ApplyScreen` (slice 'workspace') depends on `dayMonth` from slice 'applications'.
  • Cross-slice coupling: workspace → applications apps/mobile/src/features/workspace/ApplyScreen.tsx:97 — `ApplyScreen` (slice 'workspace') depends on `clockTime` from slice 'applications'.
  • + 15 more in this group — see findings.md.
X3 · Exception handling · Swallowed exception (empty catch) · ×37
  • Swallowed exception (empty catch) tooling/calm/dev.mjs:27 — 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) tooling/autofill/lab.ts:52 — 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/utils/src/deferred-request.ts:58 — `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
  • Swallowed exception (empty catch) packages/utils/src/http.ts:108 — `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
  • Swallowed exception (empty catch) packages/utils/src/http.ts:124 — `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
  • Swallowed exception (empty catch) packages/schema/src/resume/dates.ts:274 — 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/schema/src/applications/csv.ts:264 — 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/schema/src/applications/posting-source.ts:14 — 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/pdf/src/forme/font-subset.ts:93 — 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/auth/src/config.ts:696 — `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
  • Swallowed exception (empty catch) packages/api/src/features/web-access/builtin.ts:121 — `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
  • Swallowed exception (empty catch) packages/api/src/features/storage/read.ts:16 — `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
  • Swallowed exception (empty catch) packages/api/src/features/storage/read.ts:41 — `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
  • Swallowed exception (empty catch) packages/api/src/features/statistics/service.ts:40 — 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/api/src/features/statistics/service.ts:65 — 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/api/src/features/resume/events.ts:59 — 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/api/src/features/resume/events.ts:74 — `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
  • Swallowed exception (empty catch) packages/api/src/features/resume/events.ts:144 — `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
  • Swallowed exception (empty catch) packages/api/src/features/resume/events.ts:180 — `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
  • Swallowed exception (empty catch) packages/api/src/features/resume/pdf-analysis.ts:15 — `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
  • Swallowed exception (empty catch) packages/api/src/features/resume/pdf-analysis.ts:33 — `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
  • Swallowed exception (empty catch) packages/api/src/features/applications/service.ts:632 — `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
  • Swallowed exception (empty catch) packages/api/src/features/applications/service.ts:1157 — `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
  • Swallowed exception (empty catch) packages/api/src/features/ai/destination.ts:27 — 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/src/routes/dashboard/applications/index.tsx:175 — `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
  • + 12 more in this group — see findings.md.
R4 · Test Coverage · This test file cannot be loaded · ×20
  • This test file cannot be loaded apps/server/src/static/agent-skills.test.ts:9 — apps/server/src/static/agent-skills.test.ts:9 imports '../../../../plugins/reactive-resume/skills', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
  • This test file cannot be loaded packages/api/src/features/agent/review.integration.test.ts:100 — packages/api/src/features/agent/review.integration.test.ts:100 imports '../../../../../migrations/', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
  • This test file cannot be loaded packages/api/src/features/ai-providers/approval.integration.test.ts:148 — packages/api/src/features/ai-providers/approval.integration.test.ts:148 imports '../../../../../migrations/', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
  • This test file cannot be loaded packages/api/src/features/ai/usage.integration.test.ts:798 — packages/api/src/features/ai/usage.integration.test.ts:798 imports '../../../../../migrations/', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
  • This test file cannot be loaded packages/api/src/features/applications/lanes.integration.test.ts:59 — packages/api/src/features/applications/lanes.integration.test.ts:59 imports '../../../../../migrations/', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
  • This test file cannot be loaded packages/api/src/features/applications/trash.integration.test.ts:67 — packages/api/src/features/applications/trash.integration.test.ts:67 imports '../../../../../migrations/', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
  • This test file cannot be loaded packages/api/src/features/career/jobs.integration.test.ts:113 — packages/api/src/features/career/jobs.integration.test.ts:113 imports '../../../../../migrations/', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either (2 further unresolvable import(s) in the same file). The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
  • This test file cannot be loaded packages/api/src/features/career/role-recipient.integration.test.ts:143 — packages/api/src/features/career/role-recipient.integration.test.ts:143 imports '../../../../../migrations/', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
  • This test file cannot be loaded packages/api/src/features/career/role-suggestions.integration.test.ts:47 — packages/api/src/features/career/role-suggestions.integration.test.ts:47 imports '../../../../../migrations/', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
  • This test file cannot be loaded packages/api/src/features/career/service.integration.test.ts:126 — packages/api/src/features/career/service.integration.test.ts:126 imports '../../../../../migrations/', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
  • This test file cannot be loaded packages/api/src/features/cover-letters/service.integration.test.ts:46 — packages/api/src/features/cover-letters/service.integration.test.ts:46 imports '../../../../../migrations/', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
  • This test file cannot be loaded packages/api/src/features/documents/link-reconciliation.integration.test.ts:68 — packages/api/src/features/documents/link-reconciliation.integration.test.ts:68 imports '../../../../../migrations/', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
  • This test file cannot be loaded packages/api/src/features/documents/listing.integration.test.ts:39 — packages/api/src/features/documents/listing.integration.test.ts:39 imports '../../../../../migrations/', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
  • This test file cannot be loaded packages/api/src/features/documents/service.integration.test.ts:105 — packages/api/src/features/documents/service.integration.test.ts:105 imports '../../../../../migrations/', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
  • This test file cannot be loaded packages/api/src/features/feedback/service.integration.test.ts:38 — packages/api/src/features/feedback/service.integration.test.ts:38 imports '../../../../../migrations/', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
  • This test file cannot be loaded packages/api/src/features/resume/account-link.integration.test.ts:53 — packages/api/src/features/resume/account-link.integration.test.ts:53 imports '../../../../../migrations/', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
  • This test file cannot be loaded packages/api/src/features/resume/address.integration.test.ts:53 — packages/api/src/features/resume/address.integration.test.ts:53 imports '../../../../../migrations/', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
  • This test file cannot be loaded packages/api/src/features/web-access/credentials.integration.test.ts:45 — packages/api/src/features/web-access/credentials.integration.test.ts:45 imports '../../../../../migrations/', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
  • This test file cannot be loaded packages/db/src/migrations.integration.test.ts:14 — packages/db/src/migrations.integration.test.ts:14 imports '../../../migrations', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
  • This test file cannot be loaded packages/db/src/username-reservation.integration.test.ts:18 — packages/db/src/username-reservation.integration.test.ts:18 imports '../../../migrations/', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
R4 · Test Coverage · No test reaches this file · ×20
  • No test reaches this file apps/mobile/src/features/applications/ApplicationsScreen.tsx:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file apps/mobile/src/features/today/screen.tsx:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file apps/mobile/app/(dev)/motion-lab/[lab].tsx:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file apps/mobile/src/features/builder/check/CheckScreen.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 tooling/calm/seed.mjs:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file apps/mobile/src/features/career/coach.tsx:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file apps/mobile/src/features/builder/entry/EntryScreen.tsx:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file apps/mobile/src/features/applications/DetailScreen.tsx:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file apps/mobile/src/features/public/ats-messages.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/mobile/src/features/builder/menu/menu-screen.tsx:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file apps/mobile/src/features/applications/InterviewSheet.tsx:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file apps/mobile/src/features/builder/description/DescriptionScreen.tsx:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file apps/mobile/app/(dev)/kit.tsx:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file apps/mobile/src/features/career/offers.tsx:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file apps/mobile/src/features/career/preferences.tsx:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file apps/mobile/src/features/documents/search.tsx:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file apps/mobile/src/features/documents/actions.tsx:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file apps/mobile/src/features/documents/import.tsx:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file apps/mobile/src/features/builder/design/LayoutScreen.tsx:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file apps/mobile/src/features/builder/check/issues.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.
IC1 · Incompleteness & stubs · Markup wires an event to an empty handler · ×19
  • Markup wires an event to an empty handler apps/mobile/app/(dev)/kit.tsx:224 — `onValueChange` is wired to an arrow whose body is empty — the markup attaches a listener that does nothing. Implement the handler, or remove the attribute that wires it.
  • Markup wires an event to an empty handler apps/mobile/app/(dev)/kit.tsx:254 — `onValueChange` is wired to an arrow whose body is empty — the markup attaches a listener that does nothing. Implement the handler, or remove the attribute that wires it.
  • Markup wires an event to an empty handler apps/mobile/app/(dev)/kit.tsx:255 — `onValueChange` is wired to an arrow whose body is empty — the markup attaches a listener that does nothing. Implement the handler, or remove the attribute that wires it.
  • Markup wires an event to an empty handler apps/mobile/app/(dev)/kit.tsx:256 — `onValueChange` is wired to an arrow whose body is empty — the markup attaches a listener that does nothing. Implement the handler, or remove the attribute that wires it.
  • Markup wires an event to an empty handler apps/mobile/app/(dev)/kit.tsx:257 — `onSelect` is wired to an arrow whose body is empty — the markup attaches a listener that does nothing. Implement the handler, or remove the attribute that wires it.
  • Markup wires an event to an empty handler apps/mobile/app/(dev)/kit.tsx:258 — `onSelect` is wired to an arrow whose body is empty — the markup attaches a listener that does nothing. Implement the handler, or remove the attribute that wires it.
  • Markup wires an event to an empty handler apps/mobile/app/(dev)/kit.tsx:312 — `onPress` is wired to an arrow whose body is empty — the markup attaches a listener that does nothing. Implement the handler, or remove the attribute that wires it.
  • Markup wires an event to an empty handler apps/mobile/app/(dev)/kit.tsx:314 — `onPress` is wired to an arrow whose body is empty — the markup attaches a listener that does nothing. Implement the handler, or remove the attribute that wires it.
  • Markup wires an event to an empty handler apps/mobile/app/(dev)/kit.tsx:348 — `onNavigate` is wired to an arrow whose body is empty — the markup attaches a listener that does nothing. Implement the handler, or remove the attribute that wires it.
  • Markup wires an event to an empty handler apps/mobile/app/(dev)/kit.tsx:361 — `onNavigate` is wired to an arrow whose body is empty — the markup attaches a listener that does nothing. Implement the handler, or remove the attribute that wires it.
  • Markup wires an event to an empty handler apps/mobile/app/(dev)/motion-lab/[lab].tsx:189 — `onPress` is wired to an arrow whose body is empty — the markup attaches a listener that does nothing. Implement the handler, or remove the attribute that wires it.
  • Markup wires an event to an empty handler apps/mobile/app/(dev)/motion-lab/[lab].tsx:394 — `onPress` is wired to an arrow whose body is empty — the markup attaches a listener that does nothing. Implement the handler, or remove the attribute that wires it.
  • Markup wires an event to an empty handler apps/mobile/app/(dev)/motion-lab/[lab].tsx:395 — `onPress` is wired to an arrow whose body is empty — the markup attaches a listener that does nothing. Implement the handler, or remove the attribute that wires it.
  • Markup wires an event to an empty handler apps/mobile/app/(dev)/motion-lab/[lab].tsx:396 — `onPress` is wired to an arrow whose body is empty — the markup attaches a listener that does nothing. Implement the handler, or remove the attribute that wires it.
  • Markup wires an event to an empty handler apps/mobile/src/dev/storyboard/backdrop.tsx:119 — `onClose` is wired to an arrow whose body is empty — the markup attaches a listener that does nothing. Implement the handler, or remove the attribute that wires it.
  • Markup wires an event to an empty handler apps/mobile/src/dev/storyboard/backdrop.tsx:120 — `onSignedOut` is wired to an arrow whose body is empty — the markup attaches a listener that does nothing. Implement the handler, or remove the attribute that wires it.
  • Markup wires an event to an empty handler apps/web/src/features/resume/editor/write/section-view.tsx:128 — `onChange` is wired to an arrow whose body is empty — the markup attaches a listener that does nothing. Implement the handler, or remove the attribute that wires it.
  • Markup wires an event to an empty handler apps/web/src/routes/builder/kit.tsx:310 — `onRemove` is wired to an arrow whose body is empty — the markup attaches a listener that does nothing. Implement the handler, or remove the attribute that wires it.
  • Markup wires an event to an empty handler apps/web/src/routes/builder/kit.tsx:348 — `onValueChange` 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.
P12 · CI test-gate honesty · Workspace package's tests never run by CI · ×19
  • Workspace package's tests never run by CI apps/server/package.json:12 — `apps/server` is a workspace package with 156 test(s) in 31 file(s) (e.g. `apps/server/src/index.test.ts`, `apps/server/src/vercel.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 apps/web/package.json:12 — `apps/web` is a workspace package with 912 test(s) in 174 file(s) (e.g. `apps/web/src/react-compiler.test.ts`, `apps/web/src/router.test.tsx`), 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/ai/package.json:21 — `packages/ai` is a workspace package with 28 test(s) in 7 file(s) (e.g. `packages/ai/src/defaults.test.ts`, `packages/ai/src/native-search-capabilities.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/api/package.json:32 — `packages/api` is a workspace package with 992 test(s) in 116 file(s) (e.g. `packages/api/src/context.test.ts`, `packages/api/src/redis.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/auth/package.json:13 — `packages/auth` is a workspace package with 41 test(s) in 10 file(s) (e.g. `packages/auth/src/account-link.test.ts`, `packages/auth/src/backup-codes.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/db/package.json:24 — `packages/db` is a workspace package with 5 test(s) in 4 file(s) (e.g. `packages/db/src/foreign-key-indexes.test.ts`, `packages/db/src/migrations.integration.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/docx/package.json:11 — `packages/docx` is a workspace package with 26 test(s) in 8 file(s) (e.g. `packages/docx/src/header-placement.test.ts`, `packages/docx/src/html-to-docx.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/dsh-plugin/package.json:46 — `packages/dsh-plugin` is a workspace package with 6 test(s) in 3 file(s) (e.g. `packages/dsh-plugin/src/index.test.ts`, `packages/dsh-plugin/src/prompt.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/email/package.json:14 — `packages/email` is a workspace package with 7 test(s) in 2 file(s) (e.g. `packages/email/src/transport.test.ts`, `packages/email/src/templates/auth.test.tsx`), 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/env/package.json:11 — `packages/env` is a workspace package with 26 test(s) in 2 file(s) (e.g. `packages/env/src/deployment.test.ts`, `packages/env/src/server.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/fonts/package.json:13 — `packages/fonts` is a workspace package with 20 test(s) in 4 file(s) (e.g. `packages/fonts/src/files.test.ts`, `packages/fonts/src/font-bytes.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/import/package.json:20 — `packages/import` is a workspace package with 128 test(s) in 12 file(s) (e.g. `packages/import/src/html.test.ts`, `packages/import/src/job-posting-header.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/mcp/package.json:13 — `packages/mcp` is a workspace package with 20 test(s) in 5 file(s) (e.g. `packages/mcp/src/discovery.test.ts`, `packages/mcp/src/mcp-server-card.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/odt/package.json:11 — `packages/odt` is a workspace package with 5 test(s) in 1 file(s) (e.g. `packages/odt/src/odt.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/pdf/package.json:25 — `packages/pdf` is a workspace package with 243 test(s) in 75 file(s) (e.g. `packages/pdf/src/ats-extraction.integration.test.tsx`, `packages/pdf/src/browser.test.tsx`), 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/resume/package.json:32 — `packages/resume` is a workspace package with 253 test(s) in 29 file(s) (e.g. `packages/resume/src/contact-details.test.ts`, `packages/resume/src/cover-letter.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/schema/package.json:25 — `packages/schema` is a workspace package with 152 test(s) in 30 file(s) (e.g. `packages/schema/src/ai-usage.test.ts`, `packages/schema/src/application-answers.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/ui/package.json:15 — `packages/ui` is a workspace package with 18 test(s) in 10 file(s) (e.g. `packages/ui/src/components/button.test.tsx`, `packages/ui/src/components/form.test.tsx`), 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/utils/package.json:31 — `packages/utils` is a workspace package with 112 test(s) in 15 file(s) (e.g. `packages/utils/src/account-zip.test.ts`, `packages/utils/src/amount.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.
X24 · Document value interpolated into markup unescaped · Untrusted text written into markup unescaped · ×19
  • Untrusted text written into markup unescaped apps/server/src/static/seo.ts:82 — `escapeXml(href)` is text this program did not author, and it is written into the start of a URL attribute, where it chooses the scheme 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. HTML encoding does not help here — a `javascript:` URL contains nothing it changes; allow only http(s) or a relative path.
  • Untrusted text written into markup unescaped apps/server/src/static/web.ts:286 — `escapeHtml(href)` is text this program did not author, and it is written into the start of a URL attribute, where it chooses the scheme 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. HTML encoding does not help here — a `javascript:` URL contains nothing it changes; allow only http(s) or a relative path.
  • Untrusted text written into markup unescaped apps/server/src/static/web.ts:292 — `url` is text this program did not author, and it is written into the start of a URL attribute, where it chooses the scheme 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. HTML encoding does not help here — a `javascript:` URL contains nothing it changes; allow only http(s) or a relative path.
  • Untrusted text written into markup unescaped apps/server/src/static/web.ts:360 — `meta.title` 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 apps/server/src/static/web.ts:361 — `meta.description` is text this program did not author, and it is written into a quoted attribute value 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 apps/web/src/features/homepage/faq.tsx:210 — `serializeJsonLd(structuredData)` 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:68 — `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 REDACTED:83 — `escapeXml(node.href)` is text this program did not author, and it is written into the start of a URL attribute, where it chooses the scheme 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. HTML encoding does not help here — a `javascript:` URL contains nothing it changes; allow only http(s) or a relative path.
  • Untrusted text written into markup unescaped packages/pdf/src/html/document.ts:275 — `escapeHtml(downloadUrl)` is text this program did not author, and it is written into the start of a URL attribute, where it chooses the scheme 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. HTML encoding does not help here — a `javascript:` URL contains nothing it changes; allow only http(s) or a relative path.
  • Untrusted text written into markup unescaped packages/pdf/src/html/document.ts:278 — `escapeHtml(wordDownloadUrl)` is text this program did not author, and it is written into the start of a URL attribute, where it chooses the scheme 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. HTML encoding does not help here — a `javascript:` URL contains nothing it changes; allow only http(s) or a relative path.
  • Untrusted text written into markup unescaped packages/pdf/src/html/document.ts:280 — `escapeHtml(downloadUrl)` is text this program did not author, and it is written into the start of a URL attribute, where it chooses the scheme 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. HTML encoding does not help here — a `javascript:` URL contains nothing it changes; allow only http(s) or a relative path.
  • Untrusted text written into markup unescaped packages/pdf/src/html/document.ts:291 — `escapeHtml(creditUrl)` is text this program did not author, and it is written into the start of a URL attribute, where it chooses the scheme 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. HTML encoding does not help here — a `javascript:` URL contains nothing it changes; allow only http(s) or a relative path.
  • Untrusted text written into markup unescaped REDACTED:90 — `whitespace` is text this program did not author, and it is written into the text of an element through `insertAdjacentHTML` 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:99 — `whitespace` is text this program did not author, and it is written into the text of an element through `insertAdjacentHTML` 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:114 — `child.innerHTML` 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 tooling/autofill/lab.ts:17 — `kind` 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 tooling/autofill/lab.ts:27 — `fixtureForm(kind)` 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 tooling/autofill/lab.ts:30 — `OTHER_ORIGIN` is text this program did not author, and it is written into the start of a URL attribute, where it chooses the scheme 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 encoding does not help here — a `javascript:` URL contains nothing it changes; allow only http(s) or a relative path.
  • Untrusted text written into markup unescaped tooling/capture/content.ts:8 — `html.replace(/<\/(?:p|div|li|h[1-6]|section)>|<br\s*\/?>/gi,"\n")` 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.
AC2 · Forms & labels · <fieldset> without a <legend> · ×15
  • <fieldset> without a <legend> apps/web/src/features/assistant/conversation.tsx:1177 — 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/src/features/career/knowledge/resume-facts.tsx:210 — 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/src/features/career/offer-entry.tsx:491 — 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/src/features/career/workspace/answer-library.tsx:361 — 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/src/features/career/workspace/application-packet.tsx:137 — 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/src/features/documents/new-document-dialog.tsx:805 — 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/src/features/resume/editor/write/basics-card.tsx:46 — 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/src/features/resume/editor/write/entry-view.tsx:146 — 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/src/features/resume/editor/write/section-view.tsx:110 — 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/src/features/resume/editor/write/section-view.tsx:141 — 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/src/features/resume/editor/write/section-view.tsx:368 — 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/src/features/settings/profile.tsx:668 — 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/src/routes/builder/$resumeId/-components/design-panel.tsx:147 — 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/src/routes/builder/$resumeId/-components/document-menu.tsx:198 — 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/src/routes/builder/letter/-components/write-panel.tsx:649 — 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.
AC6 · Visual & motion safety · Focus outline removed inline · ×13
  • Focus outline removed inline apps/web/src/components/calm/filter-bar.tsx:54 — <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 apps/web/src/features/applications/components/add-application-dialog.tsx:518 — <textarea> 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/src/features/career/coach.tsx:781 — <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 apps/web/src/features/career/knowledge/preferences.tsx:315 — <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 apps/web/src/features/career/knowledge/preferences.tsx:426 — <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 apps/web/src/features/career/knowledge/preferences.tsx:469 — <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 apps/web/src/features/career/knowledge/preferences.tsx:490 — <select> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
  • Focus outline removed inline apps/web/src/features/career/knowledge/resume-facts.tsx:222 — <textarea> 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/src/features/career/knowledge/resume-facts.tsx:235 — <select> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
  • Focus outline removed inline apps/web/src/features/resume/editor/design/fields.tsx:40 — <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 apps/web/src/features/resume/editor/proposals/proposal-list.tsx:468 — <textarea> 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/src/features/resume/share/download-menu.tsx:110 — <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 apps/web/src/features/resume/share/download-tab.tsx:143 — <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).
R11 · Import Boundaries · Boundary violation [package · ×9
  • Boundary violation [package:relative-cross-package] apps/mobile/src/render/page-renderer.ts:1 — apps/mobile/src/render/page-renderer.ts:1 reaches into another package with a relative path (../../modules/pdf-pages) — import the package by name instead.
  • Boundary violation [package:relative-cross-package] apps/mobile/src/render/page-renderer.ts:8 — apps/mobile/src/render/page-renderer.ts:8 reaches into another package with a relative path (../../modules/pdf-pages) — import the package by name instead.
  • Boundary violation [package:third-party-deep-import] packages/pdf/src/browser.tsx:7 — packages/pdf/src/browser.tsx:7 imports harfbuzzjs/dist/harfbuzz-subset.wasm?url, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
  • Boundary violation [package:relative-cross-package] tooling/locales/generate.ts:15 — tooling/locales/generate.ts:15 reaches into another package with a relative path (../../packages/pdf/src/section-title-catalog.json) — import the package by name instead.
  • Boundary violation [package:relative-cross-package] tooling/locales/generate.ts:20 — tooling/locales/generate.ts:20 reaches into another package with a relative path (../../packages/schema/src/resume/present-labels.json) — import the package by name instead.
  • Boundary violation [package:relative-cross-package] tooling/locales/generate.ts:26 — tooling/locales/generate.ts:26 reaches into another package with a relative path (../../packages/utils/src/file-name-words.json) — import the package by name instead.
  • Boundary violation [package:relative-cross-package] tooling/locales/generate.ts:31 — tooling/locales/generate.ts:31 reaches into another package with a relative path (../../packages/schema/src/resume/expected-labels.json) — import the package by name instead.
  • Boundary violation [package:relative-cross-package] tooling/locales/generate.ts:38 — tooling/locales/generate.ts:38 reaches into another package with a relative path (../../packages/pdf/src/html/web-page-catalog.json) — import the package by name instead.
  • Boundary violation [package:relative-cross-package] tooling/locales/generate.ts:45 — tooling/locales/generate.ts:45 reaches into another package with a relative path (../../packages/email/src/templates/auth-catalog.json) — import the package by name instead.
X17 · Uncapped recursion over a caller-supplied document · Recursive walk over a caller-supplied document has no depth cap · ×7
  • Recursive walk over a caller-supplied document has no depth cap tooling/capture/content.ts:58 — `captureDocument` is exported, takes a document from its caller (line 5) and hands it to `visit`, which calls itself at line 58 (`visit`) with a piece of `node` — and nowhere in `visit` 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 `visit` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
  • Recursive walk over a caller-supplied document has no depth cap packages/api/src/features/agent/context.ts:39 — `estimateTokens` is exported and takes `value: unknown` from its caller, and it calls itself at line 39 (`estimateTokens`) with a piece of `value` (and at line 44) — and nowhere in `estimateTokens` 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 `estimateTokens` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
  • Recursive walk over a caller-supplied document has no depth cap packages/api/src/features/agent/review.ts:27 — `entryReview` is exported and takes `entry: Record<string, unknown>` from its caller, and it calls itself at line 27 (`entryReview`) with a piece of `entry` (and at line 35) — and nowhere in `entryReview` 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 `entryReview` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
  • Recursive walk over a caller-supplied document has no depth cap apps/web/src/features/resume/import/read-file.ts:37 — `detectJsonImportKind` is exported and takes `parsed: unknown` from its caller, and it calls itself at line 37 (`detectJsonImportKind`) with a piece of `parsed` — and nowhere in `detectJsonImportKind` 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 `detectJsonImportKind` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
  • Recursive walk over a caller-supplied document has no depth cap apps/mobile/src/data/codec.ts:4 — `encode` is exported and takes `value: unknown` from its caller, and it calls itself at line 4 (`encode`) with a piece of `value` (and at line 6) — and nowhere in `encode` 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 `encode` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
  • Recursive walk over a caller-supplied document has no depth cap apps/mobile/src/data/codec.ts:10 — `decode` is exported and takes `value: unknown` from its caller, and it calls itself at line 10 (`decode`) with a piece of `value` (and at line 14) — and nowhere in `decode` 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 `decode` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
  • Recursive walk over a caller-supplied document has no depth cap apps/mobile/src/data/import.ts:80 — `parseResumeFileJSON` is exported and takes `value: unknown` from its caller, and it calls itself at line 80 (`parseResumeFileJSON`) with a piece of `value` — and nowhere in `parseResumeFileJSON` 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 `parseResumeFileJSON` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
AC2 · Forms & labels · <TextInput> field component without a label · ×5
  • <TextInput> field component without a label apps/mobile/src/features/auth/TwoStepScreen.tsx:101 — This UI-library field component has no label / aria-label / aria-labelledby / id at this call site, and nothing written inside it here carries one either (a name prop is the form-submission key, not a label; an id, even one the component sets on what it renders, names nothing until a label points at it) — so it likely renders an unlabelled control. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
  • <TextInput> field component without a label apps/mobile/src/features/builder/description/DescriptionScreen.tsx:355 — This UI-library field component has no label / aria-label / aria-labelledby / id at this call site, and nothing written inside it here carries one either (a name prop is the form-submission key, not a label; an id, even one the component sets on what it renders, names nothing until a label points at it) — so it likely renders an unlabelled control. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
  • <TextInput> field component without a label apps/mobile/src/features/letters/letter-screen.tsx:177 — This UI-library field component has no label / aria-label / aria-labelledby / id at this call site, and nothing written inside it here carries one either (a name prop is the form-submission key, not a label; an id, even one the component sets on what it renders, names nothing until a label points at it) — so it likely renders an unlabelled control. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
  • <TextInput> field component without a label apps/mobile/src/features/workspace/MessagesScreen.tsx:168 — This UI-library field component has no label / aria-label / aria-labelledby / id at this call site, and nothing written inside it here carries one either (a name prop is the form-submission key, not a label; an id, even one the component sets on what it renders, names nothing until a label points at it) — so it likely renders an unlabelled control. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
  • <TextInput> field component without a label apps/mobile/src/ui/fields.tsx:394 — This UI-library field component has no label / aria-label / aria-labelledby / id at this call site, and nothing written inside it here carries one either (a name prop is the form-submission key, not a label; an id, even one the component sets on what it renders, names nothing until a label points at it) — so it likely renders an unlabelled control. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
AC2 · Forms & labels · <TextField> field component without a label · ×5
  • <TextField> field component without a label apps/mobile/src/features/builder/assistant/assistant-screen.tsx:238 — This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
  • <TextField> field component without a label apps/mobile/src/features/builder/share/web-page-screen.tsx:187 — This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
  • <TextField> field component without a label apps/mobile/src/features/builder/shared/section-actions.tsx:70 — This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
  • <TextField> field component without a label apps/mobile/src/features/career/facts.tsx:166 — This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
  • <TextField> field component without a label apps/mobile/src/features/career/stories.tsx:199 — This UI-library field component has no label / aria-label / aria-labelledby / id at this call site, and nothing written inside it here carries one either (a name prop is the form-submission key, not a label; an id, even one the component sets on what it renders, names nothing until a label points at it) — so it likely renders an unlabelled control. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
AC6 · Visual & motion safety · Animation without a prefers-reduced-motion guard · ×5
  • Animation without a prefers-reduced-motion guard apps/web/index.html:90 — `.initial-loader__spinner` moves (`animation: app-spin 0.7s linear infinite`) 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/ui/src/components/toast.tsx:28 — <span> moves — its `animate-[toast-fuse_linear_forwards]` 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 apps/web/src/index.css:93 — `html:active-view-transition-type(page)::view-transition-new(root)` moves (`animation: var(--d2) var(--ease) calc(var(--d2) * 0.7) both vt-page-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/src/index.css:125 — `html:active-view-transition-type(forward)::view-transition-new(root)` moves (`animation: var(--d2) var(--ease) calc(var(--d2) * 0.7) both vt-push-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/src/index.css:129 — `html:active-view-transition-type(back)::view-transition-new(root)` moves (`animation: var(--d2) var(--ease) calc(var(--d2) * 0.7) both vt-pop-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.
D30 · Dependency Vulnerabilities · Medium CVE · ×5
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D5 · Coupling · Off the main sequence · ×5
  • Off the main sequence: @reactive-resume/utils — @reactive-resume/utils: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 18 project(s), so it's rigid to change.
  • Off the main sequence: @reactive-resume/schema — @reactive-resume/schema: abstractness 0.00, instability 0.07, distance 0.93 — zone of pain — concrete and depended on by 13 project(s), so it's rigid to change.
  • Off the main sequence: @reactive-resume/resume — @reactive-resume/resume: abstractness 0.00, instability 0.18, distance 0.82 — zone of pain — concrete and depended on by 9 project(s), so it's rigid to change.
  • Off the main sequence: @reactive-resume/env — @reactive-resume/env: abstractness 0.00, instability 0.25, distance 0.75 — zone of pain — concrete and depended on by 6 project(s), so it's rigid to change.
  • Off the main sequence: @reactive-resume/fonts — @reactive-resume/fonts: 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.
AC2 · Forms & labels · <Combobox> field component without a label · ×4
  • <Combobox> field component without a label apps/web/src/features/career/offers.tsx:183 — 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.
  • <Combobox> field component without a label apps/web/src/features/settings/integrations/components/ai-provider-picker.tsx:33 — This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
  • <Combobox> field component without a label apps/web/src/routes/builder/kit.tsx:342 — This UI-library field component has no label / aria-label / aria-labelledby / id at this call site, and nothing written inside it here carries one either (a name prop is the form-submission key, not a label; an id, even one the component sets on what it renders, names nothing until a label points at it) — so it likely renders an unlabelled control. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
  • <Combobox> field component without a label apps/web/src/routes/builder/kit.tsx:344 — This UI-library field component has no label / aria-label / aria-labelledby / id at this call site, and nothing written inside it here carries one either (a name prop is the form-submission key, not a label; an id, even one the component sets on what it renders, names nothing until a label points at it) — so it likely renders an unlabelled control. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
D10 · Test Quality · Skipped test · ×4
  • Skipped test: (unnamed test) tests/e2e/specs/assistant.spec.ts:9 — Skipped — switched off by test.skip
  • Skipped test: (unnamed test) tests/e2e/specs/font-mirror.spec.ts:10 — Skipped — switched off by test.skip
  • Skipped test: (unnamed test) tests/e2e/specs/guest.spec.ts:5 — Skipped — switched off by test.skip
  • Skipped test: (unnamed test) tests/e2e/specs/posting-capture-extension.spec.ts:10 — Skipped — switched off by test.skip
D29 · Static Analysis (SAST) · REDACTED · ×3
  • REDACTED
  • REDACTED
  • REDACTED
PF3 · Async & latency hygiene · Sync-over-async blocking · ×3
  • Sync-over-async blocking apps/web/src/features/resume/import/read-file.ts:79 — `unzipSync` in `detectImportKind` 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 tooling/dev/test-db.mjs:50 — `execFileSync` in `ensureDatabases` 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 tooling/dev/test-db.mjs:96 — `spawnSync` 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.
R10 · Code Duplication · Duplicated block with local edits (60 matched lines × 2 locations) · ×3
  • Duplicated block with local edits (60 matched lines × 2 locations) apps/web/src/dialogs/auth/change-password.tsx:80 — apps/web/src/dialogs/auth/change-password.tsx:80 · apps/web/src/dialogs/auth/set-password.tsx:58 — the two spans are one implementation copied and then locally edited — 351 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 (60 matched lines × 2 locations) apps/web/src/features/documents/document-card.tsx:248 — apps/web/src/features/documents/document-card.tsx:248 · apps/web/src/features/documents/document-card.tsx:371 — the two spans are one implementation copied and then locally edited — 347 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
  • Duplicated block with local edits (60 matched lines × 2 locations) packages/db/src/schema/auth.ts:63 — packages/db/src/schema/auth.ts:63 · packages/db/src/schema/auth.ts:400 — the two spans are one implementation copied and then locally edited — 455 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication · Duplicated block (39 lines × 2 locations) · ×3
  • Duplicated block (39 lines × 2 locations) packages/import/src/linkedin.ts:100 — packages/import/src/linkedin.ts:100 · packages/schema/src/applications/csv.ts:20 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
  • Duplicated block (39 lines × 2 locations) packages/pdf/src/templates/kakuna/KakunaPage.tsx:54 — packages/pdf/src/templates/kakuna/KakunaPage.tsx:54 · packages/pdf/src/templates/meowth/MeowthPage.tsx:54 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
  • Duplicated block (39 lines × 2 locations) packages/pdf/src/templates/shared/sections.tsx:1101 — packages/pdf/src/templates/shared/sections.tsx:1101 · packages/pdf/src/templates/shared/sections.tsx:1298 — 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.
X2 · Cancellation propagation · Async function without AbortSignal · ×3
  • Async function without AbortSignal: fetchText tooling/locales/generate-region-zones.mjs:13 — `fetchText` 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: fetchSample apps/web/src/features/ats-checker/checker.tsx:164 — `fetchSample` 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: uiFontFace apps/web/src/features/applications/components/insights-view.tsx:323 — `uiFontFace` 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 })`.
X3 · Exception handling · Swallowed exception (caught, then discarded) · ×3
  • Swallowed exception (caught, then discarded) packages/schema/src/resume/period.ts:112 — `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, or keep only the failure you expect and rethrow the rest (`catch (e) { if (!(e instanceof SyntaxError)) throw e; … }`, or test `e.name`), because a JavaScript catch takes every exception, programming errors included.
  • Swallowed exception (caught, then discarded) packages/import/src/job-posting.ts:73 — `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, or keep only the failure you expect and rethrow the rest (`catch (e) { if (!(e instanceof SyntaxError)) throw e; … }`, or test `e.name`), because a JavaScript catch takes every exception, programming errors included.
  • Swallowed exception (caught, then discarded) packages/api/src/features/auth/export-uploads.ts:41 — `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, or keep only the failure you expect and rethrow the rest (`catch (e) { if (!(e instanceof SyntaxError)) throw e; … }`, or test `e.name`), because a JavaScript catch takes every exception, programming errors included.
AC3 · Page structure · Page without a main landmark · ×2
  • Page without a main landmark apps/web/index.html:2 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
  • Page without a main landmark tooling/capture/popup.html:2 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
D2 · Cognitive Complexity · values.compileProgram · ×2
  • values.compileProgram::compileRule (cognitive 48) packages/resume/src/stylesheet/values.ts:554 — values.compileProgram::compileRule has cognitive complexity 48 (threshold 15). Drivers by points: if/else 12 (25 pts), ternaries 7 (15 pts), boolean chains 5, loops 2 (3 pts) (nesting depth added 22). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (values.compileProgram::visit) 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.
  • values.compileProgram::visit (cognitive 20) packages/resume/src/stylesheet/values.ts:641 — values.compileProgram::visit has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (14 pts), ternaries 1 (3 pts), boolean chains 2, 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. This shape REPEATS in the file: one other method here (values.compileProgram::compileRule) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D2 · Cognitive Complexity · pdf-lines.headingTest · ×2
  • pdf-lines.headingTest::test (cognitive 46) packages/import/src/pdf-lines.ts:636 — pdf-lines.headingTest::test has cognitive complexity 46 (threshold 15). Drivers by points: boolean chains 38, if/else 8. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators. This shape REPEATS in the file: 2 other methods here (pdf-lines.headingTest, pdf-lines.headingTest::isolatedRaw) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
  • pdf-lines.headingTest::isolatedRaw (cognitive 16) packages/import/src/pdf-lines.ts:227 — pdf-lines.headingTest::isolatedRaw has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 7, if/else 4 (7 pts), loops 1, ternaries 1 (nesting depth added 3). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: 2 other methods here (pdf-lines.headingTest, pdf-lines.headingTest::test) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D29 · Static Analysis (SAST) · REDACTED · ×2
  • REDACTED
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×2
  • REDACTED
  • REDACTED
D31 · IaC & Container Security · Medium IaC · ×2
  • REDACTED
  • REDACTED
R7 · Dead Code · Dead file (~417 LoC) · ×2
  • Dead file (~417 LoC) apps/mobile/src/features/applications/InterviewSheet.tsx — no import path from any entry point (380 application, 52 tooling, 631 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/mobile/app/(app)/applications/[id]/interview.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 (~417 LoC) apps/mobile/src/features/builder/description/DescriptionScreen.tsx — no import path from any entry point (380 application, 52 tooling, 631 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (apps/mobile/app/(app)/builder/[id]/section/[section]/[item]/description.tsx, apps/mobile/app/(app)/builder/[id]/section/[section]/index.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~257 LoC) · ×2
  • Dead file (~257 LoC) apps/mobile/src/features/documents/library.tsx — no import path from any entry point (380 application, 52 tooling, 631 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/mobile/app/(app)/(tabs)/documents/index.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
  • Dead file (~257 LoC) apps/mobile/src/features/workspace/PrepScreen.tsx — no import path from any entry point (380 application, 52 tooling, 631 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/mobile/app/(app)/applications/[id]/prepare.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
AC2 · Forms & labels · <Textarea> field component without a label · ×1
  • <Textarea> field component without a label apps/web/src/features/applications/components/application-form-sheet.tsx:193 — This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
AC3 · Page structure · Heading level jumps from h1 to h3 · ×1
  • Heading level jumps from h1 to h3 apps/web/src/routes/builder/kit.tsx:638 — Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
AC6 · Visual & motion safety · Focus outline removed in CSS without a · ×1
  • Focus outline removed in CSS without a :focus replacement packages/ui/src/styles/globals.css:260 — `[data-pointer] :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.
D1 · Cyclomatic Complexity · add-application-dialog.AddApplicationForm (cyclomatic 140) · ×1
  • add-application-dialog.AddApplicationForm (cyclomatic 140) apps/web/src/features/applications/components/add-application-dialog.tsx:188 — add-application-dialog.AddApplicationForm has cyclomatic complexity 140 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators. This shape REPEATS in the file: one other method here (add-application-dialog.AddApplicationForm::add) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D1 · Cyclomatic Complexity · ai-consent.authorizeAiRequest (cyclomatic 129) · ×1
  • ai-consent.authorizeAiRequest (cyclomatic 129) apps/web/src/libs/orpc/ai-consent.ts:13 — ai-consent.authorizeAiRequest has cyclomatic complexity 129 (threshold 15). Of this number, 34 points are the body's own statements and 95 belong to 3 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · practise.Session (cyclomatic 121) · ×1
  • practise.Session (cyclomatic 121) apps/web/src/features/career/workspace/practise.tsx:373 — practise.Session has cyclomatic complexity 121 (threshold 15). Of this number, 76 points are the body's own statements and 45 belong to 16 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · config.getAuthConfig (cyclomatic 109) · ×1
  • config.getAuthConfig (cyclomatic 109) packages/auth/src/config.ts:797 — config.getAuthConfig has cyclomatic complexity 109 (threshold 15). Most of this is not in the body itself: 11 of the 109 points are its own statements and the rest belongs to 10 function literals inside it that branch (lines 874, 1052, 846, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D1 · Cyclomatic Complexity · ai-consent.authorizeAiRequest (cyclomatic 103) · ×1
  • ai-consent.authorizeAiRequest (cyclomatic 103) apps/mobile/src/api/ai-consent.ts:16 — ai-consent.authorizeAiRequest has cyclomatic complexity 103 (threshold 15). Of this number, 94 points are the body's own statements and 9 belong to 3 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · store.useLetterEditorStore (cyclomatic 97) · ×1
  • store.useLetterEditorStore (cyclomatic 97) apps/web/src/features/letters/store.ts:388 — store.useLetterEditorStore has cyclomatic complexity 97 (threshold 15). Most of this is not in the body itself: 1 of the 97 points is its own statement and the rest belongs to 15 function literals inside it that branch (lines 422, 536, 488, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D1 · Cyclomatic Complexity · rich-text-editor-field.RichTextEditor (cyclomatic 94) · ×1
  • rich-text-editor-field.RichTextEditor (cyclomatic 94) apps/web/src/features/resume/editor/write/rich-text-editor-field.tsx:214 — rich-text-editor-field.RichTextEditor has cyclomatic complexity 94 (threshold 15). Of this number, 47 points are the body's own statements and 47 belong to 19 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · messages.ProposalCard (cyclomatic 91) · ×1
  • messages.ProposalCard (cyclomatic 91) apps/web/src/features/career/workspace/messages.tsx:625 — messages.ProposalCard has cyclomatic complexity 91 (threshold 15). Of this number, 39 points are the body's own statements and 52 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.
D1 · Cyclomatic Complexity · schedule-sheet.ScheduleSheet (cyclomatic 91) · ×1
  • schedule-sheet.ScheduleSheet (cyclomatic 91) apps/web/src/features/career/schedule-sheet.tsx:138 — schedule-sheet.ScheduleSheet has cyclomatic complexity 91 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This shape REPEATS in the file: one other method here (schedule-sheet.ScheduleSheet::onSave) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D1 · Cyclomatic Complexity · screen.TodayScreen (cyclomatic 88) · ×1
  • screen.TodayScreen (cyclomatic 88) apps/mobile/src/features/today/screen.tsx:64 — screen.TodayScreen has cyclomatic complexity 88 (threshold 15). Of this number, 58 points are the body's own statements and 30 belong to 18 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · offer-entry.OfferForm (cyclomatic 87) · ×1
  • offer-entry.OfferForm (cyclomatic 87) apps/web/src/features/career/offer-entry.tsx:255 — offer-entry.OfferForm has cyclomatic complexity 87 (threshold 15). Of this number, 42 points are the body's own statements and 45 belong to 18 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · cascade.resolveStylesheet (cyclomatic 85) · ×1
  • cascade.resolveStylesheet (cyclomatic 85) packages/resume/src/stylesheet/cascade.ts:564 — cascade.resolveStylesheet has cyclomatic complexity 85 (threshold 15). Of this number, 81 points are the body's own statements and 4 belong to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · index.RouteComponent (cyclomatic 84) · ×1
  • index.RouteComponent (cyclomatic 84) apps/web/src/routes/dashboard/applications/index.tsx:121 — index.RouteComponent has cyclomatic complexity 84 (threshold 15). Of this number, 61 points are the body's own statements and 23 belong to 13 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · pdf-lines.importLines (cyclomatic 84) · ×1
  • pdf-lines.importLines (cyclomatic 84) packages/import/src/pdf-lines.ts:1349 — pdf-lines.importLines has cyclomatic complexity 84 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · documents-page.DocumentsPage (cyclomatic 80) · ×1
  • documents-page.DocumentsPage (cyclomatic 80) apps/web/src/features/documents/documents-page.tsx:80 — documents-page.DocumentsPage has cyclomatic complexity 80 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This shape REPEATS in the file: one other method here (documents-page.DocumentsPage::onSearchKeyDown) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D1 · Cyclomatic Complexity · coach.CoachPage (cyclomatic 79) · ×1
  • coach.CoachPage (cyclomatic 79) apps/web/src/features/career/coach.tsx:115 — coach.CoachPage has cyclomatic complexity 79 (threshold 15). Of this number, 45 points are the body's own statements and 34 belong to 17 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · prepare-review.ReviewForm (cyclomatic 77) · ×1
  • prepare-review.ReviewForm (cyclomatic 77) apps/web/src/features/career/workspace/prepare-review.tsx:49 — prepare-review.ReviewForm has cyclomatic complexity 77 (threshold 15). Of this number, 31 points are the body's own statements and 46 belong to 24 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · import-applications-sheet.ImportApplicationsSheet (cyclomatic 75) · ×1
  • import-applications-sheet.ImportApplicationsSheet (cyclomatic 75) apps/web/src/features/applications/components/import-applications-sheet.tsx:86 — import-applications-sheet.ImportApplicationsSheet has cyclomatic complexity 75 (threshold 15). Of this number, 38 points are the body's own statements and 37 belong to 19 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · to-forme.convertNode (cyclomatic 73) · ×1
  • to-forme.convertNode (cyclomatic 73) packages/pdf/src/forme/to-forme.tsx:477 — to-forme.convertNode has cyclomatic complexity 73 (threshold 15). Of this number, 64 points are the body's own statements and 9 belong to 4 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · fit.FitTab (cyclomatic 72) · ×1
  • fit.FitTab (cyclomatic 72) apps/web/src/features/career/workspace/fit.tsx:52 — fit.FitTab has cyclomatic complexity 72 (threshold 15). Of this number, 41 points are the body's own statements and 31 belong to 9 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · conversation.Conversation (cyclomatic 71) · ×1
  • conversation.Conversation (cyclomatic 71) apps/web/src/features/assistant/conversation.tsx:102 — conversation.Conversation has cyclomatic complexity 71 (threshold 15). Of this number, 24 points are the body's own statements and 47 belong to 21 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · new-document-dialog.NewDocument (cyclomatic 71) · ×1
  • new-document-dialog.NewDocument (cyclomatic 71) apps/web/src/features/documents/new-document-dialog.tsx:93 — new-document-dialog.NewDocument has cyclomatic complexity 71 (threshold 15). Of this number, 45 points are the body's own statements and 26 belong to 9 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · interview-dialog.InterviewDialog (cyclomatic 69) · ×1
  • interview-dialog.InterviewDialog (cyclomatic 69) apps/web/src/features/applications/components/interview-dialog.tsx:160 — interview-dialog.InterviewDialog has cyclomatic complexity 69 (threshold 15). Of this number, 40 points are the body's own statements and 29 belong to 15 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · DescriptionScreen.DescriptionScreen (cyclomatic 68) · ×1
  • DescriptionScreen.DescriptionScreen (cyclomatic 68) apps/mobile/src/features/builder/description/DescriptionScreen.tsx:46 — DescriptionScreen.DescriptionScreen has cyclomatic complexity 68 (threshold 15). Of this number, 27 points are the body's own statements and 41 belong to 17 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · apply.AnswerCard (cyclomatic 68) · ×1
  • apply.AnswerCard (cyclomatic 68) apps/web/src/features/career/workspace/apply.tsx:490 — apply.AnswerCard has cyclomatic complexity 68 (threshold 15). Of this number, 49 points are the body's own statements and 19 belong to 12 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · trash-page.TrashPage (cyclomatic 68) · ×1
  • trash-page.TrashPage (cyclomatic 68) apps/web/src/features/trash/trash-page.tsx:81 — trash-page.TrashPage has cyclomatic complexity 68 (threshold 15). Of this number, 24 points are the body's own statements and 44 belong to 12 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · offers.ScopedOffersScreen (cyclomatic 67) · ×1
  • offers.ScopedOffersScreen (cyclomatic 67) apps/mobile/src/features/career/offers.tsx:31 — offers.ScopedOffersScreen has cyclomatic complexity 67 (threshold 15). Most of this is not in the body itself: 14 of the 67 points are its own statements and the rest belongs to 14 function items inside it that branch (a function literal at line 298, a function literal at line 243, terms, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · answer-library.AnswerLibrary (cyclomatic 67) · ×1
  • answer-library.AnswerLibrary (cyclomatic 67) apps/web/src/features/career/workspace/answer-library.tsx:49 — answer-library.AnswerLibrary has cyclomatic complexity 67 (threshold 15). Of this number, 43 points are the body's own statements and 24 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.
D1 · Cyclomatic Complexity · activity.Activity (cyclomatic 65) · ×1
  • activity.Activity (cyclomatic 65) apps/web/src/features/applications/components/detail/activity.tsx:65 — activity.Activity has cyclomatic complexity 65 (threshold 15). Most of this is not in the body itself: 15 of the 65 points are its own statements and the rest belongs to 12 function items inside it that branch (a function literal at line 212, describe, a function literal at line 305, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · page-canvas.ResumePageCanvas (cyclomatic 65) · ×1
  • page-canvas.ResumePageCanvas (cyclomatic 65) apps/web/src/routes/builder/$resumeId/-components/page-canvas.tsx:71 — page-canvas.ResumePageCanvas has cyclomatic complexity 65 (threshold 15). Of this number, 48 points are the body's own statements and 17 belong to 6 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · style.toFormeStyle (cyclomatic 65) · ×1
  • style.toFormeStyle (cyclomatic 65) packages/pdf/src/forme/style.ts:377 — style.toFormeStyle has cyclomatic complexity 65 (threshold 15). Of this number, 63 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · generate.generateCareer (cyclomatic 64) · ×1
  • generate.generateCareer (cyclomatic 64) packages/api/src/features/career/generate.ts:113 — generate.generateCareer has cyclomatic complexity 64 (threshold 15). Of this number, 54 points are the body's own statements and 10 belong to 4 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · conversation.ToolPartView (cyclomatic 63) · ×1
  • conversation.ToolPartView (cyclomatic 63) apps/web/src/features/assistant/conversation.tsx:743 — conversation.ToolPartView has cyclomatic complexity 63 (threshold 15). Of this number, 61 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · shell.Workspace (cyclomatic 62) · ×1
  • shell.Workspace (cyclomatic 62) apps/web/src/features/career/workspace/shell.tsx:123 — shell.Workspace has cyclomatic complexity 62 (threshold 15). Of this number, 41 points are the body's own statements and 21 belong to 10 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · assistant-panel.AssistantPanel (cyclomatic 61) · ×1
  • assistant-panel.AssistantPanel (cyclomatic 61) apps/web/src/features/assistant/assistant-panel.tsx:59 — assistant-panel.AssistantPanel has cyclomatic complexity 61 (threshold 15). Of this number, 45 points are the body's own statements and 16 belong to 6 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · preparation.Preparation (cyclomatic 61) · ×1
  • preparation.Preparation (cyclomatic 61) apps/web/src/features/career/workspace/preparation.tsx:40 — preparation.Preparation has cyclomatic complexity 61 (threshold 15). Of this number, 19 points are the body's own statements and 42 belong to 7 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · pdf-lines.headingTest · ×1
  • pdf-lines.headingTest::test (cyclomatic 61) packages/import/src/pdf-lines.ts:636 — pdf-lines.headingTest::test has cyclomatic complexity 61 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators. This shape REPEATS in the file: one other method here (pdf-lines.headingTest) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D1 · Cyclomatic Complexity · scroll.useScrollScenes (cyclomatic 60) · ×1
  • scroll.useScrollScenes (cyclomatic 60) apps/web/src/features/homepage/scroll.ts:223 — scroll.useScrollScenes has cyclomatic complexity 60 (threshold 15). Most of this is not in the body itself: 1 of the 60 points is its own statement and the rest belongs to 6 function literals inside it that branch (lines 290, 244, 413, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D1 · Cyclomatic Complexity · sent-documents.SentDocuments (cyclomatic 59) · ×1
  • sent-documents.SentDocuments (cyclomatic 59) apps/web/src/features/applications/components/detail/sent-documents.tsx:60 — sent-documents.SentDocuments has cyclomatic complexity 59 (threshold 15). Of this number, 46 points are the body's own statements and 13 belong to 11 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · apply.ApplyTab (cyclomatic 58) · ×1
  • apply.ApplyTab (cyclomatic 58) apps/web/src/features/career/workspace/apply.tsx:80 — apply.ApplyTab has cyclomatic complexity 58 (threshold 15). Of this number, 31 points are the body's own statements and 27 belong to 15 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · actions.ScopedDocumentActionsScreen (cyclomatic 55) · ×1
  • actions.ScopedDocumentActionsScreen (cyclomatic 55) apps/mobile/src/features/documents/actions.tsx:40 — actions.ScopedDocumentActionsScreen has cyclomatic complexity 55 (threshold 15). Of this number, 21 points are the body's own statements and 34 belong to 9 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · chip-input.ChipInput (cyclomatic 55) · ×1
  • chip-input.ChipInput (cyclomatic 55) apps/web/src/components/input/chip-input.tsx:170 — chip-input.ChipInput has cyclomatic complexity 55 (threshold 15). Most of this is not in the body itself: 13 of the 55 points are its own statements and the rest belongs to 14 function items inside it that branch (handleDragEnd, handleKeyDown, removeChip, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · pdf-lines.orderExperienceHeaders (cyclomatic 55) · ×1
  • pdf-lines.orderExperienceHeaders (cyclomatic 55) packages/import/src/pdf-lines.ts:1181 — pdf-lines.orderExperienceHeaders has cyclomatic complexity 55 (threshold 15). Of this number, 44 points are the body's own statements and 11 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.
D1 · Cyclomatic Complexity · SignInScreen.SignInScreen (cyclomatic 54) · ×1
  • SignInScreen.SignInScreen (cyclomatic 54) apps/mobile/src/features/auth/SignInScreen.tsx:47 — SignInScreen.SignInScreen has cyclomatic complexity 54 (threshold 15). Of this number, 35 points are the body's own statements and 19 belong to 4 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · import.ScopedImportScreen (cyclomatic 54) · ×1
  • import.ScopedImportScreen (cyclomatic 54) apps/mobile/src/features/documents/import.tsx:43 — import.ScopedImportScreen has cyclomatic complexity 54 (threshold 15). Of this number, 30 points are the body's own statements and 24 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.
D1 · Cyclomatic Complexity · csv.mapCsvToApplications (cyclomatic 54) · ×1
  • csv.mapCsvToApplications (cyclomatic 54) packages/schema/src/applications/csv.ts:300 — csv.mapCsvToApplications has cyclomatic complexity 54 (threshold 15). Of this number, 27 points are the body's own statements and 27 belong to 2 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · schedules.ScheduleEditor (cyclomatic 53) · ×1
  • schedules.ScheduleEditor (cyclomatic 53) apps/mobile/src/features/career/schedules.tsx:81 — schedules.ScheduleEditor has cyclomatic complexity 53 (threshold 15). Of this number, 34 points are the body's own statements and 19 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.
D1 · Cyclomatic Complexity · coach.ScopedCoachScreen (cyclomatic 52) · ×1
  • coach.ScopedCoachScreen (cyclomatic 52) apps/mobile/src/features/career/coach.tsx:52 — coach.ScopedCoachScreen has cyclomatic complexity 52 (threshold 15). Of this number, 27 points are the body's own statements and 25 belong to 11 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · profile.ApplicationProfile (cyclomatic 52) · ×1
  • profile.ApplicationProfile (cyclomatic 52) apps/web/src/features/settings/profile.tsx:110 — profile.ApplicationProfile has cyclomatic complexity 52 (threshold 15). Of this number, 38 points are the body's own statements and 14 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.
D1 · Cyclomatic Complexity · SaveJobScreen.SaveJobScreen (cyclomatic 51) · ×1
  • SaveJobScreen.SaveJobScreen (cyclomatic 51) apps/mobile/src/features/applications/SaveJobScreen.tsx:41 — SaveJobScreen.SaveJobScreen has cyclomatic complexity 51 (threshold 15). Of this number, 29 points are the body's own statements and 22 belong to 8 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · proposals-screen.Proposals (cyclomatic 51) · ×1
  • proposals-screen.Proposals (cyclomatic 51) apps/mobile/src/features/builder/assistant/proposals-screen.tsx:43 — proposals-screen.Proposals has cyclomatic complexity 51 (threshold 15). Most of this is not in the body itself: 14 of the 51 points are its own statements and the rest belongs to 13 function items inside it that branch (a function literal at line 158, decide, seed, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · messages.MessagesTab (cyclomatic 51) · ×1
  • messages.MessagesTab (cyclomatic 51) apps/web/src/features/career/workspace/messages.tsx:81 — messages.MessagesTab has cyclomatic complexity 51 (threshold 15). Of this number, 48 points are the body's own statements and 3 belong to 2 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · web-access.WebAccessSection (cyclomatic 51) · ×1
  • web-access.WebAccessSection (cyclomatic 51) apps/web/src/features/settings/ai/web-access.tsx:56 — web-access.WebAccessSection has cyclomatic complexity 51 (threshold 15). Of this number, 48 points are the body's own statements and 3 belong to 3 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · offers.OffersPage (cyclomatic 50) · ×1
  • offers.OffersPage (cyclomatic 50) apps/web/src/features/career/offers.tsx:223 — offers.OffersPage has cyclomatic complexity 50 (threshold 15). Of this number, 36 points are the body's own statements and 14 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.
D1 · Cyclomatic Complexity · new-document-dialog.CopyForJob (cyclomatic 50) · ×1
  • new-document-dialog.CopyForJob (cyclomatic 50) apps/web/src/features/documents/new-document-dialog.tsx:650 — new-document-dialog.CopyForJob has cyclomatic complexity 50 (threshold 15). Of this number, 32 points are the body's own statements and 18 belong to 5 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · preferences.PreferencesContent (cyclomatic 49) · ×1
  • preferences.PreferencesContent (cyclomatic 49) apps/mobile/src/features/career/preferences.tsx:37 — preferences.PreferencesContent has cyclomatic complexity 49 (threshold 15). Of this number, 29 points are the body's own statements and 20 belong to 3 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · practise.PractiseTab (cyclomatic 49) · ×1
  • practise.PractiseTab (cyclomatic 49) apps/web/src/features/career/workspace/practise.tsx:122 — practise.PractiseTab has cyclomatic complexity 49 (threshold 15). Of this number, 48 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · coach-chat.ChatView (cyclomatic 49) · ×1
  • coach-chat.ChatView (cyclomatic 49) apps/web/src/features/career/coach-chat.tsx:84 — coach-chat.ChatView has cyclomatic complexity 49 (threshold 15). Of this number, 30 points are the body's own statements and 19 belong to 7 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · proposal-list.ProposalItem (cyclomatic 49) · ×1
  • proposal-list.ProposalItem (cyclomatic 49) apps/web/src/features/resume/editor/proposals/proposal-list.tsx:303 — proposal-list.ProposalItem has cyclomatic complexity 49 (threshold 15). Of this number, 42 points are the body's own statements and 7 belong to 4 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · html-to-docx.processBlockElement (cyclomatic 49) · ×1
  • html-to-docx.processBlockElement (cyclomatic 49) packages/docx/src/html-to-docx.ts:149 — html-to-docx.processBlockElement has cyclomatic complexity 49 (threshold 15). Of this number, 46 points are the body's own statements and 3 belong to 2 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · prototype.fillControlledForm (cyclomatic 48) · ×1
  • prototype.fillControlledForm (cyclomatic 48) tooling/autofill/prototype.ts:38 — prototype.fillControlledForm has cyclomatic complexity 48 (threshold 15). Of this number, 35 points are the body's own statements and 13 belong to 2 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · linking.parseDeepLink (cyclomatic 47) · ×1
  • linking.parseDeepLink (cyclomatic 47) apps/mobile/src/data/linking.ts:33 — linking.parseDeepLink has cyclomatic complexity 47 (threshold 15). Of this number, 43 points are the body's own statements and 4 belong to 2 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · overview.ApplicationOverview (cyclomatic 47) · ×1
  • overview.ApplicationOverview (cyclomatic 47) apps/web/src/features/career/workspace/overview.tsx:52 — overview.ApplicationOverview has cyclomatic complexity 47 (threshold 15). Of this number, 41 points are the body's own statements and 6 belong to 3 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · pdf-lines.projectSectionFields (cyclomatic 47) · ×1
  • pdf-lines.projectSectionFields (cyclomatic 47) packages/import/src/pdf-lines.ts:1839 — pdf-lines.projectSectionFields has cyclomatic complexity 47 (threshold 15). Of this number, 31 points are the body's own statements and 16 belong to 6 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · assistant-screen.AssistantScreen (cyclomatic 46) · ×1
  • assistant-screen.AssistantScreen (cyclomatic 46) apps/mobile/src/features/builder/assistant/assistant-screen.tsx:47 — assistant-screen.AssistantScreen has cyclomatic complexity 46 (threshold 15). Of this number, 23 points are the body's own statements and 23 belong to 7 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · save-posting.SavePosting (cyclomatic 46) · ×1
  • save-posting.SavePosting (cyclomatic 46) apps/web/src/features/assistant/save-posting.tsx:25 — save-posting.SavePosting has cyclomatic complexity 46 (threshold 15). Most of this is not in the body itself: 9 of the 46 points are its own statements and the rest belongs to 5 function items inside it that branch (save, a function literal at line 67, a function literal at line 71, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · LayoutScreen.LayoutScreen (cyclomatic 45) · ×1
  • LayoutScreen.LayoutScreen (cyclomatic 45) apps/mobile/src/features/builder/design/LayoutScreen.tsx:80 — LayoutScreen.LayoutScreen has cyclomatic complexity 45 (threshold 15). Most of this is not in the body itself: 7 of the 45 points are its own statements and the rest belongs to 13 function items inside it that branch (fit, a function literal at line 109, openMenu, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · search.ScopedSearchScreen (cyclomatic 45) · ×1
  • search.ScopedSearchScreen (cyclomatic 45) apps/mobile/src/features/documents/search.tsx:31 — search.ScopedSearchScreen has cyclomatic complexity 45 (threshold 15). Of this number, 30 points are the body's own statements and 15 belong to 8 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · conversation.Composer (cyclomatic 45) · ×1
  • conversation.Composer (cyclomatic 45) apps/web/src/features/assistant/conversation.tsx:1077 — conversation.Composer has cyclomatic complexity 45 (threshold 15). Of this number, 18 points are the body's own statements and 27 belong to 8 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · jobs.execute (cyclomatic 45) · ×1
  • jobs.execute (cyclomatic 45) packages/api/src/features/career/jobs.ts:541 — jobs.execute has cyclomatic complexity 45 (threshold 15). Most of this is not in the body itself: 12 of the 45 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 642, 563). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D1 · Cyclomatic Complexity · to-html.convertNode (cyclomatic 45) · ×1
  • to-html.convertNode (cyclomatic 45) packages/pdf/src/html/to-html.ts:290 — to-html.convertNode has cyclomatic complexity 45 (threshold 15). Of this number, 43 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.
D1 · Cyclomatic Complexity · store.createDraftStore.open (cyclomatic 44) · ×1
  • store.createDraftStore.open (cyclomatic 44) apps/mobile/src/data/draft/store.ts:239 — store.createDraftStore.open has cyclomatic complexity 44 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · PrepScreen.PrepScreen (cyclomatic 44) · ×1
  • PrepScreen.PrepScreen (cyclomatic 44) apps/mobile/src/features/workspace/PrepScreen.tsx:39 — PrepScreen.PrepScreen has cyclomatic complexity 44 (threshold 15). Of this number, 37 points are the body's own statements and 7 belong to 6 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · provider-fields.ProviderFieldsForm (cyclomatic 44) · ×1
  • provider-fields.ProviderFieldsForm (cyclomatic 44) apps/web/src/features/settings/ai/provider-fields.tsx:50 — provider-fields.ProviderFieldsForm has cyclomatic complexity 44 (threshold 15). Of this number, 43 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · pdf-lines.headingTest (cyclomatic 44) · ×1
  • pdf-lines.headingTest (cyclomatic 44) packages/import/src/pdf-lines.ts:207 — pdf-lines.headingTest has cyclomatic complexity 44 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators. This shape REPEATS in the file: one other method here (pdf-lines.headingTest::test) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D1 · Cyclomatic Complexity · coach-chat.MessageView (cyclomatic 43) · ×1
  • coach-chat.MessageView (cyclomatic 43) apps/web/src/features/career/coach-chat.tsx:417 — coach-chat.MessageView has cyclomatic complexity 43 (threshold 15). Of this number, 41 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.
D1 · Cyclomatic Complexity · today.NewRoles (cyclomatic 43) · ×1
  • today.NewRoles (cyclomatic 43) apps/web/src/features/career/today.tsx:634 — today.NewRoles has cyclomatic complexity 43 (threshold 15). Of this number, 27 points are the body's own statements and 16 belong to 9 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · profile.ProfileDialog (cyclomatic 43) · ×1
  • profile.ProfileDialog (cyclomatic 43) apps/web/src/features/settings/profile.tsx:467 — profile.ProfileDialog has cyclomatic complexity 43 (threshold 15). Of this number, 23 points are the body's own statements and 20 belong to 10 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · CheckScreen.CheckScreen (cyclomatic 42) · ×1
  • CheckScreen.CheckScreen (cyclomatic 42) apps/mobile/src/features/builder/check/CheckScreen.tsx:93 — CheckScreen.CheckScreen has cyclomatic complexity 42 (threshold 15). Of this number, 32 points are the body's own statements and 10 belong to 6 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · render.renderResumeElement (cyclomatic 42) · ×1
  • render.renderResumeElement (cyclomatic 42) packages/pdf/src/forme/render.ts:385 — render.renderResumeElement has cyclomatic complexity 42 (threshold 15). Most of this is not in the body itself: 14 of the 42 points are its own statements and the rest belongs to 5 function items inside it that branch (layOut, layOutOnce::render, a function literal at line 455, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · values.valueSyntaxError (cyclomatic 42) · ×1
  • values.valueSyntaxError (cyclomatic 42) packages/resume/src/stylesheet/values.ts:376 — values.valueSyntaxError 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.
D1 · Cyclomatic Complexity · list-view.ApplicationList (cyclomatic 41) · ×1
  • list-view.ApplicationList (cyclomatic 41) apps/web/src/features/applications/components/list-view.tsx:115 — list-view.ApplicationList has cyclomatic complexity 41 (threshold 15). Most of this is not in the body itself: 11 of the 41 points are its own statements and the rest belongs to 12 function items inside it that branch (move, followedUp, header, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · ApplicationsScreen.ListView (cyclomatic 40) · ×1
  • ApplicationsScreen.ListView (cyclomatic 40) apps/mobile/src/features/applications/ApplicationsScreen.tsx:176 — ApplicationsScreen.ListView has cyclomatic complexity 40 (threshold 15). Of this number, 22 points are the body's own statements and 18 belong to 11 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · facts.FactsPage (cyclomatic 40) · ×1
  • facts.FactsPage (cyclomatic 40) apps/web/src/features/career/knowledge/facts.tsx:59 — facts.FactsPage has cyclomatic complexity 40 (threshold 15). Of this number, 28 points are the body's own statements and 12 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.
D1 · Cyclomatic Complexity · stories.StoryEditor (cyclomatic 39) · ×1
  • stories.StoryEditor (cyclomatic 39) apps/web/src/features/career/knowledge/stories.tsx:523 — stories.StoryEditor has cyclomatic complexity 39 (threshold 15). Of this number, 19 points are the body's own statements and 20 belong to 9 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · proposal-list.ChangeSet (cyclomatic 39) · ×1
  • proposal-list.ChangeSet (cyclomatic 39) apps/web/src/features/resume/editor/proposals/proposal-list.tsx:144 — proposal-list.ChangeSet has cyclomatic complexity 39 (threshold 15). Of this number, 18 points are the body's own statements and 21 belong to 6 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · section-view.SectionOptions (cyclomatic 39) · ×1
  • section-view.SectionOptions (cyclomatic 39) apps/web/src/features/resume/editor/write/section-view.tsx:269 — section-view.SectionOptions has cyclomatic complexity 39 (threshold 15). Of this number, 18 points are the body's own statements and 21 belong to 10 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · application-form-sheet.ApplicationFormSheet (cyclomatic 38) · ×1
  • application-form-sheet.ApplicationFormSheet (cyclomatic 38) apps/web/src/features/applications/components/application-form-sheet.tsx:236 — application-form-sheet.ApplicationFormSheet has cyclomatic complexity 38 (threshold 15). Of this number, 19 points are the body's own statements and 19 belong to 8 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · coach-sheet.CoachSheetBody (cyclomatic 38) · ×1
  • coach-sheet.CoachSheetBody (cyclomatic 38) apps/web/src/features/career/workspace/coach-sheet.tsx:113 — coach-sheet.CoachSheetBody has cyclomatic complexity 38 (threshold 15). Of this number, 28 points are the body's own statements and 10 belong to 6 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · use-resume-import.useResumeImport.importFile (cyclomatic 38) · ×1
  • use-resume-import.useResumeImport.importFile (cyclomatic 38) apps/web/src/features/documents/import/use-resume-import.ts:94 — use-resume-import.useResumeImport.importFile has cyclomatic complexity 38 (threshold 15). Of this number, 33 points are the body's own statements and 5 belong to 2 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · picture-settings.PictureSettings (cyclomatic 38) · ×1
  • picture-settings.PictureSettings (cyclomatic 38) apps/web/src/features/resume/editor/write/picture-settings.tsx:589 — picture-settings.PictureSettings has cyclomatic complexity 38 (threshold 15). Most of this is not in the body itself: 14 of the 38 points are its own statements and the rest belongs to 11 function items inside it that branch (onUploadPicture, onDeletePicture, a function literal at line 640, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · pdf-lines.splitExperienceItems (cyclomatic 38) · ×1
  • pdf-lines.splitExperienceItems (cyclomatic 38) packages/import/src/pdf-lines.ts:965 — pdf-lines.splitExperienceItems has cyclomatic complexity 38 (threshold 15). Of this number, 35 points are the body's own statements and 3 belong to 3 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · fields.TextField (cyclomatic 37) · ×1
  • fields.TextField (cyclomatic 37) apps/mobile/src/ui/fields.tsx:83 — fields.TextField 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.
D1 · Cyclomatic Complexity · apply.Checklist (cyclomatic 37) · ×1
  • apply.Checklist (cyclomatic 37) apps/web/src/features/career/workspace/apply.tsx:959 — apply.Checklist has cyclomatic complexity 37 (threshold 15). Of this number, 25 points are the body's own statements and 12 belong to 5 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · design-panel.DesignPanel (cyclomatic 37) · ×1
  • design-panel.DesignPanel (cyclomatic 37) apps/web/src/routes/builder/$resumeId/-components/design-panel.tsx:45 — design-panel.DesignPanel has cyclomatic complexity 37 (threshold 15). Of this number, 34 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.
D1 · Cyclomatic Complexity · preview-screen.PreviewScreen (cyclomatic 36) · ×1
  • preview-screen.PreviewScreen (cyclomatic 36) apps/mobile/src/features/builder/preview/preview-screen.tsx:30 — preview-screen.PreviewScreen has cyclomatic complexity 36 (threshold 15). Of this number, 26 points are the body's own statements and 10 belong to 4 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · share-screen.ShareScreen (cyclomatic 36) · ×1
  • share-screen.ShareScreen (cyclomatic 36) apps/mobile/src/features/builder/share/share-screen.tsx:35 — share-screen.ShareScreen has cyclomatic complexity 36 (threshold 15). Of this number, 18 points are the body's own statements and 18 belong to 7 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · ProviderScreen.ScopedProviderScreen (cyclomatic 36) · ×1
  • ProviderScreen.ScopedProviderScreen (cyclomatic 36) apps/mobile/src/features/settings/ProviderScreen.tsx:59 — ProviderScreen.ScopedProviderScreen has cyclomatic complexity 36 (threshold 15). Of this number, 17 points are the body's own statements and 19 belong to 7 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · application-detail-sheet.Detail (cyclomatic 36) · ×1
  • application-detail-sheet.Detail (cyclomatic 36) apps/web/src/features/applications/components/application-detail-sheet.tsx:206 — application-detail-sheet.Detail has cyclomatic complexity 36 (threshold 15). Of this number, 19 points are the body's own statements and 17 belong to 8 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · guest.invokeGuest (cyclomatic 35) · ×1
  • guest.invokeGuest (cyclomatic 35) apps/mobile/src/data/guest.ts:24 — guest.invokeGuest has cyclomatic complexity 35 (threshold 15). Of this number, 30 points are the body's own statements and 5 belong to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · issues.describe (cyclomatic 35) · ×1
  • issues.describe (cyclomatic 35) apps/mobile/src/features/builder/check/issues.ts:66 — issues.describe has cyclomatic complexity 35 (threshold 15). Of this number, 25 points are the body's own statements and 10 belong to 4 function literals inside it that branch. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
D1 · Cyclomatic Complexity · EntryScreen.EntryScreen (cyclomatic 35) · ×1
  • EntryScreen.EntryScreen (cyclomatic 35) apps/mobile/src/features/builder/entry/EntryScreen.tsx:77 — EntryScreen.EntryScreen has cyclomatic complexity 35 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This shape REPEATS in the file: one other method here (EntryScreen.EntryScreen::render) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D1 · Cyclomatic Complexity · facts.ScopedFactsScreen (cyclomatic 35) · ×1
  • facts.ScopedFactsScreen (cyclomatic 35) apps/mobile/src/features/career/facts.tsx:29 — facts.ScopedFactsScreen has cyclomatic complexity 35 (threshold 15). Of this number, 16 points are the body's own statements and 19 belong to 10 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · consent.OAuthConsentPage (cyclomatic 35) · ×1
  • consent.OAuthConsentPage (cyclomatic 35) apps/web/src/features/auth/pages/consent.tsx:54 — consent.OAuthConsentPage has cyclomatic complexity 35 (threshold 15). Of this number, 27 points are the body's own statements and 8 belong to 2 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · preview.browser.ResumePreviewClient (cyclomatic 35) · ×1
  • preview.browser.ResumePreviewClient (cyclomatic 35) apps/web/src/features/resume/preview/preview.browser.tsx:138 — preview.browser.ResumePreviewClient has cyclomatic complexity 35 (threshold 15). Most of this is not in the body itself: 7 of the 35 points are its own statements and the rest belongs to 9 function literals inside it that branch (lines 180, 298, 168, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D1 · Cyclomatic Complexity · rich-text.RichText (cyclomatic 35) · ×1
  • rich-text.RichText (cyclomatic 35) packages/pdf/src/templates/shared/rich-text.tsx:81 — rich-text.RichText has cyclomatic complexity 35 (threshold 15). Most of this is not in the body itself: 11 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 240, renderText, renderView, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · values.expandShorthand (cyclomatic 35) · ×1
  • values.expandShorthand (cyclomatic 35) packages/resume/src/stylesheet/values.ts:241 — values.expandShorthand has cyclomatic complexity 35 (threshold 15). Of this number, 34 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · InterviewSheet.InterviewForm (cyclomatic 34) · ×1
  • InterviewSheet.InterviewForm (cyclomatic 34) apps/mobile/src/features/applications/InterviewSheet.tsx:82 — InterviewSheet.InterviewForm has cyclomatic complexity 34 (threshold 15). Most of this is not in the body itself: 15 of the 34 points are its own statements and the rest belongs to 10 function items inside it that branch (save, a function literal at line 168, pickWallTime, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · letter-screen.LetterScreen (cyclomatic 34) · ×1
  • letter-screen.LetterScreen (cyclomatic 34) apps/mobile/src/features/letters/letter-screen.tsx:30 — letter-screen.LetterScreen has cyclomatic complexity 34 (threshold 15). Of this number, 21 points are the body's own statements and 13 belong to 9 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · draft.flushResumeSave (cyclomatic 34) · ×1
  • draft.flushResumeSave (cyclomatic 34) apps/web/src/features/resume/builder/draft.ts:392 — draft.flushResumeSave has cyclomatic complexity 34 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · improve.ImprovePanel (cyclomatic 34) · ×1
  • improve.ImprovePanel (cyclomatic 34) apps/web/src/features/resume/editor/write/improve.tsx:49 — improve.ImprovePanel has cyclomatic complexity 34 (threshold 15). Of this number, 21 points are the body's own statements and 13 belong to 7 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · pages.LayoutPages (cyclomatic 34) · ×1
  • pages.LayoutPages (cyclomatic 34) apps/web/src/routes/builder/$resumeId/-sidebar/right/sections/layout/pages.tsx:109 — pages.LayoutPages has cyclomatic complexity 34 (threshold 15). Most of this is not in the body itself: 7 of the 34 points are its own statements and the rest belongs to 7 function literals inside it that branch (lines 152, 131, 237, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D1 · Cyclomatic Complexity · trash.ScopedTrashScreen (cyclomatic 33) · ×1
  • trash.ScopedTrashScreen (cyclomatic 33) apps/mobile/src/features/documents/trash.tsx:35 — trash.ScopedTrashScreen has cyclomatic complexity 33 (threshold 15). Most of this is not in the body itself: 13 of the 33 points are its own statements and the rest belongs to 7 function items inside it that branch (remove, restoreItem, a function literal at line 77, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · contacts.ContactList (cyclomatic 33) · ×1
  • contacts.ContactList (cyclomatic 33) apps/web/src/features/applications/components/detail/contacts.tsx:142 — contacts.ContactList has cyclomatic complexity 33 (threshold 15). Of this number, 16 points are the body's own statements and 17 belong to 7 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · application-packet.PacketForm (cyclomatic 33) · ×1
  • application-packet.PacketForm (cyclomatic 33) apps/web/src/features/career/workspace/application-packet.tsx:55 — application-packet.PacketForm has cyclomatic complexity 33 (threshold 15). Of this number, 16 points are the body's own statements and 17 belong to 11 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · writing-tab.WritingTab (cyclomatic 33) · ×1
  • writing-tab.WritingTab (cyclomatic 33) apps/web/src/features/resume/editor/check/writing-tab.tsx:49 — writing-tab.WritingTab has cyclomatic complexity 33 (threshold 15). Of this number, 23 points are the body's own statements and 10 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.
D1 · Cyclomatic Complexity · service.createAgent (cyclomatic 33) · ×1
  • service.createAgent (cyclomatic 33) packages/api/src/features/agent/service.ts:903 — service.createAgent has cyclomatic complexity 33 (threshold 15). Most of this is not in the body itself: 13 of the 33 points are its own statements and the rest belongs to 11 function items inside it that branch (a function literal at line 1042, a function literal at line 1105, allow, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · json-resume.convertJSONResume (cyclomatic 33) · ×1
  • json-resume.convertJSONResume (cyclomatic 33) packages/import/src/json-resume.tsx:162 — json-resume.convertJSONResume has cyclomatic complexity 33 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · pdf-lines.wrappedRightCell (cyclomatic 33) · ×1
  • pdf-lines.wrappedRightCell (cyclomatic 33) packages/import/src/pdf-lines.ts:1653 — pdf-lines.wrappedRightCell has cyclomatic complexity 33 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · store.createDraftStore.flush (cyclomatic 32) · ×1
  • store.createDraftStore.flush (cyclomatic 32) apps/mobile/src/data/draft/store.ts:436 — store.createDraftStore.flush has cyclomatic complexity 32 (threshold 15). Of this number, 16 points are the body's own statements and 16 belong to one function literal inside it that branches. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · library.ScopedLibraryScreen (cyclomatic 32) · ×1
  • library.ScopedLibraryScreen (cyclomatic 32) apps/mobile/src/features/documents/library.tsx:41 — library.ScopedLibraryScreen has cyclomatic complexity 32 (threshold 15). Of this number, 16 points are the body's own statements and 16 belong to 8 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · resume-facts.ReviewResumeFacts (cyclomatic 32) · ×1
  • resume-facts.ReviewResumeFacts (cyclomatic 32) apps/web/src/features/career/knowledge/resume-facts.tsx:50 — resume-facts.ReviewResumeFacts has cyclomatic complexity 32 (threshold 15). Of this number, 19 points are the body's own statements and 13 belong to 8 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · offers.useCells.<returned closure> (cyclomatic 32) · ×1
  • offers.useCells.<returned closure> (cyclomatic 32) apps/web/src/features/career/offers.tsx:921 — offers.useCells.<returned closure> has cyclomatic complexity 32 (threshold 15). Of this number, 19 points are the body's own statements and 13 belong to 2 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · letter-page.LetterPage (cyclomatic 32) · ×1
  • letter-page.LetterPage (cyclomatic 32) apps/web/src/routes/builder/letter/-components/letter-page.tsx:45 — letter-page.LetterPage has cyclomatic complexity 32 (threshold 15). Of this number, 18 points are the body's own statements and 14 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.
D1 · Cyclomatic Complexity · pdf-lines.educationRecords (cyclomatic 32) · ×1
  • pdf-lines.educationRecords (cyclomatic 32) packages/import/src/pdf-lines.ts:1700 — pdf-lines.educationRecords 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.
D1 · Cyclomatic Complexity · reactive-resume-v4-json.parseReactiveResumeV4JSON (cyclomatic 32) · ×1
  • reactive-resume-v4-json.parseReactiveResumeV4JSON (cyclomatic 32) packages/import/src/reactive-resume-v4-json.tsx:241 — reactive-resume-v4-json.parseReactiveResumeV4JSON has cyclomatic complexity 32 (threshold 15). Of this number, 16 points are the body's own statements and 16 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.
D1 · Cyclomatic Complexity · tree.buildItem (cyclomatic 32) · ×1
  • tree.buildItem (cyclomatic 32) packages/pdf/src/semantic/tree.ts:261 — tree.buildItem has cyclomatic complexity 32 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · store.createDraftStore.writeMetadata (cyclomatic 31) · ×1
  • store.createDraftStore.writeMetadata (cyclomatic 31) apps/mobile/src/data/draft/store.ts:581 — store.createDraftStore.writeMetadata has cyclomatic complexity 31 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · menu-screen.ResumeMenu (cyclomatic 31) · ×1
  • menu-screen.ResumeMenu (cyclomatic 31) apps/mobile/src/features/builder/menu/menu-screen.tsx:44 — menu-screen.ResumeMenu has cyclomatic complexity 31 (threshold 15). Most of this is not in the body itself: 14 of the 31 points are its own statements and the rest belongs to 6 function items inside it that branch (a function literal at line 114, a function literal at line 73, row, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · Recorder.Recorder (cyclomatic 31) · ×1
  • Recorder.Recorder (cyclomatic 31) apps/mobile/src/features/workspace/Recorder.tsx:43 — Recorder.Recorder has cyclomatic complexity 31 (threshold 15). Of this number, 24 points are the body's own statements and 7 belong to 6 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · BottomSheet.BottomSheet (cyclomatic 31) · ×1
  • BottomSheet.BottomSheet (cyclomatic 31) apps/mobile/src/ui/BottomSheet.tsx:125 — BottomSheet.BottomSheet has cyclomatic complexity 31 (threshold 15). Most of this is not in the body itself: 11 of the 31 points are its own statements and the rest belongs to 12 function items inside it that branch (a function literal at line 174, finish, requestClose, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · today.SchedulesPanel (cyclomatic 31) · ×1
  • today.SchedulesPanel (cyclomatic 31) apps/web/src/features/career/today.tsx:1105 — today.SchedulesPanel has cyclomatic complexity 31 (threshold 15). Most of this is not in the body itself: 4 of the 31 points are its own statements and the rest belongs to 8 function items inside it that branch (status, a function literal at line 1222, a function literal at line 1115, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · issues.describeFinding (cyclomatic 31) · ×1
  • issues.describeFinding (cyclomatic 31) apps/web/src/features/resume/editor/check/issues.ts:117 — issues.describeFinding has cyclomatic complexity 31 (threshold 15). Of this number, 25 points are the body's own statements and 6 belong to 3 function literals inside it that branch. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
D1 · Cyclomatic Complexity · dates-field.DatesField (cyclomatic 31) · ×1
  • dates-field.DatesField (cyclomatic 31) apps/web/src/features/resume/editor/write/dates-field.tsx:114 — dates-field.DatesField has cyclomatic complexity 31 (threshold 15). Of this number, 28 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.
D1 · Cyclomatic Complexity · editor.StylesheetCodeEditor (cyclomatic 31) · ×1
  • editor.StylesheetCodeEditor (cyclomatic 31) apps/web/src/features/resume/stylesheet/editor.tsx:130 — editor.StylesheetCodeEditor has cyclomatic complexity 31 (threshold 15). Most of this is not in the body itself: 3 of the 31 points are its own statements and the rest belongs to 10 function items inside it that branch (updateColor, a function literal at line 207, a function literal at line 319, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · error-message.getReadableErrorMessage (cyclomatic 31) · ×1
  • error-message.getReadableErrorMessage (cyclomatic 31) apps/web/src/libs/error-message.ts:24 — error-message.getReadableErrorMessage has cyclomatic complexity 31 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · write-panel.BodySection (cyclomatic 31) · ×1
  • write-panel.BodySection (cyclomatic 31) apps/web/src/routes/builder/letter/-components/write-panel.tsx:755 — write-panel.BodySection has cyclomatic complexity 31 (threshold 15). Of this number, 18 points are the body's own statements and 13 belong to 2 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · proposal-applications.saveProposalApplications (cyclomatic 31) · ×1
  • proposal-applications.saveProposalApplications (cyclomatic 31) packages/api/src/features/agent/proposal-applications.ts:126 — proposal-applications.saveProposalApplications has cyclomatic complexity 31 (threshold 15). Of this number, 30 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · tree.partMatchesOwner (cyclomatic 31) · ×1
  • tree.partMatchesOwner (cyclomatic 31) packages/pdf/src/semantic/tree.ts:688 — tree.partMatchesOwner has cyclomatic complexity 31 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · resume.PublicResumeScreen (cyclomatic 30) · ×1
  • resume.PublicResumeScreen (cyclomatic 30) apps/mobile/src/features/public/resume.tsx:26 — resume.PublicResumeScreen has cyclomatic complexity 30 (threshold 15). Of this number, 20 points are the body's own statements and 10 belong to 4 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · messages.ReplyCard (cyclomatic 30) · ×1
  • messages.ReplyCard (cyclomatic 30) apps/web/src/features/career/workspace/messages.tsx:380 — messages.ReplyCard has cyclomatic complexity 30 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators. This shape REPEATS in the file: one other method here (messages.ReplyCard::copy) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D1 · Cyclomatic Complexity · preferences.PreferencesForm (cyclomatic 30) · ×1
  • preferences.PreferencesForm (cyclomatic 30) apps/web/src/features/career/knowledge/preferences.tsx:84 — preferences.PreferencesForm has cyclomatic complexity 30 (threshold 15). Of this number, 21 points are the body's own statements and 9 belong to 8 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · files.isValidFontFile (cyclomatic 30) · ×1
  • files.isValidFontFile (cyclomatic 30) packages/fonts/src/files.ts:95 — files.isValidFontFile has cyclomatic complexity 30 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · pdf-lines.bodyColumns (cyclomatic 30) · ×1
  • pdf-lines.bodyColumns (cyclomatic 30) packages/import/src/pdf-lines.ts:784 — pdf-lines.bodyColumns has cyclomatic complexity 30 (threshold 15). Of this number, 17 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.
D1 · Cyclomatic Complexity · operators.summarizePageOperators (cyclomatic 30) · ×1
  • operators.summarizePageOperators (cyclomatic 30) packages/resume/src/ats-pdf/analyze/operators.ts:111 — operators.summarizePageOperators has cyclomatic complexity 30 (threshold 15). Of this number, 29 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · check.checkDocs (cyclomatic 30) · ×1
  • check.checkDocs (cyclomatic 30) tooling/docs/check.mjs:28 — check.checkDocs has cyclomatic complexity 30 (threshold 15). Of this number, 25 points are the body's own statements and 5 belong to 3 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · ai-consent.authorizeAiRequest.result (cyclomatic 29) · ×1
  • ai-consent.authorizeAiRequest.result (cyclomatic 29) apps/mobile/src/api/ai-consent.ts:203 — ai-consent.authorizeAiRequest.result has cyclomatic complexity 29 (threshold 15). Of this number, 27 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · FitScreen.FitScreen (cyclomatic 29) · ×1
  • FitScreen.FitScreen (cyclomatic 29) apps/mobile/src/features/workspace/FitScreen.tsx:45 — FitScreen.FitScreen has cyclomatic complexity 29 (threshold 15). Of this number, 20 points are the body's own statements and 9 belong to 2 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · BoardDrag.BoardDrag (cyclomatic 29) · ×1
  • BoardDrag.BoardDrag (cyclomatic 29) apps/mobile/src/ui/BoardDrag.tsx:85 — BoardDrag.BoardDrag has cyclomatic complexity 29 (threshold 15). Most of this is not in the body itself: 2 of the 29 points are its own statements and the rest belongs to 10 function items inside it that branch (a function literal at line 209, drop, lift, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · providers.EditProviderForm (cyclomatic 29) · ×1
  • providers.EditProviderForm (cyclomatic 29) apps/web/src/features/settings/ai/providers.tsx:643 — providers.EditProviderForm has cyclomatic complexity 29 (threshold 15). Of this number, 21 points are the body's own statements and 8 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.
D1 · Cyclomatic Complexity · config.linkAnonymousAccount (cyclomatic 29) · ×1
  • config.linkAnonymousAccount (cyclomatic 29) packages/auth/src/config.ts:361 — config.linkAnonymousAccount has cyclomatic complexity 29 (threshold 15). Most of this is not in the body itself: 3 of the 29 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 370, 534, 557). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D1 · Cyclomatic Complexity · builder.buildDocument (cyclomatic 29) · ×1
  • builder.buildDocument (cyclomatic 29) packages/docx/src/builder.ts:286 — builder.buildDocument has cyclomatic complexity 29 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · extract.findGutter (cyclomatic 29) · ×1
  • extract.findGutter (cyclomatic 29) packages/resume/src/ats-pdf/extract.ts:246 — extract.findGutter has cyclomatic complexity 29 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · generator.generateOpenApiSpec (cyclomatic 28) · ×1
  • generator.generateOpenApiSpec (cyclomatic 28) apps/server/src/openapi/generator.ts:126 — generator.generateOpenApiSpec has cyclomatic complexity 28 (threshold 15). Of this number, 23 points are the body's own statements and 5 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.
D1 · Cyclomatic Complexity · combobox.Combobox (cyclomatic 28) · ×1
  • combobox.Combobox (cyclomatic 28) apps/web/src/components/ui/combobox.tsx:88 — combobox.Combobox has cyclomatic complexity 28 (threshold 15). Of this number, 14 points are the body's own statements and 14 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.
D1 · Cyclomatic Complexity · use-application-actions.useMoveWithUndo.<returned closure> (cyclomatic 28) · ×1
  • use-application-actions.useMoveWithUndo.<returned closure> (cyclomatic 28) apps/web/src/features/applications/use-application-actions.ts:74 — use-application-actions.useMoveWithUndo.<returned closure> 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 10 function items inside it that branch (a function literal at line 148, showsMove, restore, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · calendar-view.ApplicationCalendar (cyclomatic 28) · ×1
  • calendar-view.ApplicationCalendar (cyclomatic 28) apps/web/src/features/applications/components/calendar-view.tsx:47 — calendar-view.ApplicationCalendar has cyclomatic complexity 28 (threshold 15). Of this number, 23 points are the body's own statements and 5 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.
D1 · Cyclomatic Complexity · manage-lanes-sheet.ManageLanesSheet (cyclomatic 28) · ×1
  • manage-lanes-sheet.ManageLanesSheet (cyclomatic 28) apps/web/src/features/applications/components/manage-lanes-sheet.tsx:65 — manage-lanes-sheet.ManageLanesSheet has cyclomatic complexity 28 (threshold 15). Most of this is not in the body itself: 13 of the 28 points are its own statements and the rest belongs to 7 function items inside it that branch (reorder, a function literal at line 72, a function literal at line 93, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · question-card.QuestionCard (cyclomatic 28) · ×1
  • question-card.QuestionCard (cyclomatic 28) apps/web/src/features/assistant/question-card.tsx:25 — question-card.QuestionCard has cyclomatic complexity 28 (threshold 15). Of this number, 23 points are the body's own statements and 5 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.
D1 · Cyclomatic Complexity · debrief.DebriefTab (cyclomatic 28) · ×1
  • debrief.DebriefTab (cyclomatic 28) apps/web/src/features/career/workspace/debrief.tsx:56 — debrief.DebriefTab has cyclomatic complexity 28 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · chrome.usePageScale (cyclomatic 28) · ×1
  • chrome.usePageScale (cyclomatic 28) apps/web/src/features/resume/editor/chrome.tsx:84 — chrome.usePageScale 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 119, 196, 115, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D1 · Cyclomatic Complexity · editor.StylesheetEditorShell (cyclomatic 28) · ×1
  • editor.StylesheetEditorShell (cyclomatic 28) apps/web/src/features/resume/stylesheet/editor.tsx:390 — editor.StylesheetEditorShell 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 8 function items inside it that branch (highlightRuleAt, a function literal at line 429, a function literal at line 427, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · letter-bar.LetterSaveStatus (cyclomatic 28) · ×1
  • letter-bar.LetterSaveStatus (cyclomatic 28) apps/web/src/routes/builder/letter/-components/letter-bar.tsx:257 — letter-bar.LetterSaveStatus has cyclomatic complexity 28 (threshold 15). Of this number, 23 points are the body's own statements and 5 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.
D1 · Cyclomatic Complexity · pdf-lines.foldStackedHeaders (cyclomatic 28) · ×1
  • pdf-lines.foldStackedHeaders (cyclomatic 28) packages/import/src/pdf-lines.ts:1063 — pdf-lines.foldStackedHeaders has cyclomatic complexity 28 (threshold 15). Of this number, 25 points are the body's own statements and 3 belong to 3 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · next-step.getNextStep (cyclomatic 28) · ×1
  • next-step.getNextStep (cyclomatic 28) packages/schema/src/applications/next-step.ts:76 — next-step.getNextStep has cyclomatic complexity 28 (threshold 15). Of this number, 22 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.
D1 · Cyclomatic Complexity · ReorderList.ReorderList (cyclomatic 27) · ×1
  • ReorderList.ReorderList (cyclomatic 27) apps/mobile/src/ui/ReorderList.tsx:89 — ReorderList.ReorderList has cyclomatic complexity 27 (threshold 15). Most of this is not in the body itself: 1 of the 27 points is its own statement and the rest belongs to 8 function items inside it that branch (drop, a function literal at line 182, moveBy, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · rows.ListRow (cyclomatic 27) · ×1
  • rows.ListRow (cyclomatic 27) apps/mobile/src/ui/rows.tsx:223 — rows.ListRow has cyclomatic complexity 27 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · rich-text-markup.hasUnsupportedTableMarkup (cyclomatic 27) · ×1
  • rich-text-markup.hasUnsupportedTableMarkup (cyclomatic 27) apps/web/src/components/input/rich-text-markup.ts:373 — rich-text-markup.hasUnsupportedTableMarkup has cyclomatic complexity 27 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · next-step.describeNextStep (cyclomatic 27) · ×1
  • next-step.describeNextStep (cyclomatic 27) apps/web/src/features/applications/next-step.ts:47 — next-step.describeNextStep has cyclomatic complexity 27 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · use-application-actions.useApplicationActions (cyclomatic 27) · ×1
  • use-application-actions.useApplicationActions (cyclomatic 27) apps/web/src/features/applications/use-application-actions.ts:230 — use-application-actions.useApplicationActions has cyclomatic complexity 27 (threshold 15). Most of this is not in the body itself: 1 of the 27 points is its own statement and the rest belongs to 5 function literals inside it that branch (lines 275, 240, 256, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D1 · Cyclomatic Complexity · providers.ProviderRow (cyclomatic 27) · ×1
  • providers.ProviderRow (cyclomatic 27) apps/web/src/features/settings/ai/providers.tsx:278 — providers.ProviderRow has cyclomatic complexity 27 (threshold 15). Of this number, 25 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.
D1 · Cyclomatic Complexity · document.resolveResumeEdits (cyclomatic 27) · ×1
  • document.resolveResumeEdits (cyclomatic 27) packages/api/src/features/agent/document.ts:548 — document.resolveResumeEdits has cyclomatic complexity 27 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · messages-merge.mergeClientToolResponses (cyclomatic 27) · ×1
  • messages-merge.mergeClientToolResponses (cyclomatic 27) packages/api/src/features/agent/messages-merge.ts:57 — messages-merge.mergeClientToolResponses has cyclomatic complexity 27 (threshold 15). Most of this is not in the body itself: 8 of the 27 points are its own statements and the rest belongs to one function literal inside it that branches (line 90). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
D1 · Cyclomatic Complexity · draft.draftLetterBody (cyclomatic 27) · ×1
  • draft.draftLetterBody (cyclomatic 27) packages/api/src/features/cover-letters/draft.ts:64 — draft.draftLetterBody has cyclomatic complexity 27 (threshold 15). 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, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · pdf-lines.pageToLines (cyclomatic 27) · ×1
  • pdf-lines.pageToLines (cyclomatic 27) packages/import/src/pdf-lines.ts:885 — pdf-lines.pageToLines has cyclomatic complexity 27 (threshold 15). Of this number, 19 points are the body's own statements and 8 belong to 4 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · pdf-lines.readIdentity (cyclomatic 27) · ×1
  • pdf-lines.readIdentity (cyclomatic 27) packages/import/src/pdf-lines.ts:1547 — pdf-lines.readIdentity has cyclomatic complexity 27 (threshold 15). Of this number, 19 points are the body's own statements and 8 belong to 6 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · values.compileProgram · ×1
  • values.compileProgram::compileRule (cyclomatic 27) packages/resume/src/stylesheet/values.ts:554 — values.compileProgram::compileRule has cyclomatic complexity 27 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · BasicsScreen.BasicsScreen (cyclomatic 26) · ×1
  • BasicsScreen.BasicsScreen (cyclomatic 26) apps/mobile/src/features/builder/basics/BasicsScreen.tsx:73 — BasicsScreen.BasicsScreen has cyclomatic complexity 26 (threshold 15). Of this number, 14 points are the body's own statements and 12 belong to 3 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · list-view.ApplicationRow (cyclomatic 26) · ×1
  • list-view.ApplicationRow (cyclomatic 26) apps/web/src/features/applications/components/list-view.tsx:345 — list-view.ApplicationRow has cyclomatic complexity 26 (threshold 15). Of this number, 19 points are the body's own statements and 7 belong to one function literal inside it that branches. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · manage-lanes-sheet.LaneRow (cyclomatic 26) · ×1
  • manage-lanes-sheet.LaneRow (cyclomatic 26) apps/web/src/features/applications/components/manage-lanes-sheet.tsx:277 — manage-lanes-sheet.LaneRow has cyclomatic complexity 26 (threshold 15). Of this number, 13 points are the body's own statements and 13 belong to 4 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · conversation.MessageView (cyclomatic 26) · ×1
  • conversation.MessageView (cyclomatic 26) apps/web/src/features/assistant/conversation.tsx:555 — conversation.MessageView has cyclomatic complexity 26 (threshold 15). Of this number, 16 points are the body's own statements and 10 belong to 4 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · verify-2fa.TwoFactorVerificationPage (cyclomatic 26) · ×1
  • verify-2fa.TwoFactorVerificationPage (cyclomatic 26) apps/web/src/features/auth/pages/verify-2fa.tsx:39 — verify-2fa.TwoFactorVerificationPage has cyclomatic complexity 26 (threshold 15). Most of this is not in the body itself: 6 of the 26 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 51, 130, 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.
D1 · Cyclomatic Complexity · fit.RequirementRow (cyclomatic 26) · ×1
  • fit.RequirementRow (cyclomatic 26) apps/web/src/features/career/workspace/fit.tsx:502 — fit.RequirementRow has cyclomatic complexity 26 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · role-suggestions.SuggestRoles (cyclomatic 26) · ×1
  • role-suggestions.SuggestRoles (cyclomatic 26) apps/web/src/features/career/role-suggestions.tsx:63 — role-suggestions.SuggestRoles has cyclomatic complexity 26 (threshold 15). Of this number, 21 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.
D1 · Cyclomatic Complexity · resumes.RootMatches (cyclomatic 26) · ×1
  • resumes.RootMatches (cyclomatic 26) apps/web/src/features/command-palette/pages/resumes.tsx:99 — resumes.RootMatches has cyclomatic complexity 26 (threshold 15). Of this number, 23 points are the body's own statements and 3 belong to 2 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · page-layer.CheckPageLayer (cyclomatic 26) · ×1
  • page-layer.CheckPageLayer (cyclomatic 26) apps/web/src/features/resume/editor/check/page-layer.tsx:97 — page-layer.CheckPageLayer 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 5 function items inside it that branch (a function literal at line 132, 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.
D1 · Cyclomatic Complexity · root-context.loadRootContext (cyclomatic 26) · ×1
  • root-context.loadRootContext (cyclomatic 26) apps/web/src/libs/root-context.ts:29 — root-context.loadRootContext has cyclomatic complexity 26 (threshold 15). Of this number, 19 points are the body's own statements and 7 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.
D1 · Cyclomatic Complexity · lanes.resolveApplicationTransition (cyclomatic 26) · ×1
  • lanes.resolveApplicationTransition (cyclomatic 26) packages/api/src/features/applications/lanes.ts:41 — lanes.resolveApplicationTransition has cyclomatic complexity 26 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · export-uploads.exportAccountUploads · ×1
  • export-uploads.exportAccountUploads::visit (cyclomatic 26) packages/api/src/features/auth/export-uploads.ts:22 — export-uploads.exportAccountUploads::visit has cyclomatic complexity 26 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · parity.registerParityTools (cyclomatic 26) · ×1
  • parity.registerParityTools (cyclomatic 26) packages/mcp/src/parity.ts:394 — parity.registerParityTools has cyclomatic complexity 26 (threshold 15). Most of this is not in the body itself: 5 of the 26 points are its own statements and the rest belongs to one function literal inside it that branches (line 414). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
D1 · Cyclomatic Complexity · SectionScreen.SectionScreen (cyclomatic 25) · ×1
  • SectionScreen.SectionScreen (cyclomatic 25) apps/mobile/src/features/builder/section/SectionScreen.tsx:115 — SectionScreen.SectionScreen 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, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · web-page-screen.WebPageScreen (cyclomatic 25) · ×1
  • web-page-screen.WebPageScreen (cyclomatic 25) apps/mobile/src/features/builder/share/web-page-screen.tsx:25 — web-page-screen.WebPageScreen has cyclomatic complexity 25 (threshold 15). Of this number, 13 points are the body's own statements and 12 belong to 7 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · AIScreen.AIScreen (cyclomatic 25) · ×1
  • AIScreen.AIScreen (cyclomatic 25) apps/mobile/src/features/settings/AIScreen.tsx:33 — AIScreen.AIScreen has cyclomatic complexity 25 (threshold 15). Most of this is not in the body itself: 9 of the 25 points are its own statements and the rest belongs to 2 function items inside it that branch (a function literal at line 78, testAgain). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · stage-stepper.StageStepper (cyclomatic 25) · ×1
  • stage-stepper.StageStepper (cyclomatic 25) apps/web/src/components/calm/stage-stepper.tsx:54 — stage-stepper.StageStepper has cyclomatic complexity 25 (threshold 15). Most of this is not in the body itself: 1 of the 25 points is its own statement and the rest belongs to one function literal inside it that branches (line 67). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
D1 · Cyclomatic Complexity · application-form-sheet.toPayload (cyclomatic 25) · ×1
  • application-form-sheet.toPayload (cyclomatic 25) apps/web/src/features/applications/components/application-form-sheet.tsx:101 — application-form-sheet.toPayload 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.
D1 · Cyclomatic Complexity · outline.SectionRowBody (cyclomatic 25) · ×1
  • outline.SectionRowBody (cyclomatic 25) apps/web/src/features/resume/editor/write/outline.tsx:282 — outline.SectionRowBody has cyclomatic complexity 25 (threshold 15). Of this number, 20 points are the body's own statements and 5 belong to 2 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · service.submitAnswerSnapshot (cyclomatic 25) · ×1
  • service.submitAnswerSnapshot (cyclomatic 25) packages/api/src/features/career/service.ts:376 — service.submitAnswerSnapshot has cyclomatic complexity 25 (threshold 15). Of this number, 23 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · tools.buildCareerTools (cyclomatic 25) · ×1
  • tools.buildCareerTools (cyclomatic 25) packages/api/src/features/career/tools.ts:112 — tools.buildCareerTools has cyclomatic complexity 25 (threshold 15). Of this number, 16 points are the body's own statements and 9 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.
D1 · Cyclomatic Complexity · legacy-converter.activeSlotChunks (cyclomatic 25) · ×1
  • legacy-converter.activeSlotChunks (cyclomatic 25) packages/pdf/src/semantic/legacy-converter.ts:177 — legacy-converter.activeSlotChunks 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.
D1 · Cyclomatic Complexity · selector.compileSimple (cyclomatic 25) · ×1
  • selector.compileSimple (cyclomatic 25) packages/resume/src/stylesheet/selector.ts:179 — selector.compileSimple 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.
D1 · Cyclomatic Complexity · cascade.structuralValue (cyclomatic 25) · ×1
  • cascade.structuralValue (cyclomatic 25) packages/resume/src/stylesheet/cascade.ts:504 — cascade.structuralValue 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.
D1 · Cyclomatic Complexity · account-zip.buildAccountZip (cyclomatic 25) · ×1
  • account-zip.buildAccountZip (cyclomatic 25) packages/utils/src/account-zip.ts:72 — account-zip.buildAccountZip has cyclomatic complexity 25 (threshold 15). Of this number, 21 points are the body's own statements and 4 belong to 2 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · activity-screen.ActivityScreen (cyclomatic 24) · ×1
  • activity-screen.ActivityScreen (cyclomatic 24) apps/mobile/src/features/builder/share/activity-screen.tsx:36 — activity-screen.ActivityScreen has cyclomatic complexity 24 (threshold 15). Of this number, 17 points are the body's own statements and 7 belong to 4 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · enable-two-factor.EnableTwoFactorDialog (cyclomatic 24) · ×1
  • enable-two-factor.EnableTwoFactorDialog (cyclomatic 24) apps/web/src/dialogs/auth/enable-two-factor.tsx:55 — enable-two-factor.EnableTwoFactorDialog has cyclomatic complexity 24 (threshold 15). Most of this is not in the body itself: 4 of the 24 points are its own statements and the rest belongs to 12 function items inside it that branch (a function literal at line 146, a function literal at line 257, a function literal at line 68, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · checker.Result (cyclomatic 24) · ×1
  • checker.Result (cyclomatic 24) apps/web/src/features/ats-checker/checker.tsx:397 — checker.Result has cyclomatic complexity 24 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · debrief.DebriefForm (cyclomatic 24) · ×1
  • debrief.DebriefForm (cyclomatic 24) apps/web/src/features/career/workspace/debrief.tsx:208 — debrief.DebriefForm has cyclomatic complexity 24 (threshold 15). Of this number, 13 points are the body's own statements and 11 belong to 6 function items inside it that branch. To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
D1 · Cyclomatic Complexity · read-file.detectImportKind (cyclomatic 24) · ×1
  • read-file.detectImportKind (cyclomatic 24) apps/web/src/features/resume/import/read-file.ts:59 — read-file.detectImportKind 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.
D1 · Cyclomatic Complexity · resume-reflow.EntryView (cyclomatic 24) · ×1
  • resume-reflow.EntryView (cyclomatic 24) apps/web/src/features/resume/preview/resume-reflow.tsx:46 — resume-reflow.EntryView has cyclomatic complexity 24 (threshold 15). Of this number, 21 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.
D1 · Cyclomatic Complexity · address-field.AddressField (cyclomatic 24) · ×1
  • address-field.AddressField (cyclomatic 24) apps/web/src/features/resume/share/address-field.tsx:64 — address-field.AddressField has cyclomatic complexity 24 (threshold 15). Of this number, 18 points are the body's own statements and 6 belong to one function item inside it that branches. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · write-panel.DraftBox (cyclomatic 24) · ×1
  • write-panel.DraftBox (cyclomatic 24) apps/web/src/routes/builder/letter/-components/write-panel.tsx:1047 — write-panel.DraftBox has cyclomatic complexity 24 (threshold 15). Of this number, 23 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · messages-persistence.applyStepToUiMessage (cyclomatic 24) · ×1
  • messages-persistence.applyStepToUiMessage (cyclomatic 24) packages/api/src/features/agent/messages-persistence.ts:168 — messages-persistence.applyStepToUiMessage has cyclomatic complexity 24 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · service.recordSentResume (cyclomatic 24) · ×1
  • service.recordSentResume (cyclomatic 24) packages/api/src/features/applications/service.ts:243 — service.recordSentResume 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.
D1 · Cyclomatic Complexity · packet.snapshot (cyclomatic 24) · ×1
  • packet.snapshot (cyclomatic 24) packages/api/src/features/applications/packet.ts:33 — packet.snapshot has cyclomatic complexity 24 (threshold 15). Of this number, 21 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.
D1 · Cyclomatic Complexity · tools.registerTools (cyclomatic 24) · ×1
  • tools.registerTools (cyclomatic 24) packages/mcp/src/tools.ts:80 — tools.registerTools 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 10 function literals inside it that branch (lines 173, 151, 276, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D1 · Cyclomatic Complexity · picture-shadow.getPictureShadow (cyclomatic 24) · ×1
  • picture-shadow.getPictureShadow (cyclomatic 24) packages/pdf/src/templates/shared/picture-shadow.ts:43 — picture-shadow.getPictureShadow has cyclomatic complexity 24 (threshold 15). Of this number, 21 points are the body's own statements and 3 belong to one function item 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.
D1 · Cyclomatic Complexity · images.node.readServerImage (cyclomatic 24) · ×1
  • images.node.readServerImage (cyclomatic 24) packages/pdf/src/forme/images.node.ts:13 — images.node.readServerImage 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.
D1 · Cyclomatic Complexity · content.captureDocument · ×1
  • content.captureDocument::visit (cyclomatic 24) tooling/capture/content.ts:25 — content.captureDocument::visit has cyclomatic complexity 24 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · ApplyScreen.ApplyScreen (cyclomatic 23) · ×1
  • ApplyScreen.ApplyScreen (cyclomatic 23) apps/mobile/src/features/workspace/ApplyScreen.tsx:33 — ApplyScreen.ApplyScreen 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.
D1 · Cyclomatic Complexity · uploads.handleUpload (cyclomatic 23) · ×1
  • uploads.handleUpload (cyclomatic 23) apps/server/src/static/uploads.ts:12 — uploads.handleUpload 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.
D1 · Cyclomatic Complexity · next-step-card.NextStepCard (cyclomatic 23) · ×1
  • next-step-card.NextStepCard (cyclomatic 23) apps/web/src/features/applications/components/detail/next-step-card.tsx:49 — next-step-card.NextStepCard has cyclomatic complexity 23 (threshold 15). Of this number, 16 points are the body's own statements and 7 belong to one function item inside it that branches. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · prepare.Plan (cyclomatic 23) · ×1
  • prepare.Plan (cyclomatic 23) apps/web/src/features/career/workspace/prepare.tsx:411 — prepare.Plan has cyclomatic complexity 23 (threshold 15). Of this number, 14 points are the body's own statements and 9 belong to 3 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · stories.StoriesPage (cyclomatic 23) · ×1
  • stories.StoriesPage (cyclomatic 23) apps/web/src/features/career/knowledge/stories.tsx:77 — stories.StoriesPage has cyclomatic complexity 23 (threshold 15). Of this number, 22 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · coach-thread.Composer (cyclomatic 23) · ×1
  • coach-thread.Composer (cyclomatic 23) apps/web/src/features/career/coach-thread.tsx:348 — coach-thread.Composer 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 5 function items inside it that branch (submit, upload, a function literal at line 443, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · schedule-sheet.ScheduleSheet · ×1
  • schedule-sheet.ScheduleSheet::onSave (cyclomatic 23) apps/web/src/features/career/schedule-sheet.tsx:241 — schedule-sheet.ScheduleSheet::onSave 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. This shape REPEATS in the file: one other method here (schedule-sheet.ScheduleSheet) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D1 · Cyclomatic Complexity · proposal-list.changeParts (cyclomatic 23) · ×1
  • proposal-list.changeParts (cyclomatic 23) apps/web/src/features/resume/editor/proposals/proposal-list.tsx:57 — proposal-list.changeParts has cyclomatic complexity 23 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · profile.ProfileSection (cyclomatic 23) · ×1
  • profile.ProfileSection (cyclomatic 23) apps/web/src/features/settings/account/profile.tsx:220 — profile.ProfileSection 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 8 function items inside it that branch (confirmUsername, changeEmail, updateUser, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · design-panel.LetterDesignPanel (cyclomatic 23) · ×1
  • design-panel.LetterDesignPanel (cyclomatic 23) apps/web/src/routes/builder/letter/-components/design-panel.tsx:70 — design-panel.LetterDesignPanel 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, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · service.searchWeb (cyclomatic 23) · ×1
  • service.searchWeb (cyclomatic 23) packages/api/src/features/web-access/service.ts:119 — service.searchWeb has cyclomatic complexity 23 (threshold 15). Most of this is not in the body itself: 10 of the 23 points are its own statements and the rest belongs to 4 function items inside it that branch (search, rememberFailure, a function literal at line 160, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · context.projectDocumentResults (cyclomatic 23) · ×1
  • context.projectDocumentResults (cyclomatic 23) packages/api/src/features/agent/context.ts:80 — context.projectDocumentResults 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 4 function literals inside it that branch (lines 84, 101, 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.
D1 · Cyclomatic Complexity · context.collapseOldestToolPairs (cyclomatic 23) · ×1
  • context.collapseOldestToolPairs (cyclomatic 23) packages/api/src/features/agent/context.ts:211 — context.collapseOldestToolPairs has cyclomatic complexity 23 (threshold 15). Of this number, 16 points are the body's own statements and 7 belong to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · level.parseLevel (cyclomatic 23) · ×1
  • level.parseLevel (cyclomatic 23) packages/import/src/level.ts:6 — level.parseLevel 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.
D1 · Cyclomatic Complexity · linkedin.parseLinkedInExport (cyclomatic 23) · ×1
  • linkedin.parseLinkedInExport (cyclomatic 23) packages/import/src/linkedin.ts:168 — linkedin.parseLinkedInExport has cyclomatic complexity 23 (threshold 15). Of this number, 22 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · pdf-lines.parseGeometryResume (cyclomatic 23) · ×1
  • pdf-lines.parseGeometryResume (cyclomatic 23) packages/import/src/pdf-lines.ts:1988 — pdf-lines.parseGeometryResume has cyclomatic complexity 23 (threshold 15). Of this number, 17 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.
D1 · Cyclomatic Complexity · level-display.LevelDisplay (cyclomatic 23) · ×1
  • level-display.LevelDisplay (cyclomatic 23) packages/pdf/src/templates/shared/level-display.tsx:26 — level-display.LevelDisplay has cyclomatic complexity 23 (threshold 15). Most of this is not in the body itself: 10 of the 23 points are its own statements and the rest belongs to one function literal inside it that branches (line 69). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
D1 · Cyclomatic Complexity · import.readImportFile (cyclomatic 22) · ×1
  • import.readImportFile (cyclomatic 22) apps/mobile/src/data/import.ts:93 — import.readImportFile has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · harness.collectDump (cyclomatic 22) · ×1
  • harness.collectDump (cyclomatic 22) apps/mobile/src/dev/storyboard/harness.tsx:261 — harness.collectDump 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 8 function literals inside it that branch (lines 289, 283, 280, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D1 · Cyclomatic Complexity · download-screen.ExportContent (cyclomatic 22) · ×1
  • download-screen.ExportContent (cyclomatic 22) apps/mobile/src/features/builder/download/download-screen.tsx:32 — download-screen.ExportContent 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. This shape REPEATS in the file: one other method here (download-screen.ExportContent::exportFile) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D1 · Cyclomatic Complexity · versions-screen.VersionsScreen (cyclomatic 22) · ×1
  • versions-screen.VersionsScreen (cyclomatic 22) apps/mobile/src/features/builder/versions/versions-screen.tsx:33 — versions-screen.VersionsScreen has cyclomatic complexity 22 (threshold 15). Most of this is not in the body itself: 7 of the 22 points are its own statements and the rest belongs to 5 function items inside it that branch (a function literal at line 167, rename, sameDay, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · notifications.TodayNotifications (cyclomatic 22) · ×1
  • notifications.TodayNotifications (cyclomatic 22) apps/mobile/src/features/system/notifications.tsx:85 — notifications.TodayNotifications 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 7 function literals inside it that branch (lines 112, 93, 108, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D1 · Cyclomatic Complexity · PracticeScreen.PracticeScreen (cyclomatic 22) · ×1
  • PracticeScreen.PracticeScreen (cyclomatic 22) apps/mobile/src/features/workspace/PracticeScreen.tsx:30 — PracticeScreen.PracticeScreen has cyclomatic complexity 22 (threshold 15). Of this number, 20 points are the body's own statements and 2 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.
D1 · Cyclomatic Complexity · Toast.ToastView (cyclomatic 22) · ×1
  • Toast.ToastView (cyclomatic 22) apps/mobile/src/ui/Toast.tsx:149 — Toast.ToastView has cyclomatic complexity 22 (threshold 15). Most of this is not in the body itself: 7 of the 22 points are its own statements and the rest belongs to 7 function literals inside it that branch (lines 206, 175, 244, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D1 · Cyclomatic Complexity · ReorderList.Row (cyclomatic 22) · ×1
  • ReorderList.Row (cyclomatic 22) apps/mobile/src/ui/ReorderList.tsx:229 — ReorderList.Row has cyclomatic complexity 22 (threshold 15). Most of this is not in the body itself: 4 of the 22 points are its own statements and the rest belongs to 10 function items inside it that branch (a function literal at line 270, a function literal at line 279, a function literal at line 284, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · SwipeRow.SwipeRow (cyclomatic 22) · ×1
  • SwipeRow.SwipeRow (cyclomatic 22) apps/mobile/src/ui/SwipeRow.tsx:58 — SwipeRow.SwipeRow has cyclomatic complexity 22 (threshold 15). Most of this is not in the body itself: 5 of the 22 points are its own statements and the rest belongs to 7 function items inside it that branch (a function literal at line 79, a function literal at line 88, a function literal at line 111, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · next-step.describeNextStepLine (cyclomatic 22) · ×1
  • next-step.describeNextStepLine (cyclomatic 22) apps/web/src/features/applications/next-step.ts:193 — next-step.describeNextStepLine has cyclomatic complexity 22 (threshold 15). Of this number, 19 points are the body's own statements and 3 belong to 2 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · board.ApplicationBoard (cyclomatic 22) · ×1
  • board.ApplicationBoard (cyclomatic 22) apps/web/src/features/applications/components/board.tsx:60 — board.ApplicationBoard has cyclomatic complexity 22 (threshold 15). Of this number, 12 points are the body's own statements and 10 belong to 6 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · remember-message.RememberMessage (cyclomatic 22) · ×1
  • remember-message.RememberMessage (cyclomatic 22) apps/web/src/features/assistant/remember-message.tsx:24 — remember-message.RememberMessage 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 (save, a function literal at line 93, current). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · login.LoginPage (cyclomatic 22) · ×1
  • login.LoginPage (cyclomatic 22) apps/web/src/features/auth/pages/login.tsx:116 — login.LoginPage has cyclomatic complexity 22 (threshold 15). Of this number, 12 points are the body's own statements and 10 belong to 5 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · entry-row.EntryRow (cyclomatic 22) · ×1
  • entry-row.EntryRow (cyclomatic 22) apps/web/src/features/resume/editor/write/entry-row.tsx:84 — entry-row.EntryRow has cyclomatic complexity 22 (threshold 15). Of this number, 18 points are the body's own statements and 4 belong to one function item inside it that branches. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · share-panel.PrimaryRow (cyclomatic 22) · ×1
  • share-panel.PrimaryRow (cyclomatic 22) apps/web/src/features/resume/share/share-panel.tsx:490 — share-panel.PrimaryRow has cyclomatic complexity 22 (threshold 15). Of this number, 19 points are the body's own statements and 3 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.
D1 · Cyclomatic Complexity · profile.EditableRow (cyclomatic 22) · ×1
  • profile.EditableRow (cyclomatic 22) apps/web/src/features/settings/account/profile.tsx:68 — profile.EditableRow has cyclomatic complexity 22 (threshold 15). Of this number, 12 points are the body's own statements and 10 belong to 3 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · security.Passkeys (cyclomatic 22) · ×1
  • security.Passkeys (cyclomatic 22) apps/web/src/features/settings/account/security.tsx:137 — security.Passkeys has cyclomatic complexity 22 (threshold 15). Of this number, 12 points are the body's own statements and 10 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.
D1 · Cyclomatic Complexity · app-shell.AppShell (cyclomatic 22) · ×1
  • app-shell.AppShell (cyclomatic 22) apps/web/src/routes/dashboard/-components/app-shell.tsx:141 — app-shell.AppShell has cyclomatic complexity 22 (threshold 15). Of this number, 11 points are the body's own statements and 11 belong to 6 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · translation.translationFields · ×1
  • translation.translationFields::visit (cyclomatic 22) packages/api/src/features/agent/translation.ts:80 — translation.translationFields::visit has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · sections.EducationSection (cyclomatic 22) · ×1
  • sections.EducationSection (cyclomatic 22) packages/pdf/src/templates/shared/sections.tsx:1290 — sections.EducationSection has cyclomatic complexity 22 (threshold 15). Most of this is not in the body itself: 2 of the 22 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 1339, 1391, 1310). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D1 · Cyclomatic Complexity · to-html.cssValue (cyclomatic 22) · ×1
  • to-html.cssValue (cyclomatic 22) packages/pdf/src/html/to-html.ts:92 — to-html.cssValue has cyclomatic complexity 22 (threshold 15). Of this number, 19 points are the body's own statements and 3 belong to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · markdown.resumeFactProposals (cyclomatic 22) · ×1
  • markdown.resumeFactProposals (cyclomatic 22) packages/resume/src/markdown.ts:50 — markdown.resumeFactProposals has cyclomatic complexity 22 (threshold 15). Of this number, 21 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · structural-proposals.fieldPath (cyclomatic 22) · ×1
  • structural-proposals.fieldPath (cyclomatic 22) packages/resume/src/structural-proposals.ts:85 — structural-proposals.fieldPath has cyclomatic complexity 22 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · css-escape.escapeCssIdentifier (cyclomatic 22) · ×1
  • css-escape.escapeCssIdentifier (cyclomatic 22) packages/resume/src/stylesheet/css-escape.ts:1 — css-escape.escapeCssIdentifier has cyclomatic complexity 22 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · queue.createWriteQueue.flush (cyclomatic 21) · ×1
  • queue.createWriteQueue.flush (cyclomatic 21) apps/mobile/src/data/queue.ts:144 — queue.createWriteQueue.flush 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 149, 162). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D1 · Cyclomatic Complexity · TemplateScreen.TemplateScreen (cyclomatic 21) · ×1
  • TemplateScreen.TemplateScreen (cyclomatic 21) apps/mobile/src/features/builder/design/TemplateScreen.tsx:45 — TemplateScreen.TemplateScreen has cyclomatic complexity 21 (threshold 15). Most of this is not in the body itself: 7 of the 21 points are its own statements and the rest belongs to 5 function items inside it that branch (a function literal at line 160, a function literal at line 57, apply, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · stories.StoryScreen (cyclomatic 21) · ×1
  • stories.StoryScreen (cyclomatic 21) apps/mobile/src/features/career/stories.tsx:56 — stories.StoryScreen 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 (a function literal at line 188, save, a function literal at line 141, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · list-row.ListRow (cyclomatic 21) · ×1
  • list-row.ListRow (cyclomatic 21) apps/web/src/components/calm/list-row.tsx:85 — list-row.ListRow has cyclomatic complexity 21 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · register.RegisterPage (cyclomatic 21) · ×1
  • register.RegisterPage (cyclomatic 21) apps/web/src/features/auth/pages/register.tsx:58 — register.RegisterPage has cyclomatic complexity 21 (threshold 15). 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: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · messages.ReplyCard · ×1
  • messages.ReplyCard::copy (cyclomatic 21) apps/web/src/features/career/workspace/messages.tsx:413 — messages.ReplyCard::copy has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This shape REPEATS in the file: one other method here (messages.ReplyCard) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D1 · Cyclomatic Complexity · prepare.PrepareTab (cyclomatic 21) · ×1
  • prepare.PrepareTab (cyclomatic 21) apps/web/src/features/career/workspace/prepare.tsx:50 — prepare.PrepareTab has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · facts.FactRow (cyclomatic 21) · ×1
  • facts.FactRow (cyclomatic 21) apps/web/src/features/career/knowledge/facts.tsx:556 — facts.FactRow has cyclomatic complexity 21 (threshold 15). Of this number, 19 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · content.CommandPaletteContent (cyclomatic 21) · ×1
  • content.CommandPaletteContent (cyclomatic 21) apps/web/src/features/command-palette/content.tsx:32 — content.CommandPaletteContent has cyclomatic complexity 21 (threshold 15). Of this number, 12 points are the body's own statements and 9 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.
D1 · Cyclomatic Complexity · document-card.DocumentCard (cyclomatic 21) · ×1
  • document-card.DocumentCard (cyclomatic 21) apps/web/src/features/documents/document-card.tsx:238 — document-card.DocumentCard has cyclomatic complexity 21 (threshold 15). Of this number, 19 points are the body's own statements and 2 belong to one function item inside it that branches. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · document-actions.LinkApplicationDialog (cyclomatic 21) · ×1
  • document-actions.LinkApplicationDialog (cyclomatic 21) apps/web/src/features/documents/document-actions.tsx:695 — document-actions.LinkApplicationDialog 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 3 function items inside it that branch (a function literal at line 767, choose, a function literal at line 736). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · prepare.Prepare (cyclomatic 21) · ×1
  • prepare.Prepare (cyclomatic 21) apps/web/src/features/homepage/prepare.tsx:502 — prepare.Prepare 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 629, 542, 586, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D1 · Cyclomatic Complexity · store.startLetterDraft (cyclomatic 21) · ×1
  • store.startLetterDraft (cyclomatic 21) apps/web/src/features/letters/store.ts:707 — store.startLetterDraft has cyclomatic complexity 21 (threshold 15). Of this number, 17 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.
D1 · Cyclomatic Complexity · draft.useResumeCleanup (cyclomatic 21) · ×1
  • draft.useResumeCleanup (cyclomatic 21) apps/web/src/features/resume/builder/draft.ts:1333 — draft.useResumeCleanup 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 7 function literals inside it that branch (lines 1355, 1388, 1339, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D1 · Cyclomatic Complexity · outline.Outline (cyclomatic 21) · ×1
  • outline.Outline (cyclomatic 21) apps/web/src/features/resume/editor/write/outline.tsx:106 — outline.Outline 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 4 function items inside it that branch (move, a function literal at line 154, onDragEnd, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · files.woffToSfnt (cyclomatic 21) · ×1
  • files.woffToSfnt (cyclomatic 21) packages/fonts/src/files.ts:6 — files.woffToSfnt has cyclomatic complexity 21 (threshold 15). Of this number, 17 points are the body's own statements and 4 belong to 2 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · html-to-odt.processBlock (cyclomatic 21) · ×1
  • html-to-odt.processBlock (cyclomatic 21) packages/odt/src/html-to-odt.ts:162 — html-to-odt.processBlock has cyclomatic complexity 21 (threshold 15). Of this number, 19 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · rich-text-keys.getRichTextSemanticKind (cyclomatic 21) · ×1
  • rich-text-keys.getRichTextSemanticKind (cyclomatic 21) packages/pdf/src/semantic/rich-text-keys.ts:19 — rich-text-keys.getRichTextSemanticKind has cyclomatic complexity 21 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · text.renderChildren (cyclomatic 21) · ×1
  • text.renderChildren (cyclomatic 21) packages/pdf/src/text.tsx:152 — text.renderChildren has cyclomatic complexity 21 (threshold 15). Most of this is not in the body itself: 5 of the 21 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 158, 175). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D1 · Cyclomatic Complexity · sections.ExperienceSection (cyclomatic 21) · ×1
  • sections.ExperienceSection (cyclomatic 21) packages/pdf/src/templates/shared/sections.tsx:1093 — sections.ExperienceSection has cyclomatic complexity 21 (threshold 15). Most of this is not in the body itself: 2 of the 21 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 1142, 1190, 1113, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D1 · Cyclomatic Complexity · merge.mergeIntoPreviousEntry (cyclomatic 21) · ×1
  • merge.mergeIntoPreviousEntry (cyclomatic 21) packages/resume/src/ats/merge.ts:34 — merge.mergeIntoPreviousEntry 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.
D1 · Cyclomatic Complexity · selector.matchesSimple (cyclomatic 21) · ×1
  • selector.matchesSimple (cyclomatic 21) packages/resume/src/stylesheet/selector.ts:368 — selector.matchesSimple has cyclomatic complexity 21 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
D1 · Cyclomatic Complexity · url-security.node.fetchPublic (cyclomatic 21) · ×1
  • url-security.node.fetchPublic (cyclomatic 21) packages/utils/src/url-security.node.ts:154 — url-security.node.fetchPublic 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 2 function literals inside it that branch (lines 174, 210). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D1 · Cyclomatic Complexity · PdfPagesModule.definition (cyclomatic 21) · ×1
  • PdfPagesModule.definition (cyclomatic 21) apps/mobile/modules/pdf-pages/ios/PdfPagesModule.swift:10 — PdfPagesModule.definition has cyclomatic complexity 21 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
D1 · Cyclomatic Complexity · store.createDraftStore.refresh (cyclomatic 20) · ×1
  • store.createDraftStore.refresh (cyclomatic 20) apps/mobile/src/data/draft/store.ts:647 — store.createDraftStore.refresh has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · notification-plan.notificationPlan (cyclomatic 20) · ×1
  • notification-plan.notificationPlan (cyclomatic 20) apps/mobile/src/data/notification-plan.ts:16 — notification-plan.notificationPlan 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.
D1 · Cyclomatic Complexity · capture.StoryboardController (cyclomatic 20) · ×1
  • capture.StoryboardController (cyclomatic 20) apps/mobile/src/dev/storyboard/capture.tsx:72 — capture.StoryboardController 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 96, 83, 87, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D1 · Cyclomatic Complexity · DetailScreen.NextStepHero (cyclomatic 20) · ×1
  • DetailScreen.NextStepHero (cyclomatic 20) apps/mobile/src/features/applications/DetailScreen.tsx:292 — DetailScreen.NextStepHero has cyclomatic complexity 20 (threshold 15). Of this number, 18 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · ProfileScreen.ProfileScreen (cyclomatic 20) · ×1
  • ProfileScreen.ProfileScreen (cyclomatic 20) apps/mobile/src/features/settings/ProfileScreen.tsx:19 — ProfileScreen.ProfileScreen has cyclomatic complexity 20 (threshold 15). Of this number, 10 points are the body's own statements and 10 belong to 4 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · attachment-preview.AttachmentPreview (cyclomatic 20) · ×1
  • attachment-preview.AttachmentPreview (cyclomatic 20) apps/web/src/features/applications/components/attachment-preview.tsx:12 — attachment-preview.AttachmentPreview has cyclomatic complexity 20 (threshold 15). Most of this is not in the body itself: 6 of the 20 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 39, 17, 26, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D1 · Cyclomatic Complexity · coach-chat.Proposal (cyclomatic 20) · ×1
  • coach-chat.Proposal (cyclomatic 20) apps/web/src/features/career/coach-chat.tsx:852 — coach-chat.Proposal has cyclomatic complexity 20 (threshold 15). Of this number, 12 points are the body's own statements and 8 belong to 5 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · offers.requirementsFor (cyclomatic 20) · ×1
  • offers.requirementsFor (cyclomatic 20) apps/web/src/features/career/offers.tsx:1027 — offers.requirementsFor 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.
D1 · Cyclomatic Complexity · offers.Questions (cyclomatic 20) · ×1
  • offers.Questions (cyclomatic 20) apps/web/src/features/career/offers.tsx:1167 — offers.Questions has cyclomatic complexity 20 (threshold 15). Of this number, 10 points are the body's own statements and 10 belong to 6 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · job-match.JobMatchTab (cyclomatic 20) · ×1
  • job-match.JobMatchTab (cyclomatic 20) apps/web/src/features/resume/editor/check/job-match.tsx:149 — job-match.JobMatchTab has cyclomatic complexity 20 (threshold 15). Of this number, 14 points are the body's own statements and 6 belong to 6 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · save-status.SaveStatus (cyclomatic 20) · ×1
  • save-status.SaveStatus (cyclomatic 20) apps/web/src/features/resume/editor/save-status.tsx:46 — save-status.SaveStatus has cyclomatic complexity 20 (threshold 15). Of this number, 18 points are the body's own statements and 2 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.
D1 · Cyclomatic Complexity · web-page.loadPublicWebPage (cyclomatic 20) · ×1
  • web-page.loadPublicWebPage (cyclomatic 20) packages/api/src/features/resume/web-page.ts:57 — web-page.loadPublicWebPage has cyclomatic complexity 20 (threshold 15). Of this number, 17 points are the body's own statements and 3 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.
D1 · Cyclomatic Complexity · render.listPaginationRepairs (cyclomatic 20) · ×1
  • render.listPaginationRepairs (cyclomatic 20) packages/pdf/src/forme/render.ts:275 — render.listPaginationRepairs has cyclomatic complexity 20 (threshold 15). Most of this is not in the body itself: 1 of the 20 points is its own statement and the rest belongs to 3 function literals inside it that branch (lines 283, 314, 282). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D1 · Cyclomatic Complexity · move-item.moveItem (cyclomatic 20) · ×1
  • move-item.moveItem (cyclomatic 20) packages/resume/src/move-item.ts:17 — move-item.moveItem 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.
D1 · Cyclomatic Complexity · string.fallbackGraphemes (cyclomatic 20) · ×1
  • string.fallbackGraphemes (cyclomatic 20) packages/utils/src/string.ts:146 — string.fallbackGraphemes has cyclomatic complexity 20 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · main (cyclomatic 20) · ×1
  • main (cyclomatic 20) tooling/ci/failed-logs.mjs:62 — main has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · consent.ensureApproved (cyclomatic 19) · ×1
  • consent.ensureApproved (cyclomatic 19) apps/mobile/src/data/consent.ts:63 — consent.ensureApproved has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 6 of the 19 points are its own statements and the rest belongs to one function literal inside it that branches (line 77). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
D1 · Cyclomatic Complexity · EntryActionsSheet.EntryActionsSheet (cyclomatic 19) · ×1
  • EntryActionsSheet.EntryActionsSheet (cyclomatic 19) apps/mobile/src/features/builder/entry/EntryActionsSheet.tsx:13 — EntryActionsSheet.EntryActionsSheet has cyclomatic complexity 19 (threshold 15). Of this number, 11 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.
D1 · Cyclomatic Complexity · ats.ATSCheckerScreen (cyclomatic 19) · ×1
  • ats.ATSCheckerScreen (cyclomatic 19) apps/mobile/src/features/public/ats.tsx:22 — ats.ATSCheckerScreen has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 9 of the 19 points are its own statements and the rest belongs to 2 function items inside it that branch (choose, a function literal at line 86). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · rich-input-whitespace.markPastedHtml · ×1
  • rich-input-whitespace.markPastedHtml::normalize (cyclomatic 19) apps/web/src/components/input/rich-input-whitespace.ts:56 — rich-input-whitespace.markPastedHtml::normalize has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · tool-approvals.ToolApprovals (cyclomatic 19) · ×1
  • tool-approvals.ToolApprovals (cyclomatic 19) apps/web/src/features/assistant/tool-approvals.tsx:39 — tool-approvals.ToolApprovals has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 1 of the 19 points is its own statement and the rest belongs to one function literal inside it that branches (line 48). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
D1 · Cyclomatic Complexity · prepare.PrepWithoutAi (cyclomatic 19) · ×1
  • prepare.PrepWithoutAi (cyclomatic 19) apps/web/src/features/career/workspace/prepare.tsx:194 — prepare.PrepWithoutAi has cyclomatic complexity 19 (threshold 15). Of this number, 10 points are the body's own statements and 9 belong to 5 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · facts.Correction (cyclomatic 19) · ×1
  • facts.Correction (cyclomatic 19) apps/web/src/features/career/knowledge/facts.tsx:700 — facts.Correction has cyclomatic complexity 19 (threshold 15). Of this number, 10 points are the body's own statements and 9 belong to one function item inside it that branches. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · today.ScheduleResults (cyclomatic 19) · ×1
  • today.ScheduleResults (cyclomatic 19) apps/web/src/features/career/today.tsx:501 — today.ScheduleResults has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 4 of the 19 points are its own statements and the rest belongs to 5 function items inside it that branch (detail, a function literal at line 575, title, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · ask.AccountAskCommandGroup (cyclomatic 19) · ×1
  • ask.AccountAskCommandGroup (cyclomatic 19) apps/web/src/features/command-palette/pages/ask.tsx:22 — ask.AccountAskCommandGroup has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 8 of the 19 points are its own statements and the rest belongs to 5 function items inside it that branch (choose, ready, a function literal at line 71, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · entry-view.EntryBody (cyclomatic 19) · ×1
  • entry-view.EntryBody (cyclomatic 19) apps/web/src/features/resume/editor/write/entry-view.tsx:60 — entry-view.EntryBody has cyclomatic complexity 19 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · pages.PageContainer (cyclomatic 19) · ×1
  • pages.PageContainer (cyclomatic 19) apps/web/src/routes/builder/$resumeId/-sidebar/right/sections/layout/pages.tsx:337 — pages.PageContainer has cyclomatic complexity 19 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · pages.LayoutMenuItems (cyclomatic 19) · ×1
  • pages.LayoutMenuItems (cyclomatic 19) apps/web/src/routes/builder/$resumeId/-sidebar/right/sections/layout/pages.tsx:797 — pages.LayoutMenuItems 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.
D1 · Cyclomatic Complexity · letter-page.LetterOverlay (cyclomatic 19) · ×1
  • letter-page.LetterOverlay (cyclomatic 19) apps/web/src/routes/builder/letter/-components/letter-page.tsx:206 — letter-page.LetterOverlay has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 8 of the 19 points are its own statements and the rest belongs to 6 function items inside it that branch (a function literal at line 212, a function literal at line 221, a function literal at line 236, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · write-panel.EmptyBody (cyclomatic 19) · ×1
  • write-panel.EmptyBody (cyclomatic 19) apps/web/src/routes/builder/letter/-components/write-panel.tsx:988 — write-panel.EmptyBody has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · sanitize.coerceValueAgainstTemplate (cyclomatic 19) · ×1
  • sanitize.coerceValueAgainstTemplate (cyclomatic 19) packages/ai/src/resume/sanitize.ts:110 — sanitize.coerceValueAgainstTemplate has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · translation.proposeTranslation (cyclomatic 19) · ×1
  • translation.proposeTranslation (cyclomatic 19) packages/api/src/features/agent/translation.ts:130 — translation.proposeTranslation has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · plain-text.segment (cyclomatic 19) · ×1
  • plain-text.segment (cyclomatic 19) packages/import/src/plain-text.ts:496 — plain-text.segment 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.
D1 · Cyclomatic Complexity · html-to-odt.mergeStyle (cyclomatic 19) · ×1
  • html-to-odt.mergeStyle (cyclomatic 19) packages/odt/src/html-to-odt.ts:29 — html-to-odt.mergeStyle has cyclomatic complexity 19 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
D1 · Cyclomatic Complexity · use-register-fonts.resolvePdfFonts (cyclomatic 19) · ×1
  • use-register-fonts.resolvePdfFonts (cyclomatic 19) packages/pdf/src/hooks/use-register-fonts.ts:236 — use-register-fonts.resolvePdfFonts has cyclomatic complexity 19 (threshold 15). Of this number, 10 points are the body's own statements and 9 belong to 2 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · tree.buildSemanticTree (cyclomatic 19) · ×1
  • tree.buildSemanticTree (cyclomatic 19) packages/pdf/src/semantic/tree.ts:951 — tree.buildSemanticTree has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 9 of the 19 points are its own statements and the rest belongs to one function literal inside it that branches (line 975). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
D1 · Cyclomatic Complexity · ngrams.buildNgrams (cyclomatic 19) · ×1
  • ngrams.buildNgrams (cyclomatic 19) packages/resume/src/ats-pdf/jd/ngrams.ts:18 — ngrams.buildNgrams has cyclomatic complexity 19 (threshold 15). Of this number, 13 points are the body's own statements and 6 belong to 3 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · career-offer.offerHintFromSalary (cyclomatic 19) · ×1
  • career-offer.offerHintFromSalary (cyclomatic 19) packages/schema/src/career-offer.ts:133 — career-offer.offerHintFromSalary has cyclomatic complexity 19 (threshold 15). Of this number, 14 points are the body's own statements and 5 belong to 2 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · string.glyphWidth (cyclomatic 19) · ×1
  • string.glyphWidth (cyclomatic 19) packages/utils/src/string.ts:174 — string.glyphWidth has cyclomatic complexity 19 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · store.createDraftStore.replayQueue (cyclomatic 18) · ×1
  • store.createDraftStore.replayQueue (cyclomatic 18) apps/mobile/src/data/draft/store.ts:705 — store.createDraftStore.replayQueue has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · stream.useAssistantStream.run (cyclomatic 18) · ×1
  • stream.useAssistantStream.run (cyclomatic 18) apps/mobile/src/data/stream.ts:97 — stream.useAssistantStream.run 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, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · ConsentScreen.ConsentScreen (cyclomatic 18) · ×1
  • ConsentScreen.ConsentScreen (cyclomatic 18) apps/mobile/src/features/auth/ConsentScreen.tsx:31 — ConsentScreen.ConsentScreen has cyclomatic complexity 18 (threshold 15). Of this number, 13 points are the body's own statements and 5 belong to 2 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · model.isEmptyEntry (cyclomatic 18) · ×1
  • model.isEmptyEntry (cyclomatic 18) apps/mobile/src/features/builder/shared/model.ts:274 — model.isEmptyEntry has cyclomatic complexity 18 (threshold 15). Of this number, 17 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · OverviewScreen.OverviewScreen (cyclomatic 18) · ×1
  • OverviewScreen.OverviewScreen (cyclomatic 18) apps/mobile/src/features/builder/overview/OverviewScreen.tsx:112 — OverviewScreen.OverviewScreen 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 7 function items inside it that branch (a function literal at line 126, a function literal at line 200, addSection, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · SignOutDialog.SignOutDialog (cyclomatic 18) · ×1
  • SignOutDialog.SignOutDialog (cyclomatic 18) apps/mobile/src/features/settings/SignOutDialog.tsx:15 — SignOutDialog.SignOutDialog has cyclomatic complexity 18 (threshold 15). Of this number, 10 points are the body's own statements and 8 belong to 7 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · Menu.MenuView (cyclomatic 18) · ×1
  • Menu.MenuView (cyclomatic 18) apps/mobile/src/ui/Menu.tsx:63 — Menu.MenuView has cyclomatic complexity 18 (threshold 15). Of this number, 11 points are the body's own statements and 7 belong to 5 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · scaffold.PushScreen (cyclomatic 18) · ×1
  • scaffold.PushScreen (cyclomatic 18) apps/mobile/src/ui/scaffold.tsx:153 — scaffold.PushScreen has cyclomatic complexity 18 (threshold 15). Of this number, 16 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · display.LevelDisplay (cyclomatic 18) · ×1
  • display.LevelDisplay (cyclomatic 18) apps/web/src/components/level/display.tsx:18 — display.LevelDisplay 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 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.
D1 · Cyclomatic Complexity · font-display.FontDisplay (cyclomatic 18) · ×1
  • font-display.FontDisplay (cyclomatic 18) apps/web/src/components/typography/font-display.tsx:43 — font-display.FontDisplay has cyclomatic complexity 18 (threshold 15). Of this number, 11 points are the body's own statements and 7 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.
D1 · Cyclomatic Complexity · tag-chips.TagChips (cyclomatic 18) · ×1
  • tag-chips.TagChips (cyclomatic 18) apps/web/src/features/applications/components/tag-chips.tsx:15 — tag-chips.TagChips has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 4 of the 18 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 41, 21, 18). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D1 · Cyclomatic Complexity · chat-chrome.ChatComposer (cyclomatic 18) · ×1
  • chat-chrome.ChatComposer (cyclomatic 18) apps/web/src/features/assistant/chat-chrome.tsx:83 — chat-chrome.ChatComposer has cyclomatic complexity 18 (threshold 15). Of this number, 11 points are the body's own statements and 7 belong to one function literal inside it that branches. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · use-assistant-url.useAssistantInUrl (cyclomatic 18) · ×1
  • use-assistant-url.useAssistantInUrl (cyclomatic 18) apps/web/src/features/assistant/use-assistant-url.ts:12 — use-assistant-url.useAssistantInUrl has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 1 of the 18 points is its own statement and the rest belongs to 2 function literals inside it that branch (lines 17, 26). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D1 · Cyclomatic Complexity · prepare.RefreshSwitch (cyclomatic 18) · ×1
  • prepare.RefreshSwitch (cyclomatic 18) apps/web/src/features/career/workspace/prepare.tsx:627 — prepare.RefreshSwitch has cyclomatic complexity 18 (threshold 15). Of this number, 13 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.
D1 · Cyclomatic Complexity · document-card.DocumentRow (cyclomatic 18) · ×1
  • document-card.DocumentRow (cyclomatic 18) apps/web/src/features/documents/document-card.tsx:361 — document-card.DocumentRow has cyclomatic complexity 18 (threshold 15). Of this number, 16 points are the body's own statements and 2 belong to one function item inside it that branches. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · store.readRecovery (cyclomatic 18) · ×1
  • store.readRecovery (cyclomatic 18) apps/web/src/features/letters/store.ts:297 — store.readRecovery 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, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · draft.readUnsavedResume (cyclomatic 18) · ×1
  • draft.readUnsavedResume (cyclomatic 18) apps/web/src/features/resume/builder/draft.ts:255 — draft.readUnsavedResume 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.
D1 · Cyclomatic Complexity · password-dialog.ResumePasswordDialog (cyclomatic 18) · ×1
  • password-dialog.ResumePasswordDialog (cyclomatic 18) apps/web/src/features/resume/builder/password-dialog.tsx:23 — password-dialog.ResumePasswordDialog 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 2 function items inside it that branch (submit, a function literal at line 61). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · page-layer.PageViewToggle (cyclomatic 18) · ×1
  • page-layer.PageViewToggle (cyclomatic 18) apps/web/src/features/resume/editor/check/page-layer.tsx:224 — page-layer.PageViewToggle 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, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · parser-view.ParsedText (cyclomatic 18) · ×1
  • parser-view.ParsedText (cyclomatic 18) apps/web/src/features/resume/editor/check/parser-view.tsx:102 — parser-view.ParsedText has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 6 of the 18 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 159, 182, 140, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D1 · Cyclomatic Complexity · page-overlay.PageOverlay (cyclomatic 18) · ×1
  • page-overlay.PageOverlay (cyclomatic 18) apps/web/src/features/resume/editor/page-overlay.tsx:37 — page-overlay.PageOverlay 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 7 function items inside it that branch (a function literal at line 85, handleClick, a function literal at line 48, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · typography.TypographySectionBuilder (cyclomatic 18) · ×1
  • typography.TypographySectionBuilder (cyclomatic 18) apps/web/src/routes/builder/$resumeId/-sidebar/right/sections/typography.tsx:11 — typography.TypographySectionBuilder has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 2 of the 18 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 16, 63, 28, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D1 · Cyclomatic Complexity · transcript.transcriptOf (cyclomatic 18) · ×1
  • transcript.transcriptOf (cyclomatic 18) packages/ai/src/tools/transcript.ts:33 — transcript.transcriptOf has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 1 of the 18 points is its own statement and the rest belongs to one function literal inside it that branches (line 43). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
D1 · Cyclomatic Complexity · service.describeTestConnectionFailure (cyclomatic 18) · ×1
  • service.describeTestConnectionFailure (cyclomatic 18) packages/api/src/features/ai/service.ts:227 — service.describeTestConnectionFailure has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · service.linkLetterApplication (cyclomatic 18) · ×1
  • service.linkLetterApplication (cyclomatic 18) packages/api/src/features/cover-letters/service.ts:251 — service.linkLetterApplication has cyclomatic complexity 18 (threshold 15). Of this number, 16 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.
D1 · Cyclomatic Complexity · prose.assertProse (cyclomatic 18) · ×1
  • prose.assertProse (cyclomatic 18) packages/api/src/features/agent/prose.ts:19 — prose.assertProse has cyclomatic complexity 18 (threshold 15). Of this number, 17 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · service.sourceText (cyclomatic 18) · ×1
  • service.sourceText (cyclomatic 18) packages/api/src/features/career/service.ts:100 — service.sourceText has cyclomatic complexity 18 (threshold 15). Of this number, 17 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · builder.buildHeader (cyclomatic 18) · ×1
  • builder.buildHeader (cyclomatic 18) packages/docx/src/builder.ts:139 — builder.buildHeader has cyclomatic complexity 18 (threshold 15). Of this number, 17 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · contracts.wireJsonSchema (cyclomatic 18) · ×1
  • contracts.wireJsonSchema (cyclomatic 18) packages/mcp/src/contracts.ts:79 — contracts.wireJsonSchema has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 1 of the 18 points is its own statement and the rest belongs to 2 function literals inside it that branch (lines 92, 83). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D1 · Cyclomatic Complexity · to-forme.fitImage (cyclomatic 18) · ×1
  • to-forme.fitImage (cyclomatic 18) packages/pdf/src/forme/to-forme.tsx:747 — to-forme.fitImage has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · base-styles.buildPdfBaseStyles · ×1
  • base-styles.buildPdfBaseStyles::visit (cyclomatic 18) packages/pdf/src/semantic/base-styles.ts:50 — base-styles.buildPdfBaseStyles::visit has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · render.entryPaginationRepairs · ×1
  • render.entryPaginationRepairs::visit (cyclomatic 18) packages/pdf/src/forme/render.ts:206 — render.entryPaginationRepairs::visit has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · harvest.harvestPdfDocument (cyclomatic 18) · ×1
  • harvest.harvestPdfDocument (cyclomatic 18) packages/resume/src/ats-pdf/harvest.ts:253 — harvest.harvestPdfDocument has cyclomatic complexity 18 (threshold 15). Of this number, 17 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · preparation.nextPreparationStep (cyclomatic 18) · ×1
  • preparation.nextPreparationStep (cyclomatic 18) packages/schema/src/applications/preparation.ts:36 — preparation.nextPreparationStep has cyclomatic complexity 18 (threshold 15). Of this number, 15 points are the body's own statements and 3 belong to one function item inside it that branches. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · catalog-diff.signature · ×1
  • catalog-diff.signature::message (cyclomatic 18) tooling/locales/catalog-diff.mjs:32 — catalog-diff.signature::message has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · session.authorize (cyclomatic 17) · ×1
  • session.authorize (cyclomatic 17) apps/mobile/src/auth/session.ts:326 — session.authorize has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · store.createDraftStore.resolveConflict (cyclomatic 17) · ×1
  • store.createDraftStore.resolveConflict (cyclomatic 17) apps/mobile/src/data/draft/store.ts:517 — store.createDraftStore.resolveConflict has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · provider.DataProvider (cyclomatic 17) · ×1
  • provider.DataProvider (cyclomatic 17) apps/mobile/src/data/provider.tsx:23 — provider.DataProvider has cyclomatic complexity 17 (threshold 15). Of this number, 10 points are the body's own statements and 7 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.
D1 · Cyclomatic Complexity · ApplicationsScreen.CalendarView (cyclomatic 17) · ×1
  • ApplicationsScreen.CalendarView (cyclomatic 17) apps/mobile/src/features/applications/ApplicationsScreen.tsx:755 — ApplicationsScreen.CalendarView 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 8 function items inside it that branch (a function literal at line 903, pick, page, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · download-screen.ExportContent · ×1
  • download-screen.ExportContent::exportFile (cyclomatic 17) apps/mobile/src/features/builder/download/download-screen.tsx:58 — download-screen.ExportContent::exportFile has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This shape REPEATS in the file: one other method here (download-screen.ExportContent) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D1 · Cyclomatic Complexity · page-renderer.serverPdf (cyclomatic 17) · ×1
  • page-renderer.serverPdf (cyclomatic 17) apps/mobile/src/render/page-renderer.ts:97 — page-renderer.serverPdf has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · PullToRefresh.PullToRefresh (cyclomatic 17) · ×1
  • PullToRefresh.PullToRefresh (cyclomatic 17) apps/mobile/src/ui/PullToRefresh.tsx:56 — PullToRefresh.PullToRefresh has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 4 of the 17 points are its own statements and the rest belongs to 5 function literals inside it that branch (lines 90, 105, 71, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D1 · Cyclomatic Complexity · Hero.FlightView (cyclomatic 17) · ×1
  • Hero.FlightView (cyclomatic 17) apps/mobile/src/ui/Hero.tsx:127 — Hero.FlightView 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 134, 155, 185, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D1 · Cyclomatic Complexity · PageZoom.PageZoom (cyclomatic 17) · ×1
  • PageZoom.PageZoom (cyclomatic 17) apps/mobile/src/ui/PageZoom.tsx:41 — PageZoom.PageZoom 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 8 function items inside it that branch (zoomTo, a function literal at line 126, a function literal at line 118, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · generator.addCurlSamples · ×1
  • generator.addCurlSamples::example (cyclomatic 17) apps/server/src/openapi/generator.ts:275 — generator.addCurlSamples::example has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages. This shape REPEATS in the file: one other method here (generator.addCurlSamples) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D1 · Cyclomatic Complexity · resume-page.showPage (cyclomatic 17) · ×1
  • resume-page.showPage (cyclomatic 17) apps/server/src/static/resume-page.ts:142 — resume-page.showPage has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · app.createApp (cyclomatic 17) · ×1
  • app.createApp (cyclomatic 17) apps/server/src/http/app.ts:72 — app.createApp has cyclomatic complexity 17 (threshold 15). Of this number, 9 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.
D1 · Cyclomatic Complexity · translate-resume.TranslateResume (cyclomatic 17) · ×1
  • translate-resume.TranslateResume (cyclomatic 17) apps/web/src/features/assistant/translate-resume.tsx:31 — translate-resume.TranslateResume has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 6 of the 17 points are its own statements and the rest belongs to 4 function items inside it that branch (create, a function literal at line 80, 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.
D1 · Cyclomatic Complexity · pdf-viewer.PdfViewer (cyclomatic 17) · ×1
  • pdf-viewer.PdfViewer (cyclomatic 17) apps/web/src/features/ats-checker/pdf-viewer.tsx:59 — pdf-viewer.PdfViewer has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 5 of the 17 points are its own statements and the rest belongs to 7 function literals inside it that branch (lines 65, 121, 106, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D1 · Cyclomatic Complexity · checker.AtsChecker (cyclomatic 17) · ×1
  • checker.AtsChecker (cyclomatic 17) apps/web/src/features/ats-checker/checker.tsx:65 — checker.AtsChecker 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 items inside it that branch (importAndOpen, check, a function literal at line 116, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · saved.SavedTab (cyclomatic 17) · ×1
  • saved.SavedTab (cyclomatic 17) apps/web/src/features/career/workspace/saved.tsx:52 — saved.SavedTab has cyclomatic complexity 17 (threshold 15). Of this number, 10 points are the body's own statements and 7 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.
D1 · Cyclomatic Complexity · recorder.parse (cyclomatic 17) · ×1
  • recorder.parse (cyclomatic 17) apps/web/src/features/career/workspace/recorder.ts:235 — recorder.parse has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · career-page.useStarters (cyclomatic 17) · ×1
  • career-page.useStarters (cyclomatic 17) apps/web/src/features/career/career-page.tsx:261 — career-page.useStarters has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 3 of the 17 points are its own statements and the rest belongs to 4 function items inside it that branch (word, a function literal at line 307, a function literal at line 368, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · document-actions.DocumentMenuContent (cyclomatic 17) · ×1
  • document-actions.DocumentMenuContent (cyclomatic 17) apps/web/src/features/documents/document-actions.tsx:433 — document-actions.DocumentMenuContent 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, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · section-view.Entries (cyclomatic 17) · ×1
  • section-view.Entries (cyclomatic 17) apps/web/src/features/resume/editor/write/section-view.tsx:156 — section-view.Entries has cyclomatic complexity 17 (threshold 15). Of this number, 10 points are the body's own statements and 7 belong to 6 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · read-file.detectJsonImportKind (cyclomatic 17) · ×1
  • read-file.detectJsonImportKind (cyclomatic 17) apps/web/src/features/resume/import/read-file.ts:32 — read-file.detectJsonImportKind has cyclomatic complexity 17 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · custom-domain-field.CustomDomainField (cyclomatic 17) · ×1
  • custom-domain-field.CustomDomainField (cyclomatic 17) apps/web/src/features/resume/share/custom-domain-field.tsx:23 — custom-domain-field.CustomDomainField has cyclomatic complexity 17 (threshold 15). Of this number, 13 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.
D1 · Cyclomatic Complexity · provider-model.ProviderModel (cyclomatic 17) · ×1
  • provider-model.ProviderModel (cyclomatic 17) apps/web/src/features/settings/ai/provider-model.tsx:34 — provider-model.ProviderModel has cyclomatic complexity 17 (threshold 15). Of this number, 9 points are the body's own statements and 8 belong to 6 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · providers.ProvidersSection (cyclomatic 17) · ×1
  • providers.ProvidersSection (cyclomatic 17) apps/web/src/features/settings/ai/providers.tsx:70 — providers.ProvidersSection 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 4 function items inside it that branch (a function literal at line 144, a function literal at line 183, showReady, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · agent-tool-contracts.agentReadPostings (cyclomatic 17) · ×1
  • agent-tool-contracts.agentReadPostings (cyclomatic 17) packages/ai/src/tools/agent-tool-contracts.ts:215 — agent-tool-contracts.agentReadPostings has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · config.validateOAuthGrant (cyclomatic 17) · ×1
  • config.validateOAuthGrant (cyclomatic 17) packages/auth/src/config.ts:115 — config.validateOAuthGrant has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · plain-text.groupEntries (cyclomatic 17) · ×1
  • plain-text.groupEntries (cyclomatic 17) packages/import/src/plain-text.ts:291 — plain-text.groupEntries has cyclomatic complexity 17 (threshold 15). Of this number, 14 points are the body's own statements and 3 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.
D1 · Cyclomatic Complexity · images.readImageHeader (cyclomatic 17) · ×1
  • images.readImageHeader (cyclomatic 17) packages/pdf/src/forme/images.ts:47 — images.readImageHeader has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · style-rules.toStyle (cyclomatic 17) · ×1
  • style-rules.toStyle (cyclomatic 17) packages/pdf/src/templates/shared/style-rules.ts:46 — style-rules.toStyle has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · cascade.expandVariables (cyclomatic 17) · ×1
  • cascade.expandVariables (cyclomatic 17) packages/resume/src/stylesheet/cascade.ts:245 — cascade.expandVariables has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · period.parseEndpoint (cyclomatic 17) · ×1
  • period.parseEndpoint (cyclomatic 17) packages/schema/src/resume/period.ts:155 — period.parseEndpoint has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · main (cyclomatic 17) · ×1
  • main (cyclomatic 17) tooling/locales/catalog-diff.mjs:173 — main has cyclomatic complexity 17 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
D1 · Cyclomatic Complexity · DetailScreen.workStatus (cyclomatic 16) · ×1
  • DetailScreen.workStatus (cyclomatic 16) apps/mobile/src/features/applications/DetailScreen.tsx:60 — DetailScreen.workStatus 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, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · TwoStepScreen.TwoStepScreen (cyclomatic 16) · ×1
  • TwoStepScreen.TwoStepScreen (cyclomatic 16) apps/mobile/src/features/auth/TwoStepScreen.tsx:17 — TwoStepScreen.TwoStepScreen has cyclomatic complexity 16 (threshold 15). Of this number, 10 points are the body's own statements and 6 belong to 3 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · EntryScreen.EntryScreen · ×1
  • EntryScreen.EntryScreen::render (cyclomatic 16) apps/mobile/src/features/builder/entry/EntryScreen.tsx:186 — EntryScreen.EntryScreen::render has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This shape REPEATS in the file: one other method here (EntryScreen.EntryScreen) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D1 · Cyclomatic Complexity · notifications.syncTodayNotifications.run (cyclomatic 16) · ×1
  • notifications.syncTodayNotifications.run (cyclomatic 16) apps/mobile/src/features/system/notifications.tsx:33 — notifications.syncTodayNotifications.run has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · Text.Text (cyclomatic 16) · ×1
  • Text.Text (cyclomatic 16) apps/mobile/src/ui/Text.tsx:80 — Text.Text has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · generator.addCurlSamples (cyclomatic 16) · ×1
  • generator.addCurlSamples (cyclomatic 16) apps/server/src/openapi/generator.ts:265 — generator.addCurlSamples has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This shape REPEATS in the file: one other method here (generator.addCurlSamples::example) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D1 · Cyclomatic Complexity · add-application-dialog.AddApplicationForm · ×1
  • add-application-dialog.AddApplicationForm::add (cyclomatic 16) apps/web/src/features/applications/components/add-application-dialog.tsx:389 — add-application-dialog.AddApplicationForm::add 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. This shape REPEATS in the file: one other method here (add-application-dialog.AddApplicationForm) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D1 · Cyclomatic Complexity · calendar-view.AgendaRow (cyclomatic 16) · ×1
  • calendar-view.AgendaRow (cyclomatic 16) apps/web/src/features/applications/components/calendar-view.tsx:339 — calendar-view.AgendaRow has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · export-applications-sheet.ExportApplicationsSheet (cyclomatic 16) · ×1
  • export-applications-sheet.ExportApplicationsSheet (cyclomatic 16) apps/web/src/features/applications/components/export-applications-sheet.tsx:31 — export-applications-sheet.ExportApplicationsSheet has cyclomatic complexity 16 (threshold 15). Of this number, 13 points are the body's own statements and 3 belong to one function item inside it that branches. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · document.useLetterAssistantDocument (cyclomatic 16) · ×1
  • document.useLetterAssistantDocument (cyclomatic 16) apps/web/src/features/assistant/document.ts:129 — document.useLetterAssistantDocument has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 1 of the 16 points is its own statement and the rest belongs to 3 function literals inside it that branch (lines 150, 172, 136). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D1 · Cyclomatic Complexity · tool-approvals.StoryProposal (cyclomatic 16) · ×1
  • tool-approvals.StoryProposal (cyclomatic 16) apps/web/src/features/assistant/tool-approvals.tsx:123 — tool-approvals.StoryProposal 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 literals inside it that branch (lines 145, 181, 182). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D1 · Cyclomatic Complexity · practise.HearIt (cyclomatic 16) · ×1
  • practise.HearIt (cyclomatic 16) apps/web/src/features/career/workspace/practise.tsx:1013 — practise.HearIt 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 one function item inside it that branches (play). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · offers.OneOffer (cyclomatic 16) · ×1
  • offers.OneOffer (cyclomatic 16) apps/web/src/features/career/offers.tsx:505 — offers.OneOffer has cyclomatic complexity 16 (threshold 15). Of this number, 11 points are the body's own statements and 5 belong to 2 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · offers.openQuestions (cyclomatic 16) · ×1
  • offers.openQuestions (cyclomatic 16) apps/web/src/features/career/offers.tsx:1091 — offers.openQuestions 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 one function item inside it that branches (checks). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · resume-thumbnail.useResumeThumbnail (cyclomatic 16) · ×1
  • resume-thumbnail.useResumeThumbnail (cyclomatic 16) apps/web/src/features/documents/resume-thumbnail.tsx:90 — resume-thumbnail.useResumeThumbnail 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 5 function literals inside it that branch (lines 141, 161, 111, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D1 · Cyclomatic Complexity · documents-page.DocumentsPage · ×1
  • documents-page.DocumentsPage::onSearchKeyDown (cyclomatic 16) apps/web/src/features/documents/documents-page.tsx:289 — documents-page.DocumentsPage::onSearchKeyDown has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This shape REPEATS in the file: one other method here (documents-page.DocumentsPage) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D1 · Cyclomatic Complexity · fit.fitOnce (cyclomatic 16) · ×1
  • fit.fitOnce (cyclomatic 16) apps/web/src/features/resume/editor/design/fit.ts:84 — fit.fitOnce has cyclomatic complexity 16 (threshold 15). Of this number, 13 points are the body's own statements and 3 belong to 2 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · template-group.TemplateGroup (cyclomatic 16) · ×1
  • template-group.TemplateGroup (cyclomatic 16) apps/web/src/features/resume/editor/design/template-group.tsx:56 — template-group.TemplateGroup 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 (a function literal at line 65, a function literal at line 110, a function literal at line 79, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · providers.AddProviderDialog (cyclomatic 16) · ×1
  • providers.AddProviderDialog (cyclomatic 16) apps/web/src/features/settings/ai/providers.tsx:474 — providers.AddProviderDialog 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 4 function items inside it that branch (save, a function literal at line 564, a function literal at line 550, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · review.entryReview (cyclomatic 16) · ×1
  • review.entryReview (cyclomatic 16) packages/api/src/features/agent/review.ts:16 — review.entryReview 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 2 function literals inside it that branch (lines 18, 26). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D1 · Cyclomatic Complexity · follow-up.syncFollowUp (cyclomatic 16) · ×1
  • follow-up.syncFollowUp (cyclomatic 16) packages/api/src/features/applications/follow-up.ts:11 — follow-up.syncFollowUp has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · pdf-lines.separateIdentityRail (cyclomatic 16) · ×1
  • pdf-lines.separateIdentityRail (cyclomatic 16) packages/import/src/pdf-lines.ts:137 — pdf-lines.separateIdentityRail has cyclomatic complexity 16 (threshold 15). Of this number, 11 points are the body's own statements and 5 belong to 2 function literals inside it that branch. To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions. This is NOT this file's highest cyclomatic complexity: pdf-lines.educationRecords::isLead (cyclomatic 18) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded method is counted neither in this dimension's figures nor in its score.
D1 · Cyclomatic Complexity · parity.decodeInput (cyclomatic 16) · ×1
  • parity.decodeInput (cyclomatic 16) packages/mcp/src/parity.ts:345 — parity.decodeInput 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, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · page-map.extractPageMap.pages (cyclomatic 16) · ×1
  • page-map.extractPageMap.pages (cyclomatic 16) packages/pdf/src/page-map.ts:173 — page-map.extractPageMap.pages has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 2 of the 16 points are its own statements and the rest belongs to one function item inside it that branches (visit). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · cascade.normalizeValue (cyclomatic 16) · ×1
  • cascade.normalizeValue (cyclomatic 16) packages/resume/src/stylesheet/cascade.ts:458 — cascade.normalizeValue has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · career-offer.parseOfferEntry (cyclomatic 16) · ×1
  • career-offer.parseOfferEntry (cyclomatic 16) packages/schema/src/career-offer.ts:18 — career-offer.parseOfferEntry has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · amount.parseLocalizedNumber (cyclomatic 16) · ×1
  • amount.parseLocalizedNumber (cyclomatic 16) packages/utils/src/amount.ts:1 — amount.parseLocalizedNumber has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · (anonymous) (cyclomatic 16) · ×1
  • (anonymous) (cyclomatic 16) tooling/capture/popup.mjs:97 — (anonymous) has cyclomatic complexity 16 (threshold 15). Of this number, 14 points are the body's own statements and 2 belong to 2 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · compare (cyclomatic 16) · ×1
  • compare (cyclomatic 16) tooling/locales/catalog-diff.mjs:147 — compare 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.
D10 · Test Quality · No assertions · ×1
  • No assertions: says which messages Knowledge changes hold back, as the server names them apps/web/src/features/career/coach-chat.test.tsx:461 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
D2 · Cognitive Complexity · cascade.resolveStylesheet (cognitive 204) · ×1
  • cascade.resolveStylesheet (cognitive 204) packages/resume/src/stylesheet/cascade.ts:564 — cascade.resolveStylesheet has cognitive complexity 204 (threshold 15). Drivers by points: if/else 59 (154 pts), ternaries 9 (22 pts), loops 10 (15 pts), boolean chains 13 (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.
D2 · Cognitive Complexity · screen.TodayScreen (cognitive 193) · ×1
  • screen.TodayScreen (cognitive 193) apps/mobile/src/features/today/screen.tsx:64 — screen.TodayScreen has cognitive complexity 193 (threshold 15). Drivers by points: ternaries 56 (162 pts), boolean chains 18, error handling 5 (8 pts), loops 1 (4 pts), if/else 1 (nesting depth added 112). Of this number, 111 points are the body's own statements and 82 belong to 18 function items inside it that branch. To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
D2 · Cognitive Complexity · practise.Session (cognitive 180) · ×1
  • practise.Session (cognitive 180) apps/web/src/features/career/workspace/practise.tsx:373 — practise.Session has cognitive complexity 180 (threshold 15). Drivers by points: ternaries 29 (97 pts), boolean chains 44, if/else 23 (36 pts), error handling 3 (nesting depth added 81). Of this number, 124 points are the body's own statements and 56 belong to 16 function items inside it that branch. To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
D2 · Cognitive Complexity · actions.ScopedDocumentActionsScreen (cognitive 137) · ×1
  • actions.ScopedDocumentActionsScreen (cognitive 137) apps/mobile/src/features/documents/actions.tsx:40 — actions.ScopedDocumentActionsScreen has cognitive complexity 137 (threshold 15). Drivers by points: ternaries 22 (81 pts), if/else 14 (29 pts), error handling 5 (14 pts), boolean chains 13 (nesting depth added 83). Of this number, 60 points are the body's own statements and 77 belong to 9 function items inside it that branch. To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
D2 · Cognitive Complexity · config.getAuthConfig (cognitive 126) · ×1
  • config.getAuthConfig (cognitive 126) packages/auth/src/config.ts:797 — config.getAuthConfig has cognitive complexity 126 (threshold 15). Drivers by points: if/else 44 (64 pts), boolean chains 34, ternaries 17 (25 pts), error handling 2, loops 1 (nesting depth added 28). Most of this is not in the body itself: 10 of the 126 points are its own statements and the rest belongs to 10 function literals inside it that branch (lines 874, 1052, 846, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · style.toFormeStyle (cognitive 126) · ×1
  • style.toFormeStyle (cognitive 126) packages/pdf/src/forme/style.ts:377 — style.toFormeStyle has cognitive complexity 126 (threshold 15). Drivers by points: if/else 45 (101 pts), boolean chains 17, ternaries 3 (7 pts), loops 1 (nesting depth added 60). Of this number, 125 points are the body's own statements and 1 belongs to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · documents-page.DocumentsPage (cognitive 107) · ×1
  • documents-page.DocumentsPage (cognitive 107) apps/web/src/features/documents/documents-page.tsx:80 — documents-page.DocumentsPage has cognitive complexity 107 (threshold 15). Drivers by points: ternaries 24 (85 pts), boolean chains 41, if/else 27 (33 pts) (nesting depth added 67). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function. This shape REPEATS in the file: one other method here (documents-page.DocumentsPage::onSearchKeyDown) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D2 · Cognitive Complexity · add-application-dialog.AddApplicationForm (cognitive 106) · ×1
  • add-application-dialog.AddApplicationForm (cognitive 106) apps/web/src/features/applications/components/add-application-dialog.tsx:188 — add-application-dialog.AddApplicationForm has cognitive complexity 106 (threshold 15). Drivers by points: boolean chains 89, ternaries 43 (47 pts), if/else 21 (27 pts), error handling 3 (4 pts) (nesting depth added 11). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators. This shape REPEATS in the file: one other method here (add-application-dialog.AddApplicationForm::add) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D2 · Cognitive Complexity · offers.ScopedOffersScreen (cognitive 105) · ×1
  • offers.ScopedOffersScreen (cognitive 105) apps/mobile/src/features/career/offers.tsx:31 — offers.ScopedOffersScreen has cognitive complexity 105 (threshold 15). Drivers by points: ternaries 31 (67 pts), boolean chains 23, if/else 8 (15 pts) (nesting depth added 43). Of this number, 16 points are the body's own statements and 89 belong to 14 function items inside it that branch. To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
D2 · Cognitive Complexity · html-to-docx.processBlockElement (cognitive 103) · ×1
  • html-to-docx.processBlockElement (cognitive 103) packages/docx/src/html-to-docx.ts:149 — html-to-docx.processBlockElement has cognitive complexity 103 (threshold 15). Drivers by points: if/else 23 (51 pts), ternaries 12 (37 pts), loops 3 (8 pts), boolean chains 7 (nesting depth added 58). Of this number, 100 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.
D2 · Cognitive Complexity · ai-consent.authorizeAiRequest (cognitive 99) · ×1
  • ai-consent.authorizeAiRequest (cognitive 99) apps/web/src/libs/orpc/ai-consent.ts:13 — ai-consent.authorizeAiRequest has cognitive complexity 99 (threshold 15). Drivers by points: ternaries 33 (44 pts), boolean chains 38, if/else 16 (17 pts) (nesting depth added 12). Of this number, 21 points are the body's own statements and 78 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.
D2 · Cognitive Complexity · pdf-lines.headingTest (cognitive 99) · ×1
  • pdf-lines.headingTest (cognitive 99) packages/import/src/pdf-lines.ts:207 — pdf-lines.headingTest has cognitive complexity 99 (threshold 15). Drivers by points: boolean chains 120, if/else 40 (76 pts), loops 15 (44 pts), ternaries 8 (15 pts) (nesting depth added 72). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators. This shape REPEATS in the file: 2 other methods here (pdf-lines.headingTest::isolatedRaw, pdf-lines.headingTest::test) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D2 · Cognitive Complexity · trash-page.TrashPage (cognitive 98) · ×1
  • trash-page.TrashPage (cognitive 98) apps/web/src/features/trash/trash-page.tsx:81 — trash-page.TrashPage has cognitive complexity 98 (threshold 15). Drivers by points: ternaries 25 (60 pts), boolean chains 22, if/else 14, error handling 2 (nesting depth added 35). Of this number, 21 points are the body's own statements and 77 belong to 12 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · to-forme.convertNode (cognitive 98) · ×1
  • to-forme.convertNode (cognitive 98) packages/pdf/src/forme/to-forme.tsx:477 — to-forme.convertNode has cognitive complexity 98 (threshold 15). Drivers by points: if/else 24 (49 pts), ternaries 11 (23 pts), boolean chains 19, loops 2 (6 pts), match/switch 1 (nesting depth added 41). Of this number, 89 points are the body's own statements and 9 belong to 4 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · SignInScreen.SignInScreen (cognitive 97) · ×1
  • SignInScreen.SignInScreen (cognitive 97) apps/mobile/src/features/auth/SignInScreen.tsx:47 — SignInScreen.SignInScreen has cognitive complexity 97 (threshold 15). Drivers by points: ternaries 36 (79 pts), if/else 11, boolean chains 6, error handling 1 (nesting depth added 43). Of this number, 61 points are the body's own statements and 36 belong to 4 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · csv.mapCsvToApplications (cognitive 93) · ×1
  • csv.mapCsvToApplications (cognitive 93) packages/schema/src/applications/csv.ts:300 — csv.mapCsvToApplications has cognitive complexity 93 (threshold 15). Drivers by points: if/else 40 (73 pts), boolean chains 10, ternaries 3 (6 pts), error handling 1 (3 pts), loops 1 (nesting depth added 38). Of this number, 34 points are the body's own statements and 59 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · coach.CoachPage (cognitive 92) · ×1
  • coach.CoachPage (cognitive 92) apps/web/src/features/career/coach.tsx:115 — coach.CoachPage has cognitive complexity 92 (threshold 15). Drivers by points: ternaries 23 (44 pts), boolean chains 35, if/else 11, error handling 2 (nesting depth added 21). Of this number, 58 points are the body's own statements and 34 belong to 17 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · assistant-panel.AssistantPanel (cognitive 89) · ×1
  • assistant-panel.AssistantPanel (cognitive 89) apps/web/src/features/assistant/assistant-panel.tsx:59 — assistant-panel.AssistantPanel has cognitive complexity 89 (threshold 15). Drivers by points: ternaries 19 (64 pts), boolean chains 15, if/else 8, error handling 2 (nesting depth added 45). Of this number, 76 points are the body's own statements and 13 belong to 6 function items inside it that branch. To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
D2 · Cognitive Complexity · DescriptionScreen.DescriptionScreen (cognitive 88) · ×1
  • DescriptionScreen.DescriptionScreen (cognitive 88) apps/mobile/src/features/builder/description/DescriptionScreen.tsx:46 — DescriptionScreen.DescriptionScreen has cognitive complexity 88 (threshold 15). Drivers by points: ternaries 32 (48 pts), if/else 18 (24 pts), boolean chains 15, error handling 1 (nesting depth added 22). Of this number, 34 points are the body's own statements and 54 belong to 17 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · preferences.PreferencesContent (cognitive 86) · ×1
  • preferences.PreferencesContent (cognitive 86) apps/mobile/src/features/career/preferences.tsx:37 — preferences.PreferencesContent has cognitive complexity 86 (threshold 15). Drivers by points: ternaries 28 (67 pts), if/else 9 (10 pts), boolean chains 7, error handling 2 (nesting depth added 40). Of this number, 61 points are the body's own statements and 25 belong to 3 function items inside it that branch. To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
D2 · Cognitive Complexity · offer-entry.OfferForm (cognitive 86) · ×1
  • offer-entry.OfferForm (cognitive 86) apps/web/src/features/career/offer-entry.tsx:255 — offer-entry.OfferForm has cognitive complexity 86 (threshold 15). Drivers by points: ternaries 29 (37 pts), boolean chains 29, if/else 19 (20 pts) (nesting depth added 9). Of this number, 36 points are the body's own statements and 50 belong to 18 function items inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · proposal-applications.saveProposalApplications (cognitive 86) · ×1
  • proposal-applications.saveProposalApplications (cognitive 86) packages/api/src/features/agent/proposal-applications.ts:126 — proposal-applications.saveProposalApplications has cognitive complexity 86 (threshold 15). Drivers by points: if/else 14 (52 pts), loops 6 (18 pts), ternaries 3 (9 pts), boolean chains 7 (nesting depth added 56). Of this number, 85 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ai-consent.authorizeAiRequest (cognitive 85) · ×1
  • ai-consent.authorizeAiRequest (cognitive 85) apps/mobile/src/api/ai-consent.ts:16 — ai-consent.authorizeAiRequest has cognitive complexity 85 (threshold 15). Drivers by points: boolean chains 36, ternaries 22 (34 pts), if/else 12 (13 pts), error handling 1 (2 pts) (nesting depth added 14). Of this number, 78 points are the body's own statements and 7 belong to 3 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · store.useLetterEditorStore (cognitive 84) · ×1
  • store.useLetterEditorStore (cognitive 84) apps/web/src/features/letters/store.ts:388 — store.useLetterEditorStore has cognitive complexity 84 (threshold 15). Drivers by points: if/else 28 (31 pts), boolean chains 27, ternaries 17 (23 pts), error handling 1 (2 pts), loops 1 (nesting depth added 10). None of this is in the body itself: all 84 points belong to 15 function literals inside it that branch (lines 422, 536, 488, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · pdf-lines.projectSectionFields (cognitive 83) · ×1
  • pdf-lines.projectSectionFields (cognitive 83) packages/import/src/pdf-lines.ts:1839 — pdf-lines.projectSectionFields has cognitive complexity 83 (threshold 15). Drivers by points: if/else 17 (52 pts), ternaries 5 (14 pts), boolean chains 12, loops 3 (5 pts) (nesting depth added 46). Of this number, 66 points are the body's own statements and 17 belong to 6 function items inside it that branch. To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
D2 · Cognitive Complexity · web-access.WebAccessSection (cognitive 81) · ×1
  • web-access.WebAccessSection (cognitive 81) apps/web/src/features/settings/ai/web-access.tsx:56 — web-access.WebAccessSection has cognitive complexity 81 (threshold 15). Drivers by points: ternaries 15 (58 pts), boolean chains 22, if/else 1 (nesting depth added 43). Of this number, 80 points are the body's own statements and 1 belongs to 3 function items inside it that branch. To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
D2 · Cognitive Complexity · index.RouteComponent (cognitive 80) · ×1
  • index.RouteComponent (cognitive 80) apps/web/src/routes/dashboard/applications/index.tsx:121 — index.RouteComponent has cognitive complexity 80 (threshold 15). Drivers by points: boolean chains 39, ternaries 9 (29 pts), if/else 10, error handling 1, loops 1 (nesting depth added 20). Of this number, 59 points are the body's own statements and 21 belong to 13 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · schedule-sheet.ScheduleSheet (cognitive 79) · ×1
  • schedule-sheet.ScheduleSheet (cognitive 79) apps/web/src/features/career/schedule-sheet.tsx:138 — schedule-sheet.ScheduleSheet has cognitive complexity 79 (threshold 15). Drivers by points: ternaries 38 (58 pts), boolean chains 47, if/else 5 (nesting depth added 20). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (schedule-sheet.ScheduleSheet::onSave) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D2 · Cognitive Complexity · search.ScopedSearchScreen (cognitive 78) · ×1
  • search.ScopedSearchScreen (cognitive 78) apps/mobile/src/features/documents/search.tsx:31 — search.ScopedSearchScreen has cognitive complexity 78 (threshold 15). Drivers by points: ternaries 24 (61 pts), boolean chains 13, if/else 4 (nesting depth added 37). Of this number, 52 points are the body's own statements and 26 belong to 8 function items inside it that branch. To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
D2 · Cognitive Complexity · proposals-screen.Proposals (cognitive 75) · ×1
  • proposals-screen.Proposals (cognitive 75) apps/mobile/src/features/builder/assistant/proposals-screen.tsx:43 — proposals-screen.Proposals has cognitive complexity 75 (threshold 15). Drivers by points: ternaries 25 (47 pts), boolean chains 14, if/else 10 (14 pts) (nesting depth added 26). Most of this is not in the body itself: 15 of the 75 points are its own statements and the rest belongs to 13 function items inside it that branch (a function literal at line 158, decide, seed, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · generate.generateCareer (cognitive 73) · ×1
  • generate.generateCareer (cognitive 73) packages/api/src/features/career/generate.ts:113 — generate.generateCareer has cognitive complexity 73 (threshold 15). Drivers by points: ternaries 26 (33 pts), if/else 14 (19 pts), boolean chains 15, loops 4 (6 pts) (nesting depth added 14). Of this number, 63 points are the body's own statements and 10 belong to 4 function items inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
D2 · Cognitive Complexity · to-html.convertNode (cognitive 73) · ×1
  • to-html.convertNode (cognitive 73) packages/pdf/src/html/to-html.ts:290 — to-html.convertNode has cognitive complexity 73 (threshold 15). Drivers by points: ternaries 16 (34 pts), if/else 12 (25 pts), boolean chains 10, loops 1 (3 pts), match/switch 1 (nesting depth added 33). Of this number, 68 points are the body's own statements and 5 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.
D2 · Cognitive Complexity · preparation.Preparation (cognitive 72) · ×1
  • preparation.Preparation (cognitive 72) apps/web/src/features/career/workspace/preparation.tsx:40 — preparation.Preparation has cognitive complexity 72 (threshold 15). Drivers by points: ternaries 16 (41 pts), boolean chains 24, if/else 2 (7 pts) (nesting depth added 30). Most of this is not in the body itself: 15 of the 72 points are its own statements and the rest belongs to 7 function items inside it that branch (a function literal at line 162, copyResume, writeLetter, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · share-panel.PrimaryRow (cognitive 72) · ×1
  • share-panel.PrimaryRow (cognitive 72) apps/web/src/features/resume/share/share-panel.tsx:490 — share-panel.PrimaryRow has cognitive complexity 72 (threshold 15). Drivers by points: ternaries 15 (66 pts), boolean chains 3, if/else 2 (3 pts) (nesting depth added 52). Of this number, 68 points are the body's own statements and 4 belong to one function item inside it that branches. To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
D2 · Cognitive Complexity · library.ScopedLibraryScreen (cognitive 70) · ×1
  • library.ScopedLibraryScreen (cognitive 70) apps/mobile/src/features/documents/library.tsx:41 — library.ScopedLibraryScreen has cognitive complexity 70 (threshold 15). Drivers by points: ternaries 16 (40 pts), if/else 7 (14 pts), boolean chains 6, error handling 1 (5 pts), loops 1 (5 pts) (nesting depth added 39). Of this number, 35 points are the body's own statements and 35 belong to 8 function items inside it that branch. To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
D2 · Cognitive Complexity · new-document-dialog.NewDocument (cognitive 70) · ×1
  • new-document-dialog.NewDocument (cognitive 70) apps/web/src/features/documents/new-document-dialog.tsx:93 — new-document-dialog.NewDocument has cognitive complexity 70 (threshold 15). Drivers by points: boolean chains 34, ternaries 18 (27 pts), if/else 7 (8 pts), error handling 1 (nesting depth added 10). Of this number, 44 points are the body's own statements and 26 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.
D2 · Cognitive Complexity · values.expandShorthand (cognitive 70) · ×1
  • values.expandShorthand (cognitive 70) packages/resume/src/stylesheet/values.ts:241 — values.expandShorthand has cognitive complexity 70 (threshold 15). Drivers by points: if/else 23 (56 pts), boolean chains 7, ternaries 2 (7 pts) (nesting depth added 38). Of this number, 69 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
D2 · Cognitive Complexity · conversation.ToolPartView (cognitive 69) · ×1
  • conversation.ToolPartView (cognitive 69) apps/web/src/features/assistant/conversation.tsx:743 — conversation.ToolPartView has cognitive complexity 69 (threshold 15). Drivers by points: ternaries 12 (31 pts), if/else 10 (20 pts), boolean chains 17, match/switch 1 (nesting depth added 29). Of this number, 63 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.
D2 · Cognitive Complexity · CheckScreen.CheckScreen (cognitive 67) · ×1
  • CheckScreen.CheckScreen (cognitive 67) apps/mobile/src/features/builder/check/CheckScreen.tsx:93 — CheckScreen.CheckScreen has cognitive complexity 67 (threshold 15). Drivers by points: ternaries 32 (57 pts), boolean chains 5, if/else 3 (4 pts), error handling 1 (nesting depth added 26). Of this number, 48 points are the body's own statements and 19 belong to 6 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · fit.FitTab (cognitive 67) · ×1
  • fit.FitTab (cognitive 67) apps/web/src/features/career/workspace/fit.tsx:52 — fit.FitTab has cognitive complexity 67 (threshold 15). Drivers by points: boolean chains 31, ternaries 18 (23 pts), if/else 10 (12 pts), error handling 1 (nesting depth added 7). Of this number, 41 points are the body's own statements and 26 belong to 9 function items inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
D2 · Cognitive Complexity · interview-dialog.InterviewDialog (cognitive 66) · ×1
  • interview-dialog.InterviewDialog (cognitive 66) apps/web/src/features/applications/components/interview-dialog.tsx:160 — interview-dialog.InterviewDialog has cognitive complexity 66 (threshold 15). Drivers by points: ternaries 23 (27 pts), boolean chains 22, if/else 13 (16 pts), error handling 1 (nesting depth added 7). Of this number, 37 points are the body's own statements and 29 belong to 15 function items inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · SaveJobScreen.SaveJobScreen (cognitive 65) · ×1
  • SaveJobScreen.SaveJobScreen (cognitive 65) apps/mobile/src/features/applications/SaveJobScreen.tsx:41 — SaveJobScreen.SaveJobScreen has cognitive complexity 65 (threshold 15). Drivers by points: ternaries 25 (40 pts), boolean chains 18, if/else 5, error handling 2 (nesting depth added 15). Of this number, 43 points are the body's own statements and 22 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.
D2 · Cognitive Complexity · conversation.Conversation (cognitive 65) · ×1
  • conversation.Conversation (cognitive 65) apps/web/src/features/assistant/conversation.tsx:102 — conversation.Conversation has cognitive complexity 65 (threshold 15). Drivers by points: boolean chains 33, if/else 15 (17 pts), ternaries 9 (10 pts), loops 5 (nesting depth added 3). Of this number, 17 points are the body's own statements and 48 belong to 21 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · answer-library.AnswerLibrary (cognitive 65) · ×1
  • answer-library.AnswerLibrary (cognitive 65) apps/web/src/features/career/workspace/answer-library.tsx:49 — answer-library.AnswerLibrary has cognitive complexity 65 (threshold 15). Drivers by points: boolean chains 37, ternaries 14 (22 pts), if/else 4 (5 pts), error handling 1 (nesting depth added 9). Of this number, 38 points are the body's own statements and 27 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.
D2 · Cognitive Complexity · scroll.useScrollScenes (cognitive 65) · ×1
  • scroll.useScrollScenes (cognitive 65) apps/web/src/features/homepage/scroll.ts:223 — scroll.useScrollScenes has cognitive complexity 65 (threshold 15). Drivers by points: if/else 21 (30 pts), boolean chains 15, ternaries 11 (15 pts), loops 4 (5 pts) (nesting depth added 14). None of this is in the body itself: all 65 points belong to 6 function literals inside it that branch (lines 290, 244, 413, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · rich-text-editor-field.RichTextEditor (cognitive 65) · ×1
  • rich-text-editor-field.RichTextEditor (cognitive 65) apps/web/src/features/resume/editor/write/rich-text-editor-field.tsx:214 — rich-text-editor-field.RichTextEditor has cognitive complexity 65 (threshold 15). Drivers by points: boolean chains 37, if/else 14 (20 pts), ternaries 8 (nesting depth added 6). Of this number, 23 points are the body's own statements and 42 belong to 19 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · prepare-review.ReviewForm (cognitive 64) · ×1
  • prepare-review.ReviewForm (cognitive 64) apps/web/src/features/career/workspace/prepare-review.tsx:49 — prepare-review.ReviewForm has cognitive complexity 64 (threshold 15). Drivers by points: boolean chains 27, if/else 21 (24 pts), ternaries 8 (12 pts), error handling 1 (nesting depth added 7). Of this number, 23 points are the body's own statements and 41 belong to 24 function items inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
D2 · Cognitive Complexity · overview.ApplicationOverview (cognitive 64) · ×1
  • overview.ApplicationOverview (cognitive 64) apps/web/src/features/career/workspace/overview.tsx:52 — overview.ApplicationOverview has cognitive complexity 64 (threshold 15). Drivers by points: ternaries 30 (50 pts), boolean chains 13, if/else 1 (nesting depth added 20). Of this number, 58 points are the body's own statements and 6 belong to 3 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · schedules.ScheduleEditor (cognitive 62) · ×1
  • schedules.ScheduleEditor (cognitive 62) apps/mobile/src/features/career/schedules.tsx:81 — schedules.ScheduleEditor has cognitive complexity 62 (threshold 15). Drivers by points: ternaries 28 (40 pts), if/else 6 (12 pts), boolean chains 9, error handling 1 (nesting depth added 18). Of this number, 35 points are the body's own statements and 27 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.
D2 · Cognitive Complexity · pdf-lines.splitExperienceItems (cognitive 62) · ×1
  • pdf-lines.splitExperienceItems (cognitive 62) packages/import/src/pdf-lines.ts:965 — pdf-lines.splitExperienceItems has cognitive complexity 62 (threshold 15). Drivers by points: if/else 10 (28 pts), loops 8 (19 pts), boolean chains 12, ternaries 1 (3 pts) (nesting depth added 31). Of this number, 60 points are the body's own statements and 2 belong to 3 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · shell.Workspace (cognitive 61) · ×1
  • shell.Workspace (cognitive 61) apps/web/src/features/career/workspace/shell.tsx:123 — shell.Workspace has cognitive complexity 61 (threshold 15). Drivers by points: ternaries 19 (31 pts), boolean chains 26, if/else 4 (nesting depth added 12). Of this number, 46 points are the body's own statements and 15 belong to 10 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · proposal-list.ProposalItem (cognitive 60) · ×1
  • proposal-list.ProposalItem (cognitive 60) apps/web/src/features/resume/editor/proposals/proposal-list.tsx:303 — proposal-list.ProposalItem has cognitive complexity 60 (threshold 15). Drivers by points: ternaries 18 (35 pts), boolean chains 21, if/else 3, error handling 1 (nesting depth added 17). Of this number, 48 points are the body's own statements and 12 belong to 4 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · pdf-lines.orderExperienceHeaders (cognitive 60) · ×1
  • pdf-lines.orderExperienceHeaders (cognitive 60) packages/import/src/pdf-lines.ts:1181 — pdf-lines.orderExperienceHeaders has cognitive complexity 60 (threshold 15). Drivers by points: if/else 18 (34 pts), boolean chains 14, ternaries 7 (11 pts), loops 1 (nesting depth added 20). Of this number, 53 points are the body's own statements and 7 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.
D2 · Cognitive Complexity · check.checkDocs (cognitive 60) · ×1
  • check.checkDocs (cognitive 60) tooling/docs/check.mjs:28 — check.checkDocs has cognitive complexity 60 (threshold 15). Drivers by points: if/else 10 (29 pts), loops 9 (14 pts), ternaries 3 (9 pts), boolean chains 4, error handling 1 (4 pts) (nesting depth added 33). Of this number, 54 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.
D2 · Cognitive Complexity · coach.ScopedCoachScreen (cognitive 59) · ×1
  • coach.ScopedCoachScreen (cognitive 59) apps/mobile/src/features/career/coach.tsx:52 — coach.ScopedCoachScreen has cognitive complexity 59 (threshold 15). Drivers by points: ternaries 24 (38 pts), boolean chains 12, if/else 7, error handling 2 (nesting depth added 14). Of this number, 34 points are the body's own statements and 25 belong to 11 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · apply.AnswerCard (cognitive 59) · ×1
  • apply.AnswerCard (cognitive 59) apps/web/src/features/career/workspace/apply.tsx:490 — apply.AnswerCard has cognitive complexity 59 (threshold 15). Drivers by points: boolean chains 27, ternaries 20 (24 pts), if/else 6 (8 pts) (nesting depth added 6). Of this number, 41 points are the body's own statements and 18 belong to 12 function items inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
D2 · Cognitive Complexity · practise.PractiseTab (cognitive 59) · ×1
  • practise.PractiseTab (cognitive 59) apps/web/src/features/career/workspace/practise.tsx:122 — practise.PractiseTab has cognitive complexity 59 (threshold 15). Drivers by points: ternaries 16 (32 pts), boolean chains 22, if/else 5 (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · import-applications-sheet.ImportApplicationsSheet (cognitive 58) · ×1
  • import-applications-sheet.ImportApplicationsSheet (cognitive 58) apps/web/src/features/applications/components/import-applications-sheet.tsx:86 — import-applications-sheet.ImportApplicationsSheet has cognitive complexity 58 (threshold 15). Drivers by points: boolean chains 30, if/else 12 (14 pts), ternaries 12 (13 pts), loops 1 (nesting depth added 3). Of this number, 32 points are the body's own statements and 26 belong to 19 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · pdf-lines.foldStackedHeaders (cognitive 58) · ×1
  • pdf-lines.foldStackedHeaders (cognitive 58) packages/import/src/pdf-lines.ts:1063 — pdf-lines.foldStackedHeaders has cognitive complexity 58 (threshold 15). Drivers by points: if/else 7 (26 pts), ternaries 5 (22 pts), boolean chains 6, loops 2 (4 pts) (nesting depth added 38). Of this number, 55 points are the body's own statements and 3 belong to 3 function literals inside it that branch. To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
D2 · Cognitive Complexity · store.createDraftStore.open (cognitive 57) · ×1
  • store.createDraftStore.open (cognitive 57) apps/mobile/src/data/draft/store.ts:239 — store.createDraftStore.open has cognitive complexity 57 (threshold 15). Drivers by points: if/else 24 (29 pts), ternaries 5 (13 pts), boolean chains 12, error handling 2 (3 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.
D2 · Cognitive Complexity · chip-input.ChipInput (cognitive 57) · ×1
  • chip-input.ChipInput (cognitive 57) apps/web/src/components/input/chip-input.tsx:170 — chip-input.ChipInput has cognitive complexity 57 (threshold 15). Drivers by points: if/else 22 (27 pts), boolean chains 22, ternaries 6 (8 pts) (nesting depth added 7). Most of this is not in the body itself: 10 of the 57 points are its own statements and the rest belongs to 14 function items inside it that branch (handleKeyDown, handleDragEnd, handleInputChange, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · profile.ApplicationProfile (cognitive 57) · ×1
  • profile.ApplicationProfile (cognitive 57) apps/web/src/features/settings/profile.tsx:110 — profile.ApplicationProfile has cognitive complexity 57 (threshold 15). Drivers by points: ternaries 23 (33 pts), boolean chains 20, error handling 2, if/else 2 (nesting depth added 10). Of this number, 38 points are the body's own statements and 19 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.
D2 · Cognitive Complexity · jobs.execute (cognitive 57) · ×1
  • jobs.execute (cognitive 57) packages/api/src/features/career/jobs.ts:541 — jobs.execute has cognitive complexity 57 (threshold 15). Drivers by points: if/else 17 (25 pts), ternaries 8 (17 pts), boolean chains 14, loops 1 (nesting depth added 17). Most of this is not in the body itself: 13 of the 57 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 642, 563). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · offers.OffersPage (cognitive 56) · ×1
  • offers.OffersPage (cognitive 56) apps/web/src/features/career/offers.tsx:223 — offers.OffersPage has cognitive complexity 56 (threshold 15). Drivers by points: ternaries 14 (26 pts), boolean chains 25, if/else 5 (nesting depth added 12). Of this number, 44 points are the body's own statements and 12 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.
D2 · Cognitive Complexity · improve.ImprovePanel (cognitive 56) · ×1
  • improve.ImprovePanel (cognitive 56) apps/web/src/features/resume/editor/write/improve.tsx:49 — improve.ImprovePanel has cognitive complexity 56 (threshold 15). Drivers by points: ternaries 15 (34 pts), boolean chains 11, if/else 5 (11 pts) (nesting depth added 25). Of this number, 37 points are the body's own statements and 19 belong to 7 function items inside it that branch. To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
D2 · Cognitive Complexity · PrepScreen.PrepScreen (cognitive 55) · ×1
  • PrepScreen.PrepScreen (cognitive 55) apps/mobile/src/features/workspace/PrepScreen.tsx:39 — PrepScreen.PrepScreen has cognitive complexity 55 (threshold 15). Drivers by points: ternaries 28 (43 pts), boolean chains 10, if/else 2 (nesting depth added 15). Of this number, 47 points are the body's own statements and 8 belong to 6 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · today.NewRoles (cognitive 55) · ×1
  • today.NewRoles (cognitive 55) apps/web/src/features/career/today.tsx:634 — today.NewRoles has cognitive complexity 55 (threshold 15). Drivers by points: ternaries 17 (27 pts), boolean chains 17, if/else 7 (8 pts), error handling 1 (2 pts), loops 1 (nesting depth added 12). Of this number, 33 points are the body's own statements and 22 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.
D2 · Cognitive Complexity · page-canvas.ResumePageCanvas (cognitive 55) · ×1
  • page-canvas.ResumePageCanvas (cognitive 55) apps/web/src/routes/builder/$resumeId/-components/page-canvas.tsx:71 — page-canvas.ResumePageCanvas has cognitive complexity 55 (threshold 15). Drivers by points: ternaries 21 (29 pts), boolean chains 21, if/else 5 (nesting depth added 8). Of this number, 41 points are the body's own statements and 14 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.
D2 · Cognitive Complexity · operators.summarizePageOperators (cognitive 54) · ×1
  • operators.summarizePageOperators (cognitive 54) packages/resume/src/ats-pdf/analyze/operators.ts:111 — operators.summarizePageOperators has cognitive complexity 54 (threshold 15). Drivers by points: if/else 18 (38 pts), ternaries 4 (10 pts), boolean chains 5, loops 1 (nesting depth added 26). Of this number, 53 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · parity.registerParityTools (cognitive 53) · ×1
  • parity.registerParityTools (cognitive 53) packages/mcp/src/parity.ts:394 — parity.registerParityTools has cognitive complexity 53 (threshold 15). Drivers by points: if/else 12 (27 pts), ternaries 5 (14 pts), loops 4 (9 pts), boolean chains 3 (nesting depth added 29). Most of this is not in the body itself: 6 of the 53 points are its own statements and the rest belongs to one function literal inside it that branches (line 414). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · pdf-lines.importLines (cognitive 51) · ×1
  • pdf-lines.importLines (cognitive 51) packages/import/src/pdf-lines.ts:1349 — pdf-lines.importLines has cognitive complexity 51 (threshold 15). Drivers by points: if/else 12 (25 pts), boolean chains 17, ternaries 3 (7 pts), loops 2 (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · markdown.resumeFactProposals (cognitive 51) · ×1
  • markdown.resumeFactProposals (cognitive 51) packages/resume/src/markdown.ts:50 — markdown.resumeFactProposals has cognitive complexity 51 (threshold 15). Drivers by points: ternaries 6 (22 pts), if/else 5 (16 pts), boolean chains 7, loops 3 (6 pts) (nesting depth added 30). Of this number, 50 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · values.valueSyntaxError (cognitive 51) · ×1
  • values.valueSyntaxError (cognitive 51) packages/resume/src/stylesheet/values.ts:376 — values.valueSyntaxError has cognitive complexity 51 (threshold 15). Drivers by points: if/else 18 (24 pts), ternaries 9 (18 pts), boolean chains 9 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · messages-merge.mergeClientToolResponses (cognitive 49) · ×1
  • messages-merge.mergeClientToolResponses (cognitive 49) packages/api/src/features/agent/messages-merge.ts:57 — messages-merge.mergeClientToolResponses has cognitive complexity 49 (threshold 15). Drivers by points: if/else 15 (36 pts), ternaries 2 (7 pts), boolean chains 5, loops 1 (nesting depth added 26). Most of this is not in the body itself: 9 of the 49 points are its own statements and the rest belongs to one function literal inside it that branches (line 90). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · generator.generateOpenApiSpec (cognitive 46) · ×1
  • generator.generateOpenApiSpec (cognitive 46) apps/server/src/openapi/generator.ts:126 — generator.generateOpenApiSpec has cognitive complexity 46 (threshold 15). Drivers by points: if/else 10 (29 pts), boolean chains 11, loops 3 (6 pts) (nesting depth added 22). Of this number, 41 points are the body's own statements and 5 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.
D2 · Cognitive Complexity · offers.requirementsFor (cognitive 46) · ×1
  • offers.requirementsFor (cognitive 46) apps/web/src/features/career/offers.tsx:1027 — offers.requirementsFor has cognitive complexity 46 (threshold 15). Drivers by points: ternaries 14 (39 pts), if/else 6 (7 pts) (nesting depth added 26). Of this number, 43 points are the body's own statements and 3 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.
D2 · Cognitive Complexity · use-resume-import.useResumeImport.importFile (cognitive 46) · ×1
  • use-resume-import.useResumeImport.importFile (cognitive 46) apps/web/src/features/documents/import/use-resume-import.ts:94 — use-resume-import.useResumeImport.importFile has cognitive complexity 46 (threshold 15). Drivers by points: if/else 15 (22 pts), boolean chains 11, ternaries 5 (10 pts), error handling 2 (3 pts) (nesting depth added 13). Of this number, 43 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.
D2 · Cognitive Complexity · letter-bar.LetterSaveStatus (cognitive 46) · ×1
  • letter-bar.LetterSaveStatus (cognitive 46) apps/web/src/routes/builder/letter/-components/letter-bar.tsx:257 — letter-bar.LetterSaveStatus has cognitive complexity 46 (threshold 15). Drivers by points: ternaries 14 (34 pts), boolean chains 7, if/else 4, error handling 1 (nesting depth added 20). Of this number, 41 points are the body's own statements and 5 belong to one function item inside it that branches. To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
D2 · Cognitive Complexity · document.resolveResumeEdits (cognitive 46) · ×1
  • document.resolveResumeEdits (cognitive 46) packages/api/src/features/agent/document.ts:548 — document.resolveResumeEdits has cognitive complexity 46 (threshold 15). Drivers by points: if/else 15 (29 pts), ternaries 5 (10 pts), loops 3, boolean chains 2, error handling 1 (2 pts) (nesting depth added 20). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ApplicationsScreen.ListView (cognitive 45) · ×1
  • ApplicationsScreen.ListView (cognitive 45) apps/mobile/src/features/applications/ApplicationsScreen.tsx:176 — ApplicationsScreen.ListView has cognitive complexity 45 (threshold 15). Drivers by points: ternaries 25 (28 pts), if/else 6 (7 pts), boolean chains 6, loops 2 (4 pts) (nesting depth added 6). Of this number, 24 points are the body's own statements and 21 belong to 11 function items inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · fields.TextField (cognitive 44) · ×1
  • fields.TextField (cognitive 44) apps/mobile/src/ui/fields.tsx:83 — fields.TextField has cognitive complexity 44 (threshold 15). Drivers by points: ternaries 25 (39 pts), boolean chains 5 (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · rich-text-markup.hasUnsupportedTableMarkup (cognitive 44) · ×1
  • rich-text-markup.hasUnsupportedTableMarkup (cognitive 44) apps/web/src/components/input/rich-text-markup.ts:373 — rich-text-markup.hasUnsupportedTableMarkup has cognitive complexity 44 (threshold 15). Drivers by points: if/else 15 (34 pts), loops 3 (5 pts), boolean chains 4, error handling 1 (nesting depth added 21). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · next-step.describeNextStep (cognitive 44) · ×1
  • next-step.describeNextStep (cognitive 44) apps/web/src/features/applications/next-step.ts:47 — next-step.describeNextStep has cognitive complexity 44 (threshold 15). Drivers by points: ternaries 16 (42 pts), boolean chains 1, match/switch 1 (nesting depth added 26). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
D2 · Cognitive Complexity · service.createAgent (cognitive 44) · ×1
  • service.createAgent (cognitive 44) packages/api/src/features/agent/service.ts:903 — service.createAgent has cognitive complexity 44 (threshold 15). Drivers by points: ternaries 13 (17 pts), if/else 9 (12 pts), loops 5 (10 pts), boolean chains 4, error handling 1 (nesting depth added 12). Of this number, 18 points are the body's own statements and 26 belong to 11 function items inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
D2 · Cognitive Complexity · assistant-screen.AssistantScreen (cognitive 43) · ×1
  • assistant-screen.AssistantScreen (cognitive 43) apps/mobile/src/features/builder/assistant/assistant-screen.tsx:47 — assistant-screen.AssistantScreen has cognitive complexity 43 (threshold 15). Drivers by points: ternaries 18 (21 pts), boolean chains 11, if/else 10, error handling 1 (nesting depth added 3). Of this number, 24 points are the body's own statements and 19 belong to 7 function items inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
D2 · Cognitive Complexity · generator.addCurlSamples (cognitive 43) · ×1
  • generator.addCurlSamples (cognitive 43) apps/server/src/openapi/generator.ts:265 — generator.addCurlSamples has cognitive complexity 43 (threshold 15). Drivers by points: ternaries 9 (27 pts), if/else 14 (21 pts), loops 4 (8 pts), boolean chains 7 (nesting depth added 29). To reduce it, split the body into named stages: move each independent 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 (generator.addCurlSamples::example) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D2 · Cognitive Complexity · sent-documents.SentDocuments (cognitive 43) · ×1
  • sent-documents.SentDocuments (cognitive 43) apps/web/src/features/applications/components/detail/sent-documents.tsx:60 — sent-documents.SentDocuments has cognitive complexity 43 (threshold 15). Drivers by points: boolean chains 24, ternaries 14 (19 pts) (nesting depth added 5). Of this number, 30 points are the body's own statements and 13 belong to 11 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · apply.ApplyTab (cognitive 43) · ×1
  • apply.ApplyTab (cognitive 43) apps/web/src/features/career/workspace/apply.tsx:80 — apply.ApplyTab has cognitive complexity 43 (threshold 15). Drivers by points: boolean chains 21, ternaries 12 (13 pts), if/else 9 (nesting depth added 1). Of this number, 22 points are the body's own statements and 21 belong to 15 function items inside it that branch. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · export-uploads.exportAccountUploads · ×1
  • export-uploads.exportAccountUploads::visit (cognitive 43) packages/api/src/features/auth/export-uploads.ts:22 — export-uploads.exportAccountUploads::visit has cognitive complexity 43 (threshold 15). Drivers by points: if/else 13 (30 pts), boolean chains 6, loops 2 (4 pts), error handling 1 (3 pts) (nesting depth added 21). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function. This shape REPEATS in the file: one other method here (export-uploads.exportAccountUploads) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D2 · Cognitive Complexity · import.ScopedImportScreen (cognitive 42) · ×1
  • import.ScopedImportScreen (cognitive 42) apps/mobile/src/features/documents/import.tsx:43 — import.ScopedImportScreen has cognitive complexity 42 (threshold 15). Drivers by points: ternaries 23 (38 pts), if/else 14 (17 pts), boolean chains 13, error handling 2 (nesting depth added 18). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (import.ScopedImportScreen::choose) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D2 · Cognitive Complexity · guest.invokeGuest (cognitive 41) · ×1
  • guest.invokeGuest (cognitive 41) apps/mobile/src/data/guest.ts:24 — guest.invokeGuest has cognitive complexity 41 (threshold 15). Drivers by points: if/else 19 (25 pts), boolean chains 11, ternaries 3 (5 pts) (nesting depth added 8). Of this number, 38 points are the body's own statements and 3 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · import.readImportFile (cognitive 41) · ×1
  • import.readImportFile (cognitive 41) apps/mobile/src/data/import.ts:93 — import.readImportFile has cognitive complexity 41 (threshold 15). Drivers by points: if/else 16 (29 pts), ternaries 2 (6 pts), boolean chains 5, error handling 1 (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · linking.parseDeepLink (cognitive 41) · ×1
  • linking.parseDeepLink (cognitive 41) apps/mobile/src/data/linking.ts:33 — linking.parseDeepLink has cognitive complexity 41 (threshold 15). Drivers by points: if/else 17 (20 pts), boolean chains 15, error handling 2 (3 pts), ternaries 2 (3 pts) (nesting depth added 5). Of this number, 40 points are the body's own statements and 1 belongs 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, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · activity-screen.ActivityScreen (cognitive 41) · ×1
  • activity-screen.ActivityScreen (cognitive 41) apps/mobile/src/features/builder/share/activity-screen.tsx:36 — activity-screen.ActivityScreen has cognitive complexity 41 (threshold 15). Drivers by points: ternaries 17 (36 pts), boolean chains 3, error handling 1, if/else 1 (nesting depth added 19). Of this number, 34 points are the body's own statements and 7 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.
D2 · Cognitive Complexity · facts.ScopedFactsScreen (cognitive 41) · ×1
  • facts.ScopedFactsScreen (cognitive 41) apps/mobile/src/features/career/facts.tsx:29 — facts.ScopedFactsScreen has cognitive complexity 41 (threshold 15). Drivers by points: ternaries 16 (22 pts), if/else 10, boolean chains 7, error handling 2 (nesting depth added 6). Of this number, 17 points are the body's own statements and 24 belong to 10 function items inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · list-view.ApplicationList (cognitive 41) · ×1
  • list-view.ApplicationList (cognitive 41) apps/web/src/features/applications/components/list-view.tsx:115 — list-view.ApplicationList has cognitive complexity 41 (threshold 15). Drivers by points: ternaries 10 (15 pts), boolean chains 14, if/else 12 (nesting depth added 5). Most of this is not in the body itself: 11 of the 41 points are its own statements and the rest belongs to 12 function items inside it that branch (a function literal at line 197, rowRef, header, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · error-message.getReadableErrorMessage (cognitive 41) · ×1
  • error-message.getReadableErrorMessage (cognitive 41) apps/web/src/libs/error-message.ts:24 — error-message.getReadableErrorMessage has cognitive complexity 41 (threshold 15). Drivers by points: if/else 14 (27 pts), boolean chains 10, loops 1 (3 pts), ternaries 1 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · builder.buildDocument (cognitive 41) · ×1
  • builder.buildDocument (cognitive 41) packages/docx/src/builder.ts:286 — builder.buildDocument has cognitive complexity 41 (threshold 15). Drivers by points: if/else 6 (13 pts), loops 4 (10 pts), boolean chains 9, ternaries 8 (9 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.
D2 · Cognitive Complexity · preview-screen.PreviewScreen (cognitive 40) · ×1
  • preview-screen.PreviewScreen (cognitive 40) apps/mobile/src/features/builder/preview/preview-screen.tsx:30 — preview-screen.PreviewScreen has cognitive complexity 40 (threshold 15). Drivers by points: ternaries 16 (21 pts), boolean chains 13, if/else 5, error handling 1 (nesting depth added 5). Of this number, 28 points are the body's own statements and 12 belong to 4 function items inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
D2 · Cognitive Complexity · provider-fields.ProviderFieldsForm (cognitive 40) · ×1
  • provider-fields.ProviderFieldsForm (cognitive 40) apps/web/src/features/settings/ai/provider-fields.tsx:50 — provider-fields.ProviderFieldsForm has cognitive complexity 40 (threshold 15). Drivers by points: boolean chains 26, ternaries 9 (13 pts), if/else 1 (nesting depth added 4). Of this number, 39 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · pages.LayoutPages (cognitive 40) · ×1
  • pages.LayoutPages (cognitive 40) apps/web/src/routes/builder/$resumeId/-sidebar/right/sections/layout/pages.tsx:109 — pages.LayoutPages has cognitive complexity 40 (threshold 15). Drivers by points: if/else 20 (26 pts), ternaries 6 (7 pts), boolean chains 6, loops 1 (nesting depth added 7). Most of this is not in the body itself: 7 of the 40 points are its own statements and the rest belongs to 7 function literals inside it that branch (lines 152, 131, 237, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · letter-page.LetterPage (cognitive 40) · ×1
  • letter-page.LetterPage (cognitive 40) apps/web/src/routes/builder/letter/-components/letter-page.tsx:45 — letter-page.LetterPage has cognitive complexity 40 (threshold 15). Drivers by points: ternaries 12 (22 pts), boolean chains 14, if/else 4 (nesting depth added 10). Of this number, 17 points are the body's own statements and 23 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.
D2 · Cognitive Complexity · prototype.fillControlledForm (cognitive 40) · ×1
  • prototype.fillControlledForm (cognitive 40) tooling/autofill/prototype.ts:38 — prototype.fillControlledForm has cognitive complexity 40 (threshold 15). Drivers by points: if/else 15 (21 pts), boolean chains 10, ternaries 4 (5 pts), error handling 1 (2 pts), loops 2 (nesting depth added 8). Of this number, 31 points are the body's own statements and 9 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.
D2 · Cognitive Complexity · EntryScreen.EntryScreen (cognitive 39) · ×1
  • EntryScreen.EntryScreen (cognitive 39) apps/mobile/src/features/builder/entry/EntryScreen.tsx:77 — EntryScreen.EntryScreen has cognitive complexity 39 (threshold 15). Drivers by points: ternaries 37 (73 pts), boolean chains 16, if/else 11 (13 pts), match/switch 1 (nesting depth added 38). To reduce it, split the body into named stages: move each independent 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 (EntryScreen.EntryScreen::render) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D2 · Cognitive Complexity · Recorder.Recorder (cognitive 39) · ×1
  • Recorder.Recorder (cognitive 39) apps/mobile/src/features/workspace/Recorder.tsx:43 — Recorder.Recorder has cognitive complexity 39 (threshold 15). Drivers by points: ternaries 14 (24 pts), if/else 8, boolean chains 7 (nesting depth added 10). Of this number, 32 points are the body's own statements and 7 belong to 6 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · application-form-sheet.ApplicationFormSheet (cognitive 39) · ×1
  • application-form-sheet.ApplicationFormSheet (cognitive 39) apps/web/src/features/applications/components/application-form-sheet.tsx:236 — application-form-sheet.ApplicationFormSheet has cognitive complexity 39 (threshold 15). Drivers by points: boolean chains 21, ternaries 8 (10 pts), if/else 8 (nesting depth added 2). Of this number, 18 points are the body's own statements and 21 belong to 8 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · save-posting.SavePosting (cognitive 39) · ×1
  • save-posting.SavePosting (cognitive 39) apps/web/src/features/assistant/save-posting.tsx:25 — save-posting.SavePosting has cognitive complexity 39 (threshold 15). Drivers by points: if/else 16 (20 pts), boolean chains 13, ternaries 2 (4 pts), error handling 2 (nesting depth added 6). Most of this is not in the body itself: 6 of the 39 points are its own statements and the rest belongs to 5 function items inside it that branch (save, a function literal at line 67, a function literal at line 71, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · stories.StoryEditor (cognitive 39) · ×1
  • stories.StoryEditor (cognitive 39) apps/web/src/features/career/knowledge/stories.tsx:523 — stories.StoryEditor has cognitive complexity 39 (threshold 15). Drivers by points: ternaries 16 (19 pts), boolean chains 18, if/else 2 (nesting depth added 3). Of this number, 19 points are the body's own statements and 20 belong to 9 function items inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
D2 · Cognitive Complexity · preview.browser.ResumePreviewClient (cognitive 39) · ×1
  • preview.browser.ResumePreviewClient (cognitive 39) apps/web/src/features/resume/preview/preview.browser.tsx:138 — preview.browser.ResumePreviewClient has cognitive complexity 39 (threshold 15). Drivers by points: ternaries 13 (18 pts), if/else 10 (12 pts), boolean chains 8, error handling 1 (nesting depth added 7). Most of this is not in the body itself: 4 of the 39 points are its own statements and the rest belongs to 9 function literals inside it that branch (lines 180, 298, 168, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · design-panel.DesignPanel (cognitive 39) · ×1
  • design-panel.DesignPanel (cognitive 39) apps/web/src/routes/builder/$resumeId/-components/design-panel.tsx:45 — design-panel.DesignPanel has cognitive complexity 39 (threshold 15). Drivers by points: boolean chains 17, ternaries 14 (17 pts), if/else 5 (nesting depth added 3). Of this number, 35 points are the body's own statements and 4 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.
D2 · Cognitive Complexity · notification-plan.notificationPlan (cognitive 38) · ×1
  • notification-plan.notificationPlan (cognitive 38) apps/mobile/src/data/notification-plan.ts:16 — notification-plan.notificationPlan has cognitive complexity 38 (threshold 15). Drivers by points: if/else 7 (16 pts), ternaries 4 (12 pts), loops 6 (8 pts), boolean chains 2 (nesting depth added 19). 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, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · messages.MessagesTab (cognitive 38) · ×1
  • messages.MessagesTab (cognitive 38) apps/web/src/features/career/workspace/messages.tsx:81 — messages.MessagesTab has cognitive complexity 38 (threshold 15). Drivers by points: boolean chains 20, ternaries 11 (15 pts), if/else 2, error handling 1 (nesting depth added 4). Of this number, 36 points are the body's own statements and 2 belong to 2 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · coach-chat.ChatView (cognitive 38) · ×1
  • coach-chat.ChatView (cognitive 38) apps/web/src/features/career/coach-chat.tsx:84 — coach-chat.ChatView has cognitive complexity 38 (threshold 15). Drivers by points: boolean chains 26, if/else 7 (9 pts), ternaries 2, loops 1 (nesting depth added 2). Of this number, 18 points are the body's own statements and 20 belong to 7 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · offers.useCells.<returned closure> (cognitive 38) · ×1
  • offers.useCells.<returned closure> (cognitive 38) apps/web/src/features/career/offers.tsx:921 — offers.useCells.<returned closure> has cognitive complexity 38 (threshold 15). Drivers by points: ternaries 22 (31 pts), boolean chains 4, if/else 3 (nesting depth added 9). Of this number, 25 points are the body's own statements and 13 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.
D2 · Cognitive Complexity · messages-persistence.applyStepToUiMessage (cognitive 38) · ×1
  • messages-persistence.applyStepToUiMessage (cognitive 38) packages/api/src/features/agent/messages-persistence.ts:168 — messages-persistence.applyStepToUiMessage has cognitive complexity 38 (threshold 15). Drivers by points: if/else 8 (16 pts), ternaries 4 (14 pts), boolean chains 7, loops 1 (nesting depth added 18). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ProviderScreen.ScopedProviderScreen (cognitive 37) · ×1
  • ProviderScreen.ScopedProviderScreen (cognitive 37) apps/mobile/src/features/settings/ProviderScreen.tsx:59 — ProviderScreen.ScopedProviderScreen has cognitive complexity 37 (threshold 15). Drivers by points: ternaries 15 (17 pts), boolean chains 11, if/else 5 (6 pts), error handling 3 (nesting depth added 3). Of this number, 17 points are the body's own statements and 20 belong to 7 function items inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
D2 · Cognitive Complexity · BottomSheet.BottomSheet (cognitive 37) · ×1
  • BottomSheet.BottomSheet (cognitive 37) apps/mobile/src/ui/BottomSheet.tsx:125 — BottomSheet.BottomSheet has cognitive complexity 37 (threshold 15). Drivers by points: if/else 20 (25 pts), ternaries 9, boolean chains 3 (nesting depth added 5). Most of this is not in the body itself: 9 of the 37 points are its own statements and the rest belongs to 12 function items inside it that branch (a function literal at line 174, releaseAt, finish, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · messages.ProposalCard (cognitive 37) · ×1
  • messages.ProposalCard (cognitive 37) apps/web/src/features/career/workspace/messages.tsx:625 — messages.ProposalCard has cognitive complexity 37 (threshold 15). Drivers by points: ternaries 31 (68 pts), boolean chains 29, if/else 11 (15 pts), error handling 2, match/switch 1 (nesting depth added 41). To reduce it, split the body into named stages: move each independent 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 (messages.ProposalCard::describe) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D2 · Cognitive Complexity · draft.flushResumeSave (cognitive 37) · ×1
  • draft.flushResumeSave (cognitive 37) apps/web/src/features/resume/builder/draft.ts:392 — draft.flushResumeSave has cognitive complexity 37 (threshold 15). Drivers by points: if/else 11 (14 pts), ternaries 6 (12 pts), boolean chains 10, error handling 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · service.submitAnswerSnapshot (cognitive 37) · ×1
  • service.submitAnswerSnapshot (cognitive 37) packages/api/src/features/career/service.ts:376 — service.submitAnswerSnapshot has cognitive complexity 37 (threshold 15). Drivers by points: if/else 16 (31 pts), boolean chains 6 (nesting depth added 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 into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · harvest.harvestPdfDocument (cognitive 37) · ×1
  • harvest.harvestPdfDocument (cognitive 37) packages/resume/src/ats-pdf/harvest.ts:253 — harvest.harvestPdfDocument has cognitive complexity 37 (threshold 15). Drivers by points: if/else 10 (26 pts), loops 3 (6 pts), ternaries 2 (3 pts), boolean chains 2 (nesting depth added 20). Of this number, 36 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · proposals.collectPassages (cognitive 37) · ×1
  • proposals.collectPassages (cognitive 37) packages/resume/src/proposals.ts:800 — proposals.collectPassages has cognitive complexity 37 (threshold 15). Drivers by points: if/else 6 (17 pts), ternaries 3 (11 pts), loops 3 (7 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.
D2 · Cognitive Complexity · main (cognitive 37) · ×1
  • main (cognitive 37) tooling/locales/catalog-diff.mjs:173 — main has cognitive complexity 37 (threshold 15). Drivers by points: loops 6 (16 pts), ternaries 3 (9 pts), if/else 3 (8 pts), error handling 2 (3 pts), boolean chains 1 (nesting depth added 22). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · InterviewSheet.InterviewForm (cognitive 36) · ×1
  • InterviewSheet.InterviewForm (cognitive 36) apps/mobile/src/features/applications/InterviewSheet.tsx:82 — InterviewSheet.InterviewForm has cognitive complexity 36 (threshold 15). Drivers by points: if/else 10 (13 pts), ternaries 12 (13 pts), boolean chains 10 (nesting depth added 4). Most of this is not in the body itself: 15 of the 36 points are its own statements and the rest belongs to 10 function items inside it that branch (save, pickWallTime, a function literal at line 129, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · resume.PublicResumeScreen (cognitive 36) · ×1
  • resume.PublicResumeScreen (cognitive 36) apps/mobile/src/features/public/resume.tsx:26 — resume.PublicResumeScreen has cognitive complexity 36 (threshold 15). Drivers by points: ternaries 13 (19 pts), boolean chains 8, if/else 6 (8 pts), error handling 1 (nesting depth added 8). Of this number, 24 points are the body's own statements and 12 belong to 4 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · rich-input-whitespace.markPastedHtml · ×1
  • rich-input-whitespace.markPastedHtml::normalize (cognitive 36) apps/web/src/components/input/rich-input-whitespace.ts:56 — rich-input-whitespace.markPastedHtml::normalize has cognitive complexity 36 (threshold 15). Drivers by points: if/else 9 (23 pts), loops 3 (9 pts), boolean chains 4 (nesting depth added 20). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · pdf-lines.pageToLines (cognitive 35) · ×1
  • pdf-lines.pageToLines (cognitive 35) packages/import/src/pdf-lines.ts:885 — pdf-lines.pageToLines has cognitive complexity 35 (threshold 15). Drivers by points: if/else 9 (16 pts), boolean chains 7, loops 4 (6 pts), ternaries 6 (nesting depth added 9). Of this number, 25 points are the body's own statements and 10 belong to 4 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · reactive-resume-v4-json.parseReactiveResumeV4JSON (cognitive 35) · ×1
  • reactive-resume-v4-json.parseReactiveResumeV4JSON (cognitive 35) packages/import/src/reactive-resume-v4-json.tsx:241 — reactive-resume-v4-json.parseReactiveResumeV4JSON has cognitive complexity 35 (threshold 15). Drivers by points: boolean chains 17, ternaries 8 (9 pts), if/else 5 (8 pts), error handling 1 (nesting depth added 4). Of this number, 19 points are the body's own statements and 16 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.
D2 · Cognitive Complexity · tree.buildItem (cognitive 35) · ×1
  • tree.buildItem (cognitive 35) packages/pdf/src/semantic/tree.ts:261 — tree.buildItem has cognitive complexity 35 (threshold 15). Drivers by points: ternaries 7 (12 pts), if/else 8 (11 pts), boolean chains 9, 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.
D2 · Cognitive Complexity · rich-text.RichText (cognitive 35) · ×1
  • rich-text.RichText (cognitive 35) packages/pdf/src/templates/shared/rich-text.tsx:81 — rich-text.RichText has cognitive complexity 35 (threshold 15). Drivers by points: ternaries 18 (21 pts), if/else 8 (9 pts), boolean chains 5 (nesting depth added 4). Most of this is not in the body itself: 9 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 240, renderText, renderView, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · extract.findGutter (cognitive 35) · ×1
  • extract.findGutter (cognitive 35) packages/resume/src/ats-pdf/extract.ts:246 — extract.findGutter has cognitive complexity 35 (threshold 15). Drivers by points: if/else 14 (22 pts), loops 5 (7 pts), boolean chains 5, ternaries 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · DetailScreen.NextStepHero (cognitive 34) · ×1
  • DetailScreen.NextStepHero (cognitive 34) apps/mobile/src/features/applications/DetailScreen.tsx:292 — DetailScreen.NextStepHero has cognitive complexity 34 (threshold 15). Drivers by points: ternaries 10 (24 pts), if/else 4, boolean chains 3, loops 1 (3 pts) (nesting depth added 16). Of this number, 28 points are the body's own statements and 6 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · trash.ScopedTrashScreen (cognitive 34) · ×1
  • trash.ScopedTrashScreen (cognitive 34) apps/mobile/src/features/documents/trash.tsx:35 — trash.ScopedTrashScreen has cognitive complexity 34 (threshold 15). Drivers by points: ternaries 11 (14 pts), if/else 11 (13 pts), boolean chains 5, error handling 2 (nesting depth added 5). Most of this is not in the body itself: 11 of the 34 points are its own statements and the rest belongs to 7 function items inside it that branch (remove, restoreItem, a function literal at line 77, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · picture-settings.PictureSettings (cognitive 34) · ×1
  • picture-settings.PictureSettings (cognitive 34) apps/web/src/features/resume/editor/write/picture-settings.tsx:589 — picture-settings.PictureSettings has cognitive complexity 34 (threshold 15). Drivers by points: if/else 13 (14 pts), boolean chains 11, ternaries 7 (8 pts), error handling 1 (nesting depth added 2). Most of this is not in the body itself: 12 of the 34 points are its own statements and the rest belongs to 11 function items inside it that branch (onUploadPicture, onDeletePicture, a function literal at line 640, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · outline.SectionRowBody (cognitive 34) · ×1
  • outline.SectionRowBody (cognitive 34) apps/web/src/features/resume/editor/write/outline.tsx:282 — outline.SectionRowBody has cognitive complexity 34 (threshold 15). Drivers by points: ternaries 13 (23 pts), boolean chains 9, if/else 2 (nesting depth added 10). Of this number, 29 points are the body's own statements and 5 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.
D2 · Cognitive Complexity · context.collapseOldestToolPairs (cognitive 34) · ×1
  • context.collapseOldestToolPairs (cognitive 34) packages/api/src/features/agent/context.ts:211 — context.collapseOldestToolPairs has cognitive complexity 34 (threshold 15). Drivers by points: if/else 9 (19 pts), boolean chains 7, loops 4 (5 pts), ternaries 2 (3 pts) (nesting depth added 12). Of this number, 23 points are the body's own statements and 11 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · config.linkAnonymousAccount (cognitive 34) · ×1
  • config.linkAnonymousAccount (cognitive 34) packages/auth/src/config.ts:361 — config.linkAnonymousAccount has cognitive complexity 34 (threshold 15). Drivers by points: if/else 11 (15 pts), ternaries 5 (8 pts), boolean chains 5, error handling 2 (3 pts), loops 3 (nesting depth added 8). Most of this is not in the body itself: 2 of the 34 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 370, 534, 557). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · pdf-lines.bodyColumns (cognitive 34) · ×1
  • pdf-lines.bodyColumns (cognitive 34) packages/import/src/pdf-lines.ts:784 — pdf-lines.bodyColumns has cognitive complexity 34 (threshold 15). Drivers by points: if/else 8 (19 pts), boolean chains 9, loops 4 (6 pts) (nesting depth added 13). Of this number, 30 points are the body's own statements and 4 belong to 6 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ai-consent.authorizeAiRequest.result (cognitive 33) · ×1
  • ai-consent.authorizeAiRequest.result (cognitive 33) apps/mobile/src/api/ai-consent.ts:203 — ai-consent.authorizeAiRequest.result has cognitive complexity 33 (threshold 15). Drivers by points: ternaries 13 (24 pts), boolean chains 6, if/else 3 (nesting depth added 11). Of this number, 27 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.
D2 · Cognitive Complexity · stories.StoryScreen (cognitive 33) · ×1
  • stories.StoryScreen (cognitive 33) apps/mobile/src/features/career/stories.tsx:56 — stories.StoryScreen has cognitive complexity 33 (threshold 15). Drivers by points: ternaries 11 (23 pts), if/else 5, boolean chains 4, error handling 1 (nesting depth added 12). Most of this is not in the body itself: 8 of the 33 points are its own statements and the rest belongs to 4 function items inside it that branch (a function literal at line 188, save, a function literal at line 141, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · rows.ListRow (cognitive 33) · ×1
  • rows.ListRow (cognitive 33) apps/mobile/src/ui/rows.tsx:223 — rows.ListRow has cognitive complexity 33 (threshold 15). Drivers by points: ternaries 21 (29 pts), boolean chains 3, if/else 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · combobox.Combobox (cognitive 33) · ×1
  • combobox.Combobox (cognitive 33) apps/web/src/components/ui/combobox.tsx:88 — combobox.Combobox has cognitive complexity 33 (threshold 15). Drivers by points: ternaries 13 (19 pts), boolean chains 7, if/else 6 (7 pts) (nesting depth added 7). Most of this is not in the body itself: 12 of the 33 points are its own statements and the rest belongs to 5 function items inside it that branch (handleExternalChange, findOption, filter, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · use-application-actions.useApplicationActions (cognitive 33) · ×1
  • use-application-actions.useApplicationActions (cognitive 33) apps/web/src/features/applications/use-application-actions.ts:230 — use-application-actions.useApplicationActions has cognitive complexity 33 (threshold 15). Drivers by points: ternaries 14 (22 pts), if/else 5 (6 pts), boolean chains 5 (nesting depth added 9). None of this is in the body itself: all 33 points belong to 5 function literals inside it that branch (lines 275, 240, 256, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · question-card.QuestionCard (cognitive 33) · ×1
  • question-card.QuestionCard (cognitive 33) apps/web/src/features/assistant/question-card.tsx:25 — question-card.QuestionCard has cognitive complexity 33 (threshold 15). Drivers by points: ternaries 9 (21 pts), boolean chains 9, if/else 3 (nesting depth added 12). Of this number, 31 points are the body's own statements and 2 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.
D2 · Cognitive Complexity · coach-sheet.CoachSheetBody (cognitive 33) · ×1
  • coach-sheet.CoachSheetBody (cognitive 33) apps/web/src/features/career/workspace/coach-sheet.tsx:113 — coach-sheet.CoachSheetBody has cognitive complexity 33 (threshold 15). Drivers by points: boolean chains 17, ternaries 10 (11 pts), if/else 4, error handling 1 (nesting depth added 1). Of this number, 27 points are the body's own statements and 6 belong to 6 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · preferences.PreferencesForm (cognitive 33) · ×1
  • preferences.PreferencesForm (cognitive 33) apps/web/src/features/career/knowledge/preferences.tsx:84 — preferences.PreferencesForm has cognitive complexity 33 (threshold 15). Drivers by points: ternaries 15 (20 pts), boolean chains 10, if/else 3 (nesting depth added 5). Of this number, 25 points are the body's own statements and 8 belong to 8 function literals inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
D2 · Cognitive Complexity · section-view.SectionOptions (cognitive 33) · ×1
  • section-view.SectionOptions (cognitive 33) apps/web/src/features/resume/editor/write/section-view.tsx:269 — section-view.SectionOptions has cognitive complexity 33 (threshold 15). Drivers by points: boolean chains 12, ternaries 9 (11 pts), if/else 9, loops 1 (nesting depth added 2). Most of this is not in the body itself: 15 of the 33 points are its own statements and the rest belongs to 10 function items inside it that branch (a function literal at line 313, a function literal at line 318, rename, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · files.isValidFontFile (cognitive 33) · ×1
  • files.isValidFontFile (cognitive 33) packages/fonts/src/files.ts:95 — files.isValidFontFile has cognitive complexity 33 (threshold 15). Drivers by points: if/else 10 (16 pts), boolean chains 8, loops 5 (8 pts), error handling 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · selector.compileSimple (cognitive 33) · ×1
  • selector.compileSimple (cognitive 33) packages/resume/src/stylesheet/selector.ts:179 — selector.compileSimple has cognitive complexity 33 (threshold 15). Drivers by points: if/else 12 (27 pts), boolean chains 5, match/switch 1 (nesting depth added 15). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
D2 · Cognitive Complexity · cascade.structuralValue (cognitive 33) · ×1
  • cascade.structuralValue (cognitive 33) packages/resume/src/stylesheet/cascade.ts:504 — cascade.structuralValue has cognitive complexity 33 (threshold 15). Drivers by points: if/else 21 (28 pts), boolean chains 5 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · letter-screen.LetterScreen (cognitive 32) · ×1
  • letter-screen.LetterScreen (cognitive 32) apps/mobile/src/features/letters/letter-screen.tsx:30 — letter-screen.LetterScreen has cognitive complexity 32 (threshold 15). Drivers by points: ternaries 9 (18 pts), boolean chains 12, if/else 2 (nesting depth added 9). 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, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · FitScreen.FitScreen (cognitive 32) · ×1
  • FitScreen.FitScreen (cognitive 32) apps/mobile/src/features/workspace/FitScreen.tsx:45 — FitScreen.FitScreen has cognitive complexity 32 (threshold 15). Drivers by points: ternaries 20 (26 pts), boolean chains 5, if/else 1 (nesting depth added 6). Of this number, 23 points are the body's own statements and 9 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.
D2 · Cognitive Complexity · conversation.Composer (cognitive 32) · ×1
  • conversation.Composer (cognitive 32) apps/web/src/features/assistant/conversation.tsx:1077 — conversation.Composer has cognitive complexity 32 (threshold 15). Drivers by points: boolean chains 14, if/else 9 (10 pts), ternaries 6 (7 pts), error handling 1 (nesting depth added 2). Most of this is not in the body itself: 11 of the 32 points are its own statements and the rest belongs to 8 function items inside it that branch (upload, attachPaste, submit, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · resumes.RootMatches (cognitive 32) · ×1
  • resumes.RootMatches (cognitive 32) apps/web/src/features/command-palette/pages/resumes.tsx:99 — resumes.RootMatches has cognitive complexity 32 (threshold 15). Drivers by points: ternaries 5 (15 pts), boolean chains 13, if/else 4 (nesting depth added 10). Of this number, 28 points are the body's own statements and 4 belong to 2 function items inside it that branch. To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
D2 · Cognitive Complexity · profile.ProfileDialog (cognitive 32) · ×1
  • profile.ProfileDialog (cognitive 32) apps/web/src/features/settings/profile.tsx:467 — profile.ProfileDialog has cognitive complexity 32 (threshold 15). Drivers by points: boolean chains 18, if/else 5 (6 pts), ternaries 5 (6 pts), error handling 1, loops 1 (nesting depth added 2). Of this number, 21 points are the body's own statements and 11 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.
D2 · Cognitive Complexity · design-panel.LetterDesignPanel (cognitive 32) · ×1
  • design-panel.LetterDesignPanel (cognitive 32) apps/web/src/routes/builder/letter/-components/design-panel.tsx:70 — design-panel.LetterDesignPanel has cognitive complexity 32 (threshold 15). Drivers by points: ternaries 12 (23 pts), boolean chains 7, if/else 2 (nesting depth added 11). Of this number, 27 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.
D2 · Cognitive Complexity · json-resume.convertJSONResume (cognitive 32) · ×1
  • json-resume.convertJSONResume (cognitive 32) packages/import/src/json-resume.tsx:162 — json-resume.convertJSONResume has cognitive complexity 32 (threshold 15). Drivers by points: boolean chains 32. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · pdf-lines.educationRecords (cognitive 32) · ×1
  • pdf-lines.educationRecords (cognitive 32) packages/import/src/pdf-lines.ts:1700 — pdf-lines.educationRecords has cognitive complexity 32 (threshold 15). Drivers by points: if/else 9 (14 pts), ternaries 5 (10 pts), boolean chains 6, loops 2 (nesting depth added 10). Of this number, 23 points are the body's own statements and 9 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.
D2 · Cognitive Complexity · html-to-odt.processBlock (cognitive 32) · ×1
  • html-to-odt.processBlock (cognitive 32) packages/odt/src/html-to-odt.ts:162 — html-to-odt.processBlock has cognitive complexity 32 (threshold 15). Drivers by points: if/else 12 (21 pts), ternaries 3 (5 pts), loops 2 (4 pts), boolean chains 2 (nesting depth added 13). Of this number, 28 points are the body's own statements and 4 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · next-step.getNextStep (cognitive 32) · ×1
  • next-step.getNextStep (cognitive 32) packages/schema/src/applications/next-step.ts:76 — next-step.getNextStep has cognitive complexity 32 (threshold 15). Drivers by points: if/else 10 (12 pts), ternaries 8 (12 pts), boolean chains 8 (nesting depth added 6). Of this number, 26 points are the body's own statements and 6 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · content.captureDocument · ×1
  • content.captureDocument::visit (cognitive 32) tooling/capture/content.ts:25 — content.captureDocument::visit has cognitive complexity 32 (threshold 15). Drivers by points: if/else 12 (20 pts), boolean chains 5, ternaries 3 (5 pts), loops 2 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · application-detail-sheet.Detail (cognitive 31) · ×1
  • application-detail-sheet.Detail (cognitive 31) apps/web/src/features/applications/components/application-detail-sheet.tsx:206 — application-detail-sheet.Detail has cognitive complexity 31 (threshold 15). Drivers by points: boolean chains 17, ternaries 7 (8 pts), if/else 6 (nesting depth added 1). Most of this is not in the body itself: 13 of the 31 points are its own statements and the rest belongs to 8 function items inside it that branch (goTo, reachedOn, a function literal at line 495, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · manage-lanes-sheet.LaneRow (cognitive 31) · ×1
  • manage-lanes-sheet.LaneRow (cognitive 31) apps/web/src/features/applications/components/manage-lanes-sheet.tsx:277 — manage-lanes-sheet.LaneRow has cognitive complexity 31 (threshold 15). Drivers by points: if/else 8 (11 pts), ternaries 7 (11 pts), boolean chains 9 (nesting depth added 7). Of this number, 16 points are the body's own statements and 15 belong to 4 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · fit.RequirementRow (cognitive 31) · ×1
  • fit.RequirementRow (cognitive 31) apps/web/src/features/career/workspace/fit.tsx:502 — fit.RequirementRow has cognitive complexity 31 (threshold 15). Drivers by points: ternaries 13 (20 pts), boolean chains 11 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · transcript.transcriptOf (cognitive 31) · ×1
  • transcript.transcriptOf (cognitive 31) packages/ai/src/tools/transcript.ts:33 — transcript.transcriptOf has cognitive complexity 31 (threshold 15). Drivers by points: if/else 8 (19 pts), ternaries 3 (6 pts), boolean chains 5, loops 1 (nesting depth added 14). None of this is in the body itself: all 31 points belong to one function literal inside it that branches (line 43). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · service.linkLetterApplication (cognitive 31) · ×1
  • service.linkLetterApplication (cognitive 31) packages/api/src/features/cover-letters/service.ts:251 — service.linkLetterApplication has cognitive complexity 31 (threshold 15). Drivers by points: if/else 9 (21 pts), ternaries 3 (4 pts), boolean chains 3, loops 2 (3 pts) (nesting depth added 14). Of this number, 29 points are the body's own statements and 2 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.
D2 · Cognitive Complexity · to-html.cssValue (cognitive 31) · ×1
  • to-html.cssValue (cognitive 31) packages/pdf/src/html/to-html.ts:92 — to-html.cssValue has cognitive complexity 31 (threshold 15). Drivers by points: ternaries 8 (16 pts), if/else 11 (13 pts), boolean chains 2 (nesting depth added 10). Of this number, 25 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.
D2 · Cognitive Complexity · share-screen.ShareScreen (cognitive 30) · ×1
  • share-screen.ShareScreen (cognitive 30) apps/mobile/src/features/builder/share/share-screen.tsx:35 — share-screen.ShareScreen has cognitive complexity 30 (threshold 15). Drivers by points: ternaries 9 (11 pts), if/else 8 (9 pts), boolean chains 8, error handling 2 (nesting depth added 3). Most of this is not in the body itself: 12 of the 30 points are its own statements and the rest belongs to 7 function items inside it that branch (share, goLive, setPublic, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · PracticeScreen.PracticeScreen (cognitive 30) · ×1
  • PracticeScreen.PracticeScreen (cognitive 30) apps/mobile/src/features/workspace/PracticeScreen.tsx:30 — PracticeScreen.PracticeScreen has cognitive complexity 30 (threshold 15). Drivers by points: ternaries 17 (27 pts), boolean chains 2, if/else 1 (nesting depth added 10). Of this number, 28 points are the body's own statements and 2 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.
D2 · Cognitive Complexity · contacts.ContactList (cognitive 30) · ×1
  • contacts.ContactList (cognitive 30) apps/web/src/features/applications/components/detail/contacts.tsx:142 — contacts.ContactList has cognitive complexity 30 (threshold 15). Drivers by points: boolean chains 14, ternaries 8 (12 pts), if/else 4 (nesting depth added 4). 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 items inside it that branch (save, a function literal at line 227, a function literal at line 240, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · manage-lanes-sheet.ManageLanesSheet (cognitive 30) · ×1
  • manage-lanes-sheet.ManageLanesSheet (cognitive 30) apps/web/src/features/applications/components/manage-lanes-sheet.tsx:65 — manage-lanes-sheet.ManageLanesSheet has cognitive complexity 30 (threshold 15). Drivers by points: boolean chains 11, ternaries 5 (11 pts), if/else 4 (7 pts), loops 1 (nesting depth added 9). Most of this is not in the body itself: 13 of the 30 points are its own statements and the rest belongs to 7 function items inside it that branch (a function literal at line 72, reorder, a function literal at line 93, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · proposal-list.ChangeSet (cognitive 30) · ×1
  • proposal-list.ChangeSet (cognitive 30) apps/web/src/features/resume/editor/proposals/proposal-list.tsx:144 — proposal-list.ChangeSet has cognitive complexity 30 (threshold 15). Drivers by points: boolean chains 16, if/else 9, ternaries 5. Most of this is not in the body itself: 12 of the 30 points are its own statements and the rest belongs to 6 function items inside it that branch (onKeyDown, a function literal at line 234, a function literal at line 250, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · save-status.SaveStatus (cognitive 30) · ×1
  • save-status.SaveStatus (cognitive 30) apps/web/src/features/resume/editor/save-status.tsx:46 — save-status.SaveStatus has cognitive complexity 30 (threshold 15). Drivers by points: ternaries 8 (21 pts), boolean chains 7, error handling 1, if/else 1 (nesting depth added 13). Of this number, 28 points are the body's own statements and 2 belong to one function item inside it that branches. To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
D2 · Cognitive Complexity · providers.ProviderRow (cognitive 30) · ×1
  • providers.ProviderRow (cognitive 30) apps/web/src/features/settings/ai/providers.tsx:278 — providers.ProviderRow has cognitive complexity 30 (threshold 15). Drivers by points: ternaries 13 (20 pts), boolean chains 8, if/else 2 (nesting depth added 7). Of this number, 28 points are the body's own statements and 2 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.
D2 · Cognitive Complexity · draft.draftLetterBody (cognitive 30) · ×1
  • draft.draftLetterBody (cognitive 30) packages/api/src/features/cover-letters/draft.ts:64 — draft.draftLetterBody has cognitive complexity 30 (threshold 15). Drivers by points: if/else 12 (14 pts), ternaries 9 (12 pts), boolean chains 2, error handling 1, loops 1 (nesting depth added 5). Most of this is not in the body itself: 14 of the 30 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 137, 92, 114). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · legacy-converter.activeSlotChunks (cognitive 30) · ×1
  • legacy-converter.activeSlotChunks (cognitive 30) packages/pdf/src/semantic/legacy-converter.ts:177 — legacy-converter.activeSlotChunks has cognitive complexity 30 (threshold 15). Drivers by points: if/else 11 (16 pts), boolean chains 13, ternaries 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ngrams.buildNgrams (cognitive 30) · ×1
  • ngrams.buildNgrams (cognitive 30) packages/resume/src/ats-pdf/jd/ngrams.ts:18 — ngrams.buildNgrams has cognitive complexity 30 (threshold 15). Drivers by points: if/else 7 (20 pts), boolean chains 7, loops 2 (3 pts) (nesting depth added 14). Of this number, 26 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.
D2 · Cognitive Complexity · BasicsScreen.BasicsScreen (cognitive 29) · ×1
  • BasicsScreen.BasicsScreen (cognitive 29) apps/mobile/src/features/builder/basics/BasicsScreen.tsx:73 — BasicsScreen.BasicsScreen has cognitive complexity 29 (threshold 15). Drivers by points: ternaries 14 (18 pts), if/else 5 (6 pts), boolean chains 4, error handling 1 (nesting depth added 5). Of this number, 16 points are the body's own statements and 13 belong to 3 function items inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · ats.ATSCheckerScreen (cognitive 29) · ×1
  • ats.ATSCheckerScreen (cognitive 29) apps/mobile/src/features/public/ats.tsx:22 — ats.ATSCheckerScreen has cognitive complexity 29 (threshold 15). Drivers by points: ternaries 11 (21 pts), if/else 4 (5 pts), error handling 2, boolean chains 1 (nesting depth added 11). Most of this is not in the body itself: 14 of the 29 points are its own statements and the rest belongs to 2 function items inside it that branch (choose, a function literal at line 86). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · BoardDrag.BoardDrag (cognitive 29) · ×1
  • BoardDrag.BoardDrag (cognitive 29) apps/mobile/src/ui/BoardDrag.tsx:85 — BoardDrag.BoardDrag has cognitive complexity 29 (threshold 15). Drivers by points: if/else 15, boolean chains 7, ternaries 5 (7 pts) (nesting depth added 2). Most of this is not in the body itself: 1 of the 29 points is its own statement and the rest belongs to 10 function items inside it that branch (a function literal at line 209, drop, a function literal at line 240, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · SwipeRow.SwipeRow (cognitive 29) · ×1
  • SwipeRow.SwipeRow (cognitive 29) apps/mobile/src/ui/SwipeRow.tsx:58 — SwipeRow.SwipeRow has cognitive complexity 29 (threshold 15). Drivers by points: ternaries 10 (14 pts), if/else 9 (12 pts), boolean chains 3 (nesting depth added 7). Most of this is not in the body itself: 5 of the 29 points are its own statements and the rest belongs to 7 function items inside it that branch (a function literal at line 88, a function literal at line 79, a function literal at line 111, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · insights-view.uiFontFace (cognitive 29) · ×1
  • insights-view.uiFontFace (cognitive 29) apps/web/src/features/applications/components/insights-view.tsx:323 — insights-view.uiFontFace has cognitive complexity 29 (threshold 15). Drivers by points: if/else 7 (19 pts), error handling 2 (5 pts), loops 2 (3 pts), boolean chains 2 (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · consent.OAuthConsentPage (cognitive 29) · ×1
  • consent.OAuthConsentPage (cognitive 29) apps/web/src/features/auth/pages/consent.tsx:54 — consent.OAuthConsentPage has cognitive complexity 29 (threshold 15). Drivers by points: boolean chains 19, if/else 7, ternaries 2 (3 pts) (nesting depth added 1). Of this number, 23 points are the body's own statements and 6 belong to 2 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · facts.FactsPage (cognitive 29) · ×1
  • facts.FactsPage (cognitive 29) apps/web/src/features/career/knowledge/facts.tsx:59 — facts.FactsPage has cognitive complexity 29 (threshold 15). Drivers by points: boolean chains 21, ternaries 5 (6 pts), if/else 2 (nesting depth added 1). Of this number, 20 points are the body's own statements and 9 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.
D2 · Cognitive Complexity · writing-tab.WritingTab (cognitive 29) · ×1
  • writing-tab.WritingTab (cognitive 29) apps/web/src/features/resume/editor/check/writing-tab.tsx:49 — writing-tab.WritingTab has cognitive complexity 29 (threshold 15). Drivers by points: boolean chains 15, if/else 9, ternaries 4 (5 pts) (nesting depth added 1). Of this number, 21 points are the body's own statements and 8 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.
D2 · Cognitive Complexity · chrome.usePageScale (cognitive 29) · ×1
  • chrome.usePageScale (cognitive 29) apps/web/src/features/resume/editor/chrome.tsx:84 — chrome.usePageScale has cognitive complexity 29 (threshold 15). Drivers by points: if/else 10 (12 pts), ternaries 9 (11 pts), boolean chains 6 (nesting depth added 4). Most of this is not in the body itself: 6 of the 29 points are its own statements and the rest belongs to 5 function literals inside it that branch (lines 119, 196, 115, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · tree.partMatchesOwner (cognitive 29) · ×1
  • tree.partMatchesOwner (cognitive 29) packages/pdf/src/semantic/tree.ts:688 — tree.partMatchesOwner has cognitive complexity 29 (threshold 15). Drivers by points: if/else 14 (17 pts), boolean chains 11, ternaries 1 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
D2 · Cognitive Complexity · account-zip.buildAccountZip (cognitive 29) · ×1
  • account-zip.buildAccountZip (cognitive 29) packages/utils/src/account-zip.ts:72 — account-zip.buildAccountZip has cognitive complexity 29 (threshold 15). Drivers by points: if/else 11 (17 pts), loops 5 (6 pts), boolean chains 4, ternaries 1 (2 pts) (nesting depth added 8). Of this number, 25 points are the body's own statements and 4 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.
D2 · Cognitive Complexity · queue.createWriteQueue.flush (cognitive 28) · ×1
  • queue.createWriteQueue.flush (cognitive 28) apps/mobile/src/data/queue.ts:144 — queue.createWriteQueue.flush has cognitive complexity 28 (threshold 15). Drivers by points: if/else 7 (17 pts), loops 2 (4 pts), ternaries 1 (3 pts), boolean chains 2, error handling 1 (2 pts) (nesting depth added 15). Most of this is not in the body itself: 1 of the 28 points is its own statement and the rest belongs to 2 function literals inside it that branch (lines 149, 162). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · AIScreen.AIScreen (cognitive 28) · ×1
  • AIScreen.AIScreen (cognitive 28) apps/mobile/src/features/settings/AIScreen.tsx:33 — AIScreen.AIScreen has cognitive complexity 28 (threshold 15). Drivers by points: ternaries 15 (20 pts), boolean chains 6, error handling 1, if/else 1 (nesting depth added 5). Most of this is not in the body itself: 8 of the 28 points are its own statements and the rest belongs to 2 function items inside it that branch (a function literal at line 78, testAgain). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · SignOutDialog.SignOutDialog (cognitive 28) · ×1
  • SignOutDialog.SignOutDialog (cognitive 28) apps/mobile/src/features/settings/SignOutDialog.tsx:15 — SignOutDialog.SignOutDialog has cognitive complexity 28 (threshold 15). Drivers by points: ternaries 9 (20 pts), error handling 4, if/else 3, boolean chains 1 (nesting depth added 11). Of this number, 20 points are the body's own statements and 8 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.
D2 · Cognitive Complexity · use-application-actions.useMoveWithUndo.<returned closure> (cognitive 28) · ×1
  • use-application-actions.useMoveWithUndo.<returned closure> (cognitive 28) apps/web/src/features/applications/use-application-actions.ts:74 — use-application-actions.useMoveWithUndo.<returned closure> has cognitive complexity 28 (threshold 15). Drivers by points: if/else 8 (9 pts), loops 6 (7 pts), boolean chains 6, ternaries 4, error handling 2 (nesting depth added 2). Most of this is not in the body itself: 6 of the 28 points are its own statements and the rest belongs to 10 function items inside it that branch (a function literal at line 148, restore, a function literal at line 126, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · verify-2fa.TwoFactorVerificationPage (cognitive 28) · ×1
  • verify-2fa.TwoFactorVerificationPage (cognitive 28) apps/web/src/features/auth/pages/verify-2fa.tsx:39 — verify-2fa.TwoFactorVerificationPage has cognitive complexity 28 (threshold 15). Drivers by points: ternaries 13 (14 pts), if/else 7 (9 pts), boolean chains 5 (nesting depth added 3). Most of this is not in the body itself: 5 of the 28 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 51, 130, 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.
D2 · Cognitive Complexity · sessions.describeAgent (cognitive 28) · ×1
  • sessions.describeAgent (cognitive 28) apps/web/src/features/settings/account/sessions.tsx:15 — sessions.describeAgent has cognitive complexity 28 (threshold 15). Drivers by points: ternaries 9 (25 pts), if/else 2, boolean chains 1 (nesting depth added 16). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
D2 · Cognitive Complexity · packet.snapshot (cognitive 28) · ×1
  • packet.snapshot (cognitive 28) packages/api/src/features/applications/packet.ts:33 — packet.snapshot has cognitive complexity 28 (threshold 15). Drivers by points: if/else 11 (16 pts), boolean chains 6, ternaries 6 (nesting depth added 5). Of this number, 25 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.
D2 · Cognitive Complexity · store.createDraftStore.writeMetadata (cognitive 27) · ×1
  • store.createDraftStore.writeMetadata (cognitive 27) apps/mobile/src/data/draft/store.ts:581 — store.createDraftStore.writeMetadata has cognitive complexity 27 (threshold 15). Drivers by points: if/else 12 (17 pts), boolean chains 7, error handling 1, loops 1, ternaries 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ProfileScreen.ProfileScreen (cognitive 27) · ×1
  • ProfileScreen.ProfileScreen (cognitive 27) apps/mobile/src/features/settings/ProfileScreen.tsx:19 — ProfileScreen.ProfileScreen has cognitive complexity 27 (threshold 15). Drivers by points: ternaries 11 (20 pts), if/else 5, boolean chains 1, error handling 1 (nesting depth added 9). Most of this is not in the body itself: 11 of the 27 points are its own statements and the rest belongs to 4 function items inside it that branch (save, a function literal at line 51, a function literal at line 32, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · next-step.describeNextStepLine (cognitive 27) · ×1
  • next-step.describeNextStepLine (cognitive 27) apps/web/src/features/applications/next-step.ts:193 — next-step.describeNextStepLine has cognitive complexity 27 (threshold 15). Drivers by points: ternaries 10 (21 pts), boolean chains 3, if/else 1 (2 pts), match/switch 1 (nesting depth added 12). Of this number, 25 points are the body's own statements and 2 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.
D2 · Cognitive Complexity · checker.Result (cognitive 27) · ×1
  • checker.Result (cognitive 27) apps/web/src/features/ats-checker/checker.tsx:397 — checker.Result has cognitive complexity 27 (threshold 15). Drivers by points: boolean chains 14, ternaries 8 (13 pts) (nesting depth added 5). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · recorder.parse (cognitive 27) · ×1
  • recorder.parse (cognitive 27) apps/web/src/features/career/workspace/recorder.ts:235 — recorder.parse has cognitive complexity 27 (threshold 15). Drivers by points: if/else 9 (19 pts), boolean chains 7, loops 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · stories.StoriesPage (cognitive 27) · ×1
  • stories.StoriesPage (cognitive 27) apps/web/src/features/career/knowledge/stories.tsx:77 — stories.StoriesPage has cognitive complexity 27 (threshold 15). Drivers by points: ternaries 10 (15 pts), boolean chains 8, if/else 4 (nesting depth added 5). Of this number, 26 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · offers.Questions (cognitive 27) · ×1
  • offers.Questions (cognitive 27) apps/web/src/features/career/offers.tsx:1167 — offers.Questions has cognitive complexity 27 (threshold 15). Drivers by points: ternaries 14 (22 pts), boolean chains 3, error handling 1, if/else 1 (nesting depth added 8). Most of this is not in the body itself: 11 of the 27 points are its own statements and the rest belongs to 6 function items inside it that branch (a function literal at line 1253, a function literal at line 1277, ask, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · page-layer.CheckPageLayer (cognitive 27) · ×1
  • page-layer.CheckPageLayer (cognitive 27) apps/web/src/features/resume/editor/check/page-layer.tsx:97 — page-layer.CheckPageLayer has cognitive complexity 27 (threshold 15). Drivers by points: ternaries 8 (12 pts), boolean chains 8, if/else 5 (7 pts) (nesting depth added 6). Most of this is not in the body itself: 7 of the 27 points are its own statements and the rest belongs to 5 function items inside it that branch (a function literal at line 132, 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.
D2 · Cognitive Complexity · feedback-links.FeedbackLinkDialog (cognitive 27) · ×1
  • feedback-links.FeedbackLinkDialog (cognitive 27) apps/web/src/features/resume/share/feedback-links.tsx:327 — feedback-links.FeedbackLinkDialog has cognitive complexity 27 (threshold 15). Drivers by points: ternaries 8 (21 pts), boolean chains 4, if/else 2 (nesting depth added 13). Most of this is not in the body itself: 12 of the 27 points are its own statements and the rest belongs to 3 function items inside it that branch (a function literal at line 440, askRevoke, a function literal at line 359). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · translation.proposeTranslation (cognitive 27) · ×1
  • translation.proposeTranslation (cognitive 27) packages/api/src/features/agent/translation.ts:130 — translation.proposeTranslation has cognitive complexity 27 (threshold 15). Drivers by points: if/else 8 (16 pts), loops 4 (6 pts), ternaries 2 (3 pts), boolean chains 2 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · service.searchWeb (cognitive 27) · ×1
  • service.searchWeb (cognitive 27) packages/api/src/features/web-access/service.ts:119 — service.searchWeb has cognitive complexity 27 (threshold 15). Drivers by points: ternaries 6 (11 pts), if/else 7 (10 pts), boolean chains 4, error handling 2 (nesting depth added 8). Of this number, 16 points are the body's own statements and 11 belong to 4 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · pdf-lines.readIdentity (cognitive 27) · ×1
  • pdf-lines.readIdentity (cognitive 27) packages/import/src/pdf-lines.ts:1547 — pdf-lines.readIdentity has cognitive complexity 27 (threshold 15). Drivers by points: if/else 8 (13 pts), boolean chains 9, ternaries 3, loops 2 (nesting depth added 5). Of this number, 20 points are the body's own statements and 7 belong to 6 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · render.renderResumeElement · ×1
  • render.renderResumeElement::layOut (cognitive 27) packages/pdf/src/forme/render.ts:470 — render.renderResumeElement::layOut has cognitive complexity 27 (threshold 15). Drivers by points: if/else 7 (18 pts), loops 3 (6 pts), boolean chains 3 (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 (render.renderResumeElement) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D2 · Cognitive Complexity · main (cognitive 27) · ×1
  • main (cognitive 27) tooling/ci/failed-logs.mjs:62 — main has cognitive complexity 27 (threshold 15). Drivers by points: if/else 9 (14 pts), other 5, boolean chains 3, ternaries 2 (3 pts), loops 2 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · rich-text-markup.hasRectangularTableGrid (cognitive 26) · ×1
  • rich-text-markup.hasRectangularTableGrid (cognitive 26) apps/web/src/components/input/rich-text-markup.ts:315 — rich-text-markup.hasRectangularTableGrid has cognitive complexity 26 (threshold 15). Drivers by points: if/else 6 (15 pts), loops 4 (9 pts), boolean chains 2 (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · next-steps.TryItOn (cognitive 26) · ×1
  • next-steps.TryItOn (cognitive 26) apps/web/src/features/settings/ai/next-steps.tsx:61 — next-steps.TryItOn has cognitive complexity 26 (threshold 15). Drivers by points: ternaries 11 (23 pts), boolean chains 2, if/else 1 (nesting depth added 12). Of this number, 23 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.
D2 · Cognitive Complexity · translation.translationFields · ×1
  • translation.translationFields::visit (cognitive 26) packages/api/src/features/agent/translation.ts:80 — translation.translationFields::visit has cognitive complexity 26 (threshold 15). Drivers by points: if/else 10 (17 pts), boolean chains 6, loops 2 (3 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · legacy-styles-migration.migrateLegacyStyles (cognitive 26) · ×1
  • legacy-styles-migration.migrateLegacyStyles (cognitive 26) packages/api/src/features/resume/legacy-styles-migration.ts:77 — legacy-styles-migration.migrateLegacyStyles has cognitive complexity 26 (threshold 15). Drivers by points: if/else 4 (13 pts), loops 3 (6 pts), error handling 1 (4 pts), ternaries 1 (3 pts) (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · level-display.LevelDisplay (cognitive 26) · ×1
  • level-display.LevelDisplay (cognitive 26) packages/pdf/src/templates/shared/level-display.tsx:26 — level-display.LevelDisplay has cognitive complexity 26 (threshold 15). Drivers by points: ternaries 9 (13 pts), if/else 11, boolean chains 2 (nesting depth added 4). Most of this is not in the body itself: 9 of the 26 points are its own statements and the rest belongs to one function literal inside it that branches (line 69). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · move-item.moveItem (cognitive 26) · ×1
  • move-item.moveItem (cognitive 26) packages/resume/src/move-item.ts:17 — move-item.moveItem has cognitive complexity 26 (threshold 15). Drivers by points: if/else 9 (13 pts), boolean chains 7, ternaries 3 (6 pts) (nesting depth added 7). Of this number, 24 points are the body's own statements and 2 belong to 3 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · cascade.expandedWinnersFor (cognitive 26) · ×1
  • cascade.expandedWinnersFor (cognitive 26) packages/resume/src/stylesheet/cascade.ts:344 — cascade.expandedWinnersFor has cognitive complexity 26 (threshold 15). Drivers by points: if/else 7 (18 pts), loops 4 (7 pts), boolean chains 1 (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · cascade.normalizeValue (cognitive 26) · ×1
  • cascade.normalizeValue (cognitive 26) packages/resume/src/stylesheet/cascade.ts:458 — cascade.normalizeValue has cognitive complexity 26 (threshold 15). Drivers by points: if/else 11 (20 pts), boolean chains 3, ternaries 1 (3 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.
D2 · Cognitive Complexity · catalog-diff.signature · ×1
  • catalog-diff.signature::message (cognitive 26) tooling/locales/catalog-diff.mjs:32 — catalog-diff.signature::message has cognitive complexity 26 (threshold 15). Drivers by points: if/else 8 (15 pts), boolean chains 7, loops 2 (4 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · menu-screen.ResumeMenu (cognitive 25) · ×1
  • menu-screen.ResumeMenu (cognitive 25) apps/mobile/src/features/builder/menu/menu-screen.tsx:44 — menu-screen.ResumeMenu has cognitive complexity 25 (threshold 15). Drivers by points: if/else 10 (12 pts), ternaries 8 (9 pts), boolean chains 3, error handling 1 (nesting depth added 3). Most of this is not in the body itself: 6 of the 25 points are its own statements and the rest belongs to 6 function items inside it that branch (a function literal at line 114, a function literal at line 73, row, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · calendar-view.ApplicationCalendar (cognitive 25) · ×1
  • calendar-view.ApplicationCalendar (cognitive 25) apps/web/src/features/applications/components/calendar-view.tsx:47 — calendar-view.ApplicationCalendar has cognitive complexity 25 (threshold 15). Drivers by points: boolean chains 18, ternaries 5 (6 pts), loops 1 (nesting depth added 1). Of this number, 22 points are the body's own statements and 3 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.
D2 · Cognitive Complexity · coach-chat.MessageView (cognitive 25) · ×1
  • coach-chat.MessageView (cognitive 25) apps/web/src/features/career/coach-chat.tsx:417 — coach-chat.MessageView has cognitive complexity 25 (threshold 15). Drivers by points: boolean chains 21, ternaries 3, if/else 1. Of this number, 23 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.
D2 · Cognitive Complexity · today.useNeedLine.<returned closure> (cognitive 25) · ×1
  • today.useNeedLine.<returned closure> (cognitive 25) apps/web/src/features/career/today.tsx:309 — today.useNeedLine.<returned closure> has cognitive complexity 25 (threshold 15). Drivers by points: ternaries 9 (21 pts), boolean chains 2, if/else 2 (nesting depth added 12). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
D2 · Cognitive Complexity · store.startLetterDraft (cognitive 25) · ×1
  • store.startLetterDraft (cognitive 25) apps/web/src/features/letters/store.ts:707 — store.startLetterDraft has cognitive complexity 25 (threshold 15). Drivers by points: if/else 10 (12 pts), ternaries 6 (9 pts), boolean chains 2, error handling 1, loops 1 (nesting depth added 5). Of this number, 22 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, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · dates-field.DatesField (cognitive 25) · ×1
  • dates-field.DatesField (cognitive 25) apps/web/src/features/resume/editor/write/dates-field.tsx:114 — dates-field.DatesField has cognitive complexity 25 (threshold 15). Drivers by points: ternaries 11 (14 pts), boolean chains 11 (nesting depth added 3). Of this number, 23 points are the body's own statements and 2 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.
D2 · Cognitive Complexity · providers.ProvidersSection (cognitive 25) · ×1
  • providers.ProvidersSection (cognitive 25) apps/web/src/features/settings/ai/providers.tsx:70 — providers.ProvidersSection has cognitive complexity 25 (threshold 15). Drivers by points: ternaries 6 (14 pts), boolean chains 6, if/else 3, error handling 2 (nesting depth added 8). Most of this is not in the body itself: 12 of the 25 points are its own statements and the rest belongs to 4 function items inside it that branch (showReady, a function literal at line 144, a function literal at line 183, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · sanitize.coerceValueAgainstTemplate (cognitive 25) · ×1
  • sanitize.coerceValueAgainstTemplate (cognitive 25) packages/ai/src/resume/sanitize.ts:110 — sanitize.coerceValueAgainstTemplate has cognitive complexity 25 (threshold 15). Drivers by points: if/else 12 (18 pts), boolean chains 4, ternaries 1 (2 pts), loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · service.describeTestConnectionFailure (cognitive 25) · ×1
  • service.describeTestConnectionFailure (cognitive 25) packages/api/src/features/ai/service.ts:227 — service.describeTestConnectionFailure has cognitive complexity 25 (threshold 15). Drivers by points: if/else 11 (16 pts), ternaries 2 (5 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.
D2 · Cognitive Complexity · cleanup.runStorageCleanup (cognitive 25) · ×1
  • cleanup.runStorageCleanup (cognitive 25) packages/api/src/features/storage/cleanup.ts:122 — cleanup.runStorageCleanup has cognitive complexity 25 (threshold 15). Drivers by points: if/else 10 (19 pts), ternaries 2 (4 pts), boolean chains 1, loops 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · values.cssFunctionDepth (cognitive 25) · ×1
  • values.cssFunctionDepth (cognitive 25) packages/resume/src/stylesheet/values.ts:91 — values.cssFunctionDepth has cognitive complexity 25 (threshold 15). Drivers by points: if/else 9 (21 pts), boolean chains 3, loops 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · compare (cognitive 25) · ×1
  • compare (cognitive 25) tooling/locales/catalog-diff.mjs:147 — compare has cognitive complexity 25 (threshold 15). Drivers by points: if/else 8 (17 pts), loops 2 (3 pts), other 3, boolean chains 2 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · EntryScreen.EntryScreen · ×1
  • EntryScreen.EntryScreen::render (cognitive 24) apps/mobile/src/features/builder/entry/EntryScreen.tsx:186 — EntryScreen.EntryScreen::render has cognitive complexity 24 (threshold 15). Drivers by points: ternaries 9 (23 pts), match/switch 1 (nesting depth added 14). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident. This shape REPEATS in the file: one other method here (EntryScreen.EntryScreen) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D2 · Cognitive Complexity · uploads.handleUpload (cognitive 24) · ×1
  • uploads.handleUpload (cognitive 24) apps/server/src/static/uploads.ts:12 — uploads.handleUpload has cognitive complexity 24 (threshold 15). Drivers by points: if/else 11 (13 pts), boolean chains 8, ternaries 3 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
D2 · Cognitive Complexity · enable-two-factor.EnableTwoFactorDialog (cognitive 24) · ×1
  • enable-two-factor.EnableTwoFactorDialog (cognitive 24) apps/web/src/dialogs/auth/enable-two-factor.tsx:55 — enable-two-factor.EnableTwoFactorDialog has cognitive complexity 24 (threshold 15). Drivers by points: if/else 11, boolean chains 8, ternaries 4 (5 pts) (nesting depth added 1). Most of this is not in the body itself: 4 of the 24 points are its own statements and the rest belongs to 12 function items inside it that branch (a function literal at line 146, a function literal at line 68, a function literal at line 257, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · application-form-sheet.toPayload (cognitive 24) · ×1
  • application-form-sheet.toPayload (cognitive 24) apps/web/src/features/applications/components/application-form-sheet.tsx:101 — application-form-sheet.toPayload has cognitive complexity 24 (threshold 15). Drivers by points: boolean chains 12, ternaries 11 (12 pts) (nesting depth added 1). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · activity.Activity · ×1
  • activity.Activity::describe (cognitive 24) apps/web/src/features/applications/components/detail/activity.tsx:122 — activity.Activity::describe has cognitive complexity 24 (threshold 15). Drivers by points: ternaries 7 (20 pts), boolean chains 2, if/else 2 (nesting depth added 13). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
D2 · Cognitive Complexity · tool-approvals.ToolApprovals (cognitive 24) · ×1
  • tool-approvals.ToolApprovals (cognitive 24) apps/web/src/features/assistant/tool-approvals.tsx:39 — tool-approvals.ToolApprovals has cognitive complexity 24 (threshold 15). Drivers by points: ternaries 9 (20 pts), boolean chains 4 (nesting depth added 11). None of this is in the body itself: all 24 points belong to one function literal inside it that branches (line 48). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · new-document-dialog.CopyForJob (cognitive 24) · ×1
  • new-document-dialog.CopyForJob (cognitive 24) apps/web/src/features/documents/new-document-dialog.tsx:650 — new-document-dialog.CopyForJob has cognitive complexity 24 (threshold 15). Drivers by points: ternaries 24 (32 pts), boolean chains 13, if/else 2, error handling 1 (nesting depth added 8). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition. This shape REPEATS in the file: one other method here (new-document-dialog.CopyForJob::create) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D2 · Cognitive Complexity · editor.StylesheetCodeEditor (cognitive 24) · ×1
  • editor.StylesheetCodeEditor (cognitive 24) apps/web/src/features/resume/stylesheet/editor.tsx:130 — editor.StylesheetCodeEditor has cognitive complexity 24 (threshold 15). Drivers by points: if/else 11, boolean chains 10, ternaries 2 (3 pts) (nesting depth added 1). Most of this is not in the body itself: 2 of the 24 points are its own statements and the rest belongs to 10 function items inside it that branch (a function literal at line 207, updateColor, a function literal at line 240, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · editor.StylesheetEditorShell (cognitive 24) · ×1
  • editor.StylesheetEditorShell (cognitive 24) apps/web/src/features/resume/stylesheet/editor.tsx:390 — editor.StylesheetEditorShell has cognitive complexity 24 (threshold 15). Drivers by points: boolean chains 11, if/else 8, ternaries 5. Most of this is not in the body itself: 8 of the 24 points are its own statements and the rest belongs to 8 function items inside it that branch (highlightRuleAt, a function literal at line 427, a function literal at line 429, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · providers.EditProviderForm (cognitive 24) · ×1
  • providers.EditProviderForm (cognitive 24) apps/web/src/features/settings/ai/providers.tsx:643 — providers.EditProviderForm has cognitive complexity 24 (threshold 15). Drivers by points: boolean chains 11, ternaries 7, if/else 5, error handling 1. 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, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · lanes.resolveApplicationTransition (cognitive 24) · ×1
  • lanes.resolveApplicationTransition (cognitive 24) packages/api/src/features/applications/lanes.ts:41 — lanes.resolveApplicationTransition has cognitive complexity 24 (threshold 15). Drivers by points: if/else 9 (13 pts), boolean chains 10, 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.
D2 · Cognitive Complexity · service.sourceText (cognitive 24) · ×1
  • service.sourceText (cognitive 24) packages/api/src/features/career/service.ts:100 — service.sourceText has cognitive complexity 24 (threshold 15). Drivers by points: if/else 11 (16 pts), ternaries 2 (5 pts), boolean chains 3 (nesting depth added 8). Of this number, 21 points are the body's own statements and 3 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · jobs.sendPendingEmail (cognitive 24) · ×1
  • jobs.sendPendingEmail (cognitive 24) packages/api/src/features/career/jobs.ts:798 — jobs.sendPendingEmail has cognitive complexity 24 (threshold 15). Drivers by points: if/else 7 (15 pts), boolean chains 4, error handling 1 (2 pts), ternaries 1 (2 pts), loops 1 (nesting depth added 10). Most of this is not in the body itself: 9 of the 24 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 837, 801). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · linkedin.parseCsv (cognitive 24) · ×1
  • linkedin.parseCsv (cognitive 24) packages/import/src/linkedin.ts:99 — linkedin.parseCsv has cognitive complexity 24 (threshold 15). Drivers by points: if/else 11 (20 pts), boolean chains 3, loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · use-register-fonts.resolvePdfFonts (cognitive 24) · ×1
  • use-register-fonts.resolvePdfFonts (cognitive 24) packages/pdf/src/hooks/use-register-fonts.ts:236 — use-register-fonts.resolvePdfFonts has cognitive complexity 24 (threshold 15). Drivers by points: if/else 7 (9 pts), loops 4 (7 pts), ternaries 5 (6 pts), boolean chains 2 (nesting depth added 6). Most of this is not in the body itself: 10 of the 24 points are its own statements and the rest belongs to 2 function items inside it that branch (registerFallbacks, registerFont). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · csv.parseCsv (cognitive 24) · ×1
  • csv.parseCsv (cognitive 24) packages/schema/src/applications/csv.ts:16 — csv.parseCsv has cognitive complexity 24 (threshold 15). Drivers by points: if/else 11 (20 pts), boolean chains 3, loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · store.createDraftStore.replayQueue (cognitive 23) · ×1
  • store.createDraftStore.replayQueue (cognitive 23) apps/mobile/src/data/draft/store.ts:705 — store.createDraftStore.replayQueue has cognitive complexity 23 (threshold 15). Drivers by points: if/else 9 (15 pts), boolean chains 5, error handling 1 (2 pts), loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · download.downloadDocuments (cognitive 23) · ×1
  • download.downloadDocuments (cognitive 23) apps/mobile/src/data/download.ts:13 — download.downloadDocuments has cognitive complexity 23 (threshold 15). Drivers by points: if/else 6 (13 pts), ternaries 3 (8 pts), boolean chains 1, loops 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · SectionScreen.SectionScreen (cognitive 23) · ×1
  • SectionScreen.SectionScreen (cognitive 23) apps/mobile/src/features/builder/section/SectionScreen.tsx:115 — SectionScreen.SectionScreen has cognitive complexity 23 (threshold 15). Drivers by points: ternaries 9 (10 pts), boolean chains 7, if/else 5 (6 pts) (nesting depth added 2). Of this number, 14 points are the body's own statements and 9 belong to 5 function items inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
D2 · Cognitive Complexity · ApplyScreen.ApplyScreen (cognitive 23) · ×1
  • ApplyScreen.ApplyScreen (cognitive 23) apps/mobile/src/features/workspace/ApplyScreen.tsx:33 — ApplyScreen.ApplyScreen has cognitive complexity 23 (threshold 15). Drivers by points: ternaries 16 (20 pts), boolean chains 2, if/else 1 (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
D2 · Cognitive Complexity · Toast.ToastView (cognitive 23) · ×1
  • Toast.ToastView (cognitive 23) apps/mobile/src/ui/Toast.tsx:149 — Toast.ToastView has cognitive complexity 23 (threshold 15). Drivers by points: ternaries 13 (15 pts), if/else 5 (6 pts), boolean chains 2 (nesting depth added 3). Most of this is not in the body itself: 6 of the 23 points are its own statements and the rest belongs to 7 function literals inside it that branch (lines 244, 206, 175, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · ReorderList.ReorderList (cognitive 23) · ×1
  • ReorderList.ReorderList (cognitive 23) apps/mobile/src/ui/ReorderList.tsx:89 — ReorderList.ReorderList has cognitive complexity 23 (threshold 15). Drivers by points: if/else 14 (15 pts), boolean chains 5, loops 2, ternaries 1 (nesting depth added 1). None of this is in the body itself: all 23 points belong to 8 function items inside it that branch (a function literal at line 182, drop, moveBy, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · stage-stepper.StageStepper (cognitive 23) · ×1
  • stage-stepper.StageStepper (cognitive 23) apps/web/src/components/calm/stage-stepper.tsx:54 — stage-stepper.StageStepper has cognitive complexity 23 (threshold 15). Drivers by points: boolean chains 13, ternaries 7 (9 pts), if/else 1 (nesting depth added 2). None of this is in the body itself: all 23 points belong to one function literal inside it that branches (line 67). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · debrief.DebriefTab (cognitive 23) · ×1
  • debrief.DebriefTab (cognitive 23) apps/web/src/features/career/workspace/debrief.tsx:56 — debrief.DebriefTab has cognitive complexity 23 (threshold 15). Drivers by points: boolean chains 11, ternaries 9 (11 pts), if/else 1 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
D2 · Cognitive Complexity · messages.ReplyCard · ×1
  • messages.ReplyCard::copy (cognitive 23) apps/web/src/features/career/workspace/messages.tsx:413 — messages.ReplyCard::copy has cognitive complexity 23 (threshold 15). Drivers by points: if/else 8 (13 pts), boolean chains 6, ternaries 2 (3 pts), error handling 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (messages.ReplyCard) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D2 · Cognitive Complexity · prepare.Prepare (cognitive 23) · ×1
  • prepare.Prepare (cognitive 23) apps/web/src/features/homepage/prepare.tsx:502 — prepare.Prepare has cognitive complexity 23 (threshold 15). Drivers by points: ternaries 12 (16 pts), boolean chains 6, if/else 1 (nesting depth added 4). Most of this is not in the body itself: 6 of the 23 points are its own statements and the rest belongs to 5 function literals inside it that branch (lines 629, 586, 542, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · draft.useResumeCleanup (cognitive 23) · ×1
  • draft.useResumeCleanup (cognitive 23) apps/web/src/features/resume/builder/draft.ts:1333 — draft.useResumeCleanup has cognitive complexity 23 (threshold 15). Drivers by points: if/else 10, ternaries 5 (8 pts), boolean chains 5 (nesting depth added 3). None of this is in the body itself: all 23 points belong to 7 function literals inside it that branch (lines 1355, 1388, 1339, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · entry-row.EntryRow (cognitive 23) · ×1
  • entry-row.EntryRow (cognitive 23) apps/web/src/features/resume/editor/write/entry-row.tsx:84 — entry-row.EntryRow has cognitive complexity 23 (threshold 15). Drivers by points: boolean chains 12, ternaries 7 (9 pts), if/else 2 (nesting depth added 2). Of this number, 19 points are the body's own statements and 4 belong to one function item inside it that branches. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · profile.EditableRow (cognitive 23) · ×1
  • profile.EditableRow (cognitive 23) apps/web/src/features/settings/account/profile.tsx:68 — profile.EditableRow has cognitive complexity 23 (threshold 15). Drivers by points: ternaries 7 (9 pts), if/else 8, boolean chains 5, error handling 1 (nesting depth added 2). Of this number, 13 points are the body's own statements and 10 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.
D2 · Cognitive Complexity · security.Passkeys (cognitive 23) · ×1
  • security.Passkeys (cognitive 23) apps/web/src/features/settings/account/security.tsx:137 — security.Passkeys has cognitive complexity 23 (threshold 15). Drivers by points: boolean chains 8, ternaries 6 (8 pts), if/else 7 (nesting depth added 2). Of this number, 13 points are the body's own statements and 10 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.
D2 · Cognitive Complexity · prose.assertProse (cognitive 23) · ×1
  • prose.assertProse (cognitive 23) packages/api/src/features/agent/prose.ts:19 — prose.assertProse has cognitive complexity 23 (threshold 15). Drivers by points: if/else 9 (16 pts), boolean chains 6, loops 1 (nesting depth added 7). 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, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · web-page.loadPublicWebPage (cognitive 23) · ×1
  • web-page.loadPublicWebPage (cognitive 23) packages/api/src/features/resume/web-page.ts:57 — web-page.loadPublicWebPage has cognitive complexity 23 (threshold 15). Drivers by points: if/else 7 (9 pts), ternaries 5 (8 pts), boolean chains 6 (nesting depth added 5). Of this number, 21 points are the body's own statements and 2 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.
D2 · Cognitive Complexity · section-renderers.renderCustomSection (cognitive 23) · ×1
  • section-renderers.renderCustomSection (cognitive 23) packages/docx/src/section-renderers.ts:323 — section-renderers.renderCustomSection has cognitive complexity 23 (threshold 15). Drivers by points: if/else 8 (14 pts), loops 2 (4 pts), boolean chains 3, ternaries 1 (2 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · pdf-lines.parseGeometryResume (cognitive 23) · ×1
  • pdf-lines.parseGeometryResume (cognitive 23) packages/import/src/pdf-lines.ts:1988 — pdf-lines.parseGeometryResume has cognitive complexity 23 (threshold 15). Drivers by points: if/else 8 (11 pts), boolean chains 10, loops 1, ternaries 1 (nesting depth added 3). Of this number, 18 points are the body's own statements and 5 belong to 4 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · html-to-odt.collectInline (cognitive 23) · ×1
  • html-to-odt.collectInline (cognitive 23) packages/odt/src/html-to-odt.ts:72 — html-to-odt.collectInline has cognitive complexity 23 (threshold 15). Drivers by points: if/else 9 (21 pts), boolean chains 1, loops 1 (nesting depth added 12). 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, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · render.entryPaginationRepairs · ×1
  • render.entryPaginationRepairs::visit (cognitive 23) packages/pdf/src/forme/render.ts:206 — render.entryPaginationRepairs::visit has cognitive complexity 23 (threshold 15). Drivers by points: if/else 7 (13 pts), boolean chains 6, ternaries 1 (3 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.
D2 · Cognitive Complexity · cascade.expandVariables (cognitive 23) · ×1
  • cascade.expandVariables (cognitive 23) packages/resume/src/stylesheet/cascade.ts:245 — cascade.expandVariables has cognitive complexity 23 (threshold 15). Drivers by points: if/else 12 (19 pts), boolean chains 3, loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · autofill.packetFillPlan (cognitive 23) · ×1
  • autofill.packetFillPlan (cognitive 23) packages/schema/src/applications/autofill.ts:99 — autofill.packetFillPlan has cognitive complexity 23 (threshold 15). Drivers by points: ternaries 7 (17 pts), if/else 4 (5 pts), loops 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · stream.useAssistantStream.run (cognitive 22) · ×1
  • stream.useAssistantStream.run (cognitive 22) apps/mobile/src/data/stream.ts:97 — stream.useAssistantStream.run has cognitive complexity 22 (threshold 15). Drivers by points: if/else 9 (12 pts), ternaries 3 (6 pts), boolean chains 2, error handling 2 (nesting depth added 6). Of this number, 15 points are the body's own statements and 7 belong to 3 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · harness.collectDump (cognitive 22) · ×1
  • harness.collectDump (cognitive 22) apps/mobile/src/dev/storyboard/harness.tsx:261 — harness.collectDump has cognitive complexity 22 (threshold 15). Drivers by points: if/else 10 (12 pts), boolean chains 5, ternaries 3 (5 pts) (nesting depth added 4). None of this is in the body itself: all 22 points belong to 8 function literals inside it that branch (lines 289, 283, 267, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · model.agendaItems (cognitive 22) · ×1
  • model.agendaItems (cognitive 22) apps/mobile/src/features/applications/model.ts:249 — model.agendaItems has cognitive complexity 22 (threshold 15). Drivers by points: ternaries 4 (11 pts), if/else 3 (6 pts), loops 2 (3 pts), boolean chains 2 (nesting depth added 11). Of this number, 21 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ApplicationsScreen.CalendarView (cognitive 22) · ×1
  • ApplicationsScreen.CalendarView (cognitive 22) apps/mobile/src/features/applications/ApplicationsScreen.tsx:755 — ApplicationsScreen.CalendarView has cognitive complexity 22 (threshold 15). Drivers by points: ternaries 13 (18 pts), if/else 3, boolean chains 1 (nesting depth added 5). Most of this is not in the body itself: 7 of the 22 points are its own statements and the rest belongs to 8 function items inside it that branch (a function literal at line 903, page, pick, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · model.isEmptyEntry (cognitive 22) · ×1
  • model.isEmptyEntry (cognitive 22) apps/mobile/src/features/builder/shared/model.ts:274 — model.isEmptyEntry has cognitive complexity 22 (threshold 15). Drivers by points: if/else 7 (15 pts), boolean chains 6, 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.
D2 · Cognitive Complexity · download-screen.ExportContent · ×1
  • download-screen.ExportContent::exportFile (cognitive 22) apps/mobile/src/features/builder/download/download-screen.tsx:58 — download-screen.ExportContent::exportFile has cognitive complexity 22 (threshold 15). Drivers by points: if/else 9 (13 pts), ternaries 4 (5 pts), boolean chains 3, 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. This shape REPEATS in the file: one other method here (download-screen.ExportContent) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D2 · Cognitive Complexity · attachment-preview.AttachmentPreview (cognitive 22) · ×1
  • attachment-preview.AttachmentPreview (cognitive 22) apps/web/src/features/applications/components/attachment-preview.tsx:12 — attachment-preview.AttachmentPreview has cognitive complexity 22 (threshold 15). Drivers by points: if/else 12 (14 pts), ternaries 4 (5 pts), boolean chains 3 (nesting depth added 3). Most of this is not in the body itself: 5 of the 22 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 39, 17, 26, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · remember-message.RememberMessage (cognitive 22) · ×1
  • remember-message.RememberMessage (cognitive 22) apps/web/src/features/assistant/remember-message.tsx:24 — remember-message.RememberMessage has cognitive complexity 22 (threshold 15). Drivers by points: if/else 7 (8 pts), ternaries 5 (7 pts), boolean chains 6, error handling 1 (nesting depth added 3). 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 (save, a function literal at line 93, current). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · checker.AtsChecker (cognitive 22) · ×1
  • checker.AtsChecker (cognitive 22) apps/web/src/features/ats-checker/checker.tsx:65 — checker.AtsChecker has cognitive complexity 22 (threshold 15). Drivers by points: ternaries 5 (10 pts), if/else 6 (7 pts), boolean chains 3, error handling 2 (nesting depth added 6). Most of this is not in the body itself: 7 of the 22 points are its own statements and the rest belongs to 5 function items inside it that branch (importAndOpen, check, a function literal at line 116, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · register.RegisterPage (cognitive 22) · ×1
  • register.RegisterPage (cognitive 22) apps/web/src/features/auth/pages/register.tsx:58 — register.RegisterPage has cognitive complexity 22 (threshold 15). Drivers by points: boolean chains 10, if/else 7 (9 pts), ternaries 3 (nesting depth added 2). Most of this is not in the body itself: 10 of the 22 points are its own statements and the rest belongs to one function literal inside it that branches (line 71). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · apply.Checklist (cognitive 22) · ×1
  • apply.Checklist (cognitive 22) apps/web/src/features/career/workspace/apply.tsx:959 — apply.Checklist has cognitive complexity 22 (threshold 15). Drivers by points: boolean chains 15, ternaries 4, if/else 2, error handling 1. Of this number, 15 points are the body's own statements and 7 belong to 5 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · resume-facts.ReviewResumeFacts (cognitive 22) · ×1
  • resume-facts.ReviewResumeFacts (cognitive 22) apps/web/src/features/career/knowledge/resume-facts.tsx:50 — resume-facts.ReviewResumeFacts has cognitive complexity 22 (threshold 15). Drivers by points: boolean chains 15, if/else 5, ternaries 2. Of this number, 13 points are the body's own statements and 9 belong to 8 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · document-actions.LinkApplicationDialog (cognitive 22) · ×1
  • document-actions.LinkApplicationDialog (cognitive 22) apps/web/src/features/documents/document-actions.tsx:695 — document-actions.LinkApplicationDialog has cognitive complexity 22 (threshold 15). Drivers by points: boolean chains 12, ternaries 4 (7 pts), if/else 2, error handling 1 (nesting depth added 3). 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 (choose, a function literal at line 767, a function literal at line 736). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · draft.readUnsavedResume (cognitive 22) · ×1
  • draft.readUnsavedResume (cognitive 22) apps/web/src/features/resume/builder/draft.ts:255 — draft.readUnsavedResume has cognitive complexity 22 (threshold 15). Drivers by points: if/else 5 (10 pts), boolean chains 8, error handling 2 (3 pts), loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · chrome.pageUnderPointer (cognitive 22) · ×1
  • chrome.pageUnderPointer (cognitive 22) apps/web/src/features/resume/editor/chrome.tsx:52 — chrome.pageUnderPointer has cognitive complexity 22 (threshold 15). Drivers by points: ternaries 4 (10 pts), if/else 5 (9 pts), loops 3 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · resume-reflow.EntryView (cognitive 22) · ×1
  • resume-reflow.EntryView (cognitive 22) apps/web/src/features/resume/preview/resume-reflow.tsx:46 — resume-reflow.EntryView has cognitive complexity 22 (threshold 15). Drivers by points: boolean chains 16, ternaries 6. Of this number, 19 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.
D2 · Cognitive Complexity · feedback-links.FeedbackLinksSection (cognitive 22) · ×1
  • feedback-links.FeedbackLinksSection (cognitive 22) apps/web/src/features/resume/share/feedback-links.tsx:77 — feedback-links.FeedbackLinksSection has cognitive complexity 22 (threshold 15). Drivers by points: ternaries 8 (20 pts), boolean chains 2 (nesting depth added 12). Most of this is not in the body itself: 6 of the 22 points are its own statements and the rest belongs to one function literal inside it that branches (line 106). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · page-canvas.ResumePageCaption (cognitive 22) · ×1
  • page-canvas.ResumePageCaption (cognitive 22) apps/web/src/routes/builder/$resumeId/-components/page-canvas.tsx:276 — page-canvas.ResumePageCaption has cognitive complexity 22 (threshold 15). Drivers by points: ternaries 5 (15 pts), boolean chains 7 (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.
D2 · Cognitive Complexity · write-panel.EmptyBody (cognitive 22) · ×1
  • write-panel.EmptyBody (cognitive 22) apps/web/src/routes/builder/letter/-components/write-panel.tsx:988 — write-panel.EmptyBody has cognitive complexity 22 (threshold 15). Drivers by points: ternaries 6 (15 pts), boolean chains 7 (nesting depth added 9). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
D2 · Cognitive Complexity · write-panel.DraftBox (cognitive 22) · ×1
  • write-panel.DraftBox (cognitive 22) apps/web/src/routes/builder/letter/-components/write-panel.tsx:1047 — write-panel.DraftBox has cognitive complexity 22 (threshold 15). Drivers by points: ternaries 10 (12 pts), boolean chains 9, if/else 1 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
D2 · Cognitive Complexity · service.recordSentResume (cognitive 22) · ×1
  • service.recordSentResume (cognitive 22) packages/api/src/features/applications/service.ts:243 — service.recordSentResume has cognitive complexity 22 (threshold 15). Drivers by points: if/else 10 (15 pts), boolean chains 7 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · service.readPage (cognitive 22) · ×1
  • service.readPage (cognitive 22) packages/api/src/features/web-access/service.ts:191 — service.readPage has cognitive complexity 22 (threshold 15). Drivers by points: if/else 4 (9 pts), ternaries 5 (9 pts), error handling 2 (3 pts), boolean chains 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · linkedin.parseLinkedInExport (cognitive 22) · ×1
  • linkedin.parseLinkedInExport (cognitive 22) packages/import/src/linkedin.ts:168 — linkedin.parseLinkedInExport has cognitive complexity 22 (threshold 15). Drivers by points: if/else 9 (11 pts), boolean chains 9, 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.
D2 · Cognitive Complexity · plain-text.groupEntries (cognitive 22) · ×1
  • plain-text.groupEntries (cognitive 22) packages/import/src/plain-text.ts:291 — plain-text.groupEntries has cognitive complexity 22 (threshold 15). Drivers by points: if/else 9 (17 pts), boolean chains 3, loops 1, ternaries 1 (nesting depth added 8). Of this number, 19 points are the body's own statements and 3 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.
D2 · Cognitive Complexity · selector.matchesCombinator (cognitive 22) · ×1
  • selector.matchesCombinator (cognitive 22) packages/resume/src/stylesheet/selector.ts:423 — selector.matchesCombinator has cognitive complexity 22 (threshold 15). Drivers by points: if/else 4 (11 pts), loops 3 (6 pts), ternaries 2 (4 pts), match/switch 1 (nesting depth added 12). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
D2 · Cognitive Complexity · upcoming.upcomingApplicationEvents (cognitive 22) · ×1
  • upcoming.upcomingApplicationEvents (cognitive 22) packages/schema/src/applications/upcoming.ts:21 — upcoming.upcomingApplicationEvents has cognitive complexity 22 (threshold 15). Drivers by points: if/else 6 (15 pts), loops 2 (3 pts), boolean chains 2, ternaries 1 (2 pts) (nesting depth added 11). Of this number, 21 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · store.createDraftStore.refresh (cognitive 21) · ×1
  • store.createDraftStore.refresh (cognitive 21) apps/mobile/src/data/draft/store.ts:647 — store.createDraftStore.refresh has cognitive complexity 21 (threshold 15). Drivers by points: if/else 9 (13 pts), boolean chains 8 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · DetailScreen.workStatus (cognitive 21) · ×1
  • DetailScreen.workStatus (cognitive 21) apps/mobile/src/features/applications/DetailScreen.tsx:60 — DetailScreen.workStatus has cognitive complexity 21 (threshold 15). Drivers by points: ternaries 12 (18 pts), boolean chains 3 (nesting depth added 6). Of this number, 20 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · issues.describe (cognitive 21) · ×1
  • issues.describe (cognitive 21) apps/mobile/src/features/builder/check/issues.ts:66 — issues.describe has cognitive complexity 21 (threshold 15). Drivers by points: if/else 5 (10 pts), loops 2 (4 pts), ternaries 3 (4 pts), boolean chains 2, match/switch 1 (nesting depth added 8). Most of this is not in the body itself: 3 of the 21 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 75, 272, 249, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · TemplateScreen.TemplateScreen (cognitive 21) · ×1
  • TemplateScreen.TemplateScreen (cognitive 21) apps/mobile/src/features/builder/design/TemplateScreen.tsx:45 — TemplateScreen.TemplateScreen has cognitive complexity 21 (threshold 15). Drivers by points: ternaries 9 (11 pts), if/else 5 (6 pts), boolean chains 4 (nesting depth added 3). Most of this is not in the body itself: 7 of the 21 points are its own statements and the rest belongs to 5 function items inside it that branch (a function literal at line 160, a function literal at line 57, apply, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · Menu.MenuView (cognitive 21) · ×1
  • Menu.MenuView (cognitive 21) apps/mobile/src/ui/Menu.tsx:63 — Menu.MenuView has cognitive complexity 21 (threshold 15). Drivers by points: ternaries 12 (14 pts), if/else 4 (5 pts), boolean chains 2 (nesting depth added 3). Of this number, 12 points are the body's own statements and 9 belong to 5 function items inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · ReorderList.Row (cognitive 21) · ×1
  • ReorderList.Row (cognitive 21) apps/mobile/src/ui/ReorderList.tsx:229 — ReorderList.Row has cognitive complexity 21 (threshold 15). Drivers by points: ternaries 9 (10 pts), if/else 9, boolean chains 2 (nesting depth added 1). Most of this is not in the body itself: 3 of the 21 points are its own statements and the rest belongs to 10 function items inside it that branch (a function literal at line 335, a function literal at line 270, a function literal at line 279, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · resume-page.showPage (cognitive 21) · ×1
  • resume-page.showPage (cognitive 21) apps/server/src/static/resume-page.ts:142 — resume-page.showPage has cognitive complexity 21 (threshold 15). Drivers by points: ternaries 11 (15 pts), if/else 4 (5 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.
D2 · Cognitive Complexity · debrief.DebriefForm (cognitive 21) · ×1
  • debrief.DebriefForm (cognitive 21) apps/web/src/features/career/workspace/debrief.tsx:208 — debrief.DebriefForm has cognitive complexity 21 (threshold 15). Drivers by points: boolean chains 8, if/else 5 (6 pts), error handling 3 (4 pts), ternaries 3 (nesting depth added 2). Most of this is not in the body itself: 8 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 224, change, a function literal at line 257, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · messages.ProposalCard · ×1
  • messages.ProposalCard::describe (cognitive 21) apps/web/src/features/career/workspace/messages.tsx:669 — messages.ProposalCard::describe has cognitive complexity 21 (threshold 15). Drivers by points: ternaries 5 (12 pts), if/else 4 (8 pts), match/switch 1 (nesting depth added 11). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident. This shape REPEATS in the file: one other method here (messages.ProposalCard) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D2 · Cognitive Complexity · prepare.PrepareTab (cognitive 21) · ×1
  • prepare.PrepareTab (cognitive 21) apps/web/src/features/career/workspace/prepare.tsx:50 — prepare.PrepareTab has cognitive complexity 21 (threshold 15). Drivers by points: if/else 7 (11 pts), boolean chains 7, ternaries 2 (3 pts) (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · coach-chat.Proposal (cognitive 21) · ×1
  • coach-chat.Proposal (cognitive 21) apps/web/src/features/career/coach-chat.tsx:852 — coach-chat.Proposal has cognitive complexity 21 (threshold 15). Drivers by points: ternaries 9 (12 pts), boolean chains 3, if/else 3, error handling 2, loops 1 (nesting depth added 3). Of this number, 13 points are the body's own statements and 8 belong to 5 function items inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · ask.AccountAskCommandGroup (cognitive 21) · ×1
  • ask.AccountAskCommandGroup (cognitive 21) apps/web/src/features/command-palette/pages/ask.tsx:22 — ask.AccountAskCommandGroup has cognitive complexity 21 (threshold 15). Drivers by points: ternaries 4 (10 pts), if/else 8, boolean chains 3 (nesting depth added 6). Most of this is not in the body itself: 8 of the 21 points are its own statements and the rest belongs to 5 function items inside it that branch (choose, ready, a function literal at line 29, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · store.readRecovery (cognitive 21) · ×1
  • store.readRecovery (cognitive 21) apps/web/src/features/letters/store.ts:297 — store.readRecovery has cognitive complexity 21 (threshold 15). Drivers by points: boolean chains 11, if/else 3 (6 pts), error handling 2 (3 pts), loops 1 (nesting depth added 4). 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.
D2 · Cognitive Complexity · parser-view.ParsedText (cognitive 21) · ×1
  • parser-view.ParsedText (cognitive 21) apps/web/src/features/resume/editor/check/parser-view.tsx:102 — parser-view.ParsedText has cognitive complexity 21 (threshold 15). Drivers by points: ternaries 8 (11 pts), boolean chains 6, if/else 4 (nesting depth added 3). Most of this is not in the body itself: 6 of the 21 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 159, 140, 182, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · address-field.AddressField (cognitive 21) · ×1
  • address-field.AddressField (cognitive 21) apps/web/src/features/resume/share/address-field.tsx:64 — address-field.AddressField has cognitive complexity 21 (threshold 15). Drivers by points: boolean chains 8, ternaries 6 (8 pts), if/else 5 (nesting depth added 2). Of this number, 14 points are the body's own statements and 7 belong to one function item inside it that branches. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
D2 · Cognitive Complexity · profile.ProfileSection (cognitive 21) · ×1
  • profile.ProfileSection (cognitive 21) apps/web/src/features/settings/account/profile.tsx:220 — profile.ProfileSection has cognitive complexity 21 (threshold 15). Drivers by points: ternaries 13, if/else 5, boolean chains 2, error handling 1. Most of this is not in the body itself: 7 of the 21 points are its own statements and the rest belongs to 8 function items inside it that branch (confirmUsername, changeEmail, updateUser, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · provider-model.ProviderModel (cognitive 21) · ×1
  • provider-model.ProviderModel (cognitive 21) apps/web/src/features/settings/ai/provider-model.tsx:34 — provider-model.ProviderModel has cognitive complexity 21 (threshold 15). Drivers by points: boolean chains 8, ternaries 4 (7 pts), if/else 3 (6 pts) (nesting depth added 6). Most of this is not in the body itself: 7 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 56, a function literal at line 96, a function literal at line 41, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · root-context.loadRootContext (cognitive 21) · ×1
  • root-context.loadRootContext (cognitive 21) apps/web/src/libs/root-context.ts:29 — root-context.loadRootContext has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (13 pts), boolean chains 5, ternaries 3 (nesting depth added 5). Of this number, 12 points are the body's own statements and 9 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.
D2 · Cognitive Complexity · agent-tool-contracts.agentWebSources (cognitive 21) · ×1
  • agent-tool-contracts.agentWebSources (cognitive 21) packages/ai/src/tools/agent-tool-contracts.ts:184 — agent-tool-contracts.agentWebSources has cognitive complexity 21 (threshold 15). Drivers by points: if/else 7 (14 pts), loops 2 (5 pts), boolean chains 2 (nesting depth added 10). Of this number, 18 points are the body's own statements and 3 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.
D2 · Cognitive Complexity · agent-tool-contracts.agentReadPostings (cognitive 21) · ×1
  • agent-tool-contracts.agentReadPostings (cognitive 21) packages/ai/src/tools/agent-tool-contracts.ts:215 — agent-tool-contracts.agentReadPostings has cognitive complexity 21 (threshold 15). Drivers by points: ternaries 4 (8 pts), if/else 4 (7 pts), boolean chains 5, loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · plain-text.segment (cognitive 21) · ×1
  • plain-text.segment (cognitive 21) packages/import/src/plain-text.ts:496 — plain-text.segment has cognitive complexity 21 (threshold 15). Drivers by points: boolean chains 9, if/else 5 (9 pts), ternaries 1 (2 pts), loops 1 (nesting depth added 5). Of this number, 20 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · contracts.wireJsonSchema (cognitive 21) · ×1
  • contracts.wireJsonSchema (cognitive 21) packages/mcp/src/contracts.ts:79 — contracts.wireJsonSchema has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8, loops 3 (6 pts), ternaries 2 (4 pts), boolean chains 3 (nesting depth added 5). None of this is in the body itself: all 21 points belong to 2 function literals inside it that branch (lines 92, 83). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · tools.registerTools (cognitive 21) · ×1
  • tools.registerTools (cognitive 21) packages/mcp/src/tools.ts:80 — tools.registerTools has cognitive complexity 21 (threshold 15). Drivers by points: ternaries 13, if/else 5, boolean chains 2, loops 1. Most of this is not in the body itself: 1 of the 21 points is its own statement and the rest belongs to 10 function literals inside it that branch (lines 151, 173, 276, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · images.readImageHeader (cognitive 21) · ×1
  • images.readImageHeader (cognitive 21) packages/pdf/src/forme/images.ts:47 — images.readImageHeader has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (15 pts), boolean chains 4, loops 1 (2 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · rich-text-keys.getRichTextSemanticKind (cognitive 21) · ×1
  • rich-text-keys.getRichTextSemanticKind (cognitive 21) packages/pdf/src/semantic/rich-text-keys.ts:19 — rich-text-keys.getRichTextSemanticKind has cognitive complexity 21 (threshold 15). Drivers by points: if/else 15, boolean chains 4, ternaries 1 (2 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.
D2 · Cognitive Complexity · render.substituteMissingGlyphs (cognitive 21) · ×1
  • render.substituteMissingGlyphs (cognitive 21) packages/pdf/src/forme/render.ts:82 — render.substituteMissingGlyphs has cognitive complexity 21 (threshold 15). Drivers by points: loops 6 (9 pts), if/else 6 (8 pts), ternaries 1 (3 pts), boolean chains 1 (nesting depth added 7). Most of this is not in the body itself: 6 of the 21 points are its own statements and the rest belongs to 3 function items inside it that branch (visit, collect, a function literal at line 133). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · match.countResumeNgrams (cognitive 21) · ×1
  • match.countResumeNgrams (cognitive 21) packages/resume/src/ats-pdf/jd/match.ts:333 — match.countResumeNgrams has cognitive complexity 21 (threshold 15). Drivers by points: if/else 4 (11 pts), loops 5 (9 pts), boolean chains 1 (nesting depth added 11). Of this number, 11 points are the body's own statements and 10 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.
D2 · Cognitive Complexity · merge.mergeIntoPreviousEntry (cognitive 21) · ×1
  • merge.mergeIntoPreviousEntry (cognitive 21) packages/resume/src/ats/merge.ts:34 — merge.mergeIntoPreviousEntry has cognitive complexity 21 (threshold 15). Drivers by points: ternaries 6 (10 pts), boolean chains 6, if/else 3, loops 2 (nesting depth added 4). Of this number, 20 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · patch.applyResumePatches (cognitive 21) · ×1
  • patch.applyResumePatches (cognitive 21) packages/resume/src/patch.ts:125 — patch.applyResumePatches has cognitive complexity 21 (threshold 15). Drivers by points: if/else 6 (15 pts), error handling 2 (3 pts), ternaries 1 (2 pts), loops 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · proposals.unverifiedClaims (cognitive 21) · ×1
  • proposals.unverifiedClaims (cognitive 21) packages/resume/src/proposals.ts:213 — proposals.unverifiedClaims has cognitive complexity 21 (threshold 15). Drivers by points: if/else 5 (11 pts), loops 3 (4 pts), ternaries 1 (4 pts), boolean chains 2 (nesting depth added 10). Of this number, 20 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · values.splitValue (cognitive 21) · ×1
  • values.splitValue (cognitive 21) packages/resume/src/stylesheet/values.ts:175 — values.splitValue has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (17 pts), boolean chains 3, loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · career-offer.offerHintFromSalary (cognitive 21) · ×1
  • career-offer.offerHintFromSalary (cognitive 21) packages/schema/src/career-offer.ts:133 — career-offer.offerHintFromSalary has cognitive complexity 21 (threshold 15). Drivers by points: ternaries 7 (11 pts), boolean chains 7, if/else 3 (nesting depth added 4). Of this number, 16 points are the body's own statements and 5 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.
D2 · Cognitive Complexity · period.buildMonthLookup (cognitive 21) · ×1
  • period.buildMonthLookup (cognitive 21) packages/schema/src/resume/period.ts:103 — period.buildMonthLookup has cognitive complexity 21 (threshold 15). Drivers by points: loops 4 (7 pts), if/else 2 (6 pts), ternaries 1 (4 pts), error handling 1 (3 pts), boolean chains 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · PdfPagesModule.definition (cognitive 21) · ×1
  • PdfPagesModule.definition (cognitive 21) apps/mobile/modules/pdf-pages/ios/PdfPagesModule.swift:10 — PdfPagesModule.definition has cognitive complexity 21 (threshold 15). Drivers by points: boolean chains 9, if/else 8 (9 pts), loops 3 (nesting depth added 1). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · LayoutScreen.LayoutScreen · ×1
  • LayoutScreen.LayoutScreen::fit (cognitive 20) apps/mobile/src/features/builder/design/LayoutScreen.tsx:172 — LayoutScreen.LayoutScreen::fit has cognitive complexity 20 (threshold 15). Drivers by points: if/else 5 (10 pts), ternaries 4 (7 pts), boolean chains 1, error handling 1, 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.
D2 · Cognitive Complexity · resume-pdf.handleResumePdfDownload (cognitive 20) · ×1
  • resume-pdf.handleResumePdfDownload (cognitive 20) apps/server/src/http/resume-pdf.ts:18 — resume-pdf.handleResumePdfDownload has cognitive complexity 20 (threshold 15). Drivers by points: ternaries 4 (9 pts), if/else 5 (7 pts), boolean chains 3, error handling 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · next-step-card.NextStepCard (cognitive 20) · ×1
  • next-step-card.NextStepCard (cognitive 20) apps/web/src/features/applications/components/detail/next-step-card.tsx:49 — next-step-card.NextStepCard has cognitive complexity 20 (threshold 15). Drivers by points: ternaries 10 (12 pts), boolean chains 7, if/else 1 (nesting depth added 2). Of this number, 12 points are the body's own statements and 8 belong to one function item inside it that branches. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
D2 · Cognitive Complexity · login.LoginPage (cognitive 20) · ×1
  • login.LoginPage (cognitive 20) apps/web/src/features/auth/pages/login.tsx:116 — login.LoginPage has cognitive complexity 20 (threshold 15). Drivers by points: boolean chains 13, if/else 7. Of this number, 11 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.
D2 · Cognitive Complexity · prepare.RefreshSwitch (cognitive 20) · ×1
  • prepare.RefreshSwitch (cognitive 20) apps/web/src/features/career/workspace/prepare.tsx:627 — prepare.RefreshSwitch has cognitive complexity 20 (threshold 15). Drivers by points: ternaries 8 (14 pts), boolean chains 6 (nesting depth added 6). Of this number, 16 points are the body's own statements and 4 belong to 4 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · role-suggestions.SuggestRoles (cognitive 20) · ×1
  • role-suggestions.SuggestRoles (cognitive 20) apps/web/src/features/career/role-suggestions.tsx:63 — role-suggestions.SuggestRoles has cognitive complexity 20 (threshold 15). Drivers by points: boolean chains 17, ternaries 2, if/else 1. Of this number, 16 points are the body's own statements and 4 belong to 3 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · offers.openQuestions (cognitive 20) · ×1
  • offers.openQuestions (cognitive 20) apps/web/src/features/career/offers.tsx:1091 — offers.openQuestions has cognitive complexity 20 (threshold 15). Drivers by points: boolean chains 8, if/else 3 (7 pts), loops 2 (3 pts), ternaries 2 (nesting depth added 5). Of this number, 10 points are the body's own statements and 10 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.
D2 · Cognitive Complexity · document-card.DocumentCard (cognitive 20) · ×1
  • document-card.DocumentCard (cognitive 20) apps/web/src/features/documents/document-card.tsx:238 — document-card.DocumentCard has cognitive complexity 20 (threshold 15). Drivers by points: boolean chains 13, ternaries 6, if/else 1. Of this number, 18 points are the body's own statements and 2 belong to one function item inside it that branches. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · read-file.detectImportKind (cognitive 20) · ×1
  • read-file.detectImportKind (cognitive 20) apps/web/src/features/resume/import/read-file.ts:59 — read-file.detectImportKind has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (9 pts), boolean chains 7, error handling 2 (4 pts) (nesting depth added 4). Of this number, 18 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
D2 · Cognitive Complexity · color-tokens.collectCompiledColorTokens (cognitive 20) · ×1
  • color-tokens.collectCompiledColorTokens (cognitive 20) apps/web/src/features/resume/stylesheet/color-tokens.ts:31 — color-tokens.collectCompiledColorTokens has cognitive complexity 20 (threshold 15). Drivers by points: if/else 4 (12 pts), loops 3 (6 pts), boolean chains 2 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · app-shell.AppShell (cognitive 20) · ×1
  • app-shell.AppShell (cognitive 20) apps/web/src/routes/dashboard/-components/app-shell.tsx:141 — app-shell.AppShell has cognitive complexity 20 (threshold 15). Drivers by points: boolean chains 9, ternaries 4 (6 pts), if/else 5 (nesting depth added 2). Of this number, 10 points are the body's own statements and 10 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.
D2 · Cognitive Complexity · write-panel.BodySection (cognitive 20) · ×1
  • write-panel.BodySection (cognitive 20) apps/web/src/routes/builder/letter/-components/write-panel.tsx:755 — write-panel.BodySection has cognitive complexity 20 (threshold 15). Drivers by points: boolean chains 9, ternaries 5 (7 pts), if/else 3 (4 pts) (nesting depth added 3). Of this number, 12 points are the body's own statements and 8 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.
D2 · Cognitive Complexity · LocalStorageService.list (cognitive 20) · ×1
  • LocalStorageService.list (cognitive 20) packages/api/src/features/storage/service.ts:165 — LocalStorageService.list has cognitive complexity 20 (threshold 15). Drivers by points: if/else 4 (12 pts), error handling 2 (5 pts), boolean chains 2, ternaries 1 (nesting depth added 11). 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 into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · html-to-docx.collectInlineChildren (cognitive 20) · ×1
  • html-to-docx.collectInlineChildren (cognitive 20) packages/docx/src/html-to-docx.ts:109 — html-to-docx.collectInlineChildren has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (15 pts), ternaries 1 (3 pts), boolean chains 1, loops 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · files.woffToSfnt (cognitive 20) · ×1
  • files.woffToSfnt (cognitive 20) packages/fonts/src/files.ts:6 — files.woffToSfnt has cognitive complexity 20 (threshold 15). Drivers by points: if/else 9 (13 pts), loops 4 (5 pts), boolean chains 2 (nesting depth added 5). Of this number, 12 points are the body's own statements and 8 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · to-forme.fitImage (cognitive 20) · ×1
  • to-forme.fitImage (cognitive 20) packages/pdf/src/forme/to-forme.tsx:747 — to-forme.fitImage has cognitive complexity 20 (threshold 15). Drivers by points: ternaries 8 (13 pts), boolean chains 4, if/else 3 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · render.listPaginationRepairs (cognitive 20) · ×1
  • render.listPaginationRepairs (cognitive 20) packages/pdf/src/forme/render.ts:275 — render.listPaginationRepairs has cognitive complexity 20 (threshold 15). Drivers by points: if/else 5 (7 pts), ternaries 4 (7 pts), boolean chains 4, loops 2 (nesting depth added 5). None of this is in the body itself: all 20 points belong to 3 function literals inside it that branch (lines 283, 314, 282). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · markdown.renderCustomSection (cognitive 20) · ×1
  • markdown.renderCustomSection (cognitive 20) packages/resume/src/markdown.ts:375 — markdown.renderCustomSection has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (13 pts), loops 2 (4 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.
D2 · Cognitive Complexity · proposals.quoteNormalized (cognitive 20) · ×1
  • proposals.quoteNormalized (cognitive 20) packages/resume/src/proposals.ts:445 — proposals.quoteNormalized has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (14 pts), boolean chains 3, ternaries 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.
D2 · Cognitive Complexity · css-escape.escapeCssIdentifier (cognitive 20) · ×1
  • css-escape.escapeCssIdentifier (cognitive 20) packages/resume/src/stylesheet/css-escape.ts:1 — css-escape.escapeCssIdentifier has cognitive complexity 20 (threshold 15). Drivers by points: boolean chains 10, if/else 6 (9 pts), loops 1 (nesting depth added 3). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · period.parseEndpoint (cognitive 20) · ×1
  • period.parseEndpoint (cognitive 20) packages/schema/src/resume/period.ts:155 — period.parseEndpoint has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (9 pts), ternaries 3 (7 pts), boolean chains 4 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · url-security.node.fetchPublic (cognitive 20) · ×1
  • url-security.node.fetchPublic (cognitive 20) packages/utils/src/url-security.node.ts:154 — url-security.node.fetchPublic has cognitive complexity 20 (threshold 15). Drivers by points: if/else 6, ternaries 5 (6 pts), boolean chains 4, loops 2 (3 pts), error handling 1 (nesting depth added 2). 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 174, 210). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · mirror.planMirror (cognitive 20) · ×1
  • mirror.planMirror (cognitive 20) tooling/fonts/mirror.ts:16 — mirror.planMirror has cognitive complexity 20 (threshold 15). Drivers by points: loops 7 (11 pts), if/else 3 (5 pts), ternaries 2 (4 pts) (nesting depth added 8). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
D2 · Cognitive Complexity · store.createDraftStore.resolveConflict (cognitive 19) · ×1
  • store.createDraftStore.resolveConflict (cognitive 19) apps/mobile/src/data/draft/store.ts:517 — store.createDraftStore.resolveConflict has cognitive complexity 19 (threshold 15). Drivers by points: if/else 10 (14 pts), boolean chains 4, 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.
D2 · Cognitive Complexity · capture.StoryboardController (cognitive 19) · ×1
  • capture.StoryboardController (cognitive 19) apps/mobile/src/dev/storyboard/capture.tsx:72 — capture.StoryboardController has cognitive complexity 19 (threshold 15). Drivers by points: if/else 11 (13 pts), boolean chains 3, loops 2, ternaries 1 (nesting depth added 2). Most of this is not in the body itself: 3 of the 19 points are its own statements and the rest belongs to 7 function literals inside it that branch (lines 96, 83, 79, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · InsightsScreen.InsightsScreen (cognitive 19) · ×1
  • InsightsScreen.InsightsScreen (cognitive 19) apps/mobile/src/features/applications/InsightsScreen.tsx:24 — InsightsScreen.InsightsScreen has cognitive complexity 19 (threshold 15). Drivers by points: ternaries 9 (19 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.
D2 · Cognitive Complexity · StageSheet.SentStep (cognitive 19) · ×1
  • StageSheet.SentStep (cognitive 19) apps/mobile/src/features/applications/StageSheet.tsx:118 — StageSheet.SentStep has cognitive complexity 19 (threshold 15). Drivers by points: ternaries 5 (10 pts), if/else 4 (6 pts), boolean chains 2, error handling 1 (nesting depth added 7). Most of this is not in the body itself: 4 of the 19 points are its own statements and the rest belongs to 4 function items inside it that branch (confirm, pick, a function literal at line 176, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · TwoStepScreen.TwoStepScreen (cognitive 19) · ×1
  • TwoStepScreen.TwoStepScreen (cognitive 19) apps/mobile/src/features/auth/TwoStepScreen.tsx:17 — TwoStepScreen.TwoStepScreen has cognitive complexity 19 (threshold 15). Drivers by points: ternaries 11 (15 pts), if/else 3, boolean chains 1 (nesting depth added 4). Of this number, 11 points are the body's own statements and 8 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.
D2 · Cognitive Complexity · EntryActionsSheet.EntryActionsSheet (cognitive 19) · ×1
  • EntryActionsSheet.EntryActionsSheet (cognitive 19) apps/mobile/src/features/builder/entry/EntryActionsSheet.tsx:13 — EntryActionsSheet.EntryActionsSheet has cognitive complexity 19 (threshold 15). Drivers by points: ternaries 7 (9 pts), boolean chains 8, if/else 2 (nesting depth added 2). Of this number, 12 points are the body's own statements and 7 belong to 4 function items inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
D2 · Cognitive Complexity · OverviewScreen.OverviewScreen (cognitive 19) · ×1
  • OverviewScreen.OverviewScreen (cognitive 19) apps/mobile/src/features/builder/overview/OverviewScreen.tsx:112 — OverviewScreen.OverviewScreen has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (8 pts), boolean chains 6, ternaries 4 (5 pts) (nesting depth added 3). Most of this is not in the body itself: 7 of the 19 points are its own statements and the rest belongs to 7 function items inside it that branch (a function literal at line 126, a function literal at line 200, addSection, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · web-page-screen.WebPageScreen (cognitive 19) · ×1
  • web-page-screen.WebPageScreen (cognitive 19) apps/mobile/src/features/builder/share/web-page-screen.tsx:25 — web-page-screen.WebPageScreen has cognitive complexity 19 (threshold 15). Drivers by points: boolean chains 10, if/else 6, ternaries 3. Most of this is not in the body itself: 7 of the 19 points are its own statements and the rest belongs to 7 function items inside it that branch (a function literal at line 61, saveSlug, a function literal at line 57, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · versions-screen.VersionsScreen (cognitive 19) · ×1
  • versions-screen.VersionsScreen (cognitive 19) apps/mobile/src/features/builder/versions/versions-screen.tsx:33 — versions-screen.VersionsScreen has cognitive complexity 19 (threshold 15). Drivers by points: ternaries 9 (11 pts), boolean chains 5, if/else 3 (nesting depth added 2). Most of this is not in the body itself: 5 of the 19 points are its own statements and the rest belongs to 5 function items inside it that branch (a function literal at line 167, rename, saveName, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · notifications.syncTodayNotifications.run (cognitive 19) · ×1
  • notifications.syncTodayNotifications.run (cognitive 19) apps/mobile/src/features/system/notifications.tsx:33 — notifications.syncTodayNotifications.run has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (14 pts), loops 2, ternaries 1 (2 pts), boolean chains 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · notifications.TodayNotifications (cognitive 19) · ×1
  • notifications.TodayNotifications (cognitive 19) apps/mobile/src/features/system/notifications.tsx:85 — notifications.TodayNotifications has cognitive complexity 19 (threshold 15). Drivers by points: if/else 11 (13 pts), boolean chains 3, loops 2, ternaries 1 (nesting depth added 2). None of this is in the body itself: all 19 points belong to 7 function literals inside it that branch (lines 141, 112, 93, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · PageZoom.PageZoom (cognitive 19) · ×1
  • PageZoom.PageZoom (cognitive 19) apps/mobile/src/ui/PageZoom.tsx:41 — PageZoom.PageZoom has cognitive complexity 19 (threshold 15). Drivers by points: if/else 10 (11 pts), ternaries 4 (5 pts), boolean chains 3 (nesting depth added 2). None of this is in the body itself: all 19 points belong to 8 function items inside it that branch (zoomTo, a function literal at line 126, a function literal at line 139, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · app.createApp (cognitive 19) · ×1
  • app.createApp (cognitive 19) apps/server/src/http/app.ts:72 — app.createApp has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9 (11 pts), ternaries 4 (5 pts), boolean chains 2, loops 1 (nesting depth added 3). Of this number, 12 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.
D2 · Cognitive Complexity · tag-chips.TagChips (cognitive 19) · ×1
  • tag-chips.TagChips (cognitive 19) apps/web/src/features/applications/components/tag-chips.tsx:15 — tag-chips.TagChips has cognitive complexity 19 (threshold 15). Drivers by points: ternaries 4 (7 pts), boolean chains 6, if/else 3 (4 pts), loops 2 (nesting depth added 4). Most of this is not in the body itself: 2 of the 19 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 41, 21, 18). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · board.ApplicationBoard (cognitive 19) · ×1
  • board.ApplicationBoard (cognitive 19) apps/web/src/features/applications/components/board.tsx:60 — board.ApplicationBoard has cognitive complexity 19 (threshold 15). Drivers by points: boolean chains 8, if/else 5, ternaries 5, loops 1. Most of this is not in the body itself: 9 of the 19 points are its own statements and the rest belongs to 6 function items inside it that branch (onDragEnd, laneOf, a function literal at line 89, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · conversation.MessageView (cognitive 19) · ×1
  • conversation.MessageView (cognitive 19) apps/web/src/features/assistant/conversation.tsx:555 — conversation.MessageView has cognitive complexity 19 (threshold 15). Drivers by points: boolean chains 15, if/else 2, ternaries 1 (2 pts) (nesting depth added 1). Of this number, 13 points are the body's own statements and 6 belong to 4 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · shared.MemoryProposal (cognitive 19) · ×1
  • shared.MemoryProposal (cognitive 19) apps/web/src/features/career/shared.tsx:538 — shared.MemoryProposal has cognitive complexity 19 (threshold 15). Drivers by points: ternaries 6 (17 pts), boolean chains 1, if/else 1 (nesting depth added 11). Of this number, 11 points are the body's own statements and 8 belong to 2 function literals inside it that branch. To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
D2 · Cognitive Complexity · application-packet.PacketForm (cognitive 19) · ×1
  • application-packet.PacketForm (cognitive 19) apps/web/src/features/career/workspace/application-packet.tsx:55 — application-packet.PacketForm has cognitive complexity 19 (threshold 15). Drivers by points: boolean chains 12, if/else 6, error handling 1. Of this number, 10 points are the body's own statements and 9 belong to 11 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · practise.HearIt (cognitive 19) · ×1
  • practise.HearIt (cognitive 19) apps/web/src/features/career/workspace/practise.tsx:1013 — practise.HearIt has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (12 pts), boolean chains 3, ternaries 3, error handling 1 (nesting depth added 4). Most of this is not in the body itself: 5 of the 19 points are its own statements and the rest belongs to one function item inside it that branches (play). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · schedule-sheet.ScheduleSheet · ×1
  • schedule-sheet.ScheduleSheet::onSave (cognitive 19) apps/web/src/features/career/schedule-sheet.tsx:241 — schedule-sheet.ScheduleSheet::onSave has cognitive complexity 19 (threshold 15). Drivers by points: ternaries 9 (11 pts), boolean chains 6, if/else 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. This shape REPEATS in the file: one other method here (schedule-sheet.ScheduleSheet) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D2 · Cognitive Complexity · content.CommandPaletteContent (cognitive 19) · ×1
  • content.CommandPaletteContent (cognitive 19) apps/web/src/features/command-palette/content.tsx:32 — content.CommandPaletteContent has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8, boolean chains 7, ternaries 3 (4 pts) (nesting depth added 1). Of this number, 10 points are the body's own statements and 9 belong to 4 function literals inside it that branch. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · documents-page.DocumentsPage · ×1
  • documents-page.DocumentsPage::onSearchKeyDown (cognitive 19) apps/web/src/features/documents/documents-page.tsx:289 — documents-page.DocumentsPage::onSearchKeyDown has cognitive complexity 19 (threshold 15). Drivers by points: if/else 10 (16 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. This shape REPEATS in the file: one other method here (documents-page.DocumentsPage) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D2 · Cognitive Complexity · typography.TypographySectionBuilder (cognitive 19) · ×1
  • typography.TypographySectionBuilder (cognitive 19) apps/web/src/routes/builder/$resumeId/-sidebar/right/sections/typography.tsx:11 — typography.TypographySectionBuilder has cognitive complexity 19 (threshold 15). Drivers by points: ternaries 13 (15 pts), if/else 4 (nesting depth added 2). Most of this is not in the body itself: 1 of the 19 points is its own statement and the rest belongs to 4 function literals inside it that branch (lines 16, 63, 28, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · tools.buildAgentInstructions (cognitive 19) · ×1
  • tools.buildAgentInstructions (cognitive 19) packages/api/src/features/agent/tools.ts:72 — tools.buildAgentInstructions has cognitive complexity 19 (threshold 15). Drivers by points: ternaries 13 (18 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.
D2 · Cognitive Complexity · export-uploads.exportAccountUploads (cognitive 19) · ×1
  • export-uploads.exportAccountUploads (cognitive 19) packages/api/src/features/auth/export-uploads.ts:8 — export-uploads.exportAccountUploads has cognitive complexity 19 (threshold 15). Drivers by points: if/else 18 (39 pts), ternaries 3 (8 pts), boolean chains 6, error handling 2 (5 pts), loops 3 (5 pts) (nesting depth added 31). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function. This shape REPEATS in the file: one other method here (export-uploads.exportAccountUploads::visit) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D2 · Cognitive Complexity · builder.buildHeader (cognitive 19) · ×1
  • builder.buildHeader (cognitive 19) packages/docx/src/builder.ts:139 — builder.buildHeader has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9 (10 pts), boolean chains 6, ternaries 1 (2 pts), loops 1 (nesting depth added 2). 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: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
D2 · Cognitive Complexity · pdf-lines.wrappedRightCell (cognitive 19) · ×1
  • pdf-lines.wrappedRightCell (cognitive 19) packages/import/src/pdf-lines.ts:1653 — pdf-lines.wrappedRightCell has cognitive complexity 19 (threshold 15). Drivers by points: ternaries 5 (7 pts), if/else 4 (6 pts), boolean chains 5, loops 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · picture-shadow.convolve (cognitive 19) · ×1
  • picture-shadow.convolve (cognitive 19) packages/pdf/src/templates/shared/picture-shadow.ts:23 — picture-shadow.convolve has cognitive complexity 19 (threshold 15). Drivers by points: ternaries 2 (8 pts), loops 3 (6 pts), if/else 1 (4 pts), boolean chains 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · images.node.readServerImage (cognitive 19) · ×1
  • images.node.readServerImage (cognitive 19) packages/pdf/src/forme/images.node.ts:13 — images.node.readServerImage has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (9 pts), boolean chains 6, error handling 1 (2 pts), ternaries 2 (nesting depth added 2). Most of this is not in the body itself: 8 of the 19 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 39, 37, 57). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · career-offer.parseOfferEntry (cognitive 19) · ×1
  • career-offer.parseOfferEntry (cognitive 19) packages/schema/src/career-offer.ts:18 — career-offer.parseOfferEntry has cognitive complexity 19 (threshold 15). Drivers by points: ternaries 12 (16 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.
D2 · Cognitive Complexity · signature · ×1
  • signature::argument (cognitive 19) tooling/locales/catalog-diff.mjs:55 — signature::argument has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (12 pts), boolean chains 3, loops 2 (3 pts), other 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · consent.ensureApproved (cognitive 18) · ×1
  • consent.ensureApproved (cognitive 18) apps/mobile/src/data/consent.ts:63 — consent.ensureApproved has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (9 pts), boolean chains 7, 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 one function literal inside it that branches (line 77). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · download-screen.ExportContent (cognitive 18) · ×1
  • download-screen.ExportContent (cognitive 18) apps/mobile/src/features/builder/download/download-screen.tsx:32 — download-screen.ExportContent has cognitive complexity 18 (threshold 15). Drivers by points: ternaries 16 (17 pts), if/else 10 (14 pts), boolean chains 11, error handling 1 (nesting depth added 5). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level. This shape REPEATS in the file: one other method here (download-screen.ExportContent::exportFile) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D2 · Cognitive Complexity · scaffold.PushScreen (cognitive 18) · ×1
  • scaffold.PushScreen (cognitive 18) apps/mobile/src/ui/scaffold.tsx:153 — scaffold.PushScreen has cognitive complexity 18 (threshold 15). Drivers by points: ternaries 11 (17 pts), boolean chains 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · handler.handleMcp (cognitive 18) · ×1
  • handler.handleMcp (cognitive 18) apps/server/src/mcp/handler.ts:24 — handler.handleMcp has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (8 pts), ternaries 2 (5 pts), boolean chains 2, error handling 2, loops 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · list-view.ApplicationRow (cognitive 18) · ×1
  • list-view.ApplicationRow (cognitive 18) apps/web/src/features/applications/components/list-view.tsx:345 — list-view.ApplicationRow has cognitive complexity 18 (threshold 15). Drivers by points: boolean chains 11, ternaries 4 (5 pts), if/else 2 (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, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · next-step-card.FollowUpDialog (cognitive 18) · ×1
  • next-step-card.FollowUpDialog (cognitive 18) apps/web/src/features/applications/components/detail/next-step-card.tsx:161 — next-step-card.FollowUpDialog has cognitive complexity 18 (threshold 15). Drivers by points: ternaries 4 (8 pts), boolean chains 6, if/else 3 (4 pts) (nesting depth added 5). Of this number, 11 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.
D2 · Cognitive Complexity · chat-chrome.ChatComposer (cognitive 18) · ×1
  • chat-chrome.ChatComposer (cognitive 18) apps/web/src/features/assistant/chat-chrome.tsx:83 — chat-chrome.ChatComposer has cognitive complexity 18 (threshold 15). Drivers by points: ternaries 7 (8 pts), boolean chains 6, if/else 3 (4 pts) (nesting depth added 2). Of this number, 11 points are the body's own statements and 7 belong to one function literal inside it that branches. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
D2 · Cognitive Complexity · messages.ReplyCard (cognitive 18) · ×1
  • messages.ReplyCard (cognitive 18) apps/web/src/features/career/workspace/messages.tsx:380 — messages.ReplyCard has cognitive complexity 18 (threshold 15). Drivers by points: boolean chains 24, if/else 10 (15 pts), ternaries 4 (5 pts), error handling 1 (nesting depth added 6). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators. This shape REPEATS in the file: one other method here (messages.ReplyCard::copy) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D2 · Cognitive Complexity · facts.FactRow (cognitive 18) · ×1
  • facts.FactRow (cognitive 18) apps/web/src/features/career/knowledge/facts.tsx:556 — facts.FactRow has cognitive complexity 18 (threshold 15). Drivers by points: ternaries 10 (11 pts), boolean chains 7 (nesting depth added 1). 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: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · today.ScheduleResults (cognitive 18) · ×1
  • today.ScheduleResults (cognitive 18) apps/web/src/features/career/today.tsx:501 — today.ScheduleResults has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8, boolean chains 5, ternaries 4 (5 pts) (nesting depth added 1). Most of this is not in the body itself: 2 of the 18 points are its own statements and the rest belongs to 5 function items inside it that branch (detail, a function literal at line 575, title, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · today.SchedulesPanel · ×1
  • today.SchedulesPanel::status (cognitive 18) apps/web/src/features/career/today.tsx:1152 — today.SchedulesPanel::status has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (10 pts), ternaries 3 (6 pts), boolean chains 2 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · document-card.DocumentRow (cognitive 18) · ×1
  • document-card.DocumentRow (cognitive 18) apps/web/src/features/documents/document-card.tsx:361 — document-card.DocumentRow has cognitive complexity 18 (threshold 15). Drivers by points: boolean chains 11, ternaries 5 (6 pts), if/else 1 (nesting depth added 1). Of this number, 16 points are the body's own statements and 2 belong to one function item inside it that branches. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · password-dialog.ResumePasswordDialog (cognitive 18) · ×1
  • password-dialog.ResumePasswordDialog (cognitive 18) apps/web/src/features/resume/builder/password-dialog.tsx:23 — password-dialog.ResumePasswordDialog has cognitive complexity 18 (threshold 15). Drivers by points: boolean chains 7, ternaries 6 (7 pts), if/else 3, error handling 1 (nesting depth added 1). Most of this is not in the body itself: 6 of the 18 points are its own statements and the rest belongs to 2 function items inside it that branch (submit, a function literal at line 61). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · proposal-list.changeParts (cognitive 18) · ×1
  • proposal-list.changeParts (cognitive 18) apps/web/src/features/resume/editor/proposals/proposal-list.tsx:57 — proposal-list.changeParts has cognitive complexity 18 (threshold 15). Drivers by points: boolean chains 8, if/else 6, loops 4. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · read-file.readResumeFile (cognitive 18) · ×1
  • read-file.readResumeFile (cognitive 18) apps/web/src/features/resume/import/read-file.ts:139 — read-file.readResumeFile has cognitive complexity 18 (threshold 15). Drivers by points: ternaries 5 (10 pts), if/else 6 (7 pts), boolean chains 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · service.testFailureKind (cognitive 18) · ×1
  • service.testFailureKind (cognitive 18) packages/api/src/features/ai/service.ts:212 — service.testFailureKind has cognitive complexity 18 (threshold 15). Drivers by points: if/else 10 (15 pts), boolean chains 3 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · level.parseLevel (cognitive 18) · ×1
  • level.parseLevel (cognitive 18) packages/import/src/level.ts:6 — level.parseLevel has cognitive complexity 18 (threshold 15). Drivers by points: if/else 13, boolean chains 5. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · sections.renderSection (cognitive 18) · ×1
  • sections.renderSection (cognitive 18) packages/odt/src/sections.ts:129 — sections.renderSection has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (8 pts), ternaries 3 (6 pts), boolean chains 4 (nesting depth added 5). Of this number, 13 points are the body's own statements and 5 belong to 2 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · page-map.extractPageMap.pages · ×1
  • page-map.extractPageMap.pages::visit (cognitive 18) packages/pdf/src/page-map.ts:177 — page-map.extractPageMap.pages::visit has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (7 pts), boolean chains 5, loops 2 (3 pts), ternaries 1 (3 pts) (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · style.toColor (cognitive 18) · ×1
  • style.toColor (cognitive 18) packages/pdf/src/forme/style.ts:150 — style.toColor has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (13 pts), ternaries 2 (4 pts), boolean chains 1 (nesting depth added 7). 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.
D2 · Cognitive Complexity · style.flattenAlpha (cognitive 18) · ×1
  • style.flattenAlpha (cognitive 18) packages/pdf/src/forme/style.ts:215 — style.flattenAlpha has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (12 pts), ternaries 3, boolean chains 2, loops 1 (nesting depth added 4). Of this number, 13 points are the body's own statements and 5 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.
D2 · Cognitive Complexity · text.renderChildren (cognitive 18) · ×1
  • text.renderChildren (cognitive 18) packages/pdf/src/text.tsx:152 — text.renderChildren has cognitive complexity 18 (threshold 15). Drivers by points: boolean chains 9, if/else 5 (7 pts), ternaries 2 (nesting depth added 2). Most of this is not in the body itself: 3 of the 18 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 158, 175). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · picture-shadow.getPictureShadow (cognitive 18) · ×1
  • picture-shadow.getPictureShadow (cognitive 18) packages/pdf/src/templates/shared/picture-shadow.ts:43 — picture-shadow.getPictureShadow has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8, boolean chains 5, loops 4 (5 pts) (nesting depth added 1). Of this number, 15 points are the body's own statements and 3 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.
D2 · Cognitive Complexity · sections.ExperienceSection (cognitive 18) · ×1
  • sections.ExperienceSection (cognitive 18) packages/pdf/src/templates/shared/sections.tsx:1093 — sections.ExperienceSection has cognitive complexity 18 (threshold 15). Drivers by points: ternaries 9, boolean chains 6, 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 4 function literals inside it that branch (lines 1142, 1190, 1113, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · render.renderResumeElement (cognitive 18) · ×1
  • render.renderResumeElement (cognitive 18) packages/pdf/src/forme/render.ts:385 — render.renderResumeElement has cognitive complexity 18 (threshold 15). Drivers by points: if/else 22 (39 pts), loops 7 (14 pts), boolean chains 8, ternaries 2 (3 pts) (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. This shape REPEATS in the file: one other method here (render.renderResumeElement::layOut) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D2 · Cognitive Complexity · style-rules.toStyle (cognitive 18) · ×1
  • style-rules.toStyle (cognitive 18) packages/pdf/src/templates/shared/style-rules.ts:46 — style-rules.toStyle has cognitive complexity 18 (threshold 15). Drivers by points: if/else 14 (16 pts), loops 2 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
D2 · Cognitive Complexity · rules.fragmentPointers (cognitive 18) · ×1
  • rules.fragmentPointers (cognitive 18) packages/resume/src/ats/rules.ts:239 — rules.fragmentPointers has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (11 pts), boolean chains 4, ternaries 1 (2 pts), loops 1 (nesting depth added 6). Most of this is not in the body itself: 5 of the 18 points are its own statements and the rest belongs to one function literal inside it that branches (line 248). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · ApplicationsScreen.ApplicationsScreen (cognitive 17) · ×1
  • ApplicationsScreen.ApplicationsScreen (cognitive 17) apps/mobile/src/features/applications/ApplicationsScreen.tsx:86 — ApplicationsScreen.ApplicationsScreen has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 6 (12 pts), if/else 2 (3 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.
D2 · Cognitive Complexity · ConsentScreen.ConsentScreen (cognitive 17) · ×1
  • ConsentScreen.ConsentScreen (cognitive 17) apps/mobile/src/features/auth/ConsentScreen.tsx:31 — ConsentScreen.ConsentScreen has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 6, ternaries 6, if/else 5. Of this number, 12 points are the body's own statements and 5 belong to 2 function items inside it that branch. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · DebriefScreen.DebriefScreen (cognitive 17) · ×1
  • DebriefScreen.DebriefScreen (cognitive 17) apps/mobile/src/features/workspace/DebriefScreen.tsx:28 — DebriefScreen.DebriefScreen has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 8 (11 pts), boolean chains 4, error handling 1, if/else 1 (nesting depth added 3). Of this number, 11 points are the body's own statements and 6 belong to 4 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · page-renderer.serverPdf (cognitive 17) · ×1
  • page-renderer.serverPdf (cognitive 17) apps/mobile/src/render/page-renderer.ts:97 — page-renderer.serverPdf has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (12 pts), boolean chains 4, 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.
D2 · Cognitive Complexity · generator.addCurlSamples · ×1
  • generator.addCurlSamples::example (cognitive 17) apps/server/src/openapi/generator.ts:275 — generator.addCurlSamples::example has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9, boolean chains 4, ternaries 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. This shape REPEATS in the file: one other method here (generator.addCurlSamples) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D2 · Cognitive Complexity · display.LevelDisplay (cognitive 17) · ×1
  • display.LevelDisplay (cognitive 17) apps/web/src/components/level/display.tsx:18 — display.LevelDisplay has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 11, if/else 4, ternaries 2. Most of this is not in the body itself: 6 of the 17 points are its own statements 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.
D2 · Cognitive Complexity · insights-view.ApplicationInsights (cognitive 17) · ×1
  • insights-view.ApplicationInsights (cognitive 17) apps/web/src/features/applications/components/insights-view.tsx:53 — insights-view.ApplicationInsights has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 8 (12 pts), boolean chains 5 (nesting depth added 4). Of this number, 13 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.
D2 · Cognitive Complexity · pdf-viewer.PdfViewer (cognitive 17) · ×1
  • pdf-viewer.PdfViewer (cognitive 17) apps/web/src/features/ats-checker/pdf-viewer.tsx:59 — pdf-viewer.PdfViewer has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (10 pts), ternaries 4 (5 pts), boolean chains 2 (nesting depth added 2). Most of this is not in the body itself: 5 of the 17 points are its own statements and the rest belongs to 7 function literals inside it that branch (lines 121, 65, 106, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · schedules.useSchedules.status (cognitive 17) · ×1
  • schedules.useSchedules.status (cognitive 17) apps/web/src/features/career/schedules.tsx:101 — schedules.useSchedules.status has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (10 pts), ternaries 3 (6 pts), boolean chains 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · career-page.useStarters (cognitive 17) · ×1
  • career-page.useStarters (cognitive 17) apps/web/src/features/career/career-page.tsx:261 — career-page.useStarters has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 8 (14 pts), boolean chains 2, match/switch 1 (nesting depth added 6). Most of this is not in the body itself: 2 of the 17 points are its own statements and the rest belongs to 4 function items inside it that branch (word, a function literal at line 307, a function literal at line 368, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · new-document-dialog.CopyForJob · ×1
  • new-document-dialog.CopyForJob::create (cognitive 17) apps/web/src/features/documents/new-document-dialog.tsx:680 — new-document-dialog.CopyForJob::create has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 7 (12 pts), boolean chains 2, if/else 2, 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. This shape REPEATS in the file: one other method here (new-document-dialog.CopyForJob) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D2 · Cognitive Complexity · issues.describeFinding (cognitive 17) · ×1
  • issues.describeFinding (cognitive 17) apps/web/src/features/resume/editor/check/issues.ts:117 — issues.describeFinding has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (9 pts), loops 2 (4 pts), ternaries 1 (2 pts), boolean chains 1, match/switch 1 (nesting depth added 8). Most of this is not in the body itself: 3 of the 17 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 325, 299, 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.
D2 · Cognitive Complexity · page-layer.PageViewToggle (cognitive 17) · ×1
  • page-layer.PageViewToggle (cognitive 17) apps/web/src/features/resume/editor/check/page-layer.tsx:224 — page-layer.PageViewToggle has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 6 (9 pts), boolean chains 8 (nesting depth added 3). 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.
D2 · Cognitive Complexity · outline.Outline (cognitive 17) · ×1
  • outline.Outline (cognitive 17) apps/web/src/features/resume/editor/write/outline.tsx:106 — outline.Outline has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 8, if/else 6, ternaries 3. None of this is in the body itself: all 17 points belong to 4 function items inside it that branch (move, a function literal at line 154, onDragEnd, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · share-panel.ShareHome (cognitive 17) · ×1
  • share-panel.ShareHome (cognitive 17) apps/web/src/features/resume/share/share-panel.tsx:89 — share-panel.ShareHome has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 4 (8 pts), boolean chains 6, if/else 2 (3 pts) (nesting depth added 5). Of this number, 11 points are the body's own statements and 6 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.
D2 · Cognitive Complexity · proposal-applications.assertCurrentClientWrite (cognitive 17) · ×1
  • proposal-applications.assertCurrentClientWrite (cognitive 17) packages/api/src/features/agent/proposal-applications.ts:241 — proposal-applications.assertCurrentClientWrite has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (9 pts), loops 3 (6 pts), boolean chains 2 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · prose.assertResumeChangeProse (cognitive 17) · ×1
  • prose.assertResumeChangeProse (cognitive 17) packages/api/src/features/agent/prose.ts:50 — prose.assertResumeChangeProse has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (9 pts), boolean chains 3, loops 2 (3 pts), ternaries 2 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · reply-errors.replyErrorMessage (cognitive 17) · ×1
  • reply-errors.replyErrorMessage (cognitive 17) packages/api/src/features/agent/reply-errors.ts:10 — reply-errors.replyErrorMessage has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (11 pts), boolean chains 4, ternaries 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.
D2 · Cognitive Complexity · rate-limit.consumeLocally (cognitive 17) · ×1
  • rate-limit.consumeLocally (cognitive 17) packages/auth/src/rate-limit.ts:22 — rate-limit.consumeLocally has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (10 pts), boolean chains 3, loops 1 (3 pts), ternaries 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · parity.decodeInput (cognitive 17) · ×1
  • parity.decodeInput (cognitive 17) packages/mcp/src/parity.ts:345 — parity.decodeInput has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (9 pts), boolean chains 4, loops 1 (2 pts), ternaries 1 (2 pts) (nesting depth added 4). 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.
D2 · Cognitive Complexity · rich-text-html.projectNormalizedRichTextHtml (cognitive 17) · ×1
  • rich-text-html.projectNormalizedRichTextHtml (cognitive 17) REDACTED:287 — rich-text-html.projectNormalizedRichTextHtml has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (8 pts), ternaries 4 (5 pts), boolean chains 2, loops 2 (nesting depth added 3). Most of this is not in the body itself: 3 of the 17 points are its own statements and the rest belongs to 4 function items inside it that branch (visit, a function literal at line 329, a function literal at line 314, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · tree.applyTemplateManifest (cognitive 17) · ×1
  • tree.applyTemplateManifest (cognitive 17) packages/pdf/src/semantic/tree.ts:820 — tree.applyTemplateManifest has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (8 pts), ternaries 5, boolean chains 3, loops 1 (nesting depth added 4). Of this number, 16 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · tree.buildSemanticTree (cognitive 17) · ×1
  • tree.buildSemanticTree (cognitive 17) packages/pdf/src/semantic/tree.ts:951 — tree.buildSemanticTree has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (7 pts), boolean chains 5, ternaries 4 (5 pts) (nesting depth added 3). Most of this is not in the body itself: 6 of the 17 points are its own statements and the rest belongs to one function literal inside it that branches (line 975). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · sections.EducationSection (cognitive 17) · ×1
  • sections.EducationSection (cognitive 17) packages/pdf/src/templates/shared/sections.tsx:1290 — sections.EducationSection has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 8, ternaries 6, if/else 3. Most of this is not in the body itself: 1 of the 17 points is its own statement and the rest belongs to 3 function literals inside it that branch (lines 1339, 1391, 1310). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · render.documentText · ×1
  • render.documentText::visit (cognitive 17) packages/pdf/src/forme/render.ts:144 — render.documentText::visit has cognitive complexity 17 (threshold 15). Drivers by points: loops 4 (11 pts), if/else 4 (5 pts), boolean chains 1 (nesting depth added 8). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
D2 · Cognitive Complexity · contact.findLinkMismatches (cognitive 17) · ×1
  • contact.findLinkMismatches (cognitive 17) packages/resume/src/ats-pdf/analyze/contact.ts:75 — contact.findLinkMismatches has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (10 pts), boolean chains 4, ternaries 1 (2 pts), loops 1 (nesting depth added 6). Of this number, 16 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · harvest.toLinkAnnotations (cognitive 17) · ×1
  • harvest.toLinkAnnotations (cognitive 17) packages/resume/src/ats-pdf/harvest.ts:121 — harvest.toLinkAnnotations has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 5 (10 pts), if/else 3 (5 pts), boolean chains 1, loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · rules.urlRules (cognitive 17) · ×1
  • rules.urlRules (cognitive 17) packages/resume/src/ats/rules.ts:83 — rules.urlRules has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (7 pts), boolean chains 4, loops 2 (3 pts), ternaries 1 (3 pts) (nesting depth added 6). 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.
D2 · Cognitive Complexity · rules.structureRules (cognitive 17) · ×1
  • rules.structureRules (cognitive 17) packages/resume/src/ats/rules.ts:299 — rules.structureRules has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (8 pts), boolean chains 5, loops 3 (4 pts) (nesting depth added 5). Of this number, 16 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · structural-proposals.fieldPath (cognitive 17) · ×1
  • structural-proposals.fieldPath (cognitive 17) packages/resume/src/structural-proposals.ts:85 — structural-proposals.fieldPath has cognitive complexity 17 (threshold 15). Drivers by points: if/else 10 (12 pts), boolean chains 5 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
D2 · Cognitive Complexity · amount.parseLocalizedNumber (cognitive 17) · ×1
  • amount.parseLocalizedNumber (cognitive 17) packages/utils/src/amount.ts:1 — amount.parseLocalizedNumber has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (7 pts), boolean chains 5, loops 2 (3 pts), ternaries 2 (nesting depth added 2). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · mirror.license (cognitive 17) · ×1
  • mirror.license (cognitive 17) tooling/fonts/mirror.ts:90 — mirror.license has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (9 pts), error handling 2 (4 pts), ternaries 2 (3 pts), loops 1 (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.
D2 · Cognitive Complexity · boardData (cognitive 17) · ×1
  • boardData (cognitive 17) tooling/calm/seed.mjs:132 — boardData has cognitive complexity 17 (threshold 15). Drivers by points: loops 7, ternaries 2 (4 pts), if/else 2 (3 pts), boolean chains 2, other 1 (nesting depth added 3). Of this number, 13 points are the body's own statements and 4 belong to 4 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · failureBlocks (cognitive 17) · ×1
  • failureBlocks (cognitive 17) tooling/ci/failed-logs.mjs:15 — failureBlocks has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (12 pts), loops 3 (4 pts), boolean chains 1 (nesting depth added 5). Of this number, 10 points are the body's own statements and 7 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.
D2 · Cognitive Complexity · provider.DataProvider (cognitive 16) · ×1
  • provider.DataProvider (cognitive 16) apps/mobile/src/data/provider.tsx:23 — provider.DataProvider has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 8, ternaries 5 (6 pts), if/else 2 (nesting depth added 1). 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, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · export-file.prepareExport (cognitive 16) · ×1
  • export-file.prepareExport (cognitive 16) apps/mobile/src/features/builder/download/export-file.ts:15 — export-file.prepareExport has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (9 pts), ternaries 3 (6 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.
D2 · Cognitive Complexity · import.ScopedImportScreen · ×1
  • import.ScopedImportScreen::choose (cognitive 16) apps/mobile/src/features/documents/import.tsx:95 — import.ScopedImportScreen::choose has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (11 pts), ternaries 2 (3 pts), boolean chains 1, error handling 1 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level. This shape REPEATS in the file: one other method here (import.ScopedImportScreen) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D2 · Cognitive Complexity · new.ScopedNewDocumentScreen (cognitive 16) · ×1
  • new.ScopedNewDocumentScreen (cognitive 16) apps/mobile/src/features/documents/new.tsx:14 — new.ScopedNewDocumentScreen has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 6 (8 pts), if/else 5 (6 pts), boolean chains 1, error handling 1 (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 2 function items inside it that branch (create, a function literal at line 105). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · PullToRefresh.PullToRefresh (cognitive 16) · ×1
  • PullToRefresh.PullToRefresh (cognitive 16) apps/mobile/src/ui/PullToRefresh.tsx:56 — PullToRefresh.PullToRefresh has cognitive complexity 16 (threshold 15). Drivers by points: if/else 11, ternaries 3, boolean chains 2. Most of this is not in the body itself: 3 of the 16 points are its own statements and the rest belongs to 5 function literals inside it that branch (lines 90, 105, 71, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · Hero.FlightView (cognitive 16) · ×1
  • Hero.FlightView (cognitive 16) apps/mobile/src/ui/Hero.tsx:127 — Hero.FlightView has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 11 (12 pts), if/else 4 (nesting depth added 1). 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 134, 155, 185, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · cards.HeroCard (cognitive 16) · ×1
  • cards.HeroCard (cognitive 16) apps/mobile/src/ui/cards.tsx:15 — cards.HeroCard has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 10 (16 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Coordination.fetch (cognitive 16) · ×1
  • Coordination.fetch (cognitive 16) apps/server/src/cloudflare/coordination.ts:22 — Coordination.fetch has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6, boolean chains 3, error handling 1 (3 pts), loops 1 (2 pts), ternaries 2 (nesting depth added 3). Of this number, 9 points are the body's own statements and 7 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.
D2 · Cognitive Complexity · public-resume-download.handlePublicResumeDownload (cognitive 16) · ×1
  • public-resume-download.handlePublicResumeDownload (cognitive 16) apps/server/src/http/public-resume-download.ts:25 — public-resume-download.handlePublicResumeDownload has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (6 pts), ternaries 3 (6 pts), boolean chains 3, error handling 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · font-display.FontDisplay (cognitive 16) · ×1
  • font-display.FontDisplay (cognitive 16) apps/web/src/components/typography/font-display.tsx:43 — font-display.FontDisplay has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 8, boolean chains 5, if/else 3. Of this number, 10 points are the body's own statements and 6 belong to 4 function literals inside it that branch. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · get-next-weights.getNextWeights (cognitive 16) · ×1
  • get-next-weights.getNextWeights (cognitive 16) apps/web/src/components/typography/get-next-weights.ts:5 — get-next-weights.getNextWeights has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (7 pts), ternaries 3 (5 pts), boolean chains 3, loops 1 (nesting depth added 3). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · add-application-dialog.AddApplicationForm · ×1
  • add-application-dialog.AddApplicationForm::add (cognitive 16) apps/web/src/features/applications/components/add-application-dialog.tsx:389 — add-application-dialog.AddApplicationForm::add has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 7, boolean chains 5, if/else 2 (3 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. This shape REPEATS in the file: one other method here (add-application-dialog.AddApplicationForm) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D2 · Cognitive Complexity · add-application-dialog.ReadStatus (cognitive 16) · ×1
  • add-application-dialog.ReadStatus (cognitive 16) apps/web/src/features/applications/components/add-application-dialog.tsx:1100 — add-application-dialog.ReadStatus has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6, ternaries 3 (6 pts), boolean chains 4 (nesting depth added 3). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · forgot-password.ForgotPasswordPage (cognitive 16) · ×1
  • forgot-password.ForgotPasswordPage (cognitive 16) apps/web/src/features/auth/pages/forgot-password.tsx:34 — forgot-password.ForgotPasswordPage has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 9 (13 pts), if/else 2, boolean chains 1 (nesting depth added 4). Of this number, 12 points are the body's own statements and 4 belong to 3 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · saved.SavedRow (cognitive 16) · ×1
  • saved.SavedRow (cognitive 16) apps/web/src/features/career/workspace/saved.tsx:189 — saved.SavedRow has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 9 (11 pts), boolean chains 5 (nesting depth added 2). 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: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
D2 · Cognitive Complexity · import-page.ImportPage (cognitive 16) · ×1
  • import-page.ImportPage (cognitive 16) apps/web/src/features/documents/import/import-page.tsx:52 — import-page.ImportPage has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 7 (13 pts), boolean chains 2, if/else 1 (nesting depth added 6). 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.
D2 · Cognitive Complexity · groups.groupShortcuts (cognitive 16) · ×1
  • groups.groupShortcuts (cognitive 16) apps/web/src/features/keyboard-shortcuts/groups.ts:50 — groups.groupShortcuts has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (10 pts), boolean chains 3, ternaries 1 (2 pts), loops 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · entry-view.EntryBody (cognitive 16) · ×1
  • entry-view.EntryBody (cognitive 16) apps/web/src/features/resume/editor/write/entry-view.tsx:60 — entry-view.EntryBody has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 12, ternaries 3, 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.
D2 · Cognitive Complexity · letter-page.LetterOverlay (cognitive 16) · ×1
  • letter-page.LetterOverlay (cognitive 16) apps/web/src/routes/builder/letter/-components/letter-page.tsx:206 — letter-page.LetterOverlay has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 7, if/else 4 (5 pts), ternaries 4 (nesting depth added 1). Most of this is not in the body itself: 4 of the 16 points are its own statements and the rest belongs to 6 function items inside it that branch (a function literal at line 221, a function literal at line 212, a function literal at line 236, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · messages-persistence.upsertAssistantUiMessage (cognitive 16) · ×1
  • messages-persistence.upsertAssistantUiMessage (cognitive 16) packages/api/src/features/agent/messages-persistence.ts:319 — messages-persistence.upsertAssistantUiMessage has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (13 pts), boolean chains 2, ternaries 1 (nesting depth added 5). None of this is in the body itself: all 16 points belong to one function literal inside it that branches (line 329). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · embedded.adoptEmbeddedLetters (cognitive 16) · ×1
  • embedded.adoptEmbeddedLetters (cognitive 16) packages/api/src/features/cover-letters/embedded.ts:20 — embedded.adoptEmbeddedLetters has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (9 pts), loops 4 (5 pts), boolean chains 2 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · slugs.checkSlug (cognitive 16) · ×1
  • slugs.checkSlug (cognitive 16) packages/api/src/features/resume/slugs.ts:119 — slugs.checkSlug has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (8 pts), ternaries 3 (6 pts), boolean chains 2 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · review.entryReview (cognitive 16) · ×1
  • review.entryReview (cognitive 16) packages/api/src/features/agent/review.ts:16 — review.entryReview has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 5 (8 pts), boolean chains 4, if/else 4 (nesting depth added 3). None of this is in the body itself: all 16 points belong to 2 function literals inside it that branch (lines 18, 26). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · follow-up.syncFollowUp (cognitive 16) · ×1
  • follow-up.syncFollowUp (cognitive 16) packages/api/src/features/applications/follow-up.ts:11 — follow-up.syncFollowUp has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (7 pts), boolean chains 4, ternaries 4, loops 1 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · job-posting.jobPostingsFrom (cognitive 16) · ×1
  • job-posting.jobPostingsFrom (cognitive 16) packages/import/src/job-posting.ts:67 — job-posting.jobPostingsFrom has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 3 (5 pts), boolean chains 3, if/else 1 (3 pts), loops 2 (3 pts), error handling 1 (2 pts) (nesting depth added 6). Of this number, 14 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · tree.addCombinedTextHosts (cognitive 16) · ×1
  • tree.addCombinedTextHosts (cognitive 16) packages/pdf/src/semantic/tree.ts:911 — tree.addCombinedTextHosts has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (11 pts), boolean chains 3, ternaries 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.
D2 · Cognitive Complexity · render.unplacedBlocks (cognitive 16) · ×1
  • render.unplacedBlocks (cognitive 16) packages/pdf/src/forme/render.ts:173 — render.unplacedBlocks has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (7 pts), boolean chains 5, loops 3 (4 pts) (nesting depth added 3). 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 item inside it that branches (visit). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · tokenize.tokenize (cognitive 16) · ×1
  • tokenize.tokenize (cognitive 16) packages/resume/src/ats-pdf/jd/tokenize.ts:38 — tokenize.tokenize has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (12 pts), boolean chains 2, loops 1, ternaries 1 (nesting depth added 6). Of this number, 13 points are the body's own statements and 3 belong to 2 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · match.guessEmployerAndPlace (cognitive 16) · ×1
  • match.guessEmployerAndPlace (cognitive 16) packages/resume/src/ats-pdf/jd/match.ts:125 — match.guessEmployerAndPlace has cognitive complexity 16 (threshold 15). Drivers by points: if/else 3 (7 pts), loops 2 (4 pts), boolean chains 3, ternaries 1 (2 pts) (nesting depth added 7). Of this number, 15 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · word-diff.wordDiff (cognitive 16) · ×1
  • word-diff.wordDiff (cognitive 16) packages/resume/src/word-diff.ts:11 — word-diff.wordDiff has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (8 pts), loops 5 (6 pts), boolean chains 2 (nesting depth added 2). Of this number, 14 points are the body's own statements and 2 belong to one function item inside it that branches. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · preparation.nextPreparationStep (cognitive 16) · ×1
  • preparation.nextPreparationStep (cognitive 16) packages/schema/src/applications/preparation.ts:36 — preparation.nextPreparationStep has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 9, if/else 7. Of this number, 13 points are the body's own statements and 3 belong to one function item inside it that branches. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · mirror.prepareMirror (cognitive 16) · ×1
  • mirror.prepareMirror (cognitive 16) tooling/fonts/mirror.ts:131 — mirror.prepareMirror has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (11 pts), error handling 1 (2 pts), loops 2, boolean chains 1 (nesting depth added 6). Most of this is not in the body itself: 4 of the 16 points are its own statements and the rest belongs to one function literal inside it that branches (line 141). 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.
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D32 · Data Compliance (PII/GDPR) · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
P12 · CI test-gate honesty · CI test gate excludes suites by filter · ×1
  • CI test gate excludes suites by filter REDACTED:187 — `pnpm exec turbo run test:ci --concurrency=${{ vars.USE_BLACKSMITH == 'true' && 4 || 1 }} -- --maxWorkers=${{ vars.USE_BLACKSMITH == 'true…` drops 2 test(s) in 1 file(s) (e.g. `apps/mobile/src/dev/storyboard/edges.test.ts`), and no other gate runs them before merge. Run what it excludes in another job before merge (a complementary selection), or remove the exclusion.
R10 · Code Duplication · Duplication concentrated across 15 sibling directories (77 clone groups) · ×1
  • Duplication concentrated across 15 sibling directories (77 clone groups) apps/web/src/features/assistant/conversation.tsx:1081 — 77 duplicated blocks under apps/web/src/features/ have copies in at least two of the sibling directories ai, applications, assistant, ats-checker, auth, career (+9 more sibling(s) not listed) — 27 of them are reported below, and 50 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 77 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 77 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 77 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
R10 · Code Duplication · Duplication concentrated across 11 sibling directories (52 clone groups) · ×1
  • Duplication concentrated across 11 sibling directories (52 clone groups) packages/api/src/features/cover-letters/versions.ts:27 — 52 duplicated blocks under packages/api/src/features/ have copies in at least two of the sibling directories agent, ai-providers, application-profile, applications, auth, career (+5 more sibling(s) not listed) — 17 of them are reported below, and 35 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 52 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 52 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 52 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
R10 · Code Duplication · Duplication concentrated across 19 sibling directories (46 clone groups) · ×1
  • Duplication concentrated across 19 sibling directories (46 clone groups) packages/pdf/src/templates/ditgar/DitgarPage.tsx:1 — 46 duplicated blocks under packages/pdf/src/templates/ have copies in at least two of the sibling directories azurill, bronzor, chikorita, ditgar, ditto, gengar (+13 more sibling(s) not listed) — 36 of them are reported below, and 10 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 46 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 46 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 46 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
R10 · Code Duplication · Duplication concentrated across 13 sibling directories (42 clone groups) · ×1
  • Duplication concentrated across 13 sibling directories (42 clone groups) packages/docx/src/html-to-docx.ts:54 — 42 duplicated blocks under packages/ have copies in at least two of the sibling directories ai, api, auth, docx, email, env (+7 more sibling(s) not listed) — 20 of them are reported below, and 22 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 42 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 42 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 42 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
R10 · Code Duplication · Duplication concentrated across 4 sibling directories (41 clone groups) · ×1
  • Duplication concentrated across 4 sibling directories (41 clone groups) apps/web/src/features/resume/editor/save-status.tsx:94 — 41 duplicated blocks under apps/web/src/ have copies in at least two of the sibling directories components, dialogs, features, routes — 16 of them are reported below, and 25 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 41 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 41 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 41 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
R10 · Code Duplication · Duplication concentrated across 2 sibling directories (30 clone groups) · ×1
  • Duplication concentrated across 2 sibling directories (30 clone groups) apps/mobile/src/features/builder/check/issues.ts:29 — 30 duplicated blocks under apps/ have copies in at least two of the sibling directories mobile, web — 23 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 30 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 30 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 30 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
R10 · Code Duplication · Duplication concentrated across 3 sibling directories (27 clone groups) · ×1
  • Duplication concentrated across 3 sibling directories (27 clone groups) apps/server/src/cloudflare/r2.ts:24 — 27 duplicated blocks under the repository root have copies in at least two of the sibling directories apps, packages, tooling — 16 of them are reported below, and 11 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 27 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 27 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 27 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
R10 · Code Duplication · Duplication concentrated across 10 sibling directories (18 clone groups) · ×1
  • Duplication concentrated across 10 sibling directories (18 clone groups) apps/mobile/src/features/career/facts.tsx:12 — 18 duplicated blocks under apps/mobile/src/features/ have copies in at least two of the sibling directories applications, auth, builder, career, documents, letters (+4 more sibling(s) not listed) — 7 of them are reported below, and 11 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 18 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 18 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 18 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
R10 · Code Duplication · Duplication concentrated across 11 sibling directories (13 clone groups) · ×1
  • Duplication concentrated across 11 sibling directories (13 clone groups) apps/mobile/src/features/builder/design/LayoutScreen.tsx:72 — 13 duplicated blocks under apps/mobile/src/features/builder/ have copies in at least two of the sibling directories basics, check, description, design, download, entry (+5 more sibling(s) not listed) — 4 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 13 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 13 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 13 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
R10 · Code Duplication · Duplication concentrated across 2 sibling directories (10 clone groups) · ×1
  • Duplication concentrated across 2 sibling directories (10 clone groups) apps/web/src/routes/builder/$resumeId/-components/editor-shell.tsx:54 — 10 duplicated blocks under apps/web/src/routes/builder/ have copies in at least two of the sibling directories $resumeId, letter — 9 of them are reported below, and 1 is counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 10 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 10 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 10 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
R10 · Code Duplication · Duplication concentrated across 5 sibling directories (8 clone groups) · ×1
  • Duplication concentrated across 5 sibling directories (8 clone groups) apps/mobile/src/i18n/index.ts:23 — 8 duplicated blocks under apps/mobile/src/ have copies in at least two of the sibling directories data, features, i18n, render, ui — 4 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 8 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 8 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 8 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
R10 · Code Duplication · Duplication concentrated across 4 sibling directories (5 clone groups) · ×1
  • Duplication concentrated across 4 sibling directories (5 clone groups) apps/web/src/routes/agent/$threadId.tsx:51 — 5 duplicated blocks under apps/web/src/routes/ have copies in at least two of the sibling directories agent, auth, builder, dashboard — 2 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 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 (219 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (219 matched lines × 2 locations) apps/mobile/src/features/builder/check/issues.ts:29 — apps/mobile/src/features/builder/check/issues.ts:29 · apps/web/src/features/resume/editor/check/issues.ts:52 — the two spans are one implementation copied and then locally edited — 1270 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication · Wholesale file copy (206 identical lines × 2 files) · ×1
  • Wholesale file copy (206 identical lines × 2 files) packages/pdf/src/templates/ditgar/DitgarPage.tsx:1 — packages/pdf/src/templates/ditgar/DitgarPage.tsx:1 · packages/pdf/src/templates/gengar/GengarPage.tsx:1 — these 2 files are line-for-line copies of one another — 206 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 (128 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (128 matched lines × 2 locations) packages/pdf/src/templates/lapras/LaprasPage.tsx:17 — packages/pdf/src/templates/lapras/LaprasPage.tsx:17 · packages/pdf/src/templates/onyx/OnyxPage.tsx:17 — 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 (104 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (104 matched lines × 2 locations) packages/docx/src/html-to-docx.ts:54 — packages/docx/src/html-to-docx.ts:54 · packages/odt/src/html-to-odt.ts:12 — the two spans are one implementation copied and then locally edited — 704 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 (84 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (84 matched lines × 2 locations) packages/pdf/src/templates/gengar/GengarPage.tsx:83 — packages/pdf/src/templates/gengar/GengarPage.tsx:83 · packages/pdf/src/templates/pikachu/PikachuPage.tsx:78 — the two spans are one implementation copied and then locally edited — 505 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication · Duplicated block with local edits (83 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (83 matched lines × 2 locations) apps/web/src/features/career/schedules.tsx:41 — apps/web/src/features/career/schedules.tsx:41 · apps/web/src/features/career/today.tsx:1109 — the two spans are one implementation copied and then locally edited — 666 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication · Duplicated block with local edits (77 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (77 matched lines × 2 locations) apps/mobile/src/features/builder/design/presets.ts:25 — apps/mobile/src/features/builder/design/presets.ts:25 · apps/web/src/features/resume/editor/design/presets.ts:32 — the two spans are one implementation copied and then locally edited — 823 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 (73 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (73 matched lines × 2 locations) apps/web/src/dialogs/auth/disable-two-factor.tsx:30 — apps/web/src/dialogs/auth/disable-two-factor.tsx:30 · apps/web/src/dialogs/auth/set-password.tsx:28 — the two spans are one implementation copied and then locally edited — 462 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 (69 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (69 matched lines × 2 locations) apps/web/src/features/assistant/conversation.tsx:1081 — apps/web/src/features/assistant/conversation.tsx:1081 · apps/web/src/features/career/coach-thread.tsx:356 — the two spans are one implementation copied and then locally edited — 423 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 (58 lines × 2 locations) · ×1
  • Duplicated block (58 lines × 2 locations) apps/mobile/src/i18n/index.ts:23 — apps/mobile/src/i18n/index.ts:23 · apps/mobile/src/render/letter-words.ts:9 — 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 (56 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (56 matched lines × 2 locations) apps/mobile/src/features/workspace/FitScreen.tsx:88 — apps/mobile/src/features/workspace/FitScreen.tsx:88 · apps/mobile/src/features/workspace/PrepScreen.tsx:108 — the two spans are one implementation copied and then locally edited — 330 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 (54 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (54 matched lines × 2 locations) apps/web/src/features/resume/editor/save-status.tsx:94 — apps/web/src/features/resume/editor/save-status.tsx:94 · apps/web/src/routes/builder/letter/-components/letter-bar.tsx:323 — the two spans are one implementation copied and then locally edited — 294 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 (53 lines × 2 locations) · ×1
  • Duplicated block (53 lines × 2 locations) packages/pdf/src/templates/porygon/PorygonPage.tsx:33 — packages/pdf/src/templates/porygon/PorygonPage.tsx:33 · packages/pdf/src/templates/scizor/ScizorPage.tsx:33 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
R10 · Code Duplication · Duplicated block with local edits (52 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (52 matched lines × 2 locations) apps/mobile/src/features/builder/menu/menu-screen.tsx:95 — apps/mobile/src/features/builder/menu/menu-screen.tsx:95 · apps/mobile/src/features/builder/menu/menu-screen.tsx:306 — the two spans are one implementation copied and then locally edited — 472 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication · Duplicated block with local edits (51 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (51 matched lines × 2 locations) apps/mobile/src/api/ai-consent.ts:55 — apps/mobile/src/api/ai-consent.ts:55 · apps/web/src/libs/orpc/ai-consent.ts:44 — the two spans are one implementation copied and then locally edited — 482 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 (47 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (47 matched lines × 2 locations) packages/ui/src/components/dialog.tsx:76 — packages/ui/src/components/dialog.tsx:76 · packages/ui/src/components/sheet.tsx:88 — the two spans are one implementation copied and then locally edited — 216 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 (45 lines × 2 locations) · ×1
  • Duplicated block (45 lines × 2 locations) packages/pdf/src/templates/chikorita/ChikoritaPage.tsx:34 — packages/pdf/src/templates/chikorita/ChikoritaPage.tsx:34 · packages/pdf/src/templates/ditto/DittoPage.tsx:33 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
R10 · Code Duplication · Duplicated block with local edits (44 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (44 matched lines × 2 locations) apps/web/src/features/auth/pages/login.tsx:220 — apps/web/src/features/auth/pages/login.tsx:220 · apps/web/src/features/auth/pages/register.tsx:236 — the two spans are one implementation copied and then locally edited — 279 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 (41 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (41 matched lines × 2 locations) packages/db/src/schema/cover-letter.ts:43 — packages/db/src/schema/cover-letter.ts:43 · packages/db/src/schema/resume.ts:53 — the two spans are one implementation copied and then locally edited — 366 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 (40 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (40 matched lines × 2 locations) packages/api/src/features/cover-letters/versions.ts:27 — packages/api/src/features/cover-letters/versions.ts:27 · packages/api/src/features/resume/version-history.ts:14 — the two spans are one implementation copied and then locally edited — 335 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 (36 lines × 2 locations) · ×1
  • Duplicated block (36 lines × 2 locations) apps/web/src/features/documents/documents-page.tsx:1043 — apps/web/src/features/documents/documents-page.tsx:1043 · apps/web/src/features/documents/import/import-page.tsx:193 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
R10 · Code Duplication · Duplicated block with local edits (35 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (35 matched lines × 2 locations) apps/mobile/src/features/builder/menu/menu-screen.tsx:46 — apps/mobile/src/features/builder/menu/menu-screen.tsx:46 · apps/mobile/src/features/builder/menu/menu-screen.tsx:281 — the two spans are one implementation copied and then locally edited — 221 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R2 · Cyclomatic Complexity · Complex function fixtureWrite (cyclomatic 219, cognitive 360) · ×1
  • Complex function fixtureWrite (cyclomatic 219, cognitive 360) apps/mobile/src/data/fixture-operations.ts:178 — fixtureWrite has cyclomatic complexity 219 and cognitive complexity 360; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function AddApplicationForm (cyclomatic 145, cognitive 109) · ×1
  • Complex function AddApplicationForm (cyclomatic 145, cognitive 109) apps/web/src/features/applications/components/add-application-dialog.tsx:188 — AddApplicationForm has cyclomatic complexity 145 and cognitive complexity 109; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function ScheduleSheet (cyclomatic 112, cognitive 95) · ×1
  • Complex function ScheduleSheet (cyclomatic 112, cognitive 95) apps/web/src/features/career/schedule-sheet.tsx:138 — ScheduleSheet has cyclomatic complexity 112 and cognitive complexity 95; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function authorizeAiRequest (cyclomatic 102, cognitive 85) · ×1
  • Complex function authorizeAiRequest (cyclomatic 102, cognitive 85) apps/mobile/src/api/ai-consent.ts:16 — authorizeAiRequest has cyclomatic complexity 102 and cognitive complexity 85; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function DocumentsPage (cyclomatic 98, cognitive 78) · ×1
  • Complex function DocumentsPage (cyclomatic 98, cognitive 78) apps/web/src/features/documents/documents-page.tsx:80 — DocumentsPage has cyclomatic complexity 98 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 sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 95, cognitive 92) · ×1
  • Complex function (anonymous) (cyclomatic 95, cognitive 92) apps/web/src/libs/orpc/ai-consent.ts:73 — (anonymous) has cyclomatic complexity 95 and cognitive complexity 92; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function resolveStylesheet (cyclomatic 90, cognitive 216) · ×1
  • Complex function resolveStylesheet (cyclomatic 90, cognitive 216) packages/resume/src/stylesheet/cascade.ts:564 — resolveStylesheet has cyclomatic complexity 90 and cognitive complexity 216; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function importLines (cyclomatic 88, cognitive 66) · ×1
  • Complex function importLines (cyclomatic 88, cognitive 66) packages/import/src/pdf-lines.ts:1349 — importLines has cyclomatic complexity 88 and cognitive complexity 66; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function Session (cyclomatic 79, cognitive 66) · ×1
  • Complex function Session (cyclomatic 79, cognitive 66) apps/web/src/features/career/workspace/practise.tsx:373 — Session has cyclomatic complexity 79 and cognitive complexity 66; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function send (cyclomatic 77, cognitive 84) · ×1
  • Complex function send (cyclomatic 77, cognitive 84) packages/api/src/features/agent/service.ts:1468 — send has cyclomatic complexity 77 and cognitive complexity 84; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function convertNode (cyclomatic 69, cognitive 104) · ×1
  • Complex function convertNode (cyclomatic 69, cognitive 104) packages/pdf/src/forme/to-forme.tsx:477 — convertNode has cyclomatic complexity 69 and cognitive complexity 104; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function RouteComponent (cyclomatic 65, cognitive 48) · ×1
  • Complex function RouteComponent (cyclomatic 65, cognitive 48) apps/web/src/routes/dashboard/applications/index.tsx:121 — RouteComponent has cyclomatic complexity 65 and cognitive complexity 48; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function toFormeStyle (cyclomatic 64, cognitive 127) · ×1
  • Complex function toFormeStyle (cyclomatic 64, cognitive 127) packages/pdf/src/forme/style.ts:377 — toFormeStyle has cyclomatic complexity 64 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 is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 64, cognitive 85) · ×1
  • Complex function (anonymous) (cyclomatic 64, cognitive 85) packages/auth/src/config.ts:874 — (anonymous) has cyclomatic complexity 64 and cognitive complexity 85; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function ToolPartView (cyclomatic 63, cognitive 65) · ×1
  • Complex function ToolPartView (cyclomatic 63, cognitive 65) apps/web/src/features/assistant/conversation.tsx:743 — ToolPartView has cyclomatic complexity 63 and cognitive complexity 65; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function TodayScreen (cyclomatic 63, cognitive 57) · ×1
  • Complex function TodayScreen (cyclomatic 63, cognitive 57) apps/mobile/src/features/today/screen.tsx:64 — TodayScreen has cyclomatic complexity 63 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 sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function generateCareer (cyclomatic 59, cognitive 63) · ×1
  • Complex function generateCareer (cyclomatic 59, cognitive 63) packages/api/src/features/career/generate.ts:113 — generateCareer has cyclomatic complexity 59 and cognitive complexity 63; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function NewDocument (cyclomatic 58, cognitive 54) · ×1
  • Complex function NewDocument (cyclomatic 58, cognitive 54) apps/web/src/features/documents/new-document-dialog.tsx:93 — NewDocument has cyclomatic complexity 58 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 sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function PractiseTab (cyclomatic 56, cognitive 54) · ×1
  • Complex function PractiseTab (cyclomatic 56, cognitive 54) apps/web/src/features/career/workspace/practise.tsx:122 — PractiseTab has cyclomatic complexity 56 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 sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function orderExperienceHeaders (cyclomatic 55, cognitive 70) · ×1
  • Complex function orderExperienceHeaders (cyclomatic 55, cognitive 70) packages/import/src/pdf-lines.ts:1181 — orderExperienceHeaders has cyclomatic complexity 55 and cognitive complexity 70; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 55, cognitive 64) · ×1
  • Complex function (anonymous) (cyclomatic 55, cognitive 64) apps/mobile/src/dev/storyboard/edges.test.ts:221 — (anonymous) has cyclomatic complexity 55 and cognitive complexity 64; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function AssistantPanel (cyclomatic 55, cognitive 43) · ×1
  • Complex function AssistantPanel (cyclomatic 55, cognitive 43) apps/web/src/features/assistant/assistant-panel.tsx:59 — AssistantPanel has cyclomatic complexity 55 and cognitive complexity 43; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function OfferForm (cyclomatic 54, cognitive 48) · ×1
  • Complex function OfferForm (cyclomatic 54, cognitive 48) apps/web/src/features/career/offer-entry.tsx:255 — OfferForm has cyclomatic complexity 54 and cognitive complexity 48; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function test (cyclomatic 54, cognitive 43) · ×1
  • Complex function test (cyclomatic 54, cognitive 43) packages/import/src/pdf-lines.ts:636 — test has cyclomatic complexity 54 and cognitive complexity 43; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function parseReactiveResumeV4JSON (cyclomatic 53, cognitive 56) · ×1
  • Complex function parseReactiveResumeV4JSON (cyclomatic 53, cognitive 56) packages/import/src/reactive-resume-v4-json.tsx:241 — parseReactiveResumeV4JSON has cyclomatic complexity 53 and cognitive complexity 56; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function CoachPage (cyclomatic 51, cognitive 49) · ×1
  • Complex function CoachPage (cyclomatic 51, cognitive 49) apps/web/src/features/career/coach.tsx:115 — CoachPage has cyclomatic complexity 51 and cognitive complexity 49; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function open (cyclomatic 50, cognitive 61) · ×1
  • Complex function open (cyclomatic 50, cognitive 61) apps/mobile/src/data/draft/store.ts:239 — open has cyclomatic complexity 50 and cognitive complexity 61; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function AnswerCard (cyclomatic 50, cognitive 44) · ×1
  • Complex function AnswerCard (cyclomatic 50, cognitive 44) apps/web/src/features/career/workspace/apply.tsx:490 — AnswerCard has cyclomatic complexity 50 and cognitive complexity 44; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function RichTextEditor (cyclomatic 50, cognitive 29) · ×1
  • Complex function RichTextEditor (cyclomatic 50, cognitive 29) apps/web/src/features/resume/editor/write/rich-text-editor-field.tsx:214 — RichTextEditor has cyclomatic complexity 50 and cognitive complexity 29; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function headingTest (cyclomatic 49, cognitive 104) · ×1
  • Complex function headingTest (cyclomatic 49, cognitive 104) packages/import/src/pdf-lines.ts:207 — headingTest has cyclomatic complexity 49 and cognitive complexity 104; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function processBlockElement (cyclomatic 49, cognitive 102) · ×1
  • Complex function processBlockElement (cyclomatic 49, cognitive 102) packages/docx/src/html-to-docx.ts:149 — processBlockElement has cyclomatic complexity 49 and cognitive complexity 102; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function convertNode (cyclomatic 49, cognitive 74) · ×1
  • Complex function convertNode (cyclomatic 49, cognitive 74) packages/pdf/src/html/to-html.ts:290 — convertNode has cyclomatic complexity 49 and cognitive complexity 74; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 49, cognitive 45) · ×1
  • Complex function (anonymous) (cyclomatic 49, cognitive 45) packages/api/src/features/resume/service.ts:838 — (anonymous) has cyclomatic complexity 49 and cognitive complexity 45; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function SentDocuments (cyclomatic 49, cognitive 41) · ×1
  • Complex function SentDocuments (cyclomatic 49, cognitive 41) apps/web/src/features/applications/components/detail/sent-documents.tsx:60 — SentDocuments has cyclomatic complexity 49 and cognitive complexity 41; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function ResumePageCanvas (cyclomatic 49, cognitive 36) · ×1
  • Complex function ResumePageCanvas (cyclomatic 49, cognitive 36) apps/web/src/routes/builder/$resumeId/-components/page-canvas.tsx:71 — ResumePageCanvas has cyclomatic complexity 49 and cognitive complexity 36; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function MessagesTab (cyclomatic 49, cognitive 35) · ×1
  • Complex function MessagesTab (cyclomatic 49, cognitive 35) apps/web/src/features/career/workspace/messages.tsx:81 — MessagesTab has cyclomatic complexity 49 and cognitive complexity 35; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function Workspace (cyclomatic 47, cognitive 42) · ×1
  • Complex function Workspace (cyclomatic 47, cognitive 42) apps/web/src/features/career/workspace/shell.tsx:123 — Workspace has cyclomatic complexity 47 and cognitive complexity 42; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function WebAccessSection (cyclomatic 47, cognitive 42) · ×1
  • Complex function WebAccessSection (cyclomatic 47, cognitive 42) apps/web/src/features/settings/ai/web-access.tsx:56 — WebAccessSection has cyclomatic complexity 47 and cognitive complexity 42; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function AnswerLibrary (cyclomatic 47, cognitive 36) · ×1
  • Complex function AnswerLibrary (cyclomatic 47, cognitive 36) apps/web/src/features/career/workspace/answer-library.tsx:49 — AnswerLibrary has cyclomatic complexity 47 and cognitive complexity 36; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function invokeFake (cyclomatic 46, cognitive 76) · ×1
  • Complex function invokeFake (cyclomatic 46, cognitive 76) apps/mobile/src/data/fixtures.ts:708 — invokeFake has cyclomatic complexity 46 and cognitive complexity 76; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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 · packages/api/src/features/agent/service.ts · ×1
  • packages/api/src/features/agent/service.ts: 2268 lines of code packages/api/src/features/agent/service.ts:1 — packages/api/src/features/agent/service.ts has 2268 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/import/src/pdf-lines.ts · ×1
  • packages/import/src/pdf-lines.ts: 2024 lines of code packages/import/src/pdf-lines.ts:1 — packages/import/src/pdf-lines.ts has 2024 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/api/src/features/career/service.ts · ×1
  • packages/api/src/features/career/service.ts: 1954 lines of code packages/api/src/features/career/service.ts:1 — packages/api/src/features/career/service.ts has 1954 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/pdf/src/templates/shared/sections.tsx · ×1
  • packages/pdf/src/templates/shared/sections.tsx: 1705 lines of code packages/pdf/src/templates/shared/sections.tsx:1 — packages/pdf/src/templates/shared/sections.tsx has 1705 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/api/src/features/applications/service.ts · ×1
  • packages/api/src/features/applications/service.ts: 1549 lines of code packages/api/src/features/applications/service.ts:1 — packages/api/src/features/applications/service.ts 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.
R3 · Large Files · packages/auth/src/config.ts · ×1
  • packages/auth/src/config.ts: 1330 lines of code packages/auth/src/config.ts:1 — packages/auth/src/config.ts has 1330 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/src/features/career/workspace/practise.tsx · ×1
  • apps/web/src/features/career/workspace/practise.tsx: 1321 lines of code apps/web/src/features/career/workspace/practise.tsx:1 — apps/web/src/features/career/workspace/practise.tsx has 1321 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/src/features/career/today.tsx · ×1
  • apps/web/src/features/career/today.tsx: 1303 lines of code apps/web/src/features/career/today.tsx:1 — apps/web/src/features/career/today.tsx has 1303 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/src/features/resume/builder/draft.ts · ×1
  • apps/web/src/features/resume/builder/draft.ts: 1265 lines of code apps/web/src/features/resume/builder/draft.ts:1 — apps/web/src/features/resume/builder/draft.ts has 1265 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/src/features/assistant/conversation.tsx · ×1
  • apps/web/src/features/assistant/conversation.tsx: 1261 lines of code apps/web/src/features/assistant/conversation.tsx:1 — apps/web/src/features/assistant/conversation.tsx has 1261 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/src/features/career/offers.tsx · ×1
  • apps/web/src/features/career/offers.tsx: 1260 lines of code apps/web/src/features/career/offers.tsx:1 — apps/web/src/features/career/offers.tsx has 1260 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/src/routeTree.gen.ts · ×1
  • apps/web/src/routeTree.gen.ts: 1235 lines of code apps/web/src/routeTree.gen.ts:1 — apps/web/src/routeTree.gen.ts has 1235 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/src/routes/builder/letter/-components/write-panel.tsx · ×1
  • apps/web/src/routes/builder/letter/-components/write-panel.tsx: 1225 lines of code apps/web/src/routes/builder/letter/-components/write-panel.tsx:1 — apps/web/src/routes/builder/letter/-components/write-panel.tsx has 1225 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/src/features/applications/components/add-application-dialog.tsx · ×1
  • apps/web/src/features/applications/components/add-application-dialog.tsx: 1149 lines of code apps/web/src/features/applications/components/add-application-dialog.tsx:1 — apps/web/src/features/applications/components/add-application-dialog.tsx has 1149 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/src/routes/builder/kit.tsx · ×1
  • apps/web/src/routes/builder/kit.tsx: 1147 lines of code apps/web/src/routes/builder/kit.tsx:1 — apps/web/src/routes/builder/kit.tsx has 1147 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/src/features/career/workspace/apply.tsx · ×1
  • apps/web/src/features/career/workspace/apply.tsx: 1113 lines of code apps/web/src/features/career/workspace/apply.tsx:1 — apps/web/src/features/career/workspace/apply.tsx has 1113 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/src/features/documents/documents-page.tsx · ×1
  • apps/web/src/features/documents/documents-page.tsx: 1066 lines of code apps/web/src/features/documents/documents-page.tsx:1 — apps/web/src/features/documents/documents-page.tsx has 1066 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/api/src/features/resume/service.ts · ×1
  • packages/api/src/features/resume/service.ts: 1065 lines of code packages/api/src/features/resume/service.ts:1 — packages/api/src/features/resume/service.ts has 1065 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/src/features/career/coach-chat.tsx · ×1
  • apps/web/src/features/career/coach-chat.tsx: 1053 lines of code apps/web/src/features/career/coach-chat.tsx:1 — apps/web/src/features/career/coach-chat.tsx has 1053 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/src/features/career/workspace/messages.tsx · ×1
  • apps/web/src/features/career/workspace/messages.tsx: 1017 lines of code apps/web/src/features/career/workspace/messages.tsx:1 — apps/web/src/features/career/workspace/messages.tsx has 1017 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/pdf/src/forme/to-forme.tsx · ×1
  • packages/pdf/src/forme/to-forme.tsx: 1006 lines of code packages/pdf/src/forme/to-forme.tsx:1 — packages/pdf/src/forme/to-forme.tsx has 1006 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/src/features/career/workspace/prepare.tsx · ×1
  • apps/web/src/features/career/workspace/prepare.tsx: 1004 lines of code apps/web/src/features/career/workspace/prepare.tsx:1 — apps/web/src/features/career/workspace/prepare.tsx has 1004 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · apps/mobile/src/features/applications/ApplicationsScreen.tsx · ×1
  • apps/mobile/src/features/applications/ApplicationsScreen.tsx: 965 lines of code apps/mobile/src/features/applications/ApplicationsScreen.tsx:1 — apps/mobile/src/features/applications/ApplicationsScreen.tsx has 965 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/api/src/features/career/jobs.ts · ×1
  • packages/api/src/features/career/jobs.ts: 962 lines of code packages/api/src/features/career/jobs.ts:1 — packages/api/src/features/career/jobs.ts has 962 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · packages/pdf/src/semantic/tree.ts · ×1
  • packages/pdf/src/semantic/tree.ts: 957 lines of code packages/pdf/src/semantic/tree.ts:1 — packages/pdf/src/semantic/tree.ts has 957 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/src/features/documents/new-document-dialog.tsx · ×1
  • apps/web/src/features/documents/new-document-dialog.tsx: 918 lines of code apps/web/src/features/documents/new-document-dialog.tsx:1 — apps/web/src/features/documents/new-document-dialog.tsx has 918 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · apps/mobile/src/data/fixture-operations.ts · ×1
  • apps/mobile/src/data/fixture-operations.ts: 915 lines of code apps/mobile/src/data/fixture-operations.ts:1 — apps/mobile/src/data/fixture-operations.ts has 915 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/src/features/applications/components/application-detail-sheet.tsx · ×1
  • apps/web/src/features/applications/components/application-detail-sheet.tsx: 913 lines of code apps/web/src/features/applications/components/application-detail-sheet.tsx:1 — apps/web/src/features/applications/components/application-detail-sheet.tsx has 913 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/src/features/resume/editor/check/job-match.tsx · ×1
  • apps/web/src/features/resume/editor/check/job-match.tsx: 870 lines of code apps/web/src/features/resume/editor/check/job-match.tsx:1 — apps/web/src/features/resume/editor/check/job-match.tsx 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/mobile/src/data/fixtures.ts · ×1
  • apps/mobile/src/data/fixtures.ts: 867 lines of code apps/mobile/src/data/fixtures.ts:1 — apps/mobile/src/data/fixtures.ts has 867 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/src/features/resume/share/share-panel.tsx · ×1
  • apps/web/src/features/resume/share/share-panel.tsx: 865 lines of code apps/web/src/features/resume/share/share-panel.tsx:1 — apps/web/src/features/resume/share/share-panel.tsx has 865 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/src/features/documents/import/import-page.tsx · ×1
  • apps/web/src/features/documents/import/import-page.tsx: 863 lines of code apps/web/src/features/documents/import/import-page.tsx:1 — apps/web/src/features/documents/import/import-page.tsx has 863 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/src/features/settings/profile.tsx · ×1
  • apps/web/src/features/settings/profile.tsx: 863 lines of code apps/web/src/features/settings/profile.tsx:1 — apps/web/src/features/settings/profile.tsx has 863 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/resume/src/stylesheet/cascade.ts · ×1
  • packages/resume/src/stylesheet/cascade.ts: 848 lines of code packages/resume/src/stylesheet/cascade.ts:1 — packages/resume/src/stylesheet/cascade.ts has 848 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/src/features/assistant/assistant-panel.tsx · ×1
  • apps/web/src/features/assistant/assistant-panel.tsx: 846 lines of code apps/web/src/features/assistant/assistant-panel.tsx:1 — apps/web/src/features/assistant/assistant-panel.tsx has 846 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/src/routes/builder/$resumeId/-sidebar/right/sections/layout/pages.tsx · ×1
  • apps/web/src/routes/builder/$resumeId/-sidebar/right/sections/layout/pages.tsx: 844 lines of code apps/web/src/routes/builder/$resumeId/-sidebar/right/sections/layout/pages.tsx:1 — apps/web/src/routes/builder/$resumeId/-sidebar/right/sections/layout/pages.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/mobile/src/data/draft/store.ts · ×1
  • apps/mobile/src/data/draft/store.ts: 830 lines of code apps/mobile/src/data/draft/store.ts:1 — apps/mobile/src/data/draft/store.ts has 830 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/src/features/resume/editor/write/picture-settings.tsx · ×1
  • apps/web/src/features/resume/editor/write/picture-settings.tsx: 819 lines of code apps/web/src/features/resume/editor/write/picture-settings.tsx:1 — apps/web/src/features/resume/editor/write/picture-settings.tsx has 819 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/src/features/career/coach.tsx · ×1
  • apps/web/src/features/career/coach.tsx: 818 lines of code apps/web/src/features/career/coach.tsx:1 — apps/web/src/features/career/coach.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 · packages/schema/src/resume/data.ts · ×1
  • packages/schema/src/resume/data.ts: 818 lines of code packages/schema/src/resume/data.ts:1 — packages/schema/src/resume/data.ts 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.
R6 · Tooling · The declared test suite includes a file that cannot be loaded · ×1
  • The declared test suite includes a file that cannot be loaded apps/server/src/static/agent-skills.test.ts:9 — This repository declares test tooling, and the ✓ above records that declaration — but apps/server/src/static/agent-skills.test.ts and 19 other test file(s) in this workspace cannot be loaded at all: it imports a module that names no file in this repository, so the runner throws while collecting it and none of its cases execute. The wiring is present and the suite it points at does not run as written, which is why the tooling tick must not be read as a statement that the tests pass. Fix the unloadable file(s) — each one is reported with its failing import under Test Coverage — then the declared script exercises what it claims to.
R7 · Dead Code · Dead file (~991 LoC) · ×1
  • Dead file (~991 LoC) apps/mobile/src/features/applications/ApplicationsScreen.tsx — no import path from any entry point (380 application, 52 tooling, 631 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/mobile/app/(app)/(tabs)/applications/index.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~577 LoC) · ×1
  • Dead file (~577 LoC) apps/mobile/src/features/today/screen.tsx — no import path from any entry point (380 application, 52 tooling, 631 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/mobile/app/(app)/(tabs)/index.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~563 LoC) · ×1
  • Dead file (~563 LoC) apps/mobile/app/(dev)/motion-lab/[lab].tsx — no import path from any entry point (380 application, 52 tooling, 631 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~533 LoC) · ×1
  • Dead file (~533 LoC) apps/mobile/src/features/builder/check/CheckScreen.tsx — no import path from any entry point (380 application, 52 tooling, 631 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/mobile/app/(app)/builder/[id]/(dock)/check.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~452 LoC) · ×1
  • Dead file (~452 LoC) apps/mobile/src/features/builder/entry/EntryScreen.tsx — no import path from any entry point (380 application, 52 tooling, 631 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (apps/mobile/app/(app)/builder/[id]/section/[section]/[item]/index.tsx, apps/mobile/app/(app)/builder/[id]/section/[section]/new.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~435 LoC) · ×1
  • Dead file (~435 LoC) apps/mobile/src/features/applications/DetailScreen.tsx — no import path from any entry point (380 application, 52 tooling, 631 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/mobile/app/(app)/applications/[id]/index.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~430 LoC) · ×1
  • Dead file (~430 LoC) apps/mobile/src/features/builder/menu/menu-screen.tsx — no import path from any entry point (380 application, 52 tooling, 631 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/mobile/app/(app)/builder/[id]/menu.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~422 LoC) · ×1
  • Dead file (~422 LoC) apps/mobile/src/features/settings/timezones.ts — no import path from any entry point (380 application, 52 tooling, 631 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/mobile/src/features/settings/TimezoneScreen.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~407 LoC) · ×1
  • Dead file (~407 LoC) apps/mobile/app/(dev)/kit.tsx — no import path from any entry point (380 application, 52 tooling, 631 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~383 LoC) · ×1
  • Dead file (~383 LoC) apps/mobile/src/features/career/preferences.tsx — no import path from any entry point (380 application, 52 tooling, 631 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (apps/mobile/app/(app)/career/knowledge/preferences.tsx, apps/mobile/app/(app)/career/knowledge/priorities.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~372 LoC) · ×1
  • Dead file (~372 LoC) apps/mobile/src/features/documents/actions.tsx — no import path from any entry point (380 application, 52 tooling, 631 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/mobile/app/(app)/documents/[id]/actions.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~354 LoC) · ×1
  • Dead file (~354 LoC) apps/mobile/src/features/builder/check/issues.ts — no import path from any entry point (380 application, 52 tooling, 631 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/mobile/src/features/builder/check/CheckScreen.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~344 LoC) · ×1
  • Dead file (~344 LoC) apps/mobile/src/features/builder/assistant/proposals-screen.tsx — no import path from any entry point (380 application, 52 tooling, 631 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/mobile/app/(app)/builder/[id]/assistant/proposals.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~328 LoC) · ×1
  • Dead file (~328 LoC) apps/mobile/src/features/career/stories.tsx — no import path from any entry point (380 application, 52 tooling, 631 test roots considered), but 3 in-repo import(s) from 3 other file(s) do name it (apps/mobile/app/(app)/career/knowledge/stories/[id].tsx, apps/mobile/app/(app)/career/knowledge/stories/index.tsx, apps/mobile/app/(app)/career/knowledge/stories/new.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~327 LoC) · ×1
  • Dead file (~327 LoC) apps/mobile/src/features/career/schedules.tsx — no import path from any entry point (380 application, 52 tooling, 631 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (apps/mobile/app/(app)/career/schedules/[id].tsx, apps/mobile/app/(app)/career/schedules/index.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~306 LoC) · ×1
  • Dead file (~306 LoC) apps/mobile/src/features/settings/ProviderScreen.tsx — no import path from any entry point (380 application, 52 tooling, 631 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/mobile/app/(app)/settings/ai/providers/[id].tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~299 LoC) · ×1
  • Dead file (~299 LoC) apps/mobile/src/features/builder/assistant/assistant-screen.tsx — no import path from any entry point (380 application, 52 tooling, 631 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/mobile/app/(app)/builder/[id]/assistant/index.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~293 LoC) · ×1
  • Dead file (~293 LoC) apps/mobile/src/features/builder/share/activity-screen.tsx — no import path from any entry point (380 application, 52 tooling, 631 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/mobile/app/(app)/builder/[id]/share/activity.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~291 LoC) · ×1
  • Dead file (~291 LoC) apps/mobile/src/features/applications/StageSheet.tsx — no import path from any entry point (380 application, 52 tooling, 631 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/mobile/app/(app)/applications/[id]/stage.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~289 LoC) · ×1
  • Dead file (~289 LoC) apps/mobile/src/features/applications/SaveJobScreen.tsx — no import path from any entry point (380 application, 52 tooling, 631 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/mobile/app/(app)/applications/new.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~286 LoC) · ×1
  • Dead file (~286 LoC) apps/mobile/src/features/builder/basics/BasicsScreen.tsx — no import path from any entry point (380 application, 52 tooling, 631 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/mobile/app/(app)/builder/[id]/basics.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~284 LoC) · ×1
  • Dead file (~284 LoC) apps/mobile/src/features/auth/SignInScreen.tsx — no import path from any entry point (380 application, 52 tooling, 631 test roots considered), but 3 in-repo import(s) from 3 other file(s) do name it (apps/mobile/app/(auth)/forgot-password.tsx, apps/mobile/app/(auth)/register.tsx, apps/mobile/app/(auth)/sign-in.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~279 LoC) · ×1
  • Dead file (~279 LoC) apps/mobile/src/features/career/facts.tsx — no import path from any entry point (380 application, 52 tooling, 631 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/mobile/app/(app)/career/knowledge/facts.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~267 LoC) · ×1
  • Dead file (~267 LoC) apps/mobile/src/features/letters/letter-screen.tsx — no import path from any entry point (380 application, 52 tooling, 631 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/mobile/app/(app)/letter/[id]/(dock)/index.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~255 LoC) · ×1
  • Dead file (~255 LoC) apps/mobile/src/features/builder/share/share-screen.tsx — no import path from any entry point (380 application, 52 tooling, 631 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/mobile/app/(app)/builder/[id]/(dock)/share.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~249 LoC) · ×1
  • Dead file (~249 LoC) apps/mobile/src/features/workspace/PracticeScreen.tsx — no import path from any entry point (380 application, 52 tooling, 631 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/mobile/app/(app)/applications/[id]/practise.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~248 LoC) · ×1
  • Dead file (~248 LoC) apps/mobile/src/features/workspace/DebriefScreen.tsx — no import path from any entry point (380 application, 52 tooling, 631 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (apps/mobile/app/(app)/applications/[id]/debrief.tsx, apps/mobile/app/(app)/applications/[id]/library.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~237 LoC) · ×1
  • Dead file (~237 LoC) apps/mobile/src/features/workspace/MessagesScreen.tsx — no import path from any entry point (380 application, 52 tooling, 631 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/mobile/app/(app)/applications/[id]/messages.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~233 LoC) · ×1
  • Dead file (~233 LoC) apps/mobile/src/features/builder/preview/preview-screen.tsx — no import path from any entry point (380 application, 52 tooling, 631 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (apps/mobile/app/(app)/builder/[id]/preview.tsx, apps/mobile/app/(app)/builder/[id]/versions/[version].tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~229 LoC) · ×1
  • Dead file (~229 LoC) apps/mobile/src/features/builder/design/TemplateScreen.tsx — no import path from any entry point (380 application, 52 tooling, 631 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/mobile/app/(app)/builder/[id]/design/template.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~222 LoC) · ×1
  • Dead file (~222 LoC) apps/mobile/src/features/builder/share/web-page-screen.tsx — no import path from any entry point (380 application, 52 tooling, 631 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/mobile/app/(app)/builder/[id]/share/web-page.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~218 LoC) · ×1
  • Dead file (~218 LoC) apps/mobile/src/features/builder/overview/OverviewScreen.tsx — no import path from any entry point (380 application, 52 tooling, 631 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/mobile/app/(app)/builder/[id]/(dock)/index.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~216 LoC) · ×1
  • Dead file (~216 LoC) apps/mobile/src/features/builder/versions/versions-screen.tsx — no import path from any entry point (380 application, 52 tooling, 631 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/mobile/app/(app)/builder/[id]/versions/index.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~206 LoC) · ×1
  • Dead file (~206 LoC) apps/mobile/src/features/builder/download/download-screen.tsx — no import path from any entry point (380 application, 52 tooling, 631 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (apps/mobile/app/(app)/builder/[id]/download.tsx, apps/mobile/app/(app)/letter/[id]/(dock)/export.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~204 LoC) · ×1
  • Dead file (~204 LoC) apps/mobile/src/features/workspace/FitScreen.tsx — no import path from any entry point (380 application, 52 tooling, 631 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/mobile/app/(app)/applications/[id]/fit.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R8 · Dependency Hygiene · Unused dependency 'lefthook' · ×1
  • Unused dependency 'lefthook' — Declared in the root package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
R8 · Dependency Hygiene · Unused dependency '@react-email/ui' · ×1
  • Unused dependency '@react-email/ui' — Declared in packages/email/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Minor — 113 finding(s)
X10 · Duplicated predicate · Duplicated predicate · ×40
  • Duplicated predicate apps/mobile/src/data/builder.ts:63 — `!!applicationId && application.isPending` appears character-identically in 2 files — apps/mobile/src/data/builder.ts, apps/mobile/src/features/builder/check/job-match.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/mobile/src/data/clock.ts:33 — `!/^\d{4}-\d{2}-\d{2}$/.test(date) || !/^\d{2}:\d{2}$/.test(time)` appears character-identically in 2 files — apps/mobile/src/data/clock.ts, packages/utils/src/timezone.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/mobile/src/features/builder/basics/BasicsScreen.tsx:55 — `!["http:", "https:"].includes(parsed.protocol) || !parsed.hostname.includes(".")` appears character-identically in 2 files — apps/mobile/src/features/builder/basics/BasicsScreen.tsx, apps/web/src/features/resume/editor/write/fields.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/src/features/auth/components/session-recovery.tsx:48 — `!accountId || accountId !== getAccountId()` appears character-identically in 2 files — apps/web/src/features/auth/components/session-recovery.tsx, apps/web/src/libs/auth/session-recovery.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/api/src/features/career/jobs.ts:855 — `!application || application.status === "closed"` appears character-identically in 2 files — packages/api/src/features/career/jobs.ts, packages/api/src/features/career/service.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate apps/web/src/features/career/workspace/debrief.tsx:157 — `!connection.isUnavailable && !connection.provider` appears character-identically in 2 files — apps/web/src/features/career/workspace/debrief.tsx, apps/web/src/features/career/workspace/practise.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/src/features/resume/editor/write/model.ts:179 — `!entry.hidden && !isDraftEntry(section.type, entry)` appears character-identically in 2 files — apps/web/src/features/resume/editor/write/model.ts, apps/web/src/features/resume/editor/write/section-view.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/src/features/resume/editor/write/entry-row.tsx:101 — `!event.altKey || (event.key !== "ArrowUp" && event.key !== "ArrowDown")` appears character-identically in 3 files — apps/web/src/features/resume/editor/write/entry-row.tsx, apps/web/src/features/resume/editor/write/outline.tsx, apps/web/src/routes/builder/$resumeId/-sidebar/right/sections/layout/pages.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/src/features/resume/editor/page-overlay.tsx:43 — `!pageMap || !page || page.width <= 0 || page.height <= 0` appears character-identically in 2 files — apps/web/src/features/resume/editor/page-overlay.tsx, apps/web/src/routes/builder/letter/-components/letter-page.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/src/features/career/career-page.tsx:143 — `!provider || (chips.memory && (knowledge.isPending || knowledge.isError))` appears character-identically in 2 files — apps/web/src/features/career/career-page.tsx, apps/web/src/features/career/coach.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/src/features/career/schedules.tsx:88 — `!row.intervalDays && Boolean(row.lastQueuedAt)` appears character-identically in 2 files — apps/web/src/features/career/schedules.tsx, apps/web/src/features/career/today.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/mobile/src/data/actions.ts:20 — `!scope || (backend.kind !== "fake" && getAccountScope() !== scope)` appears character-identically in 2 files — apps/mobile/src/data/actions.ts, apps/mobile/src/data/provider.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/mobile/src/features/builder/assistant/assistant-screen.tsx:123 — `!threadId || pending === undefined || dispatched.current === pending` appears character-identically in 2 files — apps/mobile/src/features/builder/assistant/assistant-screen.tsx, apps/mobile/src/features/career/coach.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/pdf/src/forme/to-forme.tsx:338 — `(node.type === HOST.text || node.type === HOST.link) && node.children.every(isEmptyText)` appears character-identically in 2 files — packages/pdf/src/forme/to-forme.tsx, packages/pdf/src/html/to-html.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/mobile/src/api/ai-consent.ts:59 — `(operation === "applications.ai.searchPostings" && !nativeSearchRequested) || (scheduled && fields.kind === "discovery")` appears character-identically in 2 files — apps/mobile/src/api/ai-consent.ts, apps/web/src/libs/orpc/ai-consent.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/src/features/career/coach.tsx:454 — `(providers.isLoading && !threadId) || threads.isPending` appears character-identically in 2 files — apps/web/src/features/career/coach.tsx, apps/web/src/features/career/workspace/coach-sheet.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/mobile/src/data/fixtures.ts:563 — `Boolean(row.trashedAt) === Boolean(fields.trashed) && (!fields.type || fields.type === "all" || row.type === fields.type) && (!fields.q || S…` appears character-identically in 2 files — apps/mobile/src/data/fixtures.ts, apps/mobile/src/data/guest.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/src/features/career/schedules.tsx:81 — `KIND_ORDER.indexOf(a.kind) - KIND_ORDER.indexOf(b.kind) || new Date(b.createdAt).getTime() - new Date(a.createdAt).getTime() || a.id.localeC…` appears character-identically in 2 files — apps/web/src/features/career/schedules.tsx, apps/web/src/features/career/today.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/mobile/src/features/builder/entry/EntryScreen.tsx:86 — `STORYBOARD && s.request !== null && s.ready !== s.request.nonce` appears character-identically in 3 files — apps/mobile/src/features/builder/entry/EntryScreen.tsx, apps/mobile/src/features/builder/share/activity-screen.tsx, apps/mobile/src/features/letters/letter-screen.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/mobile/src/data/offer-compare.ts:8 — `a.currency === b.currency && a.period === b.period` appears character-identically in 2 files — apps/mobile/src/data/offer-compare.ts, apps/web/src/features/career/offer-compare.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/src/features/applications/components/list-view.tsx:224 — `breakpoint === "desktop" || breakpoint === "wide"` appears character-identically in 2 files — apps/web/src/features/applications/components/list-view.tsx, apps/web/src/routes/builder/$resumeId/-components/page-canvas.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/server/src/cloudflare/r2.ts:54 — `candidate === key || candidate.startsWith(prefix)` appears character-identically in 2 files — apps/server/src/cloudflare/r2.ts, packages/api/src/features/storage/blob.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/mobile/src/api/ai-consent.ts:92 — `chat && typeof fields.threadId === "string"` appears character-identically in 2 files — apps/mobile/src/api/ai-consent.ts, apps/web/src/libs/orpc/ai-consent.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/mobile/src/data/queue.ts:60 — `code === "UNAUTHORIZED" || code === "SESSION_EXPIRED"` appears character-identically in 2 files — apps/mobile/src/data/queue.ts, apps/mobile/src/features/settings/sign-out.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/api/src/features/web-access/builtin.ts:160 — `code > 0 && code <= 0x10ffff && !(code >= 0xd800 && code <= 0xdfff)` appears character-identically in 2 files — packages/api/src/features/web-access/builtin.ts, packages/import/src/docx-text.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.
  • + 15 more in this group — see findings.md.
D10 · Test Quality · Mock-dominated test · ×15
  • Mock-dominated test: probes search in the user's first region packages/api/src/features/web-access/router.test.ts:34 — 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: prepares a copy at %s while preserving its base and submitted documents packages/api/src/features/documents/service.test.ts:117 — This test sets up 4 test doubles (for example `a double assigned in a shared setup`) against 0 real object(s) of its own, and its only verification is 5 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: saves the sent version and score when the %s is linked at Applied packages/api/src/features/applications/service.test.ts:245 — This test sets up 5 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: saves it once, and not before the application is sent packages/api/src/features/applications/service.test.ts:303 — 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: does not delete the replaced upload when another application still references it packages/api/src/features/applications/service.test.ts:488 — This test sets up 3 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.
  • Mock-dominated test: signals a remote run without releasing its database claim packages/api/src/features/agent/service.test.ts:1797 — 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 3 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: proceeds with cleanup when the thread is owned by the user packages/api/src/features/agent/service.test.ts:1821 — This test sets up 10 test doubles (for example `vi.fn`) against 0 real object(s) of its own, and its only verification is 8 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: keeps the selected URL and cookie aligned after normalizing a test locale apps/web/src/libs/locale-choices.test.ts:13 — This test sets up 3 test doubles (for example `vi.fn`) against 0 real object(s) of its own, and its only verification is 3 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: does not save a browser hint over a missing account language apps/web/src/libs/root-context.test.ts:87 — This test sets up 3 test doubles (for example `a double assigned in a shared setup`) 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: $name apps/web/src/features/resume/builder/draft.test.ts:1486 — This test sets up 5 test doubles (for example `vi.fn`) against 0 real object(s) of its own, and its only verification is 3 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: stops question playback and releases its audio when leaving Practise apps/web/src/features/career/workspace/workspace.test.tsx:631 — This test sets up 7 test doubles (for example `vi.fn`) against 0 real object(s) of its own, and its only verification is 4 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: never dispatches a no-AI parse to a server that cannot confirm support, while explicit AI still works apps/web/src/features/applications/components/application-workflows.test.tsx:389 — This test sets up 3 test doubles (for example `vi.fn`) 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: two-file export picks one folder and writes both files apps/mobile/src/features/builder/download/export-file.test.ts:13 — This test sets up 4 test doubles (for example `jest.fn`) against 0 real object(s) of its own, and its only verification is 3 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: shares authenticated bytes and removes the private cached PDF afterward apps/mobile/src/features/applications/posting-file.test.ts:62 — This test sets up 4 test doubles (for example `a double assigned in a shared setup`) against 1 real object(s) of its own, and its only verification is 4 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: shows translated operation failures and preserves validation messages (classified: %s) apps/mobile/src/features/applications/posting-sheet.test.tsx:32 — This test sets up 3 test doubles (for example `jest.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.
X7 · Silent fallback defaults · Silent fallback default in catch · ×13
  • Silent fallback default in catch apps/mobile/src/features/settings/profile-fields.ts:16 — `countryName` 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 apps/server/src/http/app.ts:61 — `getTrustedClient` swallows every exception into `return "unknown"` — 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/src/features/auth/components/guest-banner.tsx:18 — `readTransfer` 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 apps/web/src/features/career/workspace/debrief.tsx:421 — `ReviewCard` 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 apps/web/src/features/career/workspace/practise.tsx:1124 — `useVoiceSettings` 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 apps/web/src/features/career/coach.tsx:99 — `readOfferIds` 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 apps/web/src/features/career/offers.tsx:56 — `readPair` 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 apps/web/src/features/feedback/review-page.tsx:38 — `readName` 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/api/src/features/ai/service.ts:392 — `pdfLinks` 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/api/src/features/web-access/transport.ts:67 — `normalizeSearch` 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/api/src/features/applications/ai.ts:50 — `canonicalLanguage` 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/import/src/job-posting.ts:30 — `pageLanguage` 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/import/src/job-posting.ts:108 — `declaredLanguage` 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.
D24 · Comment Value · redundant comment · ×6
  • redundant comment apps/mobile/src/features/letters/letter-screen.tsx:46 — "The Resume and Application pickers." repeats the code it sits on: 3 of its 3 words (resume, application, pickers) are already in `const [picker, setPicker] = useState<"resume" | "application" | null>(null);`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment packages/api/src/features/applications/service.ts:212 — "Stages at which an application has been sent." repeats the code it sits on: 3 of its 3 words (stages, application, sent) are already in `const SENT_STAGES = new Set<ApplicationStatus>(["applied", "screening", "interview", "offer"]);`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment packages/api/src/features/resume/service.test.ts:130 — "A `db.select(...).from(...).where(...)` chain that resolves to `rows`." repeats the code it sits on: 4 of its 5 words (select, chain, resolves, rows) are already in `const createSelectChain = (rows: unknown[]) => ({`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment packages/api/src/features/resume/version-history.test.ts:12 — "`select().from().where().orderBy().limit()` resolving to `rows`." repeats the code it sits on: 4 of its 5 words (select, order, limit, rows) are already in `const selectChain = (rows: unknown[]) => ({`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment packages/import/src/json-resume.tsx:179 — "Map work to experience" repeats the code it sits on: 3 of its 3 words (map, work, experience) are already in `result.sections.experience.items = (jsonResume.work ?? [])`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment packages/import/src/json-resume.tsx:331 — "Map profiles (from basics.profiles) to profiles section" repeats the code it sits on: 4 of its 4 words (map, profiles, basics, section) are already in `result.sections.profiles.items = (basics.profiles ?? [])`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
D31 · IaC & Container Security · Low IaC · ×4
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
IC1 · Incompleteness & stubs · Disabled test · ×4
  • Disabled test tests/e2e/specs/assistant.spec.ts:9 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test tests/e2e/specs/font-mirror.spec.ts:10 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test tests/e2e/specs/guest.spec.ts:5 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test tests/e2e/specs/posting-capture-extension.spec.ts:10 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
X7 · Silent fallback defaults · Pending state with no failure state · ×4
  • Pending state with no failure state apps/web/src/features/settings/account/data.tsx:171 — The view draws `Exporting…` under `exporting`, but `exporting` is settled by a load that can fail and the component draws no failure state, so a failed load is shown as "not yet" for ever, or as the loaded state over its initial value. Give the component a failure state and draw it.
  • Pending state with no failure state apps/web/src/features/resume/share/web-page-preview.tsx:193 — The view draws `<div class="grid size-full place-items-center">` under `document`, but `document` is settled by a load that can fail and the component draws no failure state, so a failed load is shown as "not yet" for ever, or as the loaded state over its initial value. Give the component a failure state and draw it.
  • Pending state with no failure state apps/web/src/features/applications/components/detail/sent-documents.tsx:135 — The view draws `Generating PDF…` under `downloading === documentId`, but `downloading` is settled by a load that can fail and the component draws no failure state, so a failed load is shown as "not yet" for ever, or as the loaded state over its initial value. Give the component a failure state and draw it.
  • Pending state with no failure state apps/mobile/src/features/builder/design/LayoutScreen.tsx:286 — The view draws `<View style= >` under `fitting`, but `fitting` is settled by a load that can fail and the component draws no failure state, so a failed load is shown as "not yet" for ever, or as the loaded state over its initial value. Give the component a failure state and draw it.
D20 · ADR Quality · ADR lacks an enforcement field · ×3
  • ADR lacks an enforcement field .agents/docs/decisions/0001-server-rendered-web-pages.md:1 — Add an `enforcement:` frontmatter field or a plain `Enforcement:` header line (prose/test/analyzer/not-applicable) to make the rung explicit — the other ADRs in this repo already declare one.
  • ADR lacks an enforcement field .agents/docs/decisions/0003-both-domains-serve-public-pages.md:1 — Add an `enforcement:` frontmatter field or a plain `Enforcement:` header line (prose/test/analyzer/not-applicable) to make the rung explicit — the other ADRs in this repo already declare one.
  • ADR lacks an enforcement field .agents/docs/decisions/0005-background-application-execution.md:1 — Add an `enforcement:` frontmatter field or a plain `Enforcement:` header line (prose/test/analyzer/not-applicable) to make the rung explicit — the other ADRs in this repo already declare one.
P2 · Observability · Console output used as the logging channel · ×3
  • Console output used as the logging channel packages/auth/src/config.ts:677 — `packages/auth/src/config.ts` reports through `console.*` at line 677 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 packages/auth/src/config.ts:699 — `packages/auth/src/config.ts` reports through `console.*` at line 699 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 packages/auth/src/rate-limit.ts:63 — `packages/auth/src/rate-limit.ts` reports through `console.*` at line 63 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
D20 · ADR Quality · ADR declares no status · ×2
  • ADR declares no status .agents/docs/decisions/0004-multi-client-workspaces.md:1 — `.agents/docs/decisions/0004-multi-client-workspaces.md` declares no status, while 2 of the 3 other records in `.agents/docs/decisions` do, so a reader cannot tell whether this decision is in force. Add a `Status:` line.
  • ADR declares no status .agents/docs/decisions/0005-background-application-execution.md:1 — `.agents/docs/decisions/0005-background-application-execution.md` declares no status, while 2 of the 3 other records in `.agents/docs/decisions` do, so a reader cannot tell whether this decision is in force. Add a `Status:` line.
IC1 · Incompleteness & stubs · Empty method body · ×2
  • Empty method body apps/mobile/src/dev/storyboard/capture.tsx:36 — `seed` has an empty body — confirm it's an intentional no-op and not an unfinished method.
  • Empty method body apps/mobile/src/dev/storyboard/capture.tsx:36 — `setNow` has an empty body — confirm it's an intentional no-op and not an unfinished method.
IC1 · Incompleteness & stubs · Blanket warning suppression · ×2
  • Blanket warning suppression apps/web/src/routeTree.gen.ts:1 — A bare `eslint-disable` or `@ts-nocheck` with no rule list switches every lint rule or the whole type checker off for the rest of the file — hidden debt. Disable the specific rule on the specific line, with a justification, instead.
  • Blanket warning suppression apps/web/src/routeTree.gen.ts:3 — A bare `eslint-disable` or `@ts-nocheck` with no rule list switches every lint rule or the whole type checker off for the rest of the file — hidden debt. Disable the specific rule on the specific line, with a justification, instead.
C2 · Access Controls · No named authorization policies · ×1
  • No named authorization policies apps/server/src/http/career-jobs.ts:12 — Authorization IS enforced here (by route guards, auth middleware or checks that refuse a caller) — this is NOT a claim that endpoints are unprotected. What's missing is a NAMED rule set: who may do what is encoded inline where it is checked, so the rules can't be listed, reviewed or tested apart from the code that applies them. Recommendation, not a defect.
C5 · Data-Subject Rights · Partial data-subject-rights support · ×1
  • Partial data-subject-rights support — Corroborated rights: erasure ✓ · export ✗ · consent ✗. Each tick means this scan found code in the repository implementing that right — a deletion/anonymisation path for erasure, a data-export or portability path for export, and consent state recorded alongside the personal data it authorises. A ✗ therefore means no such code was recognised HERE, not that the right is unsupported: a capability provided by a platform, a manual runbook, or code spelled in a way this scan does not match is not visible to it. Confirm before treating a cross as a gap; where it is one, the right has to be fulfilled manually.
D20 · ADR Quality · ADR has no Context and Decision section · ×1
  • ADR has no Context and Decision section .agents/docs/decisions/0003-both-domains-serve-public-pages.md:1 — .agents/docs/decisions/0003-both-domains-serve-public-pages.md has no Context and Decision section (a heading such as `## Context`, or the MADR equivalent). A decision record states the context that forced it, the decision and its consequences, so a reader can tell later whether it still holds.
D26 · Project Cohesion · Projects may be oversized for their cohesion · ×1
  • Projects may be oversized for their cohesion — 4 of 25 project(s) overshoot their size bounds, lowering Project Cohesion to 6.8/10. The most over is `apps/web` (97628 LoC, 502 module-visible types across 80 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
  • REDACTED
D30 · Dependency Vulnerabilities · Low CVE · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
P2 · Observability · Logging is not universal · ×1
  • Logging is not universal — Only 2/3 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `tooling`.
P3 · Security & performance tooling · No SAST · ×1
  • No SAST REDACTED:4 — 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 6 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
P3 · Security & performance tooling · No dependency-update automation · ×1
  • No dependency-update automation package.json:65 — `package.json` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`.
R8 · Dependency Hygiene · Test-only dependency 'fflate' in production deps · ×1
  • Test-only dependency 'fflate' in production deps packages/api/package.json:72 — Only test files import it (first: packages/api/src/features/ai/service.docx.test.ts:4) — move it to devDependencies.
S1 · Web-Security Posture · No app-layer HTTPS enforcement detected · ×1
  • No app-layer HTTPS enforcement detected apps/server/src/index.ts:29 — `serve(…)` 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 27/30 async functions that make a cancellable request (fetch, axios, ky, ofetch, got, undici, node:http) accept an AbortSignal or pass one on, so a request keeps running after whatever wanted it has given up — a page navigated away from, an unmounted component, a timed-out job. Take a `signal` (or an options object that carries one) and hand it to the request; where nothing could ever cancel the call, omitting it is a deliberate choice — judge against how the function is used.
X5 · Nullable reference types · Strict null checking is not enabled everywhere the repository type-checks · ×1
  • Strict null checking is not enabled everywhere the repository type-checks — 2/8 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.
Minor — 5 finding(s)
D10 · Test Quality · Skipped (documented) · ×3
  • Skipped (documented): (unnamed test) tests/e2e/fixtures/ai-stub-career.ts:50 — Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
  • Skipped (documented): (unnamed test) packages/api/src/features/auth/account-storage.test.ts:20 — Skipped with a documented reason — a deferral, not lazy debt: switched off by it.skipIf
  • Skipped (documented): (unnamed test) packages/api/src/features/auth/backup.integration.test.ts:34 — Skipped with a documented reason — a deferral, not lazy debt: switched off by it.skipIf
D24 · Comment Value · doc comments repeat the names · ×2
  • doc comments repeat the names packages/resume/src/ats-pdf/types.ts:197 — 0 of 2 documented parameters and 1 of 368 summaries in `@reactive-resume/resume` only repeat the member or parameter name (e.g. "Index into ." for `lineIndex`). Delete the restating tags, or add what the name does not say.
  • doc comments repeat the names apps/web/src/features/career/workspace/practise.tsx:1256 — 0 of 0 documented parameters and 2 of 1740 summaries in `web` only repeat the member or parameter name (e.g. "Whether the browser can do this itself." for `browser`). Delete the restating tags, or add what the name does not say.

Appendix B — Reproduction & audit trail

Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.

DimensionToolVersionCommandFindingsRaw output
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-a56382fef05d45db8e7be80a3b7ec1fb/history.json --exit-code 0 --source .3artifacts/raw/gitleaks-history.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-a56382fef05d45db8e7be80a3b7ec1fb/tree.json --exit-code 0 --source .0artifacts/raw/gitleaks-tree.json
D29 · Static Analysis (SAST)semgrep—semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt .79artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilitiestrivy—trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** .7artifacts/raw/trivy-fs.json
D31 · IaC & Container Securitytrivy—trivy config --format json --quiet .11artifacts/raw/trivy-config.json
D32 · Data Compliance (PII/GDPR)semgrep—semgrep --config /opt/semgrep-rules/gdpr.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt .1artifacts/raw/semgrep-gdpr.json
D40 · Network Egress Confinementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.0—
D41 · Kernel & Syscall Confinementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.0—
D42 · Runtime Threat Enforcementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.0—
D43 · Malicious Dependenciestrivy—trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** .0artifacts/raw/trivy-fs.json

Run 01a1d9e5-235b-7748-86fd-14cf705c82a6 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.

Downloadable artifacts

Machine-readable and reproducible from this commit + frozen rubric — drop them straight into a contract appendix, a CRA dossier, or a downstream SCA / VEX tool.

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