Metadata
Release files for asyncapi-container 0.4.4
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 | |
|---|---|---|---|---|
| asyncapi_container-0.4.4.tar.gz | 4.6 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| asyncapi_container-0.4.4-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 14.1 kB
Release files / asyncapi_container-0.4.4.tar.gz
| Download URL | asyncapi_container-0.4.4.tar.gz |
|---|---|
| Size | 4.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
54ae4b26f810a8386ca69bc37d4fe0f8ab0b27c8fc736e54b8a1781d0f45cd23
|
|
BLAKE2b-256 checksum How to use checksums |
9757f387b08bd4700893a01c1f31194393c26e2aa1e4f3b390ddfde29c61671a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/2.1.3 CPython/3.11.9 Darwin/22.6.0
|
Release files / asyncapi_container-0.4.4-py3-none-any.whl
| Download URL | asyncapi_container-0.4.4-py3-none-any.whl |
|---|---|
| Size | 9.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
7a6868e827a76d777ee48c6a717df5540564fe10c622595585ffa1186389c352
|
|
BLAKE2b-256 checksum How to use checksums |
4f2ecfbbf3cabfb83c17f49a318e6536047c3274dff42611e3d024bd2beb0f69
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/2.1.3 CPython/3.11.9 Darwin/22.6.0
|
Security for asyncapi-container 0.4.4
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.