great-expectations/great_expectations
Grade a repo

93

/ 100

GradeA

Excellent work. The main thing left to polish is dependency metadata.

Top 8% of 5,156 graded repos

Always know what to expect from your data.

Documentation96
Engineering93
Health88
Python11,682Apache-2.08d ago

Top fixes

Highest-impact changes first, ranked by point weight

13 to address
  1. 1
    CI/CD14pt

    Add a lint step to catch style issues automatically.

  2. 2
    CI/CD14pt

    Add `tsc --noEmit`, `mypy`, or `cargo check` to catch type errors before they merge.

  3. 3
    CI/CD14pt

    Upload coverage to Codecov, Coveralls, or report it with `--coverage` flags.

  4. 4
    Reproducibility6pt

    Add .github/dependabot.yml with at least one package-ecosystem entry so dependencies are updated automatically.

Working through the fixes? Let every push regrade itself.

The free GitHub App rescans this repo on every push and posts the grade as a commit check, so the score climbs without coming back to rescan by hand.

Install the GitHub App

Scorecard

Every check, grouped by category and sorted worst-first

Documentation

96

Contributing guide5pt72

Contributing guide is detailed and thorough.

README12pt100

README is present.

Install and run instructions9pt100

README documents how to install the project.

License6pt100

Licensed under Apache-2.0.

Engineering

93

Reproducibility6pt80

Lockfile present (requirements.txt). Installs are reproducible.

CI/CD14pt85

CI is configured (.github/workflows/ci.yml).

Tests18pt100

Test files detected (.github/actions/cla-status/decide.test.js).

Linting and formatting5pt100

Linter or formatter configured (contrib/ruff.toml).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

88

Dependency manifest6pt62

Dependency manifest found (pyproject.toml).

Repository metadata5pt100

Repository has a description.

Activity5pt100

Actively maintained (pushed within the last month).

Housekeeping3pt100

.gitignore present.

Repository health signals

Activity, community, and responsiveness at scan time

Activity

  • 55 / 105
    Commits (30d / 90d)
  • 1,788
    Forks
  • 347
    Releaseslatest 7y ago

Community

  • 87% - Good
    Community health
  • 6 bus factor
    authors own >50% of commits
  • 11,682
    Watchers

Responsiveness

  • <1h
    Median issue response
  • 1d 22h
    Median PR merge time
  • 37
    Open issues
Repository files39 root entries
  • .github
    Good: Test files detected (.github/actions/cla-status/decide.test.js).
    Good: CI is configured (.github/workflows/ci.yml).
    Good: Issue or PR templates present.
  • assets
    Good: Environment pinned via assets/docker/clickhouse/docker-compose.yml.
  • ci
  • contrib
    Good: Linter or formatter configured (contrib/ruff.toml).
  • docs
  • great_expectations
  • reqs
  • scripts
  • tests
  • .clabot
  • .coderabbit.yaml
  • .git-blame-ignore-revs
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • .pre-commit-config.yaml
  • .readthedocs.yml
  • AGENTS.md
  • CITATION.cff
  • CLA.md
  • CODE_OF_CONDUCT.md
    Good: Code of conduct present.
  • CODEOWNERS
  • constraints-dev.txt
  • CONTRIBUTING_CODE.md
  • CONTRIBUTING_WORKFLOWS.md
  • CONTRIBUTING.md
    Good: Contributing guide is detailed and thorough.
    Issue: Contributing guide lacks a setup section (−12 pts).Fix: Show new contributors how to get a local dev environment running.
    Issue: Contributing guide lacks a code style section (−8 pts).Fix: Describe your linting/formatting rules and how to run them.
    Issue: Contributing guide lacks a testing section (−8 pts).Fix: Show contributors how to run the test suite (e.g. npm test, pytest, cargo test).
    Good: Contributing guide describes the PR/review workflow.
    Issue: Contributing guide has no code examples (−5 pts).Fix: Add code blocks showing example commands for setup, running tests, and submitting a PR.
  • DEVELOPMENT.md
  • LICENSE
    Good: Licensed under Apache-2.0.
  • lychee.toml
  • MANIFEST.in
  • pyproject.toml
    Good: Dependency manifest found (pyproject.toml).
  • README.md
    Good: README is present.
    Good: README is well structured with multiple sections.
    Good: README includes screenshots or visuals. Great for first impressions.
    Good: README has code examples.
    Good: README links to a live demo or deployed app.
    Good: README includes status badges.
    Good: README documents how to install the project.
    Good: README documents how to run the project.
  • requirements-dev.txt
  • requirements-types.txt
  • requirements.txt
    Good: Lockfile present (requirements.txt). Installs are reproducible.
  • SECURITY.md
    Good: Security policy present.
  • setup.cfg
  • setup.py
  • tasks.py
  • versioneer.py
RepoGrade badge preview

Add this badge to your README

It updates automatically each time the repo is re-graded.

[![RepoGrade](https://www.repo-grade.com/api/badge/great-expectations/great_expectations)](https://www.repo-grade.com/report/great-expectations/great_expectations)

More graded Python repos