1 maintainer
Metadata
1 maintainer
Release files for atu 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 | |
|---|---|---|---|---|
| atu-0.0.1.tar.gz | 1.3 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| atu-0.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 3.6 kB
Release files / atu-0.0.1.tar.gz
| Download URL | atu-0.0.1.tar.gz |
|---|---|
| Size | 1.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
00b77d8aaf59511b9c90fb7c2878df048a99d852b36eeea2b0ce0a648de3965b
|
|
BLAKE2b-256 checksum How to use checksums |
ed6f0f7ed6953b281dfbd1e4ecfb1a66ce874a4c706783bd86403146bf525bf2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.3.0 pkginfo/1.7.0 requests/2.25.1 setuptools/49.2.1 requests-toolbelt/0.9.1 tqdm/4.56.0 CPython/3.9.1
|
Release files / atu-0.0.1-py3-none-any.whl
| Download URL | atu-0.0.1-py3-none-any.whl |
|---|---|
| Size | 2.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
091bc429e9b111d9f07068140d00305325f093fedf1a700d3b707c72cdad95bd
|
|
BLAKE2b-256 checksum How to use checksums |
bc5a41e69918f6c5bbe90f65a0bd631bfbc1a28d17c08480ae7816d7b1602527
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.3.0 pkginfo/1.7.0 requests/2.25.1 setuptools/49.2.1 requests-toolbelt/0.9.1 tqdm/4.56.0 CPython/3.9.1
|
Security for atu 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.
