Modern React starter kit with Bun, TypeScript, Tailwind CSS, tRPC, Stripe, and Cloudflare Workers. Production-ready monorepo for building fast web apps.
C-Rank Grade: B (Solid) - 57/100
External PR Merge Rate: 83%
Response Time: 2d
First Timer Success: 100%
kriasoft/react-starter-kit has a recorded first-timer success rate of 100.0%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in kriasoft/react-starter-kit respond to incoming external pull requests in approximately 49.6 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.
The C-Rank™ system evaluates GitHub projects on a 0–100 scale using real data: PR merge rates, review turnaround time, active maintainer presence, and first-time contributor success. A score of 56.6 places kriasoft/react-starter-kit in the B tier.
The external contributor pull request merge rate for kriasoft/react-starter-kit is 83.3%, based on public PR activity from non-core contributors.
kriasoft/react-starter-kit does not currently have active "good first issue" tags indexed, but accepts external contributions through standard GitHub issue tracking.
Modern React starter kit with Bun, TypeScript, Tailwind CSS, tRPC, Stripe, and Cloudflare Workers. Production-ready monorepo for building fast web apps.
Security-obsessed senior engineer who audits infrastructure changes with exploit-level precision and demands documentation-code parity
The visible corpus is narrow: one reviewer across PR and issue threads, with identical text duplicated between PR reviews and issue comments. The reviewer's voice is technical, imperative, and evidence-dense. Each fix is named ('Fixed - ...'), the vulnerability is explained with exploit mechanics ('A branch name containing shell metacharacters can execute commands in this credential-bearing job before the step exits'), and the remediation is precise ('Use a static message or pass the value through env'). There is no small talk, no praise, no hedging. This is a maintainer who treats review as audit, not conversation.
Three friction patterns emerge. First, documentation drift is treated as a first-class defect: the reviewer explicitly flags `docs/security/checklist.md:78` for still pointing to the old command, signaling that stale docs are as blocking as broken code. Second, generators that produce partial or ambient-dependent output are rejected as verification hazards, not just inconvenience. Third, the reviewer requires that verification tooling be deterministic and complete enough to support comparison, implying that contributors cannot paper over gaps with manual review. The duplication of the same text in both PR reviews and issue comments suggests either a cross-posting habit or a single authoritative review being mirrored, not a broad community signal.
Average Response Latency
Tracks hours until a maintainer leaves a review, comment, or PR response.
External Acceptance Rate
Percentage of community pull requests successfully merged into main.
First PR Conversion
Rate at which developers submitting their first repository PR succeed.
Show contributors that your repository actively reviews and merges external pull requests.
[](https://getmerged.abhishekco.de/kriasoft/react-starter-kit?utm_source=github&utm_medium=badge)
Historical health & responsiveness evolution
External PR acceptance
First PR success rate
50% receive response in
90% receive response in
Maintainer review activity heatmap & prime window prediction
Calculating local time...
Calculating local time...
Detected: UTC
Maintainers are most responsive around 14:00 UTC (14:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 14:00 to 18:00 UTC (14:00 - 18:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~32 hours (96% approval). Large PRs (>500 lines) take ~238 hours (38% approval). Keep your diff compact for rapid review.
Enter your branch size and test coverage below to forecast review turnaround and get 1-click git splitting commands.
No cached good first issues currently tracked for kriasoft/react-starter-kit.
Rate what actually matters after opening a pull request here.
Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.
When evaluating whether to contribute to kriasoft/react-starter-kit, response velocity and maintainer engagement are crucial. GetMerged continuously tracks pull request trajectories, first-comment latency, and code review rounds to help developers avoid submitting pull requests to backlogged repositories.
Currently, maintainers of kriasoft/react-starter-kit acknowledge new external contributions in approximately 2 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 83.3% were successfully merged into the primary branch.
kriasoft/react-starter-kit has a recorded first-timer success rate of 100.0%. Repositories ranked Solid typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~2 days+. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.
The C-Rank™ index scores repositories on a 0 to 100 scale using an objective formula: external PR merge rates, initial response speed, active maintainer count, and first-time contributor retention. A score of 56.6 places kriasoft/react-starter-kit in the Solid tier.
The external pull request merge rate is 83.3%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
kriasoft/react-starter-kit does not have open beginner labels indexed currently, but external PRs for bugs and documentation improvements are evaluated via normal issue triage.
All metrics displayed for kriasoft/react-starter-kit are automatically retrieved via the public GitHub API and recalculated daily. Insider pull requests submitted by repository owners or organization members are excluded from merge rate calculations to preserve objective external contributor statistics.