OpenLake is a high performance storage engine for efficient LLM inference and GPU Training
C-Rank Grade: S (Elite) - 70/100
External PR Merge Rate: 72%
Response Time: 9h
First Timer Success: 50%
openlake-project/openlake has a recorded first-timer success rate of 50.0%. Repositories ranked S typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in openlake-project/openlake respond to incoming external pull requests in approximately 8.6 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 70.1 places openlake-project/openlake in the S tier.
The external contributor pull request merge rate for openlake-project/openlake is 71.7%, based on public PR activity from non-core contributors.
openlake-project/openlake currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Highly welcoming maintainers in openlake-project/openlake. 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/openlake-project/openlake?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 11:00 UTC (11:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 08:00 to 12:00 UTC (08:00 - 12:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~6 hours (90% approval). Large PRs (>500 lines) take ~41 hours (32% approval). Keep your diff compact for rapid review.
Currently openlake supports S3 APIs and third party benchmark clients. All APIs are supported over TCP with no ability to run local tests/bench. Introduce a CLI layer to allow users in dev settings to bootstrap local clusters, and run APIs over CLI interface. New CLI commands can be along the lines of bench (runs a new bench), get (1/1 to GET api), put and others. Initial goal is to introduce a new code layer (perhaps over engine.rs) and incrementally add new CLI commands.
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 openlake-project/openlake, 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 openlake-project/openlake acknowledge new external contributions in approximately 8 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 71.7% were successfully merged into the primary branch.
openlake-project/openlake has a recorded first-timer success rate of 50.0%. Repositories ranked Elite typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~8 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 70.1 places openlake-project/openlake in the Elite tier.
The external pull request merge rate is 71.7%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, openlake-project/openlake 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 openlake-project/openlake 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.