Metadata
Release files for axit 0.0.5
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 | |
|---|---|---|---|---|
| axit-0.0.5.tar.gz | 2.3 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| axit-0.0.5-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 5.6 kB
Release files / axit-0.0.5.tar.gz
| Download URL | axit-0.0.5.tar.gz |
|---|---|
| Size | 2.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b375ca002f730dcf5e0815020817409f8794064b104cfb7fa3b992a2ac7a5241
|
|
BLAKE2b-256 checksum How to use checksums |
4d5d29aaafea9e5dba98c714e34fab73bc1126ac0c9b516212c0b71cb266242b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.1 importlib_metadata/3.10.0 pkginfo/1.7.0 requests/2.25.1 requests-toolbelt/0.9.1 tqdm/4.59.0 CPython/3.9.2
|
Release files / axit-0.0.5-py3-none-any.whl
| Download URL | axit-0.0.5-py3-none-any.whl |
|---|---|
| Size | 3.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
add94c06d68818f0d4e22736fd04e645a6dcfe23b2272593dbcc3b8b445b2fee
|
|
BLAKE2b-256 checksum How to use checksums |
1c3dd3bbba0d0069308755f1c0875813cc5a6f049e11c17b36f132b25ce32150
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.1 importlib_metadata/3.10.0 pkginfo/1.7.0 requests/2.25.1 requests-toolbelt/0.9.1 tqdm/4.59.0 CPython/3.9.2
|
Security for axit 0.0.5
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.