Documentation and Developer resources for Layer5 products
C-Rank Grade: A (Welcoming) - 66/100
External PR Merge Rate: 77%
Response Time: 1h
First Timer Success: 65%
layer5io/docs has a recorded first-timer success rate of 65.2%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in layer5io/docs respond to incoming external pull requests in approximately 1.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 65.9 places layer5io/docs in the A tier.
The external contributor pull request merge rate for layer5io/docs is 76.6%, based on public PR activity from non-core contributors.
layer5io/docs currently has 30 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Documentation and Developer resources for Layer5 products
Collaborative maintainer environment in layer5io/docs. Reviews community pull requests with focus on project quality.
Discussions in layer5io/docs 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/layer5io/docs?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 22:00 UTC (22:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 19:00 to 23:00 UTC (19:00 - 23: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 (34% approval). Keep your diff compact for rapid review.
Objective Create a repository-specific VISION.md for layer5io/docs, following the established Layer5 vision-document approach rather than a generic project vision. Scope and constraints Documentation only. Do not change build or product behavior. Add VISION.md at the repository root. Ground the vision in the actual responsibilities and practices of layer5io/docs. Preserve existing documentation conventions and repository guidance. Quality bar Nothing generic. Statements should be specific to the Layer5 documentation repository. Every substantive claim should be traceable to this repository, authoritative Layer5/Meshery source repositories, or published Layer5 material. Distinguish documented product behavior from aspirational direction. Follow the repository's established voice and contribution conventions. Preserve compatibility concerns documented in AGENTS.md, including stable URLs/anchors and verification of product behavior against authoritative implementations. Use plain hyphe
Current Behavior as of now there, are various pages which have issue of responsiveness, and they are breaking the ui leading to awkward spaces on both sides of the pages. Pages affected by this kind of behaviour is: Core Tasks Deploying Designs Undeploying Designs Cloning a Design Reference Releases Default user role Default organization role Default Team roles Default Workspace roles Default user permission Tutorials spaces guides and tutorials Integrartions Expected Behavior in desktop view above 1920, the page shouldn't have necessary spaces Screenshots/Logs Environment Host OS: Linux Windows Browser: Chrome Contributor Guide and Resources 📚 Instructions for contributing to documentation Layer5 documentation site and source 🎨 Wireframes and designs for Layer5 site in Figma (open invite) 🙋🏾🙋🏼 Questions: Layer5 Discussion Forum and Layer5 Community Slack
Current State In Relationships docs page, there are two hierarchical relationships listed - Hierarchical-Inventory and Hierarchical-Parent. However, there are four hierarchical relationships listed in the Layers Sidebar in Kanvas: Hierarchical Inventory, Hierarchical Wallet, Hierarchical Alias and Hierarchical TagSets. An entry for Edge Annotation is missing as well in the docs. Screenshot of Kanvas for reference: Desired State The documentation must be updated to match the application. Contributor Guide and Resources 📚 Instructions for contributing to documentation Layer5 documentation site and source 🎨 Wireframes and designs for Layer5 site in Figma (open invite) 🙋🏾🙋🏼 Questions: Layer5 Discussion Forum and Layer5 Community Slack
Current Behavior On the docs homepage, the tutorial/doc cards (Cloud Docs, Kanvas Docs, Meshery Docs, Nighthawk Docs) show the wrong icon after tapping a card and then navigating back on iPhone. Confirmed on both Safari and Chrome on iOS. Android is not affected. Steps to reproduce Open the docs homepage on an iPhone (Safari or Chrome). Tap any doc card (e.g. "Kanvas Docs"). Use the browser back button to return to the homepage. Observe the icon for that card — it renders incorrectly instead of the default icon. Expected Behavior The icon should always show its default state when the homepage loads or is returned to. Screenshots/Logs ScreenRecording_08-17-2026.18-43-46_1.MP4 Environment Host OS: Mac Linux Windows Browser: Chrome Safari Firefox Edge Opera Contributor Guide and Resources 📚 Instructions for contributing to documentation Layer5 documentation site and source 🎨 Wireframes and designs for Layer5 site in Figma (open invite
Current Behavior The image on this page (https://docs.layer5.io/cloud/concepts/identity-and-security/teams/) is not rendering correctly. Expected Behavior The image should be displayed correctly, similar to the Users documentation page: https://docs.layer5.io/cloud/concepts/identity-and-security/users/ Screenshots/Logs Environment Host OS: Mac Linux Windows Browser: Chrome Safari Firefox Edge Opera Contributor Guide and Resources 📚 Instructions for contributing to documentation Layer5 documentation site and source 🎨 Wireframes and designs for Layer5 site in Figma (open invite) 🙋🏾🙋🏼 Questions: Layer5 Discussion Forum and Layer5 Community Slack
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 layer5io/docs, 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 layer5io/docs acknowledge new external contributions in approximately 1 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 76.6% were successfully merged into the primary branch.
layer5io/docs has a recorded first-timer success rate of 65.2%. 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 65.9 places layer5io/docs in the Welcoming tier.
The external pull request merge rate is 76.6%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, layer5io/docs currently has 30 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for layer5io/docs 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.