doc-quality
Document quality profiler for ML pipelines. Score, deduplicate, and validate your corpus before embedding. Zero mandatory dependencies.
Install
pip install corpus-quality
The problem
Most RAG failures start at ingestion -- when nobody checked whether the documents were actually clean before embedding them. Teams spend days tuning chunk sizes and prompt templates when the real problem is that 20% of their corpus is failed PDF extractions, near-duplicates, or wall-of-text that will split badly at any chunk boundary.
doc-quality runs before any of that.
Quick start
from doc_quality import CorpusProfiler
profiler = CorpusProfiler(corpus_name="my_rag_corpus")
report = profiler.profile_directory("./documents/")
print(report.summary())
=== DOC-QUALITY -- CORPUS QUALITY REPORT ===
Documents: 47
Pass: 34
Warn: 9
Fail: 4
Pass rate: 72%
Avg score: 74.2/100
Duplicates: 6 pairs
Recommended chunking: recursive
Single document
from doc_quality import DocumentProfiler
profiler = DocumentProfiler()
profile = profiler.profile(text, name="annual_report.pdf")
print(profile.quality_score) # 83.4
print(profile.quality_level) # QualityLevel.PASS
print(profile.boilerplate_ratio) # 0.18
print(profile.chunk_risk_score) # 0.22
print(profile.issues)
Near-duplicate detection (no embeddings needed)
from doc_quality import find_duplicates
pairs = find_duplicates({"doc_a.txt": text_a, "doc_b.txt": text_b}, threshold=0.85)
for pair in pairs:
print(pair)
# DuplicatePair('policy_v1.txt' <-> 'policy_v1_copy.txt', EXACT)
Data card for model cards and papers
print(report.data_card.to_markdown())
CLI
doc-quality profile report.txt
doc-quality corpus ./documents/ --name "my_corpus"
doc-quality corpus ./documents/ --data-card
doc-quality deduplicate ./documents/
doc-quality corpus ./documents/ --json
Quality dimensions scored
| Dimension | Weight | Detects |
|---|---|---|
| Encoding | 25% | Replacement chars, mojibake |
| Text density | 20% | Whitespace-heavy extractions |
| Uniqueness | 20% | Repeated lines, template noise |
| Sentences | 15% | List dumps, failed extractions |
| Boilerplate | 10% | Headers, footers, disclaimers |
| Table integrity | 5% | Malformed table structure |
| Chunk boundary risk | 5% | Wall-of-text, no split points |
Pipeline position
doc-quality (profile) -> chunk-bench (benchmark) -> rag-eval-kit (evaluate)
Metadata
Release files for corpus-quality 1.0.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| corpus_quality-1.0.0.tar.gz | 15.7 kB | With provenance | Details for corpus_quality-1.0.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| corpus_quality-1.0.0-py3-none-any.whl | Python 3 | none | any | Details for corpus_quality-1.0.0-py3-none-any.whl |
Total release size: 30.6 kB
Release files / corpus_quality-1.0.0.tar.gz
| Download URL | corpus_quality-1.0.0.tar.gz |
|---|---|
| Size | 15.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3ba5dac7fb0e425b0fd222c59527045b86b8c7c0f9295b88fb4740d049e13104
|
|
BLAKE2b-256 checksum How to use checksums |
f07632c77e4d17c75b91301dfb3fdec7131f4e4408fc25287306195b77cb955b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Apr 12, 2026.
Transparency logRelease files / corpus_quality-1.0.0-py3-none-any.whl
| Download URL | corpus_quality-1.0.0-py3-none-any.whl |
|---|---|
| Size | 14.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
590c13a2ae325c89e2de4e9467b393a6a6fbc7b3db46d7bda740d94e97c54515
|
|
BLAKE2b-256 checksum How to use checksums |
4d3a95a2a2f4e12db73cbe88ce160cfdb3d6d66b5efa786a47a6f96d245f8e1c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Apr 12, 2026.
Transparency logSecurity for corpus-quality 1.0.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for corpus_quality-1.0.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Apr 12, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.