FAIRy

Report Gallery

Explore real FAIRy validation reports from different repositories and data types. See what fails, why it matters, and how to fix it.

Each report below shows actual validation results from FAIRy rulepacks. These examples demonstrate common issues researchers encounter when preparing datasets for submission. Click any report to view the full details.

Start here

Rulepacks based on community feedback — examples inspired by common issues

GEO bulk sequencing submission

Repository: GEO (Gene Expression Omnibus)
Rulepack: geo_bulk_seq v0.2.2
Last updated:
Bulk RNA-seq
1 FAIL · 1 WARN · 15 checks run
Who this is for: Researchers submitting bulk RNA-seq data to GEO
❌ What failed
  • GEO.BIO.CONTEXT_MISSING - Sample does not provide tissue/cell_line/cell_type
⚠️ Warn
  • CORE.DATE.INVALID_ISO8601 - Date value is not in ISO8601 format (YYYY-MM-DD)
🔧 How to fix
  • Fill at least one of: tissue, cell_line, or cell_type fields in your sample metadata
  • Use ISO8601 date format (YYYY-MM-DD), e.g., 2025-10-02 (optional)
View full report →
Showing 0 of 1 reports

No reports match the selected filters.

Services & Licensing

Free for academic use

FAIRy-core is available free for academic and non-commercial use. Get started with starter templates and common rulepacks.

Get FAIRy-core on GitHub →

Guided pilot (paid)

We encode your institution's intake rules and deliver a readiness report + attestation. Custom rulepacks for your repository.

Request a pilot scope →
Note: The reports shown in this gallery are examples generated from test fixtures. They demonstrate common validation scenarios but do not represent actual user data. All reports are generated locally and no data is transmitted to external servers.

Ready to validate your dataset?

Run FAIRy locally on your data and get a detailed readiness report before submission.

Try FAIRy nowView documentation