The author of this package has not provided a project description
Metadata
Release files for tggl-client 1.2.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 | |
|---|---|---|---|---|
| tggl_client-1.2.0.tar.gz | 1.4 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| tggl_client-1.2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 3.4 kB
Release files / tggl_client-1.2.0.tar.gz
| Download URL | tggl_client-1.2.0.tar.gz |
|---|---|
| Size | 1.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
577609590625155191947d3770d9367b9c07a52ef48fa1d75e49014dabdd917c
|
|
BLAKE2b-256 checksum How to use checksums |
2fb6b0923e37135a7b66b837c21fbb0e73aea424e4db296f241d99a456f4d62d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.3
|
Release files / tggl_client-1.2.0-py3-none-any.whl
| Download URL | tggl_client-1.2.0-py3-none-any.whl |
|---|---|
| Size | 1.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
3946566ea5b1dda69f06b46e27998b104151b96d02adf5292b73413a3a7f499c
|
|
BLAKE2b-256 checksum How to use checksums |
5fd104341914bb533a7f34000d92f94bc7cc760968a98c819bd8bac4c4d4f45f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.3
|
Security for tggl-client 1.2.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.