The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for tocky 0.0.17
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 | |
|---|---|---|---|---|
| tocky-0.0.17.tar.gz | 30.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| tocky-0.0.17-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 68.6 kB
Release files / tocky-0.0.17.tar.gz
| Download URL | tocky-0.0.17.tar.gz |
|---|---|
| Size | 30.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
acdebe57552492d43c86e4cda1989285814fa9847cc2fac03a4d2bdc3604e7ea
|
|
BLAKE2b-256 checksum How to use checksums |
69f2b78a21fd17cd2839f31106f2cdd17812e2174c8bdb1927f74a415b993ae8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.7.1 CPython/3.11.1 Windows/10
|
Release files / tocky-0.0.17-py3-none-any.whl
| Download URL | tocky-0.0.17-py3-none-any.whl |
|---|---|
| Size | 37.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
86224d102e67b02d4f47f7dbdd4464c940a21a39f546d82c92a8508b6aea25ff
|
|
BLAKE2b-256 checksum How to use checksums |
46007d93c2348eae6b4b61c0125dd70fb17d2e8b33261515bbe8205b1e240e26
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.7.1 CPython/3.11.1 Windows/10
|
Security for tocky 0.0.17
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.
