AsyncAPI specification website
C-Rank Grade: A (Welcoming) - 63/100
External PR Merge Rate: 52%
Response Time: -
First Timer Success: 38%
asyncapi/website has a recorded first-timer success rate of 38.1%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in asyncapi/website respond to incoming external pull requests in approximately 0.0 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 63.2 places asyncapi/website in the A tier.
The external contributor pull request merge rate for asyncapi/website is 52.4%, based on public PR activity from non-core contributors.
asyncapi/website currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Balanced & professional review environment in asyncapi/website. Maintains strict focus on technical quality and test standards.
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/asyncapi/website?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 03:00 UTC (03:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 03:00 to 07:00 UTC (03:00 - 07:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (65% approval). Large PRs (>500 lines) take ~115 hours (24% approval). Keep your diff compact for rapid review.
The shared Pagination component's "Go to page" dropdown does not correctly navigate to the selected page on desktop browsers. When selecting a page from the dropdown, the trigger loses focus before the selected page button's onClick event is processed, requiring multiple clicks for page navigation. The dropdown works as expected on mobile. Current behavior On desktop, selecting a page from the dropdown may require multiple clicks before navigating to the selected page. Before: Expected behavior On desktop, selecting a page from the "Go to page" dropdown should navigate to the selected page with a single click. The existing mobile behavior should remain unchanged. After: Have you checked for similar open issues? I checked and didn't find a similar issue. Are you willing to work on this issue? Yes, I am willing to submit a PR.
Description On the AsyncAPI Finance page, the Budget Analysis → Expenses section provides filters for Categories and Months. These filters work correctly on desktop. However, on mobile, the “All Categories” and “All months” dropdown filters are not usable as expected. The month data is still available on mobile. When horizontally scrolling the Budget Analysis section from left to right, the other months can be viewed. Steps to reproduce Open https://www.asyncapi.com/finance on a mobile device or mobile viewport. Scroll to Budget Analysis → Expenses. Try to use the “All Categories” dropdown. Try to use the “All months” dropdown. Observe that the dropdown filters cannot be used as expected. Horizontally scroll/swipe the Budget Analysis section from left to right. Observe that the data for the other months is still visible. Actual behavior On mobile, the “All Categories” and “All months” dropdown filters are not usable as expected. However, the month data can
What changes are you proposing? Add automated unit tests for the blog post composition script (scripts/compose.ts) to cover its interactive CLI flow and file generation behavior. Why do we need this improvement? The compose script is frequently used by contributors to create new blog posts, but it currently has no automated coverage. Problems now: No tests for the CLI flow. Manual validation required for any change. Risk of regressions in slug generation, front matter output, and file writing. How will this change help? Safer refactoring of the script. Faster contributor feedback via npm test. Ensures consistent output (front matter + slug + file path). How could it be implemented/designed? Implementation plan: Add tests/scripts/compose.test.ts using Jest (already configured with asyncapi/website). Mock dependencies: inquirer for CLI answers. fs for file writes. moment for deterministic dates. Test scenarios: Happy path: verify file path + front matter. Slug generation: ensure t
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 asyncapi/website, 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 asyncapi/website acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 52.4% were successfully merged into the primary branch.
asyncapi/website has a recorded first-timer success rate of 38.1%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~-. 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 63.2 places asyncapi/website in the Welcoming tier.
The external pull request merge rate is 52.4%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, asyncapi/website currently has 2 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for asyncapi/website 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.