SeeRepo
Draw my repo

What is great_expectations built with?

great_expectations is a Python repo built with Flask and pyspark. It stores its data in Postgres, reaches it with SQLAlchemy, signs people in with azure-identity, azure-keyvault-secrets, and cryptography, uses AI through datasets, TensorFlow, prophet, scikit-learn, and langid, makes its content with myst-parser, openpyxl, pdf2image, pytesseract, xlrd, and 4 more, validates its data with great-expectations, marshmallow, barcodenumber, jsonschema, and Pydantic, is tested with pytest-benchmark, pytest-cov, pytest-order, pytest-random-order, pytest-split, and 9 more, deploys with boto3, and uses azure-storage-blob, feather-format, gcsfs, oracledb, psycopg2-binary, and 10 more. It has 366,832 written lines, with 582 test files.

Read on November 11, 2026, at commit a3e335b. Read it as markdown

The card says what it's built with. Its whole map opens it up: every part of the code and how it connects to the rest.

Frontend

Styles 1

  • pydata-sphinx-theme

Interface 2

Backend

Data 16

4 more

Data access 1

Sign-in 3

AI 5

Support

The base 2

Content 9

Validation 5

Testing 14

  • Pytest376 files
  • pytest-mock31 files
  • pytest-timeout1 file
  • pytest-cov
  • pytest-order
  • pytest-xdist
  • moto5 files
  • freezegun4 files
  • pyfakefs3 files
  • flaky1 file
  • pytest-benchmark
  • pytest-random-order
2 more
  • pytest-split
  • responses

Deploy 1

Tools 22

  • click2 files
  • Cookiecutter1 file
  • Setuptools1 file
  • coverage
  • Jupyter
  • jupyterlab
  • pandas-stubs
  • pre-commit
  • Ruff
  • Sphinx
  • sphinxcontrib-applehelp
  • sphinxcontrib-devhelp
10 more
  • sphinxcontrib-htmlhelp
  • sphinxcontrib-qthelp
  • sphinxcontrib-serializinghtml
  • typing-extensions47 files
  • packaging10 files
  • docstring-parser1 file
  • invoke1 file
  • mypy
  • twine
  • wheel

Other 30

  • pandas88 files
  • NumPy43 files
  • python-dateutil21 files
  • SciPy12 files
  • ruamel.yaml11 files
  • GeoPandas9 files
  • geopy2 files
  • tqdm2 files
  • ephem1 file
  • pypd1 file
  • SymPy1 file
  • dnspython
18 more
  • googleapis-common-protos
  • shapely14 files
  • requests8 files
  • tomli3 files
  • pycountry2 files
  • arxiv1 file
  • holidays1 file
  • orjson1 file
  • phonenumbers1 file
  • price-parser1 file
  • pyparsing1 file
  • pytz1 file
  • tzlocal1 file
  • user-agents1 file
  • grpcio
  • grpcio-status
  • rtree
  • zstandard

Other repos with a similar stack

Ordered by how much of its stack they share with great_expectations, then by stars.

Frequently asked questions

What language is great_expectations written in?
great_expectations is written in Python, with 366,832 written lines.
What framework does great_expectations use?
great_expectations is built with Flask and pyspark.
What database does great_expectations use?
great_expectations stores its data in Postgres and reaches it with SQLAlchemy.

The proof: great_expectations/compatibility/postgresql.py, line 1

What does great_expectations sign people in with?
great_expectations signs people in with azure-identity, azure-keyvault-secrets, and cryptography.
Does great_expectations use AI?
Yes. great_expectations uses AI through datasets, TensorFlow, prophet, scikit-learn, and langid.
What services does great_expectations use?
great_expectations uses azure-storage-blob, feather-format, gcsfs, oracledb, psycopg2-binary, pyhive, pymysql, snowflake-sqlalchemy, clickhouse-sqlalchemy, teradatasqlalchemy, pandas-gbq, pyarrow, pyathena, pyodbc, and Trino.
Does great_expectations have tests?
Yes. great_expectations has 582 test files and is tested with pytest-benchmark, pytest-cov, pytest-order, pytest-random-order, pytest-split, pytest-xdist, responses, Pytest, pytest-mock, moto, freezegun, pyfakefs, flaky, and pytest-timeout.
Which repos have a stack like great_expectations's?
The ones that share most of its stack:ray-project/rayrun-llama/llama_indexapache/superset

See inside your code, today.

Paste your repo and see it drawn, part by part: a medium one in under a minute.

Free, no account.

Or look inside SeeRepo's own →

Is it your repo? Add its badge, keep it up to date or take it down →