lance-format/lance - Open Source PR Review Scorecard

Open Lakehouse Format for Multimodal AI. Convert from Parquet in 2 lines of code for 100x faster random access, vector index, and data versioning. Compatible with Pandas, DuckDB, Polars, Pyarrow, and PyTorch with more integrations coming..

C-Rank Grade: A (Welcoming) - 66/100

External PR Merge Rate: 60%

Response Time: -

First Timer Success: 48%

Frequently Asked Questions

Is lance-format/lance welcoming to first-time open-source contributors?

lance-format/lance has a recorded first-timer success rate of 48.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.

How fast can I expect code review feedback on my pull request?

Maintainers in lance-format/lance respond to incoming external pull requests in approximately 0.0 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.

What does the 65.9 C-Rank™ score (A Tier) represent?

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 65.9 places lance-format/lance in the A tier.

What is the external contributor pull request merge rate for lance-format/lance?

The external contributor pull request merge rate for lance-format/lance is 60.1%, based on public PR activity from non-core contributors.

Are there Good First Issues available in lance-format/lance?

lance-format/lance currently has 5 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".

lance-format
lance-format/lanceA•Welcoming7.1k
GitHub
Back to Explorer
lance-format

lance-format/lance

7,140
Active (30d)A•Welcoming(66/100)Rust

Open Lakehouse Format for Multimodal AI. Convert from Parquet in 2 lines of code for 100x faster random access, vector index, and data versioning. Compatible with Pandas, DuckDB, Polars, Pyarrow, and PyTorch with more integrations coming..

GitHub
Compare••
Jump to:

AI Maintainer Review Guidelines

Review Persona

Welcoming Community Builder

Warmth Score
8.5/10
Patience Score
8.6/10
Nitpick Rate
30%

Highly welcoming maintainers in lance-format/lance. Prompt code reviews with positive guidance for new contributors.

Top PR Submission Do's

  • •Ensure code complies with the project coding style
  • •Keep PRs scoped to a single concern
  • •Include context and link to the related issue

Top PR Friction Pitfalls (Don'ts)

  • •Do not submit PRs without linking an issue
  • •Do not break existing tests without fixing them
  • •Do not mix unrelated refactors in a single PR
Response Velocity
-
No reviewer activity recorded

Average Response Latency

Tracks hours until a maintainer leaves a review, comment, or PR response.

Merge Efficiency
60.1%
Moderate PR acceptance rate

External Acceptance Rate

Percentage of community pull requests successfully merged into main.

First-Timer Success
48.0%
Accepts new contributor PRs

First PR Conversion

Rate at which developers submitting their first repository PR succeed.

Active Maintainers
80 core
Highly collaborative maintainer core
Diagnostic Health HUD
60.1%
Merge Gauge
48.0%
1st-Timer
Community Vibe38/100

Embed C-Rank Badge

Show contributors that your repository actively reviews and merges external pull requests.

GetMerged C-Rank badge for lance-format/lance
[![GetMerged C-Rank](https://getmerged.abhishekco.de/api/badge/lance-format/lance)](https://getmerged.abhishekco.de/lance-format/lance?utm_source=github&utm_medium=badge)

Active Good First Issues (5)

View on GitHub

Problem A Lance Namespace REST server return a standard throttling response: HTTP/1.1 429 Too Many Requests Retry-After: 2 with the official Namespace error code 21 (THROTTLING). However, the current REST Namespace client discards response headers while converting an HTTP response into a Namespace error. Callers only receive ThrottlingError with its message and error code; they cannot access Retry-After, the HTTP status, or other response metadata. This prevents SDK and application layers from implementing server-directed retry, queuing, or throttling coordination. Current behavior The REST request path in rust/lance-namespace-impls/src/rest.rs receives a reqwest::Response, reads the error body, and maps its Namespace error code to an error type. Response headers are not preserved during this conversion. Consequently, Python callers can catch: except lance_namespace.errors.ThrottlingError as error: ... but cannot determine whether: the server provided a retry delay; the throttling

📅 Opened Sep 10, 2026💬 6 comments
Quality: 50/100Contribute

We already have code that it generic over Utf8 and LargeUtf8, so it should mostly be a matter to findings the places where we match on those and add cases for StringView. Examples: lance/rust/lance-arrow/src/lib.rs Lines 470 to 476 in 11eeb29 pub fn iter_str_array(arr: &dyn Array) -> Box<dyn Iterator<Item = Option<&str>> + Send + '_> { match arr.data_type() { DataType::Utf8 => Box::new(arr.as_string::<i32>().iter()), DataType::LargeUtf8 => Box::new(arr.as_string::<i64>().iter()), _ => panic!("Expecting Utf8 or LargeUtf8, found {:?}", arr.data_type()), } } lance/rust/lance-index/src

📅 Opened Aug 4, 2026💬 3 comments
Quality: 40/100Contribute

In many places we output the same set of fields and/or schema per method call, or even per batch. This can be made cheaper if we initialize them once via a LazyLock and wrapping in an Arc. Here's an example where we construct a schema per query: lance/rust/lance-index/src/scalar/inverted/index.rs Lines 8107 to 8116 in 11eeb29 Field::new(FLAT_ALL_TOKENS_COL, DataType::UInt64, false), Field::new( FLAT_QUERY_TOKEN_COUNTS_COL, DataType::FixedSizeList( Arc::new(Field::new("item", DataType::UInt64, true)), query_tokens.len() as i32, ), false,

📅 Opened Aug 4, 2026💬 2 comments
Quality: 80/100Contribute

Follow up to #7226. Need to add that option for Java.

📅 Opened Jun 16, 2026💬 1 comment
Quality: 25/100Contribute

As we are wrapping up on the dataset level column statistics MVP, there are some high priority todo items: [ ] Support column stats generation for partial dataset. Currently the dataset will only be generated when all the files in the dataset has column stats written. A naive implementation is just to build the stats from the old fragment file rather than terminate early. [ ] Expose a Python API from the rust implementation. [ ] Exposing more stats in the discussion thread #4540 More could be found in the design doc

📅 Opened Jan 29, 2026💬 0 comments
Quality: 70/100Contribute
Looking for more Rust beginner tasks?Explore Rust GFI

Contributor Community Vibe Feedback

Rate what actually matters after opening a pull request here.

Have you contributed to this repo?

Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.

3 ratings required
Maintainer helpfulness
Review speed
Beginner friendliness

Contributor Compatibility & Review Speed Analysis for lance-format/lance

When evaluating whether to contribute to lance-format/lance, 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 lance-format/lance acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 60.1% were successfully merged into the primary branch.

Frequently Asked Questions - Contributing to lance-format/lance

01

Is lance-format/lance welcoming to first-time open-source contributors?

lance-format/lance has a recorded first-timer success rate of 48.0%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.

02

How fast can I expect code review feedback on my pull request?

The initial maintainer response time averages ~-. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.

03

What does the 65.9 C-Rank™ score represent?

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 65.9 places lance-format/lance in the Welcoming tier.

04

What is the external contributor pull request merge rate for lance-format/lance?

The external pull request merge rate is 60.1%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.

05

Are there beginner Good First Issues open in lance-format/lance?

Yes, lance-format/lance currently has 5 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.

GetMerged C-Rank™ Indexing Standard

All metrics displayed for lance-format/lance 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.