lakeFS - Data version control for your data lake | Git for data
C-Rank Grade: A (Welcoming) - 64/100
External PR Merge Rate: 74%
Response Time: 4d
First Timer Success: 67%
treeverse/lakeFS 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 treeverse/lakeFS respond to incoming external pull requests in approximately 100.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 63.8 places treeverse/lakeFS in the A tier.
The external contributor pull request merge rate for treeverse/lakeFS is 74.4%, based on public PR activity from non-core contributors.
treeverse/lakeFS currently has 4 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Strict review standards in treeverse/lakeFS. Ensure PR scope matches issue requirements closely before requesting review.
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/treeverse/lakeFS?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 Tuesday - Thursday from 13:00 to 17:00 UTC (13:00 - 17:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~65 hours (93% approval). Large PRs (>500 lines) take ~483 hours (33% approval). Keep your diff compact for rapid review.
Hi, thanks for the great, easy-to-use software product. Nowadays, I am storing some of my image data for AI pipelines on LakeFS. Feel like sometimes the preview of raw images of various formats would be handy. Specifically, I wonder if the preview of tiff images is possible to incorporate. For example, png preview is already working fine: And here is a preview on tiff image: Ready to collaborate and give a hand on this, if needed.
I would like to name branch some-test.ariels. But we only allow branches matching /^\w[-\w]*$. I understand these limitations: Repo names must match S3 bucket names or host-style addressing will not work. Branch names cannot contain slashes or lakefs://repo/branch/key will not work. Neither of these explain why I cannot have a period . in a branch name.
When displaying a branch, the objects page in the webui also computes and displays changes. To do this, it: Lists the objects on the branch. Lists the uncommitted changes. Merges the two lists to determine what to display. Both of these listings need to scan the same KV entries, which is slow (and see below). Instead we could: List the committed objects on the branch head (list branch@ instead of branch when branch is a branch; or ref~0 if ref@ gives us grief). List the uncommitted changes. Merge the two lists to determine what to display. Now the first listing is committed-only, which makes it incredibly faster. Why do we care? It's really slow, and this issue than doubles the effect of #2092!
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 treeverse/lakeFS, 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 treeverse/lakeFS acknowledge new external contributions in approximately 4 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 74.4% were successfully merged into the primary branch.
treeverse/lakeFS 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 ~4 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 63.8 places treeverse/lakeFS in the Welcoming tier.
The external pull request merge rate is 74.4%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, treeverse/lakeFS currently has 4 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for treeverse/lakeFS 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.