No state management strategy
Part of Architecture & Best Practices, which counts for 15% of the overall score. When this check fires it deducts 2 points from that category, once per scan, no matter how many places it turns up.
What it detects
A sizeable React app has no state-management library or Context API usage, often meaning state is drilled through many prop layers.
Why it matters
In a React app this size with no shared-state mechanism at all, data usually travels by prop drilling: every intermediate component accepts and passes values it never uses. That makes refactors ripple across many files and encourages duplicated local state that falls out of sync. Treat this as a signal to check rather than a defect.
How to fix it
First confirm the pain is real by finding props passed through three or more layers untouched. For low-frequency shared state like the current user or theme, React Context with a custom hook is built in and sufficient. For frequently-updated state shared across distant components, a small store like zustand or jotai fits; for server data, TanStack Query removes most of the need to hand-carry fetch results through props.
The paid report includes a ready-to-paste prompt for your AI coding agent for every check it finds, pointed at the exact findings from your scan. See pricing
Does your repo trip this check?
Paste a GitHub URL or drop a project folder. Scans run in your browser and take seconds.
Scan your repo