📘 learn more on GitHub!
1 maintainer
Metadata
1 maintainer
Release files for toil-strelka 1.0.9
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 | |
|---|---|---|---|---|
| toil_strelka-1.0.9.tar.gz | 12.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| toil_strelka-1.0.9-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 25.3 kB
Release files / toil_strelka-1.0.9.tar.gz
| Download URL | toil_strelka-1.0.9.tar.gz |
|---|---|
| Size | 12.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6a78b56f00910e3382065d927ad21e246166dfe9ea8229c171665f267decbcde
|
|
BLAKE2b-256 checksum How to use checksums |
4f697f71e268c0a24d1acd05cec0a327951e344a8d5b22830c66614753f34fb4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.9.6
|
Release files / toil_strelka-1.0.9-py3-none-any.whl
| Download URL | toil_strelka-1.0.9-py3-none-any.whl |
|---|---|
| Size | 13.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c7f0db752e7ffadd08b9d87771484469e43420db1735e88c316da8d1d28a8cb1
|
|
BLAKE2b-256 checksum How to use checksums |
8ecb778387263e3b84240bb9e5654cce5e57a034b1c2f3e5196ca829af3c7138
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.9.6
|
Security for toil-strelka 1.0.9
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.
