1 maintainer
Metadata
1 maintainer
Release files for asyncCommunication 1.1.3
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 | |
|---|---|---|---|---|
| asynccommunication-1.1.3.tar.gz | 2.5 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| asyncCommunication-1.1.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 5.4 kB
Release files / asynccommunication-1.1.3.tar.gz
| Download URL | asynccommunication-1.1.3.tar.gz |
|---|---|
| Size | 2.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
70b2c44f90f2d036c126c6f6e2527a2290e1fa22430596b9a1879d02d20c4cc9
|
|
BLAKE2b-256 checksum How to use checksums |
271a0a892991e82075c67f93ed7c4978102b44a48d69a5cb006d2804c4724f3d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.0 CPython/3.11.0
|
Release files / asyncCommunication-1.1.3-py3-none-any.whl
| Download URL | asyncCommunication-1.1.3-py3-none-any.whl |
|---|---|
| Size | 2.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
9c6ea41242aff344adb5a51c42e547dd4d7430fd6614ec4622e9306350bdfb0d
|
|
BLAKE2b-256 checksum How to use checksums |
049b106cb7cb817bae4566322054e935292031c5e763b95e59b621974b872eca
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.0 CPython/3.11.0
|
Security for asyncCommunication 1.1.3
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.
