The author of this package has not provided a project description
Metadata
Release files for senpy-linter 0.1.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.1.0.tar.gz | 22.3 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| senpy_linter-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 41.9 kB
Release files / senpy_linter-0.1.0.tar.gz
| Download URL | senpy_linter-0.1.0.tar.gz |
|---|---|
| Size | 22.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
fc28e97186c55dc1e4ff661e08897c11c29a10cf42d9b7b26e3acf04c8ad4ed0
|
|
BLAKE2b-256 checksum How to use checksums |
bfbdc6bdb7d44333ddaaa4ae2267be78e9d6c4a8eb911705b4d184df06839ef9
|
| 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.0-py3-none-any.whl
| Download URL | senpy_linter-0.1.0-py3-none-any.whl |
|---|---|
| Size | 19.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
49dbffb21c4b14721800c4c7d90c208aeebb7332a30fe504c0ba97fb63fb6e2b
|
|
BLAKE2b-256 checksum How to use checksums |
9b59ac59db07dca532eecd0f671970c29b0837330bdd6897ede357390ee00d09
|
| 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.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.