Website for Meshery
C-Rank Grade: A (Welcoming) - 62/100
External PR Merge Rate: 70%
Response Time: 1d
First Timer Success: 67%
meshery/meshery.io has a recorded first-timer success rate of 66.7%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in meshery/meshery.io respond to incoming external pull requests in approximately 30.4 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 62.1 places meshery/meshery.io in the A tier.
The external contributor pull request merge rate for meshery/meshery.io is 69.6%, based on public PR activity from non-core contributors.
meshery/meshery.io currently has 20 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Highly welcoming maintainers in meshery/meshery.io. Prompt code reviews with positive guidance for new contributors.
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/meshery/meshery.io?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 13:00 UTC (13:00 UTC in your timezone). Recommended submission window is Monday - Thursday from 11:00 to 15:00 UTC (11:00 - 15:00 UTC local).
Limited recent maintainer review activity recorded for this repository. Prediction based on heuristic baseline.
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~20 hours (87% approval). Large PRs (>500 lines) take ~146 hours (31% 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.
Alternative open-source projects with active maintainers in JavaScript.
This project is waiting for your contribution. If you have never contributed code on GitHub before, this is the project to get you started.
Automated auditing, performance metrics, and best practices for the web.
This is a list of projects which have curated tasks specifically for new contributors. These issues are a great way to get started with a project, or to help share the load of working on open source projects. Jump in!
Description On the Meshery website, under Getting Started, the “Meshery Docs” link is not highlighted, so it is not visually prominent and does not clearly look like a clickable link. It should be highlighted like the “Extension Points” text in the other section, so users can easily identify it as a hyperlink. Expected Behavior The “Meshery Docs” text should be clearly highlighted and visible as a clickable link, similar to “Extension Points”. Screenshots Meshery Docs Expected Environment: OS: Mac Linux Windows Browser: Chrome Safari Firefox Version: Device: Desktop Mobile Contributor Guides and Handbook The meshery.io website uses Jekyll and GitHub Pages. Site content is found under the master branch. 📚 See the Contributing to Meshery.io Website section of the readme.md and other contributing instructions, too. 🎨 Wireframes and designs for Meshery UI in Figma (open invite) 🙋🏾🙋🏼 Questions: Discussion Forum and Community Slack 📺 Self-
Current State of the Meshery.io site On individual design pages in the Meshery Catalog, the design identifier is labeled as UUID and displayed as its full UUID value. There is currently no convenient way to copy the UUID. In addition, when a design page is shared in Slack or another platform, the unfurled link preview displays the UUID instead of the design title. Current design title: vault-0.30.1.tgz Current UUID: 00fadfee-3655-40c7-8a38-6c5cd72ea4da Desired State of the Meshery.io site The UUID field label should be changed to the more concise ID, while retaining the full UUID value. A copy-to-clipboard button should be displayed next to the ID. After the button is activated, it should briefly show feedback such as Copied!. The copy control should be accessible by keyboard and have an appropriate accessible label. The page title and social-preview metadata, including Open Graph and Twitter metadata where applicable, should use the design title instead of the UUID. For the example ab
Description When hovering over the copy button on the Meshery CLI page, the “Copy to clipboard” tooltip keeps flickering. Expected Behavior The “Copy to clipboard” tooltip should appear normally and stay stable when hovering over the copy button. Screenshots hover-flicker.mp4 Environment: OS: Mac Linux Windows Browser: Chrome Safari Firefox Version: Device: Desktop Mobile Contributor Guides and Handbook The meshery.io website uses Jekyll and GitHub Pages. Site content is found under the master branch. 📚 See the Contributing to Meshery.io Website section of the readme.md and other contributing instructions, too. 🎨 Wireframes and designs for Meshery UI in Figma (open invite) 🙋🏾🙋🏼 Questions: Discussion Forum and Community Slack 📺 Self-paced Contributor Trainings
Current State of the Meshery.io site When navigating the designs or models pages on small devices, the filter section can be difficult to use and interact with. The current UI/UX is not as intuitive as it could be, making it harder for users to navigate and apply filters efficiently. Desired State of the Meshery.io site Improve the filter section on small devices to make it cleaner, more intuitive, and easier to navigate and interact with. Contributor Guides The meshery.io website uses Jekyll and GitHub Pages. Site content is found under the master branch. 📚 See the Contributing to Meshery.io Website section of the readme.md and other contributing instructions, too. 🎨 Wireframes and designs for Meshery UI in Figma (open invite) 🙋🏾🙋🏼 Questions: Discussion Forum and Community Slack 📺 Self-paced Contributor Trainings
Description Some images are not visible properly in dark mode because the same SVGs are being used for both light and dark modes. Expected Behavior The SVGs should be updated or separate versions should be provided so that the images remain visible and readable in both light and dark modes. Screenshots Screen.Recording.2026-08-22.at.6.45.32.PM.mov
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 meshery/meshery.io, 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 meshery/meshery.io acknowledge new external contributions in approximately 1 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 69.6% were successfully merged into the primary branch.
meshery/meshery.io has a recorded first-timer success rate of 66.7%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~1 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 62.1 places meshery/meshery.io in the Welcoming tier.
The external pull request merge rate is 69.6%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, meshery/meshery.io currently has 20 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for meshery/meshery.io 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.