SLYP
Stephen Lints Your Python
An opinionated linter and fixer.
Full documentation: https://slyp.readthedocs.io/en/latest/index.html
Table of Contents
Hi
👋
I'm Stephen. I'm going to lint (and fix) your Python code.
I wrote this linter because nothing else out there implemented these rules, and some of them needed CST (rather than AST), so there was no plugin framework (e.g. flake8 plugins) which I could use.
I hope it helps you.
Installation
slyp is a python package and can be run as a pre-commit hook.
On supported python versions, it should be installed with
pip install slyp
Usage
Either use it as a CLI tool:
slyp
Or as a pre-commit hook using the following pre-commit-config.yaml:
- repo: https://github.com/sirosen/slyp
rev: 0.10.3
hooks:
- id: slyp
License
slyp is distributed under the terms of the MIT license.
1 maintainer
Metadata
1 maintainer
Release files for slyp 0.10.3
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 | |
|---|---|---|---|---|
| slyp-0.10.3.tar.gz | 42.2 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| slyp-0.10.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 76.0 kB
Release files / slyp-0.10.3.tar.gz
| Download URL | slyp-0.10.3.tar.gz |
|---|---|
| Size | 42.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0c8ade9ebfbc55fdeef7a1f9f84dd0836007e74b1b821a59b07c38b922f9e922
|
|
BLAKE2b-256 checksum How to use checksums |
9198a18a64a01eaaae7af6e8d4862d9cd319a90a472eee4f2c925a7118250a8a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Sep 14, 2026.
Transparency logRelease files / slyp-0.10.3-py3-none-any.whl
| Download URL | slyp-0.10.3-py3-none-any.whl |
|---|---|
| Size | 33.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
3102e497ad964369d8160f338a2fb45bd06b44d4c9c9f4a29aba4e5989b46d99
|
|
BLAKE2b-256 checksum How to use checksums |
346a25c673c4cb8958fcb82bfacdfac67bdef50c5c1ea8f2fda35c8c73590577
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Sep 14, 2026.
Transparency logSecurity for slyp 0.10.3
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 slyp-0.10.3.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 Sep 14, 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.
