Metadata
Release files for tiller 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 | |
|---|---|---|---|---|
| tiller-0.1.0.tar.gz | 1.8 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| tiller-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 3.8 kB
Release files / tiller-0.1.0.tar.gz
| Download URL | tiller-0.1.0.tar.gz |
|---|---|
| Size | 1.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8387e2660b3b971970afeee9c9cc5b31955ffb74e30b3fc002800fe91f3a67f2
|
|
BLAKE2b-256 checksum How to use checksums |
8c1bbea50471f8919143cb754fd96947f0ab5ae13010fe6c477e1663882b7224
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.3.0 pkginfo/1.6.1 requests/2.25.1 setuptools/49.2.1 requests-toolbelt/0.8.0 tqdm/4.54.1 CPython/3.8.7
|
Release files / tiller-0.1.0-py3-none-any.whl
| Download URL | tiller-0.1.0-py3-none-any.whl |
|---|---|
| Size | 2.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
460d96614200f8f831bed37d4e49ad3a85b8f90358ec36c1adb4ac7076801691
|
|
BLAKE2b-256 checksum How to use checksums |
2391412d34d55dca748d9468ab479a0d402a677129be27dc53202928f765bdef
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.3.0 pkginfo/1.6.1 requests/2.25.1 setuptools/49.2.1 requests-toolbelt/0.8.0 tqdm/4.54.1 CPython/3.8.7
|
Security for tiller 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.