The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for asyncchatclient 1.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 | |
|---|---|---|---|---|
| asyncchatclient-1.0.1.tar.gz | 909 Bytes | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| asyncchatclient-1.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 2.0 kB
Release files / asyncchatclient-1.0.1.tar.gz
| Download URL | asyncchatclient-1.0.1.tar.gz |
|---|---|
| Size | 909 Bytes |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1820075b6467eef6c1cdd3b768898b2abb2db4b19118556ef6164d5c94a284f4
|
|
BLAKE2b-256 checksum How to use checksums |
e3fc0b7a55381f3db8c9c5189a91e5d4143dff209c954a81f6b831facf9680a5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.9.16
|
Release files / asyncchatclient-1.0.1-py3-none-any.whl
| Download URL | asyncchatclient-1.0.1-py3-none-any.whl |
|---|---|
| Size | 1.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d724559bbd511858042a9e049499a37f8966ce0119216de087064af38a597e60
|
|
BLAKE2b-256 checksum How to use checksums |
7258fdfec7c6ce97818e134175b853d61c1d26924ede571b6a86df9a65401ad1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.9.16
|
Security for asyncchatclient 1.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.
