mypy-strict-kwargs
Enforce using keyword arguments where possible.
Decision gist · record as of 2026-08-14
Yes, if your team values consistent call conventions and you already use mypy. Install friction is minimal, maintenance is active, and the plugin solves a real style problem without licensing friction. Not worth installing if you don't use mypy or if your codebase relies heavily on positional arguments to builtins or third-party libraries (though the ignore list mitigates this).AI-flagged interpretation of the facts on this page — verify before relying
Before you install
- Requires mypy to be installed and configured; Python 3.11 or later.
- Low friction: pure Python wheel with only mypy as a runtime dependency.
- Actively maintained with a release 26 days ago; repo is not archived and supports Python 3.11–3.14.
License · maintenance · safety
permissive license (permissive) — MIT License permits unrestricted use, modification, and distribution with minimal legal friction.
last release 2026-07-19 (26 days) · last repo commit 2026-08-14 · 6 stars
0 known vulnerabilities (OSV.dev, 2026-08-14) · 150,724 downloads/mo, #10,957 on PyPI
Alternatives
Verify before relying
pip install mypy-strict-kwargs
# Add to pyproject.toml:
# [tool.mypy]
# plugins = ["mypy_strict_kwargs"]
# Then run mypy normally; it will reject add(1, 2) and require add(a=1, b=2)- Whether the plugin works with all mypy versions or has specific version constraints beyond what the fact sheet states.
- Performance impact when enabled on large codebases.
- Interaction with other mypy plugins or type-checking workflows.
What it is and what it does
mypy-strict-kwargs is a mypy plugin that enforces a code-style rule: all function calls must use keyword arguments rather than positional or mixed forms. When enabled, calling a function like `add(1, 2)` will trigger a type error; only `add(a=1, b=2)` is accepted. This is similar in spirit to code formatters like Black—it removes the need to debate call conventions and ensures consistency across a codebase.
The plugin is configured via mypy's standard configuration files (pyproject.toml, mypy.ini, or setup.cfg) and supports an ignore list for functions where keyword arguments are impractical (e.g., builtins like `str()`). It depends only on mypy and has low install friction. The maintainer is active, with recent releases supporting Python 3.11 through 3.14.
Use it for
- Enforce consistent call style across a team codebase to reduce code-review friction over positional vs. keyword arguments.
- Improve error messages from mypy by ensuring named arguments, which report argument name rather than position in type mismatches.
- Gradually migrate a legacy codebase toward keyword-only calls without manual refactoring by catching violations at type-check time.
- Prevent accidental positional-argument bugs when function signatures change and arguments are reordered.
- Standardize on a single call convention for functions with many parameters to improve readability.
Worth the install?
AI-flagged interpretation of the facts on this page. Verify before relying on it.
Yes, if your team values consistent call conventions and you already use mypy.
Install friction is minimal, maintenance is active, and the plugin solves a real style problem without licensing friction. Not worth installing if you don't use mypy or if your codebase relies heavily on positional arguments to builtins or third-party libraries (though the ignore list mitigates this).
Install
mypy-strict-kwargs on PyPI
Before you install
Low friction: pure Python wheel with only mypy as a runtime dependency. Actively maintained with a release 26 days ago; repo is not archived and supports Python 3.11–3.14.
Requires mypy to be installed and configured; Python 3.11 or later.
License in practice
MIT License permits unrestricted use, modification, and distribution with minimal legal friction.
Quickstart
pip install mypy-strict-kwargs
# Add to pyproject.toml:
# [tool.mypy]
# plugins = ["mypy_strict_kwargs"]
# Then run mypy normally; it will reject add(1, 2) and require add(a=1, b=2)Verify before relying
- Whether the plugin works with all mypy versions or has specific version constraints beyond what the fact sheet states.
- Performance impact when enabled on large codebases.
- Interaction with other mypy plugins or type-checking workflows.
Package facts
| License | permissive license permissive |
| Python support | Supports the current Python release >=3.11 |
| Install friction | Low. Pure-Python wheel |
| Runtime dependencies | 1 packagemypy |
| Maintenance | Actively maintained 26 days since the last release |
| Last repo commit | |
| First released | |
| Downloads | 150,724 / month, #10,957 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/StableEnvironment :: Web EnvironmentLicense :: OSI Approved :: MIT LicenseOperating System :: Microsoft :: WindowsOperating System :: POSIXProgramming Language :: Python :: 3 :: OnlyProgramming Language :: Python :: 3.11Programming Language :: Python :: 3.12Programming Language :: Python :: 3.13Programming Language :: Python :: 3.14 |
Evidence: mypy_strict_kwargs-2026.7.19.1-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 plugin keyword arguments”
- mypy-strict-kwargsA mypy plugin that enforces keyword-argument-only calls to functions,…
- strict-kwargsA standalone CLI linter that enforces keyword arguments in Python…
- pytest-cppA pytest plugin that discovers and runs C++ tests from Google Test,…
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 strict-kwargs · pytest-mypy-plugins · flake8-logging-format · classes · coverage-conditional-plugin · flake8-black · pytype · docsig · wemake-python-styleguide · django-stubs