treeverse/lakeFS

lakeFS - Data version control for your data lake | Git for data

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 9 minutes ago
Added to GitGenius on September 12th, 2026
Created on September 12th, 2019
Open Issues & Pull Requests: 441 (+0)
GitHub issues: Enabled
Number of forks: 476
Total Stargazers: 5,523 (+0)
Total Subscribers: 41 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 4.3 hours
Mean response time: 62.7 days
90th percentile: 203.0 days
Tracked items: 778

How this project is maintained

Around half of the issues opened in the past year never receive a reply. 99% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Work labelled "docs" is answered fastest, typically in under an hour, while "no stale" waits about 3 months. 78% of tracked open issues have had no activity in three months, so the open count overstates what is actively being worked. Only 10% of issues opened in the past year have been closed.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 189
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 587 days
Stale 30+ days: 185
Stale 90+ days: 168

Recent activity

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

Top labels

  • bug (233)
  • contributor (188)
  • feature-request (122)
  • good first issue (115)
  • P2 (83)
  • area/UI (75)
  • tech-debt (63)
  • P3 (58)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

lakeFS is a data version control system that transforms object storage into a Git-like repository for managing data lakes.

The tool addresses the challenge of safely testing and managing changes to data lakes without risking production data integrity. It works by layering version control semantics on top of object storage services, enabling developers to create isolated branches that appear as full copies of production data without requiring actual data duplication. This approach allows ETL jobs, transformations, and analytics to be tested in isolated environments before being merged into production, similar to how code branches work in Git. The system is API-compatible with S3, meaning it integrates transparently with existing data frameworks and tools.

Teams should adopt lakeFS if they operate data lakes on AWS S3, Azure Blob Storage, or Google Cloud Storage and need to safely test pipeline changes before production deployment. It suits organizations running complex ETL jobs, data science workflows, or analytics that require reproducibility and isolation. The tool works seamlessly with modern data frameworks including Spark, Hive, AWS Athena, DuckDB, and Presto, making it practical for teams already invested in these ecosystems.

The project maintains active test coverage across multiple dimensions, including Go unit tests, Node tests, and integration tests. Development activity shows consistent attention to code quality and system reliability through comprehensive automated testing infrastructure.