Official Go implementation of Apache Arrow
C-Rank Grade: A (Welcoming) - 65/100
External PR Merge Rate: 82%
Response Time: 9h
First Timer Success: 33%
apache/arrow-go has a recorded first-timer success rate of 33.3%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in apache/arrow-go respond to incoming external pull requests in approximately 9.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 64.6 places apache/arrow-go in the A tier.
The external contributor pull request merge rate for apache/arrow-go is 82.4%, based on public PR activity from non-core contributors.
apache/arrow-go currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Active maintainer team in apache/arrow-go 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/apache/arrow-go?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 16:00 UTC (16:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 15:00 to 19:00 UTC (15:00 - 19:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~6 hours (96% approval). Large PRs (>500 lines) take ~45 hours (37% approval). Keep your diff compact for rapid review.
Describe the bug compute.NewDatumWithoutOwning returns the same Datum implementation as compute.NewDatum, so calling Release() on it compiles and runs like any other datum. But the datum did not retain the value, so that Release() drops the reference the caller's array still depends on: the allocator reports the buffers freed while the array is in scope and readable, and the array's own later Release() does not panic. The doc comment says "should not have Release called on it", and ends with a truncated sentence: "For the most part this is just a convenience function.+-" (datum.go line 278). With the Go allocator this is silent, because the memory stays alive under the garbage collector. With a C allocator, or when the buffers were imported from C through the cdata package, the same call frees memory under a live array. Go 1.27.1, macOS 26.6 (arm64), arrow-go v18.7.0; identical on v18.8.0-rc1. mem := memory.NewCheckedAllocator(memory.NewGoAllocator()) b := array.NewInt64Builder(mem) b.
Describe the enhancement requested Add client-side test coverage for Substrait prepared statements in arrow/flight/flightsql/client_test.go. PR #732 added server-side coverage for CreatePreparedSubstraitPlan, but the review discussion identified that the corresponding client path has no dedicated tests. The tests should cover: Client.PrepareSubstrait constructing a CreatePreparedSubstraitPlan action with the supplied plan bytes and Substrait version. Parsing the returned prepared-statement handle and schemas. Preserving all three is_update states: absent, false, and true. Txn.PrepareSubstrait request construction, including the transaction ID, if it is not already covered through shared helpers. Query and update execution do not need duplicate coverage here: after prepared-statement creation, Substrait and SQL use the same Flight SQL execution paths. Component(s) Integration
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 apache/arrow-go, 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 apache/arrow-go acknowledge new external contributions in approximately 9 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 82.4% were successfully merged into the primary branch.
apache/arrow-go has a recorded first-timer success rate of 33.3%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~9 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 64.6 places apache/arrow-go in the Welcoming tier.
The external pull request merge rate is 82.4%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, apache/arrow-go currently has 2 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for apache/arrow-go 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.