The intelligent & developer-friendly EMS to support real-time energy flexibility apps, rapidly and scalable.
C-Rank Grade: A (Welcoming) - 69/100
External PR Merge Rate: 67%
Response Time: 7h
First Timer Success: 63%
FlexMeasures/flexmeasures has a recorded first-timer success rate of 62.5%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in FlexMeasures/flexmeasures respond to incoming external pull requests in approximately 7.1 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 69.0 places FlexMeasures/flexmeasures in the A tier.
The external contributor pull request merge rate for FlexMeasures/flexmeasures is 66.7%, based on public PR activity from non-core contributors.
FlexMeasures/flexmeasures currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Growing Python project in FlexMeasures/flexmeasures welcoming community pull requests and bug fixes.
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/FlexMeasures/flexmeasures?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 14:00 UTC (14:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 12:00 to 16:00 UTC (12:00 - 16:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~5 hours (83% approval). Large PRs (>500 lines) take ~34 hours (30% approval). Keep your diff compact for rapid review.
Description When calculating KPI averages over a selected date range, days without results are currently ignored. This can lead to misleading KPI values. Example Project ran for 5 days User selects 10 days Only 1 day has data with 100% KPI Current result: KPI = 100% Missing days are not reflected in the calculation Problem Missing days are neither: counted as 0%, nor clearly distinguished as non-run days Treating missing days as 0 is can be misleading because: 0% implies the project ran and failed these days actually represent non-run days This creates confusion and can mislead users when interpreting KPI results. Expected Behavior (UI/UX Proposal) Keep the current KPI calculation logic Detect when the selected KPI date range includes days with no results Display a warning / toast message to inform the user Proposed Toast Message (example) “Some selected days have no results. KPIs are calculated only from days where the project was run.”
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 FlexMeasures/flexmeasures, 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 FlexMeasures/flexmeasures acknowledge new external contributions in approximately 7 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 66.7% were successfully merged into the primary branch.
FlexMeasures/flexmeasures has a recorded first-timer success rate of 62.5%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~7 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 69.0 places FlexMeasures/flexmeasures in the Welcoming tier.
The external pull request merge rate is 66.7%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, FlexMeasures/flexmeasures 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 FlexMeasures/flexmeasures 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.