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