Metadata
Release files for asrtt 1.3.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 | |
|---|---|---|---|---|
| asrtt-1.3.2.tar.gz | 5.6 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| asrtt-1.3.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 12.8 kB
Release files / asrtt-1.3.2.tar.gz
| Download URL | asrtt-1.3.2.tar.gz |
|---|---|
| Size | 5.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a466330152e2e146cedcf1ea8a9311bc673aed6c0bf7fcf7f1ff4a567298f1e9
|
|
BLAKE2b-256 checksum How to use checksums |
e5b7005207fa065b147722886629e34adf37b0d3979e65e3d2ac970c5e5c0795
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.12.1 pkginfo/1.4.2 requests/2.19.1 setuptools/40.4.3 requests-toolbelt/0.8.0 tqdm/4.26.0 CPython/3.7.1
|
Release files / asrtt-1.3.2-py3-none-any.whl
| Download URL | asrtt-1.3.2-py3-none-any.whl |
|---|---|
| Size | 7.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
08fb3f676a12f960daedf3d6f417a6ae452a84f2ba692cad0ceb497b5ed5a50e
|
|
BLAKE2b-256 checksum How to use checksums |
edf809488e9d1ef374a49d84f17545a289944a0ed4c2363fc223d37a1a691a96
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.12.1 pkginfo/1.4.2 requests/2.19.1 setuptools/40.4.3 requests-toolbelt/0.8.0 tqdm/4.26.0 CPython/3.7.1
|
Security for asrtt 1.3.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.