🧱 Technology Stack & Codebase Complexity

📋 Summary

Midshift is built on a modern, mainstream and deliberately narrow stack: a Next.js 16 / React 19 web application written entirely in TypeScript, hosted on Vercel, with Supabase (managed Postgres, file storage and authentication) as its only data platform and Resend as its only e-mail provider. That narrowness is a strength: a new team needs familiarity with one framework and one backend platform, and hiring for these skills is straightforward. The codebase is medium-sized (about 44,000 lines of application TypeScript, roughly 92,000 lines across everything including tests and tooling) and most functions are simple; complexity is concentrated in a small number of large request handlers and in the in-repository test harness. The main currency concern is that the core framework is pinned to an exact version (Next.js 16.2.0) that carries published critical security advisories, and two declared dependencies are not used at all. Composite complexity: 5 / 10 (moderate).

🎯 Rating

🟡 ●●●○○ 3 / 5 — Amber. The stack is current, coherent and easy to staff, but the framework is pinned to a vulnerable release with no upgrade mechanism in place, which a buyer must budget to address immediately.

🔍 Findings

1. Languages, frameworks and major libraries

2. Runtime, build, infrastructure and hosting

3. Data stores, queues, caches and third-party services

4. Measured size (cloc 2.06)

Whole repository (excluding node_modules, .next):

src/ only: 465 TypeScript files, 44,380 code lines, 9,934 comment lines (plus CSS). Of src/, the QA harness (src/app/qa) is 38 files / 4,482 code lines and test files are 70. [Observed]

Comment density is unusually high (≈22% of TypeScript lines in src are comments), most of it narrative "why" commentary. cloc timed out on four very large spec/script files on the first pass; their lines are therefore slightly under-counted in the whole-repo total. [Observed]

5. Measured complexity (lizard, TypeScript, src/)

2,621 functions; mean cyclomatic complexity (CCN) 2.82.

Top 10 most complex functions:

Files by summed CCN: src/app/qa/store.ts 1,074; src/app/qa/api/[...path]/route.ts 298; src/lib/schedule-sheet.ts 182; src/lib/for-you.ts 141; src/app/api/campaigns/[id]/plan/route.ts 107. Largest files by lines: src/app/qa/store.ts 3,349; review-view.tsx 1,373; ad-unit-panel.tsx 1,218; src/types/database.ts 1,150; admin-view.tsx 970; copy-deck-parser.ts 828. [Observed]

6. Hotspots

The standard hotspot method (complexity × change frequency) cannot be applied: the repository contains a single squashed commit (3789df6, "Midshift source for audit", 2026-10-06), so there is no churn data. [Unavailable — requires the original, unsquashed git history.]

As a proxy (complexity × size only, not churn), the candidates a new team would touch most cautiously are: the ad-unit PATCH route, the brief PATCH route, the review-file PATCH route, src/lib/for-you.ts, src/lib/copy-deck-parser.ts (self-described as "the most subtle code in the repo") and src/app/qa/store.ts, which must mirror every API route (see coupling below). [Inferred]

7. Coupling indicators

There is no repository/data-access layer between route handlers and Supabase; routes and server components query Supabase directly. [Observed]

8. Composite Complexity Score: 5 / 10

🧾 Evidence

• cloc --exclude-dir=node_modules,.next --quiet . and cloc --quiet src (outputs above).
• lizard src -l typescript --csv → 2,621 functions; distribution and top-N computed from the CSV.
• npm outdated (table in §1); npm view xlsx 'time[0.18.5]' → 2022-03-24T14:23:09.623Z.
• grep -rn "date-fns\|google-auth-library" over all source, script and test files → no imports.
• grep -rhoE "from '@/lib/[a-z0-9/-]+'" src | sort | uniq -c for fan-in.
• git log → one commit; git rev-parse --is-shallow-repository → false (history genuinely squashed, not a shallow clone).
• Files read: package.json, .nvmrc, vercel.json, README.md, .github/workflows/ci.yml.
• Mermaid diagram validated with the Mermaid validator (valid: true).

⚠️ Risks

✅ Recommendations