The author of this package has not provided a project description
Metadata
Release files for senpy-linter 0.1.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 | |
|---|---|---|---|---|
| senpy_linter-0.1.3.tar.gz | 36.2 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| senpy_linter-0.1.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 67.8 kB
Release files / senpy_linter-0.1.3.tar.gz
| Download URL | senpy_linter-0.1.3.tar.gz |
|---|---|
| Size | 36.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
32fc903b713fc1a468ebf4e940c6bbb849882fce0cde626410e03a5d72025623
|
|
BLAKE2b-256 checksum How to use checksums |
954ec3fa014cf6835412b1fa15d3deac689d7e40277397c40c94c2ffe465dd51
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.6
|
Release files / senpy_linter-0.1.3-py3-none-any.whl
| Download URL | senpy_linter-0.1.3-py3-none-any.whl |
|---|---|
| Size | 31.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
9d954b391df7015d81fd136b03c64f1cedc4562aa612319150e72fe957a4fb36
|
|
BLAKE2b-256 checksum How to use checksums |
de9e66f1b82304351b21ad01236a09d469714909dd901b03d53fe33d584b56bb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.6
|
Security for senpy-linter 0.1.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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A 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.