The author of this package has not provided a project description
Metadata
Release files for senpy-linter 0.1.6
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.6.tar.gz | 38.1 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| senpy_linter-0.1.6-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 71.8 kB
Release files / senpy_linter-0.1.6.tar.gz
| Download URL | senpy_linter-0.1.6.tar.gz |
|---|---|
| Size | 38.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
bfb615cc3a9b904569406ea53c846755bbf4db289785a4e54ece20ceb7cb4955
|
|
BLAKE2b-256 checksum How to use checksums |
2ddc61f01a43ce80cb18ea8ef2eec9e69f9a2e05ec114b1d83a012fcff712b22
|
| 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.6-py3-none-any.whl
| Download URL | senpy_linter-0.1.6-py3-none-any.whl |
|---|---|
| Size | 33.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
63697c862baebc6bcd4b82ce15256cec18caa6fb17737f318607cca0d6f62473
|
|
BLAKE2b-256 checksum How to use checksums |
475095d391c7fa19860b65914a0a73c6073860eb962038a48f38c61ee07dcc88
|
| 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.6
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.