The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for avss 0.0.2
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 | |
|---|---|---|---|---|
| avss-0.0.2.tar.gz | 5.1 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| avss-0.0.2-py2.py3-none-any.whl | Python 2, Python 3 | none | any | Details |
Total release size: 12.1 kB
Release files / avss-0.0.2.tar.gz
| Download URL | avss-0.0.2.tar.gz |
|---|---|
| Size | 5.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
91ba9f5affdfe71bd2ee9ae1f16dc06b847575597fa5e51f294bc4d28693e6dd
|
|
BLAKE2b-256 checksum How to use checksums |
d362775c154d53fe385eeb431244765465574d2c16272b15013463c6820f7064
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
python-requests/2.26.0
|
Release files / avss-0.0.2-py2.py3-none-any.whl
| Download URL | avss-0.0.2-py2.py3-none-any.whl |
|---|---|
| Size | 7.0 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
d6e3e6c0991c85e2653173cb322d8e1f3be75395a1766585abbf5dbc34683366
|
|
BLAKE2b-256 checksum How to use checksums |
ff77d7df57a716001bf31526fc4343e7f804b688497742dad7f8ba1189c023b1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
python-requests/2.26.0
|
Security for avss 0.0.2
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.
