REPO·RANK #116·1/6 firing·TypeScript
Rank#116TypeScript
Cross-signal0.40 / 6.0
Single-channel signal so far. GitHub picked up +76 stars in 24h and Bluesky buzz (1 posts / 7d). Reddit, Dev.to and X are still cold — typical for a niche project at this stage.
Cross-signal · 30D+3%
GitHubFIRING+76 stars24h
HackerNewsQUIET0 posts7d
RedditQUIET0 posts7d
BlueskyFIRING1 posts7d
Dev.toQUIET0 posts7d
XQUIET0 posts7d
Stars8.7k+229 7d+76 today
Forks279+0 7d3% fork ratio
Contribs5+0 30dteam-led
Momentum27.85.0stars-velocity score
SurfaceTHIN1 / 6last commit 14h ago
Coverage2 / 13 sources fired (7d)
·1
Added 229 stars over the past week, climbing the TypeScript leaderboard with a steady 7-day curve.
// 01 · GITHUB MOMENTUM
27.8
+76 stars 24h | +229 7d
// 02 · MENTIONS
10
10 in 24h | 1 source
// 03 · CROSS-SIGNAL
0.40
1/6 channels firing
// 04 · PACKAGE ADOPTION
-
no linked package yet
// 05 · PROJECT SURFACE
thin
last commit 14h ago
// 01
Breakdown
How is this scored?
- 6.0
- strong signal across ≥5 of 6 channels
- 5.0
- strong signal across ≥4 of 6 channels
- 4.0
- strong signal across ≥3 of 6 channels
- 3.0+
- active on 2+ channels
- <1.0
- low or no cross-channel activity
Each channel contributes 0-1. Per-channel tiers: GitHub (breakout 1.0 / hot 0.7 / rising 0.4), HN (front-page 1.0 / ≥3 mentions 0.7 / 1-2 mentions 0.4), Bluesky (≥5 mentions 1.0 / 2-4 0.7 / 1 0.4), dev.to (≥3 articles 1.0 / 2 0.7 / 1 0.4), Reddit (corpus-normalized 48h velocity), X (≥10 mentions 24h 1.0 / 3-9 0.7 / 1-2 0.4).
- GitHub momentum0.00
- Reddit0.00
- HackerNews0.00
- Bluesky0.40
- dev.to0.00
- X (Twitter)0.00
* Reddit bar shows a per-repo velocity proxy (raw score / 100); the score formula uses the corpus-normalized version so a single repo's bar may not match its contribution to the corpus-wide ranking.
// KNOWN REPO · PACKAGE · LAUNCH · SITE SURFACES
GitHubmillionco/react-doctor8.7k starsWebsitereact.doctorsite found; profile scan queued
Docspendingdocs scanner pending
npmnoneno linked npm package
ProductHuntnoneno launch linked
Paper/modelpendingHF/arXiv resolver not attached yet
AISO scan
Scan queued — refresh to check status.
// 02
Growth
Today
8.3k
+676 last 24h
7d
+1.4k
20% wow
30d
+1.4k
20% mom
Spike
+6.9k/d
3d ago · peak day
// 03
Mentions
// last scanreddit 12mhn 32mbluesky 5mdevto 2hph 1hnpm 11h
- X→ OPEN
Introducing React Doctor Agent Skill Your agent can now catch bad React code and fix it too npx react-doctor@latest install▶ Twitter11h ago - X→ OPEN
turned it into a skill for my agent; feel free to copy paste --- name: reactdoctor100 description: Use when the user says "reactdoctor100", "/goal reactdoctor100", asks to get a React project to 100/100 in React Doctor, or wants to run a React Doctor eval loop while keeping build/tests green and documenting reviewed suppressions. --- # React Doctor 100 Use the latest React Doctor release as an eval loop, not as a blind refactor plan. When triggered by `reactdoctor100`, expand the shorthand into this objective: Get the project frontend to a configured React Doctor score of 100/100 while preserving intended behavior, keeping build/tests green, fixing high-signal issues first, and documenting any reviewed suppressions. If Codex goal tools are available and the user invoked `/goal reactdoctor100`, create or continue a Codex goal for that objective. Only mark the goal complete after the configured React Doctor score is 100/100 and the relevant build/tests pass. `100/100` means the score printed by React Doctor for the project scan after any reviewed `react-doctor.config.json` suppressions are loaded. Preserve a clear distinction between high-signal fixes and documented suppressions. ## Workflow 1. Inspect the repo first. - Find the frontend package path. - Identify React version, framework, package manager, build command, and test command. - Check git status before editing. 2. Run the latest React Doctor release. Prefer offline scan mode when the CLI supports it: ```bash npx -y react-doctor@latest <frontend-path> --offline --full --fail-on none ``` If the latest CLI changes flags, inspect `npx -y react-doctor@latest --help` and adapt while preserving the intent: full local scan, no automatic failure before triage, no install/refactor subcommand unless explicitly requested. 3. Group findings by signal. Fix high-signal findings first: - accessibility and ARIA issues - keyboard/focus behavior - invalid interactive markup - unstable keys - click/event propagation bugs - render-time side effects or heavy work - clear state/effect bugs - user-visible correctness issues Review these carefully before changing code: - React 19 migration advice in React 18 projects - shadcn/Radix `forwardRef` warnings - dead-code warnings for design-system exports - broad design-opinion rules - large component/refactor nudges without a feature reason - rules that require changing TypeScript target or browser support 4. Implement in small batches. - Prefer safe behavior-preserving fixes. - Re-run build/tests after meaningful batches. - Re-run React Doctor after each batch. 5. Only suppress after triage. - Add or update `react-doctor.config.json` only for reviewed false positives, stack incompatibilities, design-policy disagreements, or risky refactor nudges. - Do not suppress new accessibility, keyboard, ownership, data-integrity, or render-correctness findings unless clearly false positive. 6. Verify before finishing. - React Doctor reports `100/100`. - Frontend build passes. - Relevant tests pass. - Worktree status is understood. 7. Document project-specific policy. - Update project agent docs when present, such as `AGENTS.md`, `CLAUDE.md`, or similar. - Mention the scan command and what kinds of rules are intentionally suppressed. 8. Commit when appropriate. - Commit if the user asks for commits or the goal implies a clean checkpoint. - Keep the final response brief: score, build/test status, key changes, commit hash if created.▶ Twitter11h ago - X→ OPEN
React Doctor has been a huge discovery! There should be more utility tools like this for verifying and sanitizing a codebase. Through /goal, it’s possible to achieve a 100% fix rate for errors.▶ Twitter11h ago - X→ OPEN
React Doctor 入れてみた。 React系コード（Next.jsなど）を診断して、0〜100点のヘルススコアと改善点を出してくれるCLI。 Codex向けskillも入れられるので、React開発の仕上げチェックに良さげ👇▶ Twitter11h ago - X→ OPEN
これで入れられる👇 npx react-doctor@latest github.com/millionco/react-d…▶ Twitter11h ago - X→ OPEN
React の lint, 通らないコードの検出、それぞれのフレームワークによるプラクティスのチェックなどをやってくれるツール。 / “GitHub - millionco/react-doctor: Let coding agents diagnose and fix your React code” htn.to/2yCowTmnxm▶ Twitter11h ago - X→ OPEN
このリポジトリはReactでコンポーネントのライフサイクル管理を支援するようなライブラリらしい デバッグ作業の効率化に役立つかも yug1224 starred millionco/react-doctor github.com/millionco/react-d…▶ Twitter11h ago - X→ OPEN
"millionco/react-doctor: Let coding agents diagnose and f…" realtime.jser.info/2026/02/2… → github.com/millionco/react-d… Reactのコードベースを静的解析して、ヘルススコア(0〜100)を算出するツール。 60以上のルールでstate/effects、パフォーマンス、アーキテクチャ、バンドルサイズ、セキュリティ、▶ Twitter11h ago - X→ OPEN
"millionco/react-doctor: Let coding agents diagnose and f…" realtime.jser.info/2026/02/2… → github.com/millionco/react-d… Reactのコードベースを静的解析して、ヘルススコア(0〜100)を算出するツール。 60以上のルールでstate/effects、パフォーマンス、アーキテクチャ、バンドルサイズ、セキュリティ、▶ Twitter11h ago - X→ OPEN
⭐ Trending on GitHub Today: > Zaneham/BarraCUDA (882 stars, +186 stars) - Open-source CUDA compiler targeting AMD GPUs (and more in the future!). Compiles .cu to GFX11 machine code. > Developer-Y/cs-video-courses (73.5K stars, +456 stars) - List of Computer Science courses with video lectures. > millionco/react-doctor (2.2K stars, +406 stars) - Let coding agents diagnose and fix your React code > blackboardsh/electrobun (4.9K stars, +402 stars) - Build ultra fast, tiny, and cross-platform desktop apps with Typescript. > sipeed/picoclaw (15.9K stars, +342 stars) - Tiny, Fast, and Deployable anywhere — automate the mundane, unleash your creativity▶ Twitter11h ago
// 04
Context
- United States of America
- https://million.dev
- 23 public repos
- 316 followers
- ruvnet/rufloTypeScript · 49.7k stars
🌊 The leading agent orchestration platform for Claude. Deploy intelligent multi-agent swarms, coordinate autonomous workflows, and build conversational AI systems. Features enterprise-grade architecture, self-learning swarm intelligence, RAG integration, and native Claude Code / Codex Integration
- rohitg00/agentmemoryTypeScript · 5.7k stars
#1 Persistent memory for AI coding agents based on real-world benchmarks
- crynta/terax-aiTypeScript · 2.6k stars
Lightweight (7MB) AI terminal emulator (ADE) built in Rust & Tauri & React
- badlogic/pi-monoTypeScript · 1.9k stars
AI agent toolkit: coding agent CLI, unified LLM API, TUI & web UI libraries, Slack bot, vLLM pods
- virattt/dexterTypeScript · 25.5k stars
An autonomous agent for deep financial research
- getpaseo/paseoTypeScript · 6.0k stars
Orchestrate coding agents remotely from your phone, desktop and CLI
// 05Deep dive
// STARS8.7k+229/ 7dJust updated
// FORKS279—/ 7dJust updated
// CONTRIBUTORS5—/ 30dJust updated
Open Issues4
Last Commit14h ago
Latest Release—
// TREND24h+767d+22930d+234
X🔥
Ranked confirmation layer for repo-specific X buzz in the last 24h.
Mentions 24h
50
Authors 24h
37
Engagement
1.8k
Peak hour
10:11
Score
100.0
Breakout on X in the last 24h. 50 matched posts across 37 authors.
Top matched posts
- @aidenybai1.4k eng
Introducing React Doctor Agent Skill Your agent can now catch bad React code and fix it too npx react-doctor@latest install
mediumphrase11h agoopenMatched through a repo-specific project phrase query.
- @ZypherHQ214 eng
React Doctor has been a huge discovery! There should be more utility tools like this for verifying and sanitizing a codebase. Through /goal, it’s possible to achieve a 100% fix rate for errors.
mediumphrase11h agoopenMatched through a repo-specific project phrase query.
- @taiyo_ai_gakuse78 eng
React Doctor 入れてみた。 React系コード（Next.jsなど）を診断して、0〜100点のヘルススコアと改善点を出してくれるCLI。 Codex向けskillも入れられるので、React開発の仕上げチェックに良さげ👇
mediumphrase11h agoopenMatched through a repo-specific project phrase query.
- @yosuke_furukawa32 eng
React の lint, 通らないコードの検出、それぞれのフレームワークによるプラクティスのチェックなどをやってくれるツール。 / “GitHub - millionco/react-doctor: Let coding agents diagnose and fix your React code” htn.to/2yCowTmnxm
highrepo_slug11h agoopenContains the exact GitHub repo slug.
- @yug12247 eng
このリポジトリはReactでコンポーネントのライフサイクル管理を支援するようなライブラリらしい デバッグ作業の効率化に役立つかも yug1224 starred millionco/react-doctor github.com/millionco/react-d…
highrepo_slug11h agoopenContains the exact GitHub repo slug.
- @jser_info4 eng
"millionco/react-doctor: Let coding agents diagnose and f…" realtime.jser.info/2026/02/2… → github.com/millionco/react-d… Reactのコードベースを静的解析して、ヘルススコア(0〜100)を算出するツール。 60以上のルールでstate/effects、パフォーマンス、アーキテクチャ、バンドルサイズ、セキュリティ、
highrepo_slug11h agoopenContains the exact GitHub repo slug.
- @jser_info4 eng
"millionco/react-doctor: Let coding agents diagnose and f…" realtime.jser.info/2026/02/2… → github.com/millionco/react-d… Reactのコードベースを静的解析して、ヘルススコア(0〜100)を算出するツール。 60以上のルールでstate/effects、パフォーマンス、アーキテクチャ、バンドルサイズ、セキュリティ、
highrepo_slug11h agoopenContains the exact GitHub repo slug.
- @taiyo_ai_gakuse3 eng
これで入れられる👇 npx react-doctor@latest github.com/millionco/react-d…
mediumphrase11h agoopenMatched through a repo-specific project phrase query.
- @ohryansbelt3 eng
⭐ Trending on GitHub Today: > Zaneham/BarraCUDA (882 stars, +186 stars) - Open-source CUDA compiler targeting AMD GPUs (and more in the future!). Compiles .cu to GFX11 machine code. > Developer-Y/cs-video-courses (73.5K stars, +456 stars) - List of Computer Science courses with video lectures. > millionco/react-doctor (2.2K stars, +406 stars) - Let coding agents diagnose and fix your React code > blackboardsh/electrobun (4.9K stars, +402 stars) - Build ultra fast, tiny, and cross-platform desktop apps with Typescript. > sipeed/picoclaw (15.9K stars, +342 stars) - Tiny, Fast, and Deployable anywhere — automate the mundane, unleash your creativity
highrepo_slug11h agoopenContains the exact GitHub repo slug.
- @cptn3mox2 eng
turned it into a skill for my agent; feel free to copy paste --- name: reactdoctor100 description: Use when the user says "reactdoctor100", "/goal reactdoctor100", asks to get a React project to 100/100 in React Doctor, or wants to run a React Doctor eval loop while keeping build/tests green and documenting reviewed suppressions. --- # React Doctor 100 Use the latest React Doctor release as an eval loop, not as a blind refactor plan. When triggered by `reactdoctor100`, expand the shorthand into this objective: Get the project frontend to a configured React Doctor score of 100/100 while preserving intended behavior, keeping build/tests green, fixing high-signal issues first, and documenting any reviewed suppressions. If Codex goal tools are available and the user invoked `/goal reactdoctor100`, create or continue a Codex goal for that objective. Only mark the goal complete after the configured React Doctor score is 100/100 and the relevant build/tests pass. `100/100` means the score printed by React Doctor for the project scan after any reviewed `react-doctor.config.json` suppressions are loaded. Preserve a clear distinction between high-signal fixes and documented suppressions. ## Workflow 1. Inspect the repo first. - Find the frontend package path. - Identify React version, framework, package manager, build command, and test command. - Check git status before editing. 2. Run the latest React Doctor release. Prefer offline scan mode when the CLI supports it: ```bash npx -y react-doctor@latest <frontend-path> --offline --full --fail-on none ``` If the latest CLI changes flags, inspect `npx -y react-doctor@latest --help` and adapt while preserving the intent: full local scan, no automatic failure before triage, no install/refactor subcommand unless explicitly requested. 3. Group findings by signal. Fix high-signal findings first: - accessibility and ARIA issues - keyboard/focus behavior - invalid interactive markup - unstable keys - click/event propagation bugs - render-time side effects or heavy work - clear state/effect bugs - user-visible correctness issues Review these carefully before changing code: - React 19 migration advice in React 18 projects - shadcn/Radix `forwardRef` warnings - dead-code warnings for design-system exports - broad design-opinion rules - large component/refactor nudges without a feature reason - rules that require changing TypeScript target or browser support 4. Implement in small batches. - Prefer safe behavior-preserving fixes. - Re-run build/tests after meaningful batches. - Re-run React Doctor after each batch. 5. Only suppress after triage. - Add or update `react-doctor.config.json` only for reviewed false positives, stack incompatibilities, design-policy disagreements, or risky refactor nudges. - Do not suppress new accessibility, keyboard, ownership, data-integrity, or render-correctness findings unless clearly false positive. 6. Verify before finishing. - React Doctor reports `100/100`. - Frontend build passes. - Relevant tests pass. - Worktree status is understood. 7. Document project-specific policy. - Update project agent docs when present, such as `AGENTS.md`, `CLAUDE.md`, or similar. - Mention the scan command and what kinds of rules are intentionally suppressed. 8. Commit when appropriate. - Commit if the user asks for commits or the goal implies a clean checkpoint. - Keep the final response brief: score, build/test status, key changes, commit hash if created.
mediumphrase11h agoopenMatched through a repo-specific project phrase query.