pyre-check vs pytype

Archived Python type analyzers compared

pyre-check and pytype are archived tools for analyzing Python types without running code. pyre-check checks annotations and documents Pysa data-flow analysis, while pytype combines annotations with type inference, including for partially annotated code.

pyre-checkpytype
LanguageOCamlPython
LicenseMITNOASSERTION
Stars7.2k5k
Forks450290
Last analyzedOct 3, 2026Oct 3, 2026

Key differences

  • pyre-check checks Python type annotations in line with PEP 484; pytype combines inline annotations with type inference.
  • pyre-check supports incremental analysis and a daemon for monitoring file changes; pytype is described as static analysis without executing the analyzed program.
  • pyre-check’s repository is archived, with type checking moved to Pyrefly and Pysa maintained separately; pytype is archived with Python 3.12 as its final supported version.
  • pyre-check is implemented in OCaml and targets Python code; pytype is implemented in Python.
  • pyre-check lists an MIT license; pytype lists its license as NOASSERTION, so its licensing information should be reviewed.

Choose pyre-check if you…

  • maintain an existing Pyre configuration or need a reference for a legacy setup.
  • want to understand its incremental type checking or documented Pysa data-flow analysis.
  • are evaluating its stated successor, Pyrefly, for a new type-checking project.
Read the pyre-check analysis →

Choose pytype if you…

  • maintain a project targeting Python 3.12 or earlier.
  • work with partially annotated Python code and want type inference alongside annotations.
  • want static type analysis that does not require running the analyzed program.
Read the pytype analysis →

Compare the numbers side by side, or add more projects

This comparison is generated with AI from the OSRepos analyses of both projects. Always check each project's repository and documentation before choosing.