structlint
Configurable development CLI that checks various aspects of architecture: method order, documentation, tests, and internal module dependency.
Roadmap
configuration tests (thorough)- remaining tests
checks_test.pycli_test.pycollection_test.pyconfiguration_test.pylogic_test.pyreporting_test.pyutils_test.py
- configuration docs
- add explicit mapping tables
- update configuration tests
- update configuration docs
- code once-over
- docs once-over
- tests once-over
- project infra overhaul
- docs CI -> publish docs
- publish package on pypi
- add CLI package output to flake.nix
- add to all projects and collect live-use feedback
- version 0.3.0
- share on reddit, get feedback
- release 0.4.0
- performance optimization
- release 0.5.0
Metadata
Release files for structlint 0.2.1
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 |
|---|---|---|---|---|
| structlint-0.2.1.tar.gz | 16.1 kB | With provenance | Details for structlint-0.2.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| structlint-0.2.1-py3-none-any.whl | Python 3 | none | any | Details for structlint-0.2.1-py3-none-any.whl |
Total release size: 33.0 kB
Release files / structlint-0.2.1.tar.gz
| Download URL | structlint-0.2.1.tar.gz |
|---|---|
| Size | 16.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9193ca745771ca30c16da9a4c05a53a0019444a6a94875a2c911994cb0601071
|
|
BLAKE2b-256 checksum How to use checksums |
fcfa82e1b32cc4658aee612b63797817f2baf988a60c682a14a658b4d0db9114
|
| 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 Oct 26, 2025.
Transparency logRelease files / structlint-0.2.1-py3-none-any.whl
| Download URL | structlint-0.2.1-py3-none-any.whl |
|---|---|
| Size | 16.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d04568cdb6df02f2a54de3a4cbfafb28695de3c7f1f6742115cffcb7d8e130fc
|
|
BLAKE2b-256 checksum How to use checksums |
756b1b15c0eaf40e75f3b54dd681ae2e8e0662643912f4d548eed2ba07139bac
|
| 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 Oct 26, 2025.
Transparency logSecurity for structlint 0.2.1
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 structlint-0.2.1.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 Oct 26, 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.