拼豆图纸生成器｜图片转拼豆、拼豆像素画与可编辑施工图｜逐格色号、辅助线、底板布局、用量统计｜Local-first fuse-bead pattern generator
C-Rank Grade: A (Welcoming) - 68/100
External PR Merge Rate: 93%
Response Time: 1h
First Timer Success: 100%
zwhy149/bead-grid-studio has a recorded first-timer success rate of 100.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in zwhy149/bead-grid-studio respond to incoming external pull requests in approximately 1.5 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 68.4 places zwhy149/bead-grid-studio in the A tier.
The external contributor pull request merge rate for zwhy149/bead-grid-studio is 92.9%, based on public PR activity from non-core contributors.
zwhy149/bead-grid-studio currently has 4 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
拼豆图纸生成器｜图片转拼豆、拼豆像素画与可编辑施工图｜逐格色号、辅助线、底板布局、用量统计｜Local-first fuse-bead pattern generator
Collaborative maintainer environment in zwhy149/bead-grid-studio. Reviews community pull requests with focus on project quality.
Discussions in zwhy149/bead-grid-studio focus heavily on practical implementation feedback, code formatting standards, and issue reproduction details.
Unlinked PRs without issue context and changes that fail automated test suites face the highest review friction.
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/zwhy149/bead-grid-studio?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 05:00 UTC (05:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 05:00 to 09:00 UTC (05:00 - 09:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~4 hours (96% approval). Large PRs (>500 lines) take ~7 hours (42% approval). Keep your diff compact for rapid review.
Goal Publish the benchmark table planned in ROADMAP.md for 16/24/32/48/60-cell output. Acceptance criteria Use original or licensed fixtures with pinned settings. State browser/device/runtime context and repeatable commands. Include quality/structure measurements, not only runtime. Avoid claims that a small grid is lossless or identical to the source.
Goal Add one focused keyboard-accessibility regression for the editor. Acceptance criteria Cover a meaningful keyboard path such as focus movement, drawer closing, or a canvas editing command. Assert a user-visible/resulting state, not only that a key was pressed. Keep it deterministic across supported Playwright browsers. Preserve existing keyboard behaviour.
Goal Review the English UI at 360px and 390px widths and improve any action labels that are unclear, clipped, or awkwardly wrapped. Acceptance criteria Check the English locale on a phone-width viewport. Keep primary actions understandable without relying on icons alone. Preserve touch-target and no-horizontal-overflow checks. Add or update a focused Playwright regression if behaviour changes.
Goal Add one original, CC0, public-domain, or otherwise redistributable image fixture for conversion regression coverage. Acceptance criteria Add the image under tests/fixtures/. Document its provenance and redistribution terms. Add a focused unit or E2E regression that uses it. Do not use customer photos, copyrighted characters, shop screenshots, or scraped social-media images. See CONTRIBUTING.md for fixture rules.
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 zwhy149/bead-grid-studio, 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 zwhy149/bead-grid-studio acknowledge new external contributions in approximately 1 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 92.9% were successfully merged into the primary branch.
zwhy149/bead-grid-studio has a recorded first-timer success rate of 100.0%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~1 hours. 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 68.4 places zwhy149/bead-grid-studio in the Welcoming tier.
The external pull request merge rate is 92.9%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, zwhy149/bead-grid-studio currently has 4 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for zwhy149/bead-grid-studio 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.