Disclosure signals
The auditor looks for concrete documentation signals, not polished section names.
A documentation preflight for synthetic datasets
Show your work before you ship the data.
Find missing provenance, generator settings, privacy assessment, quality controls, licensing, limitations, and contamination disclosures.
No uploadNo model callNo score of data quality
01
Input
Dataset card Markdown
Analysis stays in this tab. Fenced code examples do not count as evidence.
Choose documentation areas
02
Report
Documentation coverage
Ready to audit
Paste a card or load the sample to inspect ten areas.
How to read the report
Evidence found is not a claim verified.
Actionable gaps
Each missing area names the evidence still needed and suggests what to add.
Human judgment
A complete card can still describe unsafe or low-quality data. Review the substance.