darglint
A utility for ensuring Google-style docstrings stay up to date with the source code.
Decision gist · record as of 2026-08-14
Yes, if you need docstring validation and accept maintenance-mode status. The tool is stable, has no dependencies, and works reliably for its core purpose. Install it if your team uses Google, Sphinx, or Numpy docstring styles and wants automated checks for documentation accuracy. Do not expect new features or rapid bug fixes; evaluate whether the current feature set meets your needs before adopting.AI-flagged interpretation of the facts on this page — verify before relying
Before you install
- Requires Python 3.6 or later; configuration file (.darglint, setup.cfg, or tox.ini) with [darglint] section needed for non-default behavior.
- Low install friction with no runtime dependencies.
- However, the project is in maintenance mode with no active development—the maintainer no longer works with Python regularly and unlikely to add significant new features, though pull requests are accepted.
License · maintenance · safety
MIT (permissive) — MIT license is permissive, allowing use in both open-source and commercial projects with minimal restrictions.
last release 2021-10-18 (1761 days)
0 known vulnerabilities (OSV.dev, 2026-08-14) · 570,518 downloads/mo, #5,955 on PyPI
Alternatives
Verify before relying
pip install darglint
# Check a single file
darglint myfile.py
# Check all Python files in a directory
find . -name "*.py" | xargs darglint- Whether the tool integrates with modern linting workflows (flake8, pre-commit) beyond what the description excerpt covers.
- Current state of compatibility with Python 3.10+ despite classifier support only through 3.9.
- Whether configuration via .darglint, setup.cfg, or tox.ini still works reliably in current tooling ecosystems.
What it is and what it does
Darglint is a linter that validates whether docstrings accurately describe the functions and methods they document. It parses docstrings in Google, Sphinx, or Numpy style and compares them against the actual code—checking that documented parameters, return types, exceptions, and yields match what the implementation actually does. The tool runs from the command line and can be configured to ignore specific errors, adjust strictness levels (short/long/full), and customize error message formats.
The project is currently in maintenance mode: the original maintainer no longer works with Python regularly and is not adding significant new features, though bug fixes and pull requests are still accepted. It has no runtime dependencies, making installation straightforward. The tool is useful for teams that want to enforce documentation accuracy as part of their code quality pipeline, though ongoing maintenance and feature development should not be expected.
Use it for
- Enforce that docstrings document all function parameters and return values before code review.
- Catch outdated docstrings when function signatures change during refactoring.
- Validate exception documentation matches the actual exceptions a function can raise.
- Integrate into CI/CD pipelines to fail builds when docstrings drift from implementation.
- Configure strictness levels to allow simple one-liners while fully checking complex functions.
Worth the install?
AI-flagged interpretation of the facts on this page. Verify before relying on it.
Yes, if you need docstring validation and accept maintenance-mode status.
The tool is stable, has no dependencies, and works reliably for its core purpose. Install it if your team uses Google, Sphinx, or Numpy docstring styles and wants automated checks for documentation accuracy. Do not expect new features or rapid bug fixes; evaluate whether the current feature set meets your needs before adopting.
Install
darglint on PyPI
Before you install
Low install friction with no runtime dependencies. However, the project is in maintenance mode with no active development—the maintainer no longer works with Python regularly and unlikely to add significant new features, though pull requests are accepted.
Requires Python 3.6 or later; configuration file (.darglint, setup.cfg, or tox.ini) with [darglint] section needed for non-default behavior.
License in practice
MIT license is permissive, allowing use in both open-source and commercial projects with minimal restrictions.
Quickstart
pip install darglint
# Check a single file
darglint myfile.py
# Check all Python files in a directory
find . -name "*.py" | xargs darglint
Verify before relying
- Whether the tool integrates with modern linting workflows (flake8, pre-commit) beyond what the description excerpt covers.
- Current state of compatibility with Python 3.10+ despite classifier support only through 3.9.
- Whether configuration via .darglint, setup.cfg, or tox.ini still works reliably in current tooling ecosystems.
Package facts
| License | MIT permissive |
| Python support | Supports the current Python release >=3.6,<4.0 |
| Install friction | Low. Pure-Python wheel |
| Runtime dependencies | None |
| Maintenance | Abandoned 1,761 days since the last release |
| First released | |
| Downloads | 570,518 / month, #5,955 on PyPI 30-day window, as of 2026-08-14 |
| Known vulnerabilities | None known OSV.dev, checked 2026-08-14 |
| Classifiers | Intended Audience :: DevelopersLicense :: OSI Approved :: MIT LicenseProgramming Language :: Python :: 3Programming Language :: Python :: 3.6Programming Language :: Python :: 3.7Programming Language :: Python :: 3.8Programming Language :: Python :: 3.9Topic :: Software Development :: DocumentationTopic :: Software Development :: Quality Assurance |
Evidence: darglint-1.8.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 › “check docstring accuracy”
- darglintDarglint is a docstring linter that checks whether function and…
- docsigLints Python function and method signatures to ensure their…
- pydoclintPydoclint is a Python docstring linter that validates whether…
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 pydoclint · docsig · sphinxcontrib-napoleon · numpydoc · flake8-rst-docstrings · docstr-coverage · doc8 · docstring-inheritance · flake8-docstrings · sphinx-lint