Repowise analysis of my FocusMentor project

[rishu685]

Here is the Repowise code health and dead code analysis of my Next.js + Express study tool codebase.

The Finding That Surprised Me
What surprised me most was how well Repowise caught frontend UI component "spaghetti" logic and copy-paste layout drift.

--Complex Event Handlers in UI Components: Repowise flagged the handleUpload function inside my Next.js client component SyllabusUpload.tsx with a nesting depth of 6 and a cyclomatic complexity of 21. Because it wraps uploading state, fetches, nested error checks, and timeouts in one event handler, Repowise correctly highlighted it as a candidate for extraction into a separate React Hook.

--Page Component Duplication: It detected a 48% DRY violation between StoredPlan.tsx ( saved study plans viewer) and StoredResources.tsx (saved web resources viewer). Since both use similar grid card displays, filters, and localStorage lookups, the developer duplicated the page layout instead of making a generic card viewer template.

for reference:
--Files Analyzed: 222 files (64% TypeScript, 24% JavaScript)
--Overall Health: 8.28/10 (Generally healthy, but with concentrated hotspots)
--Worst File: server/services/aiService.js (Scored 1.0/10 due to being a 1,463-line God module with a cyclomatic complexity of 43)
Clean-up Candidates: 143 dead code findings (~2,866 lines of unused exports and unreachable files, including an unused /netlify subdirectory deployment clone)