Pyright-cov
Enforce minimum type coverage!
pyright-cov is a tool which you can use to enforce minimum type coverage in your projects.
Installation
pip install pyright-cov
Usage
In a virtual environment in which you have a local install of a library foo, you can
ensure that foo is type-complete with:
pyright-cov --verifytypes foo --ignoreexternal
This will fail (i.e. exit 1) if your type coverage is less than 100%. To set a lower
threshold, such as 60%:
pyright-cov --verifytypes foo --ignoreexternal --fail-under 60
To exclude symbols whose names match a given (glob) pattern, use --exclude-like, for example:
pyright-cov --verifytypes foo --ignoreexternal --exclude-like "*.tests.*"
Additional command-line flags are passed to Pyright.
Used by
Testing
Make sure you have uv and pytest installed. Then, run:
pytest tests
Metadata
Release files for pyright-cov 0.2.2
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 |
|---|---|---|---|---|
| pyright_cov-0.2.2.tar.gz | 3.5 kB | With provenance | Details for pyright_cov-0.2.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| pyright_cov-0.2.2-py3-none-any.whl | Python 3 | none | any | Details for pyright_cov-0.2.2-py3-none-any.whl |
Total release size: 7.4 kB
Release files / pyright_cov-0.2.2.tar.gz
| Download URL | pyright_cov-0.2.2.tar.gz |
|---|---|
| Size | 3.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
705790d5858bd5bd8c233dd85a7d5e7a7c73a64c86bfd4885c9e33e3e557a867
|
|
BLAKE2b-256 checksum How to use checksums |
b51a5a3229af608bb185c6f6611a23593ae4101a5b89b674860b7ee0f4a8adc1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
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 Jun 22, 2025.
Transparency logRelease files / pyright_cov-0.2.2-py3-none-any.whl
| Download URL | pyright_cov-0.2.2-py3-none-any.whl |
|---|---|
| Size | 3.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
1a6f14ea28fcd0585325400733fe66d417a78c527da7676aeb8549a008d276a9
|
|
BLAKE2b-256 checksum How to use checksums |
d6214ecb58883d7a1802c9f780e5650dfd10492be457d120a8abf0b7753e15e9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
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 Jun 22, 2025.
Transparency logSecurity for pyright-cov 0.2.2
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 pyright_cov-0.2.2.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 Jun 22, 2025.
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.