docling-project/docling-core

Docling core data types and transformations

Hosted by LF AI & Data Foundation · part of Linux Foundation

View on GitHub ↗Jump to charts ↓Open shareable report →

docling-project/docling-core has 250+ stars and 250+ forks on GitHub, is written in HTML, and was last pushed on Oct 18, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 34 minutes ago
Added to GitGenius on October 15th, 2026
Created on July 12th, 2024
Open Issues & Pull Requests: 177 (+0)
GitHub issues: Enabled
Number of forks: 251
Total Stargazers: 294 (+0)
Total Subscribers: 9 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 47.0 hours
Mean response time: 35.8 days
90th percentile: 132.5 days
Tracked items: 146

Maintainer activity

12 people did triage or write work on this repository in the last 12 months.

Counts unlabeled, assigned, unassigned, milestoned, demilestoned, locked, unlocked over the last 12 months. These are issue and pull request events that require triage or write permission. Commits and code review are not counted. labeled and renamed are excluded because GitHub issue forms record the issue author as the actor. Figures from October 18, 2026. This count is not comparable across projects: each project's automation decides which of these events a person emits. How this is counted.

How this project is maintained

Roughly one issue in four opened in the past year never receives a reply. 85% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Work labelled "enhancement" is answered fastest, typically in about an hour, while "bug" waits about 2 days. 21% of tracked open issues have had no activity in three months. Only 45% of issues opened in the past year have been closed.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 82
New in 7 days: 8
Closed in 7 days: 3
Avg open age: 211 days
Stale 30+ days: 44
Stale 90+ days: 30

Recent activity

Opened in 7 days: 6
Closed in 7 days: 3
Comments in 7 days: 6
Events in 7 days: 23

Top labels

  • bug (24)
  • enhancement (17)
  • good first issue (3)
  • chunking (2)
  • documentation (2)
  • question (2)
  • serialization (2)
  • doclang (1)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

Docling Core is a library that defines core data types and transformations for document processing in the Docling ecosystem.

The library addresses the need for a standardized, extensible foundation when building document processing and generative AI applications. It centers on the DoclingDocument, a Pydantic model that serves as the primary data structure for representing processed documents. This model-first approach enables strong type safety, schema validation, and interoperability while providing an API for constructing documents and exporting them to formats like Markdown and HTML. Beyond the core data model, the tool offers pluggable APIs for serialization and chunking, allowing developers to customize how documents are converted to different formats and split into segments for downstream tasks. A profiling API extracts structural and statistical metrics from documents, supporting both individual analysis and collection-level insights with visualization capabilities.

Docling Core is suited for teams building document processing pipelines or retrieval-augmented generation systems that need a reliable, schema-driven representation of document content. It works best as a foundation library within the broader Docling ecosystem rather than as a standalone tool. Developers should adopt it if they require fine-grained control over document structure, need to serialize documents in multiple formats, or want to implement custom chunking strategies without reinventing the data model layer.

The project maintains active development with regular updates across its core components. The codebase supports a wide range of Python versions, indicating attention to compatibility across environments. Development is structured around clear separation of concerns, with distinct APIs for serialization, chunking, and profiling that can be extended independently. The project includes comprehensive documentation with architecture guides, API references, and practical examples covering both basic usage and advanced scenarios.