mypy_baseline
Integrate mypy with existing codebase.
Decision gist · record as of 2026-08-14
Yes. If you want to adopt mypy on an existing project without the friction of fixing all pre-existing errors first, this is the right tool. It has no dependencies, low friction, active maintenance, permissive licensing, and solves a real adoption problem. Install it if incremental type-checking adoption is your goal.AI-flagged interpretation of the facts on this page — verify before relying
Before you install
- Requires Python 3.9 or later and mypy installed separately.
- Low install friction; pure Python with no runtime dependencies.
- Active maintenance with recent commits and stable production status.
License · maintenance · safety
permissive license (permissive) — MIT license (permissive); you can use, modify, and distribute freely with minimal restrictions.
last release 2026-04-13 (123 days) · last repo commit 2026-04-13 · 82 stars
0 known vulnerabilities (OSV.dev, 2026-08-14) · 693,611 downloads/mo, #5,315 on PyPI
Alternatives
Verify before relying
pip install mypy-baseline
# Generate baseline from current mypy output
mypy | mypy-baseline sync
# On subsequent runs, filter to show only new errors
mypy | mypy-baseline filter- Whether the tool works with all mypy versions or has specific version constraints.
- How baseline merge conflicts are actually avoided in practice across team workflows.
- Performance characteristics when applied to very large codebases.
What it is and what it does
mypy-baseline is a CLI wrapper around mypy that lets you adopt type checking incrementally on an existing project without being overwhelmed by pre-existing violations. On first run, it records all current mypy errors into a human-readable baseline file; on subsequent runs, it filters mypy's output to show only new errors you've introduced, ignoring everything already in the baseline. This lets teams gradually improve type coverage without having to fix all historical violations at once.
The tool works by parsing mypy's stdout—no patching or monkey-patching involved—and can track which specific errors were resolved versus newly introduced, even within the same file. It supports filtering by error category and regex patterns to suppress false positives from buggy plugins, and generates progress stats to show your team's improvement over time.
Use it for
- Adopting mypy on a large legacy codebase without requiring all existing type errors to be fixed first.
- Enforcing that new code passes type checking while allowing old code to remain untyped.
- Tracking team progress on type annotation coverage with visual stats and git history.
- Suppressing false positives from third-party mypy plugins that don't affect your actual code.
- Reviewing PRs to see exactly which type errors were introduced versus resolved in that change.
Worth the install?
AI-flagged interpretation of the facts on this page. Verify before relying on it.
Yes.
If you want to adopt mypy on an existing project without the friction of fixing all pre-existing errors first, this is the right tool. It has no dependencies, low friction, active maintenance, permissive licensing, and solves a real adoption problem. Install it if incremental type-checking adoption is your goal.
Install
mypy-baseline on PyPI
Before you install
Low install friction; pure Python with no runtime dependencies. Active maintenance with recent commits and stable production status.
Requires Python 3.9 or later and mypy installed separately.
License in practice
MIT license (permissive); you can use, modify, and distribute freely with minimal restrictions.
Quickstart
pip install mypy-baseline
# Generate baseline from current mypy output
mypy | mypy-baseline sync
# On subsequent runs, filter to show only new errors
mypy | mypy-baseline filterVerify before relying
- Whether the tool works with all mypy versions or has specific version constraints.
- How baseline merge conflicts are actually avoided in practice across team workflows.
- Performance characteristics when applied to very large codebases.
Package facts
| License | permissive license permissive |
| Python support | Supports the current Python release >=3.9 |
| Install friction | Low. Pure-Python wheel |
| Runtime dependencies | None |
| Maintenance | Actively maintained 123 days since the last release |
| Last repo commit | |
| First released | |
| Downloads | 693,611 / month, #5,315 on PyPI 30-day window, as of 2026-08-14 |
| Known vulnerabilities | None known OSV.dev, checked 2026-08-14 |
| Classifiers | Development Status :: 5 - Production/StableIntended Audience :: DevelopersLicense :: OSI Approved :: MIT LicenseProgramming Language :: PythonTyping :: Typed |
Evidence: mypy_baseline-0.7.4-py3-none-any.whl
Tags
Let your AI agent find packages like this
Example. Real query, live index.
You found this page by searching. An agent finds it by wishing: SkillFed indexes 14,416 PyPI packages by what they can do, searchable in plain language.
wish › “mypy baseline integration”
- mypy_baselineA CLI tool that captures mypy type errors as a baseline on first run,…
- pybaselinesProvides 50+ baseline correction algorithms for experimental data…
- pytest-regressionsProvides pytest fixtures for writing regression tests that compare…
Give your agent the search over MCP, or paste the wish link into any chat.
More Quality Assurance packages
Coverage.py measures which lines of Python code are executed during test runs, reporting coverage percentages and identifying untested code paths.
Install it if you want to measure test completeness or enforce coverage thresholds in your project.
Ruff is a Python linter and code formatter written in Rust that combines linting, formatting, and code fixing into a single tool, replacing Flake8, Black, isort, and related utilities.
Pexpect spawns and controls interactive console applications by sending input and matching output patterns, automating tasks that would otherwise require manual interaction.
Black reformats Python source code to a consistent style by parsing entire files and rewriting them according to an opinionated, deterministic set of rules, eliminating manual formatting decisions.
pytest-xdist distributes pytest tests across multiple CPU cores or machines to speed up test execution, with the simplest usage being `pytest -n auto` to spawn workers equal to available CPUs.
Install it if your test suite takes long enough that parallelization would save meaningful time.
Validates AWS CloudFormation templates in YAML or JSON format against resource provider schemas and best practices, checking property values and configuration correctness.
Install it if you work with CloudFormation templates.
See also igittigitt · pybaselines · pytest-pylint · ydiff · uncalled · detect-secrets · nb-clean · bc-detect-secrets · refurb · mypy-strict-kwargs