Ruff-cgx
Lint and format CGX files (collagraph single-file components) with ruff.
Usage
# Install in your environment (for example with uv)
uv add --dev ruff-cgx
# Show help for the tool
uv run ruff-cgx -h
# Check/Lint every cgx file in current folder (recursively)
uv run ruff-cgx check .
# Format every cgx file in the current folder (recursively)
uv run ruff-cgx format .
# Just check if there would be any changes from the formatter
uv run ruff-cgx format --check .
# Format just a single file
uv run ruff-cgx format my-component.cgx
# Format a folder and file
uv run ruff-cgx format ../folder_with_cgx_files my-component.cgx
Configuration
To use a specific ruff installation (e.g., in an LSP server):
import ruff_cgx
ruff_cgx.set_ruff_command("/path/to/custom/ruff")
Metadata
Release files for ruff-cgx 0.2.4
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 |
|---|---|---|---|---|
| ruff_cgx-0.2.4.tar.gz | 21.6 kB | With provenance | Details for ruff_cgx-0.2.4.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| ruff_cgx-0.2.4-py3-none-any.whl | Python 3 | none | any | Details for ruff_cgx-0.2.4-py3-none-any.whl |
Total release size: 38.5 kB
Release files / ruff_cgx-0.2.4.tar.gz
| Download URL | ruff_cgx-0.2.4.tar.gz |
|---|---|
| Size | 21.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f7fde133ed54a6b28160e8ecde89f439fc4e47f9a3cc2764a993bda18805aaec
|
|
BLAKE2b-256 checksum How to use checksums |
6b13f8fc5cc06c911643537ee94da5167e8e1fd4b3cd7abf59fba57b4aef492a
|
| 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 Mar 9, 2026.
Transparency logRelease files / ruff_cgx-0.2.4-py3-none-any.whl
| Download URL | ruff_cgx-0.2.4-py3-none-any.whl |
|---|---|
| Size | 16.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
42e5c96ffd59e3359c0f37a675fdd60f3ddfa08d1375d788676ad3eeecb006f3
|
|
BLAKE2b-256 checksum How to use checksums |
16a9bce383c3e7b461c290829a900f51222907f7f59a268ffdf1b5f286661548
|
| 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 Mar 9, 2026.
Transparency logSecurity for ruff-cgx 0.2.4
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 ruff_cgx-0.2.4.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 Mar 9, 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.