pydebt
Measurable technical debt for Python. Counts markers, complexity signals, and compares against a committed baseline so CI fails when debt grows.
Install
pip install pydebt
Usage
# snapshot current state
pydebt baseline
# summarize
pydebt scan
pydebt scan --json --top 20
# compare to baseline (exit 1 if worse)
pydebt check
# allow growth, just report
pydebt check --allow-growth
# full report
pydebt report
What it counts
| Kind | Source |
|---|---|
TODO FIXME HACK XXX |
comments (uppercase convention) |
TYPE_IGNORE |
# type: ignore in comments |
NOQA |
# noqa in comments |
NO_COVER |
# pragma: no cover in comments |
EXCEPT_PASS |
except: with only pass |
LONG_FUNCTION |
function > 50 lines |
LONG_FILE |
file > 500 lines |
CI
- run: pip install pydebt
- run: pydebt check
Baseline
.pydebt.json is committed. It stores per-file line count and per-kind marker
counts. check diffs current against it and fails on net growth.
Development
pip install -e ".[dev]"
pytest
ruff check src tests
mypy src
License
MIT
1 maintainer
Metadata
1 maintainer
Release files for pydebt 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| pydebt-0.1.0.tar.gz | 8.7 kB | With provenance | Details for pydebt-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| pydebt-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for pydebt-0.1.0-py3-none-any.whl |
Total release size: 17.2 kB
Release files / pydebt-0.1.0.tar.gz
| Download URL | pydebt-0.1.0.tar.gz |
|---|---|
| Size | 8.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
26417971b66fd215fe579b3fab5aa1bdb130c0c44cec531b2bef6b4ec629a53e
|
|
BLAKE2b-256 checksum How to use checksums |
ba662c33b5b35b4cd62a6268cc78806694c7b0e82ed7aa9e6503f2165f05f8a1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 13, 2026.
Transparency logRelease files / pydebt-0.1.0-py3-none-any.whl
| Download URL | pydebt-0.1.0-py3-none-any.whl |
|---|---|
| Size | 8.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
7ac0afb5b23fe840306206fef3daa664f981c2125a6b110671fbe39bf207fd0f
|
|
BLAKE2b-256 checksum How to use checksums |
d5b8fb321d620e22ef2da1d5d2d5875805d302e9946d79b21266b1cd9ff335e7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 13, 2026.
Transparency logSecurity for pydebt 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for pydebt-0.1.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 13, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
