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