awslabs/deequ
This system is a data quality and profiling library for Apache Spark, designed to verify data integrity, compute statistical metrics, and enforce constraints. It provides a fluent API for building and executing data analysis workflows, including column profiling, anomaly detection, and row-level quality checks. The system supports persistent storage of analysis results and integrates with the Glue DQDL format for rule definition.
63.3
Adequate · 3 August 2026
22k
lines of production code
Scala
primary language
7
bus factor · 85 authors in all
3
measurements over time
How it got here
2018 · Fluent API and storage enhancements
This period focused on introducing fluent builder APIs for data verification, analysis, and constraint suggestions, significantly improving the developer experience. It also expanded storage capabilities by adding in-memory and file-system-based metrics repositories, alongside new statistical functions and Spark 3.5 compatibility.
12 changes
2019–2026 · DQDL integration and analysis extensions
This period focused on expanding Deequ's capabilities by introducing a DQDL-based evaluation framework that supports row-level data quality checks and complex rule translation. Concurrently, the project added new analytical tools, including KLL sketch support for quantiles, data comparison utilities, and a codebase knowledge base generator.
8 changes
Survey your own repository
awslabs/deequ was measured the same way every project in this corpus was: the same rubric, at a pinned commit, with the result published in full. Point the surveyor at a repository you know and see whether you agree with it.
About this page
- The description of this project is derived from its own commit history, not from its README.
- The score is its highest published measurement, taken on 3 August 2026 at a pinned commit. It is not a live figure and does not change until the project is measured again.
- Measured at commit 76a47e5b6a — the exact code this score is about.
- Scored under rubric rubric-2026.08.18. Score the same commit under that rubric and you get the same number.