Clean scanStatic scanned
Free
Copy any element in your React app with its component stack and source location for your agent.
4.4M installs/moMIT
React Doctor
abai · Agent
React Doctor audits a React project for issues in state and effects, performance, architecture, security, accessibility and maintainability, and points to overly complex functions and repeated JSX that could be composed. It is aimed at checking React code that a coding agent has written, with JSON output for agents. A CI mode reviews every pull request and reports only the issues the change introduces, and a scan command records a Chrome performance trace while you use a running app.
Written by ooruby from the README of react-doctor 0.9.17.
Not claimed by its maker. Is this yours? Prove it and answer the findings
Why it's useful
It gives you a report of React issues, from effects to accessibility, so you can check what your coding agent wrote.
What you could do with it
- Run it at the project root to get an audit of the React codebase.
- Set up the CI workflow so each pull request reports only the issues that change introduced.
- Record a performance trace while you click through a running local app, then read the summary.
Written from its documentation: what it says it can do, not what our checks found.
Maintenance
Not measuredNo release date is on record for this package yet. The nightly publisher check records one as it reaches each npm package, about once every ten nights.
Release activity only: it says nothing about quality or safety, and a finished small package can be fine without releases. How it is measured
What this does not cover
- Everything. Treat it as you would software from anywhere else.
Receipt history: every signed receipt for every version of this listing, and what changed between them.
In its maker's words
Your agent writes bad React. This catches it
Compare with
Compare all 4How far this has been checked
Static scanned
- What it establishes
- Its published package, or for a hosted server its source repository at a recorded commit, was read file by file, without running it, by every check in our current scan.
- What it does not
- How it behaves when it runs, or anything the scan does not read yet: several rubric checks, the repository's history, and compiled code in folders named dist or build. For a hosted server, that the endpoint runs the code that was read. The ooruby Index sets out exactly what was read.
- Exactly what was read
- Version 0.9.17, the file with digest sha512-YCsjYk6MocO/oBhVxCcKvPotFxEOf/WJep/oF7jrpyVUBVKDKdpt7jVwTxrJrFE8uALMmVTljzXNTIjoL3talg==, as the registry publishes it. A published version cannot be replaced, so this names the same bytes for anyone who checks.
- Authentication
- Runs locally. No hosted endpoint is listed for this package. You run it on your own machine, so there is no endpoint of ours to authenticate against.
Adding it
Run it with:
npx -y react-doctor@0.9.17Pinned to 0.9.17, which is the version the findings above were found in. Drop the version to take whatever is newest, and the report on this page stops describing what you installed.
Where this came from
- Registry
- npm
- Package
- react-doctor
- Version read
- 0.9.17
- Resolved
- 2026-10-10
Built from source, attested
npm publishes a signed statement that this exact package was built from the repository below, at this commit. It is verifiable without taking our word for it.
- Repository
- github.com/millionco/react-doctor
- Commit
- 0a046d214ce9
- Built by
- github.com/actions/runner/github-hosted
- Registry publish attestation
- signed by npm · 2026-10-10
- Checked
- 2026-10-10
The badge, if this is your listing
It renders the current rung (static scanned) and links back here, where what that does and does not establish is one click away. It updates itself as the evidence deepens.
[](https://ooruby.com/market/react-doctor)About this listing
- Kind
- Agent
- Category
- Developer tools
- Pricing
- Free
- Sandbox
- No
- Hosted
- No
- Updated
- 2026-10-10
More from abai
See the storefrontSimilar agents
All agentsVerification records what our published tests found on a specific version at a specific date. It is not a warranty, and it does not certify that software is free of defects.