Docling core data types and transformations
C-Rank Grade: B (Solid) - 47/100
External PR Merge Rate: 55%
Response Time: 9d
First Timer Success: 56%
docling-project/docling-core has a recorded first-timer success rate of 56.0%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in docling-project/docling-core respond to incoming external pull requests in approximately 213.2 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 47.0 places docling-project/docling-core in the B tier.
The external contributor pull request merge rate for docling-project/docling-core is 55.2%, based on public PR activity from non-core contributors.
docling-project/docling-core currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Highly encouraging & supportive maintainers (75% positive review sentiment). Active code reviews with constructive guidance for new contributors in docling-project/docling-core.
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/docling-project/docling-core?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 13:00 UTC (13:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 11:00 to 15:00 UTC (11:00 - 15:00 UTC local).
Limited recent maintainer review activity recorded for this repository. Prediction based on heuristic baseline.
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~139 hours (69% approval). Large PRs (>500 lines) take ~1023 hours (25% approval). Keep your diff compact for rapid review.
Enter your branch size and test coverage below to forecast review turnaround and get 1-click git splitting commands.
Alternative open-source projects with active maintainers in Python.
Learn it. Build it. Ship it for others.
A flexible tool for creating, organizing, and sharing visualizations of live, rich data. Supports Torch and Numpy https://visdom.dev
Lutris desktop client
The TripletTableSerializer aims at serializing tables to a text format that could be understood by LLMs for downstream applications like RAG. The implementation connects a column, a row, and the content of the cell in the given column and row to create sentences of the style A, B = C. The implementation needs to be reviewed, since it takes assumptions on the role of the first column and the first row to build the triplet representation of the table cells. For instance, the inner table in test/data/doc/rich_table.gt.html: will be serialized as follows (refer to the ground truth file 0c_out_chunks.json: cell 0,0, 1 = cell 0,1. cell 1,0, 1 = <em><p>text in italic</p></em>. <ul>\n<li>list item 1</li>\n<li>list item 2</li>\n</ul>, 1 = cell 2,1. cell 3,0, 1 = inner cell 0,0, 1 = inner cell 0,1. inner cell 0,0, 2 = inner cell 0,2. inner cell 1,0, 1 = inner cell 1,1. inner cell 1,0, 2 = inner cell 1,2. <p>Some text in a generic group.</p>\n<p>More text in the group.</p>, 1 = cell 4,1
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 docling-project/docling-core, 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 docling-project/docling-core acknowledge new external contributions in approximately 8 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 55.2% were successfully merged into the primary branch.
docling-project/docling-core has a recorded first-timer success rate of 56.0%. Repositories ranked Solid typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~8 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 47.0 places docling-project/docling-core in the Solid tier.
The external pull request merge rate is 55.2%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, docling-project/docling-core 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 docling-project/docling-core 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.