react-doctor

To scan a React codebase for performance bottlenecks and dead code, run a full project scan to identify lint errors, accessibility issues, and architectural flaws. This generates a prioritized 0-100 health score with issues sorted by severity for targeted remediation.

You can check React code quality before committing by running a diff-based scan of changed files against the base branch. This verifies recent feature development or bug fixes did not introduce new correctness errors or cause a health score regression.

A React health score is a 0-100 metric evaluating codebase maintainability by identifying security vulnerabilities, performance bottlenecks, and architectural flaws. It prioritizes identified issues by severity, outputting errors first then warnings, to guide targeted code cleanup.

Yes, you can use diff scanning to prevent React code quality regressions. By scanning only the files changed against your base branch, it performs quick pre-commit checks to ensure new code does not introduce accessibility gaps or bundle size bloat.

React code scanning covers accessibility issues and bundle size bloat alongside lint errors and dead code. It runs comprehensive checks across the project to detect these specific problems, helping improve overall maintainability and prevent unexpected runtime regressions.

The best way to prioritize React code cleanup is using a generated 0-100 health score that sorts identified issues by severity. By addressing critical errors first and warnings next, you systematically resolve security vulnerabilities and architectural debt to improve maintainability.