Metadata
Release files for avassa 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 | |
|---|---|---|---|---|
| avassa-0.0.1.tar.gz | 1.1 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| avassa-0.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 6.4 kB
Release files / avassa-0.0.1.tar.gz
| Download URL | avassa-0.0.1.tar.gz |
|---|---|
| Size | 1.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
09c97143d96a1e1c5ec606004a57ec40919ddf264336f7f73002d2a248feffcf
|
|
BLAKE2b-256 checksum How to use checksums |
644c37ae51d17b17c75ad2f1e39e46b1ba23baff6fe9e3a3901f101f823b8cfd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.3.0 pkginfo/1.6.1 requests/2.22.0 setuptools/51.1.1 requests-toolbelt/0.9.1 tqdm/4.55.1 CPython/3.8.5
|
Release files / avassa-0.0.1-py3-none-any.whl
| Download URL | avassa-0.0.1-py3-none-any.whl |
|---|---|
| Size | 5.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
42ccb0157c4d40f242c9fc0ed21bb027eab97d40b68408e95b607d3a316074a8
|
|
BLAKE2b-256 checksum How to use checksums |
dcd495ad2a814e91a650cf5fd75efeaf1b30b64fd7c204e8b23cdff24e18ce0c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.3.0 pkginfo/1.6.1 requests/2.22.0 setuptools/51.1.1 requests-toolbelt/0.9.1 tqdm/4.55.1 CPython/3.8.5
|
Security for avassa 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.