The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for senpy-linter 0.1.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 | |
|---|---|---|---|---|
| senpy_linter-0.1.4.tar.gz | 37.8 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| senpy_linter-0.1.4-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 71.2 kB
Release files / senpy_linter-0.1.4.tar.gz
| Download URL | senpy_linter-0.1.4.tar.gz |
|---|---|
| Size | 37.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
86443eb12775df014cea6d3ae61088d7e9e6fe8ac70e2b3a4e8342a48eadc636
|
|
BLAKE2b-256 checksum How to use checksums |
34785169c727d77161317349ed3435c538757cda6c7e040616a5bcf45f80b175
|
| 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.4-py3-none-any.whl
| Download URL | senpy_linter-0.1.4-py3-none-any.whl |
|---|---|
| Size | 33.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
22aee0da29404fc519cf53c44c8278e1a0512e14a28bed383756fa50bd6bebac
|
|
BLAKE2b-256 checksum How to use checksums |
19bf66ebde1da21559653b0ac479a6cda5af45e958e9c4f33eaf2fb69e734b8a
|
| 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.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.
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.
