datascore
ML readiness scoring for tabular datasets.
Point it at a DataFrame and get a structured report telling you whether your data is ready for ML training — and if not, exactly why and in what order to fix it.
Install
pip install datascore
Usage
import seaborn as sns
from datascore import score
df = sns.load_dataset("titanic")
report = score(df, target="survived")
report.show()
datascore infers classification versus regression from the target. For
ambiguous integer targets, pass task="classification" or
task="regression" explicitly.
Output
datascore Report
Rows: 891 | Features: 15 | Target: survived
Score: 45/100 — NOT READY
BLOCKERS
- age: 19.9% missing values
- deck: 77.2% missing values
WARNINGS
- Missing values detected: 6.5% overall
- 107 duplicate rows detected
- High skew in sibsp: 3.6891
- High skew in parch: 2.7445
- High skew in fare: 4.7793
INFO
- Outliers in age: 11 rows
- Outliers in sibsp: 46 rows
- Outliers in parch: 213 rows
- Outliers in fare: 116 rows
- No constant features detected
- No infinite values detected
- Class balance: 62/38
Save report to markdown
report.save("report.md")
What it checks
| Category | Checks |
|---|---|
| Completeness | Missing values, high missing rate per column (>5%) |
| Integrity | Duplicate rows, constant features, infinite values |
| ML Readiness | Class imbalance, target leakage risk, high cardinality categoricals |
| Distribution | Skew per numerical column, outliers via IQR |
Scoring
Starts at 100. Each blocker deducts 15 points, each warning deducts 5.
| Score | Verdict |
|---|---|
| 80–100 | READY |
| 50–79 | NEEDS WORK |
| 0–49 | NOT READY |
Why not Great Expectations or Pandera?
Those tools validate data against rules you define upfront.
datascore requires no configuration — it tells you what the problems are without you having to know what to look for first.
Assessment, not validation.
License
MIT
Release files for datascore 0.2.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| datascore-0.2.1.tar.gz | 8.4 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| datascore-0.2.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 16.3 kB
Release files / datascore-0.2.1.tar.gz
| Download URL | datascore-0.2.1.tar.gz |
|---|---|
| Size | 8.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
cd4c887b3a3e5718f08abe1d96bc5f0d719e62cee443220c0b846bb215eee71e
|
|
BLAKE2b-256 checksum How to use checksums |
99af3254e0621c6dcac567869be3212e7f98e616db1f0e9ccde48b481cc9d16c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Sep 24, 2026.
Transparency logRelease files / datascore-0.2.1-py3-none-any.whl
| Download URL | datascore-0.2.1-py3-none-any.whl |
|---|---|
| Size | 7.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
4ec705dfb786d84df1a42b795cbf921a54f1d202c714b329ae184d6763a07130
|
|
BLAKE2b-256 checksum How to use checksums |
87087ccb5cdd9cb7d704c8ac7744e45b1c553ed574bdab503f23da56f024ea2d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Sep 24, 2026.
Transparency log