The author of this package has not provided a project description
Metadata
Release files for aoa-vis 0.1.0
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 | |
|---|---|---|---|---|
| aoa-vis-0.1.0.tar.gz | 2.1 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| aoa_vis-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 4.4 kB
Release files / aoa-vis-0.1.0.tar.gz
| Download URL | aoa-vis-0.1.0.tar.gz |
|---|---|
| Size | 2.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
70bbacb44a68bb323ef756b14c82ae247385e403c1b016c273672e72f558ac70
|
|
BLAKE2b-256 checksum How to use checksums |
d98c14def0ce52e6c187d4687e9352124f906b06c1ee5e6d70b26e8303507c16
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.0.5 CPython/3.8.6 Linux/5.8.18-1-MANJARO
|
Release files / aoa_vis-0.1.0-py3-none-any.whl
| Download URL | aoa_vis-0.1.0-py3-none-any.whl |
|---|---|
| Size | 2.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
17cc41ad1ff48e2d90e1cb95a892045f133925a021083001ecea3174f420c0a5
|
|
BLAKE2b-256 checksum How to use checksums |
05f735be125c836b6139a21cf1384a0619f178a11a6c25ce96d6fd80a0dc7929
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.0.5 CPython/3.8.6 Linux/5.8.18-1-MANJARO
|
Security for aoa-vis 0.1.0
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.