pyright to gitlab
Simple Python tool to convert Pyright JSON output to GitLab Code Quality report format.
Zero runtime dependencies - Pure Python implementation using only the standard library.
Usage
Run the script with the path to the pyright output file:
$ pip install pyright-to-gitlab
$ pyright . --outputjson | pyright-to-gitlab > code-quality.json
Alternatively, the module can be called:
$ pip install pyright-to-gitlab
$ pyright . --outputjson | python -m pyright_to_gitlab > code-quality.json
Custom path prefix
The --prefix option adds a custom prefix path to the file paths in the output. This is
useful for mono-repos, where the paths in the pyright output is not the repository root.
$ pyright . --outputjson | pyright-to-gitlab --prefix my-app > code-quality.json
Testing
To run the tests, execute
$ uv run poe check
Metadata
Release files for pyright-to-gitlab 1.3.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 | |
|---|---|---|---|---|
| pyright_to_gitlab-1.3.2.tar.gz | 56.1 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| pyright_to_gitlab-1.3.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 61.7 kB
Release files / pyright_to_gitlab-1.3.2.tar.gz
| Download URL | pyright_to_gitlab-1.3.2.tar.gz |
|---|---|
| Size | 56.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7119560ffcbde32dc55ebb1ba8de45643832a34af9687377133677f3a510bb68
|
|
BLAKE2b-256 checksum How to use checksums |
95a34f142fd28a1582f31edbeb5aa1738f7b3fcf622fd729fd548f8c3b8b1338
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 Apr 10, 2026.
Transparency logRelease files / pyright_to_gitlab-1.3.2-py3-none-any.whl
| Download URL | pyright_to_gitlab-1.3.2-py3-none-any.whl |
|---|---|
| Size | 5.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
416339034fe8cc80c24d7952f41921ccde85ca8e7095a128948546fc7765a2d3
|
|
BLAKE2b-256 checksum How to use checksums |
ea7949c048dbc53bacb3a7a876771b08cdf3fa7d4fe26cf9d9a686bde3f8aa50
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 Apr 10, 2026.
Transparency logSecurity for pyright-to-gitlab 1.3.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
All 2 files in this release have been uploaded with provenance metadata.
Attestation for pyright_to_gitlab-1.3.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 Apr 10, 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.