The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for AsyncClient 0.0.1
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 | |
|---|---|---|---|---|
| AsyncClient-0.0.1.tar.gz | 16.3 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| AsyncClient-0.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 40.3 kB
Release files / AsyncClient-0.0.1.tar.gz
| Download URL | AsyncClient-0.0.1.tar.gz |
|---|---|
| Size | 16.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
30369de9c24686d868db606765e30e587f60275d2919086a2ec7dd9630af38ed
|
|
BLAKE2b-256 checksum How to use checksums |
6987e01728ad8d4878b289e4524e95e831b723392fe731e3c562e3475c31d96d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.7.16
|
Release files / AsyncClient-0.0.1-py3-none-any.whl
| Download URL | AsyncClient-0.0.1-py3-none-any.whl |
|---|---|
| Size | 24.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
5108e254777f91b9255cc1cb35cbff63f1c15abbc24f4d653943178810a6e73c
|
|
BLAKE2b-256 checksum How to use checksums |
98e263596833ec7011d0cb2d485f95f067a9ff7b47ecfc6c055bcebce881b1db
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.7.16
|
Security for AsyncClient 0.0.1
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.
