Pyright

Visit Website

Introduction

Pyright is a full-featured, standards-based static type checker for Python from Microsoft. It is designed for high performance on large source bases and powers type checking in the Pylance extension for VS Code.

It supports recent typing features quickly, infers types for unannotated code, and offers modes from basic to strict. Configuration lives in pyrightconfig.json or pyproject.toml. A CLI runs it in CI, and watch mode gives fast incremental feedback.

In the quality loop Pyright is a fast type gate for Python, an alternative to mypy.

The source code is at microsoft/pyright on GitHub under the MIT licence, with about 15,700 stars; the most recent commit was on 10 November 2026.

Features

1. Fast checking: Built for large codebases.
2. Type inference: Infers types for unannotated code.
3. Strictness modes: basic, standard and strict.
4. Language server: Editor integration.
5. Watch mode: Incremental re-checks.
6. New typing features: Rapid support for typing PEPs.

Pros

1. Speed: Very fast feedback.
2. Free to use: Open source under the MIT licence, so the core tool costs nothing to use.
3. Actively maintained: The repository had commits as recent as 10 November 2026.
4. Community: About 15,700 GitHub stars.

Cons

1. Node.js runtime: Distributed via npm, though pip wrappers exist.
2. Different from mypy: Results can differ on edge cases.
3. Plugin model: No plugin system like mypy’s.

Usage and Links (Example)

npm install -g pyright
pyright --outputjson src/

Resources:

• Pyright website
• GitHub repository

Pricing

Pyright is free and open source under the MIT licence.

Recommended for?

1. Large Python codebases wanting fast type checks.
2. VS Code users aligning CI with Pylance.

Conclusion

Pyright is a fast, standards-focused type checker for Python.

Use it where speed and new typing features matter most.

On CheckOps, Pyright is filed under the Release & CI gates stage. Related tools listed here include Ruff, Pylint, mypy, Bandit, pre-commit and SonarQube. Before standardising on one, compare recent maintenance activity, the pricing model as your usage grows, and the integrations you rely on today. Information on this page was verified against the official website, documentation and repository on 11 November 2026.