The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for senpy-linter 0.2.0
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.2.0.tar.gz | 48.5 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| senpy_linter-0.2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 94.7 kB
Release files / senpy_linter-0.2.0.tar.gz
| Download URL | senpy_linter-0.2.0.tar.gz |
|---|---|
| Size | 48.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f47ff4137612bcb71d298191d4f38901293dfb40166212574363c941c391c3cd
|
|
BLAKE2b-256 checksum How to use checksums |
6f31f2041b9cde2281ce91afff1046a2234a537f860c17172cc9fefbfddf8d90
|
| 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.2.0-py3-none-any.whl
| Download URL | senpy_linter-0.2.0-py3-none-any.whl |
|---|---|
| Size | 46.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
93012c2fd82ff5bb5c0871cdf4715bda2824fc570f67531c95b9b4932faa692f
|
|
BLAKE2b-256 checksum How to use checksums |
6f605ee12c81082410571895945e773a5551a4b3edaa992a3707be583d6c5113
|
| 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.2.0
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.
