react-doctor vs no-mistakes

Two of the top projects in Code review and testing, side by side: who leads on each score part and who each one suits, then setup, license, activity and what each review found.

22nd of 10 in Code review and testing

react-doctor

CLI that scans React codebases for state, performance, security and accessibility issues

#44th of 10 in Code review and testing

no-mistakes

Local git proxy that runs AI review, tests and lint before opening a PR

Verdict

react-doctor ranks higher, 72 to 70. Of the 5 score parts we measure for both, react-doctor leads on 2, no-mistakes on 2 and 1 is even.

  • Adoptionreact-doctor leads by 26 points, 75 to 49: a wide gap.
  • FreshnessEven at 100.
  • Maintenancereact-doctor leads by 11 points, 95 to 84.
  • Easy to runno-mistakes leads by 17 points, 50 to 33: a wide gap.
  • Agent-readyno-mistakes leads by 15 points, 85 to 70: a wide gap.

Pick react-doctor if you are

React and React Native developers wanting code checks locally and in CI

  • Runs with one npx command from the project root, no setup needed
  • Deterministic rules rather than LLM-generated findings

Pick no-mistakes if you are

Developers who want agent-checked branches before raising PRs

  • Runs in an isolated worktree, so your working directory is not disturbed
  • Works with claude, codex, grok, opencode, copilot, cursor and others, with ordered fallbacks
react-doctor vs no-mistakes: score parts and facts
What we comparereact-doctorno-mistakes
Score parts, out of 100
Adoption75, popular49, known
Freshness100, active100, active
Maintenance95, healthy84, healthy
Easy to run33, some setup50, easy
Agent-ready70, partly85, ready
Facts from GitHub and the README
Stars15k8.9k
Licensecustom license (read the license)MIT (permissive)
Last commitOct 2026Oct 2026
Last releaseOct 2026Sep 2026
LanguageTypeScriptGo
DockerNoNo
GPUNot neededNot stated
arm64 or Apple SiliconNot statedMentioned

react-doctor

React Doctor runs deterministic checks over a React project and reports issues in state and effects, performance, architecture, security, accessibility and maintainability. It covers Next.js, Vite, Astro, TanStack, React Native and Expo. It also installs as a skill for coding agents, runs on pull requests in CI, and can record a Chrome DevTools performance trace of a running app.

Who it is for: React and React Native developers wanting code checks locally and in CI

Strengths

  • Runs with one npx command from the project root, no setup needed
  • Deterministic rules rather than LLM-generated findings
  • Agent skill installer supports Claude Code, Cursor, Codex and OpenCode
  • Rules configurable in doctor.config.ts; CI installer reports issues each PR introduces

Weaknesses

  • React-only; no support for other frameworks beyond the listed React stacks
  • CLI collects crash reports and anonymous usage data unless opted out
  • Runtime trace scan needs a running app and a Chrome DevTools trace
  • README does not list the number of rules or their names
  • no GPU
  • Needs Node.js, npm

no-mistakes

no-mistakes places a local git remote in front of your real one. Pushing to it creates a disposable worktree and runs a pipeline (review, test, docs, lint, push, PR, CI) driven by a coding agent CLI such as claude or codex. The branch is forwarded to the real remote only after every gate passes, and a PR is opened for you. Safe fixes are applied automatically; other findings wait for approval in a TUI.

Who it is for: Developers who want agent-checked branches before raising PRs

Strengths

  • Runs in an isolated worktree, so your working directory is not disturbed
  • Works with claude, codex, grok, opencode, copilot, cursor and others, with ordered fallbacks
  • Three entry points: git push, a TUI, or a /no-mistakes agent skill
  • Watches CI after the PR opens and auto-repairs failures

Weaknesses

  • Requires a runnable coding agent CLI configured for every gate
  • Agent calls spend API quota; RAM and cost figures are unknown
  • CI repairs may need another full review pass if revalidate_repairs is set
  • Auto PR creation and CI watching are documented only for configured push targets such as GitHub
  • Needs git, a coding agent CLI (claude, codex, opencode, etc.)
  • Models: claude, codex, grok, rovodev, opencode

More in Code review and testing

Building with these?

We help teams pick an open-source AI stack and run it in production. Client work never changes a rank.