The author of this package has not provided a project description
Metadata
Release files for senpy-linter 0.1.1
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.1.tar.gz | 32.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| senpy_linter-0.1.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 62.1 kB
Release files / senpy_linter-0.1.1.tar.gz
| Download URL | senpy_linter-0.1.1.tar.gz |
|---|---|
| Size | 32.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
00a40d682749fe557e612fbdfe442cebd32b267793b24992516b0fb06d16ee19
|
|
BLAKE2b-256 checksum How to use checksums |
e4645a9ed83c4295ae37a3e71db562dd05931237f0d58d8513dac3f44ebc2beb
|
| 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.1-py3-none-any.whl
| Download URL | senpy_linter-0.1.1-py3-none-any.whl |
|---|---|
| Size | 30.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
8f7e2ff4cab32d12eb421aead4bba4ab2483c25094a8dde5708525bec845ac9a
|
|
BLAKE2b-256 checksum How to use checksums |
10430f2775c3a67ee604990ab71ecadaa9646c5dac42ec1b16eacd5afbb52312
|
| 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.1
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.