huggingface/datatrove

Freeing data processing from scripting madness by providing a set of platform-agnostic customizable pipeline processing blocks.

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 12 minutes ago
Added to GitGenius on September 20th, 2026
Created on June 14th, 2023
Open Issues & Pull Requests: 105 (+0)
GitHub issues: Enabled
Number of forks: 303
Total Stargazers: 3,342 (+0)
Total Subscribers: 49 (+0)

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 51
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 536 days
Stale 30+ days: 48
Stale 90+ days: 44

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • enhancement (2)

Detailed Description

Datatrove is a Python library that provides platform-agnostic customizable pipeline processing blocks for data processing workflows.

The library addresses the complexity of building scalable data processing pipelines by offering reusable, composable blocks that can be combined into workflows. Rather than writing custom scripts for each data processing task, developers define pipelines using these standardized blocks, which handle common operations like filtering, transformation, and aggregation. The platform-agnostic design means pipelines can run on different execution backends without modification, abstracting away infrastructure concerns from pipeline logic.

Datatrove suits teams building data processing systems at scale, particularly those working with large datasets where pipeline reusability and maintainability matter. It is especially valuable for machine learning workflows where data preparation is a critical bottleneck. The library works well for organizations that need to run the same pipelines across different compute environments or want to reduce boilerplate in data engineering code. Projects that involve repeated data transformations, filtering, or preparation benefit from the ability to compose and reuse pipeline blocks rather than rewriting similar logic across multiple scripts.

The project shows consistent development activity with regular updates to its codebase. The maintainers actively address issues and incorporate contributions from the community. The library receives ongoing enhancements to its block implementations and pipeline execution capabilities. Development appears focused on expanding the ecosystem of available processing blocks and improving the flexibility of the pipeline execution framework.