The author of this package has not provided a project description
Metadata
Release files for senpy-linter 0.1.2
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.2.tar.gz | 33.5 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| senpy_linter-0.1.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 65.0 kB
Release files / senpy_linter-0.1.2.tar.gz
| Download URL | senpy_linter-0.1.2.tar.gz |
|---|---|
| Size | 33.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e6f32fb0eab5bb2ab5838c3df166a5aa948469dcefbd10b4cbd011dc3cb653fd
|
|
BLAKE2b-256 checksum How to use checksums |
d668f5139e80c2eccb93671a902b76b72cf0050e07bdfe220fb5a01a1820f35f
|
| 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.2-py3-none-any.whl
| Download URL | senpy_linter-0.1.2-py3-none-any.whl |
|---|---|
| Size | 31.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
777e8716ef2589a77f4cbf17be0be88f9f03bcdea3c1ea724aef7ce5c370a5af
|
|
BLAKE2b-256 checksum How to use checksums |
265b33f62ce5e5f1fec5a7ee95166fbce0b9c43b14846b28ffefb50061b92aa8
|
| 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.2
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.