Forecastle is a control panel which dynamically discovers and provides a launchpad to access applications deployed on Kubernetes – [✩Star] if you're using it!
C-Rank Grade: A (Welcoming) - 58/100
External PR Merge Rate: 91%
Response Time: 15d
First Timer Success: 100%
stakater/Forecastle 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 stakater/Forecastle respond to incoming external pull requests in approximately 356.9 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 57.5 places stakater/Forecastle in the A tier.
The external contributor pull request merge rate for stakater/Forecastle is 90.9%, based on public PR activity from non-core contributors.
stakater/Forecastle currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Collaborative maintainer environment in stakater/Forecastle. Reviews community pull requests with focus on project quality.
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/stakater/Forecastle?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 18:00 UTC (18:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 16:00 to 20:00 UTC (16:00 - 20: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 ~232 hours (96% approval). Large PRs (>500 lines) take ~1713 hours (41% 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 Go.
All-in-one go testing library
`kubectl` plugin for KubeDB
Backup Docker volumes locally or to any S3, WebDAV, Azure Blob Storage, Dropbox, Google Drive or SSH compatible storage
Current behaviour Apps are currently sorted alphabetically by group name, then by app name within each group. This order is fixed — there is no way for a user to change the sort field or direction at runtime. Problem The fixed alphabetical order works well for small dashboards but becomes limiting as the number of apps grows. Common real-world needs that the current order cannot satisfy include: surfacing all apps in a given namespace together regardless of group name, reversing alphabetical order, or simply switching between sort strategies without touching any Kubernetes resources. Proposed solution Add a sort control to the existing toolbar — next to the current grid/list view toggle — that lets users sort app cards on the fly, entirely in the browser with no API changes required. The sorted state should be persisted in localStorage so it survives page refreshes. Sort fields: name, group, namespace ; each field supports ascending and descending direction.
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 stakater/Forecastle, 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 stakater/Forecastle acknowledge new external contributions in approximately 14 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 90.9% were successfully merged into the primary branch.
stakater/Forecastle 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 ~14 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 57.5 places stakater/Forecastle in the Welcoming tier.
The external pull request merge rate is 90.9%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, stakater/Forecastle currently has 1 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for stakater/Forecastle 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.