The author of this package has not provided a project description
Metadata
Release files for senpy-linter 0.2.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.2.3.tar.gz | 58.1 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| senpy_linter-0.2.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 113.5 kB
Release files / senpy_linter-0.2.3.tar.gz
| Download URL | senpy_linter-0.2.3.tar.gz |
|---|---|
| Size | 58.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9b4786566cf9d37a891925093a7e7989b684bb8e996859de7de039714be64f98
|
|
BLAKE2b-256 checksum How to use checksums |
d855c2af8be16620939f555fc088ca2fea0e2c6983410b0e7df3d1d0f4d9c5f0
|
| 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.3-py3-none-any.whl
| Download URL | senpy_linter-0.2.3-py3-none-any.whl |
|---|---|
| Size | 55.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
90bf570205d98d5fcdade4532d716da626afe23c34d677b594f53cad09644565
|
|
BLAKE2b-256 checksum How to use checksums |
e9f641158091934e8631014d214dd5d427905d8369221321320d350ba9a7dab9
|
| 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.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.